[00:58] <melodie> hi
[00:59] <melodie> 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] <wgrant> melodie: What's the problem?
[00:59] <melodie> I followed the instructions from this page: https://help.launchpad.net/ReadingOpenPgpMail
[00:59] <melodie> very carefully
[01:00] <melodie> I use Sylpheed, and while trying to decypher the message with the said action, I got an error message
[01:00] <melodie> I tried to remove the * at the beginning of the command, but same, an error message
[01:00] <melodie> so I tried with command line:
[01:01] <melodie> did a "save to /tmp" and did a command line : gpg --decrypt nameofmail
[01:01] <melodie> and then a new error message that said something about the end of line not good
[01:01] <melodie> therefore I removed the text around the message and left just the message with beginning and end of message
[01:01] <melodie> then I could read the message
[01:02] <melodie> the "gpg --decrypt my-message" prompted me for my pass phrase and I could get to it.
[01:02] <melodie> I thought I should report it somewhere. others may not have the idea to do this way to solve the problem.
[01:03] <melodie> I would suggest to send the whole message encrypted, to avoid trouble.
[01:03] <melodie> wgrant: is that explained well enough ?
[01:04] <wgrant> What was the error message from within Sylpheed?
[01:04] <melodie> I check and paste it here
[01:04] <wgrant> 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] <melodie> it is in French : do you mind or do I open sylpheed in english ?
[01:05] <wgrant> Inline encryption lets anyone copy it out easily, to work around problems like you just had :)
[01:05] <melodie> English
[01:05] <wgrant> I can probably get the gist of it in French.
[01:05] <melodie> --- Terminé : gpg --no-tty --command-fd 0 --passphrase-fd 0 --decrypt /home/joyce/.sylpheed-2.0/mimetmp/00000009.mimetmp |
[01:05] <melodie> sh: -c: line 1: Erreur de syntaxe : fin de fichier prématurée
[01:05] <wgrant> Huh
[01:05] <wgrant> You had selected the whole inline message block?
[01:05] <melodie> with the * at the beginning or without is the same error message
[01:05] <wgrant> AIUI those sylpheed operations operate on the currently selected text.
[01:06] <melodie> I had selected nothing : where is it written that I should select the text before hitting the action menu ?
[01:06] <melodie> o_o
[01:06] <melodie> :)
[01:06] <melodie> then maybe this detail might be added to the doc at that page ? :)
[01:06] <melodie> what do you think ?
[01:06] <wgrant> The %p means selected content. I think %f runs over the whole file.
[01:07] <melodie> I am the kind of girl who doesn't know about such details. /o\
[01:07] <wgrant> 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] <melodie> wo who !
[01:08] <melodie> 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] <melodie> :D
[01:08] <wgrant> Heh
[01:08] <wgrant> I'll update the help wiki to say you have to select the message.
[01:08] <wgrant> Thanks for letting us know.
[01:08] <melodie> would you know of a Debian mentor for my firt package ? ;D
[01:08] <melodie> wgrant: thank you very much ! ^^
[01:09] <wgrant> #debian-mentors on OFTC might be your best bet for that :)
[01:09] <wgrant> np
[01:09] <wgrant> I've updated the docs.
[01:09] <melodie> 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] <wgrant> Heh
[01:10] <melodie> now I'll try to make it get to ppa, while waiting for it to get further
[01:10] <wgrant> Good plan.
[01:10] <melodie> thanks.
[01:10] <melodie> thanks for having updated the doc !
[01:11] <wgrant> :)
[01:12]  * wgrant wanders off for a while.
[01:12] <melodie> there is still something wrong but I can't find out what
[01:15] <melodie> wgrant: I have selected the part which is crypted and I still get the same message error
[01:17] <wgrant> melodie: Including the BEGIN and END line?
[01:17] <melodie> Yes, I tried both, but now I might have a clue
[01:17] <melodie> I check and I tell you in 2 seconds
[01:18] <wgrant> Did you readd the *?
[01:18] <wgrant> "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] <melodie> wgrant: now that works. I had to close Sylpheed and reopen it for that.
[01:19] <wgrant> Aha
[01:20] <wgrant> I've never used it.
[01:20] <melodie> 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] <melodie> )
[01:21] <melodie> 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] <wgrant> Great.
[01:24] <melodie> 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] <melodie> so...
[01:25] <melodie> maybe would you also want to advise to quit the app and restart it after configuring new actions ? :)
[01:26] <wgrant> Done
[01:28] <melodie> thanks again.
[01:31] <melodie> can you do anything about the code of conduct ? there is a fault of spelling. XD
[01:31] <melodie> s/behaviour/behavior/
[01:32] <melodie> and there is one more error. I will try to find who can do something
[01:32] <melodie> https://launchpad.net/codeofconduct/1.1/+download
[01:33] <wgrant> melodie: "behavior" is US English, pretty much everywhere else uses "behaviour"
[01:33] <melodie> wgrant: then I need to find one more dictionnary for Firefox
[01:33] <melodie> what about minimises ?
[01:33] <melodie> it says it should be written with a z inside
[01:33] <wgrant> z/s is again US vs world
[01:33] <melodie> minimizes
[01:33] <melodie> oh oh §
[01:34] <melodie> !
[01:34] <melodie> my dictionnary is us then
[01:34] <melodie> ok, never mind.
[01:34] <wgrant> 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] <melodie> I installed the English UK addon for Firefox
[01:36] <melodie> this way I can check with both
[01:36] <wgrant> Great.
[01:37] <melodie> this is a good addition. there are way too many things to learn in file. :D
[01:37] <melodie> lief
[01:37] <melodie> no
[01:37] <melodie> life
[01:37] <melodie> pff
[01:37] <melodie> sorry. :D
[01:38] <melodie> would you advise me on a name for a ppa ?
[01:44] <melodie> thanks again, and good night
[15:41] <alo21> hi all
[15:42] <alo21> I would like to fix bug... could you tell where I can find easy one?
[20:11] <ondrej> 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:12] <czajkowski> done
[21:17] <pavolzetor> hi guys,
[21:17] <pavolzetor> is there any way to track ppa downloads?
[21:17] <pavolzetor> demographics, stats
[21:17] <pavolzetor> so I will know, who and where uses my app, and how many users I do have
[21:22] <lifeless> there is an API that will give you aggregate download statistics
[21:22] <lifeless> due to UK/EU regulation we can't disclosure personally identifying information
[21:23] <pavolzetor> http://blog.launchpad.net/cool-new-stuff/tracking-ppa-download-statistics
[21:24] <pavolzetor> thnkas going to explore,
[22:19] <thumper> lifeless: hey hey, you around?
[22:19] <lifeless> yup
[22:19] <thumper> so... personal bug lists
[22:19] <thumper> was talking with the lp peeps
[22:20] <thumper> and they said you wouldn't likely block it as long as I deleted enough code
[22:21] <thumper> lifeless: what are your thoughts?
[22:21] <lifeless> I've a great deal of interest in seeing LP become more powerful :).
[22:21] <thumper> and by that you mean what?
[22:22] <lifeless> 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] <thumper> ok...
[22:22] <thumper> for me this is the ability to have a single priority list of bugs
[22:22] <thumper> which people can then attack from the top
[22:23] <lifeless> There are a few conceptual discussions around personal bugs lists
[22:23] <thumper> and having shared write access to the list
[22:23] <lifeless> from the very simple to the radically different
[22:23] <thumper> I have a relatively defined set of criteria I need
[22:23] <thumper> and happy to actually write and mentor things through
[22:23] <lifeless> you want a work queue for a team
[22:23] <thumper> although I'd like some help
[22:23] <thumper> lifeless: yes I do, priority queue :)
[22:23] <lifeless> team maintained and team executable, right ?
[22:24] <thumper> well, the team doing the work isn't the same team setting the priority
[22:24] <thumper> :)
[22:24] <thumper> need write by distro, design, tech team lead
[22:24] <thumper> to have a common agreed priority bug list
[22:25] <lifeless> so, if you had (task, team, priority)
[22:25] <thumper> write by a few distro people (not everyone )
[22:25] <thumper> yeah, that is about as complicated as my schema goes :)
[22:25] <lifeless> as a generic thing, with a editing facility and a view facility
[22:25] <thumper> yes
[22:25] <thumper> that's about it
[22:26] <lifeless> 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] <thumper> that is pretty much what I thought too
[22:26] <thumper> not too complicated
[22:27] <lifeless> 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] <thumper> although...
[22:27] <thumper> perhaps we want the possibility of multiple priority lists for a team
[22:27] <thumper> which would imply another table
[22:27] <lifeless> why ?
[22:27] <thumper> allowing a name, and display name
[22:27]  * thumper shrugs
[22:27] <thumper> well
[22:27] <thumper> right now, I only need one
[22:27] <thumper> but what about later?
[22:27] <lifeless> simple is good, folk can build up their own things on top of it.
[22:28] <thumper> yes
[22:28] <lifeless> just add another team, make the first one a member, and you've got another list.
[22:28] <thumper> I guess if you want more than one list
[22:28] <lifeless> with the same ACL.
[22:28] <thumper> make another team
[22:28] <thumper> right?
[22:28] <lifeless> 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] <lifeless> but doing named lists would be a 33% increase in data to process (and a corresponding decrease in performance)
[22:29] <thumper> so... we would address this later if needed?
[22:29] <lifeless> right
[22:31] <thumper> I'd even be fine with just a web view, and rest write interface
[22:31] <lifeless> 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] <lifeless> for your needs
[22:31] <thumper> ok
[22:31] <lifeless> I'll review on a technical basis, mrevell can identify any product issues, and then we can get rolling
[22:31] <thumper> I'll try to get to it soonish
[22:31] <thumper> ok, cool