Your message dated Wed, 19 Jun 2024 17:58:02 +0000
with message-id <[email protected]>
and subject line Bug#1007591: fixed in m16c-flash 0.1-1.4
has caused the Debian Bug report #1007591,
regarding m16c-flash: 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 [email protected]
immediately.)


-- 
1007591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007591
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: m16c-flash
Version: 0.1-1.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: m16c-flash
Source-Version: 0.1-1.4
Done: Bastian Germann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
m16c-flash, 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.
Bastian Germann <[email protected]> (supplier of updated m16c-flash 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, 09 Jun 2024 16:58:40 +0000
Source: m16c-flash
Architecture: source
Version: 0.1-1.4
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1007591
Changes:
 m16c-flash (0.1-1.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert to source format 3.0. (Closes: #1007591)
Checksums-Sha1:
 943b65e3da5c68a22c2c422bde8b24a695e1e2d6 1528 m16c-flash_0.1-1.4.dsc
 b2a0f197e0a3b1f2ac10e978462613affe03b216 2660 m16c-flash_0.1-1.4.debian.tar.xz
 0fc69509fcd3e43342deb6f808938294a7ce23d9 5739 
m16c-flash_0.1-1.4_source.buildinfo
Checksums-Sha256:
 237d8700a23a3afdb61e19b9aa4b7bbe2d043ce4bba1e5fad326cd04a67b4631 1528 
m16c-flash_0.1-1.4.dsc
 ecfa63cf101df7d5fef641c997e79b062fe07e12597b3dc8c11b6bc2e0b2b8bf 2660 
m16c-flash_0.1-1.4.debian.tar.xz
 e9e29f38366a45c06e9f6337b968ab749ee27bb29d4ff1a5d4500ba8b93ae6cc 5739 
m16c-flash_0.1-1.4_source.buildinfo
Files:
 1f7e03c861ac4e58fa7cb03e91e0ab57 1528 electronics optional 
m16c-flash_0.1-1.4.dsc
 9767ba5ea375dc256312519aa9c7a398 2660 electronics optional 
m16c-flash_0.1-1.4.debian.tar.xz
 a8fec1222a757c7c0febefa2d6197d12 5739 electronics optional 
m16c-flash_0.1-1.4_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmZl4NkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFCUpC/96h0soYUJspV+t3eJT3h+XgULR+5Fq8P/I
2LSe2tJ+e8dzS23TWM6ExLlEUEEUrer8YGaWgmwpODTcbymOav4vTFCRHjpnwH8L
08B+yYdcR+xjNUfSwrhDdsoM/nKyN0rJM/2ijjMVm3Jvk/8ja8acCptUEW1Vn676
14H03yKru96vgBmOulBARlC10sA1NyWhzAcf/TvfI+7npWCTJKCRUG2siLkYDSvL
L44j9S52YDJJ9PCB+jrAuKrMFha5aLCynAXh6bbSBggV1eGwsoZAj/+ixujpaZUq
FHxZf2BbuFqGva2wStD70+E4eRB94yvDV8vMPNRGl/JBI03UYgFWU3gBWC065ldg
qmhiuRmrt+kAXI7DPIPSe8QWIkIzVIS7JjtunNLfUdEQskq6DzTjZWpW+MKHgijX
5jSmPVGbD89HO6bSrq41jOyJ4rsagmIECaR2UslNU4bwBLcQeqmlvqIkA3PbqXxQ
5wkxwImYvTKuGHOS+12Dl2jyg2isGRQ=
=8M0I
-----END PGP SIGNATURE-----

Attachment: pgpAkomBtTKcp.pgp
Description: PGP signature


--- End Message ---

Reply via email to