Your message dated Sun, 01 May 2022 15:20:08 +0000
with message-id <e1nlbmm-00084d...@fasolo.debian.org>
and subject line Bug#1010428: fixed in twine 4.0.0-3
has caused the Debian Bug report #1010428,
regarding twine: autopkgtest needs update for new version of
python-readme-renderer: error message changed
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.)
--
1010428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: twine
Version: 4.0.0-2
Severity: serious
X-Debbugs-CC: python-readme-rende...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-readme-renderer
Dear maintainer(s),
With a recent upload of python-readme-renderer the autopkgtest of twine
fails in testing when that autopkgtest is run with the binary packages
of python-readme-renderer from unstable. It passes when run with only
packages from testing. In tabular form:
pass fail
python-readme-renderer from testing 35.0-1
twine from testing 4.0.0-2
all others from testing from testing
I copied some of the output at the bottom of this report. After a very
brief inspection, it seems the test captures an error message and
expects it to remain unchanged.
Currently this regression is blocking the migration of
python-readme-renderer to testing [1]. Of course, python-readme-renderer
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in python-readme-renderer was intended
and your package needs to update to the new situation.
If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from python-readme-renderer
should really add a versioned Breaks on the unfixed version of (one of
your) package(s). Note: the Breaks is nice even if the issue is only in
the autopkgtest as it helps the migration software to figure out the
right versions to combine in the tests.
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=python-readme-renderer
https://ci.debian.net/data/autopkgtest/testing/amd64/t/twine/21263820/log.gz
__________________________ test_fails_rst_no_content
___________________________
tmp_path =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_fails_rst_no_content0')
capsys = <_pytest.capture.CaptureFixture object at 0x7fe0218f5210>
caplog = <_pytest.logging.LogCaptureFixture object at 0x7fe0218f7eb0>
def test_fails_rst_no_content(tmp_path, capsys, caplog):
sdist = build_sdist(
tmp_path,
{
"setup.cfg": (
"""
[metadata]
name = test-package
version = 0.0.1
long_description = file:README.rst
long_description_content_type = text/x-rst
"""
),
"README.rst": (
"""
test-package
============
"""
),
},
)
assert check.check([sdist])
assert capsys.readouterr().out == f"Checking {sdist}: FAILED\n"
> assert caplog.record_tuples == [
(
"twine.commands.check",
logging.ERROR,
"`long_description` has syntax errors in markup "
"and would not be rendered on PyPI.\n",
),
]
E AssertionError: assert [('twine.comm...RST source.')] ==
[('twine.comm... on PyPI.\n')]
E At index 0 diff: ('twine.commands.check', 40,
'`long_description` has syntax errors in markup and would not be
rendered on PyPI.\nNo content rendered from RST source.') !=
('twine.commands.check', 40, '`long_description` has syntax errors in
markup and would not be rendered on PyPI.\n')
E Use -v to get the full diff
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: twine
Source-Version: 4.0.0-3
Done: Stefano Rivera <stefa...@debian.org>
We believe that the bug you reported is fixed in the latest version of
twine, 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 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stefano Rivera <stefa...@debian.org> (supplier of updated twine 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: Sun, 01 May 2022 11:05:13 -0400
Source: twine
Architecture: source
Version: 4.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <team+pyt...@tracker.debian.org>
Changed-By: Stefano Rivera <stefa...@debian.org>
Closes: 1010428
Changes:
twine (4.0.0-3) unstable; urgency=medium
.
* Patch: Support (and require) python3-readme-renderer (>= 35).
(Closes: #1010428)
* Drop unnecessary versioned Depends, we are now using
--accept-upstream-versions.
Checksums-Sha1:
d040db386f8c9583a16ff0acd77e78a512d13063 2064 twine_4.0.0-3.dsc
93f3228f69d38683d0e2a2744650c93825a63038 8688 twine_4.0.0-3.debian.tar.xz
2aeccd0db1ca05aa7fc847ff7da0c2e94aa40b75 8534 twine_4.0.0-3_source.buildinfo
Checksums-Sha256:
70391d9791d65b84642c6be8410818df497cc4d5eab78e199996d5b56f549f28 2064
twine_4.0.0-3.dsc
22964d92c3cf376ec3173946f99ade83e6d9c98c19a407b06b895bacb67c7cff 8688
twine_4.0.0-3.debian.tar.xz
a36e225e64fb7c61ad9470b095bcd4907d333b250038dab865e177e46e8bd799 8534
twine_4.0.0-3_source.buildinfo
Files:
a324d3d1d1f413f87760ed34c4bbebfa 2064 utils optional twine_4.0.0-3.dsc
9e3f70b96185ff051c77229948477e18 8688 utils optional
twine_4.0.0-3.debian.tar.xz
b736a9e159f28531f02494dec169623e 8534 utils optional
twine_4.0.0-3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCYm6hwhQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2PqmAP0aS9s7zm/J+nKYFj8aKRiRCtCTZDj+
/Nkuk1bP/QCe3wEAy2s+DCRX4j29ZQjmtOHoIOT5RE3IyOCoVmgPzTvNnAs=
=JBoq
-----END PGP SIGNATURE-----
--- End Message ---
