[06:11] Hello All [06:11] I am developer. [06:11] Previously our application was using Launchpad OpenId login service [06:12] But that is too old Now we are yet to convert it to OpenID connect [06:12] I am confused Launchpad still provide OpenID Connect API service for Login? [06:38] Any suggestion please. [06:38] Anyone alive? [06:55] OpenID and OpenID Connect are very different protocols, despite the similar names [06:55] There is no reason that a site providing one will necessarily provide the other [06:56] I have not heard of OpenID Connect and Launchpad mentioned together before [06:56] So I'm guessing you should simply continue using OpenID [06:57] Yes. Thank you for your answer. I know that both technologies are very different. [06:57] Most popular providers (Which were supporting OpenID) are now providing loging API using Oauth 2.0 combined with OpenID Connect. [06:58] So I was hopping that Launch pad will do the same. [06:58] But as you have said I also Google and found no related suggestion regarding Launchpad OpenId connect. [06:59] Thank you for answering. [06:59] Bye === hyperair is now known as m4 === m4 is now known as hyperair [22:46] trying to build a package, it works in a clean environment (virtualbox), but not in launchpad: https://launchpadlibrarian.net/203871645/buildlog_ubuntu-trusty-i386.m64py_0.2.2%2Br161~2~ubuntu14.04.1_BUILDING.txt.gz [22:47] . [22:47] UnicodeEncodeError: 'ascii' codec can't encode character '\xa9' in position 1037: ordinal not in range(128) [22:47] E: pybuild pybuild:256: build: plugin distutils failed with: exit code=1: /usr/bin/python3 setup.py build [22:48] any idea? [22:49] i think you have unicode in there you have to strip out somewhere [22:50] but I'm not 100% certain [22:50] you mean, the problem is in the source? Not in the packaging? [22:51] not 100% certain, can't attest to either of those myself [23:04] data_files = [ [23:04] ("share/pixmaps", ["xdg/m64py.png"]), [23:04] ("share/applications", ["xdg/m64py.desktop"]), [23:04] for me, it's right [23:07] does m64py.desktop contain characters outside ascii limits? [23:09] let me see [23:10] is '\xa9' an @ ? [23:11] not @ but © [23:11] at least in iso-8859-1 a9 is an © [23:12] there is a © in src/m64py/ui/license.ui [23:12] aha; you can try removing it and see if your build progresses further [23:12] but in the log, this file does not appears [23:13] or you can try figuring out if there's something else you can do to the build environment to let it go further, like it did with your vm.. [23:14] well, I installed only these packages: debhelper dh-python python3 python3-pyqt5 pyqt5-dev-tools [23:15] my wild-ass-guess is that you've got your local build running in en_US.UTF-8 and the build is running in C -- but I don't know what to suggest to fix that. [23:16] .. or local build in pt_BR.UTF-8, or whatever :) hehe [23:17] heh [23:32] ok, it was the ©, but now it's '\u201c' [23:40] ergh, “ and ” [23:47] unicode and bytestryings are a pain aren't they :P [23:48] (pytrhon headaches for IRC bot people too xD) [23:55] what annoys me is that things that worked alright in 2.x broke in 3.x. :( [23:56] yay, worked