[00:16] wgrant: thanks again [00:16] /off [00:19] teward: np [00:51] I found this page: https://help.launchpad.net/YourAccount/OpenID but it doesn't answer my question. Is there a "generic" URL to which I can direct my users for logging in to my app via OpenID? For exmample, I can provide a link to send users to https://www.google.com/accounts/o8/id All I'm finding so far for launchpad.net indicates you have to include the user's launchpad.net user name. Ideas? [00:54] pedahzur: https://login.ubuntu.com/ [00:54] This is partially guesswork, as it's been quite a while since I read about openid, but give https://launchpad.net/people/+me/+xrds a try? [00:58] wgrant: That does work, but login.ubuntu.com != launchpad Logging via launchpad gives me an identity of https://login.launchpad.net/+id/BnLLNMR while logging in with login.ubuntu.com gives me https://login.ubuntu.com/+id/BnLLNMR So, same ID, but not the same URL. [00:59] maxb: https://launchpad.net/people/+me/+xrds gives me "provider not supported" [01:00] maxb: This works though https://login.launchpad.net/ [01:00] pedahzur: login.launchpad.net is on the way to deprecation, but it works. [01:00] wgrant and maxb: That got me on the right path. Thanks! [01:01] It is not recommended for new consumers. [01:04] wgrant: Thanks. [01:05] wgrant: I thought the OpenStack project required a launchpad ID to login. Do they allow login.ubuntu.com (Can't check right now, as their https://www.openstack.org/ is returning a 525 error.) [01:06] pedahzur: login.ubuntu.com and login.launchpad.net are aliases. They share the same account database, but login.launchpad.net is deprecated. OpenStack tends to use login.launchpad.net, so it may make sense to use the same domain if your consumer is OpenStack-specific. [01:09] wgrant: Understood. But as I noted above, logging in via one vs. the other produces different entries in the database as to what the user's "identity" is. So, if they initially log in via one, and then log in via the other, without properly linking the accounts, then they will create two different accounts in my application. [01:10] pedahzur: Right, but is that a problem if you only allow one of them? [01:11] Anyway, it doesn't matter too much. If you're OpenStack-specific, and everything OpenStacky uses login.launchpad.net, I'd probably use login.launchpad.net. [01:11] No. The application right now (Gerrit in this case) doesn't allow one to restrict which OpenID providers are used. So, it will just become a support case if they log in via one, and then the other. [05:07] Hello, I tried doing sudo add-apt-repository ppa:pipelight/stable after adding the launchpad url to my sources and I still get a 404 on my debian.. [05:08] This is what I have in my sources.list file: deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu maverick main [05:10] weka: does that mean you're still using maverick (10.10)? we do not provide any packages for such old distros, lifetime expired three years ago [05:10] weka: take a look at /etc/os-release if you're unsure which version it is [05:13] PRETTY_NAME="Debian GNU/Linux 7 (wheezy)" [05:13] NAME="Debian GNU/Linux" [05:13] VERSION_ID="7" [05:13] VERSION="7 (wheezy)" [05:13] ID=debian [05:13] ANSI_COLOR="1;31" [05:13] ah - when you are using debian, why do you use the ubuntu instructions then? ^^ [05:14] I'm learning :( I thought this was Debian.. [05:14] I just want to watch netflix on this computer :( [05:14] Oh no I realize mmy mistake. The URL of the update is for Ubuntu [05:15] yep, the instructions you used were for ubuntu, there are separate repositories for debian - nevertheless, if you're only interested in watching netflix, you could also try out the linux native solution with google chrome + html5 drm [05:16] I'll try that... I have Google Chrome and Google Chrome Chromium installed [05:16] But the option to view with HTML5 was not present for me in my netflix option [12:24] excuse me, I've got this error build on Launchpad https://launchpadlibrarian.net/195703055/buildlog.txt.gz [12:27] what should I do then? [12:51] okay, I've retried the build, and it was successful [16:28] Hullo. Anyone here to help me with a PPA issue? [16:54] It's best to ask your actual question, so people can judge whether they are able to help with it [16:57] maxb: ah, sorry, I am not really good with PPA stuff [16:57] so the issue is this [16:58] on the numix ppa [16:58] link - https://launchpad.net/~numix/+archive/ubuntu/ppa [16:58] the numix-icon-theme-circle builds are failing [16:58] because bad importing from GIT [16:59] launchpad says that the GIT branch has submodules [16:59] and it doesn't [16:59] so, that's my actual question [17:00] if anyone can help - that would be fantastic [17:22] me4oslav: hmmm..... is it possible it had submodules at some point in the past? [17:29] maxb: I don't think so [17:29] we haven't use submodules [17:34] Hmm, that's odd [17:35] I cannot see the failures you refer to [17:35] Possibly because the builds are failing before they ever get to the PPA [17:35] Post a link that actually shows a failure? [17:36] Oh, numix-icon-theme-circle "Built by deleted recipe" - that's why I can't find it [17:45] maxb: I will cal one of colleagues [17:45] that knows more about this [17:47] Well, the answer is likely to end up being "the Git history has submodules, and Bazaar sadly never got support for importing them" [17:47] PaoloRotolo: hi [17:47] Hi maxb [17:47] ok, we can talk here too :D [17:48] I'm not aware of any way to work around this, unfortunately (or at least, not without sacrificing the convenience of LP doing all the import work for you) [17:50] maxb: I think we never created submodules in our Git repo [17:52] Post a link to the import branch on Launchpad? [17:58] maxb: https://code.launchpad.net/~numix/numix-icon-theme-circle/numix-icon-theme-circle [17:58] thanks [18:04] Huh. odd. I agree it doesn't seem to contain submodules. At which point, I can only think it's a bug in bzr-git or LP's integration [18:05] maxb: is this a good o bad news? :) I mean, can you fix it? [18:06] I have an appointment to go play mahjong now. It does look like it won't be a quick fix [18:08] maxb: no problem, I can upload it manually on bzr for now. I just hope that it will be fixed in future