/srv/irclogs.ubuntu.com/2016/08/04/#launchpad.txt

=== JanC_ is now known as JanC
xnoxis staging SSO different from normal SSO?10:08
xnoxas in should my production SSO credentials work on https://login-lp.staging.ubuntu.com/<token>/+login ?10:08
xnoxor do i need a second account?10:08
Odd_Blokexnox: I believe you need a second account.  There is a Launchpad env which uses production SSO but non-production LP data.11:15
Odd_Blokexnox: (But I can't remember the details, unfortunately.)11:15
xnoxdogfood i guess11:23
xnoxnah, i don't want dogfood =)11:23
Odd_Blokexnox: qastaging, perhaps.11:24
rbasakhttps://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1427406/comments/33 looks like spam.11:50
ubot5Launchpad bug 1427406 in mysql-5.6 (Ubuntu Vivid) "data corruption on arm64 and ppc64el" [Critical,Fix committed]11:50
cousin_luigiGreetings.12:07
cousin_luigiCan launchpad build for debian?12:08
=== cousin_luigi is now known as aunt_luisa
=== aunt_luisa is now known as cousin_luigi
dobeycousin_luigi: PPAs only support building on Ubuntu currently12:54
cousin_luigithanks12:54
cousin_luigibbl12:54
dobeyxnox: yes, staging and production are different databases, you need a separate account (and 2fa) for staging12:54
=== cory_fu-vac is now known as cory_fu
=== signed8bit is now known as signed8bit_Zzz
=== signed8bit_Zzz is now known as signed8bit
beisnero/ hi all. we have some cloud archive pocket automation that started failing this week.  ex. our script reaches out to open:18:39
beisnerhttps://launchpad.net/~ubuntu-cloud-archive-private/+archive/ubuntu/mitaka-proposed/+files/python-keystoneauth1_2.4.1-1ubuntu0.16.04.1~cloud0_source.changes18:39
beisnerbut gets 404 not found.  i see the same with wget.  however, if i hit a browser with that, i end up at:18:39
beisnerhttps://launchpadlibrarian.net/276333938/python-keystoneauth1_2.4.1-1ubuntu0.16.04.1~cloud0_source.changes18:39
beisneris there a known issue or behavior change?18:39
olzhasHow 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.gz20:14
olzhasexport CC=gcc-4.9; export CXX=g++-4.9 isn't helping in debian/rules20:16
olzhasgcc-4.9 and g++-4.9 are installed from ubuntu-toolchain-r/test20:17
dobeyolzhas: you don't build-depends on g++-4.9?20:22
dobeyolzhas: 4.8 is the default on 14.04. if you need to specifically build against 4.9, then you need to depend on it20:23
olzhasdobey: How?20:24
dobeyolzhas: in the build-depends field in debian/control20:24
olzhasdobey: I do have 'gcc (>= 4.9) g++ (>= 4.9)'20:24
olzhasdobey: and libstdc++ (>= 4.9)20:25
dobeyi 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, personally20:28
=== signed8bit is now known as signed8bit_Zzz
=== signed8bit_Zzz is now known as signed8bit

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!