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 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? Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:[EMAIL PROTECTED] "Quidquid latine dictum sit, altum sonatur."
pgpvzUri7eewX.pgp
Description: PGP signature
