Packages that were held out of testing (libc6)
Hi,
After the new libc6 has made it to testing, I made an apt-get update.
apt-get upgrade does not upgrade libc6, because it conflicts with php4,
which makes perfect sense. But still, a lot or packages can be upgraded,
although libc6 itself is not.
# apt-get -u upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages have been kept back
bash bison bsdutils buffer cdda2wav cdrecord corewars cron cvs devscripts
dict diffstat dvidvi eject ez-ipupdate fdutils file findutils flex gdb
grep
hostname info libc6 libc6-dev libdv2 libltdl3 libncurses5 libncurses5-dev
libnss-db libpam-modules libpam0g libpcre3 libpng2 libsdl-net1.2
libsensors1
libtiff3g libtiff3g-dev libungif4g libwine lilo lm-sensors locales login
mailx make mkisofs mount mtr-tiny nano ncurses-bin nvi passwd sed
space-orbit strace syslinux tar texinfo util-linux util-linux-locales
whois
wine winesetuptk xjump
The following packages will be upgraded
afio ash bc bsdmainutils cramfsprogs cvsdelta dash dc dialog dosemu gnupg
grace lesstif1 lesstif2 libpam-runtime libtool lm-sensors-source
ncurses-base ncurses-term procmail setserial sharutils ssystem talk talkd
traceroute transfig tuxpuck xfig xfonts-dosemu
30 packages upgraded, 0 newly installed, 0 to remove and 65 not upgraded.
My question is then: why were this packages not in testing earlier,
since they do not depend on the newer libc6?
For instance, the only dependancy of dash is:
Pre-Depends: libc6 (>= 2.2.5-13)
and the version of libc6 that has been in testing for a long time was:
2.2.5-14.3
Is this a bug in the testing scripts, or is it a feature? In the second
case, was is the justification for it?
Daniel
Reply to: