Just installed RC2 from delta'd ISOs, and on second boot the SUSEwatcher replacement has a red bang, so I click and select "Update" in the dialog for item "kernel"... and get another dialog with an angry red X and "Dependency Resolution Failed", with message "Resolver failed". I thought this stuff was fixed? How to diagnose for filing an issue? -- Glenn Holmer (Linux registered user #16682) "I love virtuosity. I love danger." -Pierre Boulez, 2005
On Sat, 22 Apr 2006, Glenn Holmer wrote:
Just installed RC2 from delta'd ISOs, and on second boot the SUSEwatcher replacement has a red bang, so I click and select "Update" in the dialog for item "kernel"... and get another dialog with an angry red X and "Dependency Resolution Failed", with message "Resolver failed".
I thought this stuff was fixed? How to diagnose for filing an issue?
We need /var/log/zmd-* and /var/log/YaST2/* attached to a bug to be able to look into this ;) Regards Christoph
On Saturday 22 April 2006 07:11, Christoph Thiel wrote:
We need /var/log/zmd-* and /var/log/YaST2/* attached to a bug to be able to look into this ;)
#168607 -- Glenn Holmer (Linux registered user #16682) "I love virtuosity. I love danger." -Pierre Boulez, 2005
2006/4/22, Glenn Holmer <gholmer@ameritech.net>:
Just installed RC2 from delta'd ISOs, and on second boot the SUSEwatcher replacement has a red bang, so I click and select "Update" in the dialog for item "kernel"... and get another dialog with an angry red X and "Dependency Resolution Failed", with message "Resolver failed".
I thought this stuff was fixed? How to diagnose for filing an issue?
I used smart for update to RC2, without problems, the only thing, is have killed the zmd daemon, because in previous updates, zmd has locking the rpm db. I do'nt know if this problem was resolved.
participants (3)
-
Christoph Thiel -
Glenn Holmer -
Juan Erbes