From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Oct 18 08:20:06 2008 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6636106569F for ; Sat, 18 Oct 2008 08:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 935DC8FC23 for ; Sat, 18 Oct 2008 08:20:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id m9I8K6Sv038419 for ; Sat, 18 Oct 2008 08:20:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id m9I8K60r038418; Sat, 18 Oct 2008 08:20:06 GMT (envelope-from gnats) Date: Sat, 18 Oct 2008 08:20:06 GMT Message-Id: <200810180820.m9I8K60r038418@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Stefan Walter Cc: Subject: Re: ports/107304: print/apsfilter does not print PDF to raw PostScript printers with print/acroread7 installed X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Stefan Walter List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Oct 2008 08:20:06 -0000 The following reply was made to PR ports/107304; it has been noted by GNATS. From: Stefan Walter To: Mark Evenson Cc: GNATS , andreas@freebsd.org Subject: Re: ports/107304: print/apsfilter does not print PDF to raw PostScript printers with print/acroread7 installed Date: Sat, 18 Oct 2008 10:17:37 +0200 Hi Mark, there hasn't been an update on ports/107304 [1] for quite a while. Can you still reproduce the problem you reported with an up-to-date ports tree, or should the PR be closed? (I'd test it myself, but I'm using CUPS and don't want to hose my configuration at the moment.) IMO, even if it's an acroread bug, ignoring it in apsfilter is the wrong way if it doesn't work correctly with it, and marking acroread as broken because apsfilter has a problem with it wouldn't make much sense, either. Regards, Stefan [1]: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/107304