infinityLocutusOfBorg: It's not "missing", it's removed intentionally.02:33
infinity* The nonstandard header <xlocale.h> has been removed.  Most programs should02:33
infinity  use <locale.h> instead.  If you have a specific need for the definition of02:33
infinity  locale_t with no other declarations, please contact02:33
infinity  libc-alpha@sourceware.org and explain.02:33
infinityLocutusOfBorg: ^02:33
=== micahg_ is now known as micahg
=== giraffe is now known as Guest34710
cpaelzerLaney: (or anyone else on autopkgtest) I've seen that since the 5th these tests are failing http://autopkgtest.ubuntu.com/packages/vagrant-mutate/artful/ppc64el05:53
cpaelzerseems reproducible and the error always is "Error: Failed to connect to atlas.hashicorp.com port 443: Connection timed out"05:53
cpaelzerother arches as well as local tries seem to work05:53
cpaelzerso I wonder if there might be any Firewall or Proxy setup that might cause this?05:54
LocutusOfBorgack infinity06:01
Laneycpaelzer: it's probably https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/171512808:03
ubottuLaunchpad bug 1715128 in cloud-init (Ubuntu) "Crashes in convert_ec2_metadata_network_config on ScalingStack bos01 (ppc64el)" [Undecided,New]08:04
cpaelzerI opened bug 1715555 for what I saw, but the bug you listed makes sense to all I've found08:20
ubottubug 1715555 in Auto Package Testing "ppc64el vagrant-mutate tests fail to access atlas.hashicorp.com" [Undecided,New] https://launchpad.net/bugs/171555508:20
cpaelzermy issue boils down to proxies missing and the bug you referred is reporting just that as an issue08:20
cpaelzerI'm dupping mine - thanks for the info08:21
cpaelzerLaney: do we fake the EC2 datasource in our scalingstack?08:27
cpaelzerto provide the config data to cloud-init08:27
LaneyI don't know how that stuff works08:28
Laneyit's more or less the normal cloud images if that helps08:28
cpaelzerthat is only the consumer08:28
cpaelzerhow the config is passed is the interesting part in this case08:28
cpaelzerLaney: it would be great if you could add the full boot log containing all cloud-init output to the bug08:28
wgrantbos01 is a pretty standard kilo AFAIK08:29
wgrantWe didn't do anything specially EC2ish while deploying it08:29
cpaelzerso it should be detected as openstack datasources then, which it is not08:29
wgrantHow does cloud-init actually detect the datasource, though?08:29
cpaelzerLaney: if you could attach the output from the failing ppc as well as the working lcy01 or lgw01 that would be great08:30
wgrantIf it uses DMI or something that might just not work on ppc64el with our relatively old setup08:30
cpaelzerwgrant: Laney: https://git.launchpad.net/cloud-init/tree/tools/ds-identify08:31
wgrantI have a religious objection to 1300 line shell scripts.08:31
wgrantAh yes, lots of DMI bits in there.08:32
Laney https://bugs.launchpad.net/cloud-init/+bug/1715241?08:34
ubottuLaunchpad bug 1715241 in cloud-init "ds-identify openstack returns not found on non-intel" [Medium,Confirmed]08:34
cpaelzerLaney: 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 detection08:34
cpaelzerIt shoudl still find an openstack config drive no matter of DMI in your case08:34
wgrantI have never seen an OpenStack that used configdrive.08:35
wgrantOh you can do it when creating the VM, I see.08:35
cpaelzerwhich brings me back to my former question what you currently use to pass cloud init config info?08:35
wgrantStill never seen it used :)08:35
wgrantIt uses the normal Nova metadata HTTP service08:36
cpaelzerI'll copy this chat to the bug, together with the logs Laney can provide this should make some progress when US wakes up later08:36
ZweiHello, I'm trying to add the test toolchain ppa, but I get this error: http://codepad.org/YoDRkJ6908:42
ZweiI'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-error08:42
ZweiI 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:42
cpaelzerZwei: was this just happening the last minutes?08:44
cpaelzerZwei: if so could you retry08:45
cpaelzerI happened to be unable to access the ppa's pages but just now things seem to have resolved08:45
cpaelzeralso the add is working in a zesty for me atm08:45
cpaelzerZwei: related issues seem to be around a broken /etc/lsb-release, please share that as well if it still is an issue08:48
Zweicpaelzer: just restarted and I got a popup window/error about "add-apt-repository has stopped unexpectedly"08:50
Zweihmm, I guess I should fix that first somehow.08:50
Zweithis is my /etc/lsb-release: http://codepad.org/7Lg1CbfB08:51
ZweiI still get exactly the same error when I run "sudo add-apt-repository ppa:ubuntu-toolchain-r/test"08:52
=== mbiebl_ is now known as mbiebl
wgrantZwei: Hm, how long since that machine has been updated? Its lsb-release looks quite out of date.08:57
ZweiHmm... 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
ZweiBut I thought I was using Zesty, as per the lsb-release, not yakkety.08:58
Zweiwgrant: Updated in January this year...08:59
ZweiWell, that's when I installed 17.04, since I needed gcc 6.x08:59
wgrantYou apparently haven't upgraded since well before zesty went stable in April09:00
wgrantTry upgrading to stable zesty and see if it works09:00
wgrant(well, reinstall the machine because it's probably compromised, then upgrade :))09:00
ZweiOkay, will google that, will report back.09:00
ZweiOh, I need to reinstall the OS?09:00
Zweiwanted to avoid that.09:00
wgrantZwei: 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:01
wgrantZwei: Anyway, if you have further questions then #ubuntu can probably help you.09:02
wgrantThis channel is for Ubuntu development, not general support.09:02
Zweiwgrant: thank you for your help!09:03
=== JanC is now known as Guest49554
=== JanC_ is now known as JanC
acheronukLocutusOfBorg: breakage here as well :/ https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/171559910:09
ubottuLaunchpad bug 1715599 in glibc (Ubuntu) "2.26-0ubuntu1 breaks compliation of several KDE sources" [Undecided,New]10:09
Unit193LocutusOfBorg: I don't suppose you're still here?10:11
Unit193LocutusOfBorg: 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
xnoxdoko, 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
xnoxand i am confused =)10:24
xnoxthat's from autopkgtest. If NM tries to require that symbol, it should have had a tigher glibc dep generated by the build, no?10:24
=== alan_g is now known as alan_g|lunch
=== alan_g|lunch is now known as alan_g
=== rumble is now known as grumble
LocutusOfBorgUnit193, will have a look tonight13:20
cpaelzercyphermox: sorry to reply in-meeting - I didn't realize15:28
cpaelzercyphermox: just replied to highlights15:28
cpaelzerbug 171135815:29
ubottubug 1711358 in ubiquity (Ubuntu) "20170817 - ISO hangs on boot on qemu with splash screen enabled and qxl graphics driver" [High,Confirmed] https://launchpad.net/bugs/171135815:29
cyphermoxcpaelzer: no worries15:29
cpaelzerI came over a report on virt-inst which I handle15:29
cyphermoxyeah, I noticed such issues, but been busy on something else15:29
cpaelzerbut eventually found that, you might find some extra info in the dup bug on there15:29
cyphermoxI'll spin a vm as soon as our meeting is done15:29
cpaelzerI just failed to know how to debug plymouth at all, as it wasn't helping me with any messages15:30
cpaelzerI documented a set of workarounds in the bug (different video driver, nosplash, ...)15:30
cpaelzerbut then gave up and hoped for people experienced in that area15:30
cpaelzerwhich I must admit I don't have a "name for plymouth" in my mind15:30
dokoLocutusOfBorg: https://launchpad.net/ubuntu/+source/h5py/2.7.1-1ubuntu1  please build with -v<version>16:05
=== JanC_ is now known as JanC
acheronukwith autopkgtest-build-lxc, when running setup-testbed, neworking fails for the container :/17:29
acheronukRunning setup script /usr/share/autopkgtest/setup-commands/setup-testbed...17:30
acheronukgrep: //etc/network/interfaces: No such file or directory17:30
acheronukErr:1 http://archive.ubuntu.com/ubuntu artful InRelease17:30
acheronuk  Temporary failure resolving ‘archive.ubuntu.com’17:30
jackpot51Are didrocks or jbicha available to talk about GDM theming?18:23
tsimonq2o/ mwhudson21:09
tsimonq2mwhudson: How are you doing?21:09
tsimonq2acheronuk: What does /etc/resolv.conf look like? I'm thinking systemd-resolved :P21:09
acheronuktsimonq2: can't check now. I nuked it all. will try tomorrow21:11
tsimonq2acheronuk: ack21:11
=== Eleventh_Doctor is now known as Pharaoh_Atem
LocutusOfBorgUnit193, .22:12
Unit193Very interested in having it for myself too. :)22:20
sarnoldUnit193: .22:24
sarnolddunno what you're going to do with these punctuation marks but i'm feeling generous22:24
tsimonq2sarnold: Debian people (or so I hear) use "." as an alias for "taken care of" or "done"22:25
tsimonq2sarnold: I was tricked by it too :P22:25
Unit193ᗣ ᗣ ᗣ   ᗧ * * * * * *22:25
sarnoldUnit193: @>--`--,--`---22:25
Unit193tsimonq2: Not that I've ever seen, it's just a Locutus thing. :)22:26
tsimonq2Unit193: Oh, mapreri told me at one point it's a Debian Release Team thing :P22:26
Unit193Mmmm, could be.  I don't tend to interact with that group.22:27
tsimonq2Unit193: Also, nice Pacman emojis :D22:27
tsimonq2Pac Man? Pacman? PacMan? *shrug*22:28
wxlyou mean canadian aboriginal syllabics22:28
tsimonq2wxl: lol?22:28
Unit193sarnold: I have a rose, but it's waaaay too much for here. :322:30
cjwatsoninfinity: 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 typed22:51
sarnoldwhat's your heart rate now?22:52

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