Comment 9 for bug 1531070

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1531070] Re: package plymouth 0.8.8-0ubuntu17.1 failed to install/upgrade: trying to overwrite '/usr/share/apport/package-hooks/source_plymouth.py', which is also in package libplymouth2:amd64 0.8.8-0ubuntu17.1

On Wed, Jan 06, 2016 at 01:33:30PM -0000, LukeKendall wrote:
> I installed the .deb for gnome-inform7 from
> http://sourceforge.net/projects/gnome-inform7/ - although I can't see
> anything that says it is for a specific Debian/Ubuntu release. Could
> that have been produced (a year ago) for a Xenial release?

No, it could not have been. Furthermore, installing a package with dpkg
would not cause changes to your system config to cause it to pull from
xenial instead of trusty.

> Other than that, all I did was ask Synaptic to mark all installed
> packages that had updates available, and then to install them. I
> certainly didn't poke about in the guts and do anything weird.

> Here are the exact commands I used:

> # dpkg -i gnome-inform7_6L38-0ubuntu1_i386.deb
> # apt-get update
> # apt-get check
> # apt-get install empathy
> # apt-get install libqt5webkit5-qmlwebkitplugin
> # apt-get -f install
> # synaptic
> # apt-get install synaptic
> # apt-get -f install

This implies that at some point prior to this, you had updated the config to
pull from xenial but had not applied the upgrade to xenial.

> From what people have said here, it sounds like Xenial is a later
> release than Trusty, and somehow my Ubuntu 14.04 started installing
> packages from Xenial, is that it? Certainly, that was not my intention.

Yes, that's correct. Xenial /will be/ 16.04, but it has not been released
yet.

> Things seems to be largely okay (though Samba has begun segfaulting). I
> certainly didn't force any updates, AFAIK, and saw no warnings about
> anything I was doing as being not recommended, so I'm still a bit confused
> about
> a) Just what started the problem
> b) How dangerous a situation I'm in now, and
> c) What I should do to try to recover.

I don't know any reliable way to recover from this without a full reinstall
of Ubuntu 14.04.