On Sun, Dec 30, 2007 at 17:28:48 -0500, charlie derr wrote:
> It's been a while, but I just attempted a massive upgrade (executing
> "aptitude upgrade") and ended up with:
>
>
> Setting up debhelper (5.0.63) ...
> Errors were encountered while processing:
[...]
> So I fiddled a bit without success.
>
>
> Unpacking replacement desktop-base ...
> gconftool-2: symbol lookup error: /usr/lib/libxml2.so.2: undefined symbol:
> gzopen64
> dpkg: warning - old post-removal script returned error exit status 127
> dpkg - trying script from the new package instead ...
> gconftool-2: symbol lookup error: /usr/lib/libxml2.so.2: undefined symbol:
> gzopen64
> dpkg: error processing /var/cache/apt/archives/desktop-base_4.0.4_all.deb
> (--unpack):
> subprocess new post-removal script returned error exit status 127
> gconftool-2: symbol lookup error: /usr/lib/libxml2.so.2: undefined symbol:
> gzopen64
> dpkg: error while cleaning up:
> subprocess post-removal script returned error exit status 127
[...]
> The above is in response to apt-get -f install (what used to work in
> the past for fixing issues, maybe that's my mistake?)
It is better to use "aptitude install -f" if aptitude is your package
manager of choice.
Anyway, it seems that you have a problem running update-gconf-defaults,
which is called in many installation scripts, the ones of desktop-base
among them. This might be caused by an issue with the libxml2 package or
it could be the symptom of a more general problem with python on your
system.
Let's see, which output do you get from these two commands:
dpkg -l libxml2 gconf2 | awk '/^[^D|+]/{print $1,$2,$3}'
/usr/bin/python -V
> If I try to upgrade one of those packages individually with aptitude
> install shared-mime-info then the below happens:
>
> The following packages will be upgraded:
> gnome-session libgnome2-common libgnomevfs2-common shared-mime-info
> 4 packages upgraded, 0 newly installed, 0 to remove and 795 not upgraded.
> Need to get 0B/2706kB of archives. After unpacking 1461kB will be used.
> Do you want to continue? [Y/n/?] y
> Writing extended state information... Error!
> E: I wasn't able to locate file for the desktop-base package. This might mean
> you need to manually fix this package.
> E: Couldn't lock list directory..are you root?
You used apt-get to break the desktop-base package behind aptitude's
back and that seems to have confused aptitude. I would hope that this
problem goes away once you have fixed the desktop-base package.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
