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

Bug#1007519: marked as done (fstrcmp: please consider upgrading to 3.0 source format)

Your message dated Mon, 11 Jul 2022 00:49:00 +0000
with message-id <E1oAhbg-000D4Q-1J@fasolo.debian.org>
and subject line Bug#1007519: fixed in fstrcmp 0.7.D001-3
has caused the Debian Bug report #1007519,
regarding fstrcmp: 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.)


-- 
1007519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007519
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: fstrcmp
Version: 0.7.D001-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.


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: fstrcmp
Source-Version: 0.7.D001-3
Done: Vagrant Cascadian <vagrant@reproducible-builds.org>

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

Debian distribution maintenance software
pp.
Vagrant Cascadian <vagrant@reproducible-builds.org> (supplier of updated fstrcmp 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: Sun, 10 Jul 2022 17:23:23 -0700
Source: fstrcmp
Architecture: source
Version: 0.7.D001-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Vagrant Cascadian <vagrant@reproducible-builds.org>
Closes: 1007519 1011479
Changes:
 fstrcmp (0.7.D001-3) unstable; urgency=medium
 .
   * QA upload.
   * Switch to source format "3.0 (quilt)". (Closes: #1007519)
   * debian/control: Remove obsolete "DM-Upload-Allowed" field.
   * Remove obsolete libfstrcmp0-dbg package.
   * Convert to "dh" and debhelper-compat 13. (Closes: #1011479)
   * Install pkgconfig file in multi-arch dir.
   * debian/control: Set Rules-Requires-Root to "no".
Checksums-Sha1:
 bb2f67341d64e5f86a4cdbe13bfa72c11638e897 1500 fstrcmp_0.7.D001-3.dsc
 013c965b28a5d4a27f67838a35e5fff341c71206 4568 fstrcmp_0.7.D001-3.debian.tar.xz
Checksums-Sha256:
 81c6a721599f9075e6b2bb367672ed17bd072c4180e7af287051121446e5a99d 1500 fstrcmp_0.7.D001-3.dsc
 c6a175d070c23b51672b88fb87d2bcfbfa66e1278fee82d8e5355fda9df06cbe 4568 fstrcmp_0.7.D001-3.debian.tar.xz
Files:
 ab2a8f9a8ff104f0af54468f6a38b682 1500 devel optional fstrcmp_0.7.D001-3.dsc
 70e8a478c975a94d6da146693a0c6260 4568 devel optional fstrcmp_0.7.D001-3.debian.tar.xz

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

iJYEARYKAD4WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCYstvUCAcdmFncmFudEBy
ZXByb2R1Y2libGUtYnVpbGRzLm9yZwAKCRDcUY/If5cWqk/QAPsFieXMakUxEGRv
oUzbawUGFa2fw8tv31uzUzEHN/Xb/wD7BFA0O2T/GiFpAtvRhI5tg/nQSGP05aRj
jkTtbAKsrQE=
=Vi4v
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: