Robert Schiele <[EMAIL PROTECTED]> writes: > On Mon, Oct 02, 2006 at 09:30:30AM +0200, Andreas Jaeger wrote: >> Robert Schiele <[EMAIL PROTECTED]> writes: >> >> > Ok, sice nobody could answer this for more than 5 months now it seems that >> > there is nobody here that has a clue about this bug. >> >> Sorry, if this got lost. >> >> > Just wanted to inform you that YaST cannot handle this situation correctly >> > and >> > decides on update to delete all affected packages ignoring dependencies >> > even >> > when the affected packages are part of the vital base system like perl. >> > Expect that ignoring this problem will get back at you at a later point in >> > time but since you get either no or just a stupid answer when talking about >> > this to someone I will now just sit down and wait for the disaster... >> >> We increment it now whenever we do a checkin of the basesystem. Would >> this still cause problems? > > No, you don't. You updated the db package (which is definitely part of the
That's a bug ;-( > base system) to 4.4 release but did _not_ increase the number thus causing > YaST to decide to destroy the installed system on upgrade. > > But I repeat the question: Is there a _serious_ reason at all for not updating > the release number when the package is rebuilt? We rebuild that often that people often asked: What's the difference between version -9 and -20? And we have to answer: Just rebuild with newer packages. It would be great to only increase the number if a dependend package changes the ABI. So, neither solution is really good. Could you file a bugreport against basesystem, please? I'll take care of it and discuss with Rudi once he's back from vacation how to finally solve this. Thanks, Andreas -- Andreas Jaeger, [EMAIL PROTECTED], 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
pgpQOWrQ9piBK.pgp
Description: PGP signature
