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 #766949, regarding sks: init script doesn't fail when sks can't bind to address 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.) -- 766949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766949 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sks Version: 1.1.5-2 Severity: normal Hi. This is basically a follow up to #766943. Apparently sks' initscript doesn't fail, even when sks couldn't bind to an address, e.g.: # systemctl -l status sks.service ● sks.service - (null) Loaded: loaded (/etc/init.d/sks) Active: active (running) since Mon 2014-10-27 06:52:22 CET; 4min 21s ago Process: 1991 ExecStart=/etc/init.d/sks start (code=exited, status=0/SUCCESS) CGroup: /system.slice/sks.service ├─2043 /usr/sbin/sks db └─2046 /usr/sbin/sks recon Oct 27 06:52:22 kronecker systemd[1]: sks.service changed dead -> start Oct 27 06:52:22 kronecker systemd[1991]: Executing: /etc/init.d/sks start Oct 27 06:52:22 kronecker sks[1991]: Starting sks daemons: sksdb.. sksrecon.. done. Oct 27 06:52:22 kronecker systemd[1]: Child 1991 belongs to sks.service Oct 27 06:52:22 kronecker systemd[1]: sks.service: control process exited, code=exited status=0 Oct 27 06:52:22 kronecker systemd[1]: sks.service got final SIGCHLD for state start Oct 27 06:52:22 kronecker systemd[1]: sks.service changed start -> running Oct 27 06:52:22 kronecker systemd[1]: Job sks.service/start finished, result=done Oct 27 06:52:22 kronecker systemd[1]: Started (null). Oct 27 06:52:23 kronecker sks[1991]: 2014-10-27 06:52:23 Failed to listen on 2a01:4f8:a0:4024::2:2:11370: Failure("Failure while binding socket. Probably another socket bound to this address") Now I think it's quite clear, that having failed to bind to an iface should be considered a critical errror (since the service won't be usable) and thus the init-script should fail as well and not let e.g. systemd believe that everything got right. Cheers, Chris.
--- 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 ---
