Hi Lionel, > Thank your for your bug report. The problem is not the upgrade of > capi4hylafax, nor a corruption of the init script, but an upgrade of > hylafax you probably did at the same time as the capi4hylafax > upgrade. You upgraded hylafax to version 2:6.0.0-1 or later, right? > Well, now hylafax bind-mounts /var/spool/hylafax/etc, and indeed > capi4hylafax has to adapt to this.
I am sorry, but I don't remember if there was a hylafax update at the same time. I can show the the situation now, which is the following: delta:~# /etc/init.d/capi4hylafax restart cp: `/etc/hylafax/config.faxCAPI' and `/var/spool/hylafax//etc/config.faxCAPI' are the same file delta:~# /etc/init.d/capi4hylafax stop cp: `/etc/hylafax/config.faxCAPI' and `/var/spool/hylafax//etc/config.faxCAPI' are the same file delta:~# /etc/init.d/capi4hylafax start cp: `/etc/hylafax/config.faxCAPI' and `/var/spool/hylafax//etc/config.faxCAPI' are the same file delta:~# dpkg -l | grep hyla ii capi4hylafax 1:01.03.00.99.svn.300-15 Faxing over CAPI 2.0 device ii hylafax-client 2:6.0.3-3 Flexible client/server fax software - client utilities ii hylafax-server 2:6.0.3-3 Flexible client/server fax software - server daemons Does that help? Regards, Christoph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
