[08:35] I forgot [08:35] @pilot in === ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: juliank [09:26] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [11:07] @pilot out === ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A [15:50] juliank: hmm I just noticed you sponsored the rsyslog merge; I guess my comments about not adding sleeps in the autopkgtest got lost when the MPs were reset? [15:51] vorlon: the MPs were deleted, but xypron told me that you didn't like it, but I didn't see that as a priority [15:51] hmm [15:51] adding 'sleep' commands is always a bad hack [15:51] vorlon: even the tests that are part of rsyslog upstream have sleep [15:52] vorlon: sure it would be nice to fix properly, and it needed a retry anyhow to build but it's better than not having the logcheck fix [15:52] that just tells me upstream also has a bad test philosophy ;) [15:52] They have a comment about slow test machines. [15:53] I guess they made a bad experience like I did. [15:53] my podman is super slow for some reason now, very weird, but everything will time out in that :D [15:53] Though my machine is not slow. Ryzen 5950 [15:53] right but the systemd unit stop command should be synchronous and the fact that it's not is a bug, this should at least be documented as a bug report instead of simply hacked around [15:55] What is the guarantee of systemd stop: The process with the PID is stopped. I did not analyze which output mechanism is used to write to file. [15:56] it should be that all processes associated with the unit are stopped, not just the leader process [15:56] E.g. does the output queue run in the same process? [20:42] hi.. have seen some pkgs of version 5.4-1ubuntuX.Y what are X and Y in the version? [20:45] xmenschool: X and Y are fairly arbitrary, but usually X is what the package was when the Ubuntu release was released and Y is an incremental stable release update. [20:45] !sru [20:45] Stable Release Update information is at https://wiki.ubuntu.com/StableReleaseUpdates [20:45] X is basically an upload number.