[00:08] <bdmurray> slangasek: does ./sru-review -s trusty rsyslog work for you?
[00:09] <bdmurray> slangasek: obviously it doesn't for me and neither does python-apt
[00:17] <slangasek> checking
[00:18] <slangasek> ERROR: Queue does not have an upload of this source.
[00:19] <slangasek> and that appears to be true
[00:19] <slangasek> bdmurray: ^^
[00:20] <bdmurray> appears to be true?
[00:21] <bdmurray> https://launchpad.net/ubuntu/trusty/+queue?queue_state=1
[00:26] <bdmurray> slangasek: ^^
[00:27] <slangasek> bdmurray: ah, note that the pocket is 'updates', not 'proposed'
[00:27] <slangasek> bdmurray: I didn't think to look in that one ;P
[00:27] <slangasek> since nobody's supposed to upload to it :)
[00:28] <bdmurray> I thought it wasn't supposed to be possible
[00:29] <slangasek> I think it's supported on the launchpad side in case of emergencies, but by policy things land in the unapproved queue and get rejected at the border
[00:29] <slangasek> or maybe they're supposed to be automatically redirected to -proposed at upload time?
[00:29] <slangasek> cjwatson, wgrant: ^^ ?
[00:29] <RAOF> I'm pretty sure they're automatically redirected at upload time
[00:29] <bdmurray> that's what I thought
[00:29] <slangasek> well, in this case they weren't
[00:30] <slangasek> perhaps because bdmurray was the uploader and he's an AA?
[00:30] <bdmurray> I'm not in AA
[00:30] <bdmurray> s/in/an/
[00:30] <bdmurray> ;-)
[00:30] <slangasek> then maybe because bdmurray was the uploader and he's in sru-team? ;)
[00:31] <RAOF> bdmurray: You're in ~ubuntu-archive, though, right?
[00:31] <bdmurray> I uploaded rsyslog to utopic and it went to proposed
[00:31] <RAOF> IIRC Launchpad can't tell the difference :)
[00:33] <slangasek> bdmurray: the utopic upload has 'utopic' as the upload target, the trusty upload has 'trusty-updates'
[00:33] <slangasek> so possibly the redirect only exists for release->proposed, not updates->proposed
[00:34] <slangasek> anyway, seems like you want to reupload to -proposed, and we'll let the LP guys adjudicate the question of what should have happened here
[00:34] <bdmurray> should we leave the updates one for them?
[00:34] <wgrant> slangasek: release is redirected to proposed
[00:34] <wgrant> updates never was
[00:35] <slangasek> wgrant: ok.  should it be?
[00:35] <slangasek> I think the existing policy exists on the grounds that in an emergency we might want to bypass -proposed
[00:36] <wgrant> Well, the existing policy exists on the grounds that uploads go where we're asked to put them.
[00:36] <wgrant> Except in the case where DistroSeries.redirect_release_uploads is set, usually on a development series.
[00:36] <slangasek> which "we" and who's asking ;)
[00:36] <wgrant> "we" == Launchpad :)
[00:37] <wgrant> The .changes' Distribution field is doing the asking.
[00:37] <wgrant> Now, one could argue that the same logic makes sense for -updates
[00:39] <wgrant> But then you have -backports, eventually -security, etc.
[00:40] <wgrant> The rule today is very explicitly that release, and only release, can be automatically overridden to proposed.
[00:40]  * slangasek nods
[00:40] <slangasek> and that's as much because the release pocket is frozen as anything
[00:40] <wgrant> And that works because pre-release series are simple and only really have one upload target
[00:40] <slangasek> that too
[00:40] <slangasek> so I think the current policy should stand
[00:42] <wgrant> I agree. It's moderately inconsistent, but probably less inconsistent and confusing than the alternative.
[00:43] <wgrant> (until we have eg. -security-proposed)
[00:43] <slangasek> that's called the security ppa, surely ;)
[14:44] <jamespage> the swift upload that I did before christmas appears to be stuck in proposed waiting for DEP-8 tests to complete - which AFAICT they have done.
[14:44] <jamespage> could someone with more knowledge or poke powers take a look please?
[16:47] <Riddell> who would know why marble isn't paying attention to my hint? "jriddell:force-badtest marble/4:14.12.0-0ubuntu2" http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#marble
[16:55] <Laney> Riddell: http://people.canonical.com/~ubuntu-archive/proposed-migration/log/vivid/2015-01-08/16:53:43.log has the answer
[16:58] <Riddell> ooh it's that kitterman chap
[16:58] <Laney> wily little tyke
[18:18] <bdmurray> slangasek: it looks like libsignon-glib was mistakenly uploaded to the proposed queue and approved for Trusty see bug 1382843 comment #28. Could you remove it?
[18:21] <slangasek> bdmurray: done