[03:43] <robru> stgraber: what's going on with queuebot?
[03:46] <stgraber> robru: my server appears to be kernel panicing every 10 minutes, not sure why
[03:48] <robru> stgraber: oh good
[03:48] <robru> good luck
[03:49] <stgraber> trying to restart just the bare minimum for now, hoping things will stay stable enough for me to investigate tomorrow
[03:49] <stgraber> in any case, it should make for an interesting bug report as the only things running on that box are unprivileged containers, so if it's one of those causing the panic, then it's a regular user causing a kernel panic...
[05:25] <infinity> pfsmorigo: Looks like the migration of the kernel and d-i was pretty much perfectly timed for the daily that's going to happen automatically in about an hour.  So, in 1.5h or so, you should have a ppc64el daily that boots again.
[10:17] <jamespage> cjwatson, any reason why this upload disappeared between proposed and release pockets:
[10:17] <jamespage> https://launchpad.net/ubuntu/utopic/+source/python-oslo.vmware/0.6.0-1ubuntu2
[10:17] <jamespage> ?
[12:16] <jdstrand> infinity: apparmor can't be identical between docker, lxc and libvirt-lxc. also, libvirt-lxc uses individual profiles instead of the sam eprofile for all, lxc confines lxc start, libvirt-lxc runs libvirtd and a profile and docker.io is unconfined
[12:17] <jdstrand> infinity: but by far most of the profiles can be the same, so I reorganized them all so they are easier to compare
[12:17] <jdstrand> (well, I didn't reorganize lxc, I reorganized libvirt-lxc and docker)
[12:18] <jdstrand> I can verify the changes in the new uploads
[12:23] <pfsmorigo> infinity: tks man. I'm testing daily right now. let's see
[12:23] <pfsmorigo> infinity: what timezone are you?
[12:29] <pfsmorigo> infinity: it worked. daily image installed fine here. tks
[12:29] <pfsmorigo> apw: ^
[13:35] <apw> pfsmorigo, he is of indeterminate timezone at best :), glad that fixed it, thanks for letting us know
[13:36] <pfsmorigo> apw: hehe
[13:36] <apw> jamespage, i think you just caught it in the copy phase from one pocket to the other, as the removal happens immediatly and the arrival happens when the next publisher completes (approximatly)
[13:38] <apw> jamespage, no ignore me, i read the numbers wrong
[13:51] <jamespage> apw, yeah - I had to double take - I've not seen that before
[13:52] <jamespage> maybe infinity or wgrant might have an idea as to where https://launchpad.net/ubuntu/utopic/+source/python-oslo.vmware/0.6.0-1ubuntu2 went ?
[13:54] <wgrant> jamespage: The copy was probably eaten by one of the swift outages this morning. An archive admin should be able to revive it for you.
[13:54] <jamespage> ah-ha!
[14:26] <jamespage> any archive admins around who can sort out my oslo.vmware upload that's got lost?
[14:26] <jamespage> stgraber, pitti? ^^
[14:28] <stgraber> jamespage: hmm, that's interesting
[14:28] <jamespage> stgraber, indeed
[14:29] <stgraber> ok, doing the usual copy on top of itself, hopefully that'll do the trick
[14:32] <stgraber> jamespage: ok, in theory I just copied it on top of itself, so in a publisher cycle it should show up in -proposed again, then britney should be able to get it to migrate
[14:32] <jamespage> stgraber, awesome thanks
[16:14] <bdmurray> any SRU team member I'd like to have a 2nd opinion on releasing the fix for bug 1354571 early.
[16:14] <ubot2> bug 1354571 in apport (Ubuntu Trusty) "apport-retrace ignores warnings from gdb" [Medium,Fix committed] https://launchpad.net/bugs/1354571
[16:33] <infinity> bdmurray: Perfectly reasonable.  My only question is if that's missing a powerpc64le-linux-gnu target, or if that gets covered by powerpc64.
[16:34] <infinity> Or, rather ppc64/ppc64le
[16:34] <infinity> Which looks wrong anyway, as that's not the GNU triplet. :P
[16:35] <bdmurray> infinity: hmm?
[16:36] <infinity> bdmurray: Looking at the diff, it enables "ppc64-linux-gnu", but the GNU triplet for ppc64 is powerpc64-linux-gnu (and the triplet for ppc64el is powerpc64le-linux-gnu).  But this could be a gdb weirdness, not a packaging bug.
[16:37] <bdmurray> infinity: are we talking about apport and bug 1354571?
[16:37] <ubot2> bug 1354571 in apport (Ubuntu Trusty) "apport-retrace ignores warnings from gdb" [Medium,Fix committed] https://launchpad.net/bugs/1354571
[16:38] <infinity> bdmurray: I'm talking about switching gdb back from "all" to a static target list.
[16:38] <infinity> bdmurray: The thing you asked about 20 minutes ago. :P
[16:40] <infinity> Unfortunately, neither "ppc64-linux-gnu" or "powerpc64-linux-gnu" show up anywhere in the source except for debian/rules, so this is a bit hard to hunt.
[16:42] <infinity> bdmurray: Do we use binutils-multiarch for ppc64el retracing yet?  Would we notice if it was broken?
[16:43] <bdmurray> infinity: I'm really lost re what you are referring to. I'd didn't ask about gdb recently.
[16:44] <infinity> bdmurray: Err, you're right.  I saw "gdb" in the bug title, and then went looking at the GDB source package.  I need to wake up.
[16:45] <infinity> And, indeed, the GDB upload has a note that it regresses arm64 and ppc64el.
[16:46] <infinity> bdmurray: Looking at apport instead. :P
[16:46] <bdmurray> infinity: Okay. Yes, the gdb in trusty-proposed does need a reupload and that's in bug 1233185. The retracers are using 7.7.1-0ubuntu4 so I haven't been too concerned about that SRU.
[16:46] <ubot2> bug 1233185 in gdb (Ubuntu Trusty) "gdb-multiarch cannot read ARM cores: "wrong size gregset struct in core file"" [High,Triaged] https://launchpad.net/bugs/1233185
[16:47] <infinity> bdmurray: apport looks fine.
[16:51] <bdmurray> infinity: thanks
[17:34] <barry> any ~ubuntu-release have a few moments to review LP: #1376736?
[17:34] <ubot2> Launchpad bug 1376736 in pycurl (Ubuntu) "[FFe] update to pycurl 7.19.5" [High,New] https://launchpad.net/bugs/1376736
[18:57] <wxl> i have a query on behalf of our wiki team. is lubuntu responsible for  https://wiki.ubuntu.com/Lubuntu/Announcement/XX.YY or is that something the general release team takes care of?
[18:59] <knome> wxl, you're responsible for your own announcements yourself, the release team only does the general ones
[19:00] <wxl> cool thanks knome
[19:00] <knome> np
[20:26] <jamespage> stgraber, hmm - oslo.vmware -1ubuntu2 does not appear to have re-appeared in proposed - is it easier for me to just upload a 1uubntu3 with the same content?
[20:35] <infinity> jamespage: Reappear?
[20:36] <jamespage> infinity, 1ubuntu2 disappeared between building in proposed and migrating to release pockts
[20:36] <infinity> jamespage: What source package is this?
[20:36] <jamespage> infinity, python-oslo.vmware
[20:37] <jamespage> infinity, https://launchpad.net/ubuntu/+source/python-oslo.vmware/0.6.0-1ubuntu2
[20:37] <infinity> Looks like the copy fell to the librarian outage.  I'll just recopy it.  Sec.
[20:39] <infinity> jamespage: https://launchpad.net/ubuntu/+source/python-oslo.vmware/0.6.0-1ubuntu2/+publishinghistory
[20:39] <infinity> jamespage: There, it has a pending publishing record now.
[20:40] <infinity> jamespage: Will fix itself shortly.
[20:40] <jamespage> infinity, thankyou - wgrant indicated it was probably due to that outage
[22:27] <jdstrand> infinity: fyi, there is one mount rule added to lxc alpha2 over what I uploaded
[22:28] <jdstrand> so, the libvirt-lxc and docker.io profiles could get that I suppose
[22:28] <jdstrand> I'll follow up with hallyn and stgraber tomorrow and see why it was added
[22:30] <hallyn> which rule is that i wonder