[ARTFUL pacemaker - note ] pacemaker package doesn't build (doesn't build as is without any changes) in Artful. I suspect the package has been first build in Zesty and then simply copied to Artful when the release was first created (without going through the build farm again). Additionally, no change has been made in Artful since the suspected Zesty->Artful copy so no one could have notice the FTBFS situation before today.
IMHO, the above is the most plausible reason explaining why we have a binary package for Artful even though it fails to build in Artful. # buildlog : https://launchpadlibrarian.net/357638704/buildlog_ubuntu-artful-amd64.pacemaker_1.1.16-1ubuntu1_BUILDING.txt.gz ... crm_mon.c: In function ‘print_nvpair’: crm_mon.c:959:30: error: comparison between pointer and zero character constant [-Werror=pointer-compare] for (c = date_str; c != '\0'; ++c) { ^~ crm_mon.c:959:28: note: did you mean to dereference the pointer? for (c = date_str; c != '\0'; ++c) { ... ^ cc1: all warnings being treated as errors Makefile:1028: recipe for target 'crm_mon.o' failed make[3]: *** [crm_mon.o] Error 1 make[3]: *** Waiting for unfinished jobs... ... dh_auto_build: make -j4 returned exit code 2 debian/rules:31: recipe for target 'override_dh_auto_build-indep' failed make[1]: *** [override_dh_auto_build-indep] Error 2 make[1]: Leaving directory '/<<PKGBUILDDIR>>' debian/rules:15: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740892 Title: corosync upgrade on 2018-01-02 caused pacemaker to fail To manage notifications about this bug go to: https://bugs.launchpad.net/charm-hacluster/+bug/1740892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
