On Sat, Jun 20, 2015 at 1:26 PM, Dominique Leuenberger a.k.a. Dimstar <dimstar@opensuse.org> wrote:
Dear Tumbleweed users and hackers,
During this week, Tumbleweed has been undergoing major work, which resulted in only one minor snapshot being released into the wild (20150612 hit the mirrors on Monday). Most changes were further preparations for GCC 5, which brings me to the actual, big news for this week:
* GCC 5 has been checked in to be the default compiler collection for Tumbleweed from now on.
Due to the nature of a compiler switch, the entire distribution (> 8000 source packages) are being rebuilt. A lengthy process that is currently still ongoing. As expected, the number of build failures went up a lot (as described in the past, the staging areas only rebuild a subset of packages, namely the ones that are shipped on the DVD; doing the full repository in stagings would be unrealistic, ,due to build power constraints).
So, beloved hackers, your help is now needed to get the number of failed packages down again. In the last couple days I tried to mark the failures in the status screen [0] with some information on what could go wrong. Start your engines, branch as much as you can, fix the builds and submit them back to the devel projects and back into Tumbleweed. Let's show the world how fast we can get this back to 'normal' numbers of failures.
Christian was kind enough to post in http://lists.opensuse.org/opensuse-factory/2015-06/msg00281.html the most common issues you might encounter and some word of advice to get the issues fixed. Also, a lot of upstreams have been fixing their codes already, so an update might be worthy to look at. Last, but not least, Fedora also performed the switch in preparation for their next release (F23) and you might as well borrow patches from there.
Should you have problems with some packages, reach out to the larger community for help.
So far I identified three packages that are responsible for a big numnber of fallouts: * libusb-compat: a patch that attempted to fix closed source softare has some negative effects. An SR, disabling the patch for now, is pending against the devel prj (SR#312910) * exiv2: somehow this managed to slip through stagings: the package did not build with gcc5, due to missing includes (unistd.h). Only when cmake as buildsystem is used, then the variable would be correctly defined. Strange issue. But a switch to cmake building is submitted in SR#312666 and exiv2 based failures are confirmed to be fixed with this * p11-kit: the 'trust' binary (which is used to create the entire SSL Cert store) has issues to be started (reports ffi_prep_cif failed: 2). This error seems responsible for most (if not all) of the java build fails as well as the KDE3 related package failures. At this moment, there is no fix pending yet for this package. A bug report has been filed: https://bugzilla.opensuse.org/show_bug.cgi?id=935510 ) so, two out of three major issues are addressed; anybody finding time/energy/wisdom to look into p11-kit could possibly move that one forward (I strongly recommend to enable make check in p11-kit: it fails with the same errors at this moment). Cheers, and keep up the good work! Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org