Your message dated Thu, 10 Sep 2020 00:34:15 +0000
with message-id <[email protected]>
and subject line Bug#966202: fixed in utfcpp 2.3.4-1.1
has caused the Debian Bug report #966202,
regarding utfcpp: Please fix the broken VCS-SVN field
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.)


-- 
966202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966202
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: utfcpp
Version: 2.3.4-1
Severity: normal
X-Debbugs-CC: [email protected]
Tags: sid

Dear Debian utfcpp maintainer,

Your package is still using anonscm.debian.org in Vcs fields, which is now
broken. Please consider updating this information in the packaging metadata.

Since the new version of taglib library is starting to use utfcpp, I am
looking into improving the packaging of utfcpp recently. Let me know if it's
okay to refresh packaging with 0-day NMUs (otherwise I would follow a bug
report -> NMU pattern).

-- 
Regards,
Boyuan Yang

--- End Message ---
--- Begin Message ---
Source: utfcpp
Source-Version: 2.3.4-1.1
Done: Boyuan Yang <[email protected]>

We believe that the bug you reported is fixed in the latest version of
utfcpp, 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.
Boyuan Yang <[email protected]> (supplier of updated utfcpp 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, 02 Sep 2020 19:42:08 -0400
Source: utfcpp
Architecture: source
Version: 2.3.4-1.1
Distribution: unstable
Urgency: medium
Maintainer: Mathieu Malaterre <[email protected]>
Changed-By: Boyuan Yang <[email protected]>
Closes: 966202
Changes:
 utfcpp (2.3.4-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Rebuild the package.
   * debian/control: Update Vcs-* fields to use git packaging repo
     under Salsa Debian Group. (Closes: #966202)
Checksums-Sha1:
 bcec9ee7aacf150651724e67d7fc2fe91b7c4c65 1864 utfcpp_2.3.4-1.1.dsc
 1e45c0cddc1f4ddafe8ecf91e716292259f2cd5a 17699 utfcpp_2.3.4.orig.tar.gz
 fedc92667bd8eb466eba2de486d044aa047a4fa5 2056 utfcpp_2.3.4-1.1.debian.tar.xz
 6fed3c024498a51ef3fb145253d76f904dc1e6e7 5592 utfcpp_2.3.4-1.1_amd64.buildinfo
Checksums-Sha256:
 507fb6436ed6f2508eebb0fa68c4800ffdd8039ba127eb9293bf11dd3e7e0854 1864 
utfcpp_2.3.4-1.1.dsc
 f62e5fd6e9f07337395c2d05c047025d35705c07be39d2a1cdb55c6e6b63723d 17699 
utfcpp_2.3.4.orig.tar.gz
 7d6fff9b7870a045dc77db7b3018ab38df013eeda6a832ddbb4061818cbbded7 2056 
utfcpp_2.3.4-1.1.debian.tar.xz
 4f5177260fdcf264939764399363f18b15be48de6f7a794a96d4a8ee47441e83 5592 
utfcpp_2.3.4-1.1_amd64.buildinfo
Files:
 08d9f6092ea81e4fb1feefb3e102de35 1864 libdevel optional utfcpp_2.3.4-1.1.dsc
 bddbb7a6fd2bb2a96d9252336af7e375 17699 libdevel optional 
utfcpp_2.3.4.orig.tar.gz
 6bb5f4dd1a6cfe5c923d14c629d85118 2056 libdevel optional 
utfcpp_2.3.4-1.1.debian.tar.xz
 2eb9ccff1f9ba1df9d65ac482a16d211 5592 libdevel optional 
utfcpp_2.3.4-1.1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl9QLvAACgkQwpPntGGC
Ws65rA//QTs/t4VuS5FBUMaBSDHJ+vxXrn/XFqCiiXY0Daymt29DPnc03bZFmMcP
hOSgwVxFENckUcHHxy/DUXWQFwdcURe3rj69kfF3IvYH3F6yxPQxzGEC/nYWrJY7
2LQGDXFu5ZurYd8w2I22REanlpDAlXtcnlDG/84jJYlKuv59hv2WQ00VwF5eyrTK
0tXMn/g+ncyZjQvVXORErGjg01TN2DA4QTh3P/hNoFuFgIWt+64tnUjqDetCgS8L
CmRK9P+qTydGWuLN0fyk7CCKg4YTKIAmFM6RhADNESZujqvNb8aC8nj9kqjZDrxr
YRmdts4KiArK8CkA0ywRZTGXYGNIxJTp14JxgREkGqDzTs2+ELM7RumcVKhCvhlS
wN2RWJ+tI/dWML0hj3Y4mvInYGZx0I+ZkghZwehenvaEyteSYDUDf1loBPId9Hfc
T91KkQjpWDq/ONe590hh3Ld5AR6cKV+jpKwmwqnxoYamCU4tJQyZwfuGGhvAct2C
j/G1+K4RLLnyyc2ngfC3ZY5n572EXh45xZPdewdPvO1QTBpceDph7ie08OdSB3Oc
lFOgnqX/kH9wflO/d/4PAoCm3OU2v8CRAJ9BFX7xF21AB9Vm2atMZIkNWaPmz4DB
RGSf0XfY1nLUgh+aRIeZ1QrIziGqdYbVxziQzsE91fpS3QmtljU=
=QO+z
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to