Your message dated Tue, 09 Aug 2005 13:32:04 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#295880: fixed in capi4hylafax 1:01.02.03-13
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Feb 2005 19:39:42 +0000
>From [EMAIL PROTECTED] Fri Feb 18 11:39:42 2005
Return-path: <[EMAIL PROTECTED]>
Received: from moutng.kundenserver.de [212.227.126.188]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1D2DyY-0001fn-00; Fri, 18 Feb 2005 11:39:42 -0800
Received: from [212.227.126.179] (helo=mrelayng.kundenserver.de)
by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
id 1D2DyX-0004So-00
for [EMAIL PROTECTED]; Fri, 18 Feb 2005 20:39:41 +0100
Received: from [80.129.133.210] (helo=pse.dyndns.org)
by mrelayng.kundenserver.de with asmtp (TLSv1:EDH-RSA-DES-CBC3-SHA:168)
(Exim 3.35 #1)
id 1D2DyX-0004HS-00
for [EMAIL PROTECTED]; Fri, 18 Feb 2005 20:39:41 +0100
Received: from pse1 ([192.168.0.3])
by pse.dyndns.org with esmtp (Exim 4.44)
id 1D2DyV-0001Gb-Ln
for [EMAIL PROTECTED]; Fri, 18 Feb 2005 20:39:39 +0100
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 18 Feb 2005 19:39:39 +0000
From: Andreas Pflug <[EMAIL PROTECTED]>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Script to address both ttySx and CAPI modems
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: kundenserver.de [EMAIL PROTECTED]
auth:0ce7ee5c3478b8d72edd8e05ccd40b70
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: capi4hylafax
Version: 01.02.03_7
Severity: wishlist
To support sending over analog modems and CAPI as well, I'd propose to
configure SendFaxCmd as /usr/sbin/dofaxsend, with this script:
#!/bin/sh
case "$2" in
tty*)
/usr/sbin/faxsend $*
*)
/usr/bin/c2faxsend $*
esac
exit $?
---------------------------------------
Received: (at 295880-close) by bugs.debian.org; 9 Aug 2005 20:50:43 +0000
>From [EMAIL PROTECTED] Tue Aug 09 13:50:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E2alY-0003ty-00; Tue, 09 Aug 2005 13:32:04 -0700
From: Lionel Elie Mamane <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#295880: fixed in capi4hylafax 1:01.02.03-13
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 09 Aug 2005 13:32:04 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 5
Source: capi4hylafax
Source-Version: 1:01.02.03-13
We believe that the bug you reported is fixed in the latest version of
capi4hylafax, which is due to be installed in the Debian FTP archive:
capi4hylafax_01.02.03-13.diff.gz
to pool/main/c/capi4hylafax/capi4hylafax_01.02.03-13.diff.gz
capi4hylafax_01.02.03-13.dsc
to pool/main/c/capi4hylafax/capi4hylafax_01.02.03-13.dsc
capi4hylafax_01.02.03-13_sparc.deb
to pool/main/c/capi4hylafax/capi4hylafax_01.02.03-13_sparc.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lionel Elie Mamane <[EMAIL PROTECTED]> (supplier of updated capi4hylafax
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 22 Jul 2005 15:29:17 +0200
Source: capi4hylafax
Binary: capi4hylafax
Architecture: source sparc
Version: 1:01.02.03-13
Distribution: unstable
Urgency: low
Maintainer: Lionel Elie Mamane <[EMAIL PROTECTED]>
Changed-By: Lionel Elie Mamane <[EMAIL PROTECTED]>
Description:
capi4hylafax - Faxing over CAPI 2.0 device
Closes: 295880 303917 318907 318935 318941 318949
Changes:
capi4hylafax (1:01.02.03-13) unstable; urgency=low
.
* New maintainer (closes: #318949)
* Treat s390x and sparc64 as 64bit archs, too.
* Fix 64 bit arch detection logic: it did the wrong thing on a 32 bit
arch that is a substring of a 64 bit arch.
* Put canonical config file in /etc/hylafax and copy it from there
to /var/spool/hylafax/etc; this matches hylafax's behaviour.
(closes: #303917, #318935, 318907)
* Install existing manpages (closes: #318941)
* create an /usr/sbin/faxsend to permit using an ISDN _and_ an
analog modem to send faxes (closes: #295880)
* g++ 4.0 transition: Build-depend on a libtiff4-dev that has transitioned.
Files:
f461093ccdef6ac7e1398fbf76afa897 707 comm extra capi4hylafax_01.02.03-13.dsc
e1a3bbb669e6b95ddb015dad1ce2f027 235643 comm extra
capi4hylafax_01.02.03-13.diff.gz
2edc017a11e588322efa4a862ea40715 206290 comm extra
capi4hylafax_01.02.03-13_sparc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC51JuscRzFz57S3MRAkjeAKDRiYJBEocj7qsKirGOEwY0F1PHjACg57fp
QHCADro1SsMup23nDjkN5p0=
=k1ey
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
