Your message dated Wed, 06 Jul 2022 19:04:15 +0000
with message-id <e1o9ajr-000ecd...@fasolo.debian.org>
and subject line Bug#1014481: fixed in junitparser 2.7.0-2
has caused the Debian Bug report #1014481,
regarding junitparser: autopkgtest regression on amd64; arm64; armhf; i386; 
ppc64el; s390x: pytest7 migration - deprecated pytest feature: -k-
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.)


-- 
1014481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: junitparser
Version: 2.7.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian-pyt...@lists.debian.org
Usertags: pytest7
User: debian...@lists.debian.org
Usertags: regression
Control: affects -1 src:pytest

Dear maintainer(s),

The latest version of pytest in unstable (7.1.2-2) seems to be breaking
the autopkgtests for this package. This regression currently keeps
pytest from migrating to testing.

You can find the CI logs here: https://ci.debian.net/packages/d/junitparser/

I had a closer look at the error logs and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: junitparser
Source-Version: 2.7.0-2
Done: Bastian Germann <b...@linutronix.de>

We believe that the bug you reported is fixed in the latest version of
junitparser, 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 1014...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <b...@linutronix.de> (supplier of updated junitparser 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: Wed, 06 Jul 2022 20:44:37 +0200
Source: junitparser
Architecture: source
Version: 2.7.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Bastian Germann <b...@linutronix.de>
Closes: 1014481
Changes:
 junitparser (2.7.0-2) unstable; urgency=medium
 .
   * Eliminate one more pytest -k- occurence (Closes: #1014481)
Checksums-Sha1:
 50c104dfa5a12dcf1011a321256e0ab8acbe7feb 2023 junitparser_2.7.0-2.dsc
 0b7da3ddfd05e9d17577eec5cbbf499bcc8f1f26 3352 junitparser_2.7.0-2.debian.tar.xz
 5e402e085524ed9287b3b22637b5be31e61a397b 6605 
junitparser_2.7.0-2_source.buildinfo
Checksums-Sha256:
 c97f594d3a85752db71b5728a5efd4e1a52aca1aacb4b9337826890b0c8f16e2 2023 
junitparser_2.7.0-2.dsc
 622ef46bf2d7334dbe026c4a70a09ab113f82474ea7c84b44e1e775353287585 3352 
junitparser_2.7.0-2.debian.tar.xz
 206c9eea1e987f99d04262770fb71d04a072a3d1142df77fb5eee3aa2e5d2cd2 6605 
junitparser_2.7.0-2_source.buildinfo
Files:
 03aa40a5d1d81be238446f6c83bc4fd4 2023 python optional junitparser_2.7.0-2.dsc
 cd1ca405f5d41c210784b1ddc957ad37 3352 python optional 
junitparser_2.7.0-2.debian.tar.xz
 8c5c85a59689fe6af496b8b85047f694 6605 python optional 
junitparser_2.7.0-2_source.buildinfo

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

iQHHBAEBCgAxFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmLF2K0THGJhZ2VAbGlu
dXRyb25peC5kZQAKCRAfXHqLRVZDFIT7C/sGo8c/S4RgkQ89IGVcunNp+FIreBL+
6ZfNeYE0CHGrdwF5ww2P1VGH7GR7APHT7HDhiG8RPD0TOBiMRn8IDebL1sCmpQgA
v2ht8S5Gz+l1I6gLJr1jokWH17lA6RvV+yCqSsKiLMSF+WQxlRjegULfM9GkksxN
JxEVe1CE3RhAavkZdvps0k7jiAkdLut7wInriCVO7QK7klAId1XDQSD9Ha9spdE9
pHUc9ozWlRfjtCVUvVzWkPB6B7lqifcVv6LjY42RVvuk/uxFmsLc432feRA+n06n
hJhTn/siYZdAz8bdVIVd6TrKUEt0fFFh/B4z030ddoYjfcCaIiZwubnO6/+h8Kmp
vWiKfQejnojjxNNwx5StjPzmHOcNs+YNdxb3c+oDbO0V8IaN5qJSjFObYTTAKRZY
sDUf4NGCTA6vIeiEq1iI2kognP61+LhkS+6+SG/JyEVECgf5yfGJsZuPhhoy5vB3
KcHIARNRwdNymAydYOMCAH4Z1uLmg29yxcg=
=dSpq
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to