=== dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk [01:38] can someone help me with merge@code.launchpad.net? [01:39] dickelbeck: probably, what's up? [01:40] I sent a couple of emails to that address today, the first few were not properly signed, and finally the very last one was. [01:40] All had the same merge bundle attached. [01:41] One good email at the end which was not bounced back. [01:41] The nature of the bundle was that it was against a private branch, so the patch was included. [01:42] launchpad created 3 new branches at project kicad, and did not actually modify the merge request list at all. [01:43] It looks like a bug, but I am finding the workflow requirement of launchpad net to be not a good match for our project. [01:58] thumper: you around? I think you could help dickelbeck. === Ursinha-nom is now known as Ursinha === Ursinha is now known as Ursinha-afk [05:18] I'm not able to tell my project that I want to have code in Launchpad.... [05:20] I feel like I may have found a bug in LP.. [05:22] MTecknology: Why can't you? [05:23] wgrant: usually there's a nifty link off to the right side saying Configure Code or something simmilar [05:24] Now it's a grayed out "Submit code" with a /!\ beside it [05:24] MTecknology: Is the no 'Configure project branch' link underneath it? [05:24] MTecknology: is this for your private project? [05:24] There should be, if you have sufficient privileges. [05:25] * micahg doesn't know if it makes a difference [05:25] micahg: no [05:25] wgrant: no [05:25] MTecknology: Which project? [05:25] err - wait - there it is [05:25] it won't find the branches though [05:26] here... [05:26] https://code.launchpad.net/~nginx https://code.launchpad.net/ninx [05:27] MTecknology: Why is the project name missing the 'g'? [05:27] The branches owned by ~nginx are in the 'nginx' project. [05:27] https://code.launchpad.net/nginx ** [05:28] So searching in the 'ninx' project won't find them. [05:28] ......... [05:28] facepalm [05:29] wgrant: any change I could get a rename from ninx to nginx-server ? [05:29] probably with an answer request.. [05:30] why nginx-server? [05:30] Isn't nginx a server? [05:30] ya, but I guess somebody took nginx and never did anything with it [05:31] I missed the g creating the project [05:31] Doesn't mean you should create a new project. [05:31] You could perhaps convince an admin to give the project, or configure it in the way you require. [05:32] I'll try to get a hold of that guy first [05:41] wgrant: could you read the mail I'm about to send him and let me know what you think? [05:42] MTecknology: I suppose. [05:42] wgrant: If you don't want to that's fine [05:42] I can just fire it off === dendro-afk is now known as dendrobates [08:49] hi [08:49] there is a problem. [08:50] hello??? [08:50] Hi. [08:50] What's the issue? [08:50] https://answers.launchpad.net/canonical-identity-provider/+question/115024 [08:50] that is the problem. [08:51] i have an email-adress, but i can not delet it. [08:51] The last comment in that question suggests that it has been manually removed. [08:51] is there a chance for a quick delet?? [08:52] sure [08:52] Enry, I deleted it for you last week? [08:52] ah hi. [08:52] no. [08:52] i am another person. [08:53] BUT with the same problem. :( [08:53] Ah ha! :-) much is clearer! [08:53] good. [08:53] Bug #507214 [08:53] Launchpad bug 507214 in Canonical ISD QA "No Way To Remove Old Emails (affected: 19, heat: 121)" [Undecided,Confirmed] https://launchpad.net/bugs/507214 [08:53] in that case, please raise the same style of request, so we can verify you are *you* :-) and it will be acted up. [08:54] upon! [08:54] It's fixed, but not yet rolled out. [08:54] Green00000: https://answers.launchpad.net/canonical-identity-provider/+addquestion === dendrobates is now known as dendro-afk [08:55] i read the faq. [08:56] okay, same request. [08:58] this point: [08:58] this point: [08:58] https://answers.launchpad.net/canonical-identity-provider/+addquestion [08:58] ???????? [09:01] Green00000: atm I have no idea who you are, what account you may have etc. by formally asking a request to delete an email address via that linked form, we can make such a determination. Going and deleting someones email because some random person on IRC asked for it, would be ... uncool. :-) [09:02] okay, i am writing. thx. [09:34] okay, thx ...... i posted the problem connected with the BUG-#. === menesis1 is now known as menesis [10:01] does launchpad generate .po files from a .pot, or do I need to provide both? === daniloff is now known as danilos [10:12] does launchpad also generate the .mo files? [11:08] jtv, danilos ^^? [11:18] rioch, it can, but only when you request it manually for download; it cannot put them in a branch yet if that's what you are asking [11:18] anyway, gotta run out for a bit === yofel_ is now known as yofel [12:28] why is my merge/bundle/patch request send to merge@code.launchpad.net is not going into https://code.launchpad.net/kicad/+activereviews [12:28] The email was signed, the openpgp key is on file, no bounce back error was received. [12:37] dickelbeck, hi. Not sure if I can help, but can you point me at a branch that you requested a merge for? [12:39] lp:kicad aka https://code.launchpad.net/~kicad-testing-committers/kicad/testing [12:40] * deryck looks [12:41] dickelbeck, I don't see a proposed merge there. To what branch did you want it merged, and how did you propose the merge? [12:42] by email to merge@code.launchpad.net, using bzr send -o fullpath.bundle and then attaching it and signing it in my mail client. [12:42] I first got 3 bounce backs because I was not signing it properly, then on the last attempt it seemed OK. [12:43] Funny thing, for awhile yesterday, there were 3 new branches created under the project umbrella that had my name in them, and "merge" also in the branch name. [12:44] Now they are gone. I think the email handler that receives these emails is very weak. [12:44] dickelbeck, ok, were you proposing merging lp:kicad into another branch? Or trying to propose another branch into lp:kicad? [12:44] merge into lp:kicad [12:46] I can send you the bundle if you want. [12:46] dickelbeck, what is the link of the branch you proposed from then? [12:46] it was a local branch, launchpad would not have access to it, therefore the bundle included the patch. [12:47] It was a problem fix branch, made locally here from a checkout (copy of lp:kicad) [12:49] dickelbeck, I'm not a code expert on lp, but I believe the branch you're proposing from has to be pushed to lp, which may be the problem here. [12:50] rockstar or abentley could help us here if they were around. [12:51] "has to be pushed to lp", if true, would contradict the documentation I think. This is the reason why the bundle includes the patch (optionally). [12:51] when are these guys available? what time zone? [12:52] dickelbeck, rockstar is normally GMT -7 but is sprinting this week so generally hit or miss. abentley is GMT -4, I believe, so should be around soonish. [12:53] dickelbeck, I'm also not an expert, but your three branches from yesterday are marked as "merged" https://code.edge.launchpad.net/~dickelbeck/+branches?field.lifecycle=ALL&field.lifecycle-empty-marker=1&field.sort_by=most+recently+changed+first&field.sort_by-empty-marker=1 [12:54] thekorn, what is this supposed to be telling me, about 3 branches that I did not even create? [13:10] deryck, hi [13:10] dickelbeck, hi, how can I help? [13:10] yo rockstar! [13:11] rockstar is better than windows 7 bitches! [13:11] Hi rockstar, can you see any history in the discussion? [13:11] deryck, that doesn't really set the bar high does it? [13:11] heh [13:11] Getting kicked in the balls is better than Windows 7. [13:12] dickelbeck, I can, and am reading. Why don't you summarize? [13:13] I unable to affect https://code.launchpad.net/kicad/+activereviews by mailing to merge@code.launchpad.net [13:14] My merge bundle is in hand, I can send it to you somehow. It wants to merge into lp:kicad from a local, non-accessible bug fix branch, and includes the patch in the bundle. [13:14] dickelbeck, how did you generate the bundle? [13:15] bzr send -o [13:15] dickelbeck, so the bundle got attached then? [13:16] do you want to see the bundle? Sorry, that was "bzr send -o fullpath.bundle" [13:16] then I attached it to a new email, signed it, sent it. [13:33] when I click on "How to get the fingerprint" on the launchpad page for "Change your OpenPGP Keys", I get a pop up that shows its loading but never loads any content. Is there somewhere else I can find out how to get the fingerprint? [13:36] Italian_Plumber, just do 'gpg --fingerprint me@example.com' or whatever is the address in your key [13:38] ok thanks i'll try that [13:40] hmmm... why would my ".gnupg" directory be owned by root? === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-brb [13:59] rockstar, what's next? [13:59] dickelbeck, sorry. [13:59] dickelbeck, you signed the email? [14:00] dickelbeck, and out of curiousity, why not `bzr send` ? [14:00] I sent the same email a couple of times, fighting with my email client at first. On the 3rd or fourth attempt it was signed properly, the first few not. [14:00] Er, why not let bzr take care of attaching the email, etc. [14:00] Does launchpad know about your key? [14:01] bzr send, did not put in the destination address properly, the recipient field in thunderbird was empty. [14:01] yes launchpad has the key. The first few bad emails gave me bounce backs, the last one did not trigger any objections. [14:02] dickelbeck, if you put "submit_to = merge@code.launchpad.net" into your ~/.bazaar/bazaar.conf, it'll set the recipient properly. [14:02] dickelbeck, and where's the branch you're proposing for merge? === flacoste_afk is now known as flacoste [14:03] on my hard drive, not accessible to launchpad.net [14:05] dickelbeck, and what's the target? [14:05] lp:kicad [14:05] Again, I still have the bundle, all this information is in there. [14:10] dickelbeck, hm, I'm not sure here. [14:11] where is the source to this email processor? how can we get a look at it? [14:12] This is a big deal to me, since it affects the overall utility of launchpad.net. our contributors are drive by contributors, don't want to push branches. [14:12] dickelbeck, bzr branch lp:launchpad/devel [14:13] dickelbeck, they already have accounts on Launchpad, right [14:13] and patches on the mailing list seem to be hard to keep track of and comment on.ulling things from the mail list [14:13] Yesterday was a big blow to my enthusiasm about moving this project to launchpad as a whole. [14:13] Hmm, why can't they push branches? [14:14] Because they cannot afford to spend 3 days learning how, they are drive by contributors. [14:14] I need a patch manager. [14:14] Add SSH key, bzr push lp:~username/project/branch [14:14] The launchpad model is not meeting my needs. [14:15] Right now I pull most of the patches down from the mailing list. I am getting buried. The website needs a patch manager. [14:17] it's easy enough to attach patches to bugs [14:17] bigjools, true. That may be what I will have to institute. [14:18] No way can I trash launchpad now that I was the guy the moved the project here by less than a fully democratic process. [14:19] Can you merge a bug attachment? How does having a patch on a bug differ that much from having a patch on an email? [14:19] I think that pushing branches is probably easier than emailing or attaching them to bugs, it's just the case that people like to do what they know already [14:20] The whole usage model is not ideal. The site needs a patch manager, or google for "code review software". If I cannot get bundles in by email, then what? [14:20] abentley may have more advice than I can offer when he's around [14:21] You can email bundles in. [14:21] it's obviously just not quite working in this particular case. [14:21] But pushing branches is almost always easier... [14:21] wgrant, please. It is not working, please read the history of this dialog. [14:21] I know it's not working *in this particular case*. [14:21] In the general case it works fine. [14:21] people are put off because it's "different" [14:22] or perceived to be hard [14:22] However it's not well documented, and the gpg signing requirement can be tricky [14:22] Is there any help page for building recipe contents? [14:24] I'm was even willing to volunteer to take patches off the mailing list and put them into https://code.launchpad.net/kicad/+activereviews [14:24] by way of email, but I am unable to do it. [14:25] I effectively email patches by doing "bzr send" [14:25] MTecknology: https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted [14:25] bigjools, are these bundles from a private branch against a public branch? [14:27] bigjools: thanks [14:27] dickelbeck: it generates a diff of two branches, doesn't matter where they are [14:27] well, one is local obviously [14:27] when abentley comes in, I'll ask him to chat to you, he knows more than I on this [14:27] bigjools, yes the documentation says that should work. It did not work for me, and I got no complaints from the mail server back. [14:28] ok [14:28] I'm sure he'll be able to figure out your problem [14:29] when is abently working, I can come back then? [14:30] he should be here soon, he's UTC-4 [14:35] thats about 10:30 in the morning for him, doing something else probably. === Daviey_ is now known as Daviey [14:40] yay, now I just need to get a branch import approved and I can become very excited [14:56] danilos, ping [14:57] hannie, hi [14:58] May I ask you something? [14:58] hannie, sure [14:58] losa ping - can someone unsubscribe the 'ipv6 task force' from https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/417757 - hugely noisy for lots of people [14:58] Launchpad bug 417757 in eglibc (Ubuntu Lucid) "[regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups (affected: 198, heat: 830)" [High,Triaged] [14:58] About Ubuntu manual Lucid-e1 and Lucid-e2 [14:59] added before we restricted subscriptions of teams [14:59] We had translated 70% of Lucid-e1 so far [14:59] hannie, yeah, are you still having problems with translations disappearing? [14:59] hannie, oh, something else, sure :) [14:59] lifeless: Done. [14:59] Yes, all my translations have become suggestions [14:59] lifeless: er, that seems quite relevant to ipv6 task force [14:59] hannie, again? on lucid-e1 or lucid-e2? [14:59] Both [14:59] lifeless: who can confirm we really want to unsusbcribe that user? [15:00] People have been complaining. [15:00] Kevin Godsby suggested not to start with e2 until end of july [15:00] mthaddon: yes, we're sure: it was subscribed in the 'please fix for me' sense [15:00] hannie, that's weird [15:00] mthaddon: by someone not in the team [15:00] But now e2 has changed from 70 % translated to 39% [15:01] lifeless: can't someone from within the team unsubscribe? [15:01] hannie, oh, right, that's because they are using message sharing: I should have thought of that earlier [15:01] Can it be fixed? [15:02] hannie, basically, since those two have mostly the same messages, they get applied to both when lucid-e2 messes them up [15:02] mthaddon: I have a suspicion that we made the permission thing there symetric [15:02] But can it be fixed? [15:02] hannie, it's a bug that I'll bump the priority for so we'll get it done soon [15:02] lifeless: You didn't. The subscription is gone now. [15:02] hannie, a work-around is still simple: project maintainers would need to set up lucid-e2 to import only templates as well [15:02] lifeless: bug#134577 [15:02] hannie, i.e. on https://translations.edge.launchpad.net/ubuntu-manual/lucid-e2/+translations-settings [15:02] ok, danilos [15:03] hannie, I'll also make sure we fix the actual bug soon [15:03] I thank you for it, it will save me a lot of time [15:03] bug 134577 ? [15:03] Launchpad bug 134577 in Launchpad Bugs "Admins should be able to unsubscribe other people from bug reports (affected: 1, heat: 9)" [Medium,Triaged] https://launchpad.net/bugs/134577 [15:03] thx wgrant [15:03] hannie, I am very sorry for the trouble [15:04] That's ok, but it gave me a few more gray hairs [15:04] Danilos, I have no access to the link you gave me [15:05] hannie, are you project maintainer/driver for ubuntu-manual? [15:06] I am just a translator [15:06] hannie, right, then you don't have access to it; it's something project maintainers can do [15:07] hannie, for yourself, you should probably download a PO file as soon as you are done with translation for a while, and if it turns it into suggestions, you can just re-upload it (at least until we fix the bug) [15:07] anyway, got to go out for a bit now, ttyl [15:08] danilos, thanks [15:56] MTecknology: Have you noticed that you've actually misspelt the project ID of nginx as ninx? :-) [15:57] maxb: https://answers.edge.launchpad.net/launchpad-registry/+question/118418 [15:57] maxb: oops [15:57] ah [16:04] maxb: thanks for the approval :) Once it imports I'm going to try out a recipe :) [16:15] anyone around to help with bug 608302 reported by X3 [16:15] Launchpad bug 608302 in Launchpad itself "copied binaries require origin ppa key to determine trustiness (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/608302 [16:17] shadeslayer: That's impossible. [16:17] shadeslayer: I can't parse that description [16:17] shadeslayer: The binaries themselves are not signed. [16:17] The archive is. [16:17] wgrant: i know the binaries are not signed,the archive is [16:18] "the ppa where the packages where copied to ppa B if added to sources reports packages are untrusted" [16:18] but strangely even after importing the key [16:18] well importing the ppa where the packages have been signed when installing come from untrusted source and could be a security risk [16:18] no [16:18] importing the origin ppa key fixed bug [16:18] er ya [16:18] echan [16:19] packages do not get authenticated === Ursinha-brb is now known as Ursinha [16:20] I don't understand the problem, can you please explain exactly what you're doing? [16:21] copy binaries from ppa A to ppa B, add ppa B to system, install packages ~ security warning [16:21] X3: what is generating the security warning? [16:22] the apt-get or aptitude install line [16:22] what you're describing is impossible [16:22] I have done this myself and it's fine [16:22] it just spews out these packages are from untrusted source and could compromise your system bla bla bla [16:23] it means that either, your Releases file is out of date (transparent proxy?) or you don't have the gpg key installed [16:23] gpg key shows up on sources manager [16:24] can you provide a screen log of your actions? [16:24] it is fixed by either a) add orgin ppa key or b)rebuild sources inead of copying binaries [16:24] basically, if you're not installing packages from PPA A then there is *no way* that it can affect PPA B [16:25] the binaries are re-published in PPA B if they are copied [16:25] yes just because there is *no way* doesn mean I been imagining this all morning [16:26] [16:24:24] can you provide a screen log of your actions? [16:27] and do you know if there's a proxy in your way? === dendro-afk is now known as dendrobates [16:27] well not at the moment since then I have deleted packages from ppa B in order to rebuild packages on ppa B and fix issue [16:27] I've seen people have GPG issues before when there's a proxy that's not refreshing Releases [16:27] no proxy === fta_ is now known as fta [16:27] well unless the VM is making proxy [16:28] don't take offence but I'm going to mark your bug invalid - there will be another explanation, I can try and help you find it [16:29] unfourtunately i cant test it out since im on maverick [16:30] ya I take no offense n wasting most of my day [16:30] :/ [16:30] I offered to help, would you like me to help or not? [16:31] sure [16:32] which PPA is affected? I can install it here. [16:32] however im unsure how this is gonna get resolved unless I rebuild packages on ppa B which is now complaning about exsiting sources [16:32] you can't publish the same version again [16:32] apt clients don't like that [16:32] so it's prevented [16:32] https://edge.launchpad.net/~team-iquik/+archive/alsa [16:33] well I tried delinting the copied packages [16:33] What is delinting? [16:33] X3: i just copied them back [16:33] maxb: deleting [16:33] its a typo for deleting [16:34] ah u copied them I was wondering what the hell they were doing still there [16:34] if it helps sort this out [16:35] i rebuilt the packages from ppa A to a ppa C to test and the error was gone [16:35] I suspect that is a coincidence [16:35] idk [16:35] can you paste the exact error you got from apt please? [16:36] its no longer up on terminal buffer is past it [16:36] sec Ill try to recreate agin [16:39] I tried here and it worked fine [16:41] funny now the error is not there, perhaps having deleted packages and re-copying fixed it [16:42] The only thing that will have caused is a timestamp change on Releases [16:42] but seeing the original error will help [16:43] cant really oblige the buffer on terminal is gone unless there is a way to dig it out [16:43] if there is a way and u can help dig it out [16:44] I don't know of a way once it's off buffer [16:44] nor I :( [16:44] I keep huge scrollback buffers for that reason :) [16:45] ya well [16:45] ok what I think happened here is that the signing key for your PPA was not generated yet because that doesn't happen until packages are put in it [16:45] so you copied packages in, then immediately tried to download them [16:45] apt-get update complains because there's no signing key yet [16:46] not quite immediatly it was a whle after, but that makes sense [16:46] then it got added a few minutes later and co-incided with you adding PPA A [16:46] idk most likely [16:46] generating keys is not that quick unfortunately [16:46] makes sense [16:47] so you should be all set now [16:47] ya thx for help [16:48] was a bit frsutrating having to find this out after a day wasted [16:48] is there anything you think we can do to make the experience better? [16:49] i knew about keys but once the ppa has packages and they published if key is not ready then it shouldnt appear on ppa until it is [16:49] yes pls [16:49] if the keys are not ready for that ppa, the ppa should not show ready status [16:49] some people accept the warning and download the packages anyway [16:49] we could put a status on new PPA pages saying the key is not ready yet [16:50] aye that not the problem [16:50] ya the satus is good way to go [16:50] ok thanks for the feedback [16:50] thx for help [16:51] got there in the end ;) [16:51] and sorry if I sounded a bit frsutrated [16:51] we've all been there ... [16:51] i bet [16:52] put a health warning on Linux [16:52] trying to get things to work as they should may cause your brains to fry [16:53] same goes for all OSes I've tried === dendrobates is now known as dendro-afk [16:59] bigjools, next time you email in a bundle to merge@code.launchpad.net, can you cc: dick@softplc.com ? TIA. Just want to compare email constructions. === fta_ is now known as fta === dendro-afk is now known as dendrobates [17:10] abentley: can you help with merge@code.launchpad.net mail processing? [17:11] dickelbeck, sure, what's the issue? [17:13] Yesterday I emailed a bundle, which included a patch since the changes were from a local branch, and they never made it to the destination branch. [17:13] the destination branch was lp:kicad and the mail was signed. [17:14] I did not get any email error notification back on the last attempt, whereas I had gotten some bounce backs until I got my signing to happen. [17:14] dickelbeck: Perhaps you could pastebin the source of the message you sent? [17:15] maxb: excellent idea, you are the first to ask. [17:16] * maxb wonders why this doesn't have more than a one-sentence mention on help.lp.net [17:16] maxb, it's not our recommended way of submitting changes. [17:17] Yet its existence is public, and not cautioned against. Thus, it ought to be documented sufficiently to not be a path to frustration [17:19] dickelbeck, our logs don't indicate that we attempted to process a merge directive yesterday, much less that processing failed. [17:20] dickelbeck, so how about that pastebin? === beuno is now known as beuno-lunch [17:20] you want me to use http://paste.ubuntu.com/ ? if so, it seems hung now. [17:21] dickelbeck, I'm not picky. [17:21] http://pastebin.com/qZFnttuX [17:22] I see some thunderbird applied line wrapping, this text was from my "sent" folder. [17:25] james_w: well, thanks for the help on Qt, got it working now :) [17:26] * Quintasan is now waiting for space increase in PPA === dendrobates is now known as dendro-afk === deryck is now known as deryck[lunch] [17:42] dickelbeck, I'm sorry, but it looks like we don't have sufficient logging to track down what happened. [17:43] well this particular bundle is already obsolete. How can I get this to work? Can bzr send the bundle itself, not using a mail client? [17:44] maybe somebody can just cc: me on an email that is expected to pass the codehandler.py and I can look for differences. [17:44] dickelbeck, yes, it can use the "editor" mail client for example. [17:44] Quintasan: :D [17:45] abentley: never header of the editor mail client, what is that and why would it be better than thunderbird w/ enigmail? [17:46] dickelbeck, it's documented in the "send" command. It's not better than thunderbird, but it is the answer to the question "Can bzr send the bundle itself, not using a mail client." [17:47] I'm trying to build a recipe that drops the debian/ from another branch into the source and builds. When I try to build it I get the error bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified. [17:48] No, it does not answer the question. If "editor" is going to send the email, then bzr is not sending the email? My question was can the python code in bzr do the SMTP protocol and send the bundle? [17:50] dickelbeck, "editor" is a pseudo-mail client supported by the "send" command, and is entirely bzr. Mail sent using this pseudo-mail client is sent by bzr itself. [17:50] abentley: editor cannot be used to send to Launchpad, because it cannot gpg-sign..... unless I've missed a trick? [17:50] maxb, this is true. [17:52] If anyone has the chance, could you peak at my build recipe and tell me what I screwed up on? https://code.launchpad.net/~nginx/+recipe/nginx-stable [17:52] abentley: Regarding the auto-create MP via email thingy - am I correct in thinking that this entails LP creating a branch from the bundle first, and that the name of the branch you want created needs to be in the bundle metadata? [17:52] dickelbeck, here is the source of a message I sent that was successfully handled by merge@code.launchpad.net: http://pastebin.ubuntu.com/467103/ [17:53] maxb, the name of the branch does not need to be in the bundle metadata. [17:53] maxb, It's true that LP creates the branch from the bundle. [17:53] How will launchpad decide it, then? [17:54] maxb, It prefers to use the name in the merge directive, but if there is none, it uses "merge" with an optional digit prefix. [17:54] ah, ok [17:54] digit *suffix* actually. [17:54] btw, yesterday LP created these funny branches yesterday for me, one for each failed attempt I think. So the sequence is out of kilter, these first 3 attempts were not properly signed emails. [17:55] Then the final email was signed, and it was dropped? Should I switch the project back to sourceforge? :) [17:55] MTecknology: I think, perhaps, that you want to *nest* not *merge* the packaging [17:55] dickelbeck, I would suggest using the lp-propose command instead. [17:56] maxb: thanks :) [17:56] MTecknology: also, I'd suggest testing whether the recipe works locally, rather than waiting for Launchpad to process [17:56] abentley: Only if you remove all the documentation from the LP site that says I can use email, and that cost me 3 days so far. [17:57] maxb: how do I do that? [17:57] The documentation should not be there if somebody is not to use it. I am not able to ask my developers to push a branch, some of them are "drive by" contributors. [17:58] lunch. [18:00] dickelbeck, your request to remove documentation is overbroad-- one aspect of doing this by mail didn't work, not all aspects. [18:00] dickelbeck, I routinely use email for commenting and making reviews. [18:00] dickelbeck, this is the first report I've had that this feature doesn't work. [18:01] That's about the only way I add comments for merging [18:02] dickelbeck, anyone who wants to propose a merge must have a launchpad account and bzr, so I don't understand why pushing would be an undue burden on drive-by contributors. [18:03] abentley: nest pyfoo lp:pyfoo foo <-- pyfoo is just a tag that you add and foo is? [18:03] abentley: sorry to cause you headaches today [18:04] MTecknology, foo is the directory where you want to place the contents of lp:pyfoo [18:04] if you want it just in / then omit? [18:04] MTecknology, in the common case, it will be "debian". [18:04] the branch I'm adding has a debian/ in it [18:05] MTecknology, the nest command does not support that. [18:05] MTecknology, if possible, use "merge" instead. [18:05] I am familiar with reporting a bug to Launchpad. Today I would like to put a question concerning Empathy 2.28.3 to Launchpad. How to do that? [18:05] abentley: I tried that and it didn't like me [18:05]