[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New woody upgrade problems



On Sat, Dec 16, 2000 at 09:18:57PM -0600, Dan Griswold wrote:
> Hey there Debianites,
> 
> Like a junkie unable to resist the fix, I did an apt-get upgrade
> today. Now I have problems getting the upgrade to complete. During the
> upgrade, I got this error:
> 
> Preparing to replace xlibs 4.0.1-10 (using .../xlibs_4.0.1-12_i386.deb) ...
> Unpacking replacement xlibs ...
> dpkg: error processing /var/cache/apt/archives/xlibs_4.0.1-12_i386.deb (--unpack):
>  trying to overwrite `/usr/X11R6/lib/X11/app-defaults', which is also in package xmcd
> dpkg-deb: subprocess paste killed by signal (Broken pipe)
> 
> Now when I run apt-get upgrade to try to finish things off, I get:

If you are upgrading distributions, you should use dist-upgrade which
handles dependencies better.  I always use dist-upgrade when tracking
the unstable branch.  The particulars in question involve the move of
"app-defaults" from /usr/X11R6/lib/X11 to /etc/X11/app-defaults ( as
*all* configuration files *should* exist under /etc according to FHS).

> You might want to run `apt-get -f install' to correct these.
> Sorry, but the following packages have unmet dependencies:
>   libxaw7: Depends: xlibs (>= 4.0.1-11) but 4.0.1-10 is installed
>   xvncviewer: Depends: xlibs (>= 4.0.1-11) but 4.0.1-10 is installed
> 
> I've tried each of these commands to no avail:
> 
> apt-get -f install
> apt-get -f install xlibs
> apt-get -f install libxaw7 xvncviewer
> apt-get -f remove xmcd
> 
> All of them give the last error I listed above (or cognates).
> 
> Any suggestions? (Besides "avoid woody" or "it's called 'unstable' for
> a reason" :-)

Well, xmcd seems to broken anyway (in woody), so a 'dpkg --purge xmcd'
will remove the cruft left behind by an 'apt-get remove' (i.e. the very
configuration files you are having problems with).  Also, many people
have noted that forcing an upgrade of debconf before other subsequent
upgrades may fix some other problems.

Unstable is usually pretty stable (with possibly a few broken/buggy
packages), but periodically has major instability (such as with perl or
libc6 version changes).  For instance, I was going to update packages
last night, but stopped when apt wanted to remove TeX.  Usually, these
things get sorted out in a few days...

-- 
Eric G. Miller <egm2@jps.net>



Reply to: