This bug was fixed in the package privoxy - 3.0.34-5
---
privoxy (3.0.34-5) unstable; urgency=medium
* d/tests/privoxy-regression-test: wait for privoxy to start up.
-- Roland Rosenfeld Wed, 15 May 2024 20:23:18
+0200
** Changed in: privoxy (Ubuntu)
Status: New => Fix Re
Thanks Roland. I tried 3.0.34-5 and I can confirm it fixes the issue!
Syncing now (LP: #2071115).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059344
Title:
3.0.34-3ubuntu1 autopkgtest failure
To
3.0.34-5 (already in Debian) should fix this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059344
Title:
3.0.34-3ubuntu1 autopkgtest failure
To manage notifications about this bug go to:
ht
In the meantime I can reproduce the issue on a Debian unstable system.
As far as I can see,
https://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff;h=19d7684c
fixes this issue.
I'll release a 3.0.34-4 with this fix to Debian soon.
--
You received this bug notification because you are a member
The attachment "artifacts-log.patch" seems to be a patch. If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.
[This is an automated message performed by a Launchpad user owned by
~brian-mu
At the moment I don't have an idea, what's going wrong in the Ubuntu
autopkgtest here.
But it looks as privoxy does not listen on 8119 as expected but fails and dies
(the message, that privoxy cannot be killed because there is no such process in
line 61 of privoxy-regression-test also leads to t
At the moment I don't have an idea, what's going wrong in the Ubuntu
autopkgtest here.
But it looks as privoxy does not listen on 8119 as expected but fails and dies
(the message, that privoxy cannot be killed because there is no such process in
line 61 of privoxy-regression-test also leads to t