[07:57] <seb128> xnox, doko, hey, is gcc-7 not building a libasan on s390x wanted or a bug?
[08:31] <xnox> seb128, i do not believe libasan is available on s390x, thus things should have conditional B-D, unfortunately.
[08:32] <seb128> xnox, k, thanks, meson autopkgtests fail on s390x due to that :/
[08:39] <Laney> it's usually pulled in by libgcc-*-dev I think
[09:05] <sarnold> Unit193: I believe leosilva is working on irssi updates; he may be able to push those out in the next day or two
[12:45] <Unit193> sarnold: I see.  Thanks.
[15:31] <xnox> infinity, given we do not care about d-i netboot size (it's not fixed, just big enough for current set of things) maybe we should calculate the size of all the things we want to copy, then create the empty dd image of the right size. Or e.g. create something really big, and shrink to smallest possible, after done copying all the things.
[15:31] <xnox> and we can have a kpi tracking the size, to make sure it doesn't become actually outragous.
[15:32] <xnox> infinity, cause FTBFS because kernels became bigger (and they will, always become bigger, due to more modules for yet another vendor of network cards)
[15:32] <xnox> what do you think?
[15:34] <GunnarHj> mapreri: Hi Mattia! As a DD, can you possibly help out with bug #1621861?
[18:40] <infinity> xnox: Who would watch this mysterious kpi?  The argument generally given for the limit is to prevent extreme growth due to oopses (which has, indeed, happened), and I doubt I'd bother watching a graph to see when that happened.
[19:03] <nacc> tjaalton: heya, just rebooted bionic and all of a sudden my external monitor stopped working (and well, can't get to the greeter without nomodeset), have you seen this:
[19:03] <nacc> [  178.256143] deja-dup-monito[5011]: segfault at bbadbeef ip 00007f5a67076588 sp 00007ffdc1addb30 error 6 in libjavascriptcoregtk-4.0.so.18.7.6[7f5a662be000+fc4000]
[19:03] <nacc> jbicha: --^ or you?
[19:03] <nacc> oh lol, nm, that's unrelated to actual monitors
[19:03] <nacc> well, the original message then :)
[19:04] <jbicha> nacc: I don't know any thing about your external monitor but there is LP: #1751460
[19:04] <nacc> jbicha: thanks for that link
[19:05] <nacc> i guess it's possible the issue with the monitor is kernel driven, but it's the same kernel i was on before
[19:05] <nacc> i guess i'm lucky this is the first breakage i've hit in bionic so far :)
[19:08] <jbicha> nacc: I'll try harder ;)
[19:08] <nacc> jbicha: heh
[19:14] <jbicha> we did break -proposed this morning so it's a good thing you weren't using -proposed :|
[19:43] <nacc> jbicha: hrm, i hav ea feeling it might be the gnome-shell update (it's starting to peg my cpu even in the receovery destkop)
[19:44] <jbicha> I pass the blame to libglvnd
[19:44] <nacc> jbicha: :)
[19:44] <jbicha> I mean we had LP: #1751414 a few days ago
[19:45] <nacc> jbicha: ack, i am running the updated packages for that from proposed, i believe
[19:46] <jbicha> you *are* running proposed? 🤦
[19:47] <nacc> jbicha: those specific packages from proposed
[19:47] <jbicha> I suggest 'ubuntu-bug display' to start a bug with debug info about your graphics drivers
[19:47] <nacc> ack
[19:48] <jbicha> libglvnd and mesa migrated this weekend so maybe you're back on mainline bionic now
[19:48] <nacc> yeah
[19:53] <nacc> jbicha: of course happy to debug further, LP: #1753576
[20:12] <tjaalton> the dpkg log looks fine
[20:13] <tjaalton> nacc: ^ meaning you should have everything from the transition
[20:13] <tjaalton> need a dmesg from a failing boot
[20:16] <mapreri> GunnarHj: you basically just filed that bug. of you trying to reach GCS and poke at him there is nothing I can do about that bug for some months…
[20:17] <mapreri> unfortunately he doesn't often hang out on IRC…
[20:18] <nacc> tjaalton: i'm not sure how to get it :/ ... if i pass text to the kernel, for some reason gdm still spins up x and it freezes
[20:18] <nacc> tjaalton: any suggestsions?
[20:19] <mapreri> GunnarHj: I supposed you were talking about NMUing the package… we've had a recent case of somebody wanting to add a Multi-Arch:foreign to a package, the maintainer made a fuss about the person filing the bug in December and trying to get a NMU in January, and as a coconsequence've been told that without waiting several months it is not acceptable :\
[20:20] <tjaalton> nacc: well, you could try booting into 4.13 to rule out the kernel
[20:21] <nacc> tjaalton: ok, i can do that, i'm going to be afk for a bit
[21:39] <mapreri> How can I unlink the debian bug from https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/238276 ?  ISTM only ~registry and Mark could do it??
[21:40] <mapreri> or maybe leave it like that, I'll just retitle and re-scope the bug… but the question stands, it's not the first time I'd like to.
[21:43] <GunnarHj> mapreri: In this case the maintainer has already taken a step to multiarch'ing the package by fixing https://bugs.debian.org/777224 - he just forgot debian/control. That's why I felt that a NMU would be harmless. But you know the culture better than me. ;)
[21:44] <mapreri> GunnarHj: Not that many DDs take NMUs happily.  ISTR gcs does better than others, but would still prefer to do things himself.
[21:45] <GunnarHj> mapreri: An Ubuntu delta is another option. Would be good to have it fixed in 18.04.
[21:46] <mapreri> GunnarHj: could you try to mail gcs saying that, or otherwise feel free to ping me like next week and I can upload it to ubuntu.
[21:46] <GunnarHj> mapreri: Ok, that sounds as a reasonable way to handle it. Will do. Thanks!
[23:52] <cjwatson> mapreri: Not ~registry.  Looks like basically ~launchpad-debian-maintainers (so in practice probably just wgrant) or admins.
[23:53] <mapreri> why did I read ~launchpad-debian-maintainers as ~registry -.-
[23:54] <mapreri> cjwatson: who's ~james-w that I don't remember ever reading about?
[23:55] <cjwatson> mapreri: Used to do the Bazaar package importer and a bunch of other stuff.  Possibly before your time though
[23:55] <mapreri> cjwatson: could perhaps ~debiandevelopers be made a bug supervisor for debian?
[23:55] <cjwatson> I wouldn't object but you'd have to ask William :)
[23:56] <mapreri> wgrant: could perhaps ~debiandevelopers be made a bug supervisor for debian?
[23:58] <cjwatson> (It seems odd to me that ~launchpad or ~registry or something isn't in ~launchpad-debian-maintainers, too.)
[23:59] <mapreri> ~launchpad would be odd, but it really would be ~registry material
[23:59] <mapreri> (but then, ~launchpad is in ~registry, so…)