/srv/irclogs.ubuntu.com/2011/01/08/#launchpad-dev.txt

lifelesswgrant: hi00:20
lifelesswgrant: do you know of any soyuz services that do librarian uploads (directly)00:21
wgrantlifeless: process-upload.py, buildd-manager, process-pending-packagediffs.py00:22
wgrantThere may be more... thinking...00:22
wgrantgina00:23
wgrantPossibly process-accepted.py, for translations stuff.00:23
wgrantAlso the mirror prober, although most seem so not think that it's Soyuz.00:24
lifelesswgrant: there is an rt needs to know01:01
wgrantlifeless: Which ticket?01:04
lifelesswgrant: HA librarian upload, in the launchpad queue01:35
lifelesswgrant: we need the machines those soyuz things run on added to firewall rules01:35
wgrantlifeless: Perhaps the ticket is not visible to warthogs.01:37
wgrantI cannot see it.01:37
lifelessbah02:40
lifelessuhm02:40
lifelessit is visible to warthogs02:40
lifeless4137902:43
lifelesswgrant: ^02:43
wgrantlifeless: Oh, it's using a custom status that's not in the default filter.02:44
wgrantlifeless: So: cesium, cocoplum, germanium, iron at least need adding to the list.02:48
wgrantI'm also somewhat surprised that loganberry isn't there.02:49
=== Ursinha-afk is now known as Ursinha
=== yofel_ is now known as yofel
pcjc2is there any guide / examples which I could follow for writing a git commit hook to change bug statuses in LP ?11:59
pcjc2I'm figuring that I need to setup a LP account for my "commit hook", so it can authenticate as "gpleda.org Commit Hook robot" or something11:59
pcjc2The intention is to parse our git commits for "Closes-bug: lp-12345", and turn that into an API request which closes the bug12:00
pcjc2I figure it is easiest to have the robot user close the bug, but it would also be possible (in theory at least), to grab the committer / author email from the commit, look them up on LP (or via a mapping table we could maintain locally), then _pretend_ the bug closure was done by that user12:01
pcjc2(Although I'm not sure how to go about getting developers to authorise the robot to close bugs on their behalf)12:02
maxbto do that, the robot would have to have access to impersonate all your committers. Unlikely they'd accept that12:02
pcjc2"they" as in LP, or "they" as in our developers?12:02
maxbthe rest ought to be pretty trivial with python's launchpadlib12:02
maxbb = lp.bugs[12345]; b.status = "Fix Released"; b.lp_save()  ---- or thereabouts12:03
pcjc2Getting the robot to authenticate might be an issue, but I've not read into it so much12:03
pcjc2maxb: That IS easy.. (easier than I expected) ;)12:03
maxbYou probably want to add a comment to the bug too12:04
pcjc2of course.. with a link to the SHA1 which closed it12:04
pcjc2copy the commit message too - whatever12:04
pcjc2doesn't the robot / LP-lib client have to log on via OpenID ?12:04
maxbNo, OAuth12:05
* pcjc2 reads https://help.launchpad.net/API/SigningRequests12:07
pcjc2we could get our developers to opt-in and allow the robot to impersonate them I guess? From the sounds of that12:08
maxbwell, you'd have to get them to opt-in to allowing your bot to impersonate them for any api action on Launchpad12:11
maxbanyone with any sort of security instinct would refuse12:11
maxbI would12:12
maxboh, one thing I missed from my pseudo-code is that you need to change status on a bug_task not a bug12:14
maxbSo you iterate the bug.bug_tasks collection to find the one that is for your project12:15
pcjc2got it.12:15
pcjc2Stupid question - how should I go about creating a LP user for my bot?12:16
maxbJust sign up as a new user, using a dedicated email address for the bot12:16
pcjc2(And presumably I can manually go through the steps of authenticating the bot to that user, then store the auth keys in the bot)12:17
maxbindeed12:17
pcjc2hmm - that is not so good... if I need a dedicated email for the bot12:17
pcjc2I don't have one - and I can't think where to set one up which isn't amaturish12:17
pcjc2mybot@gmail.com or whatever12:17
pcjc2Any way to have a bot without an email address?12:18
maxbLP users are always identified by their email address12:19
wgrantAn active Launchpad account requires an email address, unfortunately.12:19
pcjc2Imported users from SF don't always have email addresses - is that a special case?12:22
wgrantThey're not active.12:22
pcjc2I've asked our project admin to set up an email address (If possible) on the domain hosting out git repository13:31
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
maxbpcjc2: Oh, by the way, if you want to track people closing bugs, you might choose to change the assignee of the bug task (if it's not already set) in your robot16:02
pcjc2maxb: good idea17:15
pcjc2A friend of mine set up an email alias with his domain provider, so... I now have:17:15
pcjc2https://launchpad.net/~gpleda-launchpad-robot17:15
pcjc2(Now just have to write the code to make it do my bidding ;))17:16
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
pcjc2https://login.launchpad.net/+forgot_password20:35
pcjc2Does that require any lp-dev interaction - there are a few of our users who want to do bug triage, but they have forgotten their LP passwords20:36
pcjc2apparently they haven't received any email with confirmation code20:42
pcjc2anyone about?20:50
lifelesshi20:50
pcjc2Apparently the email sent by https://launchpad.net/people/+requestmerge?field.dupe_person=djdelorie is not going through for that user20:51
lifelesslp no longer stores passwords20:51
=== al-maisan is now known as almaisan-away
lifelessthats really an alias to login.ubuntu.com20:51
pcjc2I got the wrong end of the stick with the original complaint20:51
pcjc2he wants to merge ~djdelorie and ~dj-delorie20:51
lifelessah ok20:51
pcjc2(~dj-delorie is the registered on LP account, but he wishes to rename it to ~djdelorie (the one which will be merged), once the merge is done)20:52
lifelesssure20:52
lifelessso what happens when he merges20:52
pcjc2DJ is a smart guy (developer of DJGPP and all that), so I trust him when he says the mail doesn't get through - he's been watching his server logs20:52
pcjc2the email alias from the bug import I had is djdelorie@users.sf.net20:52
pcjc2but it would appear the confirmation email is getting lost in the process20:52
lifelessok20:53
lifelessso possibilities are:20:53
lifeless - our outbound mail is on the blink (low, very reliable service)20:53
lifeless - greylisting is in place at one or more of the mail providers chaining through users.sf.net20:54
lifeless - the mail chain is incorrect and mail to djdelorie@users.sf.net doesn't end up where you'd want it to20:54
lifelessAIUI the usual thing is greylisting20:54
pcjc2strange thing is my bug export has djdelorie@users.sf.net20:54
pcjc2but he says when he tries to claim it, Launchpad says the email is going to djdelorie@users.sourceforge.net20:55
pcjc2any chance we can cheat this one, or does that need a LOSA?20:55
lifelessthere is a link on the page to file support tickets20:55
lifelessunder 'note:'20:55
lifelessalso this is a email address search bug20:56
lifelesssorry20:56
lifelessspam protection bug20:56
lifelessshouldn't be able to get the email address for an arbitrary user by requesting a merge20:56
lifelesspcjc2: please let him know I clicked through myself to verify, so one of the confirmations he may receive is to merge with me... I advise against doing that :)20:56
pcjc2he just got YOUR email lifeless ;)20:57
pcjc2but he never got his own20:57
lifelessinteresting20:57
lifelessuhm20:57
pcjc2he's going to try again20:57
lifelessdoes he have (in his active account) his email address hidden?20:57
pcjc2yes20:58
lifelessit can be set to show-always, show-loggedin-users, hide-completely20:58
lifelesswhat From: and sender: did the one he got, have?20:58
pcjc2he's now whitelisted the @sf.net email address20:58
pcjc2Turns out it liked your email, but not his own20:58
lifelesshis spam filter?20:58
lifelesswhat From: and sender: did the email from me have?20:59
pcjc2yes, apparently20:59
lifelessand what ones did the one from him have, if he's gotten one now20:59
pcjc2hi gde (@lifeless, gde was the other person who is stuck with the merge)20:59
lifelesspcjc2: I'm wondering if mail-confidentiality settings are preventing correct sending of the mail21:01
gdelifeless: pcjc2 Hi there21:01
lifelesspcjc2: so if you can get those questions answered, that would be great21:01
pcjc2lifeless: He got it in the end, but I've asked him for the info21:01
lifelesspcjc2: also say, hi, long time no see ;)21:01
pcjc2(21:02:03) djgpp: To: djdelorie@users.sf.net21:02
pcjc2(21:02:04) djgpp: From: Launchpad Account Merge <noreply@launchpad.net>21:02
pcjc2(21:02:10) djgpp: Sender: bounces@canonical.com21:02
lifelesspcjc2: thats after he whitelisted?21:02
lifelesspcjc2: I'm guessing the one from me had my email address in the from: ?21:02
pcjc2All emails came from the same From address21:05
lifelessinteresting21:05
pcjc2and it turns out, were only received after he whitelisted the @sf address21:05
pcjc2So the thing which was misleading was the address which LP claimed to be sending email to21:05
lifelesshow so?21:05
pcjc2The lack of merge request was apparently just due to some spam filter / server setting21:05
lifelessdjgpp: hi, thanks for dropping in21:05
djgpphi21:06
djgppwhen I tried to recover a lost password on "djdelorie", it said it was sending a confirmation token to djdelorie@users.sourceforge.net21:06
djgpp(I still haven't gotten those mails yet though)21:06
lifelessthats very odd21:06
lifelesswhen I tried it it said "An email message was sent to djdelorie@users.sf.net. Please follow the instructions on that message to complete the merge."21:06
pcjc2ahh.. I guess that is the leak21:06
djgppthe two merge requests came through to "To: djdelorie@users.sf.net"21:07
lifelesswe don't have a dba/sysadmin handing around in the weekends, and our staging copy won't have your data in it yet.21:07
lifelessbut I can arrange to look next week and see if there are two emails on the ~djdelorie account21:07
djgppand I can get my icon to change...21:08
djgppwell, there aren't *now*21:08
pcjc2so DJ - what you did was try to login with the old ~djdelorie account (the SF import one), and it leaked out / gave you the wrong address21:08
lifelessoh, click - I see21:08
djgppI tried to log in to the *new* ~djdelorie (from the sf import), but yes.21:08
pcjc2and presumably, it is a bug for that to leak _any_ email address21:08
lifelessso, I think I know where the friction is21:08
djgppdj-delorie was my existing LP account (auto-generated from "DJ Delorie" I suppose)21:08
lifelesspassword recovery is a separate system, separate db - its the openid database21:09
pcjc2I'm still curious where it got the incorrect email from21:09
lifelessaccount merge is purely launchpad21:09
lifelessthe isd folk may know21:09
pcjc2should we (or someone) file a bug about the email address being given out for that account?21:09
djgpps/can/can't/ get my icon to change21:09
lifeless(Information Services Development)21:10
lifelesspcjc2: please file three bugs ...21:10
lifeless1) that the email addresses via the two routes were inconsistent21:10
lifeless2) that the password recovery handed out the email willy-nilly21:10
lifeless3) that the merge form handed out the email21:10
lifelessthere are some tensions between diagnosing faults and preventing disclosure to spammers21:11
lifelessbut we should at least take a look at it21:11
lifelessgde: you were having trouble too ?21:12
pcjc2ok. I bet it confuses them because DJ renamed his existing LP account dj-delorie to djdelorie (the merge one) after the merge ;)21:12
djgppand deleted the SF email from it, too :-)21:12
lifelessthat will be tricky to diagnose21:13
pcjc2sounds like something we should recreate on staging21:13
lifelesspossibly21:13
lifelesspossibly not ;)21:13
pcjc2(but the OpenID bit is production only, right)21:13
lifelessits complicated ;)21:13
lifelessI have to finish packing, flying to dallas this afternoon21:14
lifelessyou're all sorted, right ?21:14
djgppmy account seems OK now, although I should log out and back in again...21:14
pcjc2gde?21:15
djgppyup, I can log out/in21:15
djgppstill doesn't have my icon...21:15
lifelessbranding?21:16
djgpp"change details" mugshot21:16
lifelessit hasn't saved it? or its not showing it on some page you're looking at ?21:17
djgppif I go there, it has my photo, but the homepage (/~djdelorie) still has the generic blue-shirt icon.21:17
djgppah!  That's a branding logo.  GRRR!  That was NOT obvious.21:17
pcjc2gde's import was this account https://launchpad.net/~gareth-uk21:17
pcjc2I don't know what his actual LP account is21:17
pcjc2API couldn't find the email address I have for him21:18
lifelessif its hidden api cannot see it21:18
=== almaisan-away is now known as al-maisan
lifelessdjgpp: yeah, I would like us to auto-resize by default and allow overrides21:19
lifelessdjgpp: but noone has contributed a patch as yet :)21:19
pcjc2lifeless: gde's issue was that he's forgotten his LP login credentials21:21
pcjc2but we can't figure out what his proper LP account is called21:22
lifelessask a question on answers.launchpad.net/launchpad21:22
djgppI mean it *says* "that will be displayed on your home page in Launchpad" but it doesn't, and doesn't say that the icon that *is* displayed is set via branding, not details.21:22
lifelesswill need losa assistance21:22
* djgpp must get back to other projects...21:24
pcjc2I've pointer gde at https://login.launchpad.net/+forgot_password21:26
pcjc2So apparently the merge process is confusing for non-logged in, non-regular Launchpad users.21:26
pcjc2If you click the "I am <user>?" link when logged out, you get forwarded to the login page, where the "forgot password" option is pretty tempting21:29
pcjc2OOPS: (Error ID: 1834carambolalaunchpad18)21:29
pcjc2That is me playing about, Probably LP shouldn't "Oops!"21:30
gdelifeless: that link doesn't work for me - no auth email arrives21:31
pcjc2@gde: Check spam folder / whitelist?21:32
pcjc2I tried it for my account and the email came from Launchpad Login Service <noreply@launchpad.net>21:32
pcjc2But to avoid information leaks, it is possible that LP doesn't tell you if you enter an email address it doesn't know of an account for21:33
pcjc2it may just silently pretend to have emailed you, and then get on with its business21:33
pcjc2(to stop people probing for accounts)21:33
pcjc2(lifeless can probably confirm / deny)21:33
lifelesspcjc2: thats another bug to file21:36
pcjc2(which?)21:36
pcjc2the OOPS?21:36
gdepcjc2: nothinhg in spam, and it's hosted gmail so there's no explicit whitelisting afaik21:36
lifeless10:29 < pcjc2> If you click the "I am <user>?" link when logged out, you get forwarded to the login page, where the "forgot password" option is pretty tempting21:36
lifeless10:29 < pcjc2> OOPS: (Error ID: 1834carambolalaunchpad18)21:36
pcjc2ah..21:36
lifelessI can't debug now, still packing21:36
pcjc2I've no idea what the OOPS was caused by, but I can try to reproduce21:37
lifelessjust file the bug21:37
lifelesswe get a backtrace in the oops21:37
pcjc2Filing21:37
lifelessand request variables etc; its usually enough to figure out the defect21:37
pcjc2its not related to https://bugs.launchpad.net/launchpad/+bug/644824 is it?21:38
_mup_Bug #644824: User created a second Launchpad account; now gets mixed success/denied to various services <canonical-losa-lp> <defect> <lp-foundations> <Canonical SSO provider:Confirmed> <Launchpad itself:Fix Released by stub> < https://launchpad.net/bugs/644824 >21:38
lifelessrelated yes, dupe no21:38
pcjc2Will point you at the bugs I file shortly21:38
lifelessno need :)21:39
lifelessI have ~ 0 time today21:39
lifeless(sorry)21:39
pcjc2NP, thanks for helping us!21:42
* pcjc2 goes back to bug filing and leaning LP API21:42
gdelifeless: I think I'm good now- I needed to use an old email address21:43
gdelifeless: thanks for the help21:43
=== al-maisan is now known as almaisan-away
pcjc2any way to search for all bugs in a project with a remote bug watch?22:05
pcjc2(Short of me re-importing our bug data on a local instance and running SQL?)22:06
pcjc2The old bug watches auto-added based upon comments are no good because the SF trackers are shut down22:06
lifelessso you want third party bug watches? not sf ?22:09
lifelessmay need a tweak to bugtask.py & the search interface22:09
lifelessbut we do have a field in the backend thats (IIRC) indexed)22:09
pcjc2I just wanted to seek out bugs which had external watches (incorrectly) added, so I could delete the bugwatches22:12
pcjc2I've already removed the couple I spotted by hand22:13
pcjc2‏‫‏, #7004822:49
_mup_Bug #70048: Python-crash while using Deluge-Torrent-Client <deluge-torrent (Ubuntu):Invalid> < https://launchpad.net/bugs/70048 >22:49
pcjc2Lifeless, 5x Bugs filed against LP, Bug#700483, Bug#700490, Bug#700491, Bug#700493, Bug#70049622:50
_mup_Bug #700483: Email address leaked by account merge request <Launchpad itself:New> < https://launchpad.net/bugs/700483 >22:50
_mup_Bug #700490: Incorrect email address presented when merging accounts <Launchpad itself:New> < https://launchpad.net/bugs/700490 >22:50
pcjc2comeon mup, and the rest?22:50
pcjc2Bug#700491, Bug#70049322:50
pcjc2Bug#70049622:50
lifelesspcjc2: you may wish to file a request for the search you couldn't do23:09
pcjc2gah... don't want to make work for you guys23:18
pcjc2more appropriate would be a way to disable auto-adding them for imported bugs (no point linking to the tracker you're just about to replace)23:18
pcjc2but I have run out of energy for tonight23:19
pcjc2https://bugs.launchpad.net/launchpad/+bug/70050723:24
_mup_Bug #700507: Feature request: Search for bugs with an external bugwatch <Launchpad itself:New> < https://launchpad.net/bugs/700507 >23:24
lifelesspcjc2: polish isn't work ;)23:43
lifelesspcjc2: its just polish23:43

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!