[03:44] <ScottK> maxb: That looks like it.  Thanks.
[03:45] <ScottK> I'd tried the non-LP conversion tools and failed at those.
[03:53] <ScottK> maxb: Thanks again.  Exactly what I needed.
[03:54] <ScottK> I got what I needed, so you can delete those if you want.
[07:17] <jfi> Hello, the upstream connection of https://launchpad.net/ubuntu/precise/+source/hddtemp is incorrect, is it possible to change it?
[07:19] <wgrant> jfi: What's the correct one?
[07:19] <jfi> wgrant: I don't know, but I am totaly sure that it is not psensor project
[07:19] <wgrant> I'll just remove it, then.
[07:19] <jfi> thanks!
[07:20] <wgrant> Done, for quantal too
[07:26] <jfi> fine, it has fixed the distribution packaging of the psensor trunk serie, but not the 'Downloads' section, I guess that it is not normal to have 20+ the download link to the source tarball (visible at the right of: https://launchpad.net/psensor/trunk)
[07:28] <wgrant> jfi: That's unrelated, but not normal.
[07:30] <jfi> wgrant: I am going to register a bug report for it, but maybe that's just a project setting mistake from me
[08:52] <gema> hi, I am trying to update some of our blueprints with "DROPPED" work items
[08:53] <gema> and the new work items error checker thinks dropped is not a valid state
[08:53] <gema> the code seems to indicate otherwise, any insights?
[08:56] <czajkowski> gema: not seen that status before, usually TODO, INPROGRESS, POSTPONED http://blog.launchpad.net/cool-new-stuff/work-items-in-blueprints
[08:57] <wgrant> gema: DROPPED is an alias for POSTPONED, but possibly only for imports from legacy data.
[08:57] <gema> wgrant, czajkowski so what do you guys suggest I use for items that are no longer needed?
[08:58] <wgrant> lib/lp/blueprints/workitemmigration.py:        elif status in (u'postpone', u'dropped', u'drop'):
[08:58] <wgrant> Yeah, only for the migrator
[08:58] <micahg> that seems like oversight to not have a dropped status
[08:58] <wgrant> gema: POSTPONED is the proper spelling
[08:58] <gema> wgrant: but they are not postponed, they are dropped
[08:58] <wgrant> postpone/drop/dropped get mapped to POSTPONED in the Launchpad model.
[08:58] <lifeless> delete them then
[08:59] <gema> wgrant: this is not about the model, it is about keeping a reasonable good track of the workflow, and history of what we've tried and got dropped
[08:59] <gema> for one reason or another
[08:59] <gema> lifeless: which is the reason why I haven't deleted them yet :)
[08:59] <wgrant> It is completely about the model. DROPPED is not supported as a distinct status in the model that Linaro implemented in Launchpad.
[09:00] <micahg> right, that seems like an oversight
[09:00] <micahg> at least as far as Ubuntu using it
[09:00] <wgrant> It's explicitly mapped to POSTPONED. Perhaps you use them differently.
[09:01] <gema> wgrant: I was trying to use the new work item box, and in there, I cannot save work items with "DROPPED" state
[09:01] <gema> it gives me an erro
[09:01] <gema> r
[09:01] <wgrant> As I said, it's only supported for the migration from whiteboards.
[09:01] <gema> the UI gives an error, it never reaches the back end
[09:01] <lifeless> gema: there is no workaround
[09:01] <lifeless> gema: you have two options:
[09:02] <gema> wgrant: any way I can ask for that to be supported?
[09:02] <lifeless>  - put a patch forward to make this match your workflow
[09:02] <lifeless>  - delete the items instead of keeping them around
[09:02] <gema> there are three:
[09:02] <lifeless> you can of course file a bug, but this is a feature supported by volunteer time
[09:02] <gema>   - stop using blueprints that get on the way of my workflow
[09:02] <gema> :P
[09:02] <wgrant> (the Launchpad team had nothing to do with the implementation of this feature)
[09:03] <wgrant> (or the design)
[09:03] <gema> wgrant: ack
[09:03] <lifeless> gema: we're poorly placed to answer questions like 'why isn't DROPPED supported'
[09:03] <gema> lifeless: yeah, I understand
[09:03] <gema> lifeless: how big of a patch do you think that would be?
[09:03] <lifeless> cool
[09:04] <gema> lifeless: I had a look at the code yesterday for other reason and there were too many lines for me to decide to dive in
[09:04] <lifeless> in principle its quite small, the risks I see are that perhaps Salgado etc did speak to Ubuntu about it and some consensus was reached not to use DROPPED, but that wasn't widely communicated
[09:05] <lifeless> so I'd suggest mailing the launchpad-dev list, which I'm pretty sure some of the implementors of this are on, and get a discussion rolling there.
[09:05] <gema> lifeless: ack
[09:05] <gema> lifeless: it is going to have to wait until after UDS, but it is on my TODO
[09:05] <gema> thanks
[09:05] <lifeless> no worries, sorry we can't do more, quicker.
[09:06] <lifeless> if you're at UDS, you can probably nab the relevant folk directly :)
[09:06] <gema> yeah, I will visit the launchpad clinic, I think
[09:07] <gema> I will print a list of all my launchpad headaches x)
[09:07] <gema> for the doctors
[09:07] <lifeless> thats a good idea too, but for this specific topic they are no more knowledgable :(
[09:07] <gema> lifeless: understood
[09:08] <czajkowski> gema: if you're doing that, can you add the bugs to the LP clinic page sent up
[09:08] <czajkowski> please
[09:08] <gema> czajkowski: so do you want me to file a bug for this too?
[09:11] <gema> lifeless: you've made my bug low priority
[09:11] <gema> lifeless: bug 991079 :(
[09:12] <lifeless> gema: thats correct.
[09:13] <gema> lifeless: it would help the QA team keep track of all the bugs we are trying to keep track of
[09:13] <lifeless> gema: you're welcome to fix it, but pretty much any of the high or critical priority bugs are affecting more users more seriously.
[09:13] <gema> lifeless: I disagree with the priority
[09:13] <Mkaysi> Aren't the top5 hottest bugs of Launchpad marked as low,triaged?
[09:13] <lifeless> gema: your options are: - log your API script in; escalate it via your LP stakeholder; submit a patch (or get someone else to do so for you)
[09:14] <lifeless> logging your API script in is the simplest and best thing
[09:14] <gema> lifeless: we'll do that, yes
[09:14] <lifeless> because if you are trying to do QA analysis without access to all the bugs, you're going to be missing all the apport private masters etc.
[09:14] <gema> lifeless: this is just to keep track of the bugs we raise without having to visit them all every day
[09:15] <gema> lifeless: which is a waste of time if there was no activity
[09:15] <gema> lifeless: basically trying to stop the polling of bugs
[09:15] <lifeless> you probably want to subscribe for notifications and process that instead of pinging all the bugs via the API, which is still polling.
[09:15] <lifeless> it will be faster.
[09:16] <gema> lifeless: I am subscribed by default to all the bugs in ubuntu
[09:16] <lifeless> (and scale better and use less server resources)
[09:16] <gema> lifeless: it doesn't scale for me, emails
[09:16] <lifeless> I'm not suggesting you personally get the mail
[09:16] <lifeless> whatever script you have
[09:16] <gema> lifeless: ahh, I see
[09:16] <czajkowski> gema: https://wiki.ubuntu.com/UDS-Q/LaunchpadClinic yes we'd like if poeple are coming to add their bugs to them so we have an idea if its possible to help and what can be done in advance
[09:17] <gema> czajkowski: I think lifeless just gave me enough insight to fix that one
[09:17] <czajkowski> gema: grand job
[09:17] <lifeless> gema: you can give it its own user account, subscribe it to any interesting bugs, then it can read just updates to them from its mailbox and add them to whatever report it generates
[09:18] <gema> lifeless: it is a web app, that keeps a timeline of events
[09:18] <gema> lifeless: I think I prefer to log it in
[09:18] <gema> lifeless: than to have to make it read and parse emails and then store them in the database, etc
[09:18] <lifeless> gema: how many bugs is it going to be tracking? 10's 100's 1000's or 10000's ?
[09:19] <gema> 10's
[09:19] <lifeless> ok, cool
[09:19] <gema> 100's tops
[09:19] <lifeless> go to town.
[09:19] <lifeless> for 10's, and even 100's we can cope with polling
[09:19] <gema> it's just an amount that one person can read
[09:19] <lifeless> beyond that the resources used seriously outweigh the complexity of doing event driven updates
[09:19] <gema> in a page
[09:20] <gema> lifeless: resources conversations to escale the infrastructure for our needs are being discussed, I think
[09:20] <gema> lifeless: we won't bring launchpad down , no worries :)
[09:20] <wgrant> gema: The BugActivity fix is literally 3 lines of code + a maybe test -- a good thing to get started with at UDS, I think :)
[09:21] <gema> wgrant: I will clone the code just in case I get very bored on my flight to UDS, but cannot make more promises :D
[09:22] <gema> wgrant: it's not the effort of changing the three lines, but of finding the 3 lines that need to change that scares me
[09:22] <wgrant> Sure
[09:22] <wgrant> That's where the Launchpad Clinic is probably helpful :)
[09:22] <gema> wgrant: and I wouldn't want to be responsible for breaking launchpad authentication :P
[09:23] <wgrant> Heh
[09:23] <wgrant> That would be bad, but this is pretty isolated.
[09:25] <gema> wgrant: ack, will try
[09:28] <lifeless> gema: scaling isn't as easy as one might think :)
[09:29] <gema> lifeless: we'll have to make it happen somehow!
[09:30] <gema> back to blueprinting, thanks for your help, guys
[09:35] <lifeless> gema: for doing more API requests, the way to scale is to use an event driven system and not poll
[09:36] <lifeless> gema: adding more DB bandwidth is possible, but only to a degree before it gets sharply expensive; rewriting Launchpad to be on a scalable backend is a whole different cost proposition
[09:40] <gema> lifeless: is there a way to subscribe to events now?
[09:41] <gema> lifeless: or are we talking massive rearchitecturing of launchpad?
[09:42] <lifeless> for now, email
[09:42] <lifeless> its event driven
[09:42] <lifeless> we have a longpoll system too, but its not -quite- ready for widespread use/.
[09:42] <gema> lifeless: so you are actually working on a better solution
[09:43] <gema> lifeless: I don't mind to do some beta testing of it, whenever you are ready :D
[10:21] <bobweaver> hello there i am looking for simple easy too fix and package back up projects as I am board. I am not the greatest packager or engineer but i can get around well. any Ideas if there is a team like this? or if there is a way too search on LP to get such bugs ?
[10:21] <wgrant> bobweaver: You probably want #ubuntu-motu.
[10:21] <bobweaver> thanks wgrant
[13:14] <facundobatista> Hola a todos!
[13:15] <facundobatista> Question: I'm migrating a project from a SVN repo to Launchpad... is there a way to play with commit authors? The idea is to relate the commits that has a previous name to the new name of the same person in LP
[13:15] <facundobatista> Thanks!
[13:19] <dobey> facundobatista: i don't think there is any way to do that automatically, no
[13:20] <facundobatista> dobey, and no automatically?
[13:20] <facundobatista> dobey, or with "no automatically" you mean doing a request for a losa to do that?
[13:21] <dobey> facundobatista: i mean the only way i can think of to do it reliably, is to manually alter every commit in the history
[13:21] <dobey> facundobatista: and it's probably not worth the time/trouble to do that
[13:28] <facundobatista> ah, right
[13:28] <facundobatista> dobey, thanks!
[14:27] <maxb> facundobatista: To do that, you'd need to manage the conversion yourself, and just push up the resulting bzr branches to Launchpad
[14:28] <maxb> But really, it's probably not worth it, because then you'd have to use a once-off conversion tool to migrate out of, svn, whereas the bzr-svn integration generally does a better job of translating history
[14:33] <facundobatista> maxb, thanks!
[17:31] <arges> can anyone help with making a project private?
[18:35] <arges> anybody around who can help with a launchpad project?
[19:20] <s9iper1> anybody help me in signing the PGP key ?
[19:22] <dobey> s9iper1: key signing is usually done when the person can verify the person whose key is being signed, is who they claim to be
[19:24] <s9iper1> dobey; i dont understand do i need somebody else or request him to sign my key or what ?
[19:25] <dobey> s9iper1: i don't know what you are asking. you are asking for someone to sign a PGP key?
[19:28] <s9iper1> no i am asking for the guide line to sign it .. see i generate my key..send it to server but when i enter my fingerprint into launchpad to add it than launchpad said no such key. can you do something for me that how can i get it .. and here is another question arise i have seen my pgp key there is no fingerptint in it,, so the question is that if the key has no fingerprint than how can launchpad recognize it..?
[19:29] <dobey> what server did you send the key to?
[19:29] <dobey> it has to be on keyserver.ubuntu.com
[19:30] <s9iper1> yes that one
[19:30] <dobey> what is the fingerprint?
[19:31] <s9iper1> DB0E 32C3 8349 5697 0E89
[19:31] <s9iper1> 7143 0AB6 796F 24B4 AA30
[19:31] <dobey> err, what is the key id?
[19:32] <s9iper1> dobey 24B4AA30
[19:34] <s9iper1> dobey: is that right step that while copy paste to the keyserver we should export a text file and than copy paste that file without  editing it to the server ?
[19:34] <dobey> i don't know what you're asking, but probably not
[19:35] <dobey> your key is not on the key server
[19:35] <s9iper1> can you see my pgp key which i have copy pasted  on the server i send you in private ?
[19:36] <s9iper1> dobey: can i send u /?
[19:37] <dobey> i just searched for that key id on the server, and there were no results
[19:37] <dobey> i guess you uploaded it wrong perhaps
[19:38] <s9iper1> dobey: i export the key from keys and password and than just copy pasted it to this site http://keyserver.ubuntu.com/
[19:39] <s9iper1> the export was in text file with ASc formate
[19:43] <dobey> s9iper1: the private key or the public key?
[19:44] <s9iper1> public
[19:44] <s9iper1> open pgp key
[19:47] <dobey> ok, i don't know, but your key isn't on the server
[19:47] <dobey> you can search for the key id yourself
[19:49] <s9iper1> dobey: i get this message now from launchpad  see
[19:49] <s9iper1> A message has been sent to s9iper1@gmail.com, encrypted with the key 2048R/24B4AA30. To confirm the key is yours, decrypt the message and follow the link inside.
[19:49] <dobey> ok then maybe it showed up
[19:49] <dobey> and you were just being impatient
[19:50] <s9iper1> dobey what should i do now i have 2 links on it and both have the wiki page link
[19:50] <s9iper1> https://help.launchpad.net/ReadingOpenPgpMail
[19:50] <s9iper1> https://help.ubuntu.com/community/GnuPrivacyGuardHowto
[19:50] <dobey> well read the links then
[20:25] <rye> hi, i have deactivated my testing account - ~rt-test, launchpad logged me out. After a while i clicked login again and here I am, https://launchpad.net/~rt-test-deactivatedaccount
[20:33] <lifeless> rye: yes, and ? :)
[20:33] <lifeless> rye: you need to log out of LP and out of SSO
[20:46] <rye> lifeless: i did that and can relogin freely
[20:46] <rye> lifeless: i can even rename myself
[20:51] <lifeless> rye: of course
[20:51] <lifeless> rye: when you login with an SSO account, LP rejoins you and reactivates if needed.
[20:51] <Nafallo> rye: now try to rename lifeless... ;-)
[20:51] <lifeless> rye: if yo uwant the account gone, deactivate it, log out of SSO, log in to SSO as a new account, log into LP
[20:53] <rye> lifeless: erm... what about some malicious users who spam a lot, are they deactivated using the same mechanism?
[20:53]  * rye has an idea
[20:54] <rye> https://launchpad.net/~lifeless-deactivatedaccount
[20:55] <lifeless> rye: they get suspended and cannot log in at all
[20:55] <lifeless> rye: whats the back story here
[20:55] <lifeless> rye: what are you trying to achieve ?
[20:55] <lifeless> https://launchpad.net/~rye-deactivatedaccount
[20:56] <rye> lifeless: oh, i was testing our ISD RT and created an account, then I deactivated it (it said I will never be able to login again) and I did login again
[20:56] <lifeless> so, it lies :) did you file a bug ?
[20:56] <rye> lifeless: i will test this on demo, i wonder what happens when there is a -deactivatedaccount user id already
[20:56] <lifeless> you get -deactivatedaccount-deactivatedaccount
[20:57] <rye> lifeless: ok, you win, you are a superuser
[20:57] <lifeless> rye: quasi, yes.
[20:57] <rye> lifeless: no, i mean I register "user1", and "user1-deactivatedaccount" and try to deactivate user1
[20:57] <lifeless> rye: you will get user1-deactivatedaccount-deactivatedaccount
[20:57] <lifeless> rye: I knew what you meant.
[20:58] <rye> lifeless: i will test this on demo and file a bug for the promise of being not able to log in ever
[20:58] <lifeless> cool
[20:58] <lifeless> thanks
[20:59] <rye> lifeless: also, I am not in the part of the team that makes desktop releases for U1 but poking more and more places of launchpad for indicator-ubuntuone I am really fascinated by all the functionality, thank you all very much for launchpad :)
[21:00] <lifeless> rye: cool, glad you like it ;)