Control: tags -1 moreinfo On Sun, Jul 07, 2019 at 04:41:06PM +0100, Matthias Scheler wrote: > On Sun, Jul 07, 2019 at 03:17:12PM +0200, Salvatore Bonaccorso wrote: > > On Sun, Jul 07, 2019 at 01:03:17PM +0100, Matthias Scheler wrote: > > > Package: arpwatch > > > Version: 2.1a15-7 > > > Severity: grave > > > Tags: patch > > > Justification: renders package unusable > > > > I do not think this severity is warranted, ... > > It is indeed not warranted with the information that you kindly provided. > I marked this as "grave" because after an update from Debian 9 to 10 > "arpwatch" was no longer working. Even a "systemctl restart arpwatch" > couldn't bring the service back to life. > > > ... this is because of, the following as from /etc/default/arpwatch > > This file was already present on my system and didn't get overwritten > by the update from Debian 9 to 10. > > > # when using systemd you have to enable arpwatch explicitly for each > > interface > > # you want to run it on by running: > > # systemctl enable arpwatch@IFACE > > # systemctl start arpwatch@IFACE > [...] > > by the sysvinit service. > > > > Does this help? > > That does indeed solve the problem. Thank you very much. > > So the real bug here seems to be that the APT changes don't mention > this updated systemd configuration mechanism. And the existing comment > in "/etc/default/arpwatch" will not be visible on update systems, > at least not if the configuration file was change.
Thanks a lot for your quick turnaround and feedback. Let's keep the bug open, maybe documenting that more prominently would make sense? I leave that though to the maintainers to followup further (as said I did today just notice after your bugreport following the buster release and noticing the grave filled bug). Regards, Salvatore
