This bug was fixed in the package bind9 - 1:9.9.5.dfsg-3ubuntu0.12
---
bind9 (1:9.9.5.dfsg-3ubuntu0.12) trusty; urgency=medium
* Backport (70_precise_mtime.diff) 18b87b2a58d422fe4d3073540bf89b5a812ed2e5
to trusty. LP: #1553176
-- LaMont Jones Fri, 03 Feb 2017 13:13:21 -0700
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Changed in: maas/1.9
Milestone: None => 1.9.5
** Changed in: maas/1.9
Status: New => In Progress
** Changed in: maas/1.9
Assignee: (unassigned) => LaMont Jones (lamont)
** Changed in: maas/1.9
Importance
Hello LaMont, or anyone else affected,
Accepted bind9 into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bind9/1:9.9.5.dfsg-
3ubuntu0.12 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
** Description changed:
Since 2.6, linux has supported nanosecond granular time in stat(2)
returns. BIND has a comment in the code that it might use it, but
continues to ignore it.
As of 9.9.3b2, named checks the time of (at least) zone files on disk
(expanding to include include fil
4 matches
Mail list logo