[08:04] <pitti> buenos días amigos!
[08:18] <bdmurray> mvo: there are many snapd uploads in the yakkety queue, which ones can I reject?
[08:19] <ginggs> morning pitti!
[08:34] <smoser> pitti, you have a minute ?
[08:42] <slangasek> smoser: he's scratching his head at lp apis at the moment
[09:12] <pitti> smoser: sure, where are you?
[10:12] <mvo> bdmurray: hi, thanks for looking at the snapd yakkety queue. please reject all of them except for 2.17.1+16.10ubuntu1 (from 2016-12-06)
[10:20] <Laney> pitti: do you know if basic_reject()ing an item puts it back in the queue in the order of rejection?
[10:21]  * Laney is wondering about a script to move some requests to the front ...
[10:23] <pitti> Laney: did you see the bug I filed this morning? I discussed prioritization of "slow" packages like glibc or perl with infinity yesterday
[10:23] <Laney> not yet
[10:23] <pitti> bug 1647948
[10:24] <pitti> Laney: I *believe* rejecting an item doesn't fundamentally change its order in the queue
[10:24] <pitti> Laney: also, you break the transactional handling with that (reject and putting it back)
[10:24] <pitti> (but if that's a manual script that's probably not much of a concern)
[10:26] <Laney> oh FFS offlineimap
[10:26] <Laney> if I suspend while it's running it just hangs forever
[10:26] <Laney> -> no new emalis
[10:57] <nacc> is the autopkgtest queue length expected right now? maybe that was the glibc discussion earlier?
[11:32] <pitti> nacc: yep, glibc triggers three metric tons of tests (basically all of them)
[11:32] <pitti> nacc: you can see the contents of the queue on /running
[11:32] <nacc> pitti: yeah, i was looking at it now, thanks!
[11:33] <Laney> From RabbitMQ release 2.7.0, messages are always held in the queue in publication order, even in the presence of requeueing or channel closure
[11:33] <pitti> Laney: hm, I still see some lopsiding towards i386
[11:34] <pitti> anyway, lunch :)
[11:34] <Laney> pitti: a bit of skew is to be expected with random
[11:37] <shadeslayer> chrisccoulson: hey, could you please update http://bazaar.launchpad.net/~mozillateam/firefox/firefox.yakkety/view/head:/debian/changelog with update to yakkety?
[11:37] <shadeslayer> seems to be lagging behind what's in the archive
[12:55] <shadeslayer> chrisccoulson: and perhaps drop hardening-wrapper from thunderbird too like it was done for firefo
[12:55] <shadeslayer> *firefox
[13:13] <zobel> who is maintaining https://cloud-images.ubuntu.com/locator/ ?
[13:14] <Odd_Bloke> zobel: o/
[13:16] <Odd_Bloke> zobel: In case I don't respond (I'm at a sprint ATM), bugs for it are tracked at https://bugs.launchpad.net/cloud-images/+filebug :)
[15:08] <cyphermox> pitti: https://code.launchpad.net/~netplan-developers/netplan/+git/netplan/+merge/312682
[15:09] <cyphermox> and https://code.launchpad.net/~netplan-developers/netplan/+git/netplan/+merge/312683
[15:20] <xnox> infinity, the day has come, when i need to rebuild upstart.... and it fails its tests.....
[15:20] <xnox> like you told me so
[15:20] <infinity> xnox: I sure did.
[15:20] <infinity> xnox: Enjoy.
[15:21] <infinity> xnox: The best part is that when you fix it, it'll be fixed on s390x too, and we can undo all the hacks and removals that I told people they shouldn't do. :P
[15:21] <infinity> *cough*slangasek*cough*
[15:22] <doko> and libnih?
[15:22] <infinity> nih was never a problem.
[15:25] <xnox> tedg, what's left to port ubuntu-app-launch to systemd?
[15:25] <xnox> and does that need upstart/systemd to launch legacy apps at all?
[15:26] <tedg> xnox: tests and code reviews
[15:26] <tedg> xnox: Yes, it launches legacy apps under systemd as well
[15:33] <doko> infinity: http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-zesty.html ftbfs everywhere
[15:35] <infinity> doko: I assume that uses a test toolchain?
[15:36] <doko> infinity: no, regular archive test rebuild
[15:36] <infinity> doko: Oh, no.  Derp.  Just doesn't have the ppc build fix in that version of glibc.  Brain fart.  Ignore me.
[15:36] <doko> and we removed the one in yakkety-proposed, because it failed to build
[15:37] <shadeslayer> chrisccoulson: oh and thunderbird doesn't seem to have a zesty branch
[15:38] <infinity> So many new pep8 failures...
[16:14] <dims> xnox : ping about https://bugs.launchpad.net/lazr.authentication/+bug/1609128 we had to pin some stuff in openstack as well since latest pkgs are not on pypi. Do you know who can help?
[16:16] <dims> cjwatson : perhaps you may know?
[16:24] <xnox> dims, i do not believe i can release that on pypi. Maybe barry or cjwatson or wgrant
[16:24] <dims> ah thanks xnox . cjwatson wgrant pretty please :)
[16:24] <xnox> tedg, where is it?
[16:25] <xnox> tedg, i like want to upload it into zesty right now.
[16:25] <xnox> tedg, and purge src:upstart from zesty asap
[16:25] <xnox> tedg, or i'm pondering to kick off unity8 session off desktop images
[16:26] <tedg> xnox: It's a secret :-P
[16:26] <tedg> xnox: It doesn't drop Upstart yet, it has both and chooses systemd if available.
[16:26] <tedg> xnox: Wanted to land that first, let it settle and then remove Upstart.
[16:26] <xnox> aha.
[16:26] <xnox> no.
[16:27] <tedg> xnox: Oh, it doesn't build on Zesty right now, need to fix the Google Mock stuff :-(
[16:27]  * tedg waves fist at Google Mock
[16:28] <xnox> tedg, i think you want to wave fist at cmake-extras, and thus have your own copy of google mock in tree. no?
[16:29] <tedg> xnox: I think that cmake-extras has been updated and I just need to match. A TODO more than a problem.
[16:31] <xnox> tedg, there are branch conflicts
[16:32] <tedg> xnox: Did you get all the branches? https://bileto.ubuntu.com/#/ticket/2105
[16:33]  * tedg rebuilds that silo
[16:33] <xnox> right
[16:33] <xnox> tedg, why do you target xenial?
[16:34] <xnox> tedg, you should land this in zesty now, continue to iterate, and land in xenial once the kinks are ironed out.
[16:34] <xnox> tedg, you totally should be using per-series branches here, and diverge zesty from xenial for now.
[16:34] <tedg> xnox: We're doing this work for the U8 session snap as well, that needs it. That snap is built from Xenial.
[16:35] <xnox> tedg, time and priority wise, not so much.
[16:35] <xnox> tedg, zesty should not have src:upstart yesterday. xenial will have upstart forever.
[16:36] <tedg> xnox: Heh, well, depends on how you look at it :-) Priority for me is the U8 snap.
[16:36] <xnox> tedg, shall i drop u8 session from zesty-desktop-amd64.iso then?
[16:36] <tedg> And zesty will still have Upstart, just not on the iso.
[16:36] <xnox> tedg, no.
[16:36] <xnox> tedg, it will not have src:upstart
[16:37] <tedg> xnox: I'm skeptical but would love to see you accomplish that.
[16:37] <xnox> $ cat debian/upstart-xsessions
[16:37] <xnox> # xsessions listed below are run inside an Upstart user session.
[16:37] <xnox> unity8-x11
[16:37] <xnox> unity8-mir
[16:37] <xnox> in zesty
[16:37] <xnox> all other sessions moved off upstart.
[16:37] <tedg> xnox: Upstart is used by the greeters and some of the other flavors that start indicators.
[16:37] <xnox> there are no clicks pre-installed, and those don't make sense on desktop u8 anyway.
[16:38] <seb128> tedg, I think pitti fixed the greeter
[16:38] <pitti> the branch landed, but it's stuck on ubuntu-greeter having broken tests due to some HiDPI changes
[16:38] <xnox> tedg, other flavours did not have upstart seeded, thus they reverted back to non-upstart session long time ago.
[16:38] <pitti> robert was looking into this
[16:38] <tedg> Clicks don't have any relation to Upstart.
[16:38] <pitti> tedg: ubuntu-app-launch?
[16:38] <pitti> (link of clicks to upstart)
[16:38] <tedg> The UAL that runs systemd will run Clicks under systemd
[16:39] <xnox> tedg, well, my point is that on u8 desktop session today, only apps ubuntu-app-launch is used is to launch legacy apps, and from my point of view, it can just exec those directly =)
[16:39] <tedg> But I imagine that'll be the next backend to get dropped.
[16:39] <xnox> tedg, i hope to not have src:click in zesty either.
[16:39] <xnox> tedg, all of bileto will have to have separate branches for xesty-overlay vs zesty.
[16:40]  * tedg giggles at xesty overlay
[16:40] <tedg> xnox: You're welcome to fight that battle, I am not.
[16:41] <xnox> tedg, i don't need to find anything =) i will just break zesty seeds, and be done with it.
[16:41] <xnox> *fight
[16:47] <slangasek> "<infinity> nih was never a problem." <-- heh.
[16:49] <dobey> xnox, tedg: i'm not sure how much work it is, but it's probably feasible to get rid of click from zesty, and also thusly get rid of click support in xenial+overlay for the unity8 snap too
[18:02] <petn-randall> Hi, were would I find the packaging VCS to rng-tools? I plan on introducing rng-tools5 to Debian again, and I'd like to inherit the VCS history to retain the contributions of the Ubuntu maintainers.
[20:39] <tyhicks> @pilot in
[21:12] <lutostag> anybody know how I would install golang-1.7 in 16.10 and get a 'go' executable?
[21:12] <tianon> either via src:golang-defaults (ie, "golang"/"golang-go") or via PATH
[21:13] <tianon> export PATH=/usr/lib/go-1.7/bin:$PATH
[21:14] <lutostag> tianon: perfect, thanks!
[21:14] <tianon> :)
[21:16] <chiluk> nacc can you sponsor https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1634304  ?
[21:17] <chiluk> actually can anyone sponsor https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1634304 for me please?
[21:53] <loladiro> I vaguely remember a discussion somewhere about the graphics drivers dynamically linking LLVM on Ubuntu. I keep seeing applications be bitten by this, so I wanted to add my strong support to undoing that and linking LLVM statically again. Unfortunately, I haven’t been able to find that issue. Anybody have a hunch where that would have been?
[22:06] <tyhicks> chiluk: I'll have a look (I'm patch piloting right now)
[22:06] <chiluk> thanks tyhicks.
[22:07] <chiluk> tyhicks: what's the process when a package sources are the same accross two releases?
[22:07] <chiluk> do you just end up uploading the newest one and sync back to the older one?
[22:07] <chiluk> tyhicks in this case zesty and yakkety are the same source base and both need the change.
[22:08] <chiluk> I really don't want to fork the versioning for yakkety.
[22:08] <tyhicks> chiluk: you'd apply the same debdiff to both except that yakkety's version would be 1:1.3.2-3ubuntu3.1 and zesty's would be 1:1.3.2-3ubuntu4
[22:09] <chiluk> tyhicks: see that seems strange to me.
[22:09] <tyhicks> chiluk: how come?
[22:09] <chiluk> tyhicks because now you have the same sources with two different versions.
[22:09] <tyhicks> chiluk: but the resulting binary packages are built against different build-depends
[22:10] <chiluk> true..
[22:10] <chiluk> so there's no way to keep the versions the same accross the two releases?
[22:11] <tyhicks> chiluk: no because you want a machine upgrading from yakkety to zesty to upgrade to the zesty version that was built against zesty build-depends
[22:12] <tyhicks> (or maybe zesty enables some better compiler hardening options)
[22:13] <chiluk> yeah I get your point.
[22:14] <chiluk> didn't think about the upgrades possibly being an issue with the same versioning.
[22:16] <tyhicks> chiluk: mind if I adjust the versioning myself in the zesty+yakkety debdiff as I upload to zesty and yakkety?
[22:16] <tyhicks> (there's no sense in having you attach new debdiffs for that)
[22:44] <tyhicks> chiluk: your debdiffs look great but I have one question about the upstream patch
[22:44] <chiluk> shoot
[22:45] <tyhicks> chiluk: have any idea why the added comment says "default to amd64" but then it defaults to i386? https://github.com/virt-manager/virt-manager/blob/master/virtinst/urlfetcher.py#L1110
[22:45] <chiluk> yeah tyhicks have at the versioning change.. there's no sense in uploading a new debdiffaltogether
[22:46] <chiluk> tyhicks I'm really not sure.
[22:46] <chiluk> I found that peculiar as well.
[22:46] <chiluk> what I do know though is I tested the fix on yakkety as well as xenial
[22:46] <chiluk> and it fixed things in both cases.
[22:47] <chiluk> this was pretty much a straight cherry-pick
[22:47] <tyhicks> chiluk: ok, I left a question in the upstream PR but will proceed with sponsoring
[22:47] <tyhicks> chiluk: nice debdiffs!
[22:48] <chiluk> tyhicks: since I have you in the mood https://wiki.ubuntu.com/chiluk/CoreDevApplication
[22:48] <chiluk> ;)
[22:48] <tyhicks> chiluk: I mean cmon... they aren't THAT nice
[22:48] <chiluk> ouch.
[22:48] <tyhicks> chiluk: just kidding, I'm happy to leave a nice comment :)
[22:48] <chiluk> tyhicks you mean endorsement
[22:49] <tyhicks> yes
[22:49] <chiluk> I'm going to try to get through the process before too long.
[22:50] <tyhicks> you shouldn't have any problems
[23:12] <tyhicks> chiluk: done (uploads sponsored) and done (coredev endorsement)!
[23:13] <chiluk> thanks tyhicks.. now to find an sru sponsor.