Friday, 14 August 2015

Re: GCC 5 now the default in wily (release pocket)

As of today, none of our CI jobs are building any longer.

It looks like gcc 5 is now the default in Jenkins, but the libraries that are installed are still compiled with 4.9.
So, for example, we fail to link against leveldb because leveldb still has the old ABI string symbols in it.
The boost -dev packages also appear to still be at 1.55 with the old ABI. I expect that more things will
will be affected. For example, Qt5, with methods such as QString::fromStdString().

Is anyone looking at this?

Thanks,

Michi.


On 13 Aug 2015, at 0:01 , Matthias Klose <[email protected]> wrote:

> GCC 5 is now the default in the wily release pocket, together with some
> libraries, which were either forced (icu, boost1.58), or migrated on their own.
> The majority of the packages in -proposed are still blocked by missing rebuilds
> or packages failing to build.
>
> The packages which already are migrated to the release pocket should be
> installable and not break any installation, however using the release pocket for
> development which touches any of the not yet migrated packages won't work. For
> this case you should have a development chroot with both the "release" and the
> "proposed" pocket enabled.
>
> We do *not* recommend updating your default environment to wily-proposed. If you
> want to help with testing one of the desktop environments, please do that in a
> VM or in a chroot. The Ubuntu desktop already seems to be upgradable. Updates
> of Kubuntu, Xubuntu and UbuntuStudio desktops are not yet tested. Feedback is
> welcome.
>
> To get this large transition finished, your help is welcome and needed.
>
> What you should *not* do:
>
> - Starting a major transition / update of some package or
> set of packages.
>
> - Merging or force syncing a package from Debian which had a library
> transition in Ubuntu but not in Debian. We'll see to these packages
> after the majority of the packages moved to wily.
>
> What you should do:
>
> - work on a transition mentioned at [1]. Pleases coordinate with
> release managers on IRC (#ubuntu-release).
>
> - Relevant FTBFS are tracked on [2]. Help with those is greatly
> appreciated to unblock library transitions.
>
> - With a lower priority, fixing build failures and dep-wait's
> mentioned at [2]. Check that page maybe not as often as your
> email, but do it on a regular basis. Unfortunately we had to
> start the GCC 5 changes with a rather long list of issues.
>
> Remember that this transition doesn't end at the main/universe border or at the
> set of packages included in our iso images, but involves the whole archive (like
> any other transition).
>
> Thanks, Matthias
>
> [1] http://people.canonical.com/~ubuntu-archive/transitions/
> [2] http://pad.ubuntu.com/gcc-5-transition
> [3] http://qa.ubuntuwire.com/ftbfs/
>
> --
> ubuntu-devel mailing list
> [email protected]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel


--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel