Created attachment 394532 [details] updated ebuild Updated ebuild/patches for openntpd-5.7_p2.
Created attachment 394534 [details, diff] Fix run path
Created attachment 394536 [details, diff] Use gentoo pool
Created attachment 394538 [details, diff] Fix drift path
Created attachment 394542 [details, diff] Backport adjtimex fix from head
Created attachment 394544 [details, diff] Backport setproctitle fix from head to avoid clobbering __progname
1.) Should we wait for 5.7_p3? 2.) Please submit patches against gx86 and the last ebuild version instead of the new version of the file (easy to review) and try to re-use patch (haven't checked) if the patches don't change.
(In reply to Christoph Junghans from comment #6) > 1.) Should we wait for 5.7_p3? I'm not sure how often he's going to be pushing minor releases. Do you want me to ask him and skip some releases if they're going to be frequent to avoid portage churn? > 2.) Please submit patches against gx86 and the last ebuild version instead > of the new version of the file (easy to review) and try to re-use patch > (haven't checked) if the patches don't change. I sent you the big patch under separate cover. Two of the patches are new, one could have been reused, and the other two applied with fuzz and offsets. I redid the two fuzzy ones so they'd apply cleanly and redid the clean one just out of repetition ;). For future reference, should patches be reused even if they're fuzzy and offset? Thanks...
+*openntpd-5.7_p2 (25 Jan 2015) + + 25 Jan 2015; Christoph Junghans <ottxor@gentoo.org> + +files/openntpd-5.7_p2-adjtimex.patch, +files/openntpd-5.7_p2-proctitle.patch, + +openntpd-5.7_p2.ebuild, -files/openntpd-5.7_p1-signal.patch, + -files/openntpd-5.7_p1-warn-s-failure.patch, -openntpd-5.7_p1.ebuild: + version bump (bug #537292, thx to Paul) + I re-used the patches, which still apply.
