Your message dated Fri, 12 Feb 2016 06:18:54 +0000 with message-id <e1au74a-0002tx...@franck.debian.org> and subject line Bug#800279: fixed in ddtc 0.17.2 has caused the Debian Bug report #800279, regarding ddtc: Please migrate a supported debhelper compat level 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.) -- 800279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ddtc Severity: important Usertags: deprecated-debhelper-compat-leq-3 Hi, The package ddtc is using a debhelper compat level of 3 or less according to lintian. These compat levels have been deprecated for the past ~10 years and debhelper will remove support for them in the near future (as declared in [1]). * Please migrate the package to a supported debhelper compat level. - Compat 9 is recommended - Compat 5 is the bare minimum (compat 4 will be removed soon as well) * If your package uses any of the following tools, please remove them from the rules files. Neither of them does anything except warn about their deprecation. - dh_desktop - dh_scrollkeeper (deadline: January 1st 2016) - dh_suidregister - dh_undocumented * Please note that your package might have been flagged for using e.g. "DH_COMPAT=2 dh_foo ...". - This will still cause issues when the compat level is removed. * If the package has been relying on dh_install being lenient about missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1]. * Deadline: - compat 1+2: November 1st 2015 - compat 3: January 1st 2016 If you are using other deprecated debhelper features (such as omitting the debian/compat file), please consider fixing those while you are at it. Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---Source: ddtc Source-Version: 0.17.2 We believe that the bug you reported is fixed in the latest version of ddtc, 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 800...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski <kilob...@angband.pl> (supplier of updated ddtc 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: SHA256 Format: 1.8 Date: Fri, 12 Feb 2016 06:40:16 +0100 Source: ddtc Binary: ddtc Architecture: source Version: 0.17.2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packa...@qa.debian.org> Changed-By: Adam Borowski <kilob...@angband.pl> Description: ddtc - Deal with ddts mails Closes: 800279 Changes: ddtc (0.17.2) unstable; urgency=medium . * QA upload. * Set the maintainer to the QA team. * Build with debhelper 9 (closes: #800279) * Update FSF's address. Checksums-Sha1: 4a81255ccc2ff6c63ee86254f135b431a45156a6 1025 ddtc_0.17.2.dsc 3a9f09ea3546d7ddfc3406edef4ed9bd91c22327 47896 ddtc_0.17.2.tar.gz Checksums-Sha256: 62ca49a302864520bc5eb1ed40abf1ee94e2f63ebd18b718b5868e75fa688bbd 1025 ddtc_0.17.2.dsc c7e52f86cbc29640ef7326b1334f980d27b04963a45a770926cf8fcdbec71d77 47896 ddtc_0.17.2.tar.gz Files: 447740da6e8e24fa87bc1f9b575a3cb7 1025 text optional ddtc_0.17.2.dsc 3cd6e70802a1cddd0d83f4b1b0f32c2b 47896 text optional ddtc_0.17.2.tar.gz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWvXHYAAoJECw7Q2/qxoEB8rgH/1ftI/XKy7fIHMrJq2fyhO0c 3gV8VUYOjCiH+eQSeGWg3knICgRvhlWXi52krFfeTrT1fw/o13LvkJFw0B6dRJGU L2+sdHOhSMnFfjlkMk1uVRvbbqe8RLwFUiGh5WmrUNrtVkBYWif+Ta8WQnDsduKs x00q+u4KY5ebxAKaK42zM6mYHpKrvU8eJMYhGMRAW6s74Q4k+x335NDSoOfsINFl +RxnOTBBZH4KD9ZiTDpNbk4PUQjn8N5XUfGEZ7t5pg+CRnu+1G6LTXMjI6vy/UFY zOaNWjutdDrAXtpFUCtTFFqrMG7kRwdh0A/ujFhrwzdT5rW91zZo96cY5cQsoJc= =W26v -----END PGP SIGNATURE-----
--- End Message ---
