[00:29] -queuebot:#ubuntu-release- Unapproved: nvme-cli (xenial-proposed/universe) [0.5-1 => 0.5-1ubuntu0.1] (no packageset)
[06:41] <Mirv> ahoneybun: what tsimonq2 said. upload, then poke SRU team to get it forward from https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text=
[06:53] <cpaelzer> Hi, I wanted to ask if one could take a look at bug 1606940
[06:53] <ubot5`> bug 1606940 in qemu (Ubuntu Trusty) "A a single PCI read or write appears twice on the PCIe bus. This happens when using the SR-IOV feature with some PCI devices" [Medium,Fix committed] https://launchpad.net/bugs/1606940
[06:53] <cpaelzer> I tried to summarize the current state of its missing verification, but would appreciate some guidance by the release team
[06:53] <xnox> slangasek, i only see https://lists.ubuntu.com/archives/ubuntu-devel/2016-March/039274.html without scripts to rerun things.
[06:54] <cpaelzer> especially since depending on the decision that means clearing things from proposed
[06:54] <xnox> it is a mistery that $ germinate -cmain,universe output is not good enough for components-missmatches report.
[06:54]  * xnox is failing to figure out what else happens on snakefruit in between germinate and components-missmatches report runs.
[06:56] <cpaelzer> xnox: it is probably a bit like https://xkcd.com/730/
[07:02] <xnox> pitti, have you ever run components-missmatches report, outside of snakefruit infra?
[07:13] <pitti> xnox: no, I didn't
[07:13] <pitti> xnox: at some point all of this ought to be charmed up so that it can be run and developed in lxd..
[07:23] -queuebot:#ubuntu-release- Unapproved: rejected ifupdown [source] (yakkety-proposed) [0.8.13ubuntu3]
[07:24] -queuebot:#ubuntu-release- Unapproved: accepted gnome-control-center [source] (yakkety-proposed) [1:3.20.2-0ubuntu1]
[07:26] -queuebot:#ubuntu-release- Unapproved: accepted file-roller [source] (yakkety-proposed) [3.22.1-0ubuntu1]
[07:28] -queuebot:#ubuntu-release- Unapproved: fcitx (yakkety-proposed/main) [1:4.2.9.1-3 => 1:4.2.9.1-4] (input-methods, kubuntu, ubuntu-desktop) (sync)
[07:29] -queuebot:#ubuntu-release- Unapproved: accepted mate-netbook [sync] (yakkety-proposed) [1.16.1-1]
[07:42] <sil2100> Hey! Is it possible to do zesty uploads already?
[07:43] <ginggs> sil2100: see topic
[07:53] -queuebot:#ubuntu-release- Packageset: 6494 entries have been added or removed
[08:00] <apw> sil2100, not yet ... opening is not a teensy job ^^ things are progressing
[08:07] <sil2100> Thanks o/
[08:15] <xnox> slangasek, i only found this from you https://lists.ubuntu.com/archives/ubuntu-devel/2016-March/039274.html and it does not look like it has a script to re-run components-missmatches outside of snakefruit infra.
[08:16] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (yakkety-proposed) [2.16+16.10ubuntu1.1]
[08:17] <cjwatson> xnox: it runs off a sync of LP's output
[08:17] <cjwatson> xnox: which is lp:ubuntu-archive-publishing, finalize.d/20-germinate
[08:17] <cjwatson> well, scripts/cron.germinate
[08:19] <cjwatson> xnox: the $GERMINATEROOT directory that's the output of scripts/cron.germinate is the input to component-mismatches
[08:35] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.16ubuntu1]
[08:39] <xnox> and an unsplit mirror
[08:39] <pitti> apw: resuming my SRU review run from earlier, FYI
[08:41]  * xnox rsyncs ubuntu-ports on top of ubuntu
[08:42] -queuebot:#ubuntu-release- Unapproved: rejected lightdm [source] (yakkety-proposed) [1.20.0-0ubuntu1]
[08:52] <cpaelzer> pitti: if you are doing an SRU run atm could you take a look at bug 1606940?
[08:52] <ubot5`> bug 1606940 in qemu (Ubuntu Trusty) "A a single PCI read or write appears twice on the PCIe bus. This happens when using the SR-IOV feature with some PCI devices" [Medium,Fix committed] https://launchpad.net/bugs/1606940
[08:53] <pitti> cpaelzer: ack
[08:53] <cpaelzer> I asked here this morning already but that might have been too early for anyone to pick up
[08:53] -queuebot:#ubuntu-release- Unapproved: accepted mate-optimus [sync] (yakkety-proposed) [16.10.1-1]
[08:53] <pitti> one package away from being done with yakkety, will then do trusty
[08:56] -queuebot:#ubuntu-release- Unapproved: accepted fcitx [sync] (yakkety-proposed) [1:4.2.9.1-4]
[08:57] -queuebot:#ubuntu-release- Unapproved: rejected fcitx [source] (xenial-proposed) [1:4.2.9.1-1ubuntu1.16.04.1]
[08:59] <pitti> cpaelzer: if it doesn't (completely) fix the problem that's fine -- there can always be another SRU; the more important aspect is to check that it doesn't break anything else, i. e. QEMU still works on other platforms
[09:03] <xnox> getting somewhere... zesty is in the way
[09:03] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (trusty-proposed) [20101020ubuntu318.41]
[09:04] <cpaelzer> pitti: thanks - that POV gives me a chance to verify on my own - I'll quote you, do a bunch of tests and verify it then if it is ok
[09:04] <pitti> cpaelzer: I just followed up on the bug with that statement too
[09:04] <cpaelzer> pitti: perfect
[09:05] -queuebot:#ubuntu-release- Unapproved: rejected distro-info-data [source] (yakkety-proposed) [0.29ubuntu0.1]
[09:06] -queuebot:#ubuntu-release- Unapproved: rejected distro-info-data [source] (xenial-proposed) [0.28ubuntu0.2]
[09:08] <pitti> tumbleweed: sorry about https://anonscm.debian.org/git/collab-maint/distro-info-data.git/commit/?id=42b861b -- mind uploading again? (or I can do it too)
[09:08] -queuebot:#ubuntu-release- Unapproved: rejected distro-info-data [source] (trusty-proposed) [0.18ubuntu0.6]
[09:08] -queuebot:#ubuntu-release- Unapproved: rejected distro-info-data [source] (precise-proposed) [0.8ubuntu0.11]
[09:11] -queuebot:#ubuntu-release- Unapproved: distro-info-data (xenial-proposed/main) [0.28ubuntu0.1 => 0.28ubuntu0.2] (core)
[09:11] -queuebot:#ubuntu-release- Unapproved: distro-info-data (yakkety-proposed/main) [0.29 => 0.29ubuntu0.1] (core)
[09:12] <xnox> cjwatson, thank you! just had to get an unsplit dists/ mirror, and patch everything to forget that zesty is a thing, and use yakkety throughout.
[09:12] <xnox> probably could have just symlinked zesty to yakkety locally, oh well.
[09:12] <cjwatson> cool.  sorry it's complicated, but it is at least possible
[09:17] -queuebot:#ubuntu-release- Unapproved: distro-info-data (precise-proposed/main) [0.8ubuntu0.10 => 0.8ubuntu0.11] (ubuntu-server)
[09:28] <xnox> cjwatson, http://people.canonical.com/~xnox/germinate-output/builtusing/components-missmatches.svg
[09:28] <xnox> slangasek, infinity ^
[09:28] <xnox> http://people.canonical.com/~xnox/germinate-output/builtusing/components-missmatches.html
[09:30] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (yakkety-proposed) [0.29ubuntu0.1]
[09:31]  * xnox is happy
[09:31] <xnox> coffee time
[09:31] <pitti> xnox: yay, you managed to run it locally at last?
[09:32] <xnox> pitti, yeah...
[09:40] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (xenial-proposed) [0.28ubuntu0.2]
[09:43] -queuebot:#ubuntu-release- Unapproved: distro-info-data (trusty-proposed/main) [0.18ubuntu0.5 => 0.18ubuntu0.6] (core)
[09:46] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (trusty-proposed) [0.18ubuntu0.6]
[09:48] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (precise-proposed) [0.8ubuntu0.11]
[10:13] <infinity> xnox: That's a lot more stuff than the official c-m...
[10:13] <infinity> xnox: And not all built-using.
[10:13] <infinity> xnox: So, erm... Why?
[10:26] -queuebot:#ubuntu-release- Unapproved: base-files (zesty-proposed/main) [9.6ubuntu5 => 9.6ubuntu6] (core)
[10:27] <doko> thre they are ...
[10:28] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (zesty-proposed) [9.6ubuntu6]
[10:28] -queuebot:#ubuntu-release- Unapproved: binutils (zesty-proposed/main) [2.27-8ubuntu2 => 2.27-9ubuntu1] (core)
[10:28] -queuebot:#ubuntu-release- Unapproved: accepted binutils [source] (zesty-proposed) [2.27-9ubuntu1]
[10:28] <infinity> Err.
[10:28] <infinity> doko: Did you accept them?
[10:29] <infinity> doko: Cause that won't work so well. :P
[10:29] <doko> infinity: ouch
[10:29] <infinity> I did mention "I won't accept them right away". ;)
[10:29] <infinity> S'ok, I'll just retry them when I'm ready.
[10:29] <doko> ok, binutils doesn't need the updated base-files
[10:30] <infinity> Oh.  Wait.  Nothing to retry.  I'll have to generate the missing builds later.
[10:30] <infinity> I'll get there.
[10:30] <infinity> No chroots == no build records created. :)
[10:31] <apw> heh never seen that before, an empty build bit
[10:47] -queuebot:#ubuntu-release- Unapproved: debhelper (zesty-proposed/main) [10ubuntu1 => 10.2.2ubuntu1] (core)
[10:48] <pitti> ^ probably one of the earlier packages you should accept after builds are sorted out
[10:50] <infinity> pitti: Ta.
[10:50] <infinity> pitti: Say, how close are we to dropping pkg-create-dbgsyms and using the built-in dh support with a small s/deb/ddeb/ delta to avoid confusing ourselves?
[10:52] <pitti> infinity: shouldn't actually be so bad, but I haven't looked into the details of that
[10:52] <pitti> so for now this merge just keeps the old stuff
[10:52] <infinity> pitti: I kinda assumed that with that change (s/deb/ddeb/) it should kinda Just Work with current infra.
[10:52] <pitti> yeah
[10:53] <infinity> And I'm not super keen on changing the extention for us.
[10:53] <pitti> I can look into that
[10:53] <pitti> no, we can't build -dbgsym as .debs, LP will fall over
[10:53] <infinity> Well, aside from infra exploding, I think Debian was wrong anyway.
[10:54] <infinity> And keeping that delta forever is pretty much harmless.
[10:54] <infinity> And gives us an excuse to have the package soft-blacklisted from autosync.
[10:54] <pitti> ok, I'll do some experiments to at least get a feeling how different the dh approach is
[10:54] <infinity> Which isn't a bad thing for toolchain.
[10:54] <pitti> our "don't install upstream changelogs" delta is also fairly permanent anyway
[10:54] <infinity> The dh approach was heavily based on pkg-create, so I *hope* it's a drop-in replacement.
[10:54] <pitti> IMHO we should stop doing that in Debina as well, it's just pointlessly ballooning packages
[10:55] <infinity> People asked me about it a lot as it was happening, and I assume they pinged you too.
[10:55] <infinity> But I haven't looked closely at the final product.
[10:56] <infinity> Fingers crossed.
[11:02] -queuebot:#ubuntu-release- Unapproved: vmware-nsx (xenial-proposed/universe) [8.0.0-0ubuntu0.16.04.3 => 8.0.0-0ubuntu0.16.04.4] (no packageset)
[11:03] <jamespage> bdmurray, hello - could you take a look at ^^ vmware-nsx upload - it fixes the FTBFS that bug 1574610 tripped over due to the concurrenct neutron SRU going through (which I missed in pre-upload testing)
[11:03] <ubot5`> bug 1574610 in vmware-nsx (Ubuntu Xenial) "[DVSPlugin]Missing table nsxv_subnet_ext_attributes" [High,Fix committed] https://launchpad.net/bugs/1574610
[11:03] <Kamilion> urgh. trying to run pip3 freeze results in pip._vendor.pkg_resources.RequirementParseError: Invalid requirement, parse error at "'-lxc==0.'"
[11:03] <jamespage> ftbfs bug 1634450
[11:03] <ubot5`> bug 1634450 in vmware-nsx (Ubuntu Xenial) "ftbfs in xenial proposed" [High,Triaged] https://launchpad.net/bugs/1634450
[11:07] <pitti> infinity: there's actually some stuff left, like checking grep -qs '^Build-Debug-Symbols: yes$' /CurrentlyBuilding, disabling for PPA builds, etc. -- not sure how much of that is still actually relevant, though
[11:07] <pitti> infinity: I suppose we can replace NO_PKG_MANGLE=1 with ENABLE_DBGSYM=0 though
[11:08] <apw> we still have a ticky for that in the PPAs so i assume we need that
[11:08] <Kamilion> http://paste.ubuntu.com/23343298/ :/
[11:08] <pitti> but I can port just that to dh_strip
[11:08] <pitti> still easier than keeping the entire pkg-create-dbgsym
[11:12] <infinity> pitti: NO_PKG_MANGLE is overloaded anyway.
[11:16] <clivejo> where do the SRU team hang out?
[11:17] <infinity> clivejo: On the beach in Mexico.
[11:17] <infinity> clivejo: (Or here)
[11:17] <clivejo> that would be nice!
[11:18] <clivejo> I need to get an SRU into xenial / Yakkety
[11:18] <infinity> clivejo: Enough overlap between ubuntu-sru, ubuntu-release, and ubuntu-archive, that we kinda just shove all three in this channel.
[11:18] <clivejo> but Im bit confused as to how to do it
[11:18] <apw> clivejo, tells us what you have done so far
[11:18] <clivejo> usually we patch in +1 (dev), but we kinda in limbo with that at the moment
[11:18] <infinity> clivejo: File bugs.  Make sure bugs contain SRU boilerplate about rationale, test cases, etc.  Reference bugs in changelog.  Upload to xenial.
[11:19] <clivejo> LP 1633692
[11:19] <ubot5`> Launchpad bug 1633692 in plasma-discover (Ubuntu Xenial) "missing depends on ubuntu-release-upgrader-qt - breaks GUI upgrades to yakkety" [Critical,Confirmed] https://launchpad.net/bugs/1633692
[11:20] <infinity> clivejo: So, that all looks in order.  You're just missing the "upload it" bit.
[11:20] <infinity> clivejo: Or if you can't, "find a sponsor".
[11:20] <clivejo> I think I can
[11:20] <clivejo> but is the version numbering correctr
[11:20] <clivejo> 1.1?
[11:20] <infinity> Yup.
[11:20] <apw> pretend there is a devel update coming :)
[11:21] <clivejo> and I just dput to ubuntu and LP assigns it to the correct queue?
[11:21] <infinity> Yup.
[11:21] <infinity> clivejo: Remember how all your yakkety uploads during devel went to yakkety-proposed?
[11:21] <clivejo> ah thanks, just wanted to check!
[11:21] <infinity> Well, devel isn't special. :P
[11:22] <infinity> We rewrite $dist to $dist-proposed for all releases.
[11:22] <infinity> So it just magically works.
[11:22] <clivejo> infinity: Ive only had upload rights about a week now, but I learned a while ago not to assume things!
[11:22] <clivejo> always best to ask and make sure!
[11:23] <infinity> clivejo: Yeahp, ask away.
[11:23] <clivejo> can you guys poke it on?
[11:24] <infinity> pitti might be game for poking it.  He's been SRU queue mangling today.
[11:24] <clivejo> this is affecting a lot of users who want to upgrade to yakkety yak
[11:25] <xnox> infinity, this is my botched up run against yakkety. and it's probably includes touch seed, but official c-m runs do not.
[11:25] -queuebot:#ubuntu-release- Unapproved: plasma-discover (xenial-proposed/universe) [5.6.2-1ubuntu1 => 5.6.2-1ubuntu1.1] (kubuntu)
[11:26] <clivejo> ^^ pitti : would you mind trying to encourage that through the system please
[11:26] <clivejo> thanks infinity
[11:28] <pitti> clivejo: yep, will look after lunch
[11:28] <clivejo> thanking you kindly
[11:28] <clivejo> so in YY, the current version is 5.7.5-0ubuntu2, so my SRU will be 2.1?
[11:30] <apw> clivejo, imagine that the ubuntu2 was in ZZ as well, then you'd have alredy uploaded an ubuntu3 there, and be using 2.1 in yakkety to keep under it
[11:31] <clivejo> I guess I have a bad imagination!
[11:32] <clivejo> does the new ZZ archive just get a copy of everything?
[11:32] <acheronuk> clivejo: https://launchpad.net/ubuntu/+source/plasma-discover
[11:33] <acheronuk> The Zesty Zapus (pre-release freeze) 5.7.5-0ubuntu2
[11:33] <xnox> weirdly infinity, http://people.canonical.com/~xnox/germinate-output/builtusing/components-missmatches.svg this looks fine
[11:33] <xnox> no?
[11:33] <apw> clivejo, it already has indeed: https://launchpad.net/ubuntu/+source/plasma-discover
[11:34] <acheronuk> snap
[11:34] <clivejo> oh so I can upload ubuntu3 to zz?
[11:34] <apw> clivejo, you can expect the release-team to sort out the missmatch that you doing the SRU will cause, or ask you for help
[11:35] <clivejo> if I could upload ubuntu3 to ZZ that would sort out these problems in my head!
[11:35] <apw> clivejo, you can't yet, and the 2.1 should get copied forward too in the mid-term
[11:36] <infinity> xnox: Compare it to the ubuntu-archive version.  There are some new nodes there that aren't built-using.  Curious if you fixed a bug or introduced one. :P
[11:36] <apw> clivejo, but pretend you have and behave that way
[11:36] <clivejo> ok, thanks for helping me get my head around that!
[11:37] <apw> clivejo, these few days are fun times
[11:37] <clivejo> uploading 2.1 to yakkety just felt wrong for some reason!
[11:37] <infinity> FSVO "fun".
[11:37] <apw> infinity, some rather twisted and dark version indeed
[11:37] <infinity> Well, I have fun doing openings, actually.
[11:38] <infinity> I just don't have fun with all the out-of-band AWTY prodding I get while doing them.
[11:38] <apw> see my previous statement
[11:38] <infinity> Also, someone needs to mail me some bacon and eggs.
[11:38] <apw> amazon now should do breakfast
[11:39] <apw> (other delivery services are available :))
[11:39] <sarnold> or 2am tacos
[11:41] <infinity> Mmm, tacos.
[11:42] <infinity> doko: Hrm, no libasan on s390x?  Curious.
[11:43] <doko> see src/libsanitizer/configure.tgt
[11:45] <infinity> doko: I was expecting that to answer the why. ;)
[11:45] <infinity> But I guess it's just "it's not ported".
[11:50] <xnox> e.g. cm-super is needed because doxygen-latex depends on cm-super-minimal, and doxygen-latex is now required because imagemagick-doc is in main and it has Built-Using doxygen. The newly added Built-Using support now makes all binary packages that are produced by Built-Using; src, to be required in main.
[11:51] <xnox> however, i think i should be able to make germinate slightly better, and keep "Built-Using" transversal chain in the outputs somehow.
[11:53] <infinity> xnox: I'd honestly prefer it if we were just promoting the source, not all the binaries.
[11:53] <infinity> (which will then rescue -dev packages as well)
[11:53] <xnox> that's what happens now.
[11:54] <xnox> (in the current production c-m)
[11:54] <xnox> however, steve says that it doesn't tell anybody why that source is being promoted.
[11:54] <infinity> But I guess I'm curious where, for instance, the gcc-6 -> quilt thing popped up, when the archive version doesn't show that node.
[11:54] <xnox> right
[11:54] <doko> gcc-6-source depends on it
[11:54] <infinity> xnox: Yes, he's right.  It didn't tell us why.  That doesn't mean we need to promote more things, we just need a why.
[11:55] <xnox> ok
[11:55] <doko> but gcc-6-source should be only used as a b-d for the cross compilers ...
[11:55] <infinity> doko: Ahh, indeed.
[11:55] <infinity> doko: That's xnox's "promote all the things" at work here then.
[11:55] <xnox> infinity, so, would like if c-m said "Rescued from $foo (Built-Using $bar)" ?
[11:55] <infinity> So, yeah, not ideal.
[11:56] <xnox> infinity, so, would you like if c-m said "Rescued from $foo (Built-Using $bar)" ?
[11:56] <infinity> xnox: Something like that, yes.
[11:56] <xnox> cause this thing is too much (the my proposed stuff)
[11:56] <xnox> ok.
[11:56] <infinity> xnox: I don't want more binaries in main, I just want to know why I'm being asked to pomote the things we have.
[11:56] <xnox> ack.
[11:57] <infinity> (And to fix the bug where this is post-facto)
[11:57] <infinity> But I assume that's included in this branch.
[12:01] <bdmurray> jamespage: looking
[12:05] <jamespage> bdmurray, ta
[12:06] -queuebot:#ubuntu-release- Unapproved: accepted vmware-nsx [source] (xenial-proposed) [8.0.0-0ubuntu0.16.04.4]
[12:22] <pitti> clivejo: no corresponding SRU to y?
[12:23] <pitti> clivejo: accepted into x-proposed, but releasing will require fixing this in z (and presumably y too, as you also don't want to break y→ z upgrades)
[12:24] -queuebot:#ubuntu-release- Unapproved: accepted plasma-discover [source] (xenial-proposed) [5.6.2-1ubuntu1.1]
[12:30] <apw> pitti, he was supposed to be doing the y upload, which should get copied forward
[12:33] <pitti> http://archive.ubuntu.com/ubuntu/dists/zesty/ → I'll build autopkgtest containers/images
[12:33] <infinity> pitti: Yay.
[12:33] <infinity> pitti: Also, upgrade all your computers.  And tell a friend.
[12:34] <pitti> get ALL THE GOODNESS in zesty!
[12:34] <infinity> If I'm missing an interim step of "obtain friends", do that first.
[12:35] <pitti> I used to have some, until I started suggesting upgrading to development releases
[12:35] <infinity> They weren't very good friends, then.
[12:35] <infinity> If you can't handle me in development, you don't deserve me when I'm stable.
[12:35] <pitti> that wasn't part of your requirements either
[12:36] <pitti> there, distro-info-data is now reflecting reality
[12:36] <infinity> Reality is overrated.
[12:41] -queuebot:#ubuntu-release- Unapproved: ifupdown (yakkety-proposed/main) [0.8.13ubuntu2 => 0.8.13ubuntu3] (core)
[12:46] -queuebot:#ubuntu-release- Unapproved: webbrowser-app (yakkety-proposed/main) [0.23+16.10.20160928-0ubuntu1 => 0.23+16.10.20161018-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[13:03] <clivejo> pitti: yes, I intend to do yy as well, just wanted to clear up some confusion over version numbers in Yakkety
[14:01] <pitti> infinity: hm, 2 hours into staring/hacking at this, this is a lot more complex than just changing .deb to .ddeb in some place (right now I'm stuck in wondering where the hell dh calls dpkg-distaddfile or writes  debian/files -- it apparently does neither)
[14:02] <tumbleweed> heh, pitti, the one date I didn't check
[14:25] <xnox> infinity, how about this now http://people.canonical.com/~xnox/germinate-output/builtusing2/components-missmatches.html
[14:27] <xnox> needs spaces around ','
[14:49] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.16ubuntu1 => 2.16ubuntu2] (desktop-core, ubuntu-server)
[14:52]  * apw looks at that snapd
[14:55] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.16ubuntu2]
[14:58] <LocutusOfBorg> question wrt cmake
[14:58] <LocutusOfBorg>     - debian/patches/ubuntu_boost-multiarch.patch
[14:58] <LocutusOfBorg>       find boost and python in multiarch path
[14:58] <LocutusOfBorg>       this is a candidate for removal but needs rdepend testing
[14:58] <LocutusOfBorg> do you think it is *now* a good time to test?
[14:59] -queuebot:#ubuntu-release- Unapproved: fftw3 (zesty-proposed/main) [3.3.4-2ubuntu1 => 3.3.5-1] (desktop-core, ubuntu-server) (sync)
[14:59] -queuebot:#ubuntu-release- Unapproved: pango1.0 (zesty-proposed/main) [1.40.1-1ubuntu1 => 1.40.3-2] (core) (sync)
[14:59] -queuebot:#ubuntu-release- Unapproved: bbpager (zesty-proposed/universe) [0.4.7-3ubuntu3 => 0.4.7-5] (no packageset) (sync)
[15:04] <pitti> all autopkgtest workers now have zesty images and are ready
[15:05]  * apw assumes we need to get zesty-proposed pre-populated before any of that gets accepted
[15:05] <pitti> you mean copying the old stuff from yakkety-proposed?
[15:05] <apw> right
[15:06] <pitti> infinity usually does that, I suppose he has some script for it
[15:06] <apw> (more of a statement of my belief than any desire to accept them)
[15:06] <pitti> but I'm still seeding the zesty autopkgtest swift container with previous PASSes  from yakkety so that we get proper regression detection across the y→ z boundary; that'll still take a day or so
[15:10] <infinity> apw: Indeed, nothing should be accepted.
[15:10] <wgrant> pitti: What's the slowest bit of that process?
[15:10] <wgrant> I hope not scalingstack dodginess :)
[15:10] <pitti> wgrant: no, not at all; it's just my braindead script which needs optimizing
[15:11] <wgrant> pitti: Oh just posting things to swift serially?
[15:11] <wgrant> Heh
[15:11] <pitti> wgrant: basically I'm iterating over all yakkety results in swift, download results.tar, check if it's a PASS; if so, copy it and go on to the next package
[15:11] <wgrant> Right, makes sense.
[15:11] <pitti> wgrant: yeah, this is completely stupid; need to sit down and do this properly (using the database that I now have and use a permanent connection, and write it in Python)
[15:12] <pitti> I just didn't get to it as we usually took several days of prep anyway, and it only needs to run twice a year
[15:12] <wgrant> But bash scripts using eventually consistent blob stores as a database are web scale.
[15:13] <cjwatson> So is /dev/null
[15:15] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-44.64] (core, kernel)
[15:16] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-44.64~14.04.1] (kernel)
[15:19] <infinity> cjwatson: nullsql?
[15:19] <sarnold> quick! to the VCs!
[15:19]  * wgrant prepares another new scalingstack arm64 kernel...
[15:20] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-44.64~14.04.1]
[15:20] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-44.64]
[15:55] -queuebot:#ubuntu-release- Unapproved: mistral (zesty-proposed/universe) [3.0.0-1 => 3.0.0-1ubuntu1] (no packageset)
[16:03] -queuebot:#ubuntu-release- Unapproved: mistral (yakkety-proposed/universe) [3.0.0-1 => 3.0.0-1ubuntu0.16.10.1] (no packageset)
[16:08] -queuebot:#ubuntu-release- Unapproved: mistral (xenial-proposed/universe) [2.0.0-1 => 2.0.0-1ubuntu1] (no packageset)
[17:09] -queuebot:#ubuntu-release- New binary: linux-signed-lts-trusty [amd64] (precise-proposed/main) [3.13.0-99.146~precise1] (kernel)
[17:20] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-trusty [amd64] (precise-proposed) [3.13.0-99.146~precise1]
[17:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-image (yakkety-proposed/universe) [0.7ubuntu1 => 0.8+16.10ubuntu2] (no packageset)
[17:49] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (yakkety-proposed/main) [0.125ubuntu6 => 0.125ubuntu6.1] (core)
[18:30] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.16ubuntu2 => 2.16ubuntu3] (desktop-core, ubuntu-server)
[18:31] -queuebot:#ubuntu-release- Unapproved: snapd (yakkety-proposed/main) [2.16+16.10ubuntu1.1 => 2.16+16.10ubuntu1.2] (desktop-core, ubuntu-server)
[20:17] -queuebot:#ubuntu-release- Unapproved: nova (xenial-proposed/main) [2:13.1.1-0ubuntu1.1 => 2:13.1.2-0ubuntu2] (openstack, ubuntu-server)
[20:18] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (yakkety-proposed) [2.16+16.10ubuntu1.2]
[20:20] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.16ubuntu3]
[20:24] <pitti> infinity: FTR, I rewrote the tool to copy the latest successful test result of every package/arch into the new zesty swift container; it shouldn't take multiple days now, but still a few hours
[20:24] <pitti> please don't open the floodgates until then, as otherwise we can't detect regressions from y to z
[21:02] <clivejo> pitti: did you look at that plasma-discover package ?
[21:14] -queuebot:#ubuntu-release- Unapproved: plasma-discover (yakkety-proposed/universe) [5.7.5-0ubuntu2 => 5.7.5-0ubuntu2.1] (kubuntu)
[21:14] <clivejo> ^^ pitti: Thats the yakkety "fix", but xenial is the most important one as currently GUI folks cant upgrade
[21:22] <pitti> clivejo: I did, and told you this afternoon :)
[21:22] <pitti> you should also have gotten an ACCEPTED mail
[21:24] <clivejo> is there anyway to fast track it?
[21:25] <pitti> clivejo: fix it in y and z, and verify it quickly, then we can
[21:27] <clivejo> but it wont affect yy until April 2017
[21:28] <infinity> clivejo: And you'll forget about it until April if you don't fix it now.
[21:28] <infinity> clivejo: That's why we have the rule that fixes must exist in later releases first.
[21:29] <infinity> (Unless not relevant to them)
[21:29] <clivejo> how do I fix it in zz?
[21:29]  * infinity finds all sorts of NBS in yakkety-proposed and goes tidying.
[21:30] <infinity> clivejo: Upload.
[21:30] <clivejo> is the archive open?
[21:30] <infinity> If it's in the queue, that's good enough.
[21:30] <infinity> The queue is.
[21:30] <clivejo> oh, didnt know that
[21:30] <clivejo> was waiting on an email to say it was open for business!
[21:30] <infinity> It's open for light bartering.
[21:31] <infinity> Not quite business yet.
[21:34] <clivejo> I see
[21:54] -queuebot:#ubuntu-release- New sync: boost1.62 (zesty-proposed/primary) [1.62.0+dfsg-1]
[22:27] -queuebot:#ubuntu-release- Unapproved: plasma-discover (zesty-proposed/universe) [5.7.5-0ubuntu2 => 5.7.5-0ubuntu3] (kubuntu)