Your message dated Thu, 12 Dec 2024 17:19:14 +0000
with message-id <[email protected]>
and subject line Bug#1018341: fixed in django-cte 1.3.3-2
has caused the Debian Bug report #1018341,
regarding django-cte: build-depends on python3-nose or uses it for autopkgtest
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.)
--
1018341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018341
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: django-cte
Version: 1.2.1-2
User: [email protected]
Usertags: nose-rm
Dear Maintainer,
Your package still uses nose [1], which is an obsolete testing framework for
Python, dead and unmaintained since 2015 [2][3].
If you received this bug report, it means that your package either has a
build-dependency on python3-nose or uses that package in debian/tests/control.
If that is not the case, please reply and CC me explicitly.
Please port your package to one of the alternatives: nose2 [4], pytest [5]
or unittest from Python standard library [6].
There is a script called nose2pytest [7] which can assist with migrating from
nose to pytest.
This mass bug filing was discussed on debian-devel in [8].
[1]: https://tracker.debian.org/pkg/nose
[2]: https://github.com/nose-devs/nose/commit/0f40fa995384afad
[3]: https://pypi.org/project/nose/#history
[4]: https://docs.nose2.io/en/latest/
[5]: https://docs.pytest.org/en/latest/
[6]: https://docs.python.org/3/library/unittest.html
[7]: https://github.com/pytest-dev/nose2pytest
[8]: https://lists.debian.org/debian-devel/2022/08/msg00184.html
--
Dmitry Shachnev
--- End Message ---
--- Begin Message ---
Source: django-cte
Source-Version: 1.3.3-2
Done: Colin Watson <[email protected]>
We believe that the bug you reported is fixed in the latest version of
django-cte, 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.
Colin Watson <[email protected]> (supplier of updated django-cte 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: Thu, 12 Dec 2024 16:52:27 +0000
Source: django-cte
Architecture: source
Version: 1.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1018341
Changes:
django-cte (1.3.3-2) unstable; urgency=medium
.
* Team upload.
* Use pytest instead of nose (closes: #1018341).
* Switch to autopkgtest-pkg-pybuild.
* Use pybuild-plugin-pyproject.
Checksums-Sha1:
76884ee2691c629236ab3508c8b8d9673234b36a 2236 django-cte_1.3.3-2.dsc
93e8b4f59eafa891feea993339f3873f40325674 4220 django-cte_1.3.3-2.debian.tar.xz
Checksums-Sha256:
e5aa4d4bf4c7bfbadaa74d50d9de02fd68b8134204fb68c970a04c8597b2cdc8 2236
django-cte_1.3.3-2.dsc
b9571eaec98fe328c9c98a14cd9ee41d08d93c30f0f9c0951e104e617587c36b 4220
django-cte_1.3.3-2.debian.tar.xz
Files:
ffc98f35c98fabb652ba3cc39808cdcb 2236 python optional django-cte_1.3.3-2.dsc
a6810defcb0ad1ac90359408603b5b3e 4220 python optional
django-cte_1.3.3-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmdbFg4ACgkQOTWH2X2G
UAvT3g//dHwY96c/WH22fiW4WmpTiB8NULKeNW2/vCwYzx8i7Zq0G4IpMbhaxlOd
uIw6seD/8p5DIpS07N15kdUaSCbzvLMJyDnN9+10kJNv6h4FubNNXMMdIhAjYzj/
OCGlNldplW2foHVLP8qiWIUl1Yw2+FdWYnl0B31X8V6Ygfw2HfRc6a1HSgaMRYza
C2NfUe2HUTLkmdFhUeOnTTDFWliDuKNCewMBFaLrLw0Shcw1dHDxt6Xeq5mU4v57
AWEAR2eRtWCrQ7BAKaBtCL8hX1vxkm5lWEZnqzuBT89cDxIRAkdYHWXrZJRoLjBS
n8Vgv3R4MoM6NfHtQ35KB6etmfr9dJVhbKbsrsa6XkOP1bTDSckLoJjvT9xmgBt5
bzjjcVcYL2fMPXF3sutnishauUgwApEbBmi7VHu9gQwGnbK79ShvjznXc+wdazVy
UuSslq/TQg7fglH7oLtdjQ42WnKDBALiwh0gQxANdZljMynaQQAEIwBe5rNYgNoz
SHg7zMRyvDfLt+z0r0X5aLGZD8Yycr+cHcy23/Ka3vSea//Nkjfh+hVX8HtsFNN8
uqsBEqSHZh0uDShzj589tjp60AWk0ZltfjBxc2RaQRggkvbDUKLtDoxJAZyq+1Ri
eC/EJWtGm0Wl7yhR54VAWBpqUOt/KFZpiZOhh+VPvep2o5FPiQA=
=axJA
-----END PGP SIGNATURE-----
pgpSeyWuAgoqz.pgp
Description: PGP signature
--- End Message ---
