From owner-freebsd-ports Wed May 31 7:14:48 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B684337B6C0; Wed, 31 May 2000 07:14:46 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: (from sobomax@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id HAA25675; Wed, 31 May 2000 07:14:46 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Date: Wed, 31 May 2000 07:14:46 -0700 (PDT) From: Message-Id: <200005311414.HAA25675@freefall.freebsd.org> To: lkoeller@cc.fh-lippe.de, sobomax@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: ports/18644: hylafax and libtiff-3.4 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: hylafax and libtiff-3.4 State-Changed-From-To: open->analyzed State-Changed-By: sobomax State-Changed-When: Wed May 31 07:09:25 PDT 2000 State-Changed-Why: It is not a FreeBSD problem at all. It is unlikely that we would raise tiff-3.4 from the dead just to run hylafax. Try to bug hylafax developers instead. http://www.freebsd.org/cgi/query-pr.cgi?pr=18644 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message