group.of.nepali.translators team mailing list archive

[Robie Basak <1656801@xxxxxxxxxxxxxxxxxx>]

Thank you for identifying this. I agree it makes sense to fix it in
Xenial. Though I wonder about how the change might adversely impact
existing users.

For example, if a DHCP user is receiving a broken set of NTP servers
that doesn't work, currently his NTP won't be broken because the default
set will be used

But with this fixed, the default set will stop being used, and his NTP
will appear to break. Though the root cause is that his DHCP or network
was misconfigured, it would be the SRU that causes the problem to
emerge.

In principle I think this is OK, but we should point it out in
"Regression Potential", and I appreciate more opinions.

** Also affects: ntp (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: ntp (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: ntp (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1656801

Title:
  ntp: changing the default config from server to pool broke the dhcp
  hook

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged

Bug description:
  In 1:4.2.8p3+dfsg-1, the default config was changed to
  "Use pool instead of server".  This needs a corresponding
  update to /etc/dhcp/dhclient-exit-hooks.d/ntp, since the
  DHCP specified servers now get added to the default pool
  config instead of replacing them.

  This affects Xenial only as the Yakkety build includes the upstream
  fix (1:4.2.8p7+dfsg-1).

  Original Debian busg https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809344 
  & https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806676

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1656801/+subscriptions