[00:33] alguem brasileiro ou alguem que fale portugués ? [01:16] New bug: #189450 in launchpad-answers "Allow to delete a mirrored branch." [Undecided,New] https://launchpad.net/bugs/189450 [05:13] thumper, jml, hi? [05:13] hi [05:13] wassup? [05:13] is it possible to delete a branch through the web ui? [05:14] oh, i was confused because staging logs me out when it resets [05:14] i'll fix that... [05:14] poolie: there are still some kinks, but I believe that you can [05:14] (or at least, I know that abentley is working on something related to branch deletion) [05:16] ok [05:16] i think this is it: if the branch has attachments you can't delete it [05:16] which is, probably ok [05:16] but you can't even think about deleting it, which is problematic :) [05:16] ie the menu item is not there [05:19] It would be nice if the menu item were there, and lead you to a page saying "you can't delete this branch because..." [05:19] i think so [05:20] at a minimum, show the menu item in disabled state [05:21] to show "you have permission to delete the branch, but need to do something else first" [05:25] right [05:25] is there a "disabled state" in the launchpad ui standard? [05:25] but i think that would not be a good choice here because it's not obvious what you have to do to enable it [05:25] we use it for the tabs across the top. Don't know about the menus down the side [05:25] oh right [05:31] it's bug 133988 [05:31] Launchpad bug 133988 in launchpad-bazaar "Explain why a branch can't be deleted" [Medium,Confirmed] https://launchpad.net/bugs/133988 [06:10] poolie: this is the exact thing that abentley is looking at [06:16] thumper: how was the beach? [06:17] jml: very nice, but I didn't put enough sunscreen on Caitlin and she has a strip of red across her back :-( [06:18] :( [06:19] thumper: get a new ozone layer [06:35] abentley, thumper, yay! [06:41] stub, hi? [06:50] New bug: #189489 in launchpad "In-code doctests require # ELLIPSIS" [Undecided,New] https://launchpad.net/bugs/189489 [07:21] poolie: hi === stu1 is now known as stub [08:32] Morning [08:35] Is there any support in launchpad for importing data from other bugtrackers? Say I had a project with a reasonably large "Request Tracker" database, how likely is it that we'd be able to work out a migration? [08:41] fairly likely [08:41] but it's done case-by-case [08:41] (i think) [08:41] Sure thing, that's what I'd expect. [08:42] ask a question on the 'launchpad' project i guess [08:43] morning === carlos_ is now known as carlos [08:44] It's no sure thing at the moment - I'm just trying to offer it as a possibilty to a project and without help importing data it'd definitely be a no-no :) [08:45] Thanks. [09:08] carlos, thanks for your answer yesterday, I suddenly had to run for a train ;) [09:08] thisfred_: np === Ubulette_ is now known as Ubulette [09:42] how can I get my account completely removed? [09:42] deactivating leaves it accessible [09:43] brutopia: if it's deactivated, it's not really an "account" anymore. More a record of the fact that your name is mentioned. [09:44] how can I then remove the record [09:44] that bastard gets indexed in google with my real name even if I changed the name months ago [10:08] hi all [10:09] pontentially stupid question of the day: is there any significant difference between "regular" launchpad and "egde"? [10:10] edge runs a slightly newer version of the launchpad software [10:10] jelmer: yeah, I know [10:10] jelmer: but what are the main difference? [10:11] is there a "CHANGELOG" available? [10:12] or... said otherwise: "why should I switch to edge rather than the classic version?" ;) [10:12] No`: Hmm, there isn't a changelog as such [10:12] No`: I'm not sure how much you know about the LP release process, so I'll give you a quick intro :) [10:13] might help, yes [10:13] We release a new version of Launchpad once a month. Leading up to that release, naturally the team commits code throughout the month. [10:14] Non-database affecting changes are available the next day on Edge, thanks to Bazaar allowing us to automatically push it out once a day [10:14] Actually, this page might help: https://help.launchpad.net/BetaTesting [10:15] So, anyway, those commits aren't shown in a publically available changelog until the release, at which point I publish the release notes. [10:16] ok, got it now. So there is no major difference between edge and normal launchpad, except on the foreground. The data is affected the same way? [10:18] No`: Yeah [10:18] how to remove launchpad account completely? [10:19] is there anyone here with admin rights? [10:25] New bug: #189522 in malone ""I don't know" refused when reporting a bug" [Undecided,New] https://launchpad.net/bugs/189522 [10:30] brutopia: Hi [10:31] brutopia: You can remove your Launchpad account by following this guide: [10:31] brutopia: https://help.launchpad.net/DeactivatingYourAccount [10:31] Do you mind me asking why you want to deactivate your account? [10:35] brutopia: If that isn't quite what you want, then you'd need to file an admin request at: https://answers.edge.launchpad.net/launchpad/+addquestion [10:53] I already deactivated multiple times and account page can still be accessed [11:41] * Hobbsee waves [11:41] Morning, Hobbsee. === mrevell is now known as mrevell-lunch === doko_ is now known as doko === mrevell-lunch is now known as mrevell === _emgent is now known as emgent [14:33] kiko: you there? [14:36] synic, always [14:36] what's up? [14:37] actually, nevermind :) I was going to ask you if you'd delete a branch for me, but I found that I could rename it, which is more what I wanted anyway. [14:37] it became corrupted somehow [14:38] you can delete it yourself, though [14:39] I unlinked the bugs related to it, but the delete link never showed up [14:39] no blueprints were related either [14:39] synic, and subscribers? [14:39] there were those, but I wasn't sure how to remove them [14:42] synic, yeah, you need to ask them to unsub currently. I know that abentley is working on this, though. [14:43] ah, yeah, that would have been a problem. The developer that pushed the broken branch has disappeared; he might be off at school or something. Thanks though :) [14:43] (and that same dev was subscribed) === kiko is now known as kiko-fud === weltende is now known as welterde === statik` is now known as statik === kiko-fud is now known as kiko [15:48] I ve created a key and uploaded the key to the server and i ve got an email from launchpad too and ve installed FireGPG to decrypt it so selected the big chunk of text and tried decrypting it but it says its not a valid key [15:48] how do i proceed from here [15:48] can some one here help me please [15:48] i want to become a Ubuntero :) [15:49] linux__alien: I'm sure someone can (not me, alas), but not everyone is paying continuous attention to the irc channel. Give them a little bit and I'm sure you'll get an answer :) [15:50] I'm paying attention [15:50] but I think linux__alien is doing something wrong on his end. [15:50] how about using gpg directly? [15:52] hello folks [15:52] I have some problems when doing bzr push [15:52] Unable to obtain lock lp--1221404884:///lock [15:53] any ideas? ^_^ [15:53] kiko, ok got it now i decrypted it and it gave me a link and it said the key has been validated but still my status as ubuntero is no [15:53] what else should i do [15:53] linux__alien: sign the Code Of Conduct [15:56] anyone has any ideas? ^_^ [15:56] pochu, i did that too i signed it [15:57] and pasted it too and clicked continue [15:57] and now it shows me a page showing Active Signatures [15:57] and it shows me what i ve pasted against a check box [15:57] pygi, that's not the full message. [15:57] linux__alien, so you're an ubuntero now. [15:58] it says if you change your mind you can deactivate your signature [15:58] kiko, thats true :) [15:58] kiko, is that all ? Great so should i save some of these things? [15:58] linux__alien, save what? :) [15:58] kiko, this is: http://pastebin.com/m8e97a1c [15:59] kiko, i ve saved the key after i used the FireGPG [15:59] pygi, bzr break-lock. [15:59] anything else should i save? [16:03] kiko, tried that, it breaks the lock, but when I try to push, it happens again [16:03] pygi, do it until it reports no locks left [16:03] linux__alien, nothing. [16:07] kiko, thanks [16:10] pygi, IIRC there can be two locks -- a repo lock and a tree lock. IIRC. [17:44] good morning [17:44] I believe rosetta strips out #. Default lines from po files, is that right ? === PriceChild is now known as pricechild [17:53] sm, hmmm, not 100% sure === pricechild is now known as PriceChild [17:53] I believe so.. and I think my project or some tool needs them.. but I forget why [17:54] * sm needs to find out what they are for [17:55] does anyone have a documented process for maintaining project translations from both launchpad and source-code contributions ? [17:56] mine is so-so [17:58] extracted comments from programmer to translator, I see [18:03] sm: you can maintain translations in Launchpad directly, could you give more details of your needs? [18:04] my project accepts translations both via launchpad and via darcs patches to the source [18:05] this is tricky [18:05] sm: well, we are able to lock languages so no one could translate for them if you manage them in darcs [18:06] while the others using Launchpad could keep using Launchpad [18:06] if you want to use darcs and Launchpad for the same language... that's not a good idea [18:06] unless is the same user so there are no conflicts [18:07] I see, but I want to allow any translator to use either tool at any time [18:08] sm: the problem there is that if user 'A' does a translation in Launchpad and user 'B' updates it too, you have a conflict [18:08] in Launchpad we know about it and we have some locking features to prevent data lose in those cases [18:08] yes, and dealing with this is tricky and time-consuming [18:09] but darcs doesn't know how to handle it [18:09] sm: do you mean is tricky and time-consuming our handling of duplicates? or in general that kind of conflicts? [18:11] http://paste.lisp.org/display/55481 is my current procedure for keeping lp and darcs in agreement, which is time consuming [18:13] makes sense ? [18:13] make mergelp uses msgmerge [18:14] sm: does launchpad strip out #. comments? [18:14] I believe some, but not all [18:14] sm: please, file a bug, we should not lose data at all [18:14] will do [18:14] sm: if possible, give us how to reproduce it so we can debug it better [18:14] sm: thanks [18:14] sm: about "apply any new translation patches" [18:15] is that people sending patches directly to darcs ? [18:15] right [18:15] I have a few developers who prefer that [18:15] so you are the only one able to do such commits? [18:15] currently that's true, though about to change [18:15] sm: our advise is [18:16] use Launchpad as the way to 'submit' translations to your project [18:16] sm: you provide .pot file template updates [18:16] and people will use Launchpad or download/upload feature if they don't want to use the web interface [18:17] so you get translations from Launchpad from time to time and update your source tree [18:17] I see.. so they can still use their tools that way [18:17] right [18:17] you save the translations merging in your tree [18:17] because we do it automatically every time you upload an updated .pot file [18:17] you are right, this is much better [18:18] and also, the merge with .pot file is not needed either [18:18] possibly the web interface was the only option when I started this.. [18:18] because we do it too [18:18] sm: hmm, not really, upload/download has been there since first day, although maybe we did some improvements that makes it easier [18:19] sm: also, we are open to any suggestion to improve your workflow [18:20] ok, maybe I just misjudged then. We had an existing darcs translation process that was working well when lp arrived. I thought I had to keep that going for some other reason too.. hmm [18:21] I think your suggestion is the way to go, I will simplify [18:21] thanks, carlos! [18:21] sm: you are welcome [18:25] I should upload the latest pot to launchpad periodically, and I don't need to warn translators, am I right ? [18:27] yes, that's right [18:27] everything will work out fine [18:30] great === Martinp24 is now known as Martinp23 === kiko is now known as kiko-afk === Gwaihir_ is now known as Gwaihir === PriceChild is now known as pricey === pricey is now known as PriceChild === Soda is now known as Soda__ [22:20] New bug: #189751 in malone "Assigning a bug to a non-published package gives a wrong string" [Undecided,New] https://launchpad.net/bugs/189751 === Syntux is now known as Syntux_Pissed_Of [23:29] hi. How should i do to upload different distributions of the same source? should i only edit the changelog and build the source again [23:29] ? [23:35] anyone here that can answer me this, please? [23:35] Legendario: sounds right === gryc_ is now known as gryc [23:37] gryc, do i have to pbuild the package again? [23:37] I believe so [23:46] gryc, could you answer me a question about cdbs? [23:48] sorry, I've only made it through the debhelper part of the packaging guide :D [23:49] gryc, do you knwo how to specify the path of the make file in the debian/rules? [23:49] no clue [23:52] Legendario: did ion_ not answer you? [23:53] crimsun, sorry. i hadn't seen it...