/srv/irclogs.ubuntu.com/2016/12/02/#ubuntu-devel.txt

=== _salem is now known as salem_
naccinfinity: also, i'm realizing (and it may not really matter, since it's zesty only), but the rebuilt ruby-rmagick migrated through, and won't work. I guess that's what you were asying earlier? I think the above debdiff, corrected a bit more, would hvae held it in -proposed until imagemagick also was able to migrate?01:14
BluefoxicyI don't know if Ubuntu maintains the official Ubuntu Docker image, but we're having this spirited discussion on the Debian one:  https://github.com/tianon/docker-brew-debian/issues/56#issuecomment-26434298501:19
tianonyes, the Ubuntu official Docker image is produced and maintained in collaboration with Canonical ;)01:21
sarnoldBluefoxicy: https://wiki.ubuntu.com/YakketyYak/ReleaseNotes#GCC01:21
Bluefoxicysarnold:  wow, that's bold.  We were discussing -fstack-protector-strong largely.01:22
sarnoldBluefoxicy: debian did much the same, https://launchpad.net/debian/+source/gcc-6/+changelog see 6.2.0-701:23
sarnoldBluefoxicy: oh cool01:23
BluefoxicyMy observation is mainly that lots of official images (nginx, java, apache, anything based on java e.g. tomcat, php, ...) are based on debian:jessie, and publishes upstream releases by compilation mainly with autoconf.  End result is a lot of off-hand compilation without stack protection.01:24
sarnoldindeed01:24
sarnoldthat kind of thing is why we changed our gcc dfeaults rather than just dpkg-builflags mechanisms. so much software build outside of our archive...01:24
Bluefoxicyso the options are A) tell every single upstream to add CFLAGS= to their downstream Dockerfile; B) add the appropriate flags to the upstream image; or C) modify the compiler.01:24
Bluefoxicynod01:24
Bluefoxicymodifying the compiler environment catches anything with autoconf, but nothing without it01:25
BluefoxicyI'm uncomfortable modifying the compiler in drastic ways01:25
Bluefoxicyalthough in DEbian/Ubuntu that's no big deal01:25
sarnoldwell, it wasn't without detractors :)01:25
Bluefoxicyin GCC upstream, you get oddness like muslc not providing certain facilities, and then you compile stuff with -D_FORTIFY_SOURCE=2 and things magically break01:26
sarnoldkernel git bisect got more difficult.. sigh.01:26
Bluefoxicyand then all of alpine-linux developers are pissed01:26
Bluefoxicysarnold:  -Wl,-O1 -Wl,--hash-style=both btw ;)01:27
Bluefoxicynot sure if that's default now?01:27
sarnoldno idea..01:27
Bluefoxicyhttps://lwn.net/Articles/192624/01:27
Bluefoxicy-Bdirect never went anywhere; the other three are sane01:29
Bluefoxicy... hash style defaults to "sysv", linker optimization defaults to -O001:30
sarnoldBluefoxicy: there's so many interesting things in the world. nice comments ten years ago btw :)01:34
Bluefoxicyalthough it looks like at least /bin/ls has dynsym, dynstr, and gnu hash01:34
Bluefoxicyso obviously the Ubuntu build servers are doing the right thing01:34
Bluefoxicysarnold:  I was a bit brighter ten years ago01:34
sarnoldBluefoxicy: doko takes pride in having the fastest userspace builds around :D01:34
sarnoldBluefoxicy: hehe01:34
Bluefoxicysarnold:  still embarrassed by Firefox taking like 47 seconds to load while Firefox built on anything else took 6 seconds to start back in Warty?01:35
Bluefoxicythe world's come a long way in ten years01:35
Bluefoxicyhow did we ever get from one distribution loading a Web browser extremely-slowly being front-page news for months to a world where half the Internet is down because Dyn is under attack by twelve-year-olds?01:36
sarnoldI'm more surprised that 25 years ago I still had fun on computers that weren't connected to any other computers :)01:37
Bluefoxicyapt-get install super-methane-brothers ?01:38
sarnoldworse, even qbasic gorillas.bas  was fun01:39
Bluefoxicygorillas nothing, what I need is cats01:46
* Bluefoxicy grumbles at mouse01:47
=== salem_ is now known as _salem
infinitynacc: debian/ruby-rmagick/DEBIAN/shlibs won't work because that's for documenting shlibs of libraries that ruby-rmagick ships.06:03
infinitynacc: I'd probably also strip the "-6.Q16" off the end of your regex to avoid having to fiddle with that too much with every libmagickcore bump.  If you really think ruby-rmagick could end up linked to two different libmagickcore libraries, there are bigger issues afoot.06:05
infinitynacc: Otherwise, looks reasonable enough to me.  If there's a way to divine "RMagick2.so" from other files in debian/ to avoid specifying it in rules (I dunno, a gross grep of debian/foo.install or something) that might be "nice", but also pretty sure that doesn't change often enough for it to be a big deal.06:06
naccinfinity: ah! ok, that makes more sense, i must have misunderstood that part of the manpage06:07
naccinfinity: ack on the regex06:07
naccinfinity: thanks for taking a look!06:07
pittiGood morning07:28
Laneydoko: Can you help with insighttoolkit4/ppc64el please? You enabled the build for all arches a while ago, and now it gets ENOSPC on ppc64el10:51
Laney(the build log on launchpad isn't helpful)10:51
dokoLaney: how should I help? filing a bug against the buildds that they run out of disk space, or massage the build to take less disk space, maybe not building with -g?10:52
dokohttps://bugs.launchpad.net/ubuntu/+source/insighttoolkit4/+bug/1595485 ask for the removal10:54
ubottuLaunchpad bug 1595485 in ldc (Ubuntu) "packages to remove from zesty" [Undecided,New]10:54
Laneydoko: The latter, see #launchapd-ops10:54
Laneyit failed when installing the package at the end so maybe not that much more is needed10:55
Laneyor if you want to rip it all out, that's fine by me10:55
Laneythere's a lot of rdeps and untangling all of that doesn't seem like much fun :-)10:55
dokodebian buildds don't like it either ... even on x86 archs: https://buildd.debian.org/status/package.php?p=insighttoolkit411:02
Laneylooks like its in progress?11:03
Laneyprobably going to build everywhere else in zesty at least11:03
dokono, apparently manually uploaded11:03
dokoLaney: I would try with -g -O2 first /using STRIP/APPEND options11:04
Laneydoko: Just strip O3 and append O2?11:05
Laneythere's already a commented out block for that in rules11:05
Laneyfrom you ;-)11:06
Laneyok, I'll try it11:06
Laney22 hour build time is not fun11:06
Laneydoko: https://paste.ubuntu.com/23567354/ ok?11:10
dokomaybe I should turn on compressed debug info by default ... but I'm not sure what else that would break ...11:10
dokosure, looks fine11:11
LaneyO2 makes smaller binaries?11:11
dokoit should with inlining off.11:12
Laneyhttps://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2253/+build/1128981411:14
jgdxseb128, hey, how's that unity8 situation? Closer to being resolved?11:21
=== _salem is now known as salem_
Laneydoko: trying a build with -gz -feliminate-dwarf2-dups on ppc64el too11:33
Laneyman gcc -> search "compress"11:33
LaneyI don't need to set anything in LDFLAGS as well do I?11:35
dokoit should, --compress-debug-sections=...11:37
Laneyyou need both?11:38
LaneyI thought -gz would make them compressed in the first place11:38
Laneyah well, let's see11:39
Laneyall good fun11:39
dokoLaney: -gz needs to be passed to the linker too, the driver translates that to --compress-debug-sections=zlib for ld11:40
Laneyah11:41
dokohmm, I think that needs a test rebuild, and then be turned on when we open z+1 ...11:46
Saviqpitti, hey, re: resolved, I rely on "additional search domains" at home, my dhcp is sending them and they always ended up in resolvconf; I've had trouble with that since upgrading to zesty, and having installed NM from proposed now it doesn't work still - configuring them in the connection editor doesn't seem to work either, any idea how this should work? should the domains end up in resolv.conf?12:28
Saviqresolved only responds to FQDN, and that's correct, AFAIK - and `ping foo` works, but `ping bar.baz` (bar.baz.search.domain being the FQDN) does not12:31
pittiSaviq: no, they can't end up in resolv.conf -- it has a too limited syntax for that12:50
pittiSaviq: you should see them in "systemd-resolved --status"12:50
pittiSaviq: /etc/resolve.conf should only have 127.0.0.53, unless you have another resolvconf client installed (like unbound or whatnot)12:50
Saviqpitti, ok I see them there, still, resolved doesn't seem to respect them?12:51
pittiSaviq: hm, mind filing a bug12:52
Saviqpitti, will do12:52
seb128jgdx, it was resolved yesterday no?12:52
pittiSaviq: oh, sorry, I misread "additional search domains" as "domain-limited DNS servers" somehow12:52
pittiSaviq: just curious that this didn't work with NetworkManager/dnsmasq either12:52
Saviqpitti, it worked before zesty - after upgrading my setup was a bit wonky (bug #1637700)12:53
ubottubug 1637700 in network-manager (Ubuntu) "Caching dnsmasq stops resolving after some time" [Undecided,New] https://launchpad.net/bugs/163770012:53
Saviqthis might've been a IPv6 issue now I think about it (have disabled v6 for now due to other issues)12:54
jgdxseb128, okay, great! thanks12:55
seb128jgdx, yw! do you still have issues or did you just ask out of curiosity?12:56
Saviqjgdx, seb128, we've a problem with oxide now12:56
Saviqon xenial+overlay12:56
jgdxseb128, my silo's just not getting published12:56
Saviqa new oxide was released into xenial-security, newer than the one in overlay12:56
seb128jgdx, k, I don't know what the specific issue is but unity8 migrated yesterday12:57
Saviqso qml-module-ubuntu-web is uninstallable12:57
seb128oh12:57
Saviqhttps://bileto.ubuntu.com/#/ticket/214812:57
seb128what Saviq said then12:57
=== hikiko is now known as hikiko|ln
Saviqthis fixes it, but will take a day still to land12:57
Saviqjgdx, which silo, btw?12:57
jgdxSaviq, this is holding up silo 2194?12:57
jgdx^12:57
pittiSaviq: bug 1592721 landed late in yakkety, and IIRC that correlated with several bug reports12:58
ubottubug 1592721 in network-manager (Ubuntu Xenial) "Don't write search domains to resolv.conf in the case of split DNS" [Medium,Fix released] https://launchpad.net/bugs/159272112:58
pittiSaviq: which at least sounds related to your pre-resolved observations12:58
pitticould still be that it doesn't send these to resolved either12:58
pittiah no, you said that you do see them in --status12:58
Saviqpitti, bug #1636375 sounds even more related12:59
ubottubug 1636375 in systemd (Ubuntu) "systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf" [Undecided,Confirmed] https://launchpad.net/bugs/163637512:59
Saviqkinda13:00
pittiSaviq: ah, is it that one? i. e. unqualified names are expanded, but not qualified prefixes?13:00
Saviqpitti, to some extent, yes - but I only have resolved in resolv.conf13:01
pittiwell, that's fine -- and for the most part, /etc/resolv.conf is entirely irrelevant these days13:01
pitti(except for chromium)13:01
pittior if you stop resolved13:01
Saviqsure, I just mean that stopping resolved won't help here (or will it? /me tries)13:02
pittiah no, it won't13:02
Saviqpitti, yeah, I'd have to add the nameserver and search bits into resolvconf manually, but I suppose the real issue is the same as the bug says13:05
pittiSaviq: so can you resolve unqualified names with search expansion?13:05
pittii. e. "foo",  not "foo.bar"13:05
Saviqpitti, correct13:05
pittiand it would try "foo.baz" if you have "search baz"13:05
pittiSaviq: ah good, then it's that bug too13:05
SaviqI have "bar.name" and "name" as search domains, foo resolves, as does foo.bar.name, but not foo.bar13:07
Saviqpitti, https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636375/comments/5 - let me know if you need more details please13:11
ubottuLaunchpad bug 1636375 in systemd (Ubuntu) "systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf" [Undecided,Confirmed]13:11
Saviqmake that https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636375/comments/613:12
ubottuLaunchpad bug 1636375 in systemd (Ubuntu) "systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf" [Undecided,Confirmed]13:12
pittiSaviq: ack, thanks; a bit confusing to mix sawicz.net and foo.name in that way, but I know what you mean13:12
Saviqpitti, sorry, fixed the comment now13:12
Saviqor not13:12
pitti*nod*13:12
Saviqone more try13:12
pittiwell, close enough :)13:12
mdeslaurdoko: I'm stealing your nss merge13:45
dokoLaney: did you start that insighttoolkit4 build with -gz in both CXXFLAGS and LDFLAGS?13:45
dokomdeslaur: it's your's anyway ;p13:45
=== hikiko|ln is now known as hikiko
dobeydoko: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1646064/comments/114:28
ubottuLaunchpad bug 1646064 in glibc (Ubuntu) "investigate autopkgtest regressions in 2.24-7ubuntu1" [Undecided,New]14:28
Laneydoko: gcc -gz gives an error15:11
Laney-Wl,--something seemed to work15:11
LocutusOfBorg[16:17:26] <LocutusOfBorg> hi, is anybody there console-setup savvy?15:24
LocutusOfBorg[16:17:44] <LocutusOfBorg> wrt launchpad bug lp: #144385315:25
LocutusOfBorg[16:17:46] <ubot5> Launchpad bug 1443853 in kbd (Ubuntu) "Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display" [Undecided,Confirmed] https://launchpad.net/bugs/144385315:25
LocutusOfBorg[16:17:54] <LocutusOfBorg> the fix might be simple15:25
ubottuLaunchpad bug 1443853 in console-setup (Ubuntu) "Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display" [Critical,Confirmed] https://launchpad.net/bugs/144385315:25
LocutusOfBorgforwarding from -release ^^ maybe better to talk here15:25
dokoLaney: ok, -gz works in gcc-7, will need to find out why not in 6 ...15:38
dokook, needs a back port15:44
Laneylooked like it was something set up at build time15:45
dokofound it, both gcc-5 and gcc-6 are missing the backports15:48
Laneyhope it still makes a difference with just the linker option15:49
dokosure, it das. checked with the bash binary15:50
Laney:)15:51
doko$ ls -l *essed15:51
doko-rwxrwxr-x 1 doko doko 2464104 Dez  2 16:25 bash-compressed15:51
doko-rwxrwxr-x 1 doko doko 4691648 Dez  2 15:52 bash-uncompressed15:51
dokounstripped binaries15:51
Laneywith -Wl,--compress-debug-section=soemthing?15:52
Laneynod, that's what I tried too (on a hello world), made some difference15:53
dokono, built a binutils defaulting to compressed debug sections15:54
Laneyk15:55
dokohttps://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc/+sourcepub/7209526/+listing-archive-extra (still building there)15:57
naccinfinity: in the shlibs.local file, I have to specify the SOVERSION (aiui) -- is it appropriate for me to just extract that from the library version? Since I am using that specific library to determine which package provides it?16:46
infinitynacc: Well, if you insist on specifying it as shlibs.  I'd just inject the dep directly, if I were you.16:48
naccinfinity: ack, that is probably much easier :)16:49
infinitynacc: So, move that mess from override_dh_shlibdeps to override_dh_gencontrol, and inject the dep there.16:49
naccinfinity: yep, thanks!16:50
infinitynacc: dpkg-gencontrol is smart enough to reduce "foo (>= 1.0), foo (>= 2.0)" to just "foo (>= 2.0)", so shlibdeps will give you the "right" one, and you'll inject the new one, and it'll sort it out.16:50
naccinfinity: ah that was what I was going to test, great!16:51
infinitynacc: But to answer your question more directly, yes doing what you suggested would be appropriate. :)16:52
infinitynacc: (Just less code to do it the dep/control way instead of the shlibs way)16:53
infinityLess code, more readable, and probably more obvious to the next passer-by how it works.16:53
naccinfinity: agreed! :)16:54
infinitynacc: So, yeah, you can probably ditch the \n from the dpkg-query return, stuff it in a make var, and feed that variable to dpkg-gencontrol, and Bob's your uncle.16:55
* infinity handwaves over the details, since it's too early to be pastebinning examples.16:56
dokoinfinity: do you expect glibc to migrate today, or will it take some more time?16:56
infinitydoko: I expect to be uploading a new one.  Is there some urgency?16:56
dokook, then starting the test rebuilds now without it16:56
infinity(And if there was urgency, is there a reason you didn't ask me to merge it instead of just taking it on yourself to do so?)16:56
dokowell, I did ...16:56
infinitydoko: The only thing I have from you is a request to fix the ppc build failure on the next upload.  There wasn't a time limit attached to it. :P16:57
infinityAnyhow, redoing the merge, since your merge wasn't actually a complete merge.16:57
infinityAnd fixing the other bits that were staged for that upload.16:57
infinityAnd still investgating weird regressions.16:58
infinityBut I don't think any of it should be relevant to the test rebuild.16:58
naccinfinity: right, that's what i'm thinking as well -- working on it now16:59
=== JanC is now known as Guest2425
=== JanC_ is now known as JanC
bdmurrayflexiondotorg: What's the status of bug 1623856?18:08
ubottubug 1623856 in aptdaemon (Ubuntu) "Scrolled Windows in update-manager are too small to read" [Low,In progress] https://launchpad.net/bugs/162385618:08
naccinfinity: http://paste.ubuntu.com/23568890/ seems to extract the correct value into the resulting binary package18:45
infinitynacc: Why the eval?19:13
naccinfinity: I found that without that, the variable wouldn't get defined in the target section19:13
naccinfinity: as it needs to be resolved at run-time, not parse-time?19:13
infinityOh indeed.19:13
naccbasically, makefile gotcha :)19:14
infinitynacc: Yeah, not braining well.  Haven't slept much. :P19:14
naccinfinity: np! i hit my head against it for a while until i bothered googling a bit :)19:14
infinitynacc: Looks sane enough, and if it tested okay too, yay.19:14
naccinfinity: yep, i'm sending it to debian for comments19:15
infinitynacc: Could perhaps use a comment explaining why all that evil exists.19:15
nacci've bisected the php-imagick failure too, it's an imagemagick change which maybe broke the testcase's assumption19:15
naccinfinity: yep, agreed :)19:15
naccinfinity: with a small comment: http://paste.ubuntu.com/23569056/19:18
infinitynacc: I'd include a ref to the Debian bug where the imagemagick maintainers told you to piss off.19:19
naccinfinity: oh good point!19:20
infinity(Not for political reasons, but just so that future ruby-rmagick and/or imagemagick maintainers can easily find the history of the hack.19:20
infinity)19:20
naccinfinity: agreed19:21
* doko watches kees rising from the dead ...20:03
kees;p20:04
keesgdb haaaaaack20:04
dokokees: please send it upstream20:07
keesdoko: yeah, that's my intention. I always get the Changelog formatting wrong, but I'll give it a shot. ;)20:08
=== ahoneybun_ is now known as ahoneybun
keesdoko, bdmurray: sent upstream!21:46
dokoLaney: -gz now recognized in 6.2.1-5ubuntu222:41
dokoinfinity: I'm (mis)using the https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc PPA for the compressed-debug-info test rebuild. please don't change anything in this ppa for zesty (at least you didn't in the last few years ;)22:57

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