[05:58] hi wgrant [05:58] (if you're around) [06:42] Noldorin_: Hi. [06:59] wgrant, was just going to ask: what is special about the Trunk series that bug tasks can be switched to it? [07:03] wgrant, Trunk is special as a name or something else? [07:08] Noldorin_: It's not a special name. Just whichever series is set as the development focus. [07:10] wgrant, and there's only one development focus, correct [07:10] ? [07:10] Noldorin_: Right. [07:11] ok... [07:13] wgrant, so to confirm: series bug tasks for bag ports, trunk bug tasks for nothing, and project bug tasks for all bugs? [07:13] ("won't fix" should undo the Trunk task...) [07:29] Noldorin_: Pretty much, yep/. [07:29] wgrant, ah good. sorry, remind me how Trunk bugs are sometimes used.../ [07:33] Noldorin_: Ubuntu uses them to track bugs of interest to a particular release. [07:43] 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] wgrant, Trunk seems inappropaite in that case [07:55] meh [07:56] wgrant, well i'm off now, but feel free to ping me when i'm back tomorrow :-) [07:59] Noldorin_: Ubuntu doesn't have a trunk series. [07:59] Noldorin_: The development focus is the development release. [08:01] wgrant, ohh ok [08:01] wgrant, so given that i *do* have a Trunk series it makes zero sense to target to Trunk then... [08:01] i think === Philip6 is now known as Philip5 [11:00] why did https://lists.ubuntu.com/archives/oneiric-changes/2011-July/005553.html not get a changesfile? [11:21] Laney: We don't have the Debian changes files. [11:22] wgrant: it was one of the new syncs? [11:22] Laney: Yes. [11:22] That's why the changelog is terrible. [11:23] ah, and previously AA syncs weren't announced to -changes [11:23] Well, AA syncs had fake changes files. [11:24] They were done pretty much identically to that script some MOTU use :) [11:24] yeah. I was just wondering if my UDD (as in Debian's UDD) data was going to regress because of this. [11:24] But now these are done using native Soyuz package copies, from an import of the Debian archive. [11:24] Hmm. [11:24] but if syncs were never in -changes, then it won't [11:25] Autosyncs never were, right. [11:25] requestsyncs were? [11:25] Yes. [11:25] hmm. [11:25] You should probably use the API rather than -changes. [11:26] APIs like getPublishedSources provide all publications, not just those that are announced :) [11:28] yeah, that would simplify matters. [11:29] The other UDD already uses getPublishedSources for similar purposes. [11:35] I need to be able to get at least this data http://paste.debian.net/124665/ === Mkaysi_ is now known as Mkaysi === warp11 is now known as warp10 [19:16] 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] Noldorin: it depends on the project whether thats particularly useful or not [19:53] 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] lifeless, but Trunk in their case is actually a release series right? [19:59] lifeless, in my case it's devel [20:01] yes [20:35] lifeless, sorry, got disconnected there [20:35] did you respond? [20:35] I did. [20:35] I said 'yes' [20:36] lifeless, oh good. so i think i'm clear on things now [20:36] lifeless, by the way, will the ability to delete bug targets be coming at some point? :-) [20:36] maybe [20:36] (sorry I cannot be more definite yet) [20:37] that's ok [20:37] lifeless, at least it's under consideration [20:37] lifeless, for now, setting to "Won't Fix" does the job i believe. [20:54] lifeless, ? [21:03] Noldorin: yes? [21:03] lifeless, for now, setting to "Won't Fix" does the job i believe. [21:03] sorry, that was an (implicit) question :-) [21:09] Noldorin: what job ? [21:10] lifeless, oh. it's an idiom in English. sorry, assumed you were a native speaker. === Quintasan_ is now known as Quintasan [21:15] Noldorin: I am, but I'm not clear what you are asking. [21:17] lifeless, oh. setting a bug target to "won't fix" should restore the project itself as the bug target - correct? [21:17] I don't know. Try it. [21:18] Its a conjoined master, so I would expect it to change the project task as well. [21:18] ok [21:18] will do === yofel_ is now known as yofel [21:20] 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] jo-erlend: you need a project if you want bugs|gettext translations|a dedicated branch namespace [21:27] jo-erlend: if you don't need any of those, you don't need a project [21:31] lifeless, seems to work yes :-) [21:34] 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] jo-erlend: the team can be made non-open later [21:39] lifeless, lastly, how can i view closed bugs in LP? [21:39] do you mean find them ? [21:40] lifeless, view a list of them [21:40] advanced byug search [21:40] thanks === med_out is now known as medberry [22:01] why can't I set my own email address as the contact address for a team I've created? [22:10] I think because Launchpad expects email addresses to uniquely identify people, and it considers teams to be "people" too [22:21] jo-erlend: the contact address identifies mail *from* people as well as *to* peple. [22:24] lifeless, I don't understand what that means. [22:26] 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] ah. [22:31] so we have to setup a separate email account if we want one person to handle those kinds of notifications? [22:32] this is about mail coming *into* launchpad [22:32] normally you won't want a contact address on LP teams. [22:32] what are you trying to achieve? [22:38] 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] 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] if the team is assigned to a task, then the members of the team are notified [22:42] if the team has a new member requested etc, then the admins are notified [22:42] it should all Just Work in a sane way. [22:42] don't try to fine tune until you have some experience ;) [22:44] lifeless, that's a good advise. :) [22:44] hi lifeless, all [22:45] hi poolie [22:45] 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] sure [22:47] 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] thanks. [22:49] can I change the title for a project at a later time? [22:50] yes [23:10] is translations only meant for short strings in applications, or can it be used to translate manuals and such as well? [23:12] its basically gettext [23:20] lifeless, yes, but that doesn't really answer my question. [23:21] well, gettext is designed for short strings [23:35] 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] the file signing stuff hasn't changed at all, and it worked for the build right before that [23:36] its probably our intermittent gpg bug [23:36] the upload should have gone through [23:36] bug 798957 [23:36] Launchpad bug 798957 in Launchpad itself "Uploads are seemingly (but not actually) rejected" [Critical,Triaged] https://launchpad.net/bugs/798957 [23:37] 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] ok