The Gutsy Gibbon archives are now accessible, and will be openend soonish for
normal upload and syncs from Debian.
The current gutsy archive already has some basic packages updated, including our
toolchain (binutils, GCC, glibc). Noteworthy changes are:
- The Java compatible environment in main
The Ubuntu Mobile project uses a new architecture lpia; the architecture
resembles i386, but uses different optimizations options in the compiler,
different configuration and build options for some packages. Because Ubuntu
Mobile uses only a subset of main, and almost nothing of universe, a large
Recently Openjdk6 was promoted to main; with today's upload of java-common,
OpenJDK6 is the default java runtime / development kit in main, on all
architectures.
- On amd64, i386, lpia and sparc, the Hotspot VM, including the JIT compiler
is used as the VM.
- On ia64, the Hotspot VM, using
The Ubuntu Java development team is pleased to announce completed
certification of OpenJDK 6 for Ubuntu 9.04, continuing Ubuntu's tradition of
integrating the latest and greatest open source technologies into a
high-quality, easy-to-use Linux distribution.
After signing the Sun TCK agreement
Another natty test rebuild for amd64, armel and i386 was started yesterday,
including all components. Packages in the main component will build first. The
test archives are:
https://launchpad.net/ubuntu/+archive/test-rebuild-20110329/
Oneiric is now open for development, with syncs from unstable starting shortly.
The development version starts with an updated GCC and binutils, some soname
changes (gmp, libffi, boost) and re-enables the default linker settings, which
were disabled just before the natty release.
When
On 08/19/2011 06:09 PM, Matthias Klose wrote:
A test rebuild for oneiric is currently running, an overview of the build
failures can be found at
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html
The test rebuild archive itself is found at
https
Another test rebuild for precise pangolin is currently running on amd64, armhf
and i386. The results will show up at [1]. Half of main is rebuilt, and the
universe packages will start to build around this weekend.
The rebuild is running on the distro buildds, so please be a bit conservative
Quantal is now open for development, with syncs from unstable starting shortly.
The development version starts with updated versions of GCC and OpenJDK, some
soname changes (boost, hdf5), and some changes with setting the build flags for
package builds. We are finally targeting Python3 as the
Raring is now open for development, with syncs from unstable currently running.
The development version starts with updated versions of eglibc and python3, and
some upload rearrangements.
- GCC 4.7 did see some updates from the upstream branches, and supports
x32 multilibs on amd64 and
A second test rebuild of raring ringtail was started yesterday for the amd64,
i386 and armhf architectures. Currently running, and with mostly idle buildds
over easter and the current freeze it will hopefully finish within ten days.
Results can be seen at
Saucy is now open for development, with syncs from unstable currently running.
The development version starts with updated versions of GCC and boost.
- GCC 4.8 is now the default compiler, introducing among other things
improved C++11 support, AddressSanitizer , a fast memory error detector,
The first test rebuild of saucy salamander was started yesterday for the amd64,
i386 and armhf architectures. Currently running, finished for main, universe
will finish within the next ten days (armhf a bit earlier).
Results can be seen at
Trusty is now open for development, with syncs from unstable currently running.
The development version starts with a new port and with minor updates to the
toolchain and some transitions.
- GCC 4.8 was updated to the GCC 4.8.2 release and the GCC Linaro
4.8-2013-10 release. Binutils is
The first test rebuild of Trusty Tahr was started last week for all
architectures (main component only). It is still running for arm64, all other
architectures did finish the test rebuild.
Results can be seen at
The second test rebuild of Trusty Tahr was started this week for the i386
architecture (all components). The rebuild of the main component is finished
and it is now rebuilding the universe.
Results can be seen at
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
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).
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
On 02.10.2015 17:12, Matthias Klose wrote:
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
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html
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
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151218.1-xenial-baseline-xenial.html
For arm64 and armhf
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
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:
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
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
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 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 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
Similar to the Python2 demotion analysis, there is one done for GTK2 by Jeremy
Bicha, at
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=gtk2-demotion
There are a few hard to fix issues, but please review the seeds if the input
helpers in the seeds can be updated to avoid the GTK2 usage.
Python upstream announced the EOL of Python2 for 2020
https://pythonclock.org/
Getting Python2 demoted has been an ongoing task for several Ubuntu releases,
now finally having a desktop CD image in Ubuntu 17.10 which ships without a
Python2 interpreter. The next step is to get Python2 demoted
Cosmic Cuttlefish [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
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
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. Time
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). The number of build time failures
unfortunately is still high.
For arm64 and armhf the gcc-7 packages are
Disco Dingo is now open for development, with the syncs from unstable
done and built. The development version starts with only a few changes:
- Python 3.7 is now the default Python3 version, and the only supported
Python3 version.
- Perl was updated to version 5.28
- Merged-usr is now
The first test rebuild of Disco Dingo was started on December 21 2018 for
all architectures, all components. The number of build time failures
unfortunately is again high, even higher than for the last Cosmic Cuttlefish
test rebuild.
Results (please also look at the superseded builds) can be
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). The number of build time failures
unfortunately is again high.
The test rebuild was done using the
updates for 18.04 LTS
as long as we provide them for the 16.04 LTS (xenial) release.
On behalf of the OpenJDK 11 transition team,
Matthias Klose
--
List of packages in -proposed:
activemq
afterburner.fx
android-framework-23
android-platform-art
android-platform-build
android-platform-dalvik
android
The second test rebuild of Disco Dingo was started on April 04 2019 for
all architectures, just the main component. For technical reasons we were not
able to start that rebuild earlier, and a rebuild for the universe component
wouldn't finish before the 19.04 release.
The usual comment about
The first test rebuild of Eoan Ermine was started on June 16 2019 for
all architectures, all components.
Results (please also look at the superseded builds) can be found at
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190614-eoan.html
The report uses some additional color
The second test rebuild of Eoan Ermine was started on September 06 2019 for
all architectures, all components. The rebuild of the main component is
finished, the other components (restricted, universe, multiverse) are still
building.
Unfortunately we see 1300+ build failures, and still
Focal Fossa is now open for development, with the syncs from unstable
done and built, and autopkg testers trying to catch up. The development version
starts with only a few changes:
- Python 3.8 is now added as a supported Python3 version, with the
goal to ship Python 3.8 as the only
The first test rebuild of Focal Fossa was started on December 20 2019 for
all architectures, all components. The rebuild is finished except for some
pending universe/multiverse builds on armhf and arm64.
A first glance at the test results shows some missing dependencies for i386
builds, and some
The second test rebuild of Focal Fossa was started on March 27 2020 for
all architectures, all components. The rebuild is finished for the main
component, still running for the universe/multiverse components.
Results (please also look at the superseded builds) can be found at
The second test rebuild of Groovy Gorilla was started on September 25 2020 for
all architectures, all components. The rebuild is finished for the
main component. It is still running for the universe/multiverse components.
Results (please also look at the superseded builds) can be found at
Hirsute Hippo is now open for development, with the uploads collected in the
queue now approved, and syncs from unstable enabled.
The development version starts with one change:
- Python 3.9 is now added as a supported Python3 version, with the
goal to ship Python 3.9 as the only Python3
The first test rebuild of Hirsute Hippo was started on December 20 2020 for
all architectures, all components. The rebuild is almost finished.
It is still running for the multiverse component on some architectures.
Thanks to everybody keeping the buildds going during the end-of-year break.
We’re pleased to announce that impish is now *open for development*.
auto-sync has been enabled and will run soon. As usual, we expect a
large influx of builds and autopkgtests in this initial period, which
will cause delays. Please help with fixing any breakage that occurs.
The release schedule
The second test rebuild of Hirsute Hippo was started on March 25 2021 for
all architectures, all components. The rebuild is finished for the main
component, it's still running for the other components.
Results (please also look at the superseded builds) can be found at
The first test rebuild of Impish Indri was started on August 05 2021 for
all architectures, all components. The rebuild is finished on amd64 and i386 for
all components, and finished for all architectures for the main component.
Still running for universe and multiverse for non-x86 architectures.
50 matches
Mail list logo