Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 545468

Summary: net-misc/openntpd-5.7_p4 : version bump
Product: Gentoo Linux Reporter: Perfect Gentleman <perfect007gentleman>
Component: Current packagesAssignee: Paul B. Henson <henson>
Status: RESOLVED FIXED    
Severity: normal CC: junghans
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: patch to update p3 ebuild to p4
patch to portage to add p4 ebuild and new patch

Description Perfect Gentleman 2015-04-04 08:05:52 UTC
http://www.openntpd.org/txt/release-5.7p4.txt

Reproducible: Always
Comment 1 Paul B. Henson 2015-05-26 01:02:59 UTC
Created attachment 403962 [details, diff]
patch to update p3 ebuild to p4
Comment 2 Paul B. Henson 2015-05-26 01:03:48 UTC
Created attachment 403964 [details, diff]
patch to portage to add p4 ebuild and new patch
Comment 3 Paul B. Henson 2015-05-26 01:10:25 UTC
Not much value for Gentoo in this new version, as libtls is not available, making the new TLS constraint feature unusable. Of the two other changes, one is only relevant on Solaris, and the other fixes a bug only relevant on 32bit systems. I guess there might still be a few of those out there ;), and this is the last release for the 5.7 series, so might as well push it out.

After this bakes for a bit in ~amd64. I'd like to stabilize it. Christoph, remind me how long a package needs to be in unstable before opening a stablization request?

Thanks..
Comment 4 Christoph Junghans (RETIRED) gentoo-dev 2015-05-26 14:38:18 UTC
Repoman said:

  inherit.unused                1
   net-misc/openntpd/openntpd-5.7_p4.ebuild: no function called from autotools.eclass; please drop

So I dropped it.

+*openntpd-5.7_p4 (26 May 2015)
+
+  26 May 2015; Christoph Junghans <ottxor@gentoo.org>
+  +files/openntpd-5.7_p4-nolibtls.patch, +openntpd-5.7_p4.ebuild:
+  version bump (bug #545468)
+


(In reply to Paul B. Henson from comment #3)
> After this bakes for a bit in ~amd64. I'd like to stabilize it. Christoph,
> remind me how long a package needs to be in unstable before opening a
> stablization request?
Please open one in 30 days (if no major bugs shows up).