GCC 5 now the default in wily (release pocket)

[Matthias Klose]

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/

[Michi Henning]

Sorry, I don't follow.

This is on Jenkins. I have no choice as to what packages are used to build with there.

Am I missing something?

If boost can't be built for the new ABI, how is my gcc 5 compiled code going to link with boost?

Cheers,

Michi.

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().

this looks like you don't have -proposed enabled. And yes, this is expected.
boost can't be built for the new ABI, it will be removed for the wily release.
Matthias

[Steve Langasek]

Hi Michi,

Post by Michi Henning
Sorry, I don't follow.
This is on Jenkins. I have no choice as to what packages are used to build with there.
Am I missing something?

Why are these jobs building in jenkins, rather than in a ppa?

Who administers this jenkins, and why is the jenkins not set up to build
against -proposed?

I'm not sure why your jenkins build environment should have a policy that's
different from both the main archive and the CI Train silos. I think you
probably want to get this fixed.

Post by Michi Henning

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().

this looks like you don't have -proposed enabled. And yes, this is
expected. boost can't be built for the new ABI, it will be removed for
the wily release.

This refers specifically to boost 1.55, not "boost". boost in wily-proposed
is now at version 1.58 and is built for the g++5 ABI. However, this won't
make its way into wily until the phone stack is ready to migrate (along with
the various other packages that need to be migrated at the same time).