[05:58] <Noldorin_> hi wgrant
[05:58] <Noldorin_> (if you're around)
[06:42] <wgrant> Noldorin_: Hi.
[06:59] <Noldorin_> wgrant, was just going to ask: what is special about the Trunk series that bug tasks can be switched to it?
[07:03] <Noldorin_> wgrant, Trunk is special as a name or something else?
[07:08] <wgrant> Noldorin_: It's not a special name. Just whichever series is set as the development focus.
[07:10] <Noldorin_> wgrant, and there's only one development focus, correct
[07:10] <Noldorin_> ?
[07:10] <wgrant> Noldorin_: Right.
[07:11] <Noldorin_> ok...
[07:13] <Noldorin_> wgrant, so to confirm: series bug tasks for bag ports, trunk bug tasks for nothing, and project bug tasks for all bugs?
[07:13] <Noldorin_> ("won't fix" should undo the Trunk task...)
[07:29] <wgrant> Noldorin_: Pretty much, yep/.
[07:29] <Noldorin_> wgrant, ah good. sorry, remind me how Trunk bugs are sometimes used.../
[07:33] <wgrant> Noldorin_: Ubuntu uses them to track bugs of interest to a particular release.
[07:43] <Noldorin_> wgrant, ah yes...but if they're for a particular release, surely they should be assigned a *release series* (rather than Trunk) task?
[07:49] <Noldorin_> wgrant, Trunk seems inappropaite in that case
[07:55] <Noldorin_> meh
[07:56] <Noldorin_> wgrant, well i'm off now, but feel free to ping me when i'm back tomorrow :-)
[07:59] <wgrant> Noldorin_: Ubuntu doesn't have a trunk series.
[07:59] <wgrant> Noldorin_: The development focus is the development release.
[08:01] <Noldorin_> wgrant, ohh ok
[08:01] <Noldorin_> wgrant, so given that i *do* have a Trunk series it makes zero sense to target to Trunk then...
[08:01] <Noldorin_> i think
[11:00] <Laney> why did https://lists.ubuntu.com/archives/oneiric-changes/2011-July/005553.html not get a changesfile?
[11:21] <wgrant> Laney: We don't have the Debian changes files.
[11:22] <Laney> wgrant: it was one of the new syncs?
[11:22] <wgrant> Laney: Yes.
[11:22] <wgrant> That's why the changelog is terrible.
[11:23] <Laney> ah, and previously AA syncs weren't announced to -changes
[11:23] <wgrant> Well, AA syncs had fake changes files.
[11:24] <wgrant> They were done pretty much identically to that script some MOTU use :)
[11:24] <Laney> yeah. I was just wondering if my UDD (as in Debian's UDD) data was going to regress because of this.
[11:24] <wgrant> But now these are done using native Soyuz package copies, from an import of the Debian archive.
[11:24] <wgrant> Hmm.
[11:24] <Laney> but if syncs were never in -changes, then it won't
[11:25] <wgrant> Autosyncs never were, right.
[11:25] <Laney> requestsyncs were?
[11:25] <wgrant> Yes.
[11:25] <Laney> hmm.
[11:25] <wgrant> You should probably use the API rather than -changes.
[11:26] <wgrant> APIs like getPublishedSources provide all publications, not just those that are announced :)
[11:28] <Laney> yeah, that would simplify matters.
[11:29] <wgrant> The other UDD already uses getPublishedSources for similar purposes.
[11:35] <Laney> I need to be able to get at least this data http://paste.debian.net/124665/
[19:16] <Noldorin> hi wgrant ... i think i lost connection yesterday. was just saying/confirming that "Status tracked in Trunk" is fairly useless as a bug task.
[19:52] <lifeless> Noldorin: it depends on the project whether thats particularly useful or not
[19:53] <lifeless> Noldorin: ubuntu (and some other projects) change their trunk every release, and status tracked in trunk means that the bugs stay linked to the old trunk when that change occurs
[19:59] <Noldorin> lifeless, but Trunk in their case is actually a release series right?
[19:59] <Noldorin> lifeless, in my case it's devel
[20:01] <lifeless> yes
[20:35] <Noldorin> lifeless, sorry, got disconnected there
[20:35] <Noldorin> did you respond?
[20:35] <lifeless> I did.
[20:35] <lifeless> I said 'yes'
[20:36] <Noldorin> lifeless, oh good. so i think i'm clear on things now
[20:36] <Noldorin> lifeless, by the way, will the ability to delete bug targets be coming at some point? :-)
[20:36] <lifeless> maybe
[20:36] <lifeless> (sorry I cannot be more definite yet)
[20:37] <Noldorin> that's ok
[20:37] <Noldorin> lifeless, at least it's under consideration
[20:37] <Noldorin> lifeless, for now, setting to "Won't Fix" does the job i believe.
[20:54] <Noldorin> lifeless, ?
[21:03] <lifeless> Noldorin: yes?
 lifeless, for now, setting to "Won't Fix" does the job i believe.
