Your message dated Mon, 23 Sep 2019 19:33:57 +0000
with message-id <e1icu5t-0008lv...@fasolo.debian.org>
and subject line Bug#897675: fixed in libtcd 2.2.2-2.1
has caused the Debian Bug report #897675,
regarding libtcd: not binNMU safe
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.)


-- 
897675: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897675
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtcd
Version: 2.2.2-2
Severity: serious
Tags: buster sid

Hi,

Your package is not binNMU safe. This is reported by the lintian tag

https://lintian.debian.org/tags/not-binnmuable-any-depends-any.html

Basically your package libtcd-dev has:

Depends: libtcd0 (= ${source:Version})

That should be ${binary:Version}, since the version will differ from
the source version in a binNMU.

Cheers,
Emilio

--- End Message ---
--- Begin Message ---
Source: libtcd
Source-Version: 2.2.2-2.1

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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Boyuan Yang <by...@debian.org> (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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sun, 08 Sep 2019 14:24:19 -0400
Source: libtcd
Architecture: source
Version: 2.2.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith <p...@debian.org>
Changed-By: Boyuan Yang <by...@debian.org>
Closes: 897675
Changes:
 libtcd (2.2.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Make libtcd-dev dependency to be using
     ${binary:Version} instead of ${source:Version}.
     (Closes: #897675)
   * debian/control:
     + Let libtcd-dev depends on ${misc:Depends}.
     + Replace Priority: extra with Priority: optional.
   * debian/*.ex: Removed, useless. (lintian warning)
   * debian/dirs: Removed, useless.
   * debian/postinst,postrm: Empty scripts, removed.
   * debian/libtcd0.dirs: Removed, useless.
   * debian/rules:
     + Replace deprecated dh_clean -k with dh_prep.
     + Add missing recommended target build-arch and build-indep.
   * debian/source/format: Explicitly use "1.0" format.
   * debian/libtcd-dev.install: Do not install .la file.
Checksums-Sha1:
 933a5e7e2d8450f3a1d9125fff4fc6a1f2ac9937 1698 libtcd_2.2.2-2.1.dsc
 fadc8736ed2641035e986a9900b363d5d29fac6b 7153 libtcd_2.2.2-2.1.diff.gz
 aeb47d5a67239470bcaa269fc5d2c06f6a4938a5 6031 libtcd_2.2.2-2.1_amd64.buildinfo
Checksums-Sha256:
 2f6b3b3b927d8cd9987630344b010cb75f5a3abad6d2b547714d3deacea1b37e 1698 
libtcd_2.2.2-2.1.dsc
 1cef3070b06996628af784043ee1d78bf434bb60492356d57511a500ea7ebe77 7153 
libtcd_2.2.2-2.1.diff.gz
 5316d08892ff28b47d3bfbea11fe082384bfb756664568c4c5ff56b7e382a32c 6031 
libtcd_2.2.2-2.1_amd64.buildinfo
Files:
 41059eac994197764a931f55b59bd726 1698 libs optional libtcd_2.2.2-2.1.dsc
 9a8dd6941ab2436e4ff33fdee2ecbe1c 7153 libs optional libtcd_2.2.2-2.1.diff.gz
 13456e694835201a9d813ba315f2589a 6031 libs optional 
libtcd_2.2.2-2.1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAl11SMUACgkQwpPntGGC
Ws7RMRAAwVzaW1ulGtL6S6DcLUxTMNPsAMnrBIsVPPrLARxCyE59XM52xU/ze4SZ
O3ePLrYriiiMRvD94ochEcALiG5P+zEe+RnaLQf1RtglUjju/6wXm2ZnupYgbqqS
17TvfKBwyuvmuGizKsuTkGUwwSACLO11m8MgBI3ch47Inauh/Tl2yqYddZkZ1FUr
KBW/Tw94VfDH6So6BLMdWuBISqTlX8uHDstrwCIATKDMoT/KF4H6a1Nk0KFr5xlN
5wSaTIV/BMntRjgnGogsUQ3UgmuHrmUd3MG/Ao/0uKF4hhbJkAtTvNUkOEJWB0zM
twuWY7IOARL3CLQkeqzzGIHBopCIlBIhDerenJ0oR0UecPBBE5kn44IYwXiNEkxl
HTZMGII6TBhN9SRTktOWFl34Yl0MYXy4Y0rYAX0gzkgGZa8S2V9AlAPP0+CTLBLx
8+nsDmRqLTXRiyg4zxzSNPlYTnNHw6JzD5gI/1g9yCdW6wkro8s3GN3y4LNLaL0B
wNtAEJ0E55lMum1yRZ3VmW0hSdUc4QrmtEgWCY3NySraR+ZYMrKWIOdOrRiWEjn9
byb19Xi47ymQZrwMDVrtPi79shlye2wvhl6I3uHA7KPyQ2mttFSTN1PkG0YokWon
e/Jccn+QWL9V5GgS458iZ4EGLhofg5P3PQX7rIzQpZfnTd99ADk=
=JEIv
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to