Your message dated Fri, 10 Feb 2023 09:19:42 +0000 with message-id <e1pqpzg-002qow...@fasolo.debian.org> and subject line Bug#965644: fixed in libibtk 0.0.14-12.2 has caused the Debian Bug report #965644, regarding libibtk: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965644 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: libibtk Version: 0.0.14-12.1 Severity: normal Usertags: compat-5-6-removal Hi, The package libibtk uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---Source: libibtk Source-Version: 0.0.14-12.2 Done: Adrian Bunk <b...@debian.org> We believe that the bug you reported is fixed in the latest version of libibtk, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Bunk <b...@debian.org> (supplier of updated libibtk 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: Fri, 10 Feb 2023 01:30:33 +0200 Source: libibtk Architecture: source Version: 0.0.14-12.2 Distribution: unstable Urgency: high Maintainer: Christian Bayle <ba...@debian.org> Changed-By: Adrian Bunk <b...@debian.org> Closes: 965644 999106 Changes: libibtk (0.0.14-12.2) unstable; urgency=high . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965644) * debian/rules: Add build-{arch,indep}. (Closes: #999106) Checksums-Sha1: d7c18bfd1e9c257a99077af6d04ad403cf1c16b9 1753 libibtk_0.0.14-12.2.dsc c2238a403ea188a5a94b4fb898e6e76a9c94f5e6 366376 libibtk_0.0.14-12.2.diff.gz Checksums-Sha256: 59cb759160ed19adfcc31fefea0a599f989e11443e03a9243b31ba8e3b7378ab 1753 libibtk_0.0.14-12.2.dsc 03217f64ce547c8989792e81cee4a79b7b2f9cb9246ed9ba54a927a6c0778131 366376 libibtk_0.0.14-12.2.diff.gz Files: 995da51927179800b2216c232c0ac37f 1753 libs optional libibtk_0.0.14-12.2.dsc d8f06ea887d30072ee6683b68f74307f 366376 libs optional libibtk_0.0.14-12.2.diff.gz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPlgw4ACgkQiNJCh6LY mLFPtA/+I+QnR5k2YsMXgQWfQs7IqbGMNS2RJQE0I+afallX05SRIT4/Z7PADQit Kzn4vMhnVMXvu5HZfdmArMm8XnMYArvp0/vdBsOp7JQW2CM+LVf51daLxLlvt7Sz k/OAmNZ+sfB8B/+Kkgb5YCBU1kAsy6KDC2JSjlCmfscj3PZ5d0JzwUpeCQ6aF6hO CcHbYfHO1w3UPXy2UA2fAXWwdXj3jq6u8LLgVxOENKvUcr67Vq3W6/va5gHL0X66 hGfj69NgjSoQAXjv08Ndcvzlq0D1fKH/mNAEq73HKak6V1ELrJQ6vWjj7v9Ov8AF +RE2uOpZ6q0mtT/FiHCoSIvRF3ipcBbPkRzGWGHQd29ZTO53fxaMsOcUr8rtLZmS RqIY44b/YEFDM4uR4uKfP89A9AizWUX6gww6LQI8J1EmuqR83HTmrUPJKrsqNyjt yiU2atWMxrYOIb2zT+9NlPsOOdxJmFIQljUVKamMppo9E90pEyP8Nof75GgRKe7H 4DmowHWSqUxb9K/fsuhCghIn/HWGdNNNfy7uMuAsrXKgeRxHojU/HINcKoTRCYNx Lz5sn44x3lJgrFBvcBuIT8JF/QhjF82kKTRcwcZrUAG0HWe1SIAxYS+V0YhAzgr6 GPLduE/JhvnnsYSVY/RnvC+Zu1DSQuDs92vs0qKUk0S/NiDhock= =tEPq -----END PGP SIGNATURE-----
--- End Message ---
