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

From: Jeffrey L. Taylor (jeff_at_austinblues.dyndns.org)
Date: 01/10/05

  • Next message: Anthony Walters: "Re: Debian bastion host"
    Date: Mon, 10 Jan 2005 08:49:55 -0600
    To: debian-user@lists.debian.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

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Anthony Walters: "Re: Debian bastion host"

    Relevant Pages

    • Re: HAL not initialized
      ... packages is causing the problem), but now whenever I boot my system ... receiving the following error: ...
      (Ubuntu)
    • HAL not initialized
      ... packages is causing the problem), but now whenever I boot my system ... receiving the following error: ...
      (Ubuntu)
    • SH Core Dumps
      ... While I was rebuilding some of the packages, ... randomly core dump, which is causing many things not to ...
      (freebsd-questions)
    • Re: Xgl timeframe?
      ... installing your packages? ... Matthew Garrett | mjg59@xxxxxxxxxxxxx ...
      (Ubuntu)
    • Re: [opensuse] problem with some of the latest kde3 backports
      ... The first set of packages I did with the new networkstatus code had a broken ... Obsoletes which is causing some problems down the line, ...
      (SuSE)