[07:43] tumbleweed, I don't understand where that list of paths comes from [08:22] is -backports enabled by default on ubuntu server and ubuntu desktop? [08:25] on impish, yes. [12:23] 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" === cpaelzer_ is now known as cpaelzer [14:35] 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] jdstrand, phalor is in #ubuntu 🙂 [15:30] Can a core dev please retry the following autopkgtests for me? [15:30] https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=ppc64el&package=casync&trigger=systemd%2F249.11-0ubuntu3 [15:30] https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=arm64&package=systemd&trigger=systemd%2F249.11-0ubuntu3 [15:30] https://autopkgtest.ubuntu.com/request.cgi?release=jammy&arch=armhf&package=tang&trigger=systemd%2F249.11-0ubuntu3 [15:30] Thanks in advance. [15:31] enr0n: looking [15:33] enr0n: . [15:34] ginggs: thanks! === chrisccoulson_ is now known as chrisccoulson [16:50] LocutusOfBorg: FWIW, a bisect got me to https://github.com/python/cpython/commit/af1d64d9f7a7cf673279725fdbaf4adcca51d41f as the culprit [16:50] Commit af1d64d in python/cpython "bpo-42260: Main init modify sys.flags in-place (GH-23150)" [16:51] so cpython regression? [16:52] the embedding in esys-particle looks very straight-forward, so it's unlikely to be a bug there, but more digging ahead :) [16:52] tumbleweed, what about trying to add a call to _PySys_UpdateConfig in esys-particle? [16:54] 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] if almost all code using cpython failed, we'd have noticed it by now [17:02] it's something a lot more subtle === mfo_ is now known as mfo