DevHeads.net

Postings by Matthias Klose

Second Disco Dingo test rebuild

The second test rebuild of Disco Dingo was started on April 04 2019 for
all architectures, just the main component.

Disco Dingo test rebuilds

The first test rebuild of Disco Dingo was started on December 21 2018 for
all architectures, all components.

Cosmic Cuttlefish test rebuilds

The first test rebuild of Cosmic Cuttlefish was started on September 11 2018 for
all architectures, all components (main component and seeded packages finished,
unseeded packages still building).

xenial (16.04 LTS) and bionic (18.04 LTS) test rebuilds

There are four test rebuilds done for xenial and bionic (main only), both the
release and the updates pockets. The results of both builds are combined in one
table. Please see

<a href="http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180727-main-xenial.html" title="http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180727-main-xenial.html">http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180727-mai...</a>

<a href="http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-bionic.html" title="http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-bionic.html">http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-bio...</a>

The table also has some new color codes to mark packages which always failed to
build, and for packages which failed to build in a reference release.

Cosmic Cuttlefish is now open for development

Cosmic CANIMAL [1] is now open for development, with the syncs from unstable
done and built. The development version starts with only a few changes:

- The final GCC 8.1.0 release (not yet used as the default)

- Only one transition almost done (ncurses)

Please be aware about the planned compiler changes (GCC update from 7 to 8)
around June/July, an update to OpenJDK 11, and an update from Python 3.6 to 3.7.

Please check your uploads in a cosmic chroot, don't just test in a bionic or
artful environment. See [2] or [3] how to setup such a development chroot.

Second Bionic Beaver test rebuilds

The second test rebuild of Bionic Beaver was started on April 08 2018 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building).

1000 New Year's pledges for 2018 (first Bionic Beaver test rebuilds)

The first test rebuild of Bionic Beaver was started on December 21 2017 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building). The number of build time failures
unfortunately is at an all time high around a four digit number.

Bionic Beaver now open for development

Before heading on with Bionic Beaver, let's have a look at all the remaining
build failures in Artful Aardvark [1], which is the highest number of build
failures at the end of a release cycle we ever had. Please don't repeat that
and plan to address these build failures in time for the Bionic Beaver release
(at least for all the packages in main and in seeds).

Bionic Beaver [2] is now open for development.

Second Ubuntu Artful Aardvark test rebuild

The second test rebuild of Artful Aardvark was started on September 22 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building).

For arm64 and armhf the gcc-6 and gcc-7 packages are based on the Linaro
6-2017.09 snapshots.

Results (please also look at the superseded builds) can be found at

<a href="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html" title="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html">http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html</a>

The test rebuild uses the release pocket only, without packages from the
proposed pocket.

Additional build failures for packages in artful-proposed (not yet in artful)

GCC 7 default update planned for early August

Hi,

it's this time of the year where you go to your vacation, and look at a new
shiny new GCC version in the archive when you come back. Well, not exactly ...

I'm planning to change the default on Aug 03/04, and then working to get things
migrated and buildable again, including two transitions for GCC runtime
libraries. Fixing things pro-actively is appreciated. If there are questions,
please use the #ubuntu-devel irc channel.

First Ubuntu Artful Aardvark test rebuilds (and upcoming GCC 7 transition)

The first test rebuild of Artful Aardvark was started on July 6 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building).

For arm64 and armhf the gcc-6 packages are based on the Linaro 6-2017.06
snapshot.

Results (please also look at the superseded builds) can be found at

<a href="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-artful.html" title="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-artful.html">http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-artful.html</a>

The test rebuild uses binutils, gcc-6, gcc-7 and linux packages currently still
in the proposed release pocket, which can also be found separately in the PPA

<a href="https://launchpad.net/~ub" title="https://launchpad.net/~ub">https://launchpad.net/~ub</a>

Second Ubuntu Zesty Zapus test rebuilds (all components, all architectures, GCC 7)

The second test rebuild of Zesty Zapus was started on March 22 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building).

For arm64 and armhf the gcc-6 packages are based on the Linaro 6-2017.03
snapshot.

Results (please also look at the superseded builds) can be found at

<a href="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html" title="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html">http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html</a>

Additional build failures for packages in zesty-proposed (not yet in zesty)
can be found at <a href="http://qa.ubuntuwire.com/ftbfs/" title="http://qa.ubuntuwire.com/ftbfs/">http://qa.ubuntuwire.com/ftbfs/</a>

