[13:32] <arges> is there any way to target an ubuntu package to a series if its in this state -> bug 1386524 (trying to target to vivid)
[13:37] <rbasak> Is that the Launchpad bug where if you delete a bug task it's gone forever?
[13:38] <arges> rbasak: yea, i'm not sure if the vivid task was deleted or just the development task... but maybe its a similar 'feature'
[13:38] <rbasak> Looks like they all were
[13:38] <rbasak> AIUI there's no way out of that.
[13:38] <rbasak> Not sure what the bug reference is for this issue.
[13:38] <rbasak> It has Affected Me Too.
[13:39] <rbasak> Once you know, you can never delete bug tasks (Invalidate them instead) as a pre-workaround.
[13:39] <rbasak> But it doesn't work unless everyone knows not to do it, which they don't.
[13:42] <cjwatson> In [2]: lp.bugs[1386524].addTask(target='/ubuntu/vivid/+source/valgrind')
[13:42] <cjwatson> Out[2]: <bug_task at https://api.launchpad.net/devel/ubuntu/vivid/+source/valgrind/+bug/1386524>
[13:42] <cjwatson> done
[13:42] <arges> cjwatson: thanks!
[13:43] <cjwatson> I can't remember if that works in all situations, but it's useful enough to work around at least some UI problems
[13:45] <arges> cjwatson: good to know, adding to my bag of tricks
[14:09] <rtg> infinity, linux (wily) in the unapproved queue
[14:25] <smoser> can someone review my curtin upload please ? https://launchpad.net/ubuntu/wily/+queue?queue_state=1&queue_text=curtin . pretty simple. fixes busted install.
[14:34] <infinity> rtg: Accepted and heading to bed, I'll check on it when I wake up to see if anything asploded.
[14:34] <rtg> infinity, ack
[15:34] <arges> cyphermox: hi looking at the multipath-tools upload for trusty, does that fix the failures seen in the -proposed version?
[15:35] <arges> cyphermox: bug 1468897, does multipath -l work?
[15:36] <cyphermox> arges: yes, that's the point of that new upload :)
[15:36] <arges> cyphermox: ok, wasn't exactly clear. which is why I was asking
[15:36] <cyphermox> I can go do it again right now if you want
[15:37] <arges> cyphermox: well you'll have to just re-verify it when it hits -proposed
[15:37] <cyphermox> yep
[15:37] <arges> cyphermox: cool thanks, i'll review that again soon
[15:38] <cyphermox> arges: http://paste.ubuntu.com/12705401/
[15:38] <cyphermox> no worries, when it gets to -proposed I and others will review/and verify it again
[15:39] <arges> cyphermox: great! ok
[18:40] <davmor2> infinity, cyphermox: did we get a final yay or neigh to wubi removal?
[18:41] <cyphermox> don't look at me, I'm not release-team :)
[18:41] <davmor2> cyphermox: oh fair enough over to infinity then
[18:44] <cyphermox> I think he's sleeping for now, it may be a while before he responds
[18:45] <davmor2> cyphermox: damn him and his different timezone ;)
[18:53] <cyphermox> there is no such thing as a timezone :)
[18:58] <slangasek> bdmurray: hmm, does adding the sssd team to package-subscribers imply this team is a recognized subscribing team for MIR purposes?
[19:08] <bdmurray> slangasek: Yes
[19:10] <slangasek> bdmurray: ok.  that seems dubious to me; it's a team with only two people and doesn't map to anything that's accountable to either Ubuntu (flavor teams) or Canonical (company teams)
[19:10] <slangasek> I mean, we already have problems with some of the existing ownership mappings, I don't think we need to make it worse by introducing even more specialized teams :)
[19:14] <bdmurray> I see your point.
[19:17] <bdmurray> I'll dig into why I added them, it was a bit ago.
[19:30] <slangasek> bdmurray: ok
[22:21] <bdmurray> slangasek: fwiw bug 1491263 is the MIR that used the sssd team
[23:11] <slangasek> bdmurray: hrm ok
[23:31] <slangasek> bdmurray: and the original sssd MIR was https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/903752 - before we had the "must have subscriber" but, I think?
[23:42] <bdmurray> slangasek: yes, that sounds right