problems upgrading from 14.04 to 16.04
Ralf Mardorf
silver.bullet at zoho.com
Wed Sep 28 09:37:50 UTC 2016
On Wed, 28 Sep 2016 05:10:22 -0400, Tom H wrote:
>There's a problem with libkolabxml1 but it no longer exists on
>16.04/16.10
We could repeat this again and again.
https://lists.ubuntu.com/archives/ubuntu-users/2016-September/287556.html
We already know which packages are the culprits. The OP upgraded from
an install, that was not an install build from official repositories
only. Now it requires some work to fix it.
On Tue, 27 Sep 2016 15:21:09 +0200, J.L. Blom wrote:
>Interestingly, your suggestion showed a lot of i386 packages a.o.
>mysql. I'll give the output here, which is quite lengthy.
>___________________________________________
>joep at laguna:~$ sudo apt purge --dry-run libkolabxml1 libstdc++6:i386
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>You might want to run 'apt-get -f install' to correct these:
>The following packages have unmet dependencies:
> acroread-bin:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is
> not
>going to be installed
> libgl1-mesa-dri:i386 : Depends: libstdc++6:i386 (>= 5.2) but it is
> not
>going to be installed
> libglu1-mesa:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is
> not
>going to be installed
> libicu55:i386 : Depends: libstdc++6:i386 (>= 5.2) but it is not
> going
>to be installed
> libjack-jackd2-0:i386 : Depends: libstdc++6:i386 (>= 5.2) but it is
>not going to be installed
> libllvm3.5:i386 : Depends: libstdc++6:i386 (>= 4.8) but it is not
>going to be installed
> libllvm3.8:i386 : Depends: libstdc++6:i386 (>= 5.2) but it is not
>going to be installed
> libmysqlclient20:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it
> is
>not going to be installed
> libosmesa6:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is not
>going to be installed
> libqt4-declarative:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it
>is not going to be installed
> libqt4-network:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is
>not going to be installed
> libqt4-script:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is
> not
>going to be installed
> libqt4-sql:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is not
>going to be installed
> libqt4-sql-mysql:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it
> is
>not going to be installed
> libqt4-xml:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is not
>going to be installed
> libqt4-xmlpatterns:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it
>is not going to be installed
> libqtcore4:i386 : Depends: libstdc++6:i386 (>= 5.2) but it is not
>going to be installed
> libqtdbus4:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is not
>going to be installed
> libqtgui4:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is not
>going to be installed
> libstdc++6 : Depends: gcc-5-base (= 5.4.0-6ubuntu1~16.04.2) but
>5.4.1-2ubuntu1~14.04 is to be installed
> libtxc-dxtn-s2tc0:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it
> is
>not going to be installed
> qt-at-spi:i386 : Depends: libstdc++6:i386 (>= 4.1.1) but it is not
>going to be installed
> ubuntu-emulator-runtime:i386 : Depends: libstdc++6:i386 (>= 4.6) but
>it is not going to be installed
>E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
>specify a solution).
>__________________________________________________________
>What I don't understand is why "apt-get -f install" isn't working or
>is there an conflicting situation even deeper in the chain of events.
You used non-official repositories and caused a situation that requires
interaction, --fix-broken can't do magic.
"-f, --fix-broken
Fix; attempt to correct a system with broken dependencies in place.
This option, when used with install/remove, can omit any packages
to permit APT to deduce a likely solution. If packages are
specified, these have to completely correct the problem. The option
is sometimes necessary when running APT for the first time; APT
itself does not allow broken package dependencies to exist on a
system. It is possible that a system's dependency structure can be
so corrupt as to require manual intervention (which usually means
using dpkg --remove to eliminate some of the offending packages).
Use of this option together with -m may produce an error in some
situations. Configuration Item: APT::Get::Fix-Broken." -
http://manpages.ubuntu.com/manpages/xenial/en/man8/apt-get.8.html
You can't expect the Ubuntu user-friendliness, if you tailor your
install by leaving the Ubuntu approach. If you go an expert approach,
you are on your own. Actually you could backup your install and start
fixing it manually. Yes, it will be hard work. If something should go
wrong, restore the install and restart the hard work.
If you are using official repositories only _and_ official releases
only, IOW if you neither use non-official repositories nor a
development release, you won't run in such an issue. You are using
official releases, but non-official repositories. Now you need to
remove packages that aren't of vital significance, that do cause the
unsolvable dependency hell.
Regards,
Ralf
More information about the ubuntu-users
mailing list