Judging by this response, the fontconfig failure is not practically important.
----- Forwarded message from Debian Bug Tracking System <[EMAIL PROTECTED]>
-----
X-Mailer: MIME-tools 5.417 (Entity 5.417)
X-Loop: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Debian Bug Tracking System)
To: Justin Pryzby <[EMAIL PROTECTED]>
Subject: Bug#363136 acknowledged by developer (Re: Processed: reopening
363136)
X-Debian-PR-Message: they-closed 363136
X-Debian-PR-Package: defoma
Reply-To: [EMAIL PROTECTED]
Date: Wed, 19 Apr 2006 07:49:38 -0700
X-Spam-Score: 0.4 (/)
X-Spam-Report: Spam Filtering performed by sourceforge.net.
See http://spamassassin.org/tag/ for more details.
Report problems to
http://sf.net/tracker/?func=add&group_id=1&atid=200001
0.3 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME
0.0 HTML_MESSAGE BODY: HTML included in message
0.1 HTML_00_10 BODY: Message is 0% to 10% HTML
This is an automatic notification regarding your Bug report
#363136: deforma should exit failure on failure,
which was filed against the defoma package.
It has been closed by one of the developers, namely
"Angus Lees" <[EMAIL PROTECTED]>.
Their explanation is attached below. If this explanation is
unsatisfactory and you have not received a better one in a separate
message then please contact the developer, by replying to this email.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references;
b=cG1kkghtxo+MWrliEmFH7Kqm7gGHZ/AWK9JdjPD1JeQP6THVLlYY6M+m77xVc42tS4frpfAObKUeHS2tl4j4snkmOHpSsWf+TbVn6L5nHa8yX1Y45EKSyk8KytZr4KxXOSZZsTZpKuX2GngoPK/4Yo7cYhdNXxX/XV2cpot35xc=
Date: Wed, 19 Apr 2006 14:58:12 +0100
From: "Angus Lees" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Processed: reopening 363136
In-Reply-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=-1.5 required=4.0 tests=BAYES_00,HTML_MESSAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
This was never a bug, since fc-cache success is entirely optional.
Likewise, purging fontconfig should not fail just because defoma couldn't
remove a few files in a directory that is later rm -rf'ed anyway. The bug
if anything, is that fontconfig.defoma doesn't optimise for the "full purge"
case by skipping the fc-cache run on what is at that point an empty
directory and removing the fc-cache output files itself. This violates a
few abstraction layers, and breaks if/when fontconfig moves to writing cache
files to some other location (eg /var/cache/).
Alternatively, fontconfig.defoma could discard error output from fc-cache to
avoid misleading the user but I'm not sure that's a net win either.
Closing bug as "not a bug". Please reopen as a request for one of these
features if you feel the benefit outweighs the cost.
--
- Gus
----- End forwarded message -----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
