The sks ebuild needs some love.
The sks binary is a daemon; it should be installed in usr/sbin, not in usr/bin.
The db dir needs a dodir (deb puts it in /var/lib/sks).
It needs an init script and a uid/gid.
start-stop-daemon --start --quiet --user sks:sks --make-pidfile --pidfile /run/sks/sks.pid --chdir /var/lib/sks --exec /usr/sbin/sks -- db &
should do the trick.)
Incidently, the /usr/bin/sks_build.sh script, as currently installed, expects sks to bin in /usr/sbin and the db in /var/lib/sks, so that is already correct.
Also, 1.1.3 is out.
/etc/sks also needs a dodir and example sksconf, membership and mailsync files.
Deb’s mailsync ends with:
┃ # Jonathan McDowell <email@example.com> says that having
┃ # his keyserver's address in the Debian package is fine.
Someone with an @gentoo email address should ask to use that address for Gentoo’s default sks/mailsync, too.
This package now lacks an active maintainer, if you want to help please see:
*** Bug 445152 has been marked as a duplicate of this bug. ***
(In reply to comment #3)
> *** Bug 445152 has been marked as a duplicate of this bug. ***
This contains ebuilds
Created attachment 332860 [details]
Created attachment 332862 [details, diff]
The bdb_stubs patch from 1.1.2 with a few unused lines ommited.
Created attachment 332864 [details]
Runscript for the database daemon.
Created attachment 332866 [details]
Renscript for the key recon daemon.
Created attachment 332868 [details]
Common config for the runscripts.
Created attachment 332870 [details]
Systemd service file for the database daemon.
Created attachment 332872 [details]
Systemd service file for the key recon daemon.
There have been reports of Sks-1.1.4 crashing after a while, which I have experienced but it is not consistant for me.
Are you willing to proxy maintain this?
(In reply to comment #13)
> Are you willing to proxy maintain this?
I'll need to read up on QA, but sure.
(In reply to comment #14)
> (In reply to comment #13)
> > Are you willing to proxy maintain this?
> > http://www.gentoo.org/proj/en/qa/proxy-maintainers/index.xml
> I'll need to read up on QA, but sure.
Will CC proxy-maintainers people then
Created attachment 363282 [details]
Created attachment 363284 [details, diff]
Based on the ebuild from Emery Hemingway is a version of the ebuild I use locally that amongst others include a patch for ECC OIDs on x86 (backport from upstream trunk)
Note that I've only uploaded the ebuild and patch to this bug, as the rest of the files from Emery should be the same. The full repo I'm using locally containing the complete set of files (runscripts etc) is available at https://bitbucket.org/kristianf/portage-overlay/src/tip/net-misc/sks?at=default .
Created attachment 363294 [details]
I accidentaly uploaded the wrong version of the sks-1.1.4.ebuild initially, that still contained a library reference to BDB5.2
(In reply to Kristian Fiskerstrand from comment #19)
> Created attachment 363294 [details]
There are a number of problems with this ebuild, please use the repoman utitily and see the #gentoo-sunrise channel for help.
Created attachment 363302 [details]
Created attachment 363304 [details, diff]
Created attachment 363306 [details]
@systemd: mrueg requested systemd unit review on IRC.
Any reason for adding:
to the systemd unit? You can also drop "Type=simple" as it's the default ;)
Created attachment 363344 [details]
Created attachment 363346 [details]
There are no upstream requirements for the recon service to run at a non-default nice level. Updated files also remove Type=simple
They look ok for me :)
I put the Nice option in the recon unit because the recon daemon isn't expected to do anything in realtime, it just periodically polls other servers for updates.
Thanks for your help!
*sks-1.1.4 (22 Nov 2013)
22 Nov 2013; Manuel Rüger <firstname.lastname@example.org>
+files/sks-db.service, +files/sks-recon.initd, +files/sks-recon.service,
+files/sks.confd, +sks-1.1.4.ebuild, metadata.xml:
Version bump. Add initd scripts and systemd unit files by Emery Hemingway.
Fixes bug #427030. Add Kristian Fiskerstrand as maintainer and proxy-
maintainers as herd.