[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1007547: marked as done (fwanalog: please consider upgrading to 3.0 source format)

Your message dated Mon, 29 Aug 2022 15:19:13 +0000
with message-id <E1oSgXh-003tpv-S9@fasolo.debian.org>
and subject line Bug#1007547: fixed in fwanalog 0.6.9-9
has caused the Debian Bug report #1007547,
regarding fwanalog: 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 owner@bugs.debian.org
immediately.)


-- 
1007547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007547
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: fwanalog
Version: 0.6.9-8
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: fwanalog
Source-Version: 0.6.9-9
Done: Bastian Germann <bage@debian.org>

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

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated fwanalog 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 29 Aug 2022 16:41:24 +0200
Source: fwanalog
Architecture: source
Version: 0.6.9-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1007547
Changes:
 fwanalog (0.6.9-9) unstable; urgency=medium
 .
   * QA upload.
   * d/copyright: Convert to machine-readable format.
   * Convert 3.0 (quilt) format (Closes: #1007547).
Checksums-Sha1:
 27c0800b3a3f891fa22f005495d1e4af49d6465e 1541 fwanalog_0.6.9-9.dsc
 539103ea0836c56c447af89bf61721e7954865c7 20068 fwanalog_0.6.9-9.debian.tar.xz
 cfe0c059f54102107be6ba2dc1e8ad58f48ac828 5537 fwanalog_0.6.9-9_source.buildinfo
Checksums-Sha256:
 b572340007691c70d4f369c5985d870fb9637f5d6b778551b8e630e21e38dba0 1541 fwanalog_0.6.9-9.dsc
 e90b84360f60f69ad282732e0a893ab1be6635a350cbdedb6537c003be94e572 20068 fwanalog_0.6.9-9.debian.tar.xz
 b1d8312c69d6376e7e49209872946613a103d3dae1f67a5708fda770e027bc4c 5537 fwanalog_0.6.9-9_source.buildinfo
Files:
 7d2a6f7578ffa74c5e3cd2e4c82a2a73 1541 net optional fwanalog_0.6.9-9.dsc
 c21311a1079cd19e613a7d1b3308c1a7 20068 net optional fwanalog_0.6.9-9.debian.tar.xz
 ec7d019005e60f40599ca0351fe2b104 5537 net optional fwanalog_0.6.9-9_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmMM1EkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFA8ZC/49F+2rZePHFr2Bnx2CqZpYUV8fKtTu24Oy
/hW2iNYunjB6/LYcR+H1Bty357/EHPrZ/ltMm+EzJp8w9nWwHlRUGmkIpj8Hbge3
n9sHYppLTfyTZNxvkNWoEBRxJEUIDJTwlntnIGykki4r/MFHRElJSdfXnojmZaXg
zyr1WOp5mzIF96/N0LaNTOT6lBZ8HlrUNrQbluUqwKAKVRCBHul0MKLIyE8OhJmj
vHAOVc3XJta6Ol7tdlEnnGyU6Mab+zlXNCWJ91Lt/bruoBrTE1EBMeBiZA9P3jM5
WWZ+QA5LrnWsqQqTOwQbr7iJfufixVCU3T+/I+JutwsgTJp1l8BtRVhTvV2dSQLf
G/Y8Sma9iGs2jFPZlZBxjfHxX+e/Fro8LGSItY92+Hibc+s4+4gVRnsSpgZzqtFM
fYxIZFBi7JrCo3a3ytMvbw6409a0g6uKrROAKxN3dU8J28e2O5mFC97rmF3cBulX
DJR68vg1LioRGWxmYuq/PkYeUrZBcvY=
=GR9u
-----END PGP SIGNATURE-----

Attachment: pgpZMQuti5abe.pgp
Description: PGP signature


--- End Message ---
Reply to: