** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1275649
Title:
MAAS packaging doesn't include maas-generated
named.con
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1275649
Title:
MAAS packaging doesn't include maas-generated
named.conf.op
** Changed in: maas
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1275649
Title:
MAAS packaging doesn't include maas-generated
named.conf
This is almost ready to be fixed; there's a dependent branch in maas
waiting to land which is blocked on the iscpy package getting accepted
into trusty.
** Changed in: maas
Assignee: (unassigned) => Julian Edwards (julian-edwards)
** Changed in: maas
Status: Triaged => In Progress
--
** Branch linked: lp:~julian-edwards/maas/forwarders-config-writer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1275649
Title:
MAAS packaging doesn't include maas-generated
named.c
And thinking about it, we need to write some code in maas to make it
easier for packaging to insert the config.
** Changed in: maas
Status: Invalid => Triaged
** Changed in: maas
Importance: Undecided => High
** Changed in: maas
Milestone: None => 14.04
--
You received this bug n
