Public bug reported:

Currently, on plucky, a new version of privoxy (4.0.0) is blocked in 
plucky-proposed
because of failing autopkgtests.

The failing test is check-ssl, this test has been added during the transition 
of the package
from version 3.0.34 (oracular) to 4.0.0.

This test runs fine on Debian.

Here is the test log:
---

188s autopkgtest [11:11:44]: test check-ssl: preparing testbed
188s Reading package lists...
188s Building dependency tree...
188s Reading state information...
188s Starting pkgProblemResolver with broken count: 0
188s Starting 2 pkgProblemResolver with broken count: 0
189s Done
189s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
190s autopkgtest [11:11:46]: test check-ssl: [-----------------------
190s Generate SSL key-pair
190s Generate privoxy config
190s Starting privoxy on port 8119
191s 2025-02-03 11:11:47: Requesting pages from badssl.com with various 
certificate problems. This will only work if Privoxy has been configured 
properly and can reach the Internet.
191s 2025-02-03 11:11:47: Requesting https://expired.badssl.com/
191s 2025-02-03 11:11:47: Ooops. We expected status code 403, but received: 503.
191s 2025-02-03 11:11:47: Requesting https://wrong.host.badssl.com/
192s 2025-02-03 11:11:48: Ooops. We expected status code 403, but received: 503.
192s 2025-02-03 11:11:48: Requesting https://self-signed.badssl.com/
192s 2025-02-03 11:11:48: Ooops. We expected status code 403, but received: 503.
192s 2025-02-03 11:11:48: Requesting https://untrusted-root.badssl.com/
192s 2025-02-03 11:11:48: Ooops. We expected status code 403, but received: 503.
192s 2025-02-03 11:11:48: Requesting https://no-common-name.badssl.com/
192s 2025-02-03 11:11:48: Ooops. We expected status code 403, but received: 503.
192s 2025-02-03 11:11:48: Requesting https://no-subject.badssl.com/
193s 2025-02-03 11:11:49: Ooops. We expected status code 403, but received: 503.
193s 2025-02-03 11:11:49: Requesting https://incomplete-chain.badssl.com/
193s 2025-02-03 11:11:49: Ooops. We expected status code 403, but received: 503.
193s 2025-02-03 11:11:49: There were 7 requests that did not result in status 
code 403!
193s check https://www.howsmyssl.com
194s check TLS version
194s ERROR: TLS-Version is 
194s check values, that should be false
194s ERROR: beast_vuln is not false but 
194s ERROR: tls_compression_supported is not false but 
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s ERROR: unknown_cipher_suite_supported is not false but 
194s check values, that should be true
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s ERROR: ephemeral_keys_supported is not true but 
194s ERROR: session_ticket_supported is not true but 
194s check insecure cipher suites
194s ERROR: insecure_cipher_suites is not empty: 
194s check overall rating
194s ERROR: Rating is 
194s Stopping privoxy on port 8119
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s jq: parse error: Invalid numeric literal at line 1, column 10
194s autopkgtest [11:11:50]: test check-ssl: -----------------------]
195s autopkgtest [11:11:51]: test check-ssl:  - - - - - - - - - - results - - - 
- - - - - - -
195s check-ssl            FAIL non-zero exit status 1

** Affects: privoxy (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: update-excuse

** 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/2097351

Title:
  autopkgtest failures : check-ssl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/privoxy/+bug/2097351/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to