Your message dated Mon, 09 Mar 2026 10:32:08 +0000
with message-id <[email protected]>
and subject line Bug#1126675: Removed package(s) from unstable
has caused the Debian Bug report #682945,
regarding sks: recon does not start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
682945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682945
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sks
Version: 1.1.3-1
Severity: normal
Hi,
just noticed an error during logrotate’s cronjob, where it tried
to restart sks but the recon part was not running.
I have no idea what that is and how severe this is, if it is a
problem at all. This server is a private installation that, by
design, MUST not exchange public keys with the keyserver network.
root@[…]:~ # mksh -x /etc/init.d/sks start
+ [ -r /etc/default/sks ]
+ . /etc/default/sks
+ initstart=yes
+ DAEMON=/usr/sbin/sks
+ SKSDBPID=/var/run/sks/sksdb.pid
+ SKSRECONPID=/var/run/sks/sksrecon.pid
+ test -e /usr/sbin/sks
+ [ ! -x /usr/sbin/sks ]
+ echo -n Starting sks daemons:
Starting sks daemons:+ [ yes != yes ]
+ dirname /var/run/sks/sksdb.pid
+ mkdir -p /var/run/sks
+ dirname /var/run/sks/sksdb.pid
+ chown debian-sks /var/run/sks
+ echo -n sksdb..
sksdb..+ echo -n sksrecon..
sksrecon..+ start-stop-daemon --start --quiet --oknodo --chuid
debian-sks:debian-sks --make-pidfile --pidfile /var/run/sks/sksdb.pid --exec
/usr/sbin/sks -- db
+ echo done.
done.
+ exit 0
+ start-stop-daemon --start --quiet --oknodo --chuid debian-sks:debian-sks
--make-pidfile --pidfile /var/run/sks/sksrecon.pid --exec /usr/sbin/sks -- recon
root@[…]:~ # Fatal error: exception Sys.Break
_mcleanup: gmon.out: Permission denied
If this is expected behaviour, I guess we’ll need to clean up
the cronjob. If not, please advice. Thanks in advance!
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages sks depends on:
ii adduser 3.113+nmu3
ii db-util 5.1.6
ii libc6 2.13-33
ii libdb5.1 5.1.29-5
ii logrotate 3.8.1-4
ii zlib1g 1:1.2.7.dfsg-13
sks recommends no packages.
Versions of packages sks suggests:
ii postfix [mail-transport-agent] 2.9.3-2+b1
ii procmail 3.22-20
-- Configuration Files:
/etc/default/sks changed:
initstart=yes
/etc/sks/mailsync changed:
/etc/sks/sksconf changed:
hostname: […]
hkp_port: 11371
dontgossip:
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.1.6+git20210302.c3ba6d5a-4.1+rm
Dear submitter,
as the package sks has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1126675
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
