=== _salem is now known as salem_
=== funkyHat_ is now known as funkyHat
=== salem_ is now known as _salem
pittiGood morning05:51
dholbach@pilot in06:52
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
xnox3 months in, and my irc stopped working, because let's encrypt certificate did not renew *sigh*08:33
cpaelzerHi, sorry to ask, but I never touched this before - I'm trying to fix an issue with the GCC& build as reported by https://lists.ubuntu.com/archives/ubuntu-devel/2016-July/039448.html09:05
cpaelzerwhat is the "right" way to locally reproduce this with e.g. sbuild?09:06
cpaelzerI've seen the test added http://ppa.launchpad.net/ubuntu-toolchain-r/test/ubuntu09:06
cpaelzerso should I do like https://wiki.ubuntu.com/SimpleSbuild#Temporarily_adding_PPAs ?09:06
cpaelzeror is there another preferred method09:06
cpaelzerit is working, so it can't be too wrong :-)09:17
dholbachhey seb128 - can you or anyone in your team take a look at https://code.launchpad.net/~jbicha/indicator-session/lp1600502-fix-icon-install/+merge/299625?09:20
seb128dholbach, hey, I guess I can try having a look, though my cmake foo is weak, might be one rather for charles or ted09:21
seb128I can try to nag them though09:21
dholbachthanks a lot09:21
mwhudsoncpaelzer: you might also be able to use --extra-package pointing at an appropriate gcc-defaults package09:38
=== dholbach_ is now known as dholbach
cpaelzermwhudson: thanks, will try that next time09:42
cpaelzerwould not affect the actual chroot which is nice09:42
infinitycpaelzer: --extra-repository=spec --extra-repository-key=file.asc10:20
infinitycpaelzer: Adds the PPA on the CLI instead of in the chroot, so only affects that build.10:20
infinitycpaelzer: (See sbuild(1))10:20
cpaelzerinfinity: I searched for ppa in there and the web but you never know how it is called ina  given context in advance - of course it is repository not ppa as it is the more generic term10:22
cpaelzerinfinity: thanks a lot!10:22
cpaelzeras always if you would know before, what you know after doing/realizing sometihng it would have been much easier :-)10:23
cpaelzerI think I should try to mention that in https://wiki.ubuntu.com/SimpleSbuild#Temporarily_adding_PPAs to not mislead the next10:23
* cpaelzer is checking if he can edit there ...10:24
infinitycpaelzer: Yeah, the advice to mangle the chroot is certainly not ideal, since one can easily end up with a dirty base chroot and have to start over.10:24
infinitycpaelzer: +1 for replacing that section with --extra-repo* bits.10:24
infinitycpaelzer: With a derp-friendly blurb on how to find the public sig for repo.asc, I guess.10:25
mwhudsoninfinity: does that actually work? i couldn't make --extra-repository-key behave10:29
mwhudsonbut i was probably holding it wrong10:30
mwhudsonalso mk-sbuild is pretty fast, i have a collection with various different ppas enabled10:31
infinitymwhudson: Works for me.10:33
cpaelzerinfinity: mwhudson: I replaced the modding of the chroot with the sbuild options, my gpg key foo was good enough to get them to work - but surely not perfect. If one has a sequence that works without ever touching the local keyreing please feel free to let me know or modify in place https://wiki.ubuntu.com/SimpleSbuild#Temporarily_adding_PPAs11:02
mwhudsoncpaelzer: i have a horrible feeling that involves GNUPGHOME=`mktemp -d` or some such horror11:04
mwhudsonbut i'm not really sure :)11:04
cpaelzermwhudson: no need for Horror on a Monday :-) what I have written works and is surely less damaging than what the wiki page said before11:09
cpaelzerjust wanted to leave the chance open if one knows an even better way11:09
cpaelzerif with "horror" it might not be that much better11:09
dholbach@pilot out11:17
=== udevbot changed the topic of #ubuntu-devel to: Xenial (16.04) Released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of precise-xenial | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
=== fginther` is now known as fginther
=== _salem is now known as salem_
coreycbinfinity, hi, would you be able to review keystone and pythonkeystoneauth1 in the xenial review queue?14:45
LocutusOfBorghi folks, quick question14:59
LocutusOfBorg"what's the file system mounted at /tmp?" <-- buildd/armhf system14:59
LocutusOfBorgif you want the whole picture: https://github.com/borgbackup/borg/issues/131014:59
tewardLocutusOfBorg: /tmp/ should be a tmpfs in RAM, is it a qemu-static armhf schroot or a native armhf build env.?15:00
LocutusOfBorgteward, official buildds15:01
tewardah, then you'll have to wait for the buildd maintainers to answer that more effectively.15:01
LocutusOfBorgthis is the build15:02
LocutusOfBorgkishi04 seems owned by infinity15:03
LocutusOfBorgbut it might be a general issue/configuration I think15:03
LocutusOfBorgthey are also asking the result of getconf PAGE_SIZE15:12
ddellavpitti when you get a second, can you or someone else on the SRU team take a look at https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1592865? It's good to go15:14
ubottuLaunchpad bug 1592865 in keystone (Ubuntu Xenial) "[SRU] mitaka point releases" [Undecided,Incomplete]15:14
ddellavcoreycb ^15:14
bregmahey folks, is there a formal way to file a remove request for a package in Yakkety?15:15
LocutusOfBorgbregma, open a bug and subscribe ubuntu-archive15:16
LocutusOfBorge.g. 159548515:16
LocutusOfBorgLP: #159548515:16
ubottuLaunchpad bug 1595485 in singular (Ubuntu) "packages to remove from yakkety" [Undecided,New] https://launchpad.net/bugs/159548515:16
bregmaLocutusOfBorg, a bug against Ubuntu or a bug against the particular package?15:16
LocutusOfBorgthe second one15:16
bregmak thanks15:16
* bregma likes easy15:17
LocutusOfBorgwell, if the package disappears in Debian, it is semi-automatically removed from ubuntu too15:17
LocutusOfBorgunless there are rdeps that needs fixing15:17
bregmait's a Ubuntu-only package15:17
LocutusOfBorgso, if you don't want to make things difficult to both you and archive team (like I did in the above bug)15:18
LocutusOfBorgreverse-depends -r yakkety src:foo; reverse-depends -r yakkety -b src:foo15:18
LocutusOfBorgand reverse-depends -r yakkety -b libfoo-dev15:18
coreycbddellav, I pinged infinity in here a little while ago about keystone and keystoneauth1 since he has Mondays for the sru team:  https://wiki.ubuntu.com/StableReleaseUpdates#Publishing15:25
cjwatsonLocutusOfBorg: the log of https://launchpad.net/ubuntu/+source/procenv/0.43-2/+build/8361172 should answer your questions15:26
LocutusOfBorgcjwatson, can I assume it didn't change in the last months then?15:28
LocutusOfBorgI don't see any mounts:15:30
LocutusOfBorg  /tmp:15:30
LocutusOfBorgso I presume it is under "/" mount15:30
cjwatsonindeed, and yes, you can so assume15:31
LocutusOfBorgthanks! I'm a little bit confused about a non tmpfs tmp :)15:31
LocutusOfBorgbut I can understand the rationale for that indeed15:32
* LocutusOfBorg leaves15:32
cjwatson/tmp is an FHS-mandated directory regardless of what filesystem it's on, and on buildds I think it makes sense to leave the memory for compilers to use15:32
Odd_Blokeslangasek: infinity: https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/298305 <-- this fixes some major pain points with using Vagrant images (for xenial and later), which we'd like to (a) fix in yakkety, and (b) SRU to xenial16:18
Odd_BlokeIf you could cast your eyes over it, it would be much appreciated.16:19
semiosisOdd_Bloke: want to talk about the bash -u option now?  or are you OK with it being removed?16:28
Odd_Blokesemiosis: I'm happy with it being removed; we need to do some clean-up there (to, for example, switch away from bash), so it's a more pervasive change than makes sense for this.16:29
semiosisOdd_Bloke: sounds good.  curious, what would you use instead of bash?16:30
slangasekPOSIX sh16:31
semiosisthat makes sense.16:32
rharperslangasek: smoser and I are starting a curtin SRU,  do you prefer a single SRU bug, or can we just use the individual bugs (we've four of them) in the changelog/debdiff ?20:51
slangasekrharper: if there's been discussion about SRU exception process for curtin, it's not captured on https://wiki.ubuntu.com/StableReleaseUpdates; individual bugs are probably best here22:09
semiosisslangasek: working on your feedback in https://code.launchpad.net/~semiosis/livecd-rootfs/fix-for-1565985/+merge/29830522:13
slangaseksemiosis: great :)22:13
semiosisslangasek: can you explain a bit more what you mean in your comment re manage_etc_hosts: localhost... i dont understand22:14
semiosis"The bug reference for this makes sense in terms of why this is wanted; but why is this a vagrant-specific change? I'm skeptical of this being a delta vs. 999-cpc-fixes.chroot."22:14
slangaseksemiosis: so, you're adding this into a cloud-init userdata that's specific to the vagrant image. the 999-cpc-fixes.chroot hook also creates cloud-image userdata for the generic cloud image22:14
slangaseksemiosis: is there some reason that this change should be made *only* for vagrant, which is the effect of the current change?22:15
=== sakrecoer_ is now known as sakrecoer
semiosisslangasek: well I'm not an expert on that subject.  not sure if it's generally useful to other cloud images (although I can imagine how it would be!)22:17
slangaseksemiosis: hostname setting and resolution seem applicable for other environments than vagrant, AFAICS22:18
slangasekmaybe Odd_Bloke has a comment here22:18
semiosisslangasek: however, since the vagrant builder combines the cloud-init stuff into an ISO which gets bundled in the vagrant box, we do need to generate cloud-init config in the vagrant builder.  unless you'd suggest going back and modifying the vagrant box in the 999 step22:19
slangaseksemiosis: I'm saying that if this is a bug affecting multiple images, we shouldn't fix it in just one of the images and close the bug22:19
slangasekbut should fix it in both places22:19
semiosisslangasek: that makes sense.  but i dont see how that matters for my merge request... even if that change were needed elsewhere, it is still needed in the vagrant builder, no?22:21
slangaseksemiosis: your merge request has a changelog entry which closes that bug ;)22:21
slangasekand regardless, before merging I would want to be sure we either have a reason not to apply it to the other userdata, or apply it equally in both places22:22
slangasekso that does probably need Odd_Bloke's expertise22:22
slangasekor maybe rcj is more likely to be around22:22
semiosissounds good.  i can ping Odd_Bloke tomorrow morning if he doesn't get to it first22:22
semiosisslangasek: i have a xenial ec2 instance and i get the same unable to resolve host there, which supports your idea22:24
semiosisi had not noticed that on the ec2 instance before so i just checked22:24
=== alexisb is now known as alexisb-afk
=== DzAirmaX_ is now known as DzAirmaX

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