Hi, Quite often th Software Updater of SuSE 10.1 fails with the message Update 10.1: Dependency Resolution Failed. This time with the additional info "Resolvable id 181816 does not exist.". What kind of error is this? SuSE not having the download site ok? Config error here? Software error in the updater? Sometimes the problem resolves itself. Sometimes installing the updates one-by-one helps. Sometimes starting YOU and updating from there helps, but anyhow it is hard to predict what to do, let alone have less experienced users updating their system. Any clues? Thanks --- Jan P.s In this case the initial packages were beagle (noarch) and beagle (i586). Deselecting "beagle (i586)" and press update. The system says it also needs to update the beagle binary package and all works just fine again :-(
Jan Wielemaker
Hi,
Quite often th Software Updater of SuSE 10.1 fails with the message Update 10.1: Dependency Resolution Failed. This time with the additional info "Resolvable id 181816 does not exist.". What kind of error is this? SuSE not having the download site ok? Config error here? Software error in the updater? Sometimes the problem resolves itself. Sometimes installing the updates one-by-one helps. Sometimes starting YOU and updating from there helps, but anyhow it is hard to predict what to do, let alone have less experienced users updating their system.
Next time you hit this, please open a bugreport at bugzilla.novell.com and attach the logfiles. We need to understand in which circumstances this happens to fix it, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Monday 14 August 2006 04:18, Andreas Jaeger wrote:
Jan Wielemaker
writes: Quite often th Software Updater of SuSE 10.1 fails with the message Update 10.1: Dependency Resolution Failed. This time with the additional info "Resolvable id 181816 does not exist.".
Next time you hit this, please open a bugreport at bugzilla.novell.com and attach the logfiles. We need to understand in which circumstances this happens to fix it,
I am experiencing this too. Sorry, for me this was the straw that broke the camel's back. I have ripped out ZMD by the throat and replaced him with Smart. -- Glenn Holmer (Q-Link: ShadowM) http://www.lyonlabs.org/commodore/c64.html
On Monday 14 August 2006 11:18, Andreas Jaeger wrote:
Jan Wielemaker
writes: Hi,
Quite often th Software Updater of SuSE 10.1 fails with the message Update 10.1: Dependency Resolution Failed. This time with the additional info "Resolvable id 181816 does not exist.". What kind of error is this? SuSE not having the download site ok? Config error here? Software error in the updater? Sometimes the problem resolves itself. Sometimes installing the updates one-by-one helps. Sometimes starting YOU and updating from there helps, but anyhow it is hard to predict what to do, let alone have less experienced users updating their system.
Next time you hit this, please open a bugreport at bugzilla.novell.com and attach the logfiles. We need to understand in which circumstances this happens to fix it,
Thanks for replying. I guess the relevant info is still there. Which logfiles do you like to receive? --- Jan
Jan Wielemaker
On Monday 14 August 2006 11:18, Andreas Jaeger wrote:
Jan Wielemaker
writes: Hi,
Quite often th Software Updater of SuSE 10.1 fails with the message Update 10.1: Dependency Resolution Failed. This time with the additional info "Resolvable id 181816 does not exist.". What kind of error is this? SuSE not having the download site ok? Config error here? Software error in the updater? Sometimes the problem resolves itself. Sometimes installing the updates one-by-one helps. Sometimes starting YOU and updating from there helps, but anyhow it is hard to predict what to do, let alone have less experienced users updating their system.
Next time you hit this, please open a bugreport at bugzilla.novell.com and attach the logfiles. We need to understand in which circumstances this happens to fix it,
Thanks for replying.
I guess the relevant info is still there. Which logfiles do you like to receive?
Put them into bugzilla - /var/log/zmd* from the failure, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Put them into bugzilla - /var/log/zmd* from the failure,
Andreas
Why not do as Amarok did (or similar) as this system still needs extensive testing/debugging. When it crashed it automatically loaded up a email compose window with all the attachments already selected and data required for debugging and just let the use input something in the compose window to describe what they did and send it. I'm sure you'd get a lot more input into the issues than relying on Bugzilla. Going through Bugzilla is a laborious exercise, especially with attachments and a right royal pain in the a**e.
participants (4)
-
Andreas Jaeger
-
Glenn Holmer
-
ianseeks
-
Jan Wielemaker