[00:58] hi [00:59] if there is someone here, I would like to report a small issue while receiving a confirmation by mail after I send gpg keys fingerprint to launchpad [00:59] melodie: What's the problem? [00:59] I followed the instructions from this page: https://help.launchpad.net/ReadingOpenPgpMail [00:59] very carefully [01:00] I use Sylpheed, and while trying to decypher the message with the said action, I got an error message [01:00] I tried to remove the * at the beginning of the command, but same, an error message [01:00] so I tried with command line: [01:01] did a "save to /tmp" and did a command line : gpg --decrypt nameofmail [01:01] and then a new error message that said something about the end of line not good [01:01] therefore I removed the text around the message and left just the message with beginning and end of message [01:01] then I could read the message [01:02] the "gpg --decrypt my-message" prompted me for my pass phrase and I could get to it. [01:02] I thought I should report it somewhere. others may not have the idea to do this way to solve the problem. [01:03] I would suggest to send the whole message encrypted, to avoid trouble. [01:03] wgrant: is that explained well enough ? [01:04] What was the error message from within Sylpheed? [01:04] I check and paste it here [01:04] melodie: It'd be nice to use OpenPGP/MIME, but then anyone using a webmail or Windows mail client would be in trouble. [01:05] it is in French : do you mind or do I open sylpheed in english ? [01:05] Inline encryption lets anyone copy it out easily, to work around problems like you just had :) [01:05] English [01:05] I can probably get the gist of it in French. [01:05] --- Terminé : gpg --no-tty --command-fd 0 --passphrase-fd 0 --decrypt /home/joyce/.sylpheed-2.0/mimetmp/00000009.mimetmp | [01:05] sh: -c: line 1: Erreur de syntaxe : fin de fichier prématurée [01:05] Huh [01:05] You had selected the whole inline message block? [01:05] with the * at the beginning or without is the same error message [01:05] AIUI those sylpheed operations operate on the currently selected text. [01:06] I had selected nothing : where is it written that I should select the text before hitting the action menu ? [01:06] o_o [01:06] :) [01:06] then maybe this detail might be added to the doc at that page ? :) [01:06] what do you think ? [01:06] The %p means selected content. I think %f runs over the whole file. [01:07] I am the kind of girl who doesn't know about such details. /o\ [01:07] See section 13.4 of http://sylpheeddoc.sourceforge.net/en/manual/manual-13.html. Could you try with %f? Perhaps we should update the docs to use that instead. [01:07] wo who ! [01:08] I would not want to hurt your feeling, but I don't fancy reading so many docs to get to one aim. I already read man gpg a lot... [01:08] :D [01:08] Heh [01:08] I'll update the help wiki to say you have to select the message. [01:08] Thanks for letting us know. [01:08] would you know of a Debian mentor for my firt package ? ;D [01:08] wgrant: thank you very much ! ^^ [01:09] #debian-mentors on OFTC might be your best bet for that :) [01:09] np [01:09] I've updated the docs. [01:09] wgrant: I have been there. I was just kidding, because I used quite some time to get to learn to make a package as fast as I could. :) [01:10] Heh [01:10] now I'll try to make it get to ppa, while waiting for it to get further [01:10] Good plan. [01:10] thanks. [01:10] thanks for having updated the doc ! [01:11] :) [01:12] * wgrant wanders off for a while. [01:12] there is still something wrong but I can't find out what [01:15] wgrant: I have selected the part which is crypted and I still get the same message error [01:17] melodie: Including the BEGIN and END line? [01:17] Yes, I tried both, but now I might have a clue [01:17] I check and I tell you in 2 seconds [01:18] Did you readd the *? [01:18] "Prepending *: this will allow you to send to the command's standard input a text that you will enter in a dialog window. But in contrast to prepending >, the entered text is hidden (useful when entering passwords)." [01:19] wgrant: now that works. I had to close Sylpheed and reopen it for that. [01:19] Aha [01:20] I've never used it. [01:20] once I hit the command in the menu action, after having selected the text, including entry and end of encrypted part, I am prompted the passphrase in a small window, then I can read the message. this works in French as well as in English (if I start Sylpheed from a console with the "LANG=C" environment. [01:20] ) [01:21] wgrant: it works indeed with the full command line as provided, with the * at the beginning and the | at the end of the command line. [01:24] Great. [01:24] wgrant: fun ! now it works even without selecting the encrypted part. I think maybe the trick would have been to close and reopen Sylpheed after having set up the new actions. [01:24] so... [01:25] maybe would you also want to advise to quit the app and restart it after configuring new actions ? :) [01:26] Done [01:28] thanks again. [01:31] can you do anything about the code of conduct ? there is a fault of spelling. XD [01:31] s/behaviour/behavior/ [01:32] and there is one more error. I will try to find who can do something [01:32] https://launchpad.net/codeofconduct/1.1/+download [01:33] melodie: "behavior" is US English, pretty much everywhere else uses "behaviour" [01:33] wgrant: then I need to find one more dictionnary for Firefox [01:33] what about minimises ? [01:33] it says it should be written with a z inside [01:33] z/s is again US vs world [01:33] minimizes [01:33] oh oh § [01:34] ! [01:34] my dictionnary is us then [01:34] ok, never mind. [01:34] http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences#-our.2C_-or http://en.wikipedia.org/wiki/American_and_British_English_spelling_differences#-ise.2C_-ize_.28-isation.2C_-ization.29 [01:36] I installed the English UK addon for Firefox [01:36] this way I can check with both [01:36] Great. [01:37] this is a good addition. there are way too many things to learn in file. :D [01:37] lief [01:37] no [01:37] life [01:37] pff [01:37] sorry. :D [01:38] would you advise me on a name for a ppa ? [01:44] thanks again, and good night === Resistance is now known as EvilResistance === EvilResistance is now known as Resistance === jalcine is now known as Jacky [15:41] hi all [15:42] I would like to fix bug... could you tell where I can find easy one? === Guest67073 is now known as Ursula === Ursula is now known as Guest37794 === Guest37794 is now known as Ursula_ === Ursula_ is now known as Ursinha [20:11] hi, can somebody moderate: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/876387/comments/40 (haven't found where to report directly in launchpad) [20:11] Ubuntu bug 876387 in psmisc (Ubuntu Oneiric) "fuser forking uncontrollably in cron job" [High,Triaged] [20:12] done [21:17] hi guys, [21:17] is there any way to track ppa downloads? [21:17] demographics, stats [21:17] so I will know, who and where uses my app, and how many users I do have [21:22] there is an API that will give you aggregate download statistics [21:22] due to UK/EU regulation we can't disclosure personally identifying information [21:23] http://blog.launchpad.net/cool-new-stuff/tracking-ppa-download-statistics [21:24] thnkas going to explore, === wedtm is now known as wedtm|away === wedtm|away is now known as wedtm [22:19] lifeless: hey hey, you around? [22:19] yup [22:19] so... personal bug lists [22:19] was talking with the lp peeps [22:20] and they said you wouldn't likely block it as long as I deleted enough code [22:21] lifeless: what are your thoughts? [22:21] I've a great deal of interest in seeing LP become more powerful :). [22:21] and by that you mean what? [22:22] I mean that I like features being added, as long as we can maintain them - which is what deleting code is about, keeping the total codebase size under control [22:22] ok... [22:22] for me this is the ability to have a single priority list of bugs [22:22] which people can then attack from the top [22:23] There are a few conceptual discussions around personal bugs lists [22:23] and having shared write access to the list [22:23] from the very simple to the radically different [22:23] I have a relatively defined set of criteria I need [22:23] and happy to actually write and mentor things through [22:23] you want a work queue for a team [22:23] although I'd like some help [22:23] lifeless: yes I do, priority queue :) [22:23] team maintained and team executable, right ? [22:24] well, the team doing the work isn't the same team setting the priority [22:24] :) [22:24] need write by distro, design, tech team lead [22:24] to have a common agreed priority bug list [22:25] so, if you had (task, team, priority) [22:25] write by a few distro people (not everyone ) [22:25] yeah, that is about as complicated as my schema goes :) [22:25] as a generic thing, with a editing facility and a view facility [22:25] yes [22:25] that's about it [22:26] you could model your ACL by having a team 'ubuntu-desktop-bugs-priority', anyone in that team can edit it, and as its a public team, anyone can see it. [22:26] that is pretty much what I thought too [22:26] not too complicated [22:27] that in itself wouldn't support rich integration (e.g. showing a priority on regular bug listings) [because of performance and UI issues: 1:M on task means you may have many priorities to show] [22:27] although... [22:27] perhaps we want the possibility of multiple priority lists for a team [22:27] which would imply another table [22:27] why ? [22:27] allowing a name, and display name [22:27] * thumper shrugs [22:27] well [22:27] right now, I only need one [22:27] but what about later? [22:27] simple is good, folk can build up their own things on top of it. [22:28] yes [22:28] just add another team, make the first one a member, and you've got another list. [22:28] I guess if you want more than one list [22:28] with the same ACL. [22:28] make another team [22:28] right? [22:28] right, you can say its a workaround, but its one that if people are doing we can address by adding a name facility. [22:29] but doing named lists would be a 33% increase in data to process (and a corresponding decrease in performance) [22:29] so... we would address this later if needed? [22:29] right [22:31] I'd even be fine with just a web view, and rest write interface [22:31] so, I suggest you do a minimal LEP, don't worry about implementation stuff there, try to make sure that you have enough functionality listed that it would be usable [22:31] for your needs [22:31] ok [22:31] I'll review on a technical basis, mrevell can identify any product issues, and then we can get rolling [22:31] I'll try to get to it soonish [22:31] ok, cool === weddy is now known as weddy|away === epsy is now known as \u03b5 === weddy|away is now known as weddy