[06:12] <slangasek> cjwatson: yeah, and cady's yakkety chroot has wrong sources, so I can't actually investigate it there... I have an RT open
[09:09] <Trevinho> infinity: hey, please once you're here could you consider promoting unity/compiz and friends from xenial proposed to updates? It's quite important for us and OEM to have that in the .1 image.
[09:15] <infinity> Trevinho: It's on my radar.
[09:17] <Laney> Unity, descend to -10 feet
[09:18] <Trevinho> infinity: thanks
[09:36] <seb128> unity-settings-daemon would be good to get as well
[10:21] <infinity> seb128: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1571640 seems to still be in limbo?
[10:21] <seb128> infinity, the corresponding greeter change didn't land so it's basically a no-op, emiting a signal nobody uses
[10:22] <seb128> I can mark it verification-done on the basis that it doesn't create regressions
[10:23] <infinity> seb128: WFM.
[10:24] <seb128> done
[10:35] <xnox> infinity, hello =) would you release a few SRUs for me please? =)
[10:35] <xnox> bug #1592990
[10:35] <xnox> bug #1595495
[10:36] <infinity> xnox: Yeah, yeah.
[10:36] <infinity> xnox: You verified it 4 minutes ago, patience.
[10:36] <xnox> and then I would like to upload ubiquity to fix two bugs in yakkety, and same into xenial:
[10:36] <xnox> bug #1584417
[10:36] <xnox> and
[10:36] <xnox> bug #1603926
[10:36] <xnox> would that be ok?
[10:36] <xnox> let me paste the debdiff
[10:37] <xnox> http://paste.ubuntu.com/19884627/
[10:37] <xnox> infinity, thank you sir =)
[10:38] <infinity> xnox: If you're doing ubiquity, could you help verify the console-setup in proposed before doing a source refresh?
[10:40] <infinity> xnox: And, y'know, do a source refresh.
[10:41] <xnox> infinity, all changes are systemdish right? so check that things don't explode and work correctly post-install?
[10:41] <xnox> yeah, source refresh.
[10:41]  * xnox is validating that the bugfixes in ubiquity are correct in yakkety now.
[11:09] <infinity> xnox: Well, validate that the bugs are fixed.  cyphermox didn't get around to it before he went and got married.
[11:15] <infinity> pitti: And if you could verify your systemd SRU, that'd be nice.
[12:21] <pitti> infinity: ok, I'll look into doing at least some
[12:22] <pitti> infinity: would you be ok with short-cutting some other -updates, like the 5 day old ones?
[12:22] <pitti> this morning I released the ≥ 7 days stuff
[12:30] <infinity> pitti: I did a ton.  Check -changes
[12:31] <pitti> ah, good
[12:31] <pitti> so pending-sru just needs to update
[12:48] <pitti> infinity: meh, so it does not regress, but it fixes only half of bug 1593379
[12:48] <pitti> but either way, none of those are really important for .1
[12:55] <infinity> pitti: The upgrade bug seems important, at least.
[12:55] <pitti> that yes
[12:56] <infinity> pitti: If you're happy that nothing has regressed, I'd like to release this, and you can follow-up with a proper fix for 1593379
[12:56] <infinity> pitti: If that seems reasonable to you.
[12:56] <pitti> infinity: yes, sounds good; I'll reopen after releasing
[12:56] <pitti> infinity: upgrade, reboot, shutdown etc. was fine
[12:57] <pitti> and it has a ton of autopkgtests too
[12:57] <infinity> pitti: Reopen away.
[12:58] <pitti> done
[13:26] <xnox> infinity, console-setup is good, and auberginy
[13:28] <xnox> will upload into proposed queue, ubiquity with sources updated to the -proposed console-setup and -proposed partman-base
[13:32] <infinity> xnox: Ta.
[14:23] <infinity> xnox: Do you need images built with that ubiquity to verify it?
[14:48] <xnox> infinity, not really. I upgrade from live session and test it that way. There is nothing that affects things before multi-user.target
[14:49] <xnox> i will test the binaries from -proposed to verify the two bugs and that things didn't explode in a second.
[14:49] <infinity> xnox: Danke.
[14:50] <infinity> pitti: Review my base-files to make sure I can type?
[15:28] <pitti> infinity: LGTM, accepted
[17:29] <xnox> infinity, xenial-proposed ubiquity is good.
[18:24] <slangasek> cjwatson: fooey - cady's chroot is sorted, and the haskell-http-conduit build failure isn't reproducible there either.  But consistently reproducible in LP
[18:24] <slangasek> and a distinctive lack of verbose output from the test log
[18:25] <slangasek> output in failing log:
[18:25] <slangasek>   Response cookie jar is nothing when request cookie jar is nothing
[18:25] <slangasek> Test suite test: FAIL
[18:25] <slangasek> output in successful log:
[18:25] <slangasek>   Response cookie jar is nothing when request cookie jar is nothing
[18:25] <slangasek>   TLS
[18:25] <slangasek> [...]
[18:30] <jderose> infinity: latest 16.04.1 daily desktop ISOs still seem to have proposed enabled by default... was that intentional or an oversight?
[18:31] <infinity> jderose: Spinning non-proposed images tonight after I promote ubiquity and base-files.
[18:31] <jderose> infinity: gotcha, sounds good. thanks!
[18:50] <infinity> xnox: You didn't comment on the bugs or change the tags...
[18:54] <infinity> slangasek: Upload to a PPA with a "cat dist-ghc/test/http-conduit-2.1.11-test.log" on failure?
[18:56] <jderose> infinity: out of curiosity, when should 14.04 start prompting folks for upgrades to 16.04?
[18:57] <infinity> jderose: Best case scenario, Thursday.  We might delay a few days to make sure we have solid upgrade testing, but assume "soon".
[18:58] <jderose> infinity: we're doing 14.04 upgrade testing today, so i'll let you know if we find anything. so i assume right now i need to use `upgrade-manager -d` to force it still?
[18:58] <rbasak> If possible I'd like to land the MySQL SRU before prompting release upgrades. There are a bunch of bugs that cause postinst failures that should be fixed.
[18:58] <rbasak> (I have yet to verify but will do so before the ageing period is done)
[18:58] <infinity> jderose: Yep.
[18:58] <jderose> cool, thanks
[19:10] <slangasek> infinity: I just catted a successful one and it's even more useless than the build log... I suppose we can see what a ppa says
[19:11] <infinity> slangasek: Oh.  I was just taking the message's word on it being useful. :P
[19:11] <infinity> slangasek: I should know not to trust programmers.
[19:13] <slangasek> yeah, I'll try it anyway, maybe it's usefully verbose only on failure
[19:36] <jderose> infinity: one little issue i just found: i did a 14.04 to 16.04 upgrade. upgrade worked fine, but at the end clicking "Restart Now" has no effect... system does not reboot, update-manager just closes
[19:36] <infinity> jderose: Curious.  Does restarting via other methods work?
[19:37] <infinity> jderose: Cause that sounds a bit like something forgot how to talk to upstart to reboot into systemd.  Which we have a lot of icky hacks for.
[19:40] <jderose> infinity: restarting from the indicator and power button both opened the reboot/shutdown dialog, and they rebooted fine. so at a glance seemed like a problem with upgrade-manager.
[19:40] <infinity> jderose: Huh.  If it's reproducible with a simple recipe, please file a bug.
[19:40] <jderose> infinity: okay, will do after i eat some lunch
[20:03] <xnox> infinity, yes, ran out to a birthday party =/
[20:03] <xnox> 1sec
[20:03] <infinity> xnox: I read that as "ran out of birthday party".
[20:04] <xnox> =)
[20:04] <infinity> "Man, I'd do that, but I'm all out of birthday party."
[20:04] <infinity> xnox: Anyhow, I trusted you and released it.  But do document something in the bug in case someone yells at me later for being a cowboy. ;)
[20:04] <infinity> s/bug/bugs/
[20:05] <infinity> I wonder if I can make "out of birthday party" a thing.  Basically, the new lack of carefactor.
[20:05] <xnox> and done
[20:18] <cjwatson> slangasek: Could be something that only happens on 64-bit kernels?  Though can't imagine what
[20:59] <infinity> Ahh, crap.  I didn't disable PROPOSED for those RCs.
[21:00]  * infinity head -> desk.
[21:00] <jderose> infinity: hehe :P
[21:01] <infinity> Meh.  I'll respin in the morning.
[21:01] <cjwatson> slangasek: BTW you don't need to use devirt PPAs for arm64 any more
[21:01] <infinity> They'll only pick up one or two packages from proposed anyway.
[21:01] <cjwatson> or armhf for that matter
[21:01] <slangasek> cjwatson: yeah
[21:01] <cjwatson> slangasek: I notice that the description of that PPA specifies a condition under which it should be deleted, and that condition now holds :)
[21:01] <slangasek> heh
[21:01] <cjwatson> slangasek: (but maybe it's been repurposed for s390x ...)
[21:02] <slangasek> cjwatson: except the ppa doesn't have s390x enabled ;)  if you could do that, I would repurpose it, yes
[21:03] <cjwatson> slangasek: done
[21:04] <slangasek> cjwatson: thanks
[21:05] <slangasek> hmm do I not have -proposed enabled for this ppa? <checks>
[21:05] <slangasek> sure didn't :P
[21:13] <slangasek> 0 of 1 test suites (0 of 1 test cases) passed.
[21:13] <slangasek> Test suite test: RUNNING...
[21:13] <slangasek> Test suite test: FAIL
[21:13] <slangasek> Test suite logged to: dist-ghc/test/http-conduit-2.1.11-test.log
[21:13] <slangasek> yep, super useful
[21:13] <slangasek> thanks for that
[21:31] <cjwatson> slangasek: #debian-haskell@oftc might have clues
[21:31] <infinity> slangasek: You beat me to that accept by a few seconds.
[21:31] <infinity> slangasek: Got very confused.
[21:32] <slangasek> infinity: roaksoax escalated to me directly :)
[21:32] <infinity> slangasek: I assume he wants it on point release media (see #-devel)
[21:32] <slangasek> cjwatson: yeah, I'm not going to spend any more time on this one today during work hours
[21:33]  * cjwatson nods
[21:33] <infinity> slangasek: If so, you have my blessing to expedite the -updates promotion while I'm asleep, I'll be respinning tomorrow for isc-dhcp, probably, and for the PROPOSED blunder.
[21:33] <slangasek> infinity: ack
[21:59] <jderose> infinity: seems 100% reproducible - https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604173
[21:59] <jderose> small issue in the grand scheme of things, though
[22:03] <slangasek> that's odd, has someone recently subscribed me to notifications for Xubuntu Desktop images on the ISO tracker?
[22:04] <slangasek> I certainly do not recall subscribing myself, or receiving notifications for previous milestones