[13:36] <mvo> rbalint: hey, iirc you work quite a bit on shadow, right? I have a change for "su" that I would love to get an opinion on: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/984390
[13:36] <mvo> rbalint: this is an issue on core18 currently but the bug itself was reported some time ago (and has a patch). if that looks valid I can prepare a cosmic upload
[13:53] <rbalint> mvo, looking
[13:55] <mvo> rbalint: I guess I need to also sent this upstream
[13:58] <rbalint> mvo, morover the plan is shipping login/su/... from util-linux, thus it we change anything we should make sure the switch won't regress it https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833256
[14:00] <rbalint> mvo, i'm generally ok with the patch, offering it upstream would be nice, so please do it or I can do it sometimes later
[14:01] <mvo> rbalint: great, thank you, I clean it up a little and sent it upstream
[14:01] <mvo> rbalint: I can also look at util linux just to see what will happen once the switch happens
[14:02] <rbalint> mvo, thanks!
[14:02] <mvo> rbalint: thank you
[14:15] <mvo> rbalint: I updated the bug with the link to the upstream report and my finding about util-linux (looks like there su-common.c is DTRT from reading the code)
[14:22] <cpaelzer> doko: search engines won't help me, is "invalid suffix ... on integer constant" more common with the most recent toolchain?
[14:26] <doko> cpaelzer: context?
[14:26] <cpaelzer> doko: https://launchpadlibrarian.net/375901368/buildlog_ubuntu-cosmic-amd64.qemu_1%3A2.12+dfsg-3ubuntu1~ppa2_BUILDING.txt.gz
[14:26] <cpaelzer> most common case: my mistake, but I fail to yet see it
[14:26] <cpaelzer> I kicked a rebuild of the most recent version (to make sure if it is me or the toolchain)
[14:27] <cpaelzer> then I know in which direction to stare more
[14:27] <cpaelzer> doko: but if you might know like "yeah this now is more often because ..." I would appreciate to know about it
[14:27] <doko> no idea, maybe look at the macro expansion first?
[14:27] <cpaelzer> already on it
[14:28] <cpaelzer> only inserts it into  function/struct names
[14:28] <cpaelzer> which is why I wonder if any of it now wconsiders 2_12 an int
[14:28] <cpaelzer> doko: but TL;DR you are not aware of common issues, so most likely something on my rebase broke
[14:28] <cpaelzer> let it be my task then
[14:28] <cpaelzer> only wanted to poll for known issues on that
[14:36] <doko> cpaelzer: sorry, no
[14:37] <doko> python had thousands separators, not C ;)
[14:37] <cpaelzer> hehe :-)
[15:25] <sil2100> slangasek, cyphermox: hey! Could one of you merge my keep-grub-pc ubiquity branch? I can release this without having it merged, but I didn't want to introduce a desync between the vcs and what's in ubuntu
[15:25] <sil2100> slangasek, cyphermox: of course, if you don't mind that, I could also just release that as is
[15:48] <slangasek> sil2100: I cannot, I am not in the installer team
[15:49] <cyphermox> I will
[16:08] <sil2100> cyphermox: thanks!
[16:08] <sil2100> slangasek: uh oh, I could have checked, I just assumed because you should be part of "all the teams" I guess!
[16:13] <cyphermox> sil2100: slangasek: well, you both should probably be in that team, cjwatson or xnox can fix that
[16:18] <cjwatson> done
[16:18] <cjwatson> you will probably want to filter at least incoming ubiquity bugmail
[16:19] <cjwatson> oh, hm, I think slangasek may have been there already and deactivated themself; apologies if that was intended
[16:19] <slangasek> oh?  not that I was ever aware of doing :)
[16:19] <slangasek> well, maybe past-me was aware
[16:20] <cjwatson> ICBW but your membership date is nearly a decade ago
[16:20] <sil2100> cjwatson: thank you!