[00:56] <stgraber> oh, didn't expect an auto-accept, nice :)
[00:57] <stgraber> cyphermox: ^ that upload is me fixing nm-openvpn to be a bit less busted as far as IPv6 as it was the only blocker for me to run on IPv6 only
[00:57] <cyphermox> stgraber: ack. I'm looking at a ppp bug myself
[00:57] <stgraber> cyphermox: that patch doesn't change default behavior and only allows passthrough of the tcp6 and udp6 protocols when the user is already specifying it. It's probably suitable for upstream though I'd expect they'd like to make it a bit more complete.
[00:58] <cyphermox> ok
[00:58] <cyphermox> I'm not sure yet, but I think my pptp tests were crashing my router.
[00:58] <stgraber> specifcally, if you want to connect over IPv6, you must add the :udp6 or :tcp6 suffix with my patch, instead of having openvpn try ipv6 and fallback to ipv4 which would be preferred
[00:58] <stgraber> I figured I'd keep things simple this late in the cycle :)
[00:59] <cyphermox> mmkay
[01:00] <stgraber> I could find a nice way to have OpenVPN do the IPv6 to IPv4 fallback... I think the right answer is to generate a second --remote config entry for the fallback protocol, but then the patch becomes significantly larger :)
[01:00] <stgraber> my patch is still right, the right fix would just be added on top, so the change ever makes it upstream, we can cherry-pick it safely
[01:01]  * stgraber is happy, Google fixed Hangout over IPv6 this morning and now NM is fixed too, those were the only two reasons why I was adding IPv4 connectivity back sometimes!
[01:10] <cyphermox> yippee.
[01:11] <cyphermox> stgraber: if Videotron could do a bit of work to get IPv6 to finally be available at large
[01:11] <cyphermox> it's so close
[01:12] <stgraber> haha, yeah, that's why I'm on teksavvy DSL here :)
[01:13] <cyphermox> except so retarded with that weird Comcast DHCPv6 PD crap
[01:17] <cyphermox> well, I'm surprised to see that teksavvy prices aren't that far from those of Videotron
[01:17] <cyphermox> stgraber: if you have time to review stuff, ubiquity & its slideshow ;)
[01:32] <cyphermox> heh, nevermind about the ubiquity upload, looks like that's TheMuso's, and I have some merging to do
[02:29] <stgraber> I'm assuming we're keeping base-files in the queue until a bit before we start spinning rc images?
[02:31] <infinity> stgraber: *shrug*
[02:31] <stgraber> I don't mind personally but I've noticed that the queue has been emptied except for base-files a few times today :)
[02:31] <infinity> stgraber: It's not like it says "we're released, tell your friends", it just doesn't say "development series" anymore.
[02:32] <infinity> But yeah, traditionally, we seem to accept it right before the weekend respin.
[03:04] <mwhudson> ^ we have the security fix already in ubuntu5 but uploading the release seems like it makes sense
[03:05] <stgraber> mwhudson: good, so that means I don't have to re-upload lxd since it picked up the fix with ubuntu5 already
[03:05] <mwhudson> stgraber: indeed
[03:06] <mwhudson> although hm
[03:06] <mwhudson> stgraber: looks like the fix is a bit more extensive than the patch i had, there's some ecdsa stuff to
[06:50] <pitti> infinity: ^ this is quite a mouthful, please see bug 1553309
[06:50] <ubot5`> bug 1553309 in openssl (Ubuntu) "[FFe]: Include FIPS 140-2 into openssl package" [Undecided,In progress] https://launchpad.net/bugs/1553309
[06:51] <pitti> infinity: I did some rounds of patch reviews and discussions, and now sponsored the package as it's "good enough" and we desperaately need autopkgtests and field testing now
[06:51] <pitti> there will be another upload with some patch cleanup
[06:51] <pitti> infinity: want me to accept this myself, or do you want to revie?
[06:51] <pitti> w
[07:55] <pitti> infinity: ok, accepting this, and added a block-proposed tag, to get the test machinery going
[11:08] <cpaelzer> Hi, please let me know if there are any questions about the dpdk upload that would have to be resolved to ack the upload
[11:10] <caribou> same here regarding vsftpd : the previous upload failed on a DEP8 test
[11:17] <infinity> caribou: I'd pay you big money to edit patches by hand when you're making a 1-line change instead of quilt refreshing. :P
[11:17] <infinity> (Doubly-so, since this is a delta from Debian)
[11:23] <infinity> caribou: Example:
[11:23] <infinity> caribou: Yours: http://launchpadlibrarian.net/253581897/vsftpd_3.0.3-3ubuntu1_3.0.3-3ubuntu2.diff.gz
[11:23] <infinity> caribou: Mine: http://paste.ubuntu.com/15808504/
[11:24] <infinity> caribou: (And I uploaded that second one, you don't have to...)
[12:50] <infinity> pitti: ^-- Review?
[12:53] <caribou> infinity: for once I wanted to do it in a "clean" way :)
[12:53] <infinity> caribou: Heh.  Well, to be fair, it's not your fault quilt refresh sucks so hard at this. :P
[12:54] <infinity> caribou: Nor that, for some braindead reason, the initial format for dpkg --commit doesn't match the default format of quilt refresh.
[12:54] <caribou> infinity: I got myself into a few problems previously by hacking directly at the patches
[12:54] <infinity> caribou: But it drives me nuts to introduce extra delta, that's all.
[12:54] <caribou> infinity: I didn't like the fact that it was touching other things either
[12:54] <infinity> caribou: I probably hand-edit patches more often than I apply them with patch, so I'm also weird. :P
[12:55] <caribou> infinity: even worse, running adt-run manually gave me FTBS errors that don't reproduce on the builders
[12:55] <caribou> infinity: I still need to get the DM to accept to revert that change
[12:56] <caribou> thanks for doing it yourself btw
[12:56] <infinity> caribou: Yeah, I read through the bug report before accepting your upload.  You seem to be in the right on this one, IMO.
[12:57] <caribou> infinity: well I researched a bit to find a reference to the fact that it should be starting (which xnox told me was the debian policy) and couldn't find it so I went ahead with xnox's suggestion
[12:57] <infinity> caribou: I think the only time "unconfigured by default" is a valid setup for a daemon is when there's literally no sane default possible.  Which just isn't true for an ftpd.  Listening on all interfaces/protocols, password-only, is a totally sane default.
[12:57] <caribou> infinity: well, it's been like that on debian/ubuntu for years, I couldn't figure out why they reverted it just because of the manpage
[12:58] <caribou> luckily the DEP8 test caught it
[12:58] <infinity> caribou: "Daemons must start by default if at all possible" might have been an Ubuntu policy decision, not Debian.  One of the many tweaks that made us more user-friendly.  I'd have to dig up references to be sure, though.
[12:59] <xnox> caribou, que?
[12:59] <infinity> Because it's just plain silly to install a thing and have it not working.
[12:59] <caribou> infinity: I found a lot of forum/blog/stackexchange mentions that it was the default on debian, just couldn't find any reference of it in the policy manual
[13:00] <xnox> oh that thing
[13:00] <caribou> xnox: yep
[13:00] <xnox> i think i ended up saying "we should listen on ipv6 and ipv4 by default"
[13:00] <xnox> just like we did in the past.
[13:00] <caribou> xnox: that's what listen_ipv6 does now
[13:00] <xnox> well in the past we used to only do ipv4, but you know it's 2016 and ipv6 is a thing now.
[13:00] <xnox> yeap.
[13:00] <xnox> cool =)
[13:02] <pitti> infinity: done
[13:02] <cyphermox> good morning
[13:03] <infinity> pitti: Ta.
[13:03] <infinity> And now I go coffee and breakfasting while I wait for some archive churn.
[13:03] <cpaelzer> infinity: reminder - you wanted to go shopping
[13:04] <infinity> cpaelzer: Thanks. :P
[13:22] <tyhicks> pitti: hi - I'm seeing that same failing lxc test is preventing the latest apparmor migration again
[13:23] <tyhicks> pitti: could you hint it again?
[13:23] <pitti> tyhicks: oh, is lxc failing regularly now?
[13:24] <pitti> There is no download available for release=xenial, stream=daily, arch=amd64
[13:24] <pitti> wut
[13:24] <tyhicks> There is no download available for release=xenial, stream=daily, arch=amd64
[13:24] <tyhicks> pitti: neither stgraber or I can reproduce it locally
[13:26] <pitti> hinted
[13:26] <pitti> tyhicks: ^
[13:26] <pitti> but this is entirely new to me
[13:27] <pitti> curiously it works fine on ppc
[13:27] <ogra_> the architecture of the future
[13:27] <tyhicks> pitti: it failed in the same way on monday
[13:28] <tyhicks> pitti: retries can get it to eventually pass but I figured 3 retries was enough
[13:31] <pitti> tyhicks: btw, nice to see linux' tests passing again since the new apparmor landed
[13:31] <tyhicks> yes :)
[13:46] <apw> i am glad ... we've been assuming it was the only issue ...
[14:09] <cyphermox> breakfast time
[14:22] <infinity> xnox: You didn't want to add statd to s390-tools' suggests?
[14:23] <xnox> infinity, yes no maybe =)
[14:24] <xnox> infinity, i should, shouldn't I ?
[14:24] <infinity> xnox: *shrug*
[14:24] <infinity> xnox: I think you've done that for the broken-out packages so far.
[14:24] <infinity> xnox: OTOH, I suspect this isn't your last s390-tools upload. :P
[14:24] <xnox> =)))))))
[14:24] <xnox> unfortunately, i doubt it.
[14:24] <infinity> xnox: So, catch it on the next upload, if you want.
[15:47] <infinity> pitti: ^-- Based on a grep-dctrl, I decided just the virtual package was the right way to go, rather than s/16/12/
[15:48] <infinity> Ahh, and thanks. :)
[15:48] <pitti> infinity: yep, that's also what I tested in the schroot
[15:48] <pitti> infinity: was auto-accepted :)
[15:48] <infinity> Oh, of course.
[15:48] <infinity> I'll retry smc when that publishes.
[15:48] <pitti> was looking at that huge unity+stuff landing, but dinner time now
[15:48] <infinity> Then we're down to one nbs?
[15:48] <pitti> yeah, will look at the latex thingy tomorrow
[15:49] <pitti> or rather, later tonight after basketball
[15:51] <doko> hmm, why is this still "core"?
[15:52] <infinity> pitti: gregoriotex was removed from testing over 1000 days ago.  Should probably just demote or remove it, unless there's an obvious and simple fix.
[15:54] <infinity> platform.xenial/supported-development-common: * libstdc++-4.9-pic
[15:54] <infinity> platform.xenial/supported-development-common: * gcj-4.9-jdk		
[15:54] <infinity> ubuntu.xenial/development: * g++-4.9-multilib
[15:54] <infinity> ubuntu.xenial/development: * gfortran-4.9-multilib
[15:54] <infinity> ubuntu.xenial/development: * gcj-4.9-jdk
[15:54] <infinity> ubuntu.xenial/development: * gcj-4.9-source
[15:54] <infinity> ubuntu.xenial/development: * gcc-4.9-source
[15:54] <infinity> ubuntu.xenial/development: * libstdc++-4.9-pic
[15:54] <infinity> doko: ^
[15:54] <doko> not anymore
[15:56] <infinity> doko: Well, things could just be lagging a bit, then.  I wouldn't worry about it for now.
[16:01] <infinity> pitti: I'm going to just remove gregoriotex.  I can't honestly see a single soul complaining.  "LuaTeX style for Gregorian chant scores".
[16:01] <infinity> SUPER USEFUL.
[16:03] <ogra_> the choirs will hunt you down !
[16:03] <infinity> Let 'em.
[16:04] <ogra_> yeah, until they show up under your bedroom window when you wanna sleep
[16:05] <Skuggen> Noo, my chants
[16:06] <cyphermox> infinity: why is that not seeded in minimal?
[16:06] <ginggs> It is as if millions of Enigma fans suddenly cried out in terror, and were suddenly silenced.
[16:06] <infinity> ginggs: Enigma has no fans.
[16:07] <infinity> ginggs: Just a lot of people who regret their purchasing decisions in the 90s.
[16:07]  * ogra_ knows a lot cryptographers that are enigma fans
[16:07] <ogra_> oh, wait, thats the other enigma
[16:08] <apw> they don't run things we make, not secure enough, they run hello-world they wrote in asm, and nothing else
[16:10] <xnox> infinity, how dare you!
[16:10] <xnox> pretty much everybody uses CTAN anyway, rather than distro packages for leave modules
[16:11] <infinity> I was pretty sad to discover that gregorio had no rdeps.
[16:12] <infinity> Was kinda hoping for some pocket of the archive dedicated to gregorian chant apps, maintained by debian-monks@lists.
[16:12] <infinity> With any luck, they'd also make some stellar booze.
[16:12] <infinity> But, sadly, no.
[16:13] <xnox> omg i've never seen so many nice comments on youtube.
[16:13] <xnox> on the enigma channel it's like "this is amazing" "i love it" "splendit"
[16:13] <ogra_> about enigma ?
[16:13] <xnox> aha
[16:13] <ogra_> lol
[16:13] <xnox> not a single diss at all
[16:14] <infinity> Kids these days...
[16:14] <ogra_> must be the music ... it lulls you into some weird state of mind
[16:14] <ogra_> (dont play it backwards though)
[16:15] <infinity> Enigma is a gateway drug that leads to Brian Eno.
[16:15] <infinity> I guess parents just aren't doing their job anymore.
[16:15] <pitti> infinity: gregoritex> sounds good
[16:16] <infinity> pitti: Good, cause it's already gone. :P
[16:16] <infinity> pitti: So, in a few publisher cycles, we should be at 0 NBS.
[16:16] <ogra_> pitti, so you are one of these enigma fans then ?
[16:16] <pitti> yay
[16:16] <infinity> And then on to the next report to clean up.
[16:16] <pitti> c-m? :-)
[16:17] <infinity> c-m's in pretty good shape, just a few odds and ends.
[16:17] <infinity> Ridding the world of mysql-5.6 looks to be the biggest thing left right now.
[16:18] <infinity> doko: Have you noticed the irony that, just in time for powerpc scalingstack (well, almost there), the GCC testsuite doesn't kill my buildds anymore? :P
[16:19] <doko> infinity, you told me ...
[16:19] <infinity> doko: Oh, did I?  Well, I'm old and forgetful.  I'm sure you can relate to at least half of that statement.
[16:38] <rbasak> infinity: can I have a pre-upload review of https://git.launchpad.net/~racb/ubuntu/+source/mysql-5.7/commit/?h=fixes&id=633deaa392959a658ff1b784e93eb0a7a3a73ac6 please, since it'll take a while to test and upload if you want it tweaking? It's a little extensive, but fixes a known issue. I've already quoted $rootpw properly and noted the LP bug reference in the changelog properly in a future commit.
[16:38] <rbasak> The full set of changes I intend to upload are ubuntu/devel..fixes in https://git.launchpad.net/~racb/ubuntu/+source/mysql-5.7/log/?h=fixes
[16:45] <stgraber> mwhudson: uploaded a new lxd now so you won't have to worry about having it rebuilt to get the rest of that golang fix :)
[16:48] <pitti> stgraber: thanks for the fix :)
[16:52] <stgraber> pitti: trivial enough :) looks like I thought of it for the stop case but not for start
[16:55] <xnox> infinity, d-i passed smoke test and looks lovely
[16:55] <xnox> however sysconfig-hardware is only half-Configured
[16:56] <infinity> xnox: postinst broke?
[16:56] <xnox> rmdir: failed to remove '/etc/sysconfig/scripts/common': No such file or directory^M
[16:56] <xnox> yeap.
[16:56] <xnox> looking.
[16:57] <xnox> i shall fix that shortly
[16:57] <xnox> i guess all ugprade logic is fine, but the fresh clean install was not =)
[16:58] <infinity> xnox: Kay, but that sounds promising, if that's all that went wrong.
[17:00] <xnox> anyway, all should be good now.
[17:00] <xnox> it was a bit crap that i couldn't do versioned upgrade script. As there is no way to know if old d-i was used to do the installation =(
[17:01] <lamont> thanks for the accept, whoever
[17:01] <lamont> stupid broken test harness exposing broken things by accident like that
[17:11] <xnox> infinity, if you approve sysconfig above, that would be nice.
[17:11]  * xnox is afk
[17:37] <Trevinho> Laney: hey, just noticed that https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1551986 had only the UIFe ACKed, not the FFe... Packages are in upload queue though :-/
[17:37] <ubot5`> Launchpad bug 1551986 in unity (Ubuntu Xenial) "[FFe][UIFe] HUD hotkey assignment is suboptimal" [High,In progress]
[17:38] <Trevinho> I've to go for a while now, but we can discuss that later... Anyway if someone from release team can give it a look. It's something design wanted to change at the last sight.
[17:42] <Laney> Trevinho: erm
[17:42] <Laney> you're changing the window controls now?
[17:44] <Laney> this is insane
[17:44] <Laney> argh
[17:44] <infinity> Laney: On the one hand, "erk", (especially the continued confusion over semicolon versus super), on the other hand, I fully support remapping the braindead Alt-tap right up until release day (it's the one keybinding I *always* have to remap locally) :P
[17:45] <Laney> Fixing the hud's shitty binding is one thing
[17:45] <Laney> Making alt-space be hud is quite something else
[17:45] <Laney> I'm going to block this stuff until we can sort it out
[17:46] <infinity> Well, it needs to be a combo, at any rate.  The problem with it being a single key is long-proven to be just not workable.
[17:46] <xnox> ship it
[17:46] <infinity> Alt-space does feel odd, though.
[17:47] <xnox> i think alt-space is the old gnome-do binding, and the old mac os x app which originally did that.
[17:47] <Laney> Randomly taking over a bit of window manager functionality one week before release
[17:47] <xnox> and alt-space does search on a mac os x too, no?
[17:47] <Laney> nuts
[17:48] <Laney> alt-space is *already* something in compiz
[17:48] <xnox> i can't remember how one summons Cortana on windows, might be alt-space too
[17:48] <xnox> Laney, what is it in compiz?
[17:48] <Laney> press it
[17:48] <infinity> Alt-space on Win32 and many/most UNIX window managers (including the one we use) is the window action menu.
[17:48] <infinity> Min/Max/Move/etc.
[17:48] <xnox> Laney, for me that did a drop down menu, randomly in a wrong position.
[17:48] <apw> infinity, isn't alt-space already a keybinding
[17:48] <xnox> i guess it doens't know how to display that menu in the righ tlocation with global menus in full screen size.
[17:49] <infinity> apw: Yes, it's what I said above. :P
[17:49] <infinity> The proposal seems to be to take over Alt-space and move the window menu to another keybinding, which is daft.
[17:50] <infinity> I'd suggest Alt-Menu for the HUD and leave Alt-Space alone.
[17:50] <apw> infinity, whats alt-menu ?  the right click key ?
[17:50] <infinity> apw: Menu is the right-click key, yeah.
[17:51] <apw> i don't even have one of those
[17:51] <infinity> Me neither.
[17:51] <xnox> infinity, i think that upload breaks accesibility and like TheMuso will complain loudly.
[17:51] <infinity> It's the perfect place to bind the HUD! ;)
[17:51] <apw> infinity, ahhh :)
[17:51] <rbasak> ^^ amarok will dep-wait on mysql-5.7 5.7.11-0ubuntu6 above
[17:51] <rbasak> I believe that should be all seeded packages switched to 5.7 after this, but I'll double check tomorrow after the archive has settled.
[17:57] <apw> if alt-super works why are we not just putting hud on that
[17:58]  * Laney just commented on the bug
[17:58] <Laney> I'm going away though so others feel free to carry this on
[18:11] <seb128> willcooke, you might want to read the backlog there
[18:12] <seb128> Laney, the plan afaik was to move the menu combo to another binding, that should have been in the same landing?
[18:13] <seb128> the email mentioned moving it to alt-super
[18:13] <seb128> or
[18:13] <seb128> https://launchpad.net/ubuntu/+source/compiz/1:0.9.12.2+16.04.20160412-0ubuntu1
[18:14] <seb128>   * Show window actions menu on alt+semicolon. (LP: #1551986)
[18:14] <ubot5`> Launchpad bug 1551986 in unity (Ubuntu Xenial) "[FFe][UIFe] HUD hotkey assignment is suboptimal" [High,In progress] https://launchpad.net/bugs/1551986
[18:14] <seb128> that already landed it seems?
[18:18] <xnox> seb128, semicolon is a very bad binding... because of keyboard layouts....
[18:19] <seb128> xnox, I think it's a changelog thinko, see bug
[18:19] <doko> infinity, can you accept openjdk-8, or do you plan to build images tomorrow?
[18:19] <seb128> it's super-alt
[19:22] <lamont> I suspect that https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820056 is worthy of an SRU, once it's fixed (migration should be possible, I expect, for many cases)  No way in hell it'll be in before the release
[19:22] <ubot5`> Debian bug 820056 in bind9 "writeable file 'foo': already in use" [Important,Open]
[19:35] <Trevinho> seb128, xnox: yeah changelog is broken... It's super+alt
[19:40] <Trevinho> Laney: I know... I personally would have used super+space for HUD and keeping the Alt+space to what it used to be. But, design preferred this solution.
[19:41] <Trevinho> Laney: also I thought you were aware of that request, sorry.
[19:47] <infinity> Trevinho: It's fundamentally just greedy and gross to subvert a common keybinding for something new, and move the one we're all used to to somewhere else to compensate.
[19:48] <infinity> Trevinho: I'd be much more supportive of just moving HUD to Super+Alt and leaving Alt+Space alone.
[19:48] <infinity> (Or super+space, if you want, given that's just one key over from what design wanted)
[19:49] <infinity> Trevinho: But "hey, let's move TWO key binding to make up for the bad placement of one of them" is daft.
[19:49] <infinity> willcooke, seb128 ^
[19:49] <seb128> +1 on that
[19:49] <infinity> Trevinho: FWIW, I'm all for moving the HUD off Alt, that was a bad idea from day 1, it's just nutty to move it to another well-known binding.
[19:50] <seb128> but the keys choice comes from design I think
[19:50] <seb128> unsure how much they are open to the alternative
[19:50] <infinity> seb128: Fine, design's not immune to me rejecting packages. :P
[19:50] <seb128> willcooke, do you know?
[19:50] <infinity> So, get some design people in here to argue.
[19:50] <lamont> bind9_9.10.3.dfsg.P4-8 -- driver is "* Add support for native pkcs11.  LP: #1565392" which makes tjaalton's package usable again, by delivering separately built binaries for its use (see the bug for the crying)
[19:50] <ubot5`> Launchpad bug 1565392 in bind9 (Ubuntu) "add support for native pkcs11" [Undecided,Confirmed] https://launchpad.net/bugs/1565392
[19:50] <xnox> infinity, i can go into the office =) it will be funny.
[19:50] <willcooke> infinity, seb128 - please comment on the bug and I will speak to Design
[19:50] <seb128> willcooke, thanks
[19:53] <infinity> willcooke: Added a quick comment.
[19:54] <willcooke> thanks infinity
[20:21] <Trevinho> infinity: yeah, I know... I already had all the concerns you mentioned here by my own. So It's nothing new to read. I would go with Super+Alt on HUD or Super+Space (better to me), but I understand that design point was "super is something we use for windows related actions, so alt+space is not good".
[20:21] <cjwatson> Any reason why the seeds shouldn't be changed to replace ubuntu-snappy-cli with snapd?  ubuntu-snappy-cli is a transitional package now
[20:21] <infinity> cjwatson: Yeahp, it should all be changed, I was just waiting for all to filter down.
[20:21] <Trevinho> anyway my role is getting things done, then I did what it was designed.
[20:22] <Trevinho> s/I/we/
[20:22] <infinity> Trevinho: Yeah, I understand.  I'm happy to be the guy who has to say "no". :P
[20:22] <infinity> s/happy to be/fine with being/
[20:22] <infinity> cjwatson: You want I should do that, or are yo ualready committing?
[20:23] <cjwatson> Go for it, I should go and do other evening things.
[20:23]  * pitti retries smc, https://launchpad.net/ubuntu/+source/cegui-mk2/0.8.4+dfsg-4ubuntu1 is built now
[20:23] <infinity> pitti: Ahh, I had been waiting on armhf to publish.
[20:24] <infinity> pitti: (which it's still doing)
[20:25] <pitti> infinity: hm, 42 mins not enough? well, if it still fails, we'll just retry again
[20:25] <pitti> but at least we know if it works on the other arches then
[20:25] <infinity> Yeah, I'll retry armhf again in a few minutes when the publisher gets there. :P
[20:26] <infinity> I kinda want the publisher logtail in the lp.net web UI somewhere, so other people can pull the tricks I do by staring at it in progress.
[20:27] <cjwatson> We might at least get it into an ELK instance with slightly wider view access at some point this year or so.
[20:28] <infinity> cjwatson: Well, to be fair, watching the logtail is a workaround for the UI being suboptimal in other ways, but it's a workaround that works for people who know what the log is telling them. :P
[20:28] <cjwatson> UI, publication process in general, ...
[20:29] <pitti> infinity: *sob* https://launchpadlibrarian.net/253676097/buildlog_ubuntu-xenial-amd64.smc_1.9+git20121121-1.2build2_BUILDING.txt.gz
[20:29] <infinity> cjwatson: If publishing records had an extra "publishing" state, we could set "publishing" where we currently set "published", and then flip to "published" at the dists switch.
[20:29] <infinity> cjwatson: But that's effort.  Watching a log is easy.
[20:30] <infinity> pitti: Hah.
[20:30] <infinity> pitti: At least it's different!
[20:31] <cjwatson> infinity: Which would confuse a different set of people who care about archive.u.c :-/
[20:31] <infinity> cjwatson: Well, I don't think the LP UI can ever be accurate WRT mirrors.
[20:31] <infinity> cjwatson: Those people clearly don't matter.
[20:31] <infinity> (And it would be closer to right, at least)
[20:32] <cjwatson> Sure, but the fact that a.u.c is a set of mirrors is an implementation detail.
[20:32] <cjwatson> (I'm not arguing it's perfect as it stands BTW)
[20:32] <infinity> Right.  My "solution" would make it "better" for the mirror situation, but still incorrect.
[20:32] <infinity> Lots of "air quotes" around "here".
[20:33] <pitti> anyway, that smc thing is a "tomorrow" thing, I reserve this nightshift for some quiet autopkgtest infra hacking
[20:34] <tjaalton> was final freeze for universe too?
[20:34] <infinity> cjwatson: To be fair, I think most people who assume "published" is meaningful are caring about up-to-the-minute ftpmaster status for build-deps and the like, not so much mirror lag, but YMMV.
[20:34] <pitti> I just uploaded the three no-change rebuilds for the urdfdom lib transition (bug 1569626)
[20:34] <ubot5`> bug 1569626 in urdfdom (Ubuntu) "[FFe] Sync urdfdom 0.4.1-1 (universe) from Debian unstable (main)" [Undecided,Fix committed] https://launchpad.net/bugs/1569626
[20:34] <infinity> tjaalton: Yes and no.
[20:34] <tjaalton> infinity: like, still able to get tested stuff out but will end up in the queue?
[20:34] <infinity> tjaalton: We'll still have the auto-accept bot on until close to release time, but there's an honor system in play where you agree not to upload Stupid Things.
[20:35] <tjaalton> right, of course
[20:35] <infinity> tjaalton: Read a former Final Freeze announce from 6mo ago.
[20:35] <tjaalton> ok
[20:35] <infinity> tjaalton: Or wait a day for a new one. ;)
[20:35] <pitti> infinity: debian bug 812096 does not sound very hopeful, though
[20:35] <ubot5`> Debian bug 812096 in src:smc "smc: FTBFS: configure: error: Package requirements (CEGUI-OPENGL >= 0.7.2) were not met:" [Serious,Open] http://bugs.debian.org/812096
[20:36] <tjaalton> well, looks like I can bump freeipa to 4.3.1, but that needs an update to bind9 which lamont is testing now, and also adding systemd support to opendnssec which I've tested already
[20:36] <infinity> pitti: Fun.  Well, we have a week to decide what to do about it.
[20:36] <tjaalton> it's really just a big bugfix release, finally allowing to install ipa replicas
[20:37] <tjaalton> I guess apache systemd support might be pushing it too far :P
[20:37] <pitti> infinity: "package the latest upstream version" at least sounds like a way out, only three reverse recommends
[20:37] <infinity> pitti: If it's a trivial uupdate job that requires zero thought on our part, I'm game.
[20:37] <lamont> tjaalton: it's actually sitting in the queue hoping for approval..
[20:37] <lamont> bind9 that is
[20:37] <tjaalton> lamont: ooh shiny
[20:37] <infinity> pitti: We have more than enough work to do to be wasting real effort on it, though.
[20:37] <tjaalton> thanks a lot!
[20:38] <lamont> and since bind9 is on the cd images.... :/
[20:38] <pitti> infinity: demote-to-proposed with ignoring the recommends on the three games-* metapackages would work too
[20:38] <infinity> lamont: bind?  Isn't that old news?  I thought everyone used knot these days.
[20:38] <pitti> (didn't realize that these are just metapackages)
[20:39] <lamont> infinity: I refuse to rise to the bait. :p
[20:39] <infinity> pitti: Yup.  But hey, we can sort it during the release sprint, it's not like affects media.
[20:39]  * xnox has knot stickers on my laptop
[20:39]  * lamont can tie knots
[20:39] <cyphermox> tjaalton: any plans to backport the xenial X stack to trusty?
[20:39] <pitti> actually, it is already in -proposed, so just remove from xenial-release, done
[20:39] <pitti> infinity: yep0
[20:39]  * pitti off irc, waves good night
[20:39] <tjaalton> cyphermox: of course, once things have settled down a bit
[20:40] <cyphermox> tjaalton: ok, I was just checking if you were going to do it or if it's somebody else
[20:41] <tjaalton> cyphermox: no it's been me since mlankhorst jumped ship
[20:43] <cyphermox> tjaalton: ack, thanks
[20:44] <tjaalton> i'd hope to get mesa 11.2.1 in before release, but not sure about that
[20:47] <tjaalton> sounds like it'll get released on friday
[20:56] <cyphermox> ok
[21:59] <mwhudson> stgraber: haha
[22:55] <bdmurray> infinity / slangasek: I'm just going to make a generic EOLReleaseAnnouncement and put it in meta-release and on changelogs.ubuntu.com (when it comes back) to resolve bug 1569233. Sound good?
[22:55] <ubot5`> bug 1569233 in ubuntu-release-upgrader (Ubuntu) "changelogs.ubuntu.com/EOLReleaseAnnouncement missing, causes distro upgrade failure on EOL systems" [Medium,Triaged] https://launchpad.net/bugs/1569233
[23:05] <slangasek> bdmurray: "when it comes back"? where has it gone?
[23:06] <slangasek> bdmurray: if the point here is that it doesn't require somebody to remember to create a per-series EOLReleaseAnnouncement file each time a release EOLs, reducing the number of things we have to touch sounds like a good idea to me
[23:10] <bdmurray> slangasek: I think they are changing out hardware. My initial idea in comment 2 would require more touching like that, so going with a generic one on changelogs.
[23:10] <cjwatson> it had a catastrophic disk failure (ironically, while adding more disk)
[23:11] <cjwatson> aiui it's being recovered in one of the harder ways
[23:12] <slangasek> heh
[23:13] <slangasek> recovery procedure: replay 12 years of Ubuntu development in a pocket universe
[23:14] <cjwatson> https://rt.admin.canonical.com/Ticket/Display.html?id=89921 if you want to follow along
[23:16] <cjwatson> though I notice that extract-changelogs could usefully be fixed to use order_by_date=True ... I should have a poke at that
[23:16] <slangasek> hmm that ticket number is older than I would expect for something that is taking meta-release offline
[23:16] <bdmurray> meta-release is still accessible
[23:16] <slangasek> ah
[23:17] <bdmurray> its just I can't get to the server at the moment, and that bug isn't that important
[23:20] <cjwatson> pitti: I just noticed r160 in ddeb-retriever, in which you seem to have missed the long comment I left immediately above the changed code explaining why any attempt to do what you did would introduce a subtle data-loss bug :-(
[23:21] <cjwatson> pitti: can you have a look over that comment and we can discuss it when we're both around?