[00:14] <tsimonq2> (Mesa should not migrate until qtbase is uploaded, and that'll be another couple of days, hopefully not longer.)
[00:15] <tsimonq2> ((Core Qt bootstrapping for 5.9.4 is complete, so it just depends on how quickly I can get through the other uploads... #ubuntu-qt has more details.))
[02:07] <tsimonq2> infinity: Is that glibc transition something that will collide with the Qt transition? That's close to being ready-to-land and I don't want to break things. :)
[03:24] <slangasek> tsimonq2: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output_notest.txt shows the list of packages that need updated for glibc to get in (once tests are resolved); it's a small list and almost certainly not entangled w/ Qt, but if you want to double-check, there it is.  Also, is this Qt transition something that will collide with the curl transition?
[03:25] <tsimonq2> slangasek: I'm not sure what the curl transition involves but https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3113/+packages https://pad.ubuntu.com/BhiLYwz07Y + no-change rebuilds of qtbase and qtdeclarative rdeps + sddm is what it is
[03:25] <tsimonq2> slangasek: It's a bugfix Qt release.
[03:26] <slangasek> tsimonq2: anything that depends on libcurl3 will need rebuilt
[03:26] <slangasek> I know there are some KDE packages affected
[03:27] <tsimonq2> slangasek: I'd have to check.
[03:27]  * tsimonq2 does so
[03:29]  * slangasek kicks off the rebuilds of the things needing rebuilt for glibc; no reason to wait
[03:29] <tsimonq2> Cool
[03:30] <tsimonq2> slangasek: One thing I've always relied on either Ben or Britney to tell me but I can't seem to figure out how to do is find rdeps of e.g. qt{base,declarative}-abi-5-9-3
[03:30] <slangasek> grep-dctrl is your friend
[03:31] <tsimonq2> Ahh, nice.
[03:31]  * tsimonq2 RTFMs
[03:32] <slangasek> good news, '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' returns no results
[03:33]  * tsimonq2 notes that command for future ref, thanks
[03:35] <tsimonq2> Once the monster that is qtwebengine (embedded Chromium, it's like a 200 MB source package that takes hours to compile, fun) is done building here, the rest of the Qt transition should take little to no time.
[03:35] <tsimonq2> So my original estimate was two days but it might be ready by tomorrow afternoon(ish) (UTC-6)
[03:36] <tsimonq2> slangasek: Is that OK from a Release Team perspective or do you think glibc needs more time (for some reason)?
[03:38] <tsimonq2> ("the rest of the Qt transition" in Bileto, that is)
[04:20] <slangasek> tsimonq2: glibc + qt shouldn't get in the way of each other, from what I see, so no reason to delay on account of glibc
[04:21] <tsimonq2> slangasek: OK, cool. Thanks.
[04:22] <tsimonq2> Tonight I'll start the Britney checks in Bileto so it has time to process while I'm asleep.
[04:52] <slangasek> I see someone's been retrying colord/armhf a few times against glibc... that probably needs an updated valgrind
[06:55]  * RAOF needs to do the last bits required to release a new colord in Debian and sync.
=== sil2100 changed the topic of #ubuntu-release to: Released: Xenial 16.04.3, Artful 17.10 | Archive: open | Bionic Release Coordination, 16.04.4 in progress | Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melius malum quod cognoscis
[08:01] <sil2100> Note to any SRU members around - for the time of the point release, please don't promote things from xenial-proposed to xenial-updates
[08:01] <sil2100> Not sure if we have any lock for that now as I probably don't have the powers for doing it
[08:11] <tsimonq2> sil2100: generate-freeze-block could be what you're looking for, although that mightt be just for devel...
[08:11] <tsimonq2> ¯\_(ツ)_/¯
[08:18] <apw> sil2100, ack
[08:19] <apw> tsimonq2, as we don't gate sru's yet via britney it won't help sadly, and in fact everything is blocked
[08:20] <tsimonq2> apw: Ah ok
[08:20] <tsimonq2> Not just seeded stuff?
[08:20] <tsimonq2> What's the reasoning there?
[08:20] <tsimonq2> Also, TIL about not using Britney for that :)
[08:21] <sil2100> Well, not seeded stuff can go in I guess, but since people rarely check that I just mentioned in overall
[08:22] <apw> sil2100, keep it at "don't" for now, makes people think before they act
[08:22] <apw> tsimonq2, yeah it is in the plan, just never seems to hit the top of the list
[08:27] <tsimonq2> apw: Got something along the lines of a spec somewhere for that?
[08:28] <apw> tsimonq2, heh as far as i know it is in infinity's head
[08:28] <tsimonq2> :D
[08:33] <mitya57> slangasek, tsimonq2: “grep-dctrl \( -FDepends qtdeclarative-abi-5-9-3 -o -FDepends qtbase-abi-5-9-3 \) … returns no results”
[08:33] <mitya57> That's because we did not bump the ABI version last time, and it was 5-9-2.
[08:33] <tsimonq2> Ahh
[08:33] <tsimonq2> Right
[08:34] <mitya57> Well, for qtbase only, for qtdeclarative I think it was bumped.
[09:04] <jibel> sil2100, on ubuntu desktop 20180223.1 it still says 16.04.3
[09:17] <infinity> jibel: Fixed.
[09:18] <infinity> sil2100: ^-- When you updated debian-cd, you missed a 'bzr pull' at nusakan:~cdimage/cdimage/debian-cd
[09:18] <infinity> sil2100: So, you get to spin another set with the correct versions. :P
[09:18] <infinity> sil2100: I'll leave that to you.
[09:24] <jibel> infinity, thanks
=== freyes__ is now known as freyes
[10:48] <sil2100> hmmm
[10:49] <sil2100> Ah, crap, I know what happened
[10:49] <sil2100> Since the bzr checkout was actually from nusakan I assumed it's directly to the right branch
[10:50] <sil2100> duh, still needed that bzr pull from the private bzr place to production
[10:51] <sil2100> Stupid me, assuming bzr push pushes to production directly
[11:09] -queuebot:#ubuntu-release- New: accepted gnome-keyring [amd64] (bionic-proposed) [3.27.4-2ubuntu1]
[11:09] -queuebot:#ubuntu-release- New: accepted gnome-keyring [armhf] (bionic-proposed) [3.27.4-2ubuntu1]
[11:09] -queuebot:#ubuntu-release- New: accepted gnome-keyring [ppc64el] (bionic-proposed) [3.27.4-2ubuntu1]
[11:09] -queuebot:#ubuntu-release- New: accepted gnome-keyring [arm64] (bionic-proposed) [3.27.4-2ubuntu1]
[11:09] -queuebot:#ubuntu-release- New: accepted gnome-keyring [s390x] (bionic-proposed) [3.27.4-2ubuntu1]
[11:09] -queuebot:#ubuntu-release- New: accepted gnome-keyring [i386] (bionic-proposed) [3.27.4-2ubuntu1]
[11:10] -queuebot:#ubuntu-release- New: accepted udisks2 [amd64] (bionic-proposed) [2.7.6-1ubuntu1]
[11:10] -queuebot:#ubuntu-release- New: accepted udisks2 [armhf] (bionic-proposed) [2.7.6-1ubuntu1]
[11:10] -queuebot:#ubuntu-release- New: accepted udisks2 [ppc64el] (bionic-proposed) [2.7.6-1ubuntu1]
[11:10] -queuebot:#ubuntu-release- New: accepted udisks2 [arm64] (bionic-proposed) [2.7.6-1ubuntu1]
[11:10] -queuebot:#ubuntu-release- New: accepted udisks2 [s390x] (bionic-proposed) [2.7.6-1ubuntu1]
[11:10] -queuebot:#ubuntu-release- New: accepted udisks2 [i386] (bionic-proposed) [2.7.6-1ubuntu1]
[11:23] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:23] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:26] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:26] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:31] <Laney> can someone promote for https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1749912 please? https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.txt
[11:31] <ubot5`> Ubuntu bug 1749912 in libglvnd (Ubuntu) "MIR: libglvnd" [Wishlist,Fix committed]
[11:32] <apw> Laney, looking
[11:32] <Laney> merci!
[11:32] <Laney> should make mutter become a candidate in excuses
[11:33] <Laney> and gnome-session..?
[11:38] <apw> Laney, done
[11:40] <Laney> apw: thanks!
[11:41] -queuebot:#ubuntu-release- Builds: Mythbuntu Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:41] -queuebot:#ubuntu-release- Builds: Mythbuntu Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:42] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:42] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:42] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:42] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:43] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:43] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:44] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:44] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:44] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Xenial 16.04.4] has been updated (20180226)
[11:44] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Xenial 16.04.4] has been updated (20180226)
[11:46] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Xenial 16.04.4] has been updated (20180226)
[11:46] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Xenial 16.04.4] has been updated (20180226)
[12:00] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Xenial 16.04.4] has been updated (20180226)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Xenial 16.04.4] has been updated (20180226.1)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Xenial 16.04.4] has been updated (20180226.1)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Xenial 16.04.4] has been updated (20180226.1)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Xenial 16.04.4] has been updated (20180226.1)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base powerpc [Xenial 16.04.4] has been updated (20180226.1)
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Xenial 16.04.4] (20180226.1) has been added
[12:20] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Xenial 16.04.4] has been updated (20180226.1)
[12:32] -queuebot:#ubuntu-release- New binary: curl [s390x] (bionic-proposed/main) [7.58.0-2ubuntu2] (core)
[12:33] -queuebot:#ubuntu-release- New binary: curl [i386] (bionic-proposed/main) [7.58.0-2ubuntu2] (core)
[12:34] -queuebot:#ubuntu-release- New binary: curl [ppc64el] (bionic-proposed/main) [7.58.0-2ubuntu2] (core)
[12:36] -queuebot:#ubuntu-release- New binary: curl [amd64] (bionic-proposed/main) [7.58.0-2ubuntu2] (core)
[12:43] -queuebot:#ubuntu-release- New binary: curl [arm64] (bionic-proposed/main) [7.58.0-2ubuntu2] (core)
[12:45] -queuebot:#ubuntu-release- New binary: curl [armhf] (bionic-proposed/main) [7.58.0-2ubuntu2] (core)
[13:18] <coreycb> hello, can an archive admin review percona-xtradb-cluster-5.7 in the bionic NEW queue?
[13:33] -queuebot:#ubuntu-release- Unapproved: apache2 (xenial-proposed/main) [2.4.18-2ubuntu3.5 => 2.4.18-2ubuntu3.6] (ubuntu-server)
[15:47] -queuebot:#ubuntu-release- Unapproved: corosync (artful-proposed/main) [2.4.2-3build1 => 2.4.2-3ubuntu0.17.10.1] (ubuntu-desktop, ubuntu-server)
[15:50] -queuebot:#ubuntu-release- Unapproved: pacemaker (artful-proposed/main) [1.1.16-1ubuntu1 => 1.1.16-1ubuntu2] (ubuntu-server)
[15:52] -queuebot:#ubuntu-release- Unapproved: corosync (xenial-proposed/main) [2.3.5-3ubuntu2 => 2.3.5-3ubuntu2.1] (ubuntu-desktop, ubuntu-server)
[15:53] -queuebot:#ubuntu-release- Unapproved: pacemaker (xenial-proposed/main) [1.1.14-2ubuntu1.3 => 1.1.14-2ubuntu1.4] (ubuntu-server)
[16:22] <apw> Laney, you have a couple of ADT test failures still holding it back
[16:24] -queuebot:#ubuntu-release- New source: ksmtp (bionic-proposed/primary) [17.12.2-0ubuntu1]
[16:24]  * Laney meows at apw 
[16:24] <Laney> which it?
[16:24] <apw> that lib thing you had me promote
[16:24] <Laney> mesa?
[16:26] <Laney> oh yeah it's not going in just now anyway due to mesa I don't think
[16:38] <Laney> not that I know what the issue is
[16:41] <Laney> tseliot: is this fixed by the new nvidia in NEW?
[16:42] <tseliot> Laney: what is "this"? I think I got disconnected
[16:43] <Laney> oh right, the nvidia / mesa / libglvnd stuff going on in proposed atm
[16:44] <tseliot> yes, ideally it would all land at the same time
[16:45] <Laney> think the breaks are set up so that it will
[16:46] <Laney> but nvidia-340 & 384 seem uninstallable
[16:46] <xnox> tseliot, btw. should 304 be fixed up? there is a patch, that somebody on the forums wrote to make it compile with v4.15.
[16:46] <xnox> tseliot, it does change the module license....
[16:47] <tseliot> Laney: I have changes for 340, but I was waiting for the new xserver to land first. Also, 390 will replace 384
[16:47] <Laney> okey
[16:47] <tseliot> xnox: 304 should be dropped. tjaalton filed a bug report about it
[16:47] <Laney> well mesa isn't actually trying to go in yet
[16:47] <tseliot> good thing I need to fix some stuff in nvidia first
[16:48] <tseliot> 390
[16:48] <seb128> it's annoying that this stack is not ready, it's blocking other transitions and features in proposed now :/
[16:50] <tseliot> my drivers are ready to go. I don't know what's blocking mesa, to be honest
[17:02] <apw> mesa seems to be being held because of a fair number of adt regressions
[17:04] <nacc> apw: i believe tjaalton is working on a transition, but i'm not 100%
[17:15] -queuebot:#ubuntu-release- Unapproved: horizon (xenial-proposed/main) [2:9.1.2-0ubuntu4 => 2:9.1.2-0ubuntu5] (openstack, ubuntu-server)
[17:17] <slangasek> tjaalton: fwiw processing Debian removals, s2tc is dropped because Debian bug #888430 says it's obsolete as of mesa 17.3, which we have in bionic.  I'm assuming that makes it ok to drop, but shout if I'm wrong
[17:17] <ubot5`> Debian bug 888430 in ftp.debian.org "RM: s2tc -- ROM; superseded by native s3tc support in mesa" [Normal,Open] http://bugs.debian.org/888430
[17:18] <jbicha> yay, removals
[17:28] <slangasek> infinity: was that you retrying awesome/armhf in a loop to try to get it to pass?  looks flaky/racy here, maybe time for a badtest?
[17:28] -queuebot:#ubuntu-release- Unapproved: accepted corosync [source] (artful-proposed) [2.4.2-3ubuntu0.17.10.1]
[17:30] <infinity> slangasek: Dunno about "in a loop", I may have tried it a couple of times.
[17:31] <slangasek> k :)
[17:35] -queuebot:#ubuntu-release- Unapproved: rejected pacemaker [source] (artful-proposed) [1.1.16-1ubuntu2]
[17:36] <ddstreet> sil2100 re: 16.04.4, is everything currently in the xenial upload queue waiting until march 2 before it's accepted/rejected?
[17:38] <infinity> ddstreet: No.
[17:38] <ddstreet> infinity ok so it'll proceed into -proposed as usual?  just wait there until after point release?
[17:38] <infinity> ddstreet: Things can be reviewed and accepted into -proposed, there's just a lock on releasing from -proposed to -updates.
[17:39] <ddstreet> awesome thnx!
[17:39] <slangasek> tsimonq2: ^^ speaking of which, what conclusions did you reach wrt the Lubuntu-specific SRUs for 16.04.4?
[17:41] <tsimonq2> slangasek: They can land after the point release .
[17:41] <sil2100> ddstreet: as infinity said
[17:42] <slangasek> tsimonq2: ok cool
[17:42] <flocculant> sil2100: thanks - I noticed the 16.04.3 on Saturday - but you were off doing life, so couldn't ping you :p
[17:42] <tsimonq2> Out of curiosity, what's the reasoning behind  blocking even non-seeded packages froo migrating to xenial-updaytes?
[17:43] <tsimonq2> (grr @ mobile keyboard)
[17:43] <infinity> tsimonq2: There's no reason they can't, except that migrations are a manual process, and "don't do it" is easier than "do it, but double-check all these lists and don't screw up".
[17:44] <tsimonq2> infinity: Ah, makes sense.
[17:44] <tsimonq2> Thanks.
[17:47] <sil2100> flocculant: yeah, sorry about that!
[17:48] <flocculant> sil2100: not too worried - expected at least 1 respin before Thursday - and after installing it was calling itself 16.04.4 :p
[17:50] <slangasek> fpc autopkgtest fails because it succeeds. Well job
[17:50] <flocculant> sil2100: shame the ubiquity change re keyboard layout choice wasn't in - I'm failing the lvm test for us - not that it stops me marking it ready
[17:51] <infinity> slangasek: Having a working Pascal compiler does seem like it could be qualified as a failure.
[17:52] <sil2100> flocculant: yeah, it's fixed for bionic but we didn't backport it yet indeed
[17:52] <sil2100> Maybe next point-release then
[17:52] <nacc> slangasek: could you review the updated removals in LP: #1749745? today? i'm uploading the reverse-recommends drops now, and after the bug is processed, we should be able to remove php7.1
[17:52] <ubot5`> Launchpad bug 1749745 in zoneminder (Ubuntu) "php7.2 has removed the mcrypt module" [Undecided,New] https://launchpad.net/bugs/1749745
[17:52] <flocculant> ack
[17:54] <slangasek> sergiusens: I'm triggering autopkgtests of the snapcraft in release against the maven in release, to hopefully confirm whether this failure is already present in that version; if so we should badtest it and let snapcraft migrate
[17:54] <slangasek> sergiusens: (unless this is a new test which doesn't exist at all in the release version?)
[17:55] <sergiusens> slangasek: the snapcraft that is released might not work in 18.04 as this is the release that has all the bits; I can manually check with an older version of maven on my side
[17:56] -queuebot:#ubuntu-release- Unapproved: pacemaker (artful-proposed/main) [1.1.16-1ubuntu1 => 1.1.17+really1.1.16-1ubuntu2] (ubuntu-server)
[17:56] <slashd> sil2100, ^
[17:57] <sil2100> slashd: thanks!
[17:57] <slangasek> sergiusens: well, the point of my test is to establish whether this is already broken in the release pocket, and if so allow the snapcraft to migrate because it's not a regression; your bit sounds more useful for fixing the broken autopkgtest, which is something I would leave to you
[18:00] -queuebot:#ubuntu-release- New: accepted okular [amd64] (bionic-proposed) [4:17.12.2-0ubuntu1]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [armhf] (bionic-proposed) [4:17.12.2-0ubuntu1]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [ppc64el] (bionic-proposed) [4:17.12.2-0ubuntu1]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [amd64] (bionic-proposed) [4:17.12.2-0ubuntu2]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [armhf] (bionic-proposed) [4:17.12.2-0ubuntu2]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [ppc64el] (bionic-proposed) [4:17.12.2-0ubuntu2]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [arm64] (bionic-proposed) [4:17.12.2-0ubuntu1]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [s390x] (bionic-proposed) [4:17.12.2-0ubuntu1]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [i386] (bionic-proposed) [4:17.12.2-0ubuntu2]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [i386] (bionic-proposed) [4:17.12.2-0ubuntu1]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [s390x] (bionic-proposed) [4:17.12.2-0ubuntu2]
[18:00] -queuebot:#ubuntu-release- New: accepted okular [arm64] (bionic-proposed) [4:17.12.2-0ubuntu2]
[18:07] <sergiusens> slangasek: http://autopkgtest.ubuntu.com/packages/s/snapcraft/bionic/amd64 ... "snapcraft/2.39.2+18.04" was green and "snapcraft/2.39.2+18.04.2" failed and my local debdiff between those two show no relevant affecting changes http://paste.ubuntu.com/p/CM7DfghzK4/
[18:07] -queuebot:#ubuntu-release- Unapproved: accepted pacemaker [source] (artful-proposed) [1.1.17+really1.1.16-1ubuntu2]
[18:09] -queuebot:#ubuntu-release- Unapproved: accepted corosync [source] (xenial-proposed) [2.3.5-3ubuntu2.1]
[18:10] <tjaalton> slangasek: they're right, s2tc can be dropped. the recommends on libtxc-* were left over after a merge, and I have dropped them from git
[18:11] -queuebot:#ubuntu-release- Unapproved: accepted pacemaker [source] (xenial-proposed) [1.1.14-2ubuntu1.4]
[18:14] <tjaalton> hrm, the kde autopkgtests tend to be less useful, they just say "fail" and nothing to debug other than blindly retry until they pass
[18:55] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-390 [amd64] (bionic-proposed) [390.25-0ubuntu1]
[18:55] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-390 [i386] (bionic-proposed) [390.25-0ubuntu1]
[19:10] <slashd> davecore, ^^
[19:10] <davecore> slashd: ack
[19:48] <slangasek> nacc: huh, cakephp-scripts shows up as a revdep of cakephp now, but didn't get flagged previously on LP: #1749745.  Remove also?
[19:48] <ubot5`> Launchpad bug 1749745 in gosa (Ubuntu) "php7.2 has removed the mcrypt module" [Undecided,New] https://launchpad.net/bugs/1749745
[19:48] <nacc> slangasek: oh sorry, i meant to add it, yes, i'll add a task
[19:49] <nacc> slangasek: oh wait, yes, but it's from src:cakephp
[19:50] <slangasek> nacc: oh oops I typed the wrong command - ack
[20:02] <tsimonq2> slangasek: Since Bileto seems to bypass the usual queue checks, I think it's a good idea to ask for a review; could you please do a prelim review of https://bileto.ubuntu.com/#/ticket/3113 to make sure it looks good?
[20:03] <tsimonq2> (with your AA hat on)
[20:16] <nacc> slangasek: thanks for the removals, i believe c-m also has a list of binaries that can move to universe now (it should be everything in php7.1, but i think it won't until the NBS php-mcrypt is removed. Do you want me to add tasks for that in that bug?
[20:23] <slangasek> nacc: absolutely not, c-m is its own todo list :)
[20:24] <nacc> slangasek: ok :)
[20:24] <slangasek> nacc: and fwiw I haven't removed gosa yet, I need to still decide what makes sense with its revdeps... zoneminder had a sourceful RC bug in its own right, but the gosa plugins might be releasable again if someone fixes gosa - so those might be demote-to-proposed in the near term
[20:24] <nacc> slangasek: ack, that's fine with me
[20:25] <nacc> slangasek: keeping in mind gosa-plugins-* is from src:gosa
[20:25] <nacc> slangasek: so i guess you mean just demote the whole source package?
[20:26] <slangasek> nacc: gosa-plugin-mailaddress is its own src package; etc
[20:26] <slangasek> nacc: these'ns: https://bugs.launchpad.net/ubuntu/+source/gosa/+bug/1749745/comments/9
[20:26] <ubot5`> Ubuntu bug 1749745 in gosa (Ubuntu) "php7.2 has removed the mcrypt module" [Undecided,New]
[20:27] <nacc> slangasek: ah ok, sorry, i had checked several of that list and they wer in src:gosa, so i must have missed some
[20:27] <nacc> (e.g., gosa-plugin-webdav is from src:gosa)
[20:27] <slangasek> oh
[20:28] <slangasek> well hang on then, do we have some source packages that need nuked?
[20:28] -queuebot:#ubuntu-release- Unapproved: nplan (artful-proposed/main) [0.32~17.10.1 => 0.32~17.10.2] (core)
[20:34] <slangasek> nacc: yeah, definitely some weirdness in the reverse-depends output here, some of these binaries are definitely from src:gosa and always have been so shouldn't show up in the output against src:gosa
[20:44] -queuebot:#ubuntu-release- New binary: nvidia-cuda-toolkit [ppc64el] (bionic-proposed/multiverse) [9.1.85-1] (no packageset)
[20:48] -queuebot:#ubuntu-release- New binary: nvidia-cuda-toolkit [amd64] (bionic-proposed/multiverse) [9.1.85-1] (no packageset)
[20:50] <slangasek> sergiusens: the snapcraft autopkgtest failed in the release pocket of course, but the maven test case that failed in the -proposed version *passed* in the release version
[20:52] <slangasek> sergiusens: how do you want to play this?  I can justify letting this package into the release pocket with a skiptest hint on the grounds that so much else has changed around it that the version currently in release pocket is unreleasable anyway - but I'll only do that if you agree that regressing the maven plugin (as the test regression implies) is ok
[20:59] <sergiusens> slangasek: I played with the test locally and it all works, the only environmental differences we have are that autopkgtests use a proxy. I'll keep looking into it.
[21:00] <slangasek> sergiusens: I'm glad you'll keep looking into it - in the meantime, do you think this package should be allowed through the gauntlet?
[21:00] <sergiusens> slangasek: personally, yes; this is the one where we add all that elf work to make things actually do things after built
[21:00] <slangasek> e.g. if the test passes locally, do you think it's a bad test, and maybe it's not a regression for users?
[21:01] <sergiusens> slangasek: whatever is in bionic now produces things that do not work
[21:01] <slangasek> heh
[21:01] <slangasek> sergiusens: fyi that's a trump card you can always play to get me to skip autopkgtests
[21:02] <sergiusens> I am not faking anthing here fwiw ;-)
[21:09] <slangasek> sergiusens: when you test it locally, are you using bionic-proposed as a source?  Do the snapcraft tests inherit the apt pinning autopkgtest does for -proposed, or does it try to pull all packages from -proposed?
[21:13] <sergiusens> slangasek: I do not have -proposed enabled at all; so no to everything; it was a light test in between the things I was doing. I don't mind waiting a week for this to get in (it has already been 3 months ;-) )
[21:19] <nacc> slangasek: yeah, it feels like something chnaged, but i don't know what
[21:19] <slangasek> sergiusens: I do mind it waiting another week if that results in further decay (especially as e.g. we're waiting on a working snapcraft for subiquity).  But if you're testing without -proposed, and the autopkgtest is testing with full -proposed, and it fails in -proposed, there's a chance something is about to regress in release that impacts snapcraft
[21:26] <slangasek> tsimonq2: sorry, effectively the answer is no, I can't do a prelim review
[21:27] <tsimonq2> slangasek: No problem
[21:27] <tsimonq2> Thanks
[21:30] -queuebot:#ubuntu-release- New: accepted curl [amd64] (bionic-proposed) [7.58.0-2ubuntu2]
[21:30] -queuebot:#ubuntu-release- New: accepted curl [armhf] (bionic-proposed) [7.58.0-2ubuntu2]
[21:30] -queuebot:#ubuntu-release- New: accepted curl [ppc64el] (bionic-proposed) [7.58.0-2ubuntu2]
[21:30] -queuebot:#ubuntu-release- New: accepted curl [arm64] (bionic-proposed) [7.58.0-2ubuntu2]
[21:30] -queuebot:#ubuntu-release- New: accepted curl [s390x] (bionic-proposed) [7.58.0-2ubuntu2]
[21:30] -queuebot:#ubuntu-release- New: accepted curl [i386] (bionic-proposed) [7.58.0-2ubuntu2]
[21:43] <tgm4883> Could someone take a look as to why mythtv isn't being promoted out of bionic-proposed? http://people.canonical.com/~ubuntu-archive/proposed-migration/bionic/update_excuses.html#mythtv
[21:57] <infinity> tgm4883: Because upgrading libvpx causes a bazillion things to become uninstallable.
[21:57] <infinity> (ie: you're in the middle of a transition)
[21:57] <tgm4883> ah, so it should clear itself up then eventually?
[21:58] <infinity> Seems plausible.  Not sure who, if anyone, is actively working on that particular transition right now.
[21:58] <tgm4883> ok
[21:59] <tgm4883> I just got the email that it's been in proposed for 5+ days so was worried
[22:06] <acheronuk> tjaalton: kde tests on mesa should be passed now, or about to
[22:24] -queuebot:#ubuntu-release- Unapproved: nplan (xenial-proposed/universe) [0.32~16.04.3 => 0.32~16.04.4] (no packageset)
[23:26] -queuebot:#ubuntu-release- New: rejected latte-dock [source] (bionic-proposed) [0.7.3-0ubuntu1]
[23:32] <slangasek> xnox: I am confused by your followups on LP: #1748000, Timo filed a bug requesting the package's removal and you assigned it to the kernel team
[23:32] <ubot5`> Launchpad bug 1748000 in nvidia-graphics-drivers-304 (Ubuntu) "Remove from the archive: this legacy driver is unmaintained upstream" [Critical,Triaged] https://launchpad.net/bugs/1748000
[23:33] <xnox> slangasek, there is a ftbfs in the wild, but it's best to remove the package.
[23:33] <xnox> slangasek, i was not sure what was going to happe quicker
[23:33] <xnox> slangasek, please remove it.