=== tmpRAOF is now known as RAOF
pittiGood morning04:44
dholbachgood morning06:30
ari-tczewhello dholbach06:32
dholbachhey ari-tczew06:33
dodeluserhello. I got a special question about this tutorial: https://help.ubuntu.com/community/LiveCDCustomization#Advanced_Customizations06:39
dodeluserI do not understand this line: sudo chroot edit mkinitramfs -o /initrd.gz 2.6.15-26-k706:40
dodelusersomeone can help me?06:40
dholbach@pilot in06:44
=== udevbot changed the topic of #ubuntu-devel to: Archive: wily open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: dholbach
flexiondotorgdholbach, As pilot could you take a look at https://code.launchpad.net/~ubuntu-mate-dev/indicators-gtk2/indicator-application-gtk2/+merge/24411608:41
flexiondotorgdholbach, I've discussed this with infinity.08:41
flexiondotorgdholbach, infinity was able to get it to build and pass the test, just as I was when testing in a PPA.08:42
flexiondotorgdholbach, infinity and I agreed to wait to merge and upload for the 15.10 cycle.08:42
flexiondotorgdholbach, Any chance you could merge and upload today please?08:42
=== doko_ is now known as doko
tseliotpitti: hi, u-d-c seems to fail to build (i.e. to pass all the tests) on armhf and arm64. Is there a way to skip some of the tests based on the architecture?09:09
=== davidcalle_ is now known as davidcalle
tseliotpitti: that's in wily09:10
pittitseliot: I don't think you want to skip based on the architecture, but rather availability of the nvidia-experimental pacakge or hybrid-detect, or whatever the test checks?09:12
pittitseliot: and yes, you can do that; we already conditionally skip some tests09:13
pittitests/ubuntu_drivers.py:    @unittest.skipUnless(os.path.isdir('/sys/devices'), 'no /sys dir on this system')09:13
pittitseliot: just odd that this worked in vivid, looks like something in nvivia-experiemntal changed between vivid and wily?09:13
pittihttps://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.4.5 succeeded on all arches, after all09:14
tseliotpitti: maybe nvidia-experimental was finally removed09:14
tseliotpitti: or it was never there for arm09:14
tseliotthat's a transitional package09:15
tseliotactually, it was09:15
tseliotpitti: also, we no longer have nvidia-current and nvidia-current-updates09:16
pittitseliot: ah, nvidia-experimental is a dummy package from the tests, it never existed in actual ubuntu09:17
tseliotpitti: we had nvidia-$ver-experimental at some point, but the version was in the name too09:18
pittiso this looks like an issue/regression in python-apt, or something missing in the fake apt repo setup09:20
pittiin test_system_driver_packages_chroot() there is no nvidia-experimental being set up09:20
pittionly in test_system_device_drivers_chroot()09:20
pittiso that somehow seems to leak to the other test09:21
tseliotpitti: also the error on arm64 seems to be different09:21
tseliotan AssertionError vs the KeyError on armhf09:21
pittitseliot: probably the same issue, though -- the apt cache is bogus09:21
pittiaptdaemon and python-apt didn't change, but apt did09:23
tseliotpitti: shall we just skip the test for now? I'm trying to get a fix into wily before I actually SRU it09:25
pittino, please don't skip it09:25
pittithis is an actual regression or bug somewhere which should be investigated09:25
tseliotno doubt about it being a bug that needs to be fixed09:26
pittiand it's not likely to be specific to armhf, I guess it would randomly occur on any arch; so doing a few test builds in wily-proposed locally would be a good first step?09:27
pittithe fix is committed to git already, so you can SRU it anyway09:27
tseliotpitti: ok, it works for me then09:28
dholbachflexiondotorg, will take a look09:28
flexiondotorgdholbach, Thanks!09:29
* zyga recalls a discussion about [dg]conf sandboxing 10:03
zygaand recalls the path issue10:03
zygaand recalls windows virtual store feature10:04
dholbachLocutusOfBorg1, I'll update the changelog entries in the patches on 1417563, ok?10:25
jamespageanyone know whether its possible to use multicast on the launchpad builders?10:42
jamespage(context - http://paste.ubuntu.com/11077249/ - test failure in designate)10:42
jamespageinterestingly that works just fine in a virtualized PPA builder10:43
cjwatsonjamespage: don't think we really define that either way10:50
cjwatsonthat's a kernel module, I suppose?10:50
jamespagecjwatson, maybe - I was just surprised by the diff between virtualized ppa and distro builders10:51
cjwatsonjamespage: well, everything will become more like the former soonish10:52
cjwatsonit's a bit odd, I would have expected that kind of module to be autoloaded IIRC10:52
jamespagecjwatson, it might be the SO_REUSEPORT flag that's actually prohibited10:54
jamespagethat does have some security implications I guess10:54
jamespagecjwatson, what kernel do the distro builders run on?10:55
cjwatsonjamespage: look at the top of any build log10:55
jamespageyeah - sorry - just realized that10:55
jamespageits 3.2.010:55
cjwatsonright, and reuseport was 3.910:56
jamespagecjwatson, yeah - https://git.openstack.org/cgit/openstack/designate/commit/?id=c09a295c403e19811bf748d88155b368412c31bd10:56
jamespagelooks like upstream have a workaround10:56
jamespagepicking that now10:56
cjwatsonand the virt builders are 3.1310:56
cjwatsonoh, right, the non-virt builders are still on precise base systems10:58
cjwatsonwe won't be fixing that directly, we'll be moving all builds into scalingstack architecture by architecture instead10:59
cjwatson(well, some of the non-virt builders, it varies)10:59
=== MacSlow is now known as MacSlow|lunch
LocutusOfBorg1dholbach, please hold on, I can update them :)11:04
LocutusOfBorg1seems that Debian has new releases ready11:05
dholbachLocutusOfBorg1, it's done already11:07
dholbach@pilot out11:25
=== udevbot changed the topic of #ubuntu-devel to: Archive: wily open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== MacSlow|lunch is now known as MacSlow
LocutusOfBorg1dholbach, thanks!12:40
pittismoser: hey Scott! do you plan to merge cloud-utils with Debian? (I'm interested in the fix for debian bug 783826), or is cloud-utils independently maintained in Ubuntu?12:41
ubottuDebian bug 783826 in cloud-utils "cloud-utils: growpart uses deprecated sfdisk options" [Important,Fixed] http://bugs.debian.org/78382612:41
=== _salem is now known as salem_
=== rbanffy_ is now known as rbanffy
cyphermoxgood morning!13:03
cyphermox@pilot in13:03
=== udevbot changed the topic of #ubuntu-devel to: Archive: wily open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> utopic | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: cyphermox
smoserpitti, i have a fix for that . do we have htat sfdisk in ubuntu now?13:05
pittismoser: in wily-proposed13:06
smoserok. let me see if i can't get it uploaded.13:06
pittismoser: it doesn't migrate as it curently unconditionally Breaks: cloud-utils; that'll become versioned once cloud-utils gets fixed13:06
pittismoser: i. e. it's "safely" stuck in -proposed, I mostly wanted to know how we apply the fix13:07
smosercloud-utils is in ubuntu, debian maintain separately.  i should probably look to merge with them at some point. lp:~smoser/cloud-utils/growpart-sfdisk-2.26 has the fix .13:11
pittismoser: ah, you developed that independently? fedora and Debian have a fix too13:13
pittismoser: ok, thanks! I'll adjust the Breaks: in util-linux once this hits wily, then it can migrate13:15
smoserpitti, well, i kind of re-impleented what htey had.13:18
smoserthis new path with sfdisk 2.26 actually gets us to a point where we could use sfdisk for gpt partition table growth also.13:19
xnoxdoko: can you make -Wabi the default in debian & ubuntu and then grep logs / make buildd log scanner pick them up ( https://qa.debian.org/bls/ ) i guess it would already, no?13:27
dokoxnox, did you check, what it will pick up? because nobody did this experiment13:29
xnoxdoko: well, actually that's the wrong one. I'm after -Wabi-tag as per dual abi docs https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html13:30
xnoxdoko: boost started to intentionally use 03 abi string et.al. in a few places because they started to get bug reports about mixed abi.13:31
xnoxor rather use things that didn't change abi.13:31
xnoxNot all uses of the new ABI will cause changes in symbol names, for example a class with a std::string member variable will have the same mangled name whether compiled with the old or new ABI. In order to detect such problems the new types and functions are annotated with the abi_tag attribute, allowing the compiler to warn about potential ABI incompatibilities in code using them. Those warnings can be enabled with the -Wabi-tag option.13:31
xnoxthat's what i'm afraid off.... when symbol names mangle the same way, but are in fact different.13:32
xnoxdoko: looking at fedora they did f22 release with gcc-5 but changed _GLIBCXX_USE_CXX11_ABI to be 013:32
dokono, cxx11 symbols mangle differently13:32
xnoxand they ware doing f23 release with _GLIBCXX_USE_CXX11_ABI to 1. Not sure if that's good or not.13:32
dokoyes, they didn't have the time13:33
dokosuse is doing it directly13:33
xnox"for example a class with a std::string member variable will have the same mangled name whether compiled with the old or new ABI." -> surely things will explode if something uses that member variable in 03 & 11 context, no?!13:33
smoserpitti, just realized util-linux should break cloud-guest-utils, not cloud-utils. i think.13:35
pittismoser: ah, Debian didn't split it; sure, I'll adjust that together with the versioned breaks: then13:35
dokoxnox, who says this? note, that currently can't check this without a custom build, had to disable the dual abi13:37
xnoxdoko: call me conservative, but when upstream docs say "things can break" i give them a benefit of a doubt that "the world will be on fire"13:40
xnox... and given latest election results, we are all conservative here in the UK, supposedly. ( /me ponders if Laney will find this comment funny )13:40
=== elopio_ is now known as elopio
=== marcusto_ is now known as marcustomlinson
dokoxnox, which upstream, boost or libstdc++?14:05
xnoxdoko: boost.14:08
xnoxdoko: libstdc++ did it for e.g. exceptions. (internally)14:08
xnoxdoko: well, some portions of boost upstream (maintiner of boost-filesystem for example did that)14:09
xnoxbut they do believe it is not sustainable.14:09
dokoyes, the old experimental c++11 abi and the new stable c++11 abi are not compatible14:10
dokothat's the reason why I disabled the dual abi for now14:10
* Laney votes for xnox 14:28
infinityUnit193: It's in the trusty branch.14:47
=== dholbach_ is now known as dholbach
bdmurraympt: Do you have a suggestion on what color to use for Wily in the Error Tracker?15:10
mptbdmurray, the current sequence goes through the primary and secondary colors ROYGBV … Have we gone through a complete cycle of that? (I don’t remember, and can’t tell while bug 1073560 and bug 1053410 are unfixed)15:12
ubottubug 1073560 in Errors "Legend doesn't scale to the number of versions shown" [Medium,Confirmed] https://launchpad.net/bugs/107356015:12
ubottubug 1053410 in Errors "Graph doesn't go back as far as the first recorded errors" [Low,Triaged] https://launchpad.net/bugs/105341015:12
mptbdmurray, if we haven’t, the answer is easy. :-) If we have, maybe repeat the cycle but go lighter15:13
mpt(since “by 12.04 standards” makes hardly any difference any more)15:14
bdmurraympt: 15.04 is the bright green https://errors.ubuntu.com/?release=Ubuntu%2015.04&period=day15:14
mptAh, right, so we’ve already started the “go lighter” cycle, since 12.04 was dark green15:15
mptwhich means that Wily would be … light blue?15:16
mpta lighter blue than 12.1015:16
ogra_pitti, dont you like #snappy anymore ?15:24
pittiogra_: ah, must have lost it in last bip reconnect, sorry15:29
dokojamespage, maven mismatches ...16:22
=== d_ed is now known as d_edt
=== d_edt is now known as d_ed
=== sforshee` is now known as sforshee
markeliteno, ignore that20:42
smoseris it sane/possible to Recommends with an |20:43
smoseri'd like:20:43
smoserRecommends: util-linux (>= 2.26) | gdisk20:44
smoserslangasek, ^ ?20:53
slangaseksmoser: that's legitimate, sure20:53
smoserok. thanks.20:54
lifelessIIRC left hand is chosen in the absence of any other constraints20:54
smoseryeah, that shwat i thought20:54
slangasekso in this case you probably want gdisk | util-linux (>= 2.26), to force install of gdisk to satisfy the recommends on those systems too old to have util-linux 2.2620:55
smoserreally ?20:56
smoseri dont follow that.20:56
smoserif the left hand side matches (util-linux >=2.26) then that is preferable.20:56
smoseroh well. /me assumes slangasek is right and uploads and goes afk20:58
smoserpitti, just uploaded 0.27-0ubuntu16 which should work20:59
slangaseksmoser: if util-linux 2.26 is already installed, the recommends is a no-op20:59
slangasekbut if it's not installed that probably means it's not available20:59
slangaseksmoser: however this is all a corner case20:59
smoserk. thanks.21:00
=== mwhudson_ is now known as mwhudson
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
=== _salem is now known as salem_
=== greyback__ is now known as greyback

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