** Bug watch added: Debian Bug tracker #696390
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696390
** Also affects: ntp (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696390
Importance: Unknown
Status: Unknown
** Changed in: ntp (Ubuntu)
Status: In
** Changed in: ntp (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1236065
Title:
Crypto support missing in Saucy
To manage notifications
** Branch linked: lp:ubuntu/saucy-proposed/ntp
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1236065
Title:
Crypto support missing in Saucy
To manage notifications about this bug go
This bug was fixed in the package ntp - 1:4.2.6.p5+dfsg-3ubuntu1
---
ntp (1:4.2.6.p5+dfsg-3ubuntu1) saucy; urgency=low
* Merge from Debian testing to regain crypto support (LP: #1236065). Remaining
changes:
+ debian/ntp.conf, debian/ntpdate.default: Change default server to
Here's the debdiff between what's currently in Saucy and the update I'm
proposing with the debdiff above. The merge from Debian testing only
pulls in the fix for this bug.
** Patch added: old-saucy-to-new.debdiff
Merge ntp 1:4.2.6.p5+dfsg-3 from Debian testing.
I've verified that QRT's test-ntp.py now passes. Here's the relevant
snippet from the build log:
checking for openssl library directory... /usr/lib/x86_64-linux-gnu
checking for openssl include directory... /usr/include
checking if we will
