[07:34] <plashenkov> infinity: Hello, Adam! Could you please tell when https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1574693 will be available in updates?
[08:39] <jamespage> please could a member of the SRU team look at https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1585660
[08:40] <jamespage> I really want to get the latest point release into Xenial before we get to many people using the 10.2.0 from release ...
[09:14] <infinity> plashenkov: Now.
[09:23] <tsimonq2> infinity: thanks a lot for getting those fixes approved, that splash screen one has been annoying ;)
[09:23] <tsimonq2> (teh bug, not the fix)
[10:37] <Trevinho> pitti: hey, could you check the SRU packages that are waiting in SRU queue as per ticket https://requests.ci-train.ubuntu.com/#/ticket/1614 ?
[11:11] <pitti> Trevinho: can you please try to ping some other SRU team members today? I've been doing pretty much all the SRU work recently, and it's taking up too much time, to be brutally honest
[11:12] <pitti> (or I might do some stuff in the evening, but please start with the roster at https://wiki.ubuntu.com/StableReleaseUpdates#Publishing)
[11:19] <Trevinho> pitti: yeah, I undestand... Thanks
[11:21] <Trevinho> bdmurray: hey, can you check the SRU queue for unity7 stack? It's quite important for .1. Changes are in ticket https://requests.ci-train.ubuntu.com/#/ticket/1614
[13:48] <sergiusens> slangasek pitti our snapcraft adt tests on yakkety are being hit by https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1599799 is there a way to tag/comment on update_excuses about this and let it in?
[13:49] <pitti> sergiusens: technically yes, but we don't actually know yet what is broken
[13:50] <pitti> sergiusens: 2.0.2's tests still succeed, and there has not been any investigation yet whether it's the tests that regressed or snapd itself
[13:50] <pitti> and the error suggests the latter, i. e. we should not let a broken version in
[13:50] <sergiusens> pitti yeah, I am sad to be affected by taking the extra mile wrt testing :-P
[13:51] <sergiusens> pitti oh, I don't want snapd in, just snapcraft, one of the adt tests fail on a part of the test where we `snap install/remove`
[13:52] <pitti> sergiusens: oh! so this actually confirms that bug 1599799 is not a test issue, but an actual bug
[13:53] <pitti> sergiusens: OTP, back in 10
[13:53] <pitti> sergiusens: will hint that
[13:55] <pitti> sergiusens: done
[14:03] <sergiusens> thanks
[14:13] <jbicha> infinity: if you're doing sru work today, could you look into accepting drupal7 from unapproved?
[14:29] <apw> jbicha, i believe he is travelling
[14:30] <jbicha> oh, makes sense
[14:30]  * apw hands pitti a gold star to put on ADTs wall
[14:30] <pitti> sergiusens: it landed
[14:30] <pitti> apw: oh, thanks :)
[14:31] <xnox> rtg, thank you! you are amazing =)
[14:32] <rtg> xnox, for what ?
[14:32] <pitti> is it "say thanks to the developer next to you" day or something such? :-)
[14:36] <xnox> rtg, for linux bug updates about qeth driver removal.
[14:37] <davmor2> apw: don't flash shiny things in front of pitti he won't be able to concentrate on anything else for the rest of the day
[14:37] <rtg> xnox, I just did 'qeth: delete napi struct when removing a qeth device'. Is that what you are talking about ?
[14:38] <xnox> yeah =)
[14:38] <pitti> davmor2: you mean like that big yellow hot plasma ball on the sky that has been burning my brains for two weeks now? :-)_
[14:40]  * davmor2 looks outside nope nothing but grey up there I think pitti is obviously at an amusement park and not working at all
[14:41] <pitti> davmor2: I see my prejudices about British weather confirmed :)
[14:45] <ogra_> pitti, the german weather isnt better ...  northern of the weisswurstgrenze at least
[14:45] <davmor2> pitti: http://dailypicksandflicks.com/wp-content/uploads/2012/06/In-the-Bible-it-rained-for-40-days-they-called-it-a-disaster.-In-England-we-call-it-summer..jpg
[14:46] <ogra_> you are just lucky to have that little hole in the clouds sitting above you for a few more hours
[15:36] <davmor2> pitti: https://www.youtube.com/watch?v=r35NSTwOxw4 head for about 2 minutes in :)
[17:32] <bdmurray> Trevinho: so bamf, compiz, libunity, nux, unity, unity-control-center, and unity-lens-applications in the xenial queue?
[17:35] <bdmurray> Trevinho: oh its in the ticket to which you linked
[17:51] <sergiusens> bdmurray mind letting snapcraft into xenial-proposed while at it?
[17:59] <bdmurray> sergiusens: I'll add it to the list
[18:02] <sergiusens> bdmurray ty
[18:36] <bdmurray> Trevinho: bug 1304388 is missing proper SRU information, I'll still let unity-control-center in but would like to see the bug fixed up.
[18:39] <jbicha> bdmurray: if you have time today, could you look into letting drupal7 in for xenial?
[18:41] <jbicha> to be more specific, drupal7 is already in -proposed but I uploaded a new version a few weeks ago with an extra dependency it needs
[20:02] <slangasek> vsearch excuses make no sense; vsearch-data isn't listed in the source package for vsearch in -proposed, it's only present in the yakkety version.  what's going on? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#vsearch
[20:05] <nacc_> slangasek: maybe i've always misinterpreted that style of output, but i thought it meant there was a binary package in 1.1.3+dfgs-1 but that is no longer present in 2.0.0-1?
[20:07] <slangasek> nacc_: that should certainly not be the meaning; it's valid for a new version of a source package to drop a binary package, it's only an error if a) the dropped binary package is still present in -proposed at an older version, or b) the maintainer did something wrong in debian/control to imply the package *should* still be built but isn't being built
[20:09] <slangasek> in this case I'll trick proposed-migration by removing vsearch-data early from yakkety, since it has no revdeps
[20:09] <slangasek> but that should not be required
[20:09] <nacc_> slangasek: hrm, your points make sense to me, I've just only seen it for cases like I described -- i defer to your knowledge in this case :)
[20:10] <slangasek> there are other weird things in update_output that I think I need a pitti to help diagnose
[20:31] <slangasek> pitti: ignoring test failures on s390x for something as critical as nova is a false optimization; please escalate this issue to xnox instead of overriding
[20:34] <slangasek> ah, so vsearch has a test dep on vsearch-data, I wonder if that could be it
[23:18] <xnox> slangasek, pitti - wait what where how?
[23:18] <xnox> we are like telling a few people that it is all good and dandy.
[23:18] <xnox> (nova and openstack in general)
[23:18] <slangasek> xnox: nova autopkgtests are flaky (at best) on s390x
[23:19] <slangasek> xnox: so, please fix so that pitti doesn't ignore failures ;)
[23:20] <xnox> i wonder if they are there because of lxd vs kvm runner.
[23:20] <xnox> or because they are indeed flaky
[23:20] <slangasek> they have sometimes succeeded
[23:21] <xnox> not tonight however, as i am about to hit the bed, and only got distracted by the l1cc email =)
[23:21] <xnox> (which imho i should have written whilst in cape town)