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