[07:43] <LocutusOfBorg> tumbleweed, I don't understand where that list of paths comes from
[08:22] <toabctl> is -backports enabled by default on ubuntu server and ubuntu desktop?
[08:25] <oerheks> on impish, yes.
[12:23] <phalor> is this a bug? (ufw allow in on ens3 proto tcp from any port any to 192.168.2.1 port 25) says "ERROR: Could not find protocol"
[14:35] <jdstrand> if phalor returns, removing 'port any' makes it work. 'any' isn't a valid port (the error could be clearer on that point; it isn't referring to 'proto tcp', it is referring to the lookup in /etc/services)
[15:08] <ogra> jdstrand, phalor is in #ubuntu 🙂
[15:30] <enr0n> Can a core dev please retry the following autopkgtests for me?
[15:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=ppc64el&package=casync&trigger=systemd%2F249.11-0ubuntu3
[15:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=arm64&package=systemd&trigger=systemd%2F249.11-0ubuntu3
[15:30] <enr0n> https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=armhf&package=tang&trigger=systemd%2F249.11-0ubuntu3
[15:30] <enr0n> Thanks in advance.
[15:31] <ginggs> enr0n: looking
[15:33] <ginggs> enr0n: .
[15:34] <enr0n> ginggs: thanks!
[16:50] <tumbleweed> LocutusOfBorg: FWIW, a bisect got me to https://github.com/python/cpython/commit/af1d64d9f7a7cf673279725fdbaf4adcca51d41f as the culprit
[16:51] <LocutusOfBorg> so cpython regression?
[16:52] <tumbleweed> the embedding in esys-particle looks very straight-forward, so it's unlikely to be a bug there, but more digging ahead :)
[16:52] <LocutusOfBorg> tumbleweed, what about trying to add a call to _PySys_UpdateConfig in esys-particle?
[16:54] <LocutusOfBorg> tumbleweed, do you agree that almost all the code using cpython should fail? or maybe they do not fail because esys-particle is installed into a custom old python directory?
[17:02] <tumbleweed> if almost all code using cpython failed, we'd have noticed it by now
[17:02] <tumbleweed> it's something a lot more subtle