Your message dated Fri, 10 Feb 2023 09:19:54 +0000
with message-id <e1pqpzs-002qqd...@fasolo.debian.org>
and subject line Bug#965786: fixed in pppoeconf 1.21+nmu3
has caused the Debian Bug report #965786,
regarding pppoeconf: 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.)


-- 
965786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pppoeconf
Version: 1.21
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package pppoeconf 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: pppoeconf
Source-Version: 1.21+nmu3
Done: Adrian Bunk <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
pppoeconf, 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 pppoeconf 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:46:49 +0200
Source: pppoeconf
Architecture: source
Version: 1.21+nmu3
Distribution: unstable
Urgency: high
Maintainer: Gregory Colpart <r...@debian.org>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 965786
Changes:
 pppoeconf (1.21+nmu3) unstable; urgency=high
 .
   * Non-maintainer upload.
   * debian/compat: 5 -> 7. (Closes: #965786)
Checksums-Sha1:
 d2e6a44f76a6ee0ea56d42da5fc511c3381e453c 1584 pppoeconf_1.21+nmu3.dsc
 361395a351ab13251d8e3c25052fb89ae1710ce2 52005 pppoeconf_1.21+nmu3.tar.gz
Checksums-Sha256:
 20c313e4bf9d9596aae39b56c5493eb3e4063c2ec3326be4a823437b2b19ff83 1584 
pppoeconf_1.21+nmu3.dsc
 420bff71b4f3c0aceead57c1e3b095afe9da9ed67b3dccd0c7b29d9b0ad88240 52005 
pppoeconf_1.21+nmu3.tar.gz
Files:
 5bae8493c626173c4e70abb353f0038e 1584 net optional pppoeconf_1.21+nmu3.dsc
 ef0b3cd137a142d7fb19f0015b12799f 52005 net optional pppoeconf_1.21+nmu3.tar.gz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmPlhjgACgkQiNJCh6LY
mLE41g/9H5Bjgotnqghl5nvPwPN1Lasj6pgJ89S6fp1TETM3PMffmY61uu2V3wf9
4PM68DUP6yrqD8I08ocFudjYVP+Qy/FJLQaCJzlH3nQwjDVb3vFReBPWxIeosv6u
4N16vlNV4gcnj1CmWN1sZW5U7+5RAvn17kKlHgBUvigkxKbvspT5a1HVaG4mN08C
RQYuHpj2ErFB9eO/lPJ0PU+cj8nLg/Yzwilyuwu3Dpg1ThWIvMSfXwdQw1RUbB5m
I2FE2ce1MgpTDmRIzx+UoSYbxCiVX2fNY00sVeQ8rNPfUBGIE9pB+63i1bv/UH7y
56Dw9+rnIaUWI0CaRJQWNDvkx9LAT7fSLfQEb4uNztxV2RRUeMv4IQ4wPlK3IYy7
P+2/c223Mv6T/4tEnzuKzxe9GBO9Z3mMZnTE1hJ+Ti4QobudNz5vZzUmQzssZZgq
1s1N7xxGxxnAsklhegxIG0tEj8sjSKeDgJfh/UYt6rNz5l4sp29jS1JUPyjNT9gE
wkfS/MbkszI9hMwtjnCnYYxeqCqHdcHJOTHTzDZUE/DvFiDSPR8T6muz1TAbSWzK
QaNUvzcByT7jtW3Y6C3SgH4KllEB1Ng4SQkICKqutVPhrweWMlR5LRtvcwZK5qpM
KyhqHkNwaEKLzqwBJH0L1b/MVbhxY2CiUjmIWpCaMHL/QIHW788=
=s4An
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to