[00:04]  * wgrant likes the new picker widget.
[00:11] <kiko> wgrant, where did you see it? neat!
[00:19] <intellectronica> kiko: https://edge.launchpad.net/launchpad/+edit-people
[00:20] <intellectronica> ho ho ho, it's quite buggy, though
[00:26] <wgrant> intellectronica: I never tried a second search, it seems. Now I see the problem.
[00:26] <wgrant> Ah, it's just for big searches.
[00:26] <intellectronica> wgrant: yes. filed bug #358815
[00:26] <wgrant> It feels like it should automatically search.
[00:27] <intellectronica> but otherwise it's really gorgeous
[00:27] <wgrant> Maybe after a little timeout without typing.
[00:27] <intellectronica> wgrant: i think that will happen too at some point. the problem with doing that is that you need to plan carefully in order to not hammer the server
[00:27] <wgrant> But I guess the request is a bit slow.
[00:27] <wgrant> Right.
[00:27] <intellectronica> but that's definitely coming
[00:28] <wgrant> When does the bug page get AJAXed?
[00:29] <intellectronica> wgrant: most of it will happen next week
[00:29] <wgrant> Ooh.
[00:29] <intellectronica> it got slightly delayed because of performance week, but that and +filebug are what we're going to be doing for the rest of the cycle
[06:40] <superm1> hi guys.  for a universe package, is my translation .pot pulled out of my package automatically during build? https://translations.edge.launchpad.net/ubuntu/jaunty/+source/mythbuntu-control-centre I don't see anywhere to upload the pot manually
[06:56] <wgrant> superm1: No - only main (and possibly restricted) can be translated through Launchpad.
[07:00] <superm1> wgrant, somehow some exception was made for this package, because translation templates were uploaded at some point
[07:01] <superm1> the resultant translations need to be manually exported from LP and imported into the package
[07:01] <persia> superm1, Were the translations perhaps part of a project other than Ubuntu?
[07:02] <superm1> take a look at that URL i posted
[07:02] <superm1> "Template "mythbuntu-control-centre" in Ubuntu Jaunty package "mythbuntu-control-centre""
[07:05] <persia> Right: I was more wondering if they lived somewhere else once, and got manually moved.
[07:06] <superm1> not that i'm aware
[07:09] <wgrant> It doesn't look like it was ever imported.
[07:09] <wgrant> Which seems impossible.
[07:10] <persia> It's certainly outside of common experience
[07:10] <lifeless> why don't we translate universe ?
[07:10] <wgrant> lifeless: Because langpacks are a hard problem.
[07:11] <wgrant> lifeless: Each language is currently distributed in just a couple of binary packages, and if universe was to be included in those they would be very big.
[07:11] <wgrant> It remains to be seen whether Debian's tdebs will solve this problem well.
[07:11] <persia> And if we split it into lots of packages, it gets very confusing.
[07:12] <superm1> i'd personally be fine with keeping translations for individual packages in those packages for universe
[07:12] <superm1> that's what we do with mythbuntu-control-centre (well when it works right...)
[07:12] <persia> superm1, The problem there is that users end up with extra translations on-disk for languages they don't use.  In well-translated packages, this can become large.
[07:12]  * wgrant snoops at build logs.
[07:14] <lifeless> persia: then they shouldn't install languages they don't use :)
[07:15] <wgrant> lifeless: Then you need a package for every package-language, which is... insane.
[07:15] <wgrant> But that would be the ideal solution.
[07:15] <persia> lifeless, See, that's the balance: either translation data comes with binaries, in which case users end up with extra languages, or translations are split by language, which makes the translations data large for any given language, and the number of useful strings small.
[07:15] <persia> wgrant, Isn't tdebs a variant on that line of thought?
[07:15] <wgrant> persia: IIRC tdebs is all languages in one.
[07:15] <wgrant> But one per package.
[07:16] <wgrant> And updateable without a source upload.
[07:16] <wgrant> So it's not much better than the current situation in Debian and universe.
[07:16] <wgrant> Just a little more easily and cheaply updateable.
[07:16] <persia> Huh?  Based on http://www.emdebian.org/emdebian/langupdate.html I thought it was one tdeb per package/language combination.
[07:17] <persia> Or are emdebian tdebs different?
[07:17]  * wgrant is looking at emails.
[07:18] <wgrant> DEP-4 is the spec.
[07:18] <persia> Ah, I found a chart.  emdebian is per locale, but the big spec is per-source.
[07:18] <wgrant> Right.
[07:18] <wgrant> And I can't get to DEP-4 at the moment...
[07:18] <wgrant> That does make sense, though.
[07:18] <persia> http://people.debian.org/~codehelp/tdeb/ is a draft, I think.
[07:19] <wgrant> Looks like it.
[07:19] <persia> Anyway, I like the emdebian solution better, but it's a huge pain to manage that many little packages.
[07:19] <wgrant> Certainly.
[07:19] <wgrant> I wonder how much overhead there is in the Emdebian solution.
[07:19] <wgrant> Space-wise, I mean.
[07:20] <lifeless> Packages is not geared to handle it I suspect
[07:20] <wgrant> tdebs presumably don't have changelogs or things like that duplicated.
[07:20] <lifeless> way tooooooo much redundancy
[07:20] <wgrant> Ooh yes.
[07:20] <lifeless> but the debs themselves should be able to be a nonissue
[07:20] <persia> Well, if there's no changelog for tdebs, how do you track independent tdeb upload changes?
[07:20] <lifeless> persia: same as porter NMU's
[07:21] <persia> lifeless, I suppose, but I'm becoming convinced I'm the last person left who still reads changelogs.
[07:21] <wgrant> I guess you should know that +tN means translation changes only.
[07:22] <persia> wgrant, For source or binary upload?
[07:23] <wgrant> persia: Binary. +tN is invalid for source uploads.
[07:23] <wgrant> lifeless: It looks like tdebs aren't in Packages (or similar) files at all.
[07:24] <wgrant> Ergh:
[07:24] <wgrant> "A tdeb needs usr/share/doc/copyright and changelog.Debian and dpkg will create the necessary files, just as with a normal .deb. "
[07:24] <lifeless> wgrant: if its not in Packages, how does apt find it
[07:24] <persia> That's just ugly.
[07:25] <wgrant> lifeless: It generates the filename by looking at the binary's Translations-Version field.
[07:25] <persia> wgrant, Doesn't that imply a binary upload for each translations update?
[07:25] <wgrant> http://people.debian.org/~codehelp/tdeb/ch7.html#s7.2
[07:25] <wgrant> persia: Overrides, I suppose.
[07:25] <persia> I suppose.
[07:26] <wgrant> Although this is only the draft, and dep.debian.net seems to be missing.
[07:26] <lifeless> wgrant: ah thats why there is only one tdeb per package
[07:26] <lifeless> because its broken by design :P
[07:27] <wgrant> lifeless: I think that one tdeb per package per language would be fine with that setup, as long as the changelog doesn't have to be duplicated.
[07:28] <lifeless> wgrant: oh? how would 'current za translation tdeb be found' be satisfied
[07:29] <wgrant> lifeless: That's true.
[07:29] <wgrant> lifeless: Maybe it could be in the DDTP files.
[07:30] <lifeless> wgrant: it needs to be mirrored
[07:30] <wgrant> lifeless: Aren't the DDTP files mirrored?
[07:30] <lifeless> oh, could be
[07:31] <wgrant> They certainly should be.
[07:31] <wgrant> They are.
[07:31] <wgrant> http://mirror.pacific.net.au/ubuntu/dists/jaunty/main/i18n/Translation-ar
[07:37] <persia> In that case, perhaps it isn't so hard to manage several million tdebs, assuming one allows tdebs to contain *only* the .mo files and minimal overhead in /var/lib/dpkg/
[07:40] <wgrant> Right.
[07:40] <wgrant> persia: Do you know how Emdebian does it?
[07:40] <persia> I don't, other than from the document I linked above.
[07:40] <persia> It's just that about half the email I've seen about tdebs seems to come from Neil.
[09:41] <savvas> any progress about bug 128324 ?
[13:47] <technopagan> Hi! I had to change a project's name in LP and now the checkout on my computer isn't accepted as a branch of that project anymore... I made a new checkout already, but just out of curiosity: Is it possible to tell Bazaar that the other branch is the correct branch to use?
[13:51] <wgrant> technopagan: You could unbind and bind to the new one.
[13:54] <technopagan> wgrant: Thanks! But how will bzr know that the path is now "/foo/" instead of the old "/foobar/"?
[13:56] <wgrant> technopagan: because you told it in the bind command.
[14:03] <technopagan> wgrant: I apologize for this possibly dumb question beforehand, but I only tell bzr the local paths on my machine - How will it know that the path on LP has changed? It changed when I had to rename the project...
[14:05] <wgrant> technopagan: You need to tell 'bzr bind' the URL to bind to.
[14:05] <wgrant> When you create a checkout, it will automatically bind to the URL that you check out from.
[14:06] <wgrant> If that URL changes, you need to 'bzr unbind' and 'bzr bind lp:~user/project/branch'
[14:12] <Flimm> Where is the 'register a release' button?
[14:12] <Flimm> I can't seem to find it for some reason.
[14:18] <Flimm> ...
[14:22] <Flimm> Why do you need a milestone to register a release?
[14:25] <persia> Flimm, It's a convention: one presumably has a set of milestones, some of which are releases.
[14:25] <persia> As a benefit, one can target certain bugs to be fixed in a given release this way.
[14:26] <wgrant> As of 2.2.3, a release is a special milestone.
[14:26] <wgrant> In 2.2.4, I hear the UI will suck less.
[14:26] <persia> Of course, for those not using that sort of development method, it's a bit of overhead.
[14:26] <Flimm> OK, thank you, it makes sense now.
[14:26] <wgrant> (for example, you should be able to create a release and a milestone at the same time)
[14:27] <Flimm> I see all my old releases have been linked to completed milestones
[14:27] <persia> wgrant, Except that if one follows the method that practices having milestones, one creates the milestones in advance, and then makes some subset of them into releases later.
[14:27] <persia> (not that this makes sense for other development models)
[14:28] <wgrant> persia: In that case one doesn't use the integrated button, but creates a release from an existing milestone like one must now.
[14:29] <persia> wgrant, Right.  I should stop being an apologist.  I taught development methodology too much in the past, and some things stuck in odd ways.
[14:35] <Flimm> Where can I set a codename for a release?
[14:37] <wgrant> I can't find UI for that anywhere.
[14:38] <wgrant> sinzui: ^^
[14:41] <sinzui> Flimm: Edit the milestone, the release only contains the release notes, changelog, and files
[14:41] <wgrant> I can't see a codename field on the milestone page.
[14:42] <sinzui> wgrant: Flimm: right, I intend to change the label on the form
[14:43]  * sinzui looks for real code_name on bloody milestone
[14:46] <ovnicraft> hi i trying to set my project part of project_B and this is part of project_A but when i search project_B just appears project_A, how i can resolve this issue?
[14:46]  * sinzui files big fat bug that code_name is hidden on milestone!
[14:47] <sinzui> Flimm: you are the victim of a lapse of reason. I will get a fix landed for next week. It will not be available on launchpad.net until the next big release at the end of the month.
[14:48] <Flimm> That's alright, I'll just have to release my project without a funky codename
[14:48] <Flimm> Should I file a bug?
[14:48] <sinzui> There seems to be confusion in the code as to the use of milestone name and code_name...there should probably be only one
[14:48] <sinzui> Flimm: I'm doing that noe
[14:48] <sinzui> now
[14:56] <sinzui> Flimm: I reported bug 359078
[15:32] <gnomefreak> did anyone see bug 358755 :)
[15:32] <gnomefreak> i seem to get all the losers
[15:39] <intellectronica> gnomefreak: oh well, what can you do. this is more a 'mistake' than spam
[15:39] <intellectronica> people make mistakes
[15:40] <gnomefreak> intellectronica: mistake is not asking for illegal info mistake == typo or filing a bug instead of a question
[15:42] <intellectronica> sometimes people make really bad mistakes :)
[15:42] <gnomefreak> :)
[15:45] <intellectronica> gnomefreak: the user will be banned, and we're conducting a traditional goat flogging ritual to purify the bugtracker from his presence
[15:46] <gnomefreak> intellectronica: thanks i was just thinking about removing bugs like that so others don't see it while i hav eoutside smoking
[15:47] <intellectronica> i always need a cigarette after seeing a bug like that
[15:47] <intellectronica> it's very bad for my health
[15:48] <gnomefreak> mine too but sometime im going to die. Might as well enjoy life but that is my twisted brain at work
[15:49]  * intellectronica realises he's out of cigarettes. runs, shaking, to the store
[15:50] <gnomefreak> off to gym see you later :)
[16:20] <savvas> what happens if the connection drops and I'm uploading a package to PPA?
[16:20] <savvas> start again? :)
[17:00] <mthaddon> savvas: I think that's a fair assumption
[17:27] <RachedTN-away> hello, I wanna to delete : https://edge.launchpad.net/~ubuntu-tn-editorial
[17:28] <RachedTN-away> can somebody desactivate or delete, please ?
[17:42] <RachedTN-away> How to add a project to a team
[17:42] <RachedTN-away> I recently create a new team, than a new project, but I can't find how to add this project to the team ?
[17:45] <joey> hi RachedTN-away
[17:45] <RachedTN-away> hi joey
[17:45] <joey> RachedTN-away, let me see if I can help you.
[17:46] <RachedTN-away> k
[17:46] <RachedTN-away> ok :)
[17:46] <joey> RachedTN-away, you want to delete https://edge.launchpad.net/~ubuntu-tn-editorial?
[17:46] <RachedTN-away> yes
[17:46] <joey> ok
[17:46] <RachedTN-away> good
[17:47] <joey> RachedTN-away, ok I'll get that done.  Did you have another question?
[17:47] <RachedTN-away> joey: ﻿I recently create a new team, than a new project, but I can't find how to add this project to the team ?
[17:47] <joey> RachedTN-away, ok, can you paste in the link to the project?
[17:48] <RachedTN-away> joey: https://edge.launchpad.net/drafting-project
[17:48] <RachedTN-away> and this is the link of the team : https://edge.launchpad.net/~ubuntu-tn-drafting
[17:50] <joey> RachedTN-away, for the editorial team, it appears that I'll need you to fill out an Question so we can verify you are the owner, even though I can see you are. Please ask for that team to be deleted here:  https://answers.edge.launchpad.net/launchpad
[17:51] <RachedTN-away> ok
[17:52] <joey> RachedTN-away, https://edge.launchpad.net/drafting-project/+edit-people
[17:52] <RachedTN-away> joey: https://answers.edge.launchpad.net/launchpad/+question/67070
[17:52] <joey> RachedTN-away, you go to "change details" and then click on the black "people" mini-bar
[17:54] <RachedTN-away> joey:  sorry, but I can't see "change details" in this page : https://edge.launchpad.net/drafting-project/+edit-people
[17:54] <joey> RachedTN-away, from this page, https://edge.launchpad.net/drafting-project/  or use the +edit-people to add the teams
[17:56] <RachedTN-away> joey: ok
[17:56] <RachedTN-away> :)
[17:56] <RachedTN-away> I see :P
[17:58] <RachedTN-away> thanks a lot joey : it's OK now :)
[17:58] <joey> RachedTN-away, you bet! Enjoy
[20:31] <natureshadow> hi there!
[20:34] <natureshadow> I cannot seem to find any link like "Register a Release" on the series overview page of the trunk series in twittare ...
[20:34] <natureshadow> It should be there according to the docs ,)
[20:58] <DawnLight1> hello. i'm looking for help with https://launchpad.net/rain8net which i've never developed, only created in sf and asked people for help. the development seems to be done now and it's now about packaging it for distros. will anyone want to help?
[21:03] <DawnLight1> otherwise, where would be a good place to ask for such help?
[21:19] <DawnLight> how to i mark a bug as being blocked by another?
[22:32] <RachedTN> I wonder why : https://staging.launchpad.net
[22:32] <RachedTN> isn't working correctly
[22:32] <RachedTN> I often get this error : Timeout error
[22:32] <RachedTN> !!
[22:32] <joey> really RachedTN
[22:33] <joey> mthaddon, ^^
[22:33] <RachedTN> it doesn't happen I work on ﻿https://edge.launchpad.net
[22:33] <mthaddon> joey: yes?
[22:34] <mthaddon> RachedTN: it's a staging server, not a production server, so the hardware isn't as beefy, and it's often down without warning for maintenance or other reasons
[22:35] <RachedTN> mthaddon: ok, I see, but I don't bother you by creating and discativating teams and projects ^^
[22:35] <RachedTN> ﻿I don't want to bother you by creating and discativating teams and projects ^^
[22:36] <RachedTN> I am the owner of a team, and I wanna to delete a reltaed project from the team, how should I do ?
[22:36] <RachedTN> 's/reltaed/related/'
[22:36] <mthaddon> RachedTN: you want to delete the project, or just remove it from "related projects"?
[22:37] <RachedTN> mthaddon: ﻿just remove it from "related projects"
[22:37] <mthaddon> RachedTN: I don't believe there's a way to do that - I think that list is auto-populated based on inferences from usage
[22:37] <mthaddon> RachedTN: it will update over time and if it's no longer related it'll be removed
[22:38] <RachedTN> mm
[22:38] <mthaddon> joey: is that correct? ^
[22:39] <joey> depending on which panel you are looking at, it's autopopulated
[22:39] <joey> so mthaddon, you are correct
[22:39] <joey> the front page though with Featured projects, is set by an admin
[22:40] <RachedTN> joey : if I desactivat the admin who add this project, will the project be removed from the related projects
[22:40] <RachedTN> ?
[22:41] <joey> RachedTN, if you deactivate the person listed in the maintainer field?
[22:41] <RachedTN> yes
[22:42] <joey> RachedTN, then you have a problem and you'll need a LP admin to help you :-)
[22:43] <RachedTN> joey: LP , what's that ?
[22:43] <RachedTN> LP : LauncPad
[22:43] <joey> RachedTN, please paste in the url of the page you are looking at.
[22:43] <joey> yes, lp = launchpad
[22:43] <RachedTN> https://edge.launchpad.net/~ubuntu-tn-drafting
[22:43] <RachedTN> https://edge.launchpad.net/~ubuntu-tn-drafting
[22:44] <RachedTN> https://edge.launchpad.net/~ubuntu-tn-drafting/+related-software
[22:45] <RachedTN> joey : if I desctivate this person : https://edge.launchpad.net/~ubuntu-tn-drafting/+member/mawale
[22:45] <RachedTN> who added the project to the related projects
[22:45] <joey> RachedTN, it's related because that team is associated with those two projects
[22:46] <joey> it's automatically added
[22:46] <RachedTN> let's suppose that Idont wanna my tema to be associated to a project, what should I do ?
[22:46] <joey> remove the team from the project :-)
[22:46] <RachedTN> but it's not my project
[22:48] <kiko> RachedTN, how strange.
[22:49] <RachedTN> kiko: yep :)
[22:49] <joey> the spec associated with that is owned by your team
[22:50] <joey> so it seems in all three cases you are the admin
[22:50] <joey> the tn-drafing team, https://edge.launchpad.net/drafting-project, and the spec https://edge.launchpad.net/tn-drafting-project/+specs
[22:50] <RachedTN> here is the situation : I have created a team (that means I am the owner), one of the administrator has associated a project that I don't like, so I wanna to remove that project
[22:51] <RachedTN> joey : I wanna to keep ﻿https://edge.launchpad.net/drafting-project  and remove ﻿ https://edge.launchpad.net/tn-drafting-project
[22:51] <RachedTN> because it's a redondancy
[22:51] <joey> ah I see
[22:51] <joey> Wajih made your team the owner
[22:52] <RachedTN> yep
[22:52] <joey> that's easy!
[22:52] <RachedTN> how ?
[22:52] <joey> RachedTN, just file an Question (same link as earlier) and ask for that project to be deactivated.  You have to do it thought since you are the owner of the team that maintains that project
[22:53] <RachedTN> ok, how easy is that :P
[22:53] <joey> That way we know it's a valid request :-D
[22:53] <mthaddon> RachedTN: if you let me know the question URL once you've created it, I can do that for you right away
[22:54] <joey> Now that's service! :-)
[22:55] <RachedTN> joey: https://answers.edge.launchpad.net/ubuntu/+question/67091
[22:55] <RachedTN> mthaddon: https://answers.edge.launchpad.net/ubuntu/+question/67091
[22:56] <RachedTN> you are really cool guys, VIVA Ubuntu and Canonical :)
[22:57] <joey> RachedTN, thank you for speaking English. My Arabic isn't very good :-)
[22:57] <mthaddon> ok, all done
[22:57] <RachedTN> mthaddon: thank you
[22:57] <mthaddon> sure
[22:57] <RachedTN> joey : I hope you'll leran arabic oneday, it's really amazing :)
[22:58] <RachedTN> and thanks very much :)
[22:58] <joey> RachedTN, there are few people here who speak it.  I learned Esperanto so I could have fun. :-)
[22:59] <RachedTN> joey: I think that Mr Taher Achour ( atunisian man who made the LPI199) work with you, isn't he ?
[23:00] <joey> RachedTN, I don't know him personally.
[23:01] <RachedTN> joey : If you see him, tell him that ubuntu-tn LoCo are proud of him and they wanna to see him one day :)
[23:01] <RachedTN> joey: have a nice day and take care, sorry to bother you :)
[23:01] <joey> no worries. Come back here if you have any more Launchpad questions
[23:51] <nicoInattendu> Hi, a question on merge. I rry to merge my dev branch on a 'trunk' branch . The merge is caaepter and apporved on trunk, but I don't see the code in the trunk . It is a matter of time ?  The branch maeged is here : https://code.launchpad.net/~nico-inattendu/luciole/nico-0.7 and try to merge here https://code.launchpad.net/~nico-inattendu/luciole/main
[23:53] <savvas> nicoInattendu: you have to merge it yourself with bzr merge
[23:53] <savvas> (I think)
[23:53] <nicoInattendu> In which branch ? in the main ?
[23:53] <savvas> the web interface is just to show other what's going on :)
[23:54] <savvas> erm...
[23:54] <savvas> you want to merge nico-0.7 into main right?
[23:54] <nicoInattendu> Right
[23:55] <savvas> while in main, try: bzr merge lp:~nico-inattendu/luciole/nico-0.7
[23:56] <savvas> I could be wrong though, so don't trust me :)
[23:59] <nicoInattendu> No , it was  great  :). But now I dont' understand the goal of the web interface for merge stuff.
[23:59] <savvas> 00:54:13 < savvas> the web interface is just to show other what's going on :)
[23:59] <savvas> *others