=== Guest68817 is now known as anthonyjf
[09:00] <Odd_Bloke> wgrant: cjwatson: I'm hitting "fatal: remote error: DNS lookup failed: address 'xmlrpc.lp.internal' not found: [Errno 24] Too many open files." when I try to use Launchpad git on lp:~daniel-thewatkins/cloudware/+git/cloud-images-checker
[09:04] <wgrant> Odd_Bloke: Investigating.
[09:04] <Odd_Bloke> wgrant: Thanks; do you want me to file a bug or anything?
[09:06] <wgrant> Odd_Bloke: Not at this point. Thanks for pointing it out.
[09:06] <Odd_Bloke> wgrant: We first saw it at 0840 UTC (first Jenkins job failure), it was working at 0817 (the previous Jenkins job run).
=== Spads_ is now known as Spads
=== DalekSec_ is now known as DalekSec
[09:34] <wgrant> Odd_Bloke: Should be all happy now.
[09:34] <Odd_Bloke> wgrant: Looks good, thanks!
=== elmo_ is now known as elmo
[17:19] <tintou> Hi all
[17:20] <dobey> hi
[17:20] <tintou> I want to authenticate to launchpad, but I'm stuck because the request_token isn't returning oauth_callback_confirmed=true
[17:20] <tintou> (using OAuth v1)
[17:21] <dobey> you're trying to implement your own oauth client?
[17:22] <tintou> I'm using GSignond
[17:22] <dobey> you're trying to make a plug-in for online-accounts in ubuntu?
[17:23] <tintou> almost, the GLib version :)
[17:23] <dobey> or something else? i'm not quite sure what GSignond is
[17:24] <tintou> Single Sign-on daemon, a similar one than the one use in ubuntu but using GLib instead of Qt
[17:24] <tintou> It's already working fine for Yahoo (also using OAuth v1)
[17:25] <tintou> so I'm using the URLs from this page: https://help.launchpad.net/API/SigningRequests
[17:27] <tintou> but https://launchpad.net/+request-token is returning oauth_token=AuthToken&oauth_token_secret=AuthTokenSecret
[17:29] <tintou> so oauth_callback_confirmed=true is missing to comply to the specifications http://tools.ietf.org/html/rfc5849#section-2.1
[17:32] <tintou> Is this the right place or should I open a bug report on Launchpad itself :P
[17:41] <dobey> i'm not sure
[17:41] <dobey> but it's not that simple
[17:41] <dobey> oh well
[19:03] <benjaoming> I've published a beta release in a PPA and then deleted it. The old stable is now marked "superseded", is there a way to bring it back?
[19:04] <dobey> no, you can't revert to an older version in the archive
[19:07] <benjaoming> dobey: thanks for clarifying! if the stable release was 1.0, and the beta was 2.0~b1, can I then upload a 1.1 and it'll work?
[19:08] <dobey> no
[19:09] <dobey> you can upload 1.0 as 2.0~b1.is.really.1.0
[19:51] <Peng> Isn't that what epochs are for? 1:1.0
[19:51] <Peng> Isn't that what epochs are for? 1:1.1 *
[19:53] <dobey> no, you shouldn't use an epoch
[19:54] <Peng> Why not?
[19:55] <dobey> they are method of absolute last resort. you definitely shouldn't add a new epoch in a PPA, when debian/ubuntu don't have the epoch on the package
[19:55] <Peng> oooh
[19:55] <dobey> adding an epoch breaks upgrading for anyone who used your ppa, even if you got hit by a bus and never upload to it again
=== Peng is now known as SJW
[21:47] <benjaoming> So just to make sure I understand: Deleting the latest version means that the superseded version is no longer available => No installation candidate? I mean, testing it now, and it seems that's how things work..
[21:49] <benjaoming> And thanks for being understanding, I bet a million others have asked the same question :)
[21:50] <dobey> yes, once you've uploaded a newer version you can't go back to the older version
[23:16] <benjaoming> dobey: cool thanks, much obliged -- will have to work harder on getting the beta release finalized then :)