=== JanC_ is now known as JanC
[10:08] <xnox> is staging SSO different from normal SSO?
[10:08] <xnox> as in should my production SSO credentials work on https://login-lp.staging.ubuntu.com/<token>/+login ?
[10:08] <xnox> or do i need a second account?
[11:15] <Odd_Bloke> xnox: I believe you need a second account.  There is a Launchpad env which uses production SSO but non-production LP data.
[11:15] <Odd_Bloke> xnox: (But I can't remember the details, unfortunately.)
[11:23] <xnox> dogfood i guess
[11:23] <xnox> nah, i don't want dogfood =)
[11:24] <Odd_Bloke> xnox: qastaging, perhaps.
[11:50] <rbasak> https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/comments/33 looks like spam.
[11:50] <ubot5> Launchpad bug 1427406 in mysql-5.6 (Ubuntu Vivid) "data corruption on arm64 and ppc64el" [Critical,Fix committed]
[12:07] <cousin_luigi> Greetings.
[12:08] <cousin_luigi> Can launchpad build for debian?
=== cousin_luigi is now known as aunt_luisa
=== aunt_luisa is now known as cousin_luigi
[12:54] <dobey> cousin_luigi: PPAs only support building on Ubuntu currently
[12:54] <cousin_luigi> thanks
[12:54] <cousin_luigi> bbl
[12:54] <dobey> xnox: yes, staging and production are different databases, you need a separate account (and 2fa) for staging
=== cory_fu-vac is now known as cory_fu
=== signed8bit is now known as signed8bit_Zzz
=== signed8bit_Zzz is now known as signed8bit
[18:39] <beisner> o/ hi all. we have some cloud archive pocket automation that started failing this week.  ex. our script reaches out to open:
[18:39] <beisner> https://launchpad.net/~ubuntu-cloud-archive-private/+archive/ubuntu/mitaka-proposed/+files/python-keystoneauth1_2.4.1-1ubuntu0.16.04.1~cloud0_source.changes
[18:39] <beisner> but gets 404 not found.  i see the same with wget.  however, if i hit a browser with that, i end up at:
[18:39] <beisner> https://launchpadlibrarian.net/276333938/python-keystoneauth1_2.4.1-1ubuntu0.16.04.1~cloud0_source.changes
[18:39] <beisner> is there a known issue or behavior change?
[20:14] <olzhas> How to make launchpad build machine use gcc-4.9 on ubuntu 14.04? https://launchpadlibrarian.net/277101921/buildlog_ubuntu-trusty-amd64.scram_0.11.4-1ubuntu4_BUILDING.txt.gz
[20:16] <olzhas> export CC=gcc-4.9; export CXX=g++-4.9 isn't helping in debian/rules
[20:17] <olzhas> gcc-4.9 and g++-4.9 are installed from ubuntu-toolchain-r/test
[20:22] <dobey> olzhas: you don't build-depends on g++-4.9?
[20:23] <dobey> olzhas: 4.8 is the default on 14.04. if you need to specifically build against 4.9, then you need to depend on it
[20:24] <olzhas> dobey: How?
[20:24] <dobey> olzhas: in the build-depends field in debian/control
[20:24] <olzhas> dobey: I do have 'gcc (>= 4.9) g++ (>= 4.9)'
[20:25] <olzhas> dobey: and libstdc++ (>= 4.9)
[20:28] <dobey> i don't know the details of the gcc packages in 14.04 beyond 4.8 being the default. maybe #ubuntu or #ubuntu-devel could help discern what the actual deps should be. at least for 14.04 you probably need to depend on g++-4.9/gcc-4.9 packages. if you want same packaging to work for all versions of ubuntu, i don't know what a good way to declare that is, personally
=== signed8bit is now known as signed8bit_Zzz
=== signed8bit_Zzz is now known as signed8bit