Odd dependancy situation with libc6 and libc6-dev
Wow. I was installing some slink packages today with dpkg on
my hamm system, and I got myself into a wacky situation.
I'd had the latest hamm versions of libc6 and libc6-dev (2.0.7t-1)
installed. I installed the slink version of libc6 (2.0.7u-2) without a
hitch. But then I realized I should have been forced to upgrade
libc6-dev at the same time!
However, I got no conflict error from dpkg. Here's the interesting
output from dpkg --status:
[root@che:/home/che]# dpkg --status libc6-dev 11:51PM
Package: libc6-dev
Status: install ok installed
Priority: standard
Section: devel
Installed-Size: 4841
Maintainer: Dale Scheetz <dwarf@polaris.net>
Source: glibc
Version: 2.0.7t-1
Replaces: ldso (<< 1.9.0-0), man-db (<= 2.3.10-41), gettext (<= 0.10.26-1), ppp (<= 2.2.0f-24), libgdbmg1-dev (<= 1.7.3-24)
Provides: libc-dev
Depends: libc6 (= 2.0.7t-1), gcc (>= 2.7.2.3-1)
Conflicts: libc-dev, libdl1-dev, libdb1-dev, libgdbm1-dev, libpthread0-dev
Description: The GNU C library version 2 (development files).
Includes libc headers, kernel headers and static libraries.
[root@che:/home/che]# dpkg --status libc6 11:53PM
Package: libc6
Status: install ok installed
Priority: required
Section: base
Installed-Size: 1413
Maintainer: Dale Scheetz <dwarf@polaris.net>
Source: glibc
Version: 2.0.7u-2
Pre-Depends: ldso (>= 1.8.10-1)
Conflicts: libc5 (<< 5.4.33-7), libpthread0 (<< 0.7-10)
Description: The GNU C library version 2 (run-time files).
Includes shared libraries needed to run programs.
How can this be? How can libc6-dev still be installed and depend on
libc6 (= 2.0.7t-1) ?
dselect, by the way, did notice that this was naughty and prompted me
to grab the new libc6-dev.
--
Brought to you by the letters M and V and the number 11.
"Someday, we will be." "For it has already begun." -- Akira
Debian GNU/Linux -- where do you want to go tomorrow? http://www.debian.org/
I'm on FurryMUCK as Che, and EFNet and YiffNet IRC as Che_Fox.
Reply to: