[08:14] <darkxst> infinity, would it be possible to move webkit2gtk source only into main for building?, we need for it gnome-online-accounts which is need by gnome-control-center. bug 1466290
[08:14] <ubot93> bug 1466290 in gnome-online-accounts (Ubuntu) "Update to 3.16" [Medium,New] https://launchpad.net/bugs/1466290
[08:14] <infinity> darkxst: I had that bug open to look at.  Just hadn't gotten there yet.
[08:18] <darkxst> ok, anyway the binaries that dep on webkit2gtk can all be demoted to universe (not used by Ubuntu even though they are in main)
[08:20] <infinity> darkxst: I haven't looked at the situation well enough to answer that yet. :P
[09:48] <bdrung_work> hi, http://releases.ubuntu.com/15.04/ shows ubuntu-15.04-snappy-amd64+generic.img.xz and ubuntu-15.04-snappy-amd64-generic.img.xz. What's the difference beside the one character (+ vs -) in its name?
[10:08] <infinity> bdrung_work: One is a symlink to the other because a blog post mentioned the incorrect (-) naming scheme. :P
[10:08] <bdrung_work> ah, okay
[10:09] <infinity> Or some install instructions or something.  I forget the history, but should probably revisit the next time someone asks me to publish a snappy thing to cdimage and make sure it's not a problem anymore.
[10:13] <bdrung_work> infinity, having two files opens the question, which is the correct (and future proof) name
[10:16] <infinity> bdrung_work: arch+subarch is the canonical way to name subarches (as seen with, say, amd64+mac)
[11:00] <darkxst> infinity, I checked gnome-control-center and gnome-online-accounts, admittedly though I didnt check if there are other syncs from debian that might start building with webkit2gtk
[12:09] <rbasak> ScottK: thank you for releasing the grub2 SRU. Though grub2-signed hasn't been released concurrently. Won't this cause a problem for those who are doing the UEFI signed verification thing?
[12:10] <rbasak> cjwatson: ^^ help. infinity is asleep, slangasek presumably not up yet, and I don't know who else I can ask. Will this cause a regression?
[12:13] <cjwatson> That will cause a regression, yes.
[12:14] <rbasak> Well, it's live now, so we should do something.
[12:14] <cjwatson> Let me go and release it quickly now - it isn't quite aged, but the main change was in grub2 anyway.
[12:14] <rbasak> OK - thanks!
[12:16] <cjwatson> And as you say most of it was already live.
[12:16] <cjwatson> Done.
[12:16] <rbasak> Thank you!
[12:17] <cjwatson> Oh, yikes, I accidentally released it for utopic too and it wasn't explicitly verified for that so grub2 hadn't yet been released.
[12:18] <cjwatson> I think the path of least resistance is to release it there too.
[12:18] <cjwatson> Odds of problems are pretty low.
[12:18] <rbasak> :(
[12:18] <rbasak> OK
[12:18] <rbasak> I'll see if matsubara can verify utopic.
[12:18] <cjwatson> All done now.
[13:22] <arges> infinity: rbasak: hi. looking at bug 1454719, looks like most packages are in except docker.io... do i need to wait on somebody before putting that into -proposed?
[13:22] <ubot93> bug 1454719 in docker.io (Ubuntu Vivid) "docker.io update to 1.6.2" [Wishlist,Triaged] https://launchpad.net/bugs/1454719
[13:23] <arges> rbasak: and whats up with golang-pty-dev for utopic? did that ever get uploaded?
[13:30] <rbasak> arges: working on infinity on it. I have a list of fixes that are needed for the remaining items.
[13:30] <rbasak> err, _with_ infinity
[13:31] <arges> rbasak: got it. i'll leave it then
[16:38] <jamespage> please could the python-os-brick binary NEW packages be acked into wily
[16:42] <jamespage> ta
[19:16] <infinity> rbasak: Any progress on docker while I slumbered?
[19:56] <rbasak> infinity: sorry, kickinz1 was out today, so I focused on other stuff instead. I'll get back to Docker tomorrow with kickinz1.
[20:06] <infinity> rbasak: Mmkay.
=== boiko_ is now known as boiko
[20:58] <tjaalton> infinity: do you know if the daily trusty image should boot fine? mine drops in initramfs
[20:58] <tjaalton> could me my fault of course
[21:27] <infinity> tjaalton: I think that might be because we need the casper in the queue. :P
[21:27] <infinity> tjaalton: Let me review that and get it in.
[21:28] <infinity> tjaalton: I find it a bit disconcerting that no one's complained until now, since it's probably been broken for weeks. :/
[21:33] <infinity> tjaalton: Next daily (at 6:31am UTC) should have the fix.
[21:33] <infinity> tjaalton: If you're around and want a test ISO faster, I can spin a one-off.
[21:33] <tjaalton> infinity: nah it's fine, I can try the next daily
[21:34] <tjaalton> should I ack the packages from proposed if it's good?
[21:34] <tjaalton> the xorg stack that is
[21:34] <tjaalton> realized that there's no tracker bug for everything..
[21:34] <infinity> tjaalton: Let me know if the daily fixes your boot issue, that should help validate the casper bug.
[21:34] <tjaalton> ok
[21:34] <infinity> tjaalton: And yes, if you decide all the X stuff is good, lemme know.
[21:34] <tjaalton> right
[21:35] <infinity> tjaalton: Other than booting on two laptop with nearly identical Intel configs, I can't really test the X HWE reasonably. :/
[21:35] <infinity> tjaalton: I hope you have access to a few more video cards than I do.
[21:35] <tjaalton> well it's just the mechanics that need testing
[21:36] <tjaalton> and it's solid last I tried
[21:36] <infinity> tjaalton: Oh, there's also new nvidia drivers in the trusty queue.  I'm guessing I need those for the point release?  Or are the current ones in -updates 3.19 compatible?
[21:36] <infinity> (binary drivers, that is)
[21:36] <tjaalton> hmm yes you want those too, tseliot pinged about those earlier I think
[21:36] <infinity> tjaalton: Right, I'll get those reviewed.
[21:37] <infinity> tjaalton: And you also uploaded a new intel-lts-vivid for me, I see.  I'll look at that too.
[21:37] <tjaalton> yeah noticed they weren't in sync
[21:38] <infinity> Oh, was that the awful xv video corruption bug?
[21:38] <tjaalton> need to set up the scripts that mlankhorst had, if I could login to people.c.c (or whatever it is), vpn doesn't work for me
[21:38] <infinity> Definitely want to fix that.  It's vile.
[21:38] <tjaalton> scripts that generate these webpages with package versions and stuff
[21:38] <tjaalton> yep that one
[21:38] <infinity> tjaalton: VPN doesn't work for you?
[21:39] <tjaalton> naw
[21:39] <infinity> tjaalton: Sounds like something you should bring up in #is. :P
[21:39] <tjaalton> I have no dns if I start it
[21:39] <tjaalton> yeah tried that too
[21:39] <infinity> tjaalton: Do you have dnsmasq installed?
[21:39] <tjaalton> maybe if I don't use _this_ machine
[21:39] <infinity> tjaalton: If so, don't.
[21:40] <tjaalton> dnsmasq-base it seems
[21:40] <infinity> -base is fine (and needed)
[21:40] <infinity> Anyhow, lemme look at driver SRUs.
[21:40] <tjaalton> right, thx
[21:43] <infinity> tjaalton: Intel accepted.  nvidia will take a bit more gin before I'm prepared to face it.
[21:43] <tjaalton> nvidias are straight backports from vivid iirc
[21:43] <infinity> Pretty sure he did a bit of mangling to make them trusty-compatible.
[21:43] <infinity> At least, the changelog implies such.
[21:44] <tjaalton> ok
[21:44] <tjaalton> the one I was able to ack was clean
[21:44] <infinity> So, I need to diff and understand said mangling, and check for sanity.