Package: capi4hylafax Version: 1:01.02.03-7 Severity: normal
capi4hylafaxconfig changes /var/spool/hylafax/etc/config.faxCAPI, which is a real file, and seems to be the one actually used by hylafax. faxsetup run afterwards will copy whatever was setup in /etc/hylafax/config.faxCAPI to /var/spool/hylafax/etc/ and overwrite the changes made with capi4hylafaxconfig. shouldn't /var/spool/hylafax/etc just be a symbolic link to /etc/hylafax to prevent this? At he moment there seem to exist two separate sets of config files which are not kept in sync all the time. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-andi-1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages capi4hylafax depends on: ii isdnactivecards 1:3.6.2005-01-03-5 Support utilities for active ISDN ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libcapi20-2 1:3.6.2005-01-03-5 libraries for CAPI support ii libgcc1 1:3.4.3-12 GCC support library ii libstdc++5 1:3.3.5-8 The GNU Standard C++ Library v3 ii libtiff4 3.7.2-1 Tag Image File Format (TIFF) libra -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
