Bug#586288: marked as done (fop: log4j not initialized correctly)

[Debian Bug Tracking System]

Your message dated Sun, 13 Sep 2015 21:11:23 +0200
with message-id <CA+7wUswGCU5FWSLOfSycdq7T2SSKbyqhq5akXX7S=PyxAnfLnQ at mail.gmail.com>
and subject line Re: Bug#586288: fop: log4j not initialized correctly
has caused the Debian Bug report #586288,
regarding fop: log4j not initialized correctly
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
586288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586288
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: "brian m. carlson" <sandals at crustytoothpaste.ath.cx>
Subject: fop: log4j not initialized correctly
Date: Thu, 25 Mar 2010 16:07:03 +0000
Size: 6413
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20150913/f65bc650/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Mathieu Malaterre <malat at debian.org>
Subject: Re: Bug#586288: fop: log4j not initialized correctly
Date: Sun, 13 Sep 2015 21:11:23 +0200
Size: 3009
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20150913/f65bc650/attachment-0003.mht>