[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1030570: marked as done (RM: bind-dyndb-ldap -- RoQA; broken with newer bind9 releases; unsupportable in stable)

Your message dated Sat, 29 Apr 2023 08:35:50 +0000
with message-id <E1psg3a-00H0iU-Vb@fasolo.debian.org>
and subject line Bug#1030570: Removed package(s) from stable
has caused the Debian Bug report #1030570,
regarding RM: bind-dyndb-ldap -- RoQA; broken with newer bind9 releases; unsupportable in stable
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 owner@bugs.debian.org
immediately.)


-- 
1030570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030570
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian.org@packages.debian.org
Usertags: rm

Hi Adam,

As discussed in bug #1027825, #1014503 and #1004729 (and probably
more), bind-dyndb-ldap is currently broken in bullseye and because of
its use of unstable internal details of bind9 not supportable on
stable. The concensus is that the binary package needs to be build
from src:bind9, but that's not a great option for stable.

I suggest we remove src:bind-dyndb-ldap from unstable. I have it
blocked from entering bookworm too.

Paul

--- End Message ---
--- Begin Message --- 
We believe that the bug you reported is now fixed; the following
package(s) have been removed from stable:

bind-dyndb-ldap |     11.6-3 | source
bind9-dyndb-ldap |     11.6-3 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x

------------------- Reason -------------------
RoQA; broken with newer bind9 releases; unsupportable in stable
----------------------------------------------

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1030570@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1030570

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Archive Administrator (the ftpmaster behind the curtain)

--- End Message ---
Reply to: