This was fixed in apparmor[1], and I see a new run passed already.
1. https://launchpad.net/ubuntu/+source/apparmor/4.1.0~beta1-0ubuntu5
** Changed in: squid (Ubuntu)
Status: New => Fix Released
** Changed in: python3-defaults (Ubuntu)
Status: New => Invalid
--
You received thi
Nothing to do in python-defaults, marking that invalid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095600
Title:
squid: autopkgtest failure with Python 3.13
To manage notifications about this b
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095600
Title:
squid: autopkgtest failure with Python 3.13
To manage notifications about this bug go to:
https://b
** Also affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095600
Title:
squid: autopkgtest f
This can be worked around in squid by adding python3-legacy-cgi as a
test dependency for the autopkgtest.
However, the failure is actually in the apparmor package, see LP:
#2095597
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -3,5 +3,5 @@
Restrictions: allow-stderr
Tests: squid
-
