Package: approx Version: 5.7-2 Severity: important Dear Maintainer,
Approx used to work fine on this server. At some point a few weeks ago it simply stopped working. I am guessing it was an upgrade to of approx (5.7 from 5.4?) or some change in the systemd configuration at the same time that caused the problem. However I was not able to investigate at the time, I just had to switch all the machines to individual working rather than using the approx system. I have just retried and there is no approx service registered and no access to port 9999 on the server. Whilst I have added things to the /etc/approx/approx.conf file, I have not fiddles with the approx files in any other way. I thus have the "out of the box" configuration other than extra lines in the one configuration file. On the one hand the problem has a workaround, on the other approx is basically unusable and so this is a crtitical bug. I am hoping that this is a problem at my end I am fearing that approx is no unusable in perpituity -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages approx depends on: ii adduser 3.115 ii bzip2 1.0.6-8 ii curl 7.51.0-1 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-8 ii libpcre3 2:8.39-2 ii rsyslog [system-log-daemon] 8.23.0-2 ii update-inetd 4.43 ii xz-utils 5.2.2-1.2 approx recommends no packages. Versions of packages approx suggests: pn libconfig-model-approx-perl <none> -- Configuration Files: /etc/approx/approx.conf changed [not included] -- debconf information: approx/port: 9999
