[05:31] apw; the hint you added yesterday to make the pp6e4l vagrant-mutate test pass (testbed error) can be removed [05:31] apw: the bug is (supposed to) be fixed [06:05] cpaelzer: it was a skiptest hint so it can be removed anyway - thanks, I'll nuke that one and a number of others I had added (and rerun the tests) [06:49] slangasek: ok [06:49] slangasek: just wanted to make sure we don't skip too much forever [06:50] cpaelzer, na i just skiptest'd that one package to let it go, it had done all its other tests ok so that was safe [07:31] -queuebot:#ubuntu-release- New: accepted node-md5.js [sync] (artful-proposed) [1.3.4-1] [07:34] -queuebot:#ubuntu-release- New binary: node-md5.js [amd64] (artful-proposed/none) [1.3.4-1] (no packageset) [07:42] -queuebot:#ubuntu-release- New: accepted node-md5.js [amd64] (artful-proposed) [1.3.4-1] [08:13] jbicha: you synced a gnome-boxes which has unsatisfiable build-deps? [08:54] slangasek: please could you override the failing snapcraft test triggered by lxml? it's unrelated, see https://forum.snapcraft.io/t/snapcraft-autopkgtest-failure/2007 [08:57] * LocutusOfBorg goes fixing gnome-boxes --> slangasek, jbicha [09:09] * LocutusOfBorg goes fixing gnome-dictionary and hopefully gnome-documents [09:33] is publisher having a sad day? [09:35] not particularly [09:36] maybe just slow... I waited almost one hour, and some node stuff is still "accepted" [09:37] couple of long runs but I think that's because it ended up publishing several stable pockets [09:38] ah, daily Contents updates, that would explain it [09:40] seems good now, thanks [09:42] doko, sync python3.6? [09:54] LocutusOfBorg: no! please stop syncing for a while unnecessary stuff so that the autopkg testers can catch up [09:54] doko, I'm *asking* not *syncing* :) [09:55] well, I see your answers on artful-changes ... :-/ [09:56] gnome-* is fixed now, and should not trigger tests [09:57] netcdf was broken, I had to fix it [09:57] boinc was broken by glibc [09:57] I'm trying only to sync stuff without testsuite or to fix broken tests (e.g. mechanicalsoup I'm working right now) [09:58] did you really fix llvm? <3 [10:33] LocutusOfBorg: gnome-dictionary probably could have used a FFe [10:33] syncing gtranslator to match… [10:40] I don't see new features in the diff [10:45] the problem is the removed libgdict library not added features [10:46] LP: #1715612 [10:46] Launchpad bug 1715612 in gnome-dictionary (Ubuntu) "FFe: Sync gnome-dictionary 3.25.90-1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/1715612 [11:45] I just mass-retried all the ppc64el/artful regressions [11:46] now the the images should be fixed wrt cloud-init [11:46] hopefully will get one or two more passes [12:15] hi, I don't understand why my bind9 upload is stuck in artful-proposed ( 1:9.10.3.dfsg.P4-12.6ubuntu1). All tests that pass have passed, but there is this line of text: "Invalidated by dependency". What does that mean? [12:16] I see that present in other entries [12:17] you need to wait for the listed package to become a candidate [12:19] glibc, so nothing else will get through until glibc becomes a candidate? [12:19] I see a few "regressions" in the glibc entry [12:20] that's the whole archive almost? [12:25] nothing that version depends on it [12:26] e.g. bind9 has multiple: Depends: libc6-udeb (>= 2.26) [12:31] ahasenack, it is weird that .deb got >=2.15 dependency but udebs got 2.26. Is the udeb build somehow build differently with much higher symbols? [12:31] or shlibdeps not calculated right? [12:33] nothing like that was touched in this upload [12:34] sure, but the build is done against a new glibc. [12:34] let me download the binaries [12:35] xnox: built against libc from a-proposed, right? [12:35] ahasenack, yes... everything is build against proposed. [12:35] always. [12:36] ahasenack, note previous build is similarly broken. e.g. libisccfg-export140_9.10.3.dfsg.P4-12.5ubuntu1_amd64.deb depends on libc6 (>= 2.4) yet libisccfg-export140-udeb depends on libc6-udeb (>= 2.24) [12:36] that may be intentional of course [12:37] imho, if the binaries are not built any different between .deb and .udeb cases, the dep may be bogus - or cunning. [12:37] apw, right, if it is intentional, it is annoying =) [12:38] hmmmm.... [12:38] apw, libc6-udeb does not ship symbols file i wonder if shlibs based udeb dependencies is even a thing?! [12:51] if it has no symbols that probably explains the link to the latest major version === klebers_ is now known as klebers [14:15] slangasek, I see you did some maven related work, do you have any clue for the failures? [14:15] I'm trying to debug it, and seems Debian is indeed fine, rebuilds work there [14:16] some version mismatch, but I didn't find it (yet) [14:16] I see latest maven-* uploads in Debian changed and fixed some build/runtime dependencies, so maybe this is the clue [14:37] maybe ask before you upload? [14:54] I still think I can solve it [14:54] but I don't want to do the same job twice [15:04] LocutusOfBorg, do you do local test builds before syncing? [15:04] you should, we are post-feature freeze and post debian import freeze thus we have stopped importing things from debian en-masse. [15:05] only specific targetted fixes should be synced, not in general anything that got uploaded. [15:05] LocutusOfBorg, why do we need exec-maven-plugin 1.6.0-4? [15:06] the changelog is irrelevant for ubuntu, at this point in the cycle no? [15:08] LocutusOfBorg, why are you syncing so many minor updates? can they wait until 18.04 is open? [15:08] e.g. https://launchpad.net/ubuntu/+source/gant/1.9.11-7 is minor update, not fixing any bugs. [15:27] -queuebot:#ubuntu-release- Unapproved: flashcache (xenial-proposed/universe) [3.1.3+git20150701-2ubuntu2 => 3.1.3+git20150701-2ubuntu3] (no packageset) [15:40] LocutusOfBorg, doko: no, I uploaded what I did to try to un-break the builds that were already stuck in -proposed; the packages I uploaded, if I installed the sid binaries, were enough to unbreak the build for me, but those themselves fail to build. maven is some sort of bootstrap nightmare [15:42] slangasek, LocutusOfBorg: yes, I was trying to resolve that for 17.10. CCed you on the last email. I hope tdaitx picks this up [15:42] ok [15:46] slangasek, I did try the bootstrap and it didn't work [15:47] I mean, copy the debian package from debian, no change rebuild it, install and no change rebuild again [15:47] it failed [15:51] I'll have a deeper look after work [16:00] doko, slangasek: just went through the log, yeah, I was looking into maven last night, had a late start today so I'm still picking up from yesterday [16:06] thanks [16:29] bdmurray: weird, so somehow doing 'debuild' on a xenial box is removing that gcc build-depends from the zesty python3.6 package. No idea why [16:29] * SpamapS is building a zesty chroot to try it in now [16:33] -queuebot:#ubuntu-release- Unapproved: accepted xfsprogs [source] (zesty-proposed) [4.3.0+nmu1ubuntu4.1] [16:37] -queuebot:#ubuntu-release- Unapproved: accepted xfsprogs [source] (xenial-proposed) [4.3.0+nmu1ubuntu1.1] [17:34] bdmurray: Hey, I figured out the build-dep thing. The rules file added that to the synced package from Debian, but when one builds the source package in Ubuntu, that gcc build-dep is not added. It's also not needed, it's for backports. [17:34] bdmurray: so, if you haven't rejected the other one yet... [17:35] oh I see it was rejected [17:35] * SpamapS re-uploads [17:36] -queuebot:#ubuntu-release- Unapproved: python3.5 (zesty-proposed/main) [3.5.3-1 => 3.5.3-1ubuntu0~17.04.0] (core) [17:53] -queuebot:#ubuntu-release- Unapproved: accepted python3.5 [source] (zesty-proposed) [3.5.3-1ubuntu0~17.04.0] [20:23] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-95.118] (core, kernel) [20:52] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-95.118]