[00:02] <RAOF> Do we have any way of surfacing the autopkgtest failures for people's SRUs?
[00:06] <rbasak> RAOF: what are you asking for beyond what the links in http://people.canonical.com/~ubuntu-archive/pending-sru.html provide?
[00:07] <RAOF> rbasak: I'm wondering whether the uploader of those SRUs gets notified.
[00:07] <rbasak> Oh, I see.
[00:07] <RAOF> Because there are a *bunch* of SRUs that would otherwise be releasable, but which have autopkgtest regressions associated with them.
[00:07] <rbasak> The failures come from the Jenkins end, so maybe they do.
[00:07] <RAOF> And I 'aint gonna be releasing those :)
[00:08] <rbasak> RAOF: while you're looking at SRU, mind looking at syslinux-themes-debian in trusty and utopic please? It's trivial, and I'd like them in -updates before Vivid is released.
[00:08] <RAOF> rbasak: Sure!
[00:09] <rbasak> Thanks! I care more than average because it's an upgrade bug and needs to be fixed in the "from" release to have any effect. So if it's after Vivid, there will be a whole load more people affected.
[01:32] <RAOF> Well, that's cute.
[01:32] <RAOF> Someone's signed up to Launchpad with an address that replies to every email with “please click this link to prove you're not a spammer” in French.
[09:03] <tjaalton> infinity: hey, should I push lts-vivid xorg bits? libdrm and xtrans are already waiting in the queue
[11:11] <rbasak> I'm a bit confused as to why bug 1042511 didn't get a verification-needed tag when ROAF accepted it. But it's verification-done now anyway.
[11:11] <rbasak> s/ROAF/RAOF/
[12:58] <jamespage> hi release team - we're just putting rc1 of openstack kilo through testing - all updates should be uploaded by eod
[15:18] <Laney> bdmurray: Shouldn't we use a buildX version for python-apt to have it autosynced next time?
[15:18] <bdmurray> Laney: yeah, that'd make sense
[15:19] <Laney> Righto
[15:45] <infinity> tjaalton: Get it all staged, but don't push it to the queue until after release, IMO.
[15:51] <tjaalton> infinity: that's thursday next week? sounds fine
[15:52] <tjaalton> first cut is staged on canonical-x ppa already, put there by mlankhorst. mesa got updated in the meantime but rest should be fine
[16:34] <infinity> tjaalton: You can always do upgrade and stack-swap testing before you push, of course.
[16:34] <tjaalton> sure
[16:34] <infinity> tjaalton: Since, historically, Maaarten did that a few months later, it seems, and we panicked to fix it all before the point release. :P
[16:36] <tjaalton> yeah and cert team needs it quickly, skylake testing is pretty pointless without mesa, -intel even though they have the kernel already
[16:37] <tjaalton> so i'll make sure it's working properly by end of next week
[16:38] <infinity> tjaalton: Awesome, thanks.
[17:53] <ScottK> jamespage: Looking at the stack of new dependency requirements for OpenStack Kilo "Release Candidate" 1, I am left wondering how you get to RC and don't know what your dependencies are.  It would help a lot on the stack of dependency FFe's your team is filing if the FFe listed the rdepends and which of those rdepends are part of OpenStack and which ones aren't.
[18:30] <zequence> infinity: I'm going to need to refresh our meta and resping our ISO before tomorrow
[18:31] <zequence> I'm testing it now. Bug 1444535
[18:45] <zequence> infinity: I've uploaded the meta, but it needs to be okayed.
[19:20] <sil2100> infinity: hey! libgit2 is in the unapproved queue right now, I would need it in -proposed so that we can unblock the whole tranistion
[19:27] <zul> ScottK:  they are all dependencies for openstack
[19:30] <zul> ScottK:  they shouldnt affect packages outside of openstack, ie python-stevedore bump is needed otherwise openstack wont build, the oslo.* namespaces are only used by openstack as well
[19:56] <infinity> sil2100: I'll look at it.
[20:05] <sil2100> infinity: thanks o/
[20:25] <jamespage> ScottK, those are all packages under the openstack namespace upstream - so its not un-anticipated that upstream may rev minimum versions of what in effect are internal dependencies between final beta and rc
[20:28] <ScottK> jamespage: OK.  I find it surprising to modify dependency requirements post beta freeze, but every project is different.  In any case, an explicit statement that there are no non-OpenStack rdepends would be helpful.
[20:35] <jamespage> zul: ^^ please can you check and update the bug reports please - ta
[20:45] <zul> jamespage:  ack
[21:15] <infinity> zequence: I don't see your meta upload...
[21:15] <zequence> infinity: No?
[21:15] <infinity> zequence: Did you sign it? :P
[21:16] <zequence> infinity: Now that you say that, I might not have
[21:21] <zequence> infinity: Should I bump it and do a new upload?
[21:33] <zequence> infinity: Actually, I did an upload to my ppa to test it, and that went fine.
[21:33] <zequence> lp:ubuntu/ubuntustudio-meta ?
[21:45] <zequence> infinity: I'm going to need to hit the sack in a few moments. Will be around again in 6-7h. If there's anything I can do now, I'll do it, otherwise, I'll be back tomorrow. Sorry to catch this so late.
[22:28] <infinity> zequence: Sorry, wasn't watching IRC.
[22:28] <infinity> zequence: You can just sign and reupload, no need to bump the version.
[22:28] <infinity> zequence: Or I can just upload your meta for you, since I just updated it here.
[22:28] <infinity> zequence: Err, except that my update here found no changes...
[22:29] <infinity> zequence: So, now I'm unsure what you're changing.
[22:33] <infinity> zequence: Oh, I see what you did.  Yeah, I'll grab the bzr branch, refresh, and upload.
[23:00] <infinity> bdmurray: Did you never reupload update-manager with that test dep fix?
[23:14] <infinity> ScottK: Were you taking care of badgering the server team about the openstack/python vomit in the queue?  Backscroll seemed to imply you were.
[23:15] <ScottK> infinity: Taking care of is a bit strong.
[23:15] <ScottK> I was at least trying to prod them in the right direction.
[23:15] <infinity> ScottK: Prodding, badgering, potayto, potahto.