[01:17] slangasek: FTR: src:qtwebengine-opensource-src is building in Bileto ticket 3113 now; if/when the build passes, it should be ready to publish. [01:18] I unfortunately don't have the rights to do that quite yet though, so unless you'd like to press the button for me, I'll be waiting on either Dmitry or Gi'anfranco. [01:18] *Gianfranco [01:19] tsimonq2: did the discussion yesterday about abis being bumped or not yield a different answer wrt entangling with curl? [01:19] slangasek: Oh, good point, let me double-check that now that you mention it... [01:21] $ grep-dctrl $ -FDepends qtdeclarative-abi-5-9-3 -o -FDepends qtbase-abi-5-9-3 $ -a -FDepends libcurl3 /chroots/bionic/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_bionic_*amd64_Packages [01:21] That returns nothing. [01:21] er [01:22] $ grep-dctrl $ -FDepends qtdeclarative-abi-5-9-2 -o -FDepends qtbase-abi-5-9-2 $ -a -FDepends libcurl3 /var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_bionic_*amd64_Packages [01:22] THAT command returns nothing (well, they both do, but the last one is more accurate ;) ) [01:22] slangasek: So we're good. [01:23] ok [04:10] slangasek: ukui-power-manager is in Bionic source NEW [04:11] -queuebot:#ubuntu-release- New source: ukui-power-manager (bionic-proposed/primary) [1.1.1-0ubuntu1] [05:22] acheronuk: yes, thanks.. and now it's clutter left [05:25] tjaalton: I'm thinking Qt will land in -proposed within the next 12 hours or so, and at that point I'll take the block-proposed tag off of that mesa bug. [05:27] tsimonq2: ok, good [06:04] -queuebot:#ubuntu-release- New binary: lxc [amd64] (bionic-proposed/main) [2.1.1-0ubuntu2] (ubuntu-server) [06:04] -queuebot:#ubuntu-release- New binary: lxc [s390x] (bionic-proposed/main) [2.1.1-0ubuntu2] (ubuntu-server) [06:05] -queuebot:#ubuntu-release- New binary: lxc [i386] (bionic-proposed/main) [2.1.1-0ubuntu2] (ubuntu-server) [06:05] -queuebot:#ubuntu-release- New binary: lxc [ppc64el] (bionic-proposed/main) [2.1.1-0ubuntu2] (ubuntu-server) [06:07] -queuebot:#ubuntu-release- New binary: lxc [arm64] (bionic-proposed/main) [2.1.1-0ubuntu2] (ubuntu-server) [06:07] -queuebot:#ubuntu-release- New binary: lxc [armhf] (bionic-proposed/main) [2.1.1-0ubuntu2] (ubuntu-server) [08:32] -queuebot:#ubuntu-release- New source: pyxs (bionic-proposed/primary) [0.4.1+dfsg1-0ubuntu1] [09:31] -queuebot:#ubuntu-release- New: accepted pocket-lint [amd64] (bionic-proposed) [0.5.31-0ubuntu2] [10:53] RAOF: hi, could you please release fixes for LP: #1644662 to -updates? [10:53] Launchpad bug 1644662 in gnome-themes-standard (Ubuntu Artful) "Icons missing when appearance setting is "high contrast"" [High,Fix committed] https://launchpad.net/bugs/1644662 [11:19] -queuebot:#ubuntu-release- Unapproved: libvirt (xenial-proposed/main) [1.3.1-1ubuntu10.19 => 1.3.1-1ubuntu10.20] (ubuntu-server, virt) [11:20] -queuebot:#ubuntu-release- Unapproved: libvirt (artful-proposed/main) [3.6.0-1ubuntu6.3 => 3.6.0-1ubuntu6.4] (ubuntu-server, virt) [12:29] Qt 5.9.4 transition incoming [12:29] tjaalton: why is the new X11 still in -proposed? https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 [12:29] Ubuntu bug 1752053 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-390 fails to boot graphical display" [Undecided,Confirmed] [12:33] tseliot: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#gdbm [12:34] why did -390 migrate without libglvnd? [12:34] or didn't it depend on the new xserver? [12:35] hi all, can someone from the release team take a look at percona-xtradb-cluster-5.7 in the bionic NEW queue? we're moving OpenStack to 5.7 in bionic. [12:36] tjaalton: I think the packages pull in libglvnd, but I didn't add a dependency on the new X [12:37] ok, that's too bad [12:37] and bionic did have the old libglvnd.. [12:37] oh [12:37] tjaalton: does the new libglvnd break things or what? [12:38] no, the old one was useless [12:38] how do we fix this? [12:40] get xserver migrated [12:40] by ignoring the remaining failures [12:40] slangasek: ^^ [12:40] virtualbox hasn't been updated to build against 4.15, for one [12:45] hmm, nvidia could be demoted back to proposed [13:47] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:47] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:47] -queuebot:#ubuntu-release- Builds: Netboot armhf [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:47] -queuebot:#ubuntu-release- Builds: Netboot i386 [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:47] -queuebot:#ubuntu-release- Builds: Netboot powerpc [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:47] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:47] -queuebot:#ubuntu-release- Builds: Netboot s390x [Xenial 16.04.4] (20101020ubuntu451.22) has been added [13:52] tjaalton: block-proposed removed from mesa, should process on the next Britney run [13:53] tsimonq2: except clutter tests are still failing [13:55] tjaalton: OK; but at least there's not a block-proposed tag now :) [13:56] right, thanks [14:15] tjaalton: did you look into the clutter failures? [14:16] Laney: nothing in them [14:16] tried to hint together with libglvnd, didn't help on ppc64el at leaste [14:16] -e [14:17] what do you mean? [14:17] but ruby-gnome2 got green after hinting xorg-server + mesa + libglvnd [14:17] to pull those from -proposed [14:18] saying that the errors are same as on the gtk+3.0 update [14:19] yes that one pulled the new mesa too [14:19] ah [14:19] ok then :) [14:23] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-11.12] (core, kernel) [14:25] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-11.12] [14:27] just tried locally with all of proposed (--apt-pocket=proposed), still fails :( [14:32] I'll check with upstream [14:36] Laney: can you modify the installation? add this in /etc/drirc: https://pastebin.com/xVndMjWM [14:36] err [14:36] no [14:36] it's only for gnome-shell :) [14:41] hum [14:41] could be that adding a patch or two to xserver would fix these [14:41] if it's related to 30bit support [14:41] as it looks like [14:41] Clutter-Conform:ERROR:texture.c:62:texture_pick_with_alpha: assertion failed: (actor == CLUTTER_ACTOR (tex)) [14:42] http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test <- if you do that stuff you should be able to make it fail for you [14:42] the commits are on the stable tree anyway, we'd get them eventually via 1.19.7 but it's not out yet [14:43] thanks, I'll try that [14:43] How long after I start a transition should Ben pick things up? [14:44] (I technically started two but) qtbase-abi-5-9-2 -> qtbase-abi-5-9-4 and qtdeclarative-abi-5-9-2 -> qtdeclarative-abi-5-9-4 aren't showing up. [14:45] Laney: this should help https://gitlab.gnome.org/GNOME/mutter/merge_requests/36 [14:45] or just skip the tests [14:46] that's what daniels said [14:47] * apw has a look seen when ben last updated [14:47] so there are some arm tests on xserver that most likely failed due to the new mesa [14:48] apw: It's weird, because the footer says it's been updated but the transition isn't showing up [14:48] If anything I'm making sure it's not PEBKAC on my part :) [14:49] tsimonq2, those are new? they are not going to get in the way or current ones that need migrating right? [14:50] seb128: Right; I cleared it with slangasek yesterday (and the day before at that) [14:52] seb128: mesa was also waiting on Qt to show up in -proposed because mesa breaks Qt and the uploaded Qt has the patch [14:52] ah ok [14:52] (wtbase, to be specific) [14:52] *qtbase [14:52] so that transition is a new one that needs to clear off as well now? [14:52] is it an easy one? [14:53] It should be fairly easy, it's just a bugfix Qt release [14:53] I already did direct rdeps and fixed e.g. gammaray [14:53] ("did" meaning no-change rebuilt) [14:54] k, good then [14:55] we really need those transitions to clear, we have other ones waiting to be upload and ff coming [14:55] tsimonq2, i am not sure i can see any new trackers in the config ? [14:55] or the other option is to stack the ones which are waiting but that would makes it difficult to sort out then [14:55] flocculant: Poke, what was that one problematic Xfce package that needed a no-change rebuild for the last Qt transition? [14:56] seb128: Right; the *last* think I think we all want is what we had at the beginning of the cycle except last minute :) [14:56] apw: Hm... maybe it won't show up then [14:56] tsimonq2, where did you add them ? [14:57] apw: I'm not sure what you mean; I didn't add things anywhere manually, I just started the transition [14:57] not sure we have any autotrackers [14:58] OK, so how do I add it? [14:58] (I'd like to learn how for this time and the following times) [14:58] you'd need to make up the .ben and add it to the transition-tracker-config if you have access [14:58] How do I know if I have access? :) [14:59] * tsimonq2 is just in ~motu [15:00] * apw pasts long urls into PM for tsimonq2 [15:01] Ah yes, so I do have commit access here. [15:01] As acheronuk says, qool. [15:01] :P [15:40] -queuebot:#ubuntu-release- Unapproved: cockpit (artful-backports/universe) [161-1~ubuntu17.10.1 => 162-1~ubuntu17.10.1] (no packageset) [15:41] -queuebot:#ubuntu-release- Unapproved: cockpit (xenial-backports/universe) [161-1~ubuntu16.04.1 => 162-1~ubuntu16.04.1] (no packageset) [15:44] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (artful-backports) [162-1~ubuntu17.10.1] [15:44] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (xenial-backports) [162-1~ubuntu16.04.1] [15:48] Can a Core Developer please no-change rebuild qtubuntu for qtbase-abi-5-9-4? I don't have upload access. [15:49] LocutusOfBorg, apw: ^^^^ [15:52] awesome/armhf should be hinted as ignored.. seems to be quite failure prone in the past too [15:53] also, clutter & virtualbox should not be blocking xorg-server [15:59] tsimonq2: just a no-change direct-upload rebuild into bionic? [15:59] sil2100: Yes. [16:00] tsimonq2: done o/ [16:01] sil2100: Thank you! [16:01] yw! === Savicq is now known as Saviq [16:12] tseliot, slangasek: xorg-server would migrate if awesome/armhf would not time out(?), clutter has known issues with new mesa, and virtualbox dkms doesn't build with 4.15 [16:13] as a recap [16:13] and with that, I'm afk [16:13] "clutter has known issues with new mesa" sigh... [16:15] well not clutter, but cogl and mutter [16:15] it won't affect xserver [16:15] ok [16:15] just that the blocking autopkgtest pulled new mesa [16:15] and fails [16:16] what about libglvnd? [16:16] would that work with the current mesa? [16:16] I hinted some tests to pull mesa & libglvnd too, and they passed [16:16] for instance awesome/arm64 passed now, but armhf seems to time out or something [16:16] no [16:17] do you have a bug report for mesa/mutter? [16:17] no, Laney might create one?-) [16:18] bah, I'll do it [16:21] Laney, tseliot: bug 1752123 [16:21] bug 1752123 in mutter (Ubuntu) "Force 8bit RGB config" [Undecided,New] https://launchpad.net/bugs/1752123 [16:22] thanks [16:22] tjaalton: thx [16:22] I found https://src.fedoraproject.org/rpms/cogl/blob/master/f/0001-egl-Use-eglGetPlatformDisplay-not-eglGetDisplay.patch too, is it related? [16:23] Laney: it might be [16:23] well I did try the patch, but we're not that lucky :-) [16:25] sounds like it's useful with libglvnd in any case [16:31] so, it's picking the wrong EGL config. I haven't seen the cogl code, but it should be easy to fix [16:35] tsimonq2, . [16:36] LocutusOfBorg: \o/ [16:47] me and sil2100 raced at the same time [16:47] he win [16:48] :D [16:53] tseliot: mutter merged cogl, the mutter patch should fit back to cogl without too much trouble [16:56] tjaalton: yes, and cogl seems to use GBM_FORMAT_XRGB8888 in _cogl_winsys_egl_context_created(), so things should just work [16:56] tjaalton: we only need to fix the leak in the patch for mutter then [16:59] -queuebot:#ubuntu-release- New source: rax-nova-agent (bionic-proposed/primary) [2.1.12-0ubuntu1] [17:12] tjaalton: on a second thought, the leak mentioned in the bug report doesn't seem to be there any more [17:13] g_free (egl_configs) is there at the end of the call [17:14] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (artful-proposed) [4.3.5-3ubuntu2.1] [17:15] Laney: do commits e4e4f9acfc63d0e7e097b4276b37ffe7320dc0fd 00b45444df8ed6bf17eaae6532db0bc86b471912 91e04666093ae0cc976159e1aa466cf2e2184138 solve your problem in mutter? [17:16] tseliot: I don't (atm) have a problem in mutter, just the clutter/cogl one [17:17] maybe the cogl bits from the mutter copy need to be ported over [17:17] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (xenial-proposed) [4.3.3-5ubuntu12.8] [17:19] -queuebot:#ubuntu-release- New: accepted lxc [amd64] (bionic-proposed) [2.1.1-0ubuntu2] [17:19] -queuebot:#ubuntu-release- New: accepted lxc [armhf] (bionic-proposed) [2.1.1-0ubuntu2] [17:19] -queuebot:#ubuntu-release- New: accepted lxc [ppc64el] (bionic-proposed) [2.1.1-0ubuntu2] [17:19] -queuebot:#ubuntu-release- New: accepted lxc [arm64] (bionic-proposed) [2.1.1-0ubuntu2] [17:19] -queuebot:#ubuntu-release- New: accepted lxc [s390x] (bionic-proposed) [2.1.1-0ubuntu2] [17:19] -queuebot:#ubuntu-release- New: accepted lxc [i386] (bionic-proposed) [2.1.1-0ubuntu2] [17:19] Laney: yes, I think so. Cogl should already do the right thing, picking GBM_FORMAT_XRGB8888 [17:19] -queuebot:#ubuntu-release- Unapproved: accepted isc-dhcp [source] (trusty-proposed) [4.2.4-7ubuntu12.11] [17:21] tseliot: alright, well you should be able to reproduce the failure and test any ports ;-) [17:22] Laney: how do I reproduce the problem? Use intel + the new mesa + X11 in Bionic? [17:23] tseliot: you can use xvfb even [17:24] something like autopkgtest --apt-upgrade --apt-pocket=proposed=src:mesa clutter-1.0 ~/temp/*1.22.2-3ubuntu1*.deb --shell-fail -- qemu autopkgtest-bionic-amd64.img [17:24] umm without the ~/temp/bit [17:25] Laney: I'm not familiar with autopkgtest. Where can I find the documentation, please? [17:26] http://packaging.ubuntu.com/html/auto-pkg-test.html#executing-the-test [17:26] thanks [17:28] but maybe also installing clutter-1.0-tests and running those with xvfb-run gnome-desktop-testing-runner would work -- I didn't check that though [17:28] with the -proposed mesa ofc [17:31] ok, let's see what I can do [17:39] tsimonq2: not sure - don't generally know about packaging [17:40] flocculant: ack [17:41] sorry :) might possibly have been not xfce - might well have been something local to me [17:41] s/xfce/Xubuntu [17:41] OK, well let me know :) [17:42] tsimonq2: I use a couple of apps that qt - cantata and clementine - though I build from git [17:43] anyway - if something blows up in Xubuntu I will be sure to let you know [17:43] Sure/ [17:44] does anybody have clues about abi-compliance-checker regressed in release? [17:44] https://autopkgtest.ubuntu.com/packages/abi-compliance-checker/bionic/arm64 [17:45] I blame maybe gcc/binutils, seems reproducible with the old glibc [17:45] infinity, ^^ [17:45] (blocking perl migration) [18:25] tsimonq2: ok, I see qtbase-opensource-src in and lots of failing autopkgtests. What needs to happen to get passing results there? [18:27] slangasek: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/a/akonadi/20180227_135433_a2e38@/log.gz is interesting [18:27] slangasek: Otherwise I haven't looked deeply yet; I've mostly been dealing with no-change rebuilding rdeps this far [18:28] slangasek: Aaaand I think that's why there's a bunch of failures, uninstallable deps :) [18:29] slangasek: So I'll hit retry on these once Ben says it's good, and some of the failures should go away. [18:30] slangasek: But I do have the day off today, so I'll work on getting these done should there be any real failures as soon as I can. [18:32] s/some of the failures should go away/a lot of the failures should go away/ [18:32] But I have been working on it :) [18:33] tsimonq2: they need to be retries that pull multiple sources from -proposed, I'm sure, so it's not just hitting the retry button; are you triggering with --all-proposed, or with a trigger list? [18:34] slangasek: I have yet to get that far [18:34] slangasek: But probably with --all-proposed [19:08] slangasek: So qtdeclarative tests are retried, but I just realized I can't retry *any* of the qtbase tests because I don't have upload access... [19:09] tsimonq2: if you give me a retry-autopkgtest-failures pipeline that you think will DTRT, I'll push buttons [19:13] slangasek: I would even go so far as to do a ./retry-autopkgtest-regressions --all-proposed --blocks qtbase-opensource-src | vipe | xargs -rn1 -P10 wget --load-cookies ~/.cache/autopkgtest.cookie -O- [19:13] slangasek: I'd say after looking at all these failures, the vast majority are depwait packages that should be fixed now [19:13] ok [19:13] minus the 'vipe', I hope? :) [19:14] idk, I copy/pasted from ./retry-autopkgtest-regressions -h [19:14] XD [19:14] But yea, I guess so [19:17] I can poke sensible test retries test tomorrow while USA people are sleeping, if that helps [19:17] Sure [19:21] LocutusOfBorg: Not the most helpful of logs. I assume running the test locally and looking at the referenced build-log.txt might be more illuminating. [19:21] infinity, I can't setup an arm64 pbuilder environment anymore :/ [19:23] I hit this bug https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1725333 [19:23] Ubuntu bug 1725333 in glibc (Ubuntu) "do-release-upgrade broke WSL" [Undecided,Confirmed] [19:23] LocutusOfBorg: Oh, didn't notice it's only regressed on arm64. Fun. [19:24] :/ [19:24] this is why I pinged you :) [19:49] tjaalton: badtesting awesome/armhf; haven't looked at the others yet; do you know why nvidia-graphics-drivers-340 is unhappy with the new libglvnd? seems libglvnd is rather critical, nvidia is currently broken in bionic because it needs the new libglvnd [19:50] slangasek: new 340 isn't uploaded yet because xorg-server hasn't migrated [19:50] though it could/should depend on the new version [19:50] like 390 should've [19:51] tjaalton: I don't follow. why should xorg-server migrate before the new 340 is uploaded? [19:52] should migrate together, because 340/390 use the new more automated configuration [19:54] well they can't migrate together if nvidia-graphics-drivers-340 hasn't been uploaded [19:54] true [19:54] tseliot will upload it and add the dep [19:54] yes [19:55] tseliot: ^^ any eta on nvidia-graphics-drivers-340 then? since it's in the critical path for un-breaking -390 in bionic release [19:55] a few minutes, I think [19:56] slangasek: I need to add the dependency on the new X [19:56] ok [20:17] hello. Can we please get snapcraft 2.39.2 into xenial-updates? I've marked the sru as verified: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1745488 [20:17] Ubuntu bug 1745488 in snapcraft (Ubuntu Artful) "[SRU] New stable micro release 2.39.2" [Undecided,Confirmed] [20:28] slangasek: I've just uploaded 340 [20:28] tseliot: cheers [20:29] :) [20:36] slangasek: btw, the blocker still remains that cogl needs fixing so all clutter tests work with the new mesa.. [20:41] tjaalton: well, yuck [20:51] RAOF: ping. Can you help us releasing snapcraft 2.39.2? [21:28] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-143.192] (core, kernel) [21:31] -queuebot:#ubuntu-release- New source: s2tc (bionic-proposed/primary) [1.0+git20151227-2ubuntu1] [21:32] slangasek: fyi, afaict, php7.1 can now be removed from the archive [21:32] (src:php7.1, that is) [21:36] https://bugs.launchpad.net/ubuntu/+source/php7.1/+bug/1752177 [21:36] Ubuntu bug 1752177 in php7.1 (Ubuntu) "RM superseeded by php7.2" [High,Triaged] [21:36] xnox: ah thanks [21:37] was just going to file the same :) [22:10] dgadomski: [22:11] dgadomski: You want #1644662 released to xenial-updates? We're in the process of spinning the 16.04.4 release - do you have approval from the release team? [22:39] looks like linux-firmware didn't make it out of xenial-proposed before the 16.04.4 freeze - which breaks server ISO installs on servers with QED nics - any chance that can get pushed in? [22:42] slangasek: I'm scratching my head at why a lot of these autopkgtests are still showing failures [22:42] slangasek: I mean, some of them seem fine... [22:42] slangasek: It could also be that I jumped the gun in asking you to retry them [22:43] slangasek: I mean, I can install most of these in an LXD container with -proposed enabled... [22:43] * tsimonq2 wishes I had upload access so I could confirm with just one or two of these that it was indeed depwait and not some hidden, complex dependency mess [22:51] dannf, you need to highlight e.g. slangasek sil2100 (who is not here?!) cyphermox who can i believe release linux-firmware, and can trigger the respin of the world. [22:51] tsimonq2: have you tried them locally? [22:51] tsimonq2: being able to install with -proposed enabled is not quite the same as being ok per britney, because you need to be able to install with the packages currently in release not there as well [22:51] nacc: Yes, in LXD [22:52] mwhudson: ohh, good point [22:52] tsimonq2: which is extremely confusing [22:52] nacc: Oh, the autopkgtest... that's also a good point [22:52] mwhudson: It is [22:52] tsimonq2, you mention autopkgtests, and proposed migration. do you see install failure in autopkgtests? or when britney considers packages for migration (update output)? [22:52] tsimonq2: yeah, i meant the dep8 test [22:53] xnox: In the autopkgtest itselfd [22:53] tsimonq2: which packages are you fighting with? [22:53] *itself [22:53] mwhudson: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src [22:53] mwhudson: A really good chunk of those are dep problems [22:53] oh that package name doesn't make me think of tentacles at all [22:55] * tsimonq2 pulls a few locally and throws it at autopkgtest-virt-schroot [22:56] tsimonq2: ok yes so the one failure i looked at there is pretty opaque indeed [22:56] mwhudson: That's why I'm like "OK, retrying these *probably* fixes them..." [22:57] tsimonq2: i clicked retry on this one http://autopkgtest.ubuntu.com/packages/k/kde-cli-tools/bionic/amd64 [22:57] mwhudson: Alright, let's see [22:57] tsimonq2, the way i see things, is that a lot of your builds still have not been published, despite completing on launchpad 7h ago. [22:58] xnox: All of the builds for everything I've uploaded today have been published [22:58] Unless you can prove me wrong there [22:59] But I did indeed manually vet rdeps to make sure they published [23:00] tsimonq2, true. i was looking at old cached edition of excuses. [23:08] Ahh, so indeed there's still some stuff in the queue from ~vorlon [23:16] I really really wish it would show on update_excuses.html if a test is queued... [23:18] That would have saved me lots of time here [23:19] tsimonq2: yeah, there's been some on and off discussion of that [23:19] tsimonq2: didn't you offer to fix it? :) [23:20] nacc: I offered to fix the duplicate tests in the queue; similar but not the same :) [23:20] lol [23:20] Do we have a bug for that state in update_output.html or should I file one now? [23:21] tsimonq2: i'm not sure [23:21] Aha: https://bugs.launchpad.net/auto-package-testing/+bug/1654761 [23:21] Ubuntu bug 1654761 in Auto Package Testing "Use another status for retried but queued items" [Undecided,New] [23:23] * tsimonq2 will do work on this post-feature freeze ;) [23:29] robert_ancell: I notice the snapd-glib upload wanting to go into artful-proposed isn't bugfix-only. [23:29] robert_ancell: But many of the packages around snapd have standing SRU exceptions; should snapd-glib have one, too? [23:32] RAOF, it should do but I haven't done the paperwork for it. I've been doing a SRU for each upload under the category of "new upstream microreleases" [23:33] Which, I suspect, is why I'm now processing the artful upload from November last year :) [23:33] RAOF, what version was that one? [23:34] robert_ancell: 1.24 [23:35] Fixing https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1723874 and https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1721762 [23:35] Ubuntu bug 1723874 in snapd-glib (Ubuntu Artful) "First installation of a snap reports an error "Connection reset by peer"" [High,Fix committed] [23:35] Ubuntu bug 1721762 in snapd-glib (Ubuntu Artful) "Cancelled installation of snap continues" [High,Fix committed] [23:37] And also adding a bunch of features and an API break(!) [23:40] RAOF: ping. Can you help us releasing snapcraft 2.39.2? [23:40] elopio: Sure! [23:40] thank you :) This is the bug: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1745488 [23:40] Ubuntu bug 1745488 in snapcraft (Ubuntu Artful) "[SRU] New stable micro release 2.39.2" [Undecided,Confirmed] [23:41] Hm, or maybe? [23:41] What's going on with snapcraft‽ [23:43] elopio: Why is the version in xenial-proposed greater than the version in artful-proposed? [23:44] elopio: Also, 16.04.4 is being prepared. [23:44] elopio: Also, have you investigated the autopkgtest failure? [23:44] RAOF, yeah, the API break is a tricky one. We had to move an enum in the Qt bindings. The good news is probably nothing is using them in that release and it's not an ABI break. It's also fairly trivial to fix an app that would use the enum. [23:45] robert_ancell: Anything in the archive which *might* use them? [23:48] RAOF, the only thing in the archive is plasma-discover and that didn't start using them until bionic. And the change was recommended by the author of that. [23:48] I got to bypass the issue in xenial because we never shipped the Qt bindings.