http://bugzilla.novell.com/show_bug.cgi?id=492256 User jayambe40@hotmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=492256#c8 --- Comment #8 from Jay Ambee <jayambe40@hotmail.com> 2009-04-06 11:45:03 MDT --- (In reply to comment #6)
Well, we have a known source of inconsistencies since some time ago. See bug #420488. Just recently, from the buildhistory of kdebase4-workspace (that includes kde4-kdm): 2009-03-31 17:46:34 bf786f660b8078df02971c63fb0a6bf3 255 4.2.2-218.3 2009-04-02 23:49:35 10ea56059328be02e18abcd03b09b41e 257 4.2.2-217.2 2009-04-03 22:09:53 10ea56059328be02e18abcd03b09b41e 257 4.2.2-217.3 2009-04-04 18:48:35 2abfa878e47588a65a6ecfe0fc4305f3 259 4.2.2-219.1 2009-04-05 18:31:26 2abfa878e47588a65a6ecfe0fc4305f3 259 4.2.2-219.2 2009-04-06 01:00:21 2abfa878e47588a65a6ecfe0fc4305f3 259 4.2.2-219.3 2009-04-06 11:37:03 58d986bb2e7b1a83a1bc0519d0ce0d29 260 4.2.2-221.1
The release number changed from 218 to 217. And ZYpp will not *update* to a package with a *lower* release number. In this case we were lucky and the release number increased again only two days later, but that's not always the case.
WOW! .... this is great .... but what do want to propose?? Should I just do an online update to the now current versions to resolve the problem?? just log in as root, start yast and give the package update a go?? I am really considering a complete reinstall of the system ... but who knows when I will get stuck again in a sitiaition like this??? Would you mind to give me a clear instruction what to do?? Thanks a lot!! Jay -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.