Please help fixing the build failures.

Another test rebuild u

First Ubuntu Zesty Zapus test rebuilds (all components, all architectures, GCC 7)

The first test rebuild of Zesty Zapus was started on December 02 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building).

For arm64 and armhf the gcc-6 packages are based on the Linaro 6-2016.10
snapshot.

Results (please also look at the superseded builds) can be found at

<a href="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-zesty.html" title="http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-zesty.html">http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-zesty.html</a>

Additional build failures for packages in zesty-proposed (not yet in zesty)
can be found at <a href="http://qa.ubuntuwire.com/ftbfs/" title="http://qa.ubuntuwire.com/ftbfs/">http://qa.ubuntuwire.com/ftbfs/</a>

Please help fixing the build failures.

Another test rebuild u

Zesty Zapus open for development

Zesty Zapus [1] is now open for development, with syncs from unstable
still running. The development version already starts with some
changes:

- GCC on armhf and arm64 now is built again from the GCC Linaro branch.

- Starting with library transitions: openmpi, boost 1.62.

Please check your uploads in a zesty chroot, don't just test in a xenial or
yakkety environment. See [2] or [3] how to setup such a development chroot.

Second Ubuntu Yakkety Yak test rebuilds (all components, all architectures, Linaro-GCC)

The second test rebuild of Yakkety Yak was started on September 16 for all
architectures, all components (main component and seeded packages mostly
finished, unseeded packages still building).

Results (please also look at the superseded builds) can be found at

<a href="http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html" title="http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html">http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html</a>

Additional build failures for packages in yakkety-proposed (not yet in yakkety)
can be found at <a href="http://qa.ubuntuwire.com/ftbfs/" title="http://qa.ubuntuwire.com/ftbfs/">http://qa.ubuntuwire.com/ftbfs/</a>

Please help fixing the build failures.

