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

Bug#953155: marked as done (buster-pu: package bind9/1:9.11.5.P4+dfsg+1-1)

Your message dated Sat, 10 Sep 2022 19:28:38 +0100
with message-id <9c28d75422a89138b6935e86dadbbab674b33aa4.camel@adam-barratt.org.uk>
and subject line Re: Bug#953155: buster-pu: package bind9/1:9.11.5.P4+dfsg+1-1
has caused the Debian Bug report #953155,
regarding buster-pu: package bind9/1:9.11.5.P4+dfsg+1-1
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.)


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

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

Hi,

recently, there was a bug #952946 filled against BIND 9 (and other packages)
about license problem with OASIS PKCS#11 (pkcs11.h) that has incompatible
license.  Upstream has already fixed that in the next upstream release to be due
in March and the question here is whether we want to do the dfsg to dfsg+1 bump
just because of the pkcs11.h header in both buster and stretch.

Thanks,
Ondrej

- -- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

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

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAl5g1yxfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcJx+g/+MvoycUBOX4RnfL2lmlbX+Po/F/mN55uVYsT16TDPU1rAFTkNYvRfvCO6
hfRuOmzkA0bhGyD6Oy8JKVw6ukYZ/oDyS3YLY37pbpl9StCmHqfyzYo0G/iDSVhh
e9Df+MYfpf3l6y1+US4EfC0a2+fLbrT/1TNJicF5Bm0Nin61nm03ZRTY52LaLp5y
uBxFzpDMbwfs5L6hfqkpUbsUmXBamRiK0gnNTwaUmN48Zjv6hVoQJDe9Ho8hjwE4
RPyzCYXapzjWXl2NPjvhOEBOXg9UOdNCLv2vl2RYIpj1P6y56N+j4OP8qxW/9nTf
Ww3kdr4z+w71UlQAbklRuAMzXBVr4QuapirXCOhJz07Rxs9o+jCzZhPKmQlt4ON9
V1uVCGavJgJowX2frm4L+RrGHuU3JIuG6HaYVnyIXLUvQFnVqFXEKAmJzHe7HffD
ze+lCuMYfu6tJYXdtYoBzuf2f5L7DDNSZl2U/P3sNpYNityHzn6TjAUlkhegyXZx
41+qIX+m/xMT8fB2u0Cwvdgh8sTVT2EYdwGVjNK4DjQ+xy9F0GYG6ukSWI0Dh6/Y
i8ubmVAI1mu4qzuKAbDaexsP592wgGL62KSQRcgqcoIqxasLxHU8PYvWsbHu78kq
rheG3gA5ocj8GSxuvc/a+lQSKJIbSWjSntBkcneGgKc09xyK6pI=
=Buio
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
On Sun, 2020-04-26 at 16:51 +0200, Julien Cristau wrote:
> Control: tag -1 moreinfo
> 
> On Thu, Mar 05, 2020 at 11:40:44AM +0100, Ondřej Surý wrote:
> > Hi,
> > 
> > recently, there was a bug #952946 filled against BIND 9 (and other
> > packages)
> > about license problem with OASIS PKCS#11 (pkcs11.h) that has
> > incompatible
> > license.  Upstream has already fixed that in the next upstream
> > release to be due
> > in March and the question here is whether we want to do the dfsg to
> > dfsg+1 bump
> > just because of the pkcs11.h header in both buster and stretch.
> > 
> Can you provide more details as to exactly what the license problem
> is
> and what the change would look like?

Apparently this never went anywhere.

As the final point release for buster has now happened, I'm going to
close this bug now.

Regards,

Adam

--- End Message ---
Reply to: