hylafax (3:6.0.7-1) unstable; urgency=medium

  This new package version is rather different from previous ones because
  it integrates with systemd and changes the way to copy/overlap the
  configuration directory /etc/hylafax to /var/spool/hylafax/etc.
  
  1. systemd configuration
  
  Please note that on new installation, systemd services are not started
  automatically. You should enable them in order to start on boot:
  
  # systemctl enable hylafax.service hfaxd.service  
  
  If you configure a modem with faxaddmodem, a new systemd unit file
  will be created, faxgetty@DEVICE.service, wher DEVICE is the complete
  name of the device without the leading /dev. After the modem is configured
  another systemd service is enabled, faxq.
  
  So, on systems with a modem on /dev/ttyUSB0 and another on /dev/ttyS0,
  you should normally have these units:
  hylafax.service            ** hides any script in /etc/init.d
  hfaxd.service              ** the server letting client submit faxes
  fagetty@ttyUSB.service     ** send/receive faxes on /dev/ttyUSB0 modem
  fagetty@ttyS0.service      ** send/receive faxes on /dev/ttyS0 modem
  faxq.service               ** manage the queue of faxes
  
  They are all configured as part of the first one, so starting
  hylafax.service will start all other services as well.
 
  faxgetty services are created by faxaddmodem and when upgrading
  hylafax to 6.0.7-1.

  The systemd dependency from faxgetty to the device is coupled with an
  udev rule. Rules are defined in /lib/udev/rules.d/*hylafax-server*
  and only include ttyS0-4, ttyUSB0-15, ttyIAX0-7
  
  2. /var/spool/hylafax/etc
  
  The configuration is still in /etc/hylafax, but all daemons running as
  systemd services mount the directory in /var/spool/hylafax/etc as
  well. This is configured in the systemd unit file.
  
  All other commands that are not run as daemons, have been moved
  to directory /var/lib/hylafax/bin. In their original pathnames
  has been installed a wrapper that mount the directory, calls
  the real command, then umount the directory.
   
 -- Giuseppe Sacco <eppesuig@debian.org>  Fri, 14 Feb 2020 00:24:41 +0100