Another test rebuild using the Linaro-GCC 6 as the default (planning the
defaults change around th

First Ubuntu Yakkety Yak test rebuilds (all components, all architectures, GCC 6)

The first test rebuild of Yakkety Yak was started on July 01 for all
architectures, all components (main component and seeded packages finished,
unseeded packages still building).

Results (please also look at the superseded builds) can be found at

<a href="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160701-yakkety.html" title="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160701-yakkety.html">http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201...</a>

Another test rebuild using GCC 6 as the default (planning the defaults change
around the end of July) can be found at

<a href="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160705-gcc6-yakkety.html" title="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160705-gcc6-yakkety.html">http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201...</a>

Please start fixing build failures with GC

GCC/binutils and Python 2/3 updates for xenial

In the past weeks I've prepared updates for 16.04 LTS, updating gcc-5, binutils,
python2.7 and python3.5 to the last upstream point releases. The archive was
rebuilt using these versions, and an analysis of the test rebuild can be found
at LP: #1586673 (SRU for binutils and gcc-5).

binutils is already available in xenial-proposed, the other packages can be
found in the PPA ubuntu-toolchain-r/ppa.

OpenGL to OpenGL ES change on arm64?

built with OpenGL ES. Do we really have to cripple an architecture like this?
I don't see any discussion about this. How does this affect things like GPU
accelerators and CUDA aware packages?

Matthias

Yakkety Yak is now open for development

Yakkety Yak [1] is now open for development, with syncs from unstable
still running. The development version already starts with some
changes:

- GCC is configured to build with -fPIE (and to pass -z now to ld)
by default on amd64 and ppc64el.

- Three library transitions are almost done: boost 1.60, ICU 57,
and libpng 1.6.

- A bunch of library transitions is already triggered by the sync
from Debian.

oracle-java8-installer again inflates the priorities for the alternatives

Hi,

The oracle-java8-installer package in the webupd8team PPA again inflates the
priorities for the alternatives, as in looking for the highest available
alternative, then adding one to it and using that as the new alternative value.
This is not how it should be, and even wrong when you install multiple
oracle-java*-installer packages. You seem to have an oracle-java8-set-default
package which explicitly should do that, don't mess around with the priorities
for the alternatives. Pretty please fix this in a way that you don't just
inflate the priority of the alternatives.

Third Ubuntu Xenial Xerus test rebuilds (all components, all architectures)

The third test rebuild of Xenial Xerus was started on April 01 (no joke) for all
architectures, all components (it is finished besides some pending builds for
powerpc and armhf). Compared to the last test rebuild this sees some new build
failures introduced by new upstream versions during the feature freeze (e.g.

Second Ubuntu Xenial Xerus test rebuilds (all components, all architectures)

The second test rebuild of Xenial Xerus was started in late February for all
architectures, all components (it is finished besides some pending builds for
powerpc and armhf).

Results (please also look at the superseded builds) can be found at

<a href="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160226-xenial.html" title="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160226-xenial.html">http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201...</a>

For arm64 and armhf the gcc-5 packages are based on the Linaro 5-2016.02
snapshot.

Additional build failures for packages in xenial-proposed (not yet in xenial)
can be found at <a href="http://qa.ubuntuwire.com/ftbfs/" title="http://qa.ubuntuwire.com/ftbfs/">http://qa.ubuntuwire.com/ftbfs/</a>

Please help fixing the build failures.

Matthias

First Ubuntu Xenial Xerus test rebuilds (all components, all architectures)

A first test rebuild of Xenial Xerus was started last year for all
architectures, all components.

Results (please also look at the superseded builds) can be found at

<a href="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151218.1-xenial-baseline-xenial.html" title="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151218.1-xenial-baseline-xenial.html">http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201...</a>

For arm64 and armhf the gcc-5 packages are based on the Linaro 5-2015.12
release.

Additional build failures for packages in xenial-proposed (not yet in xenial)
can be found at <a href="http://qa.ubuntuwire.com/ftbfs/" title="http://qa.ubuntuwire.com/ftbfs/">http://qa.ubuntuwire.com/ftbfs/</a>

Please help fixing the build failures.

Matthias

PS: A second test rebuild (using a GCC 5 defaulting to -fPIE

Xenial Xerus is now open for development

Xenial Xerus [1] is now open for development, with syncs from unstable
still running. The development version already starts with some
changes:

- Python 3.5 already is the default Python3 version. Aiming for a
Python2 free desktop for the Xenial release.

- Binutils is built from the trunk, targeting the 2.26 branch.

- The launchpad build farm [2] saw some changes.

moving libraries to multiarch locations and adding the M-A: same attribute

Hi,

I initially started looking at cross-building openjdk-8 and openjdk-9, seeing
that I need get a large number of gnome library packages ready for multiarch.
I'd like to start with this at the beginning of the x-series, preparing the
patches in Ubuntu, and then forwarding these to Debian.

I then looked what libraries are left in /usr/lib on a typical desktop
installation, and found some more. Attaching the list of source packages which
build such library packages.

First Wily Werewolf test rebuild

A first test rebuild of Wily Werewolf was started on Oct 01 for all
architectures. It is finished for the main component on i386 and amd64.

Results can be found at
<a href="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html" title="http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html">http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-201...</a>

The archive for the test rebuild is
<a href="https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/" title="https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/">https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/</a>

Additional build failures for packages in wily-proposed (not yet in wily)
can be found at <a href="http://qa.ubuntuwire.com/ftbfs/" title="http://qa.ubuntuwire.com/ftbfs/">http://qa.ubuntuwire.com/ftbfs/</a>

Please help fixing the build failures.

Matthias

GCC 5 now the default in wily (release pocket)

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.

pretty please can we kill the png optimizer?

Hi,

we don't ship cd images anymore, we are not limited to CD sizes, and as long as
we don't hit some 2GB limit, we shouldn't optimize for size. This "optimizer"
adds for some packages 100% build time, in rare occasions up to 2000%. This is
not worth the savings. If we want to optimize for size, this should be done by
test rebuilds and individual patches, not consuming scare buildd resources.

thanks, Matthias

preparing to copy packages built with GCC 5 to wily-proposed. please hold back uploads for some hours

Hi,

we're trying to migrate packages from

<a href="https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-039" title="https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-039">https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-039</a>

into wily-proposed today. Please avoid uploads / integrations of packages which
are found in this PPA, and which don't fix any build failures in this PPA. Also
hold back with new upstream versions of unrelated or semi related packages.

thanks, Matthias

GCC 5 for 14.10 (wily) on July 31

Hi,

We are currently preparing the switch to GCC 5 as the default compiler for 14.10
(wily). Unlike earlier updates to newer compiler versions, which only required
updating packages to newer language standards, this time we have a partial ABI
transition in the standard C++ library (libstdc++6).