** Changed in: bind9 (Ubuntu)
Importance: Undecided => Low
** Changed in: bind9 (Ubuntu Xenial)
Importance: Undecided => Low
** Changed in: bind9 (Ubuntu Xenial)
Status: Invalid => Won't Fix
** Tags added: packaging
--
You received this bug notification because you are a member
** Changed in: bind9 (Ubuntu Xenial)
Milestone: xenial-updates => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To
I agree with Chris, this is a significant change in SRU for small
benefit. We're stuck with python2 in main for the duration of 16.04;
SRUs to change an interpreter post-release are not justifiable under our
SRU policy.
Happy to discuss this further if there's an overriding reason here, but
in
Also, apport.py is python2, so this needs more work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To manage notifications
There are a sum total of 2 binaries affected by the change:
/usr/sbin/dnssec-checkds
/usr/sbin/dnssec-coverage
Both of which are in bind9utils, and used for verifying dnssec
configuration. Neither of them is actually required for the operation
of BIND.
--
You received this bug notification
This seems like a significant change for an SRU, for (what seems to me
to be) a small benefit. What testing will be done to validate that there
aren't behaviour changes switching to python3? Particularly - it seems
plausible that a python3 version would error out in some cases where
python2 would
** Changed in: bind9 (Ubuntu Xenial)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To
There are some utility scripts which are written in python. As part of
9.10, they were changed to be able to run with python2 or python3. This
change simply switches them from using python2 to using python3,
affecting the #! at the top of the generated script, but otherwise
changing nothing.
Does that change any API/ABI that bind9 exposes to its clients? I. e. is
there some regression potential for plugins/admin-provided helper
scripts and the like which might need to get ported to Python 3? What
does this setting do exactly?
** Changed in: bind9 (Ubuntu Xenial)
Status: In
** Changed in: bind9 (Ubuntu Xenial)
Milestone: None => xenial-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not depend on python2 in xenial
To
[Impact]
python 2.7 is installed on xenial machines, when it should not be needed (which
affects the minimum footprint for bind9utils, and therefore maas.
[Test Case]
Install maas-rackd. Note how python2.7 comes along for the ride..
[Regression potential]
python3 support was added to BIND with
** Patch added: "debdiff for 8ubuntu2"
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1578674/+attachment/4656508/+files/bind9_9.10.3.dfsg.P4-8ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fixed in 1:9.10.3.dfsg.P4-10 in yakkety.
** Changed in: bind9 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578674
Title:
bind9 packages should not
13 matches
Mail list logo
