First Impish Indri test rebuild / GCC 11
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. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210805-impish-impish.html The rebuild was done with a few packages which are not yet in the impish release pocket. These are: - glibc 2.34 - linux (linux-libc-dev), only in the proposed pocket - golang-defaults pointing to golang-1.17 GCC 11 is now the default compiler; there are no bug reports filed in LP for build failures triggered by GCC 11, however there are reports in the Debian BTS. http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-11;users=debian-...@lists.debian.org Porting advice can be found at https://gcc.gnu.org/gcc-11/porting_to.html The additional packages used for the test rebuild are found in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile Additional build failures for packages in hirsute-proposed (not yet in hirsute) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Impish Indri is now open for development
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 can be found at https://discourse.ubuntu.com/t/impish-indri-release-schedule/18540 A major change this cycle will be the GCC defaults change to GCC 11 planned for July, introducing C++17 by default. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Second Hirsute Hippo test rebuild
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 https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210325-hirsute-hirsute.html Additional build failures for packages in hirsute-proposed (not yet in hirsute) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Happy Easter bug/egg hunt, Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
First Hirsute Hippo test rebuild (and GCC related test rebuilds)
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. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20201216-hirsute-hirsute.html Additional build failures for packages in hirsute-proposed (not yet in hirsute) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 11 can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20201216-hirsute-gcc11-hirsute.html Still running on arm64, armhf, ppc64el. That's in preparation for GCC 11 for the 21.10 release. GCC test packages can be found in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages Yet another test build turning on link time optimizations by default is at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20201216-hirsute-lto-hirsute.html This is only done for the 64bit architectures amd64, arm64, ppc64el and s390x. The optimizations are turned on by the dpkg package available in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/dpkg-lto/+packages Happy New Year and bug fixing, Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Hirsute Hippo is now open for development
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 version in hirsute. Please check your uploads in a hirsute chroot, don't just test in a focal or groovy environment. See [1] or [2] how to setup such a development chroot. Some major changes planned for this cycle are mentioned in the Hirsute release schedule [3]. -- [1] https://wiki.ubuntu.com/SimpleSbuild [2] https://wiki.ubuntu.com/DebootstrapChroot [3] https://discourse.ubuntu.com/t/hirsute-hippo-release-schedule/18539 -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Second Groovy Gorilla test rebuild
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 https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200925-groovy-groovy.html Some build failures on ppc64el and s390x are caused by a buildd issue, and will be retried soonish. Please ignore these where you see a ftbfs just on those architectures, but successes on the other architectures. Additional build failures for packages in groovy-proposed (not yet in groovy) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Second Focal Fossa test rebuild
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 https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200327-focal-focal.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to eoan. Additional build failures for packages in focal-proposed (not yet in focal) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild with GCC trunk enabled by default. Focal will ship with GCC 10 (as an optional compiler, not the default), and become the default GCC in 20.10. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200327-focal-gcc10-focal.html Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
First Focal Fossa test rebuild
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 missing dependencies for Python2 related packages. Please note that the test rebuild is done for the release pocket only. For the first time we have a test rebuild with such a vast amount of packages stuck in the proposed pocket. So besides fixing build failures, please also follow-up on getting packages migrated to the release pocket. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191220-focal-focal.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to eoan. Additional build failures for packages in focal-proposed (not yet in focal) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild with binutils and GCC trunk enabled by default. Focal will ship with binutils 2.34, and GCC 10 (as an optional compiler, not the default). https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191220-focal-gcc10-focal.html Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Focal Fossa is now open for development
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 Python3 version in focal. Details will follow on the ubuntu-devel ML. - Perl was updated to version 5.30. - s390x is now built targeting z13 (GCC only for now). - While the Python2 removals imported from Debian are just syncs like any others, it's worth pointing out that some uncoordinated removals are causing some churn [3], and on top of that there is a Ubuntu dept/delta which needs to see fixing as well [4]. Please check your uploads in a focal chroot, don't just test in a eoan or bionic environment. See [1] or [2] how to setup such a development chroot. -- [1] https://wiki.ubuntu.com/SimpleSbuild [2] https://wiki.ubuntu.com/DebootstrapChroot [3] https://lists.debian.org/debian-python/2019/10/msg00081.html [4] https://lists.ubuntu.com/archives/ubuntu-devel/2019-October/040833.html -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Second Eoan Ermine test rebuilds
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 counting ... On the other hand the test rebuild includes the recent GCC, glibc packages, and the glib2.o/gtk packages synced from experimental. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190906-eoan.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. The test rebuild already uses the linux-libc-dev 5.3 package found in the ubuntu-toolchain-r/volatile PPA. Additional build failures for packages in eoan-proposed (not yet in eoan) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild with link time optimization turned on by default (passing -flto=auto in CFLAGS/CXXFLAGS). Other distributions turned these optimzations on by default, or are considering doing that. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190906-lto-eoan.html Packages to use -flto by default (dpkg) can be found in the ubuntu-toolchain-r/dpkg-lto PPA. WARNNING: Make sure to install these dpkg packages in a throw-away environment. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
First Eoan Ermine test rebuilds
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 coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Additional build failures for packages in eoan-proposed (not yet in eoan) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild using GCC 9.1, which will become the default compiler for the 19.10 release. Results at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190614-gcc9-eoan.html Packages to set GCC 9 as the default GCC can be found in the ubuntu-toolchain-r/volatile PPA. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. 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 increasing build failures compared to the previous release cannot be proven this time, however a first look at the build failures in main suggests that disco uploads for the kernel, glibc, glib2.0 and vala were made without checking for the impact of build failures. Results (please also look at the superseded builds) can be found at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-disco-disco.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Bug reports for all build failures are filed. Additional build failures for packages in disco-proposed (not yet in disco) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Call for Testing: OpenJDK 11 packages in bionic-proposed and cosmic-proposed
Ubuntu 18.04 LTS shipped with OpenJDK 10 with the intent to update to OpenJDK 11, which unlike OpenJDK 10 is covered by LTS upstream security support that is more suitable for the lifetime of an Ubuntu LTS. Both OpenJDK 10 and 11 dropped some APIs, got stricter with the javadoc tools, and had some other incompatible build changes, which are mostly fixed now in our packages for the upcoming 19.04 release. Instead of backporting single patches for 250+ packages, we decided to backport the packages to 18.04 LTS and 18.10 where necessary. The backports are currently available in the bionic-proposed and cosmic-proposed pockets. We are planning to copy these packages to both the security and updates pockets in the last week of March. Please test these packages (see the end of the email for a list) and file new bug reports for any issue with these planned updates, subscribing the openjdk-11-transition team to the bug report. As an alternative, feel free to contact us on the #ubuntu-java IRC channel. WARNING: In order to resolve any issues found, we might need to remove some packages from -proposed or SRU them at a lower version number, so please don’t do the tests in your production environment; and be ready to downgrade packages if they are not propagated to the updates and security pockets. It is of particular importance to get more feedback on end-user applications, which may be affected in ways not identifiable in automated testing. These packages are free of all known regressions; but it’s possible there are unknown regressions, which is why we are asking for your help. Please check that your favorite applications continue to work. Some application packages that are known to be affected by OpenJDK API changes, and have had some manual testing but warrant additional testing are: jabref, jedit, jhove, libreoffice, mobile-atlas-creator, netbeans, tomcat8, tomcat9, sweethome3d, and virtualbox. The uploads themselves are tracked in the following bug reports: https://launchpad.net/bugs/1784196 https://launchpad.net/bugs/1814133 https://launchpad.net/bugs/1818647 https://launchpad.net/bugs/1819448 The updates include the OpenJDK 11 packages itself, and the packages found at https://bugs.launchpad.net/~openjdk-11-transition/+packagebugs OpenJDK 8 in 18.04 LTS (bionic) remains in the community-supported universe component. We will provide OpenJDK 8 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-platform-development android-platform-external-boringssl android-platform-external-libselinux android-platform-external-libunwind android-platform-frameworks-base android-platform-frameworks-data-binding android-platform-frameworks-native android-platform-libcore android-platform-libnativehelper android-platform-system-core android-platform-system-extras android-platform-system-tools-aidl android-platform-tools-apksig angular-maven-plugin annotation-indexer ant ant-contrib antlr4 apache-directory-server apktool asm aspectj aspectj-maven-plugin batik bindex bnd bridge-method-injector carrotsearch-hppc cava clojure clojure-maven-plugin clojure1.8 commons-httpclient dd-plist dummydroid ecj eclipse-debian-helper eclipse-jdt-core eclipse-jdt-debug eclipse-jdt-ui eclipse-platform-debug eclipse-platform-resources eclipse-platform-runtime eclipse-platform-team eclipse-platform-text eclipse-platform-ua eclipse-platform-ui eclipselink el-api elki enjarify equinox-bundles equinox-framework equinox-p2 f2fs-tools figtree fontawesomefx fonts-liberation2 gettext gluegen2 gmbal gmbal-commons gmbal-pfl gradle gradle-apt-plugin gradle-completion gradle-debian-helper groovy hikaricp hsqldb hsqldb1.8.0 insubstantial istack-commons jabref jackson-core jackson-databind jackson-dataformat-xml jackson-module-jaxb-annotations jarjar-maven-plugin java-common java3d javafxsvg javamail javatools jaxb jaxb-api jaxe jaxrpc-api jaxrs-api jaxws jaxws-api jboss-classfilewriter jboss-jdeparser2 jboss-modules jcommander jersey1 jetty9 jftp jhove jmdns jnr-posix jruby jruby-openssl jsp-api jtreg jts junit4 jws-api jxgrabkey jython libapache-poi-java libbtm-java libcommons-collections3-java libcommons-collections4-java libcommons-compress-java libcommons-lang3-java libeclipse-emf libequinox-osgi-java libgoogle-gson-java libgpars-groovy-java libhibernate-validator-java libjackson-json-java libjavaewah-java libjdo-api-java libjdom1-java libjgoodies-looks-java libjogl2-java libnb-javaparser-java libnb-platform18-java libnetx-java libpdfbox2-java libpicocontainer-java libquartz-java libreoffice libreoffice-l10n libsambox-java libscout libscram-java libsejda-java libsmali-java libspring-java libstax2-api-java libswingx-java libwoodstox-java libxml-security-java libxstream-java logback lucene-solr
Disco Dingo test rebuilds
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 found at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181220-disco.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Additional build failures for packages in disco-proposed (not yet in disco) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild using an early version of GCC 9, which will become the default compiler for the 19.10 release. Results at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181220-gcc9-disco.html Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Disco Dingo is now open for development
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 default in Disco for new installations only.
It means that /bin is a symlink to usr/bin, similarly /lib and /sbin.
Existing systems, upon upgrade, will not be reconfigured for
merged-usr. Care needs to be taken to ensure that both merged-usr and
split-usr systems are continued to be supported. For example apparmor
rules may need to be adjusted to use {,/usr}/bin/touch and similar.
Please use debootstrap from cosmic or later, until the pending SRUs
are approved.
- OpenSSL 1.0 removal. It is expected that OpenSSL 1.0 will be removed
from Disco release, with OpenSSL 1.1.1 LTS as the only provided
OpenSSL ABI.
Please check your uploads in a disco chroot, don't just test in a cosmic or
bionic environment. See [1 or [2] how to setup such a development chroot.
--
[2] https://wiki.ubuntu.com/SimpleSbuild
[3] https://wiki.ubuntu.com/DebootstrapChroot
--
ubuntu-devel-announce mailing list
ubuntu-devel-announce@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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). The number of build time failures unfortunately is again high. The test rebuild was done using the openjdk-11 packages from the openjdk-r/ppa PPA (cosmic still has OpenJDK-10, instead of the OpenJDK-11 packages used for the rebuild. Results (please also look at the superseded builds) can be found at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180911-cosmic.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Additional build failures for packages in bionic-proposed (not yet in bionic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Cosmic Cuttlefish is now open for development
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 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. -- [1] http://markshuttleworth.com/archives/1521 [2] https://wiki.ubuntu.com/SimpleSbuild [3] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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). The number of build time failures unfortunately is still high. For arm64 and armhf the gcc-7 packages are based on the Linaro 7-2018.03 snapshot. The test rebuild was done using the java-common packages from the bionic-proposed pocket, already pointing to OpenJDK 10 (packaged as openjkd-11). Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html Additional build failures for packages in bionic-proposed (not yet in bionic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 8 as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-gcc8-bionic.html The GCC 8 test rebuild uses the gcc-defaults packages from the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile We will make GCC 8 the default compiler for the 18.10 release, so please start looking at those build failures as well. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. Time for some New Year's pledges! For arm64 and armhf the gcc-7 packages are based on the Linaro 7-2017.11 snapshot. Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20171220-bionic.html Additional build failures for packages in bionic-proposed (not yet in bionic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 8 as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20171220-gcc8-bionic.html The GCC 8 test rebuild uses gcc-defaults and gcc-8 packages from the PPAs https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile It is NOT planned to make GCC 8 the default compiler for bionic beaver, but adding ti as a non-default compiler is still being evaluated. Yet another test rebuild using binutils trunk can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20171220-binutils-bionic.html The binutils test rebuild uses binutils from the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/binutils It is planned to upload binutils trunk to bionic in late January. Happy New Year, Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
GTK2 demotion
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. This is not a goal for the upcoming 18.04 LTS release, however it would be appreciated to address some of these issues for the LTS for easier maintenance. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Python2 demotion (moving from main to universe) in progress
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 to universe, before finally in the far future it can be removed entirely from the archive. To get this done, we need: - OpenStack package builds using Python3 - Removing or updating Python2 packages in the Ubuntu seeds. - Fixing remaining packages to use Python3 instead of Python2 - Make sure that no new Python2 packages enter main (now being a topic for the MIR process). Besides the OpenStack issues, you can find about 50 remaining issues at https://bugs.launchpad.net/ubuntu/+bugs?field.tag=py2-demotion There are now about 35 left, so please consider working on these, or commenting on solutions for some issue. It is unlikely that the demotion of Python2 will be possible for the 18.04 LTS release, but please work on the issues so that we are ready for the demotion once OpenStack is using Python3. Thanks, Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. The development version already starts with some changes: - dpkg, debhelper, apt merges. - library transitions: ICU, boost 1.65, libcdio Please check your uploads in a bionic chroot, don't just test in a xenial or artful environment. See [3] or [4] how to setup such a development chroot. Auto syncs will be enabled soonish. -- [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html [2] http://markshuttleworth.com/archives/1518 [3] https://wiki.ubuntu.com/SimpleSbuild [4] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html 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) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Information about transitioning to GCC 7 can be found at: * https://gcc.gnu.org/gcc-7/porting_to.html * https://wiki.debian.org/GCC7 * Please forward patches for GCC 7 build failures to the bug reports already filed in Debian (see the above wiki page for the bug list). Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-artful.html 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 https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa Additional build failures for packages in artful-proposed (not yet in artful) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 7 as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-gcc7-artful.html For arm64 and armhf the gcc-7 packages are based on the Linaro 7-2017.06 snapshot. The test rebuild uses gcc-defaults, binutils, gcc-6, gcc-7 and linux packages currently still in the proposed release pocket, which can also be found separately in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test We are planning the transition to GCC 7 for late July / August. Please help fixing the build issues using the update GCC. Information about transitioning to GCC 7 can be found at: * https://gcc.gnu.org/gcc-7/porting_to.html * https://wiki.debian.org/GCC7 * Please forward patches for GCC 7 build failures to the bug reports already filed in Debian (see the above wiki page for the bug list). Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html Additional build failures for packages in zesty-proposed (not yet in zesty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using a snapshot of GCC 7 (not yet released) as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-gcc7-zesty.html GCC 7 is not yet released and will not be used as the default compiler for the 17.04 release. GCC 7 packages can be found in the ubuntu-toolchain-r/test PPA. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-zesty.html Additional build failures for packages in zesty-proposed (not yet in zesty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using a snapshot of GCC 7 (not yet released) as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-gcc7-zesty.html GCC 7 is not yet released and will not be used as the default compiler for the 17.04 release. GCC 7 packages can be found in the ubuntu-toolchain-r/test PPA. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. -- [1] http://www.markshuttleworth.com/archives/1512 [2] https://wiki.ubuntu.com/SimpleSbuild [3] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html Additional build failures for packages in yakkety-proposed (not yet in yakkety) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using the Linaro-GCC 6 as the default (planning the defaults change around the end of October) can be found at http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-linaro-yakkety.html The corresponding compiler can be found in the ubuntu-toolchain-r/test PPA. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160701-yakkety.html Another test rebuild using GCC 6 as the default (planning the defaults change around the end of July) can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160705-gcc6-yakkety.html Please start fixing build failures with GCC 6 now. Porting help can be found at https://gcc.gnu.org/gcc-6/porting_to.html Additional build failures for packages in yakkety-proposed (not yet in yakkety) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. Please help finishing such transitions if you see them. - Please expect a change of the GCC compiler to the 6.2 release in June/July. Please don't procrastinate work targeted for Yakkety. We ended the Xenial development cycle with more outstanding build failures and more outstanding merges than previous release cycles. An upload doesn't end when you hit upload, but needs to build, and then migrate to the release pocket of the archive. Please follow-up on build failures and dep-waits [3] and pending migrations to the release pocket [4]. Sorry to say this again, but we didn't improve much Start working on merges ([5], [6]) now, don't wait until you need a feature freeze exception for your merge. Please check your uploads in a yakkety chroot, don't just test in a xenial environment. See [7] or [8] how to setup such a development chroot. -- [1] http://www.markshuttleworth.com/archives/1496 [2] [3] http://qa.ubuntuwire.com/ftbfs/ [4] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [5] https://merges.ubuntu.com/main.html [6] https://merges.ubuntu.com/universe.html [7] https://wiki.ubuntu.com/SimpleSbuild [8] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. glibc). Results (please also look at the superseded builds) can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160401-xenial.html For arm64 and armhf the gcc-5 packages are based on the Linaro 5-2016.03 snapshot. Additional build failures for packages in xenial-proposed (not yet in xenial) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160226-xenial.html 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 http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias PS: Another test rebuild (using a snapshot of GCC 6) is built in preparation of the move to GCC 6 in 16.10. This can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160226-gcc6-xenial.html The corresponding compiler packages are in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test/ ... just in case you want to make packages ready for GCC 6. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151218.1-xenial-baseline-xenial.html 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 http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias PS: A second test rebuild (using a GCC 5 defaulting to -fPIE -Wl-z,now) was done on amd64, ppc64el and s390x, in preparation to turn on these flags on these architectures. Found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151218.1-pie-z-now-xenial.html PS: A third test rebuild (using a snapshot of GCC 6) is built in preparation of the move to GCC 6 in 16.10. This can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151218.1-gcc6-xenial.html The corresponding compiler packages are in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test/ ... just in case you want to make packages ready for GCC 6. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. If you experience unexpected build failures without a log, please retry the build. If the build failure persists, ask on #ubuntu-devel, or file a bug report for the launchpad-buildd project [3]. - A glibc update will follow later during this cycle. - A bunch of library transitions is already triggered by the sync from Debian. Please help finishing such transitions if you see them. - We expect further updates to some language stacks (ruby, perl, golang, node.js, mono, openjdk, and more). Please don't procrastinate work targeted for Xenial. We ended the Wily development cycle with more outstanding build failures and more outstanding merges than previous release cycles. An upload doesn't end when you hit upload, but needs to build, and then migrate to the release pocket of the archive. Please follow-up on build failures and dep-waits [4] and pending migrations to the release pocket [5]. Start working on merges ([6], [7]) now, don't wait until you need a feature freeze exception for your merge. You'll see developers much more xenial than grumpy! Please check your uploads in a xenial chroot, don't just test in a wily environment. See [8] or [9] how to setup such a development chroot. -- [1] http://www.markshuttleworth.com/archives/1479 [2] https://launchpad.net/builders [3] https://bugs.launchpad.net/launchpad-buildd/+filebug [4] http://qa.ubuntuwire.com/ftbfs/ [5] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [6] https://merges.ubuntu.com/main.html [7] https://merges.ubuntu.com/universe.html [8] https://wiki.ubuntu.com/SimpleSbuild [9] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Re: First Wily Werewolf test rebuild
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 The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/ Additional build failures for packages in wily-proposed (not yet in wily) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. the test rebuilds now finished for the amd64, i386 and armhf architectures. Compared to previous releases we still have more build failures compared to previous releases, so pretty please have a look at these build failures and fix these. Relevant URLs are: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html http://qa.ubuntuwire.com/ftbfs/ please also have a look at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html when you uploaded a package you would expect to be in the release pocket but which is still is stuck in wily-proposed. Thanks, Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/ Additional build failures for packages in wily-proposed (not yet in wily) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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. 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-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
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). Basically we'll have to rebuild around 3500 source packages, and will have some hundred follow-up library transitions. The libstdc++6 transition is prepared in the PPA https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-016 To test other packages you need to use this PPA as a dependency for your PPA / your local chroot. It is not enough to use the GCC 5 packages in wily. We are preparing the transition in a PPA, because direct uploads would break things a bit too much. Of course we can't prepare some thousand packages in the PPA and keep track of them with the wily archive, so at some point (July 31), we'll copy this PPA to the distribution and will continue the transition from there. The PPA probably is not yet ready to be installed into your host system, not everything is yet rebuilt using the new compilers. Help from the Ubuntu desktop team would be appreciated. Same for the server and cloud teams. The technical details what you can expect from GCC 5 are described in the Debian Wiki (not different for Ubuntu) at https://wiki.debian.org/GCC5. Porting hints available at https://gcc.gnu.org/gcc-5/porting_to.html. The g++-5/libstdc++6 will trigger some followup transitions; these are currently only tracked for Debian unstable, and will sync/merge into Ubuntu. We are trying to avoid explicit transitions in Ubuntu because of the extra work, and because Ubuntu doesn't guarantee partial updates. Packages affected by the transition will have a dependency on libstdc++6 (>= 5.2), which won't migrate to the release pocket soon. We will keep these packages in the proposed pocket until we can validate that common installation like the Ubuntu desktop or the Kubuntu desktop won't break. This effectively means, that migrations to the release pocket won't happen for a week or two (of course except those not relying on libstdc++6). If you are a core developer you can upload directly to the landing-016 PPA. Please keep in mind that you are responsible to keep packages in this PPA up to date. Packages should have a higher version number than in wily-proposed. No-change uploads should have a version number of the form -~gcc5.N When in doubt, please ask on IRC (FreeNode, #ubuntu-devel). Non core developers should prepare packages in their own PPA, depending on the landing-16 PPA. The Kubuntu developers already did this with KDE, having eliminated all issues exposed by GCC 5 (see [1]). It would be good to prepare something similar for Lubuntu and Xubuntu. What still needs fixing? Build failures with GCC 5 can be seen with the last test rebuild using GCC 5 [2], comparing that with a regular test rebuild [3]. Build failures in the landing-016 PPA should be fixed. Packages with fixes in Debian should be merged / synced either now (unstable), or after GCC 5 becomes the default (those which are being prepared in Debian experimental). Build failures and component mismatches should be cleared during the following two weeks. Thanks for joining the ride, and have fun with this roller coaster transition (it's by far the biggest transition since the migration to Warty Warthog)! Matthias [1] https://lists.ubuntu.com/archives/kubuntu-devel/2015-July/009765.html [2] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150402-gcc5-vivid.html [3] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150402-vivid.html -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Ubuntu Vivid Vervet test rebuilds (all components, all architectures)
A test rebuild of Vivid Vervet was started this week for all architectures, and is finished for the main component. Results can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150202-vivid.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/ Additional build failures for packages in vivid-proposed (not yet in vivid) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias PS: A second test rebuild (using a snapshot of GCC 5) is currently running, in preparation of the move to GCC 5 in 15.10. This can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150202-gcc5-vivid.html https://launchpad.net/ubuntu/+archive/test-rebuild-20150202-gcc5/ The corresponding compiler packages are in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test/ ... just in case you want to make packages ready for GCC 5. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Ubuntu Utopic Unicorn test rebuild (main, all architectures)
A test rebuild of Utopic Unicorn was started this week for all architectures, and is finished for amd64, i386, armhf and ppc64el. The rebuild for arm64 and powerpc will finish this week. Results can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140914-utopic.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20140914 Additional build failures for packages in utopic-proposed (not yet in utopic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures for the final release. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Third Ubuntu Trusty test rebuild (all components, all architectures except powerpc)
The third test rebuild of Trusty Tahr was started this week for all architectures except powerpc (all components). Results will appear at (currently this link doesn't yet exist) http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140307-trusty.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20140307/ Additional build failures for packages in trusty-proposed (not yet in trusty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures for the final release. To prepare for the u-series, a second test rebuild using GCC 4.9 as the default is run in parallel in https://launchpad.net/ubuntu/+archive/test-rebuild-20140307-4.9/ The compiler used for this test rebuild can be found in the ubuntu-toolchain-r/test PPA. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Second Ubuntu Trusty test rebuild (all components, i386 architecture)
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140127-trusty.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20140127/ The test rebuild is done with a change which is not yet in the archive, changing the default Python3 to use the not yet released Python 3.4. These packages can be found in a ppa [1]. Please ask on IRC (#ubuntu-devel) if you are in doubt that a build failure is caused by the changed Python3 default. Additional build failures for packages in trusty-proposed (not yet in trusty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures for the final release. Matthias [1] https://launchpad.net/~ubuntu-toolchain-r/+archive/python3 -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
First Ubuntu Trusty test rebuild (main component, all architectures)
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140108-trusty.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20140108/ The test rebuild was done with a change which is not yet in the archive, changing the default Python3 to use the not yet released Python 3.4. These packages can be found in a ppa [1]. Please ask on IRC (#ubuntu-devel) if you are in doubt that a build failure is caused by the changed Python3 default. Additional build failures for packages in trusty-proposed (not yet in trusty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures for the final release. Planning the next test rebuild for amd64, i386 and armhf for all components for the next week. Matthias [1] https://launchpad.net/~ubuntu-toolchain-r/+archive/python3 -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Trusty Tahr open for development
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 built from the 2.24 release branch. - An glibc update will follow later during this cycle. - Perl was updated from v5.14 to to v5.18. - Berkeley DB was updated from v5.1 to v5.3. - boost was updated from v1.53 to v1.54. Please check your uploads in a trusty chroot, don't just test in a saucy environment. See [1] how to setup such a development chroot. Trusty is the first development version that sees the AArch64 (arm64) port from the start of the cycle. Buildd resources are still somewhat limited compared to the other architectures, so please ask first on #ubuntu-devel before giving back a build for this port (e.g. compiler complaining about an unreproducible ICE). [1] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
second ubuntu saucy test rebuild
The second test rebuild of saucy salamander was started on Tuesday for the amd64, i386 and armhf architectures. Currently running, finished for main (armhf only), universe will finish within the next ten days (armhf a bit earlier). Results can be seen at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130917-saucy.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20130917/ Additional build failures for packages in saucy-proposed (not yet in saucy) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures for the final release. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
first ubuntu saucy test rebuild
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130614-saucy.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20130614/ Some common build failures are: - underlinking: symbols used in linked object files, which formerly were resolved by linked libraries. The fix almost always is to add the library (mentioned in the error message) to the link command. - build failures exposed by GCC-4.8. See http://gcc.gnu.org/gcc-4.8/porting_to.html for some guidance. Please help fixing the build failures for the final release. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Saucy now open for development
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, and ThreadSanitizer, a tool do detect data races. Find the complete list of changes at [1]. Information on porting to GCC 4.8 from previous versions of GCC can be found in the porting guide [2]. The cross compilers for armhf, arm64 and powerpc default to 4.8 as well. - Glibc and binutils updates will follow later during this cycle. - boost was updated from v1.49 to v1.53. Please check your uploads in a saucy chroot, don't just test in a raring environment. See [3] how to setup such a development chroot. [1] http://gcc.gnu.org/gcc-4.8/changes.html [2] http://gcc.gnu.org/gcc-4.8/porting_to.html [3] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
second raring ringtail test rebuild
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 http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20130329-raring.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20130329/ Some common build failures are: - underlinking: symbols used in linked object files, which formerly were resolved by linked libraries. The fix almost always is to add the library (mentioned in the error message) to the link command. - Tcl/Tk migration to multiarch locations. For autoconf based packages it should be enough to adjust the configure arguments for the Tcl/Tk libraries. The location for the header files didn't change. - eglibc-2.17 changes: -Werror=unused-result used together with -Werror. - Some glib/gtk/dbus related build and test failures, however there is no common pattern yet. Please help fixing the build failures for the final release. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
raring ringtail test rebuild
A test rebuild of raring ringtail started in 2012 for the amd64, i386 and armhf architectures is now finished for all components on armhf. The amd64 and i386 rebuilds will hopefully finish in a few days. Results can be seen at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20121221-raring.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20121221/ Some common build failures are: - not finding pyconfig.h, installed into a multiarch include dir - eglibc-2.16 changes (puts). Please help fixing the build failures for the final release. Matthias PS: For those interested, a second test rebuild using a snapshot of GCC-4.8 is going on. Status at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20121221-4.8-raring.html -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Raring now open for development
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 i386. - eglibc is updated to 2.16.1 [1]. Known issues are + a new macro TIME_UTC which conflicts with a macro of the same name in boost. + exposing a warning for building without any optimization, but defining _FORTIFY_SOURCE (currently disabled in the Ubuntu package). A check for _FORTIFY_SOURCE using the preprocessor without optimization now doesn't show the fortify support anymore. - Python 3.3 [2] is now the default python3 version. Packages are now rebuilt to use the new python version. It's the plan to drop python3.2 support before the first raring beta release. - Toolchain source packages are now setup to support an aarch64 cross toolchain. - For Raring, all uploads will go to raring-proposed, and a modified instance of "britney" (the software that handles migration from Debian unstable to testing) will copy them to raring when they've been built everywhere and do not reduce the count of installable packages in the archive [3]. Please check your uploads in a raring chroot, don't just test in a quantal environment. See [4] how to setup such a development chroot. [1] http://sourceware.org/ml/libc-alpha/2012-06/msg00807.html [2] http://docs.python.org/3.3/whatsnew/3.3.html [3] https://lists.ubuntu.com/archives/ubuntu-devel/2012-October/036043.html [4] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
quantal quetzal test rebuild
This weekend a test rebuild of quantal quetzal did start for the amd64, i386 and armhf architectures. The test rebuild is now finished for the main and restricted components, and continues with the universe and multiverse components. Results can be seen at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120922-quantal.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20120922 Please help fixing the build failures for the final release. Note that an upload won't show up in the superseded sections, if it is uploaded to quantal-proposed, but didn't propagate yet to quantal. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Quantal open for development
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 only Python version on the ISO/installation images. - GCC 4.7 is now the default, introducing some build failures caused by unknown compiler options, and more C++ strictness. Hints how to fix packages can be found at [1]. Bug reports for packages are not yet filed directly in Launchpad, but can be found on the Debian BTS instead [2]. - OpenJDK 7 is now used as the default, replacing OpenJDK 6, introducing some build failures. The build status can be tracked at [3], open issues are tracked at [4]. - Removing build flags exported from dpkg-buildpackage for quantal will get us in sync with Debian. Implications and fixes are discussed on the ubuntu-devel ML [5]. - Python 3 is now again part of a minimal chroot on quantal, and will be the only Python version provided on the ISO/installation images for quantal. Packages which need updates and ports for Python 3 are tracked at [6] Please check your uploads in a quantal chroot, don't just test in a precise environment. See [7] how to setup such a development chroot. [1] http://gcc.gnu.org/gcc-4.7/porting_to.html [2] http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-4.7;users=debian-...@lists.debian.org [3] https://wiki.ubuntu.com/JavaTeam/Java7Default [4] https://bugs.launchpad.net/ubuntu/+bugs?search=Search&field.bug_reporter=james-page&field.tags_combinator=ALL&field.tag=java7-ftbfs+encoding [5] https://lists.ubuntu.com/archives/ubuntu-devel/2012-April/035149.html [6] https://wiki.ubuntu.com/Python/FoundationsQPythonVersions [7] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
third test rebuild of precise pangolin
Another (and probably the last) test rebuild for precise pangolin is currently running on amd64, armhf and i386 (finished for main, universe is still building). The results will show up at [1]. The rebuild is running on the distro buildds, so please be a bit conservative with uploading packages (e.g. really do a successful local build before upload). Please look at the build failures for the packages in the "superseded" section too. It's not guaranteed that these are really fixed. Matthias [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120328-precise.html -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
second test rebuild of precise pangolin
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 with uploading packages (e.g. really do a successful local build before upload). Common issues in build failures are: - default CFLAGS/CXXFLAGS include -Werror=format-security. Fixes are easy; don't stop fixing the first occurrence, but complete a local build. - Gnome pkgconfig files dropping -lm from Libs, and other packages not explicitly linking with -lm (resulting in symbols like "sqrt" and "pow" not found). - Some obsolete symbols in newer glib/gtk libraries. - Some kernel header issues. The rebuild is already using the eglibc-2.15 packages from the ubuntu-toolchain-r PPA, planned for an upload on Tue, Feb 07. The packages can be found at [2]. Matthias [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120201-precise.html [2] https://launchpad.net/~ubuntu-toolchain-r/+archive/glibc/ -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
first rebuild of precise pangolin, including armhf
This week, a kind of rebuild for precise pangolin in the disguise of the armhf bootstrap did end. The build did expose some ARM unspecific build failures; please use the information from the armhf build logs to address these build failures. Please use the ftbfs pages to gather more information: - http://qa.ubuntuwire.com/ftbfs/ (not yet showing armhf) This mostly shows failures introduced by syncs from Debian unstable (Debian didn't yet file bug reports after introducing the -Werror=format-security default). - http://qa.ubuntuwire.org/ftbfs/primary-precise-armhf.html Shows armhf and armel build failures. Look at build failures which appear on armhf but not armel. These are likely build failures for other architectures as well. There are some generic issues found in more than one package: - default CFLAGS/CXXFLAGS include -Werror=format-security. Fixes are easy; don't stop fixing the first occurrence, but complete a local build. - Gnome pkgconfig files dropping -lm from Libs, and other packages not explicitly linking with -lm (resulting in symbols like "sqrt" and "pow" not found). - libreadline-dev dropping build dependency on libncurses-dev, and libncurses introducing a new libtinfo library. ARM (hf) specific issues include - compilers not yet built on armhf (gnat, fpc, ocamlopt), or not yet having the correct defaults (clang). - packaging mentioning armel only, but not armhf; usually needs fixes in both the control and rules files. http://people.canonical.com/~adconrad/universe-armel-armhf_differences might help with these although it includes all the packages build depending on gnat and fpc. - hard float issues, needing porting work. known ones are libreoffice, ocamlopt and fpc, but there will be more ... The armhf precise archive is installable with debootstrap(1) in a chroot on any armel Ubuntu/Linaro release. Thanks to Adam Conrad for driving the bootstrap, to Loic Minier for fixing ARM issues on the fly, to the Losa's for keeping the build farm alive, and many others. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Precise open for development
Precise is now open for development, with syncs from testing starting shortly. The development version starts with an - an updated GCC (4.6.x, Linaro 2011-10) and binutils (2.22 branch), - gnat-4.6 as the default gnat, - python2.6 dropped from the list of supported python 2.x versions, - merged dpkg, debhelper and cdbs, - the swig version updated from 1.3 to 2.0, - jpeg8 as the default jpeg version. In preparation for the LTS, syncs will run from the Debian testing distribution. If you require a sync request from unstable, please file a sync request (or sync on your own). Please do avoid syncing libraries changing the soname from unstable or experimental. These may still show build failures in dependent packages, which are not yet fixed in Debian experimental or unstable. Wait until these can be synced/merged from testing. When merging or requesting a sync, please look at the list of known build failures ([1] and [2]); bugs (tagged `ftbfs') are filed for every packages which fails to build from source. Please close these with the merged uploads. Please check your uploads in a precise chroot, don't just test in an oneiric environment. See [3] how to setup such a development chroot. [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html [2] http://qa.ubuntuwire.com/ftbfs/ [3] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Re: oneiric test rebuild running, bugs for build failures filed, please be more patient with PPA builders
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://launchpad.net/ubuntu/+archive/test-rebuild-20110816 > > The rebuild of the main component is done, and bug reports are field (all > tagged > ftbfs), packages from other components are still rebuilding. The rebuild for amd64 is now done, the rebuild for i386 did reach "libv" Bug reports are filed for the failed builds, targeted to the 'oneiric' release, and tagged with the "ftbfs" tag. A rebuild for armel is ongoing (main from "a" to "libx" done). Overview at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110819-oneiric.html Test rebuild archive at https://launchpad.net/ubuntu/+archive/test-rebuild-20110819/ Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
oneiric test rebuild running, bugs for build failures filed, please be more patient with PPA builders
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://launchpad.net/ubuntu/+archive/test-rebuild-20110816 The rebuild of the main component is done, and bug reports are field (all tagged ftbfs), packages from other components are still rebuilding. If you are a PPA power user managing an daily-build archive or something similiar, please consider building packages only every 2nd or 3rd day for the next week until the test rebuild is done (or build not for every distro series). Bug reports for the universe component will be filed next week depending on the progress of the rebuild. Thanks for your cooperation Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Oneiric open for development
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 merging or requesting a sync, please look at the list of known build failures [1]; bugs (tagged `ftbfs') are filed for every packages which fails to build from source. Please close these with the merged uploads. Please check your uploads in an oneiric chroot, don't just test in a natty environment. See [2] how to setup such a development chroot. [1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110413-natty.html [2] https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Natty test rebuild for amd64, armel, i386 (all components)
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/ https://launchpad.net/ubuntu/+archive/test-rebuild-20110329-arm Build failures are tracked in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110329-natty.html http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110329-arm-natty.html The status pages are updated hourly. The rebuilds are expected to complete sometime next week for amd64 and i386. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Natty test rebuild for ix86 (all components)
Another natty test rebuild for ix86 was started yesterday, including all components. Packages in the main component will build last, because we already had a test rebuild for main two weeks ago. The test archive is https://launchpad.net/ubuntu/+archive/test-rebuild-20110125 Build failures are tracked in http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110125-natty.html The status page is updated hourly. The rebuild is expected to complete sometime next week. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
GCC-4.6 rebuild tests
[ Note that GCC-4.6 will not be used for natty / 11.04, but we consider using this version for the O-series / 11.10 ] A test rebuild of natty/main using the current GCC version from the trunk was finished last week. While only one internal compiler error was found, some more build failures were seen due to new warnings and more strict frontends. A list of build failure can be seen at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110111-gcc-natty.html If a package appears in the `superseded' section, it doesn't mean that the build failure with GCC-4.6 is fixed. Some comments and hints for fixes can be found at https://wiki.ubuntu.com/GCC4.6 Please extend the wiki page if appropriate. To work on the build failures, please use either the gcc-snapshot package from natty or the gcc-4.6 package from the ubuntu-toolchain-r/test PPA. A large number of build failures is seen for packages building with -Werror. The compiler packages above were changed to add a -Wno-error=unused-but-set-variable when -Werror is found. Despite this local change the these packages need to build without this local change. Matthias PS: Fixing build failures with GCC-4.5 in natty should still have priority ;) -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Re: changing the python default from 2.6 to 2.7
2.7 is now the default python version in natty. packages were rebuilt and should be upgradable (except a handful, like ethos and xen-3.3). "Upgradable" doesn't mean that everything already works with 2.7, so please report issues and tag these with `python27'. The next step will be to identify all the packages only depending on libpython2.6 or python2.6 (but not 2.7) and rebuild/upgrade these to python2.7. UPGRADE ISSUES: When upgrading from Ubuntu 10.10 (maverick), please make sure to upgrade to maverick-updates first, before upgrading to natty. If you are upgrading directly from maverick or from an earlier natty snapshot, and are stuck, please see comment #5 in bug #689306 [1]. Matthias [1] https://launchpad.net/bugs/689306 On 08.12.2010 01:05, Matthias Klose wrote: > Tomorrow, Wednesday December 8, we'll change the default Python version in > Natty from 2.6 to 2.7. > > This will be followed by a series of no-change uploads to rebuild packages > with Python 2.7. Some parts of the archive will be uninstallable or not > upgradeable for a few days; please wait with upgrades until the rebuilds are > done, and for the next two days, also avoid bug reports about upgrade > problems. > > If you find issues which are not temporary while the rebuilds are ongoing, > please report these in Launchpad, and tag them with `python27`. We expect to > resolve the majority of such issues this year, with the remaining issues > addressed by the end of January. > > If you want to help fix problems related to the Python 2.7 switch, please > submit merge proposals and requests by tagging issues with `python27'. > A ping to barry and doko on #ubuntu-devel is welcome. > > Another goal for the natty release is to make the installation and removal of > python packages more robust. This will result in some packaging changes. > Unless these changes are already made in Debian or coordinated with Debian, > please don't change the packaging. We'll followup later how we will address > these issues. > > Barry Warsaw > Matthias Klose > > -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
changing the python default from 2.6 to 2.7
Tomorrow, Wednesday December 8, we'll change the default Python version in Natty from 2.6 to 2.7. This will be followed by a series of no-change uploads to rebuild packages with Python 2.7. Some parts of the archive will be uninstallable or not upgradeable for a few days; please wait with upgrades until the rebuilds are done, and for the next two days, also avoid bug reports about upgrade problems. If you find issues which are not temporary while the rebuilds are ongoing, please report these in Launchpad, and tag them with `python27`. We expect to resolve the majority of such issues this year, with the remaining issues addressed by the end of January. If you want to help fix problems related to the Python 2.7 switch, please submit merge proposals and requests by tagging issues with `python27'. A ping to barry and doko on #ubuntu-devel is welcome. Another goal for the natty release is to make the installation and removal of python packages more robust. This will result in some packaging changes. Unless these changes are already made in Debian or coordinated with Debian, please don't change the packaging. We'll followup later how we will address these issues. Barry Warsaw Matthias Klose -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
gcc in natty now passes --as-needed by default to the linker
There is a second change to the linking in natty; as announced in [1], --no-add-needed/--no-copy-dt-needed-entries is passed by default, with the current gcc in natty, --as-needed is passed as well. Please see [2] for implications (runtime failures) and a list of packages which might be affected. To revert this change on a per package basis, pass --no-as-needed to the linker (-Wl,--no-as-needed in LDFLAGS). To add an explicit dependency on a library use --no-as-needed -lfoo --as-needed. Please tag bug reports with `as-needed' if you see runtime failures caused by this change (mostly unresolvable symbols referenced by plugins and ldopened objects). Matthias [1] https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-October/000772.html [2] http://wiki.debian.org/ToolChain/DSOLinking#Onlylinkwithneededlibraries -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Natty Narwhal open for development
Natty Narwhal is now open for development. If you haven't yet subscribed to the natty-changes ML, please do so at [1]. It's worth mentioning the update to GCC 4.5 and a change to the linking behaviour. - GCC 4.5 is more strict than earlier GCC versions, and may cause build problems in packages. The majority of packages should be fixed, a list of remaining problems can be found at [2]. Please fix the packages to build with GCC 4.5, don't fall back to GCC-4.4. - The linking behaviour was changed to not resolve symbols anymore in indirectly linked shared libraries. A binary directly using a symbol from a shared library has to link with this library. Details can be found at [3], an analysis of required changes (and some patches) for packages in main can be found at [4]. A list of open issues is found at [5]. While support for two community ports was dropped in maverick, please keep in mind that the builds for the armel and powerpc architectures are not available as fast as on amd64 and i386. Please either make sure to update build dependencies, if newer versions are needed, or only upload a package in a dependency chain when a required build dependency is published on all architectures (same thing when scheduling rebuilds for library transitions). Don't be nasty to natty ;) Matthias [1] https://lists.ubuntu.com/mailman/listinfo/natty-changes [2] http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-4.5;users=debian-...@lists.debian.org [3] http://wiki.debian.org/ToolChain/DSOLinking [4] https://wiki.ubuntu.com/RobSavoye/GoldFixes [5] http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=no-add-needed;users=peter.fritzs...@gmx.de -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Announcing OpenJDK 6 Certification for Ubuntu 9.04 (jaunty)
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 earlier this year, Java developers went to work with the certification process and received final certification from Sun in late May. This certification means that the OpenJDK 6 package included with Ubuntu 9.04 now passes the rigorous testing of the Java SE Test Compatibility Kit (TCK) and is compatible with the Java(TM) SE 6 platform on the amd64 (x86_64) and i386 (ix86) architectures. OpenJDK is a free and open source implementation of Sun's Java(TM) SE 6 platform. The Java TCK is a toolkit providing tools, tests, and documentation to help determine whether or not Java implementations meet compliance. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
upcoming python changes / upgrade issues
After the alpha-5 release we will update the python interpreter from 2.5.4 to 2.6.1. For about 24 hours you will no be able to cleanly update jaunty, until some packages are rebuilt with python2.6. For a better upgrade experience during this time, please add the pythoneers PPA to your sources.list, which already has the rebuilds available: deb http://ppa.launchpad.net/pythoneers/ppa/ubuntu jaunty main Don't forget to remove this line after the change is complete; I will notice u-d-a when the change is done for main. For universe you may experience installability issues somewhat longer. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Java related changes in intrepid
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 byte code interpreter is used. - On powerpc, the Cacao VM, including the Cacao JIT compiler is used as the VM. What will change for the packaging? - Use of the default-jre-headless, default-jre, default-jdk, default-jdk-builddep packages is preferred in favour of a specific runtime/jdk. The packages provide a symlink /usr/lib/jvm/default-java to point to our preferred choice of jvm/sdk. - build dependencies: If a source package builds a "-gcj" package, don't stop building it yet. This will slow down the gij runtime. Instead, use "default-jdk-builddep", which depends on the default jdk and java-gcj-compat-dev. If no "-gcj" package is built, use default-jdk as a build dependency. - dependencies: For a dependency, which doesn't require an UI, use default-jre-headless | java2-runtime-headless for all other dependencies, use default-jre | java2-runtime Replace java2- with java5- only if newer language features are required. For intrepid we strive to replace all direct references to java-gcj-compat-dev and java-gcj-compat with references to default-*. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
2007 Google Summer of Code in Ubuntu - project results
The 2007 Google Summer of Code is over, and most projects mentored by Ubuntu are successfully completed with the code finding the way into the forthcoming Ubuntu gutsy or harty releases. Congratulations to the successful students and many thanks to their mentors! See https://wiki.ubuntu.com/GoogleSoC2007/Results This year Ubuntu did start with 20 single projects, 13 projects were completed successfully (for two projects the mentors were not entirely happy with the results), two students did drop out of the project, because they did find a/another job for this time. All students who did pass the midterm evaluation did pass the final evaluation as well. In six of the seven unfinished projects the students were unknown to their mentors, as reasons for not continuing the project were given personal things and unforeseen time constraints (i.e. exams). To wrap up this SoC we'll have a short meeting on irc (freenode) in the #ubuntu-meeting channel on Oct 1, 17:00 UTC for students and mentors. Everybody else is welcome as well. -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
new architecture lpia
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 part of the archive is not yet built for this architecture. The buildds are currently building the archive, so you might get notice about build failures for your uploads. Build failures outside the Ubuntu Mobile project are handled with the same priority as for our community ports. "lpia" uses GCC-4.2 as the system compiler (instead of GCC-4.1 for the other architectures), so some packages which are not yet built may fail to build due to a stricter compiler. The majority of packages in main is already built; if you do want to do development in a "lpia" environment, create a "lpia" chroot. as root: debootstrap --arch lpia gutsy /srv/chroot/gutsy-lpia http://ports.ubuntu.com/ A tutorial how to setup and use a chroot can be found at https://wiki.ubuntu.com/DebootstrapChroot -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
IcedTea - a first step towards OpenJDK
IcedTea is a temporary fork of OpenJDK which allows building with a free toolchain and adding/replacing code which is not yet available under a free license. First deb Packages for amd64, i386 and lpia are available at deb http://people.ubuntu.com/~doko/ubuntu/ gutsy/ deb-src http://people.ubuntu.com/~doko/ubuntu/ gutsy/ These packages target developers only. Feedback about the following topics is appreciated (on ubuntu-devel-discuss or #ubuntu-java): - packaging and installation issues; the packaging is derived from the sun-javaX packages, so the packages do have the same "features" and bugs. - license issues; we currently cannot upload the packages, because some files still have non-free or no licenses. Unfortunately there doesn't exist yet a list of problematic files. - usability; do packages and applications build and run with the new jre and jdk (focus on main)? Please contact me if you do want to join the packaging and maintainance effort. Thanks for any input. Matthias -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Opening development for Gutsy Gibbon
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 (gij/gcj) was updated to provide Java 1.5 compatibility, allowing now packages in main, which require 1.5 compatibility and can be built using gcj. - We will drop support for g77 for the Gutsy release, demoting g77 to universe. This transition will require manual changes in all packages build-depending on g77. The g77 and gfortran libraries are incompatible, so we will need to rename all library packages linked against libg2c when building these packages with gfortran. To avoid differing naming we will coordinate this work with Debian. - A prerelease of GCC-4.2 will be available in the archive; we will make sure that packages in main can be built using this new version. Gutsy is now open in "frozen" mode to allow the upload / sync of basic and some infrastructure packages first, which should be available before the normal uploads start. Please follow the normal sync rules (file a bug and subscribe ubuntu-archive) and rules for upload in frozen periods (upload and notify archive admins on #ubuntu-devel). The archive will be open for normal operation around Thursday noon UTC (Mar 26). -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
Join the Google Summer of Code with Ubuntu
Hi all, Ubuntu is once again participating in the Google Summer of Code [1]. We would like to make as many projects as possible, available for students to work on. It is a great opportunity to expose new students to the wonderful world of Ubuntu, get some exciting projects off the ground and get good exposure for the projects, students and organisations alike. SoC 2007 starts early this year, so there are even better chances to get projects for the second Ubuntu release this year (around October 2007). What can you do to help? We need - Exciting project ideas - preferably with detailed specs. Ideas can be related to the following broad topics: * Ubuntu [2] * Edubuntu [3] * Kubuntu [4] * Accessability [5] - If you have a project idea, and would like it to be considered, please add a project headings with a brief description to our Ideas Page [6]. Selected projects will be tracked on Blueprint. If you are ready to create a detailed spec please add it to Blueprint [7]. We would encourage members of the community who have been thinking of a cool new feature or plan to seize the opportunity to get it into the idea pool, as it might just get selected and implemented. You can see a list of proposed projects at [8]. - Mentors - volunteers in the know who will answer any questions the selected students have, and help them to settle into the community for the duration of the SoC. You will also be responsible for providing feedback to Google, the Student and Canonical on the project progress, as well as evaluating the project at the end of the programme. For your time and trouble you will receive a cool limited edition t-shirt! If you would like to volunteer to be a mentor, please contact [9]. - Good capable eligible Students, to apply for the projects. If you are a registered student and are over 18 years of age, you can apply for one of the projects (applications open on the Summer of Code page starting March 14 2007). We would like to select students who are enthusiastic about our projects and are able to commit the time and energy required to make them successful. Please make your applications detailed and give us enough information to be able to make an intelligent selection. Please remember that being selected is a privilege and a great opportunity. The more you commit, the greater your chance of a fantastic reward at the end Additionally if it is really good your code might be included in Ubuntu! See [10] for the SoC FAQ. Additional informations about your project should be provided in the Ubuntu/Kubuntu wikis in the form of a specification. The full Summer of Code rules can be found in the student FAQ [11] [1] http://code.google.com/soc/ [2] http://ubuntu.com/ [3] http://edubuntu.com/ [4] http://kubuntu.com/ [5] https://wiki.ubuntu.com/Accessibility [6] https://wiki.ubuntu.com/GoogleSoC2007 [7] https://launchpad.net/distros/ubuntu/+specs [8] https://blueprints.launchpad.net/ubuntu/+specs?searchtext=SoC2007 [9] mailto:[EMAIL PROTECTED] [10] http://code.google.com/support/bin/topic.py?topic=10442 Feel free to contact Scott James Remnant or Matthias Klose, if you require any further information. Please email [EMAIL PROTECTED] -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
