Your message dated Sat, 02 Mar 2024 14:56:58 +0000
with message-id <[email protected]>
and subject line Bug#1007575: fixed in libtcd 2.2.2-2.2
has caused the Debian Bug report #1007575,
regarding libtcd: 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.)


-- 
1007575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libtcd
Version: 2.2.2-2.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: libtcd
Source-Version: 2.2.2-2.2
Done: Bastian Germann <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libtcd, 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 libtcd 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: Wed, 21 Feb 2024 13:21:40 +0000
Source: libtcd
Architecture: source
Version: 2.2.2-2.2
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 1007575 1029537 1047678
Changes:
 libtcd (2.2.2-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add watch file (Closes: #1029537).
   * Convert to source format 3.0 (Closes: #1007575).
   * debian/clean: Add files so src builds after binary build (Closes: 
#1047678).
Checksums-Sha1:
 6a1a83a06138a984d9a711642212d296be50e842 1574 libtcd_2.2.2-2.2.dsc
 a52bde8fab44336e8e685cea9673f6b3ee954b79 3572 libtcd_2.2.2-2.2.debian.tar.xz
 19855712f456b0dbf9d9fd9a716d8e46e8008c0d 5725 libtcd_2.2.2-2.2_source.buildinfo
Checksums-Sha256:
 e01a0ab8202b0624df4437ab7c97c655d9c20d7bf26822b9ce22a2a325d0f2fa 1574 
libtcd_2.2.2-2.2.dsc
 6a51db718bc81867504cbbfe2080c09578e886ab93040f17377ef8d1d6b0e34c 3572 
libtcd_2.2.2-2.2.debian.tar.xz
 e002d73fcc5b33c9a4eedaa40bca1047699cc7c90160fe722a39ede7652b4370 5725 
libtcd_2.2.2-2.2_source.buildinfo
Files:
 24c6b47e0933da66d2382b5ef8962c40 1574 libs optional libtcd_2.2.2-2.2.dsc
 24fe55b5bab91b623d3a4b7eb8fc5a14 3572 libs optional 
libtcd_2.2.2-2.2.debian.tar.xz
 f1cfcf6427b42d0402a9f9aaede3e78d 5725 libs optional 
libtcd_2.2.2-2.2_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmXV/lEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIkvC/wPE0OcBbpQhgicW8ORVksbuCqiLtGPRRkE
B7/vHaf3Qwp6SrBFVXdie4OriJz+qUcn6S5++RlAOiAQgWY5eDiqS7hFxDrzI19f
osM4zetck7s1gsuhKogYLp7F26n7LBN/5LhY1oMeiyLWtCmtCMvnEnAcKXRXY/AX
hC5T/cKJ3hDVfHag7cMF0eoJx52Z/XHt4VxBU9HMpZ6dfeLKaobgz73tsauclkEx
jICUO4UxTgyH7hQpbK9kkjJ1OLOkooWNfURtJdqXlf+stAjbnXX6fk31uq2jekBs
ncFVh/LuE9rJ7OEUSmH7pqPmQEWHeQHkQHJ0peqcl4oyizzx8/j/+kAQErgooZub
atj8SuO+r7JQfGFLpRIfKb1swRtkibIaZ/6Cio5zDN/fnd0KKuO5yVT0y5Hv0VGb
wcw/ByqXBs9/518DIDyh6hpUpI5J7VpA0jbMyzAb2LIFuUWB9G4o7VbOpgwUg+RS
2I2H7QMBCWq9zkuD5VTB4g4r9v9NeVg=
=hJak
-----END PGP SIGNATURE-----

Attachment: pgpNLW3kmLekx.pgp
Description: PGP signature


--- End Message ---

Reply via email to