On 12 Dec 1997, Martin Mitchell wrote: > Chris Fearnley <[EMAIL PROTECTED]> writes: > > > debian/bo/binary-i386/base/libc5_5.4.33-6.deb conflicts with libc6 > > making it IMPOSSIBLE to upgrade!! I had to downgrade to > > libc5_5.4.33-3.deb from a LSL CD (thank goodness this bug is not > > shipped on CDs!!) in order to upgrade to libc6. But I noticed that > > the broken package is still on the ftp sites. So lots of people will > > not be able to upgrade their Debian systems without technical support. > > YUK! > > Huh? The upgrade path is quite clear: install a newer libc5 (5.4.33-7) > from hamm, then you may install libc6.
The solution isn't quite so simple. The libc5 from hamm DEPENDS ON libc6. There is a definate problem here. The dependancies make it difficult to upgrade partially to running libc6 stuff without upgrading the complete distribution. Installing libc5 from hamm pretty much forces you to migrate your development system to libc6 or libc5-altdev since it CONFLICTS with libc5-dev. I'm forwarding this discussion to debian-devel because I'm sick of trying to find a useful workaround for people who just want to install a few packages from hamm without upgrading the whole thing. Here's a basic table of the relationships of the various libc5's +----------------+-----------+-----------+ | | libc6 | libc5-dev | +----------------+-----------+-----------+ | libc5-5.4.33-3 | OK | OK | What we USED to have in bo +----------------+-----------+-----------+ | libc5-5.4.33-6 | CONFLICTS | OK | What is in bo now +----------------+-----------+-----------+ | libc5-5.4.33-7 | OK | CONFLICTS | What is in hamm now +----------------+-----------+-----------+ As you can see, we used to have a working way of installing libc6 whilst keeping libc5-dev and friends. We no longer do. This is in dire need of being fixed. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
