=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
[02:11] <[MT]> I can't figure out why this thing won't import. :(   https://code.launchpad.net/~tdc/tdc/debian
[02:13] <[MT]> I can run 'git clone https://alioth.debian.org/anonscm/git/collab-maint/tdc.git' just fine
[02:13] <dobey> [MT]: seems pretty clear. the url is wrong
[02:14] <dobey> and apparently you just deleted it anyway
[02:15] <[MT]> dobey: sorry, I should have waited. I just tried removing the trailing / that I didn't notice was there. Hoping that fixes the issue.
[02:16] <dobey> you can edit the branch url, instead of deleting it and making a new import
[02:17] <[MT]> oh? where do you change it?
[02:18] <dobey> on the branch page, under the short list of last few import attempts, there is a green link that says "Edit or review" or something like that
[02:19] <[MT]> I don't see that.
[02:22] <dobey> "(+) Edit import source or review import"
[02:24] <[MT]> still not seeing it
[02:25] <dobey> weird
[02:33] <[MT]> dobey: I was under the impression only lp admins get that option; also- it failed again
[02:33] <[MT]> could you try to clone that url and tell me if it fails for you?
[02:34] <dobey> i changed it to use git:// and it got a better error
[02:34] <dobey> i think maybe https:// doesn't work for cloning git from alioth perhaps
[02:34] <[MT]> was there a 3rd import that I'm not seeing yet?
[02:35] <dobey> [MT]: maybe only people with certain permissions do then. but i thought the owner of the branch could edit the import url
[02:35] <dobey> ah well
[02:36] <[MT]> dobey: if I try to personally clone it with git://, it fails, if I try with https:// it works (on my laptop)
[02:41] <dobey> with bzr-git?
[02:42] <[MT]> with just git
[02:44] <[MT]> dobey: could you try changing it to just http:// ?
[02:46] <dobey> also failed
[02:52] <[MT]> I don't get it... https://alioth.debian.org/anonscm/git/collab-maint/tdc.git <-- that's the correct repo
[02:54] <dobey> there
[02:55] <dobey> git://anonscm.debian.org/collab-maint/tdc.git
[02:55] <dobey> http urls don't work for the imports
[02:55] <[MT]> ooooh....
[02:55] <[MT]> you're brilliant :D
[02:55] <dobey> anyway, it's imported now
[02:55] <[MT]> Could you do me one last huge favor?... https://code.launchpad.net/~nginx/nginx/debian  <-- that needs to be updated too
[02:59] <[MT]> actually... that's not the issue with that one, but it'd be nice to see them use the same url anyway
[03:01] <dobey> apparently it is
[03:01] <dobey> it's imported now
[03:01] <[MT]> THANKS!!! :D
[03:03] <dobey> np
[03:03] <dobey> later :)
[03:03] <[MT]> ttyl
[04:45] <phillw> hi , any staffers about? I need a rather messed up lp area for lubuntu handing back
[06:33] <phillw> ah well, as not staffers about, I have to sign off and hand it back to others :( Still, I hope you all got easter eggs :P
=== xnox is now known as NoNameYet_xnox
=== chandan_kumar is now known as chandankumar
=== chandankumar is now known as chandan_kumar
=== mpt_ is now known as mpt
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== wedgwood is now known as Guest26994
=== wedgwood1 is now known as wedgwood
[15:54] <arosen1> Is there an issue going on with launchpad right now? I'm unable to access:  https://login.launchpad.net/+openid
[17:09] <dobey> arosen1: no, but what do you mean by "unable to access" exactly?
[17:09] <arosen1> dobey:  i think its an ISP issue.
[17:09] <arosen1> a few other people in #openstack-infra are having the same issue.
[17:09] <arosen1> if i tunnel somewhere else it works fine
[17:09]  * arosen1 so nvm :) 
[17:10] <dobey> ok
[19:17] <thomasberends> I´m trying to work with the Launchpad API, but I get back an XML responsive, instead of JSON. How can I change this?
[19:17] <dobey> how are you trying to work with it?
[19:18] <thomasberends> dobey: I´m testing out requests. Unsigned, but they give back results.
[19:18] <thomasberends> I tried to get a bug report. https://api.launchpad.net/1.0/bugs/1160687 , this gives back XML.
[19:18] <dobey> thomasberends: that doesn't tell me at all what you are doing
[19:19] <dobey> you're doing it in python? why are you expecting json?
[19:19] <thomasberends> dobey: The API documentation talks about JSON, instead of XML.
[19:20] <dobey> are you sending the appropriate Accept: header in your request?
[19:22] <cjwatson> namely, Accept: application/json
[19:22] <thomasberends> dobey: Nevermind. Stupid me.
[19:23] <thomasberends> Damn. I never thought I would forget this in my life. I was testing it in a tester application, and it had settings from the last test. It asked the API for XML....