Your message dated Wed, 07 Oct 2020 09:35:59 +0000
with message-id <[email protected]>
and subject line Bug#971212: fixed in prometheus 2.20.0+ds-2
has caused the Debian Bug report #971212,
regarding prometheus: FTBFS: dh_auto_test fails
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 [email protected]
immediately.)
--
971212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971212
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: prometheus
Version: 2.20.0+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === RUN TestNewHTTPWithServerName
> 2020/09/27 11:19:57 http: TLS handshake error from 127.0.0.1:46428: remote
> error: tls: bad certificate
> target_test.go:306: Get "https://127.0.0.1:41891": x509: certificate
> relies on legacy Common Name field, use SANs or temporarily enable Common
> Name matching with GODEBUG=x509ignoreCN=0
> --- FAIL: TestNewHTTPWithServerName (0.00s)
The full build log is available from:
http://qa-logs.debian.net/2020/09/26/prometheus_2.20.0+ds-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: prometheus
Source-Version: 2.20.0+ds-2
Done: Shengjing Zhu <[email protected]>
We believe that the bug you reported is fixed in the latest version of
prometheus, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shengjing Zhu <[email protected]> (supplier of updated prometheus 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 07 Oct 2020 17:16:33 +0800
Source: prometheus
Architecture: source
Version: 2.20.0+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <[email protected]>
Changed-By: Shengjing Zhu <[email protected]>
Closes: 971212
Changes:
prometheus (2.20.0+ds-2) unstable; urgency=medium
.
* Team upload.
* Backport patch to fix tests with go1.15 (Closes: #971212)
Checksums-Sha1:
136b95c031deaa224b6928f42a95348d34845556 3258 prometheus_2.20.0+ds-2.dsc
531ffec300e4f440c793e5ce4d10d34e47d61ca4 36104
prometheus_2.20.0+ds-2.debian.tar.xz
d5d2dc2e67331d806c8aa93cb55fbcdbf089f3cc 19529
prometheus_2.20.0+ds-2_amd64.buildinfo
Checksums-Sha256:
2a7c42f96983344c34200917b7921c8cc7baef3dce342dd889f18b98684d8975 3258
prometheus_2.20.0+ds-2.dsc
c9c2c063676f11dd89db5dd9e9ec1f8c99a65e86d3518f63628b9afa4a483187 36104
prometheus_2.20.0+ds-2.debian.tar.xz
2a3cbfd19b05e014ac43581351fb577279902abeb0549d8654867cb8f5658064 19529
prometheus_2.20.0+ds-2_amd64.buildinfo
Files:
eecf879f2bd87e1fd6f7c299ce2ab24b 3258 net optional prometheus_2.20.0+ds-2.dsc
91e415973ae95cfa9e5ba9bb93e6a0e5 36104 net optional
prometheus_2.20.0+ds-2.debian.tar.xz
ef0a5b73ec87c63087de300bf45a9a45 19529 net optional
prometheus_2.20.0+ds-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX32IXxAcemhzakBkZWJp
YW4ub3JnAAoJEMSFSjgY4LAWfksBAMsj2e2MgLXnRm5AJUDqCaAy6TyvjU6auKOb
g3d489/NAQDjbZRZIjkNyDAL/z5Pi5voyBkvrhWU2w1IJHST804QAA==
=I3TI
-----END PGP SIGNATURE-----
--- End Message ---
