trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: December 2014

Re: [trinity-users] a real upgrade mess

From: "Timothy Pearson" <kb9vqf@...>
Date: Sat, 20 Dec 2014 19:44:11 -0600
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224

> upgrade on my notebook machine went relatively uneventfully, so i
> thought it safe to upgrade desktop machine. and boke everything to
> the extent that i do not have x on the desktop machine at all.
>
> am running ubuntu-12.04LTS
>
> from a terminal, having added the specified lines to my sources.list
> and commented out the old tde lines, i did:
>
> sudo apt-get update
> sudo aptutide upgrade
>
> due to server congestion i had to run the latter several times. it
> then specified a problem, to be solved by removal of libcal2b-trinity
> and libqt-perl.
>
> the installation blows up in a fashion too long to list here -- i'd
> have to type it in character by characer, and it includes "25 not
> fully installed or removed" when i went back at it with sudo apt-get
> dist-upgrade. that command blows up with:
>
> dpkg: error
> processing
> /var/cache/apt/archives/tdelibs-data-trinity_4%3a14.0.0-r1231-0ubuntu12.04.0+pr138_all.deb
> (--unpack):
> trying to
> overwrite
> '/opt/trinity/share/icons/crystalsvg/16x16/devices/cdrom_unmount_encrypt.png',
> which is also in package kdebase-kio-plugins-trinity
> 4:3.5.13.2-0ubuntu12.04.0+0
> dpkg-deb (subprocess): data was killed by signal (Broken pipe)
> dpkg-deb (subprocess): error: subprocess <decompress> returned error
> exit status 2
> Errors were encountered while
> processing:
> /var/cache/apt/archives/tdelibs-data-trinity_4%3a14.0.0-r1231-0ubuntu12.04.0+pr138_all.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> not real sure how to proceed. ideas?
>
> thanks.
> --
> dep

I'd try this:
dpkg -i --force-all
/var/cache/apt/archives/tdelibs-data-trinity_4%3a14.0.0-r1231-0ubuntu12.04.0+pr138_all.deb
dpkg --configure -a
apt-get dist-upgrade

The first command forces tdelibs to unpack over the old tdelibs, which
should solve your conflict problems.  I've run into this on a few machines
myself but it was always due to me upgrading from R14 preliminary to R14
final, not from 3.5.13.x to R14.

Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iFYEARELAAYFAlSWJesACgkQLaxZSoRZrGF2tADeKEUEG13WMLFNg0p7nyeyc2V+
TpOJgo1X+pxekQDcDF1RnPSZYPxApuoqWf7U1fuBT9omgNbHdv8n5A==
=3cO0
-----END PGP SIGNATURE-----