[21:03] <Noldorin> sorry, that was an (implicit) question :-)
[21:09] <lifeless> Noldorin: what job ?
[21:10] <Noldorin> lifeless, oh. it's an idiom in English. sorry, assumed you were a native speaker.
[21:15] <lifeless> Noldorin: I am, but I'm not clear what you are asking.
[21:17] <Noldorin> lifeless, oh. setting a bug target to "won't fix" should restore the project itself as the bug target - correct?
[21:17] <lifeless> I don't know. Try it.
[21:18] <lifeless> Its a conjoined master, so I would expect it to change the project task as well.
[21:18] <Noldorin> ok
[21:18] <Noldorin> will do
[21:20] <jo-erlend> I've started a Norwegian channel for Python developers and I'd like to create a little stronger organization than an IRC channel provides. I thought perhaps a Launchpad team would be the way to go. That way we can setup a mailinglist, add a bazaar branch for translating tutorials and such, right? It's not necessary to create a project as well?
[21:27] <lifeless> jo-erlend: you need a project if you want bugs|gettext translations|a dedicated branch namespace
[21:27] <lifeless> jo-erlend: if you don't need any of those, you don't need a project
[21:31] <Noldorin> lifeless, seems to work yes :-)
[21:34] <jo-erlend> lifeless, great. I'm registering a team. It asks me for the subscription policy and says an open team cannot have PPAs. This can be changed at a later time, yes?
[21:38] <lifeless> jo-erlend: the team can be made non-open later
[21:39] <Noldorin> lifeless, lastly, how can i view closed bugs in LP?
[21:39] <lifeless> do you mean find them ?
[21:40] <Noldorin> lifeless, view a list of them
[21:40] <lifeless> advanced byug search
[21:40] <Noldorin> thanks
[22:01] <jo-erlend> why can't I set my own email address as the contact address for a team I've created?
[22:10] <maxb> I think because Launchpad expects email addresses to uniquely identify people, and it considers teams to be "people" too
[22:21] <lifeless> jo-erlend: the contact address identifies mail *from* people as well as *to* peple.
[22:24] <jo-erlend> lifeless, I don't understand what that means.
[22:26] <lifeless> jo-erlend: we cannot have the same email address twice in the system, or we cannot determine who to use for checking permissions, signatures etc when someone sends a mail to a bug/question/blueprint etc
[22:30] <jo-erlend> ah.
[22:31] <jo-erlend> so we have to setup a separate email account if we want one person to handle those kinds of notifications?
[22:32] <lifeless> this is about mail coming *into* launchpad
[22:32] <lifeless> normally you won't want a contact address on LP teams.
[22:32] <lifeless> what are you trying to achieve?
[22:38] <jo-erlend> how do I delete an active poll? I just wanted to test something sine I hadn't done it before, but I messed it up and now it won't go away! :)
[22:39] <jo-erlend> lifeless, nothing special, really. But if there is lots of routine launchpad technical stuff, then I want to handle that for the team so the mailinglist doesn't get spammed with uninteresting stuff for the other members.
[22:41] <lifeless> if the team is assigned to a task, then the members of the team are notified
[22:42] <lifeless> if the team has a new member requested etc, then the admins are notified
[22:42] <lifeless> it should all Just Work in a sane way.
[22:42] <lifeless> don't try to fine tune until you have some experience ;)
[22:44] <jo-erlend> lifeless, that's a good advise. :)
[22:44] <poolie> hi lifeless, all
[22:45] <lifeless> hi poolie
[22:45] <jo-erlend> lifeless, ok. So we have a team, and are now two members. We would like to have a place to track plans and ideas for how to grow the community. I thought that could be done using bugs and blueprints. Then it makes sense to create a project called python-no-community for instance and add the team to it?
[22:46] <lifeless> sure
[22:47] <lifeless> note that you probably want to make the team a bug supervisor, otherwise lp will mail the project owner on every bug change no matter what
[22:49] <jo-erlend> thanks.
[22:49] <jo-erlend> can I change the title for a project at a later time?
[22:50] <lifeless> yes
[23:10] <jo-erlend> is translations only meant for short strings in applications, or can it be used to translate manuals and such as well?
[23:12] <lifeless> its basically gettext
[23:20] <jo-erlend> lifeless, yes, but that doesn't really answer my question.
[23:21] <lifeless> well, gettext is designed for short strings
[23:35] <superm1> hey launchpad guys, could you comment on this error that our automated build bot was spitting out on it's dput: http://paste.ubuntu.com/655933/
[23:35] <superm1> the file signing stuff hasn't changed at all, and it worked for the build right before that
[23:36] <lifeless> its probably our intermittent gpg bug
[23:36] <lifeless> the upload should have gone through
[23:36] <lifeless> bug 798957
[23:37] <superm1> yeah checking the PPA, the upload did go through, but the uploads that were supposed to happen after that didn't happen because of the non-zero exit on dpu
[23:37] <superm1> ok