Your message dated Tue, 02 Apr 2024 12:05:01 +0000
with message-id <e1rrcsv-00helv...@fasolo.debian.org>
and subject line Bug#1007330: fixed in stone 2.4-1.1
has caused the Debian Bug report #1007330,
regarding stone: 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.)


-- 
1007330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stone
Version: 2.4-1
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.


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: stone
Source-Version: 2.4-1.1
Done: Bastian Germann <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
stone, 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 stone 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: Sat, 23 Mar 2024 10:38:35 +0000
Source: stone
Architecture: source
Version: 2.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Takuo Kitame <kit...@debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 403401 626252 999881 1007330
Changes:
 stone (2.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/copyright: Convert to machine-readable format.
   * Convert to source format 3.0. (Closes: #1007330)
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #999881)
 .
   [ Tatsuya Kinoshita ]
   * Fix FTBFS on GNU/Hurd. (Closes: #403401)
 .
   [ Tomoaki Hayasaka ]
   * Do not pass empty POP_FLAGS and POP_LIBS to build. (Closes: #626252)
Checksums-Sha1:
 355dcd5d228b24226b3a88f2858cc0ec42674748 1490 stone_2.4-1.1.dsc
 e406a3b804520cad15fe4241a61463fb41d4c443 8140 stone_2.4-1.1.debian.tar.xz
 a51805dbe06d9bed8d84417a8e62c0dba2227c52 6087 stone_2.4-1.1_source.buildinfo
Checksums-Sha256:
 af500702eaf02cb7f805f6508fab6e544b9e5ecd40c4019c269f90cc520611f0 1490 
stone_2.4-1.1.dsc
 60ad829a313d2219bc62e9ec709352115cced13ba1055bd1e4b9fc405207e79f 8140 
stone_2.4-1.1.debian.tar.xz
 fa70eca34531941f2ec1a2b633aad39865281c20233fc6e4ec82ac3719b1d7b4 6087 
stone_2.4-1.1_source.buildinfo
Files:
 0690a95e2bab4d3ce5791de2879aa24f 1490 net optional stone_2.4-1.1.dsc
 c7e4d66716e93a029505a627e450bf83 8140 net optional stone_2.4-1.1.debian.tar.xz
 fbd7b5d98b0349ad10425a50745f9217 6087 net optional 
stone_2.4-1.1_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmX+uOMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFFiYDADbhu+3BvRy/uPjLpEglseC+0QycM5M2jJm
0QAkQpiqjR4M35G15UxCx6DVVcvEVJgzTRN5vEYcS2d2XW6xdi43jq9cfY4vkKR1
gxfj6zgY7xEbWS2tV0l3WTLevkuwevzJ+3p5kxqrluQdWR3kBTp77lxl6DGp2YS0
JjGev8Ckjz4hF09Gx8GM4GRTccaZBXDOBbm+F+p+e80y2lyvHIDueIx0KXcDSf6X
v/k32IfrSGn53Be7P8l/RvHv89/EcVuYgPsJfb5wv9fuMrJ3fVGfV3xtZBaYDhBI
CiDg2uM6BcY5Rz27nkvp6dxTC5GqVzrzyABP9u6DVhrDBNkBgMEiOABxOGhioA37
5ZUgoMa1nsaOuP2oG/i3dbQxH5zAA53dzC4WV8KWAYXeg6lNP4lw16mo5Vh3Sea6
j6s2GcOEQfJtSPqS7zhvJvrV23Tk5W0TN1WAUGLViuafoeZRivB2PGU1IgNCwTOZ
u4lR+3pDUPg7p2hgAQlHuUERLHWvYo4=
=jqbD
-----END PGP SIGNATURE-----

Attachment: pgphLZZsKkC6Y.pgp
Description: PGP signature


--- End Message ---

Reply via email to