Re: [Sks-devel] 1.1.5 is in wheezy-backports

[Karl Schmitz]

Hi all,

first of all: thanks to Daniel for providing the backport. Also, thanks to all who worked on the SKS 1.1.5 release.

All in all, the update from 1.1.4 (had wheezy-backports in my APT sources already) to 1.1.5 went smooth on my server.
Alas, due to my special setup (see below) the debian-sks account hit:

# aptitude
(Reading database ... 37695 files and directories currently installed.)
Preparing to replace sks 1.1.4-2~bpo70+1 (using .../sks_1.1.5-1~bpo70+1_amd64.deb) ...
Stopping sks daemons: sksrecon.. sksdb..... done.
Unpacking replacement sks ...
Processing triggers for man-db ...
Setting up sks (1.1.5-1~bpo70+1) ...
debian-sks uid check: ok
ERROR: debian-sks account has an invalid home directory!
Please check /usr/share/doc/sks/README.Debian on how to
correct this problem
dpkg: error processing sks (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 sks
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up sks (1.1.5-1~bpo70+1) ...
debian-sks uid check: ok
ERROR: debian-sks account has an invalid home directory!
Please check /usr/share/doc/sks/README.Debian on how to
correct this problem
dpkg: error processing sks (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 sks
Press Return to continue.

What's so special about my setup? On my servers, I have a comparably small root ('/') file system and a large /srv file system.
For SKS, I moved /var/lib/sks to /srv/sks, changed /var/lib/sks into a symlink pointing to /srv/sks, and changed debian-sks's home to /srv/sks. The latter change led to the error shown above, leaving sks 1.1.5-1~bpo70+1 half-configured.

I worked around that by changing debian-sks's home back to /var/lib/sks (thank god I made the "compatibility" symlink) and finishing package configuration:

# fg
aptitude
Setting up sks (1.1.5-1~bpo70+1) ...
debian-sks uid check: ok
debian-sks homedir check: ok
Starting sks daemons: sksdb.. sksrecon.. done.
Press Return to continue.

IMHO, the account check is a bit exaggerated, isn't it? The administrator should be free to alter debian-sks's home.

Also, checking free space on /var before taking the backup would be nice (possibly with an option to specify an alternate backup directory).
The backup almost filled up my root file system.

Besides these minor issues: well done! My server is running SKS 1.1.5 now.

Kind regards,

Karl

Am 04.06.2014 18:00, schrieb Daniel Kahn Gillmor:

Hi folks--

I built SKS 1.1.5 against debian wheezy, tested it, and it is now in
wheezy-backports.

If you're running debian stable, and you want to move to sks 1.1.5, you
should set up the wheezy-backports repository [0] and install sks from
there.

At the moment, only the amd64 platform is built, but the other platforms
should be built over the next day or so.

I'm running this in production on zimmermann.mayfirst.org, so if there
are any problems, i hope to hear about them.  please let me know if you
think there are any issues.

Thanks to everyone who worked on the 1.1.5 release.

happy hacking,

	--dkg

[0] http://backports.debian.org/Instructions/

signature.asc
Description: OpenPGP digital signature