Your message dated Tue, 07 Sep 2021 13:03:30 +0000
with message-id <e1mnal8-0004xs...@fasolo.debian.org>
and subject line Bug#993534: fixed in dogtag-pki 10.10.6-1
has caused the Debian Bug report #993534,
regarding 389-ds-base breaks dogtag-pki autopkgtest: CA spawn failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
993534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 389-ds-base, dogtag-pki
Control: found -1 389-ds-base/1.4.4.16-1
Control: found -1 dogtag-pki/10.10.2-3
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of 389-ds-base the autopkgtest of dogtag-pki fails
in testing when that autopkgtest is run with the binary packages of
389-ds-base from unstable. It passes when run with only packages from
testing. In tabular form:

                       pass            fail
389-ds-base            from testing    1.4.4.16-1
dogtag-pki             from testing    10.10.2-3
all others             from testing    from testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of 389-ds-base to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=389-ds-base

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dogtag-pki/14986372/log.gz

autopkgtest [09:10:45]: test pkispawn: [-----------------------
>>>> IP address is 192.168.122.100
>>>> Hostname was:
>>>> /etc/hosts now has:
127.0.0.1       localhost
::1             localhost ip6-localhost ip6-loopback
ff02::1         ip6-allnodes
ff02::2         ip6-allrouters

192.168.122.100 autopkgtest.debci autopkgtest
Starting installation...
Completed installation for pki-tomcat
Notice: Trust flag u is set automatically if the private key is present.
/usr/lib/python3/dist-packages/urllib3/connection.py:455:
SubjectAltNameWarning: Certificate for autopkgtest.debci has no
`subjectAltName`, falling back to check for a `commonName` for now. This
feature is being removed by major browsers and deprecated by RFC 2818.
(See https://github.com/urllib3/urllib3/issues/497 for details.)
  warnings.warn(
Loading deployment configuration from debian/tests/deploy.cfg.
Installation log: /var/log/pki/pki-ca-spawn.20210902091106.log
Installing CA into /var/lib/pki/pki-tomcat.

Installation failed:
<!doctype html><html lang="en"><head><title>HTTP Status 404 – Not
Found</title><style type="text/css">body
{font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b
{color:white;background-color:#525D76;} h1 {font-size:22px;} h2
{font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a
{color:black;} .line
{height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP
Status 404 – Not Found</h1><hr class="line" /><p><b>Type</b> Status
Report</p><p><b>Message</b> The requested resource
[&#47;ca&#47;admin&#47;ca&#47;getStatus] is not
available</p><p><b>Description</b> The origin server did not find a
current representation for the target resource or is not willing to
disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat/9.0.43
(Debian)</h3></body></html>

Please check the CA logs in /var/log/pki/pki-tomcat/ca.
>>>> CA spawn failed:
autopkgtest [09:12:24]: test pkispawn: -----------------------]

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 10.10.6-1
Done: Timo Aaltonen <tjaal...@debian.org>

We believe that the bug you reported is fixed in the latest version of
dogtag-pki, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Timo Aaltonen <tjaal...@debian.org> (supplier of updated dogtag-pki package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 07 Sep 2021 14:25:32 +0300
Source: dogtag-pki
Built-For-Profiles: noudeb
Architecture: source
Version: 10.10.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team <pkg-freeipa-de...@alioth-lists.debian.net>
Changed-By: Timo Aaltonen <tjaal...@debian.org>
Closes: 991173 991174 991665 993534
Changes:
 dogtag-pki (10.10.6-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #993534)
     - CVE-2021-3551 (Closes: #991665)
   * CVE-2021-20179.diff: Dropped, upstream.
   * Refresh patches.
   * JNA requirement got dropped, update packaging for it.
   * pki-server.postinst: Remove world access from existing installation
     logs.
   * control: Drop velocity from depends, it's not used anymore.
   * control: Drop libcommons-httpclient-java from depends, not used
     anymore.
   * control: Bump libjss dependency.
   * pki-tps.install: Updated.
   * tests: Add iproute2 to test depends. (Closes: #991173)
   * tests: Add isolation-container to test restrictions. (Closes:
     #991174)
Checksums-Sha1:
 a8f1023e9f5c785f7b6c9ae8337e24b5b2b20fd0 3857 dogtag-pki_10.10.6-1.dsc
 35a14e241a3ac52cd610b8b1ac0b5316ae057317 6937360 dogtag-pki_10.10.6.orig.tar.xz
 ca20413ff89673d310008e5d7bc241e921d594a2 33156 
dogtag-pki_10.10.6-1.debian.tar.xz
 844a5978d433c2d6a4ac3e966c3d4e55bcfc228b 15129 
dogtag-pki_10.10.6-1_source.buildinfo
Checksums-Sha256:
 e20473ffd3b8ca81a3242303e7b515802c2093c74e176ce09278625ad3cea935 3857 
dogtag-pki_10.10.6-1.dsc
 ab456046336e00957040663c5e5f12fcd4a461958c716d521e9087b20ac8f5f9 6937360 
dogtag-pki_10.10.6.orig.tar.xz
 e6489bbb179523b12a912f1a67167fec8dd5bf5d2b5af0f292bcb7d2394385e7 33156 
dogtag-pki_10.10.6-1.debian.tar.xz
 37ee4a1ef79d940dddd99e91358d1d4be421dc245a21dc2624124445e14c9ae2 15129 
dogtag-pki_10.10.6-1_source.buildinfo
Files:
 1c0b76e5f764b7c5477c29e7d12cbbbc 3857 java optional dogtag-pki_10.10.6-1.dsc
 68d328da8932f5675f7c2f027ed49634 6937360 java optional 
dogtag-pki_10.10.6.orig.tar.xz
 a0a84c11cc9ebfc30416370b8d875427 33156 java optional 
dogtag-pki_10.10.6-1.debian.tar.xz
 89d097428702dadc162d77e1282cba0b 15129 java optional 
dogtag-pki_10.10.6-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAmE3TPEACgkQy3AxZaiJ
hNxLbA//Yz/wnNrtwVlxJnE6hxZ3OLZ1UqIdKw+XoVjpjtSEXtaAXThN2aN7qLmI
SCjjHVqhNo6kFcz3BchAu0gbxjZRVfhB7oGny46JA1eGhNVS/Qsix9cL2PNLrvVE
IHLdoIfsBVcbc/jZG2L9CF5H854J//cj5Yf0IEoRZa5MVT5wOhLOtfStQyfHXCUl
b1HgIPuNd6XmolqhBfMPNFjBp41iXoPT3Y8bT1zyM3/tkaNr9XZm3+ZRAEo+YUBT
BxoRukV1tfys7awAbHhH5qvA37eKoYY5o0GquzgCW5t5HZJ+q+qshjqPeGs1nlR7
DBOtZRScLw6C/AQk+pkHPzDNNTwlXq+c8yy6nE03OmeAGIHxQHpTi7+4xKhPk2/i
rMuHIlwUGjWYa/bUNYNmfovysCWkzeoFH0Ribmsztb50jkPK+vbTGFGN6v/cbgwV
tM6e2H0RpyhgCzxSqagJ3Wpsh971xOnGdO+EMG6ZFC9oNt8Gx1S1MRQVeP0rSyOQ
tTaeZXkmbmm/EY03HiuSI2WygyX5vb39O5LN9o/7RRQckbYaLw01iBJmLd0MkBXJ
nHj87E9d57KIbsBudv5RlmhLXO8L+td27Gk1ZtnGMtX1Fez6522lnGoxKkdQrWFd
AkrFo/ktoSTlNMpJnBvh1VMrh9VXtlW3BGdt4pTda2JIW5IN3Eo=
=ej7f
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to