Your message dated Thu, 04 Apr 2024 21:51:23 +0000
with message-id <e1rsuzt-00bmv7...@fasolo.debian.org>
and subject line Bug#1007071: fixed in lockfile-progs 0.1.19+nmu1
has caused the Debian Bug report #1007071,
regarding lockfile-progs: 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.)
--
1007071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lockfile-progs
Version: 0.1.19
Severity: wishlist
Tags: bookworm sid
Usertags: format1.0 format1.0-kp-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.
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: lockfile-progs
Source-Version: 0.1.19+nmu1
Done: Bastian Germann <b...@debian.org>
We believe that the bug you reported is fixed in the latest version of
lockfile-progs, 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 lockfile-progs 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: Mon, 25 Mar 2024 20:52:38 +0000
Source: lockfile-progs
Architecture: source
Version: 0.1.19+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning <r...@defaultvalue.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 1007071
Changes:
lockfile-progs (0.1.19+nmu1) unstable; urgency=medium
.
* Non-maintainer upload.
* d/copyright: Convert to machine-readable format.
* Convert to source format 3.0. (Closes: #1007071)
Checksums-Sha1:
ddc25628eac2ecefc48186dbeb17db4f63e45c16 1321 lockfile-progs_0.1.19+nmu1.dsc
11fd3b4a27104f050382de1f45cf984f214fe65a 14156
lockfile-progs_0.1.19+nmu1.tar.xz
e8323465e3b99e2bb524924f06aeec8acbfabbf2 6205
lockfile-progs_0.1.19+nmu1_source.buildinfo
Checksums-Sha256:
f2514a5e5482945944477c0ce2277e477e8c5d06a7163573b97ce6ed895ef98a 1321
lockfile-progs_0.1.19+nmu1.dsc
a176942f749f034dc42f56798b7aa4636d904b79410ca65c052b63cf3e53dcc2 14156
lockfile-progs_0.1.19+nmu1.tar.xz
d684df4801339e99483ea58d5929bc1e966bfcec1f20f6dd2293e4c4af7c53e3 6205
lockfile-progs_0.1.19+nmu1_source.buildinfo
Files:
9f302fe7fded56d439cedff18aa511d9 1321 misc optional
lockfile-progs_0.1.19+nmu1.dsc
f257690852b9f3f4df1417ff2c54584c 14156 misc optional
lockfile-progs_0.1.19+nmu1.tar.xz
e1f94a135e69280a750d41fb5d3f6019 6205 misc optional
lockfile-progs_0.1.19+nmu1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYB5sUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFEFKDADcc8ve7gd/BcUruNzCP8BSFIqS1CWNYEnk
A07u3WyKgPr7DNwIewoEDi4W8+RF7vMz4qmjyKFZ78ks1a0CZC1gylA614P5bgmR
bF6qDigO/jl1EoOq3gzdYv5GEKt/4xiVm8mBHF4WJBMYUbj3E2EFSTsv73pRKDh4
6oWR2VLHxVkVRxxRkjWrvgQr5vP22UvAimjYePTnJuhtI+gSkoeKWQCTGc58R4FX
6APJrv7X1W4zBvLoKHGlDvGMfjUaM1KFHIwOlD+dnz8xvFUTSWDJfsChsmaQDbPT
1xvVEdCvd55/3UhghgXnGJq5U3EM3ao0QRPJr1+A9q+I1dcLMBT7X37V0QPLwUjy
pkDh9f4QD8HDb71AB2deICuk9XAbxEmXqLzF5VwqotWOOYIFW2OqkK3VupNzOlH1
nmK/uQKQ/AVUzi7UGMMFvdHlqkD0ykRiLDHlL+lcQIT2V8ejObj2mCc8IQ4G4TUf
TM6PnILw3vTR/AxODjpb4CbMri614ZQ=
=LgWB
-----END PGP SIGNATURE-----
pgpGbcrRD3KCb.pgp
Description: PGP signature
--- End Message ---
