[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Simon Waters wrote:
Keith Abraham wrote:apt-get is reporting that most "testing" packages now require libc6 2.3.5-6 and locales 2.3.5-6. Yet when I try to upgrade these two packages apt-listbugs reports critical bugs which don't seem to exist on Debian's bug lists. Is this one of those times when I need to do a dist-upgrade?Since listbugs queries the database they are in there somewhere.
Listbugs indicated that a directory was missing and I understood this to mean that upgrading libc6 meant some relocation would occur. (Especially since gcc went from version 3.4 to 4.0.)
Also I didn't think critical bugs would stop you installing a package, is that perhaps an option you've chosen somewhere? In configuring listbugs perhaps?
Nope. I just find such words as "critical" a bit frightening. Perhaps I'm being naive in understanding a bug status of "critical" (and "grave") as akin to their use in a hospital?
I believe the advice is always to run "apt-get -s dist-upgrade" when
living in testing or unstable ("-s" is a dry run), it certainly
shouldn't hurt to do a dist-upgrade assuming you have a vanilla testing
or unstable installation.
Having recently done the libc upgrade a couple of times it all "just
worked", and I remember when libc upgrades were fraught and fearful affairs.
Thanks Simon. Doing an "apt-get -s dist-upgrade" didn't throw up any errors/bugs so I'll do an "dist-upgrade" after my next backup. Keith -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html