[02:33] <infinity> LocutusOfBorg: It's not "missing", it's removed intentionally.
[02:33] <infinity> * The nonstandard header <xlocale.h> has been removed.  Most programs should
[02:33] <infinity>   use <locale.h> instead.  If you have a specific need for the definition of
[02:33] <infinity>   locale_t with no other declarations, please contact
[02:33] <infinity>   libc-alpha@sourceware.org and explain.
[02:33] <infinity> LocutusOfBorg: ^
[05:53] <cpaelzer> Laney: (or anyone else on autopkgtest) I've seen that since the 5th these tests are failing http://autopkgtest.ubuntu.com/packages/vagrant-mutate/artful/ppc64el
[05:53] <cpaelzer> seems reproducible and the error always is "Error: Failed to connect to atlas.hashicorp.com port 443: Connection timed out"
[05:53] <cpaelzer> other arches as well as local tries seem to work
[05:54] <cpaelzer> so I wonder if there might be any Firewall or Proxy setup that might cause this?
[06:01] <LocutusOfBorg> ack infinity
[08:03] <Laney> cpaelzer: it's probably https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1715128
[08:20] <cpaelzer> I opened bug 1715555 for what I saw, but the bug you listed makes sense to all I've found
[08:20] <cpaelzer> my issue boils down to proxies missing and the bug you referred is reporting just that as an issue
[08:21] <cpaelzer> I'm dupping mine - thanks for the info
[08:27] <cpaelzer> Laney: do we fake the EC2 datasource in our scalingstack?
[08:27] <cpaelzer> to provide the config data to cloud-init
[08:28] <Laney> I don't know how that stuff works
[08:28] <Laney> it's more or less the normal cloud images if that helps
[08:28] <cpaelzer> that is only the consumer
[08:28] <cpaelzer> how the config is passed is the interesting part in this case
[08:28] <cpaelzer> Laney: it would be great if you could add the full boot log containing all cloud-init output to the bug
[08:29] <wgrant> bos01 is a pretty standard kilo AFAIK
[08:29] <wgrant> We didn't do anything specially EC2ish while deploying it
[08:29] <cpaelzer> so it should be detected as openstack datasources then, which it is not
[08:29] <wgrant> How does cloud-init actually detect the datasource, though?
[08:30] <cpaelzer> Laney: if you could attach the output from the failing ppc as well as the working lcy01 or lgw01 that would be great
[08:30] <wgrant> If it uses DMI or something that might just not work on ppc64el with our relatively old setup
[08:31] <cpaelzer> wgrant: Laney: https://git.launchpad.net/cloud-init/tree/tools/ds-identify
[08:31] <wgrant> I have a religious objection to 1300 line shell scripts.
[08:32] <wgrant> Ah yes, lots of DMI bits in there.
[08:34] <Laney>  https://bugs.launchpad.net/cloud-init/+bug/1715241?
[08:34] <cpaelzer> Laney: if you could provide those logs I'm sure smoser and rharper will find that most interesting later on and then has all the data to start finding what is wrongin the detection
[08:34] <wgrant> Aha
[08:34] <cpaelzer> It shoudl still find an openstack config drive no matter of DMI in your case
[08:34] <cpaelzer> (assumption)
[08:35] <wgrant> I have never seen an OpenStack that used configdrive.
[08:35] <wgrant> Oh you can do it when creating the VM, I see.
[08:35] <cpaelzer> which brings me back to my former question what you currently use to pass cloud init config info?
[08:35] <wgrant> Still never seen it used :)
[08:36] <wgrant> It uses the normal Nova metadata HTTP service
[08:36] <cpaelzer> thanks
[08:36] <cpaelzer> I'll copy this chat to the bug, together with the logs Laney can provide this should make some progress when US wakes up later
[08:37] <wgrant> Thanks.
[08:37] <Laney> Ta
[08:42] <Zwei> Hello, I'm trying to add the test toolchain ppa, but I get this error: http://codepad.org/YoDRkJ69
[08:42] <Zwei> I've googled around but not 100% sure how to fix this. Should I do some of the solutions mentioned here? https://askubuntu.com/questions/49040/apt-could-not-find-a-distribution-template-error
[08:42] <Zwei> I want to double check since I want to minimize downtime. Thank you.
[08:42] <Zwei> (I was told to come here and ask doko, so tagging doko...)
[08:44] <cpaelzer> Zwei: was this just happening the last minutes?
[08:45] <cpaelzer> Zwei: if so could you retry
[08:45] <cpaelzer> I happened to be unable to access the ppa's pages but just now things seem to have resolved
[08:45] <cpaelzer> also the add is working in a zesty for me atm
[08:48] <cpaelzer> Zwei: related issues seem to be around a broken /etc/lsb-release, please share that as well if it still is an issue
[08:50] <Zwei> cpaelzer: just restarted and I got a popup window/error about "add-apt-repository has stopped unexpectedly"
[08:50] <Zwei> hmm, I guess I should fix that first somehow.
[08:51] <Zwei> this is my /etc/lsb-release: http://codepad.org/7Lg1CbfB
[08:52] <Zwei> I still get exactly the same error when I run "sudo add-apt-repository ppa:ubuntu-toolchain-r/test"
[08:57] <wgrant> Zwei: Hm, how long since that machine has been updated? Its lsb-release looks quite out of date.
[08:58] <Zwei> Hmm... I'm in Synaptic Package manager, trying to find out which package caused the error, I clicked Reload and for this: "The repository 'http://ppa.launchpad.net/jonathonf/gcc-6.3/ubuntu yakkety Release' does not have a Release file."
[08:58] <Zwei> But I thought I was using Zesty, as per the lsb-release, not yakkety.
[08:59] <Zwei> wgrant: Updated in January this year...
[08:59] <Zwei> Well, that's when I installed 17.04, since I needed gcc 6.x
[09:00] <wgrant> You apparently haven't upgraded since well before zesty went stable in April
[09:00] <wgrant> Try upgrading to stable zesty and see if it works
[09:00] <wgrant> (well, reinstall the machine because it's probably compromised, then upgrade :))
[09:00] <Zwei> Okay, will google that, will report back.
[09:00] <Zwei> Oh, I need to reinstall the OS?
[09:00] <Zwei> damn...
[09:00] <Zwei> wanted to avoid that.
[09:01] <wgrant> Zwei: You don't have to, but you are at least six months behind on security updates, so if it's been anywhere near the Internet I would be reinstalling it myself.
[09:02] <wgrant> Zwei: Anyway, if you have further questions then #ubuntu can probably help you.
[09:02] <wgrant> This channel is for Ubuntu development, not general support.
[09:03] <Zwei> wgrant: thank you for your help!
[09:03] <Zwei> :)
[10:09] <acheronuk> LocutusOfBorg: breakage here as well :/ https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1715599
[10:11] <Unit193> LocutusOfBorg: I don't suppose you're still here?
[10:19] <Unit193> LocutusOfBorg: Just looking for a sponsor for https://launchpad.net/~unit193/+archive/ubuntu/staging/+sourcepub/8240708/+listing-archive-extra (since for some reason it isn't in the packageset still.)  It's a bugfix release, adds translations, and addresses the only remark doko (ftp-master) had on it.
[10:19] <Unit193> http://xfce.10915.n7.nabble.com/ANNOUNCE-xfce4-statusnotifier-plugin-0-2-0-released-tp49735.html
[10:24] <xnox> doko, infinity - i'm having new fun with NM NetworkManager: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by NetworkManager)
[10:24] <xnox> and i am confused =)
[10:24] <xnox> that's from autopkgtest. If NM tries to require that symbol, it should have had a tigher glibc dep generated by the build, no?
[13:20] <LocutusOfBorg> Unit193, will have a look tonight
[15:28] <cpaelzer> cyphermox: sorry to reply in-meeting - I didn't realize
[15:28] <cpaelzer> cyphermox: just replied to highlights
[15:29] <cpaelzer> bug 1711358
[15:29] <cyphermox> cpaelzer: no worries
[15:29] <cpaelzer> I came over a report on virt-inst which I handle
[15:29] <cyphermox> yeah, I noticed such issues, but been busy on something else
[15:29] <cpaelzer> but eventually found that, you might find some extra info in the dup bug on there
[15:29] <cyphermox> I'll spin a vm as soon as our meeting is done
[15:30] <cpaelzer> I just failed to know how to debug plymouth at all, as it wasn't helping me with any messages
[15:30] <cpaelzer> I documented a set of workarounds in the bug (different video driver, nosplash, ...)
[15:30] <cpaelzer> but then gave up and hoped for people experienced in that area
[15:30] <cpaelzer> which I must admit I don't have a "name for plymouth" in my mind
[16:05] <doko> LocutusOfBorg: https://launchpad.net/ubuntu/+source/h5py/2.7.1-1ubuntu1  please build with -v<version>
[17:29] <acheronuk> with autopkgtest-build-lxc, when running setup-testbed, neworking fails for the container :/
[17:30] <acheronuk> Running setup script /usr/share/autopkgtest/setup-commands/setup-testbed...
[17:30] <acheronuk> grep: //etc/network/interfaces: No such file or directory
[17:30] <acheronuk> Err:1 http://archive.ubuntu.com/ubuntu artful InRelease
[17:30] <acheronuk>   Temporary failure resolving ‘archive.ubuntu.com’
[18:23] <jackpot51> Are didrocks or jbicha available to talk about GDM theming?
[21:05] <mwhudson> morning
[21:09] <tsimonq2> o/ mwhudson
[21:09] <tsimonq2> mwhudson: How are you doing?
[21:09] <tsimonq2> acheronuk: What does /etc/resolv.conf look like? I'm thinking systemd-resolved :P
[21:11] <acheronuk> tsimonq2: can't check now. I nuked it all. will try tomorrow
[21:11] <tsimonq2> acheronuk: ack
[22:12] <LocutusOfBorg> Unit193, .
[22:14] <Unit193> Thanks!
[22:18] <LocutusOfBorg> yw!
[22:20] <Unit193> Very interested in having it for myself too. :)
[22:24] <sarnold> Unit193: .
[22:24] <sarnold> dunno what you're going to do with these punctuation marks but i'm feeling generous
[22:25] <tsimonq2> sarnold: Debian people (or so I hear) use "." as an alias for "taken care of" or "done"
[22:25] <tsimonq2> sarnold: I was tricked by it too :P
[22:25] <Unit193> ᗣ ᗣ ᗣ   ᗧ * * * * * *
[22:25] <sarnold> Unit193: @>--`--,--`---
[22:25] <Unit193> \o/
[22:26] <Unit193> tsimonq2: Not that I've ever seen, it's just a Locutus thing. :)
[22:26] <tsimonq2> Unit193: Oh, mapreri told me at one point it's a Debian Release Team thing :P
[22:27] <Unit193> Mmmm, could be.  I don't tend to interact with that group.
[22:27] <tsimonq2> Unit193: Also, nice Pacman emojis :D
[22:28] <tsimonq2> Pac Man? Pacman? PacMan? *shrug*
[22:28] <wxl> you mean canadian aboriginal syllabics
[22:28] <tsimonq2> wxl: lol?
[22:30] <Unit193> sarnold: I have a rose, but it's waaaay too much for here. :3
[22:31] <sarnold> hehe
[22:51] <cjwatson> infinity: yo, you should possibly clear out root's .bash_history from chroot tarballs.  freaked me out slightly just now when I pressed up-arrow right after unpacking it and there were commands I knew I'd never typed
[22:52] <sarnold> *terror*
[22:52] <sarnold> what's your heart rate now?