From: [email protected]

Package: hylafax-server
Version: 1:4.1.8-13
Severity: grave
Justification: renders package unusable

-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.18-bf2.4
Locale: LANG=C, LC_CTYPE=C

Versions of packages hylafax-server depends on:
ii debconf 1.4.30 Debian configuration management sy ii gs 8.01-4 Transitional package
ii gs-esp [gs] 7.07.1-6 The Ghostscript PostScript interpr ii gs-gpl [gs] 8.01-4 The GPL Ghostscript PostScript int ii hylafax-client 1:4.1.8-13 Flexible client/server fax softwar ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii libgcc1 1:3.4.1-4sarge1 GCC support library
ii libpam0g 0.76-22 Pluggable Authentication Modules l ii libstdc++5 1:3.3.4-6sarge1 The GNU Standard C++ Library v3
ii libtiff-tools 3.6.1-1 TIFF manipulation and conversion t ii libtiff3g 3.6.1-1 Tag Image File Format library
ii mailx 1:8.1.2-0.20040524cvs-1 A simple mail user agent
ii mime-codecs 7.18-9 Fast Quoted-Printable and BASE64 M ii zlib1g 1:1.2.1.1-5 compression library - runtime

-- debconf information:
* hylafax-server/configure_note:
hylafax-server/start_now: true

This is just the latest in a series of issues that cropped up in the aftermath of an
apt-get upgrade which braught in a new version of hylafax about two months ago give
or take.

Permissions were wrong. Ownerships had to be fixed.
Files were missing, including papaersizes and typerules.
Here is the email I sent to the
[email protected] list:

Message 278:

From [email protected] Sat Aug 21 16:01:36 2004

Date: 21 Aug 2004 16:01:36 -0000
From: [email protected]
To: [email protected], [email protected]
Subject: Re: [hylafax-users] Error: Can not determine file type, Debian Package bugs?
Cc: [email protected]
In-Reply-To: <1092839851.21714.40.camel@localhost>

Giuseppe:

Thank you for the heads up about the spam complaints. I'll ask our
server administrator to whitelist your ip, if I can dig that up
somewhere.

I just copied /etc/old/hylafax/typerules to /etc/hylafax.

The error I'm getting now says:
root@biko:~# /etc/init.d/hylafax start
ERROR: /var/spool/hylafax/etc/pagesizes is newer than
/etc/hylafax/pagesizes
Please send a bug report on the hylafax-server package

so - - -

root@biko:~# ls -al /var/spool/hylafax/etc/pagesizes
-rw-r--r-- 1 root root 0 Aug 17 16:24 /var/spool/hylafax/etc/pagesizes
root@biko:~# ls -al /etc/hylafax/pagesizes
-rw-r--r-- 1 root root 3316 Apr 19 01:57
/etc/hylafax/pagesizes
root@biko:~# cp /etc/hylafax/pagesizes /var/spool/hylafax/etc/pagesizes
cp: overwrite `/var/spool/hylafax/etc/pagesizes'? y

then - - -

root@biko:~# /etc/init.d/hylafax start
ERROR: /var/spool/hylafax/etc/typerules is newer than
/etc/hylafax/typerules
Please send a bug report on the hylafax-server package

and - - -

root@biko:~# ls -al /etc/hylafax/typerules
-rw-r--r-- 1 root root 6408 Jan 31 2004
/etc/hylafax/typerules
root@biko:~# ls -al /var/spool/hylafax/etc/typerules
-rw-r--r-- 1 root root 0 Aug 17 16:24 /var/spool/hylafax/etc/typerules
root@biko:~# cp /etc/hylafax/typerules /var/spool/hylafax/etc/typerules
cp: overwrite `/var/spool/hylafax/etc/typerules'? y

which yielded:

root@biko:~# /etc/init.d/hylafax start
Starting HylaFAX daemons: faxq hfaxd faxgetty.
root@biko:~#

and finally:

hesco@biko:~$ ./fax.sh
Password:
request id is 1 (group id 1) for host localhost (1 file)

<--- That was pretty exciting.
<--- Hadn't seen that in quite a while.

Thanks for the clues. Happy to have this working again. I'll check it
out with a test broadcast and see what happens.

My prior experience was that hylafax installed cleanly "out-of-the-box"
as it were, using apt-get install, faxsetup, addfaxmodem and addfaxuser.
I had never had to jump through these sorts of hoops before. And this
is probably my third or fourth install from the Debian packaging system.

Not knowing much about the .deb packaging system, I can't really offer
you any patches, I'm afraid. But perhaps this experience might inform
the work of someone who does speak that language.

-- Hugh Esco

Subject: Re: [hylafax-users] Error: Can not determine file type, Debian
Package bugs?
From: Giuseppe Sacco <[email protected]>
To: [email protected]
Cc: [email protected]
Date: Wed, 18 Aug 2004 16:37:31 +0200

Il mer, 2004-08-18 alle 16:16, Hugh Esco ha scritto:

Hello all:

Hi Hugh,
I have been trying to send you private responses but I always get this
error:

Remote MTA pk.greens.org: SMTP diagnostic: 553 interbusiness.it banned
FOR IGNORING SPAM COMPLAINTS. Please complain to your service provider.

Of course I did contacted my provider and, one month ago, they told me
they were contacting your provider.

Now, back to your problem:

Our fax server has been down for perhaps 45 or 60 days now, ever since a recent apt-get upgrade revved the version. I'm finally sitting down to
work through the error messages I'm getting. So far, the steps I have
had to take that were not addressed by the Debian packaging system have included:

root@biko:~/hylafax# chmod 600 /etc/hylafax/hosts.hfaxd
root@biko:~/hylafax# chown uucp:uucp /etc/hylafax/hosts.hfaxd

These two steps are done by the installation procedure. Did you noticed
that the uid where changed *during* the installation process?

which got the Login failed: 530 Login incorrect. errors to go away.

cp /etc/old/hylafax/pagesizes /etc/hylafax

which did away with: Unknown page size default

Every time a new package is installed, the pagesizes file is changed in
order to add a new line with default pagesize that are read by libpaper.
What is the default papersize you setup in libpaper?

manually ran:
/usr/sbin/faxgetty ttyS0
/usr/sbin/faxgetty ttyS1

and added to inittab:

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)