Re: "apt-get dist-upgrade" wants to trash my system

["Jeffrey L. Taylor" <jeff@austinblues.dyndns.org>]

Quoting Sam Watkins <swatkins@fastmail.fm>:
> On Mon, Jan 10, 2005 at 07:24:35AM -0600, Jeffrey L. Taylor wrote:
> > "apt-get dist-upgrade" wants to remove a bunch of packages, many of
> > them critical.  See below.  How do I figure what is causing this?
> > 
> > TIA,
> >   Jeffrey
> > 
> > # apt-get -u dist-upgrade
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > Calculating Upgrade... Done
> > The following packages will be REMOVED:
> >   adduser amanda-client amanda-common amavisd-new apache apt-file
> >   base-config bind9 binutils bsdmainutils clamav clamav-base
> >   clamav-daemon clamav-freshclam console-common console-data
> >   console-tools courier-authdaemon courier-base courier-imap
> >   courier-imap-ssl courier-maildrop courier-ssl cvs debconf debconf-utils
> >   debhelper devscripts dpkg-dev emacs20 emacsen-common fetchmail
> >   fetchmail-common g++ g++-2.95 gcc gcc-2.95 hotplug iptables
> >   kernel-package kernel-source-2.4.18 less libconvert-tnef-perl
> >   libhtml-tree-perl libmailtools-perl libmime-perl libnet-perl
> >   libnet-ph-perl libnet-snpp-perl libpaperg libstdc++2.10-dev liburi-perl
> >   libwww-perl lm-sensors lm-sensors-source logrotate mailgraph mailx
> >   man-db mrtg mrtg-contrib mrtg-ping-probe mutt netbase portsentry
> >   postfix postfix-tls psfontmgr samba-common screen smbclient
> >   spamassassin squirrelmail ssh x-ttcidfont-conf xbase-clients xemacs21
> >   xemacs21-bin xemacs21-mule xemacs21-support xlibmesa3 xserver-common
> >   xserver-xfree86 
> > The following packages have been kept back
> >   initscripts libdb4.1 libsasl2 
> 
> Perhaps the packages it wants to remove have been compiled against one
> of the libraries that are being kept back.  Try:
> 
>   apt-get install initscripts libdb4.1 libsasl2
> 
> and then
> 
>   apt-get dist-upgrade
> 
> 

Thanks.  This (and a night worrying) was enough to figure out the
problem.  I have both stable and testing listed in my sources.  Stable
is higher priority.  The packages that have been kept back are not in
stable and depend on a newer version of libc6.  Removing the testing
source gets rid of the problem.  When sarge becomes stable, I will
have a similar problem, but migration should go smoothly.

Thanks,
  Jeffrey