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

Bug#1007431: marked as done (makepatch: please consider upgrading to 3.0 source format)

Your message dated Thu, 25 Aug 2022 19:55:10 +0000
with message-id <E1oRIwY-00GsEi-TO@fasolo.debian.org>
and subject line Bug#1007431: fixed in makepatch 2.03-3
has caused the Debian Bug report #1007431,
regarding makepatch: 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.)


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

We believe that the bug you reported is fixed in the latest version of
makepatch, 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 1007431@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 makepatch 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: Thu, 25 Aug 2022 21:23:06 +0200
Source: makepatch
Architecture: source
Version: 2.03-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1007431
Changes:
 makepatch (2.03-3) unstable; urgency=medium
 .
   * QA upload.
   * Convert to 3.0 (quilt) format (Closes: #1007431).
   * d/watch: Drop because it is non-functional.
Checksums-Sha1:
 98362625e86ef7fc7289c707a515e053aad4a52e 1562 makepatch_2.03-3.dsc
 911d8fcb4b05ef42dce34f00b6797c1be3db659b 3964 makepatch_2.03-3.debian.tar.xz
 cfc03202d1c823345a485834fa5737d27c7b3062 5517 makepatch_2.03-3_source.buildinfo
Checksums-Sha256:
 f0f452afe39314b003c38f030437c920b14e5db578e32a2b855323626c56b0d9 1562 makepatch_2.03-3.dsc
 65d0cf6ad3559656af61dfa36d4b14d3f0b45159cdd0167178c3af01f3a73bf0 3964 makepatch_2.03-3.debian.tar.xz
 f811462a83e4f48fd5efb534d71b12cb2052fb81ce6c781f91aab626c456c5c3 5517 makepatch_2.03-3_source.buildinfo
Files:
 7023f281728e211e7626b6d14019b382 1562 utils optional makepatch_2.03-3.dsc
 19ac53311e8b0e375ac37f50e8c7403d 3964 utils optional makepatch_2.03-3.debian.tar.xz
 8efa304b07d49683613760f86220acee 5517 utils optional makepatch_2.03-3_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmMHz9oQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAF5DACuVOjEt+ndd/DOvEE0e/oXz5V3cuAL61RW
mlL1+e9BsFvQo394Tcpi0HUlrdUn+1xdlZZx747IJ++0D4C4OXKKK/U/ZltP7frE
H8Mvu6jnoTd5Nzo9UtZBSdU0fYYZ25es7uUPzFYNeuQdwhQPYxWAUWc3rTM9fr80
D7jTA1EIPy766/cLGVUhVKi20Rb/wSjTWpL6vAS+CI/V5FO/CUtvBc6DhQlUBfyD
JhHjlEbj+XL6BYCYt+XV0mm/nqZC0djxxcRSkCuXBxH/F6iJLa9TGZfFVHsnks4Y
pk8ZriYQ2lmi5B79L68/9ySF+7mWeCk72M2wG8w6QvRsQyw7lE8s6HnYWb+Brdd7
WQPuuiLBGjgjuFeeyf4XxvJ7DLlhPwB91GJ5m2W9S7b/pwWwIXRsZeVrAFNz7msS
RmSictetTTVgKXf3cddf3AzM9uD4lkjJO6dNZh/ayD9fjeQ/Oc/FCVl43nf17S2j
CKZgueLIZdNK1NCSpPbzM/FFZtPi1Sw=
=Ewwg
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: