[09:32] <rbalint> ddstreet, yes, the plan is merging 242 from Debian instead of cherry-picking more changes
[11:54] <ddstreet> rbalint ah ok, well i'll just sru and leave eoan as is then
[12:37] <ddstreet> rbalint you mind if i push systemd to eoan to fix the FTBFS in the meantime, until it's updated to 242?
[14:08] <coreycb> sil2100: hi, did you happen to get a chance to look at those RM bugs?
[14:13] <sil2100> coreycb: sorry, got preempted last time and then forgot, picking them up now
[14:22] <coreycb> sil2100: no problem, thanks so much
[15:04] <sil2100> coreycb: ok, so I processed as many removals from the list as possible - I could not act on 2 of the bugs because the packages still had 'valid' reverse-dependencies
[15:04] <sil2100> Left some comments there
[15:05] <coreycb> sil2100: thanks i'll take a look
[15:30] <rbalint> ddstreet, feel free but i'd rather drop it from proposed since issues keep popping up due to missing patches for gcc9
[15:37] <ddstreet> rbalint the FTBFS is an upstream bug, the testcase overflows the stack, i'll fix it upstream first but it's trivial to fix in eoan as well
[15:38] <ddstreet> but, i can just leave eoan alone...just means nobody can build systemd for eoan until 242 is merged (and hopefully, it will build then)
[15:40] <rbalint> ddstreet, feel free to push the fix to eoan, too, i may not finish the merge today
[15:41] <rbalint> ddstreet, my point was that it may not be the last issue to fix before it can migrate
[15:41] <ddstreet> rbalint if you're merging todayish, i'll just stay out of your way
[15:43] <rbalint> ddstreet, i start today, but i think it will take a few iteration to polish it, so if you are fairly certain that this update gets it to release, (like built in on all arches and autopkgtest passes) then it is worth a shot
[15:44] <rbalint> ddstreet, santa_ also reported an issue, thus it is not only a testcase fix that's missing
[16:12] <santa_> ddstreet: FYI the issue I have seen is that _sometimes_ the systemd from proposed hangs on "systemctl start network-online.target". the autopkgtest LXD backend relies on this command, so it makes autopkgtest hang. I have inspected systemd's git and there's a number of changes in the part I believe is involved in the hang
[16:13] <santa_> rbalint: btw, whenever you have a package ready to test feel free to ping me and I will test as soon as I can
[16:18] <roaksoax> ir
[17:34] <ddstreet> santa_ have you opened a lp or upstream bug, and/or have dbg logs of it happening?
[17:35] <ddstreet> if you are confident it's already fixed upstream tho, probably easiest to just retest after the merge to 242
[17:39] <santa_> ddstreet: I'm not confident it's fixed upstream but the code involved changed
[17:40] <santa_> let me see if I can find a build log with the thing happening
[17:46] <santa_> http://tritemio-groomlake.duckdns.org/logs/knewstuff_5.60.0-0ubuntu1%2btritemio9_amd64-2019-07-19T21%3a16%3a10Z
[17:47] <santa_> ddstreet: ↑ just search "network-online.target" there
[18:01] <ddstreet> santa_ well network-online.target will definitely block for more than 60 seconds if it's having trouble actually setting up the nw
[18:01] <ddstreet> you sure that's not the problem?
[18:11] <santa_> ddstreet: when that happened I got into the cointainer and if I recall correclty, the thing was blocked ad-infinitum, even after the network was actually up
[18:11] <ddstreet> ah, well yeah that's bad then
[18:12] <ddstreet> santa_ did you happen to notice, in the container, and dbus errors?  i've seen 'lost' dbus messages that cause waiting systemd processes to never finish, in some autopkgtests https://github.com/systemd/systemd/issues/12932
[18:13] <ddstreet> you may need to turn on debug though, at least for dbus
[18:13] <ddstreet> hopefully the 242 merge will fix it, though :)
[18:16] <santa_> ddstreet: interesting. nope, I didn't check dbus thing. iirc I just checked the journal but I didn't see any ugly thing
[18:17] <santa_> in any case if the 242 merge doesn't fix it I would be glad to re-check with your help
[18:17] <santa_> I'm just a plain user wrt systemd XD
[21:13] <rbasak> Skuggen: mysql-8.0 FTBFS. Looks like some openssl changes since the PPA build. Please could you take a look?
[21:13] <rbasak> I don't know if it would be better to patch or bump to the latest microrelease if there's a fix upstream.
[21:13] <rbasak> If it's not difficult I think cherry-picking a patch would be less disruptive, and we can update later? What do you think?