Upgrading to 14.04 gives problems II

[Colin Law]

On 22 September 2014 11:00, J.L. Blom <joep at neuroweave.nl> wrote:
> On 22/09/14 08:23, Colin Law wrote:
>>
>> I guess that will have come from one of the ppas you had on precise, and
>> because it is later than the trusty one it has not been replaced. I don't
>> fully understand why it is a problem as it is later than the one that the
>> other packages depend on so I would have thought they would be happy with
>> it. However I am sure the thing to do is return it to the standard version.
>> Try this as a dry run first using sudo apt-get install -s
>> liblcms2-2=2.5-0ubuntu4 and make sure it is not going to cause havoc. It may
>> well say it has to remove some stuff so make sure it doesn't look as if it
>> is going to remove anything that might cause problems. If it is just
>> packages like openjdk for example you can put them back if you need them.
>> Assuming it looks ok then run it without -s. If that goes ok then start
>> again at the top by installing wine, and if it still won't go in then work
>> down the chain (which may not be quite the same as before) till you find the
>> offending package. As a matter of interest, did you have a libreoffice ppa
>> enabled? That package may have come from that. Colin
>
>
> Colin,
> Well, Problem solved!!
> That was the culprit, as simple as that. And as I already suspected a
> situation apparently missed by the developers and very much understandable.
> It is an error that apparently is introduced during upgrading where
> liblcms2-2 was nor upgraded to the trusty version as the trusty version was
> older than the precise version.
> So when an error saying ¨broken packages¨ occurs, and checking for broken
> packages gives no broken packages present, it is maybe an idea to check for
> consistency in package version as the parser -or linker - checks for package
> consistency and will not link libraries from different versions as
> apparently distribution version has priority over program- or library
> version.
> Colin and Gary again thanks a lot for the support, which moreover was also a
> learning experience,

As I said it is likely the package came from a ppa or a manual install
not from the ubuntu repository.  The sytem upgrade could not downgrade
the package as it did not know the reason it was there. You are right
though about apt-get, it could certainly have provided more helpful
error messages.

If it did come from a ppa then the moral is to always use ppa-purge to
get rid of ppas before upgrading.  It would be helpful if the upgrade
process could suggest this (or even do it for you after asking).
There is a page on the wiki that I follow when upgrading [1] (it leads
you through uninstalling any non-standard packages before the
upgrade), though even it does not specifically using ppa-purge.  Again
possibly it would be good if the upgrade process pointed one at that
before proceeding.  By following that I do not believe I have ever had
a problem upgrading.

I still don't understand messages I posted in my last message,
hopefully someone will elucidate.

Glad to be of help.  I enjoy the challenge if truth be told.

Colin.

[1] https://help.ubuntu.com/community/CleanUpgrade