> Hi Thomas, why the prefix
Because if I am looking at the list of bind9 bugs it isn't obvious from
the title what bind is supposed to be integrated with. :)
** Summary changed:
- integrate with bind package
+ Please integrate Samba 4 with bind9 package
--
You received this bug notification b
** Changed in: samba4 (Debian)
Status: Unknown => Confirmed
** Changed in: bind9 (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975973
Title:
inte
** Bug watch added: Debian Bug tracker #667999
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667999
** Also affects: bind9 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667999
Importance: Unknown
Status: Unknown
** Also affects: samba4 (Debian) via
http://bug
Hi Thomas, why the prefix? This is already associated with the samba4
package.
** Summary changed:
- samba4: integrate with bind package
+ integrate with bind package
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: bind9 (Ubuntu)
Status: New => Triaged
** Changed in: bind9 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975973
Title:
integrate
Ideally we should have provision generate /etc/samba/named.conf.samba or
something alone those lines instead; this would make it unnecessary to
provide custom apparmor rules for the configuration file. It would be
nice if bind provided some sort of mechanism that allowed external
applications to in
** Summary changed:
- bind9 config changes for samba4 cause apparmor profile conflicts
+ integrate with bind package
** Changed in: samba4 (Ubuntu)
Status: New => Triaged
** Changed in: samba4 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you
