Your message dated Sun, 22 Dec 2024 22:06:52 +0000
with message-id <[email protected]>
and subject line Bug#1090917: fixed in python-requests-futures 1.0.2-1
has caused the Debian Bug report #1090917,
regarding python-requests-futures: please update debian/watch for the new PyPi 
naming policy
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.)


-- 
1090917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1090917
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python-requests-futures
Version: 1.0.1-1
Severity: normal

Dear Maintainer,

Due to changes in PyPi ecosystem;
the current debian/watch cannot detect new releases.

https://pypi.debian.net/requests-futures
 requests-futures-0.9.9.tar.gz
 requests-futures-1.0.0.tar.gz
 requests-futures-1.0.1.tar.gz
 requests_futures-1.0.2.tar.gz

It's only a matter of replacing a '-' with a '_'.

Greetings

Alexandre

-----

“In distribution names, any run of -_. characters (HYPHEN-MINUS, LOW LINE and
FULL STOP) should be replaced with _ (LOW LINE), and uppercase characters
should be replaced with corresponding lowercase ones.”

This link is for binary distributions, but there is a separate specification
for source distributions [2] which says that rules are the same.

[1]: 
https://packaging.python.org/en/latest/specifications/binary-distribution-format/#escaping-and-unicode
[2]: 
https://packaging.python.org/en/latest/specifications/source-distribution-format/#source-distribution-file-name

--- End Message ---
--- Begin Message ---
Source: python-requests-futures
Source-Version: 1.0.2-1
Done: Sebastian Ramacher <[email protected]>

We believe that the bug you reported is fixed in the latest version of
python-requests-futures, 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.
Sebastian Ramacher <[email protected]> (supplier of updated 
python-requests-futures 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: SHA512

Format: 1.8
Date: Sun, 22 Dec 2024 22:57:14 +0100
Source: python-requests-futures
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher <[email protected]>
Changed-By: Sebastian Ramacher <[email protected]>
Closes: 1090917
Changes:
 python-requests-futures (1.0.2-1) unstable; urgency=medium
 .
   * New upstream version 1.0.2
   * debian/watch: Search for new versions.
     Thanks to Alexandre Detiste (Closes: #1090917)
   * debian/control:
     - Bump Standards-Version
     - Bump debhelper compat to 13
     - Set RRR: no
   * debian/: Switch to dh-sequence-python3
Checksums-Sha1:
 22db5d199404e144d34d098fafcb47210c75ee46 1487 
python-requests-futures_1.0.2-1.dsc
 23818d1134f72d41eff7542a513955e55f29e91f 8856 
python-requests-futures_1.0.2.orig.tar.xz
 9a19505f48eeb66151eed4e24bbc6b936be256f9 2640 
python-requests-futures_1.0.2-1.debian.tar.xz
 4d1387b080533d4c1c4f9a11628fd19f1ff6e97f 7611 
python-requests-futures_1.0.2-1_source.buildinfo
Checksums-Sha256:
 61f21fa64e744cb2726b229868da0426a26aeb6f0197050c0b1c46bb5591e91f 1487 
python-requests-futures_1.0.2-1.dsc
 c6a5748f381ba5f9930f74d8d831bb944fa2e3ea27cacc15118289da2f76f261 8856 
python-requests-futures_1.0.2.orig.tar.xz
 2ca9cba4e4848ee3a5c8a86e5ba8f0e6efb9ed56da3f2ec81761f2f24d2f0285 2640 
python-requests-futures_1.0.2-1.debian.tar.xz
 c9d4f5347b624ddc875128582c5820c399a587a407e2268fe96787d6e69a6340 7611 
python-requests-futures_1.0.2-1_source.buildinfo
Files:
 14cd07be113f33decb1871208333f7bf 1487 python optional 
python-requests-futures_1.0.2-1.dsc
 da28a1ea7ecc2d34da9cbcc51529043a 8856 python optional 
python-requests-futures_1.0.2.orig.tar.xz
 3b0631f8d555a325229145086cdb5448 2640 python optional 
python-requests-futures_1.0.2-1.debian.tar.xz
 63ad3f2607d31a39b2d0d96790a0d11a 7611 python optional 
python-requests-futures_1.0.2-1_source.buildinfo

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

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZ2iLsgAKCRAhk2s2YA/N
iaRsAQD4f6it27kzcchQORK3kcXxOPUaW0pidhObW2JA+BeihQEAtXdzMdakIlAE
Cd7IeOzaH9j152u9EiRry+XlzgAX9AQ=
=OcO2
-----END PGP SIGNATURE-----

Attachment: pgpUwBBOCSwLB.pgp
Description: PGP signature


--- End Message ---

Reply via email to