Your message dated Fri, 02 Dec 2022 22:04:58 +0000
with message-id <e1p1e9s-00baek...@fasolo.debian.org>
and subject line Bug#1007517: fixed in libdatapager-perl 0.01-2.3
has caused the Debian Bug report #1007517,
regarding libdatapager-perl: please consider upgrading to 3.0 source format
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.)


-- 
1007517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdatapager-perl
Version: 0.01-2.2
Severity: wishlist
Tags: bookworm sid
Usertags: format1.0 format1.0-nkp-nv

Dear maintainer,

This package is among the few (1.9%) that still use source format 1.0 in
bookworm.  Please upgrade it to source format 3.0, as (1) this format has many
advantages, as documented in https://wiki.debian.org/Projects/DebSrc3.0 ; (2)
this contributes to standardization of packaging practices.

Please note that this is also a sign that the packaging of this software
could maybe benefit from a refresh. It might be a good opportunity to
look at other aspects as well.

It was noticed in https://lists.debian.org/debian-devel/2022/03/msg00096.html
that the conversion for this package is likely trivial, and builds bit-by-bit
identical binary packages.


This mass bug filing was discussed on debian-devel@:
https://lists.debian.org/debian-devel/2022/03/msg00074.html

Thanks

Lucas

--- End Message ---
--- Begin Message ---
Source: libdatapager-perl
Source-Version: 0.01-2.3
Done: Bastian Germann <b...@debian.org>

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

Debian distribution maintenance software
pp.
Bastian Germann <b...@debian.org> (supplier of updated libdatapager-perl 
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: Fri, 02 Dec 2022 22:57:14 +0100
Source: libdatapager-perl
Architecture: source
Version: 0.01-2.3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry E. Oboukhov <un...@debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 1007517
Changes:
 libdatapager-perl (0.01-2.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert to 3.0 source format. (Closes: #1007517)
Checksums-Sha1:
 64b403126a6530b4930e7c5875a07c11b15a750c 1657 libdatapager-perl_0.01-2.3.dsc
 4617fbb983e882e11198757b5315c39ba0efd7ab 1628 
libdatapager-perl_0.01-2.3.debian.tar.xz
 fe5e4582d3ebf5e3bef24c4bfe7ab1f5c403b2cc 5593 
libdatapager-perl_0.01-2.3_source.buildinfo
Checksums-Sha256:
 f34977307ed88661a11614fc5638eaa6acdbd4dfdda8d0895b768429a2a30512 1657 
libdatapager-perl_0.01-2.3.dsc
 941d24568ec6faa63c4ca6da7d9f19b125a9b53627e13b422cceceda445e6507 1628 
libdatapager-perl_0.01-2.3.debian.tar.xz
 ad58cdf78da0b28df228aa715e1ad94b5d9377eb77d425cfcadc642cdbaa5cd2 5593 
libdatapager-perl_0.01-2.3_source.buildinfo
Files:
 3f72ae0c0e04877c3f0f4a11221f725a 1657 perl optional 
libdatapager-perl_0.01-2.3.dsc
 8e407b816ef7e766d1bf0d960c3c0c67 1628 perl optional 
libdatapager-perl_0.01-2.3.debian.tar.xz
 74b0327902b4425b43d71f4262a46a9b 5593 perl optional 
libdatapager-perl_0.01-2.3_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOKdOUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAGtC/9WnQ6o8zMCKEZNLd0w2mXZtLG23WViLyEX
bzDAdlfRGIpmlBJYOhmsXxpgg1AGvTLF/luJmOz/zhclH0Yrhi1pkXSsHrXsqCJl
RmHdMpE/x5V1/vWA83qWs+7RDSYa3yP8Z8Z0i5ki82gHx5/vJDc4sXub5o+LyvkS
Ko+xvTyUAi6biiZaY4nXqIOCpcy7eWM6Kbwt8/8QkQWwfUhnqpphpm8NlmR7AZcl
0eFj+rRoSs04qKdF+Coe9ErW2miHXqr/MyhTuI6YOyZ0UJEJv5nSBpYyqqMfoAAh
+seBbKzPfZ6puZ9ScPgDzYFJLIfcbNu4RBmhDu/kjCmTgn3sSzN7p7vDLv8owAbr
Zi55aFncYlNnkZxGS/ufYSWSLl89PSeBG7NoP92iwSptJyeHTilXUJfmm7WJrTCJ
UvLHcRaHXz+RazVcX1YktV5MWU5d5I3YxOY5kQ1Sv8HnJIueim6WWwFRLldvScVm
QJYUajlxo+EgSezxgVZO1TTnsDHha6Q=
=zSYy
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to