Hi Mathieu,
On Samstag, 22. Oktober 2011, Mathieu Malaterre wrote:
As one of the many fop maintainers, I would vote *against* backporting
fop 1.0 to squeeze (quite strongly actually). See bug #610344 and more
recently #646141.
ok.
The question now becomes should we backport 0.95 with a
Hi Holger,
On Tue, Oct 18, 2011 at 11:55 AM, Holger Levsen hol...@layer-acht.org wrote:
as a workaround one can rebuild xmlgraphics-commons and fop from wheezy. (A
newer version of xml-graphics-common is needed for the newer fop.)
xmlgraphics-commons_1.4.dfsg-3.dsc and fop_1.0.dfsg2-3.dsc
Hi,
from #debian-java
* h01ger wonders if you think #575411 is a.) important and b.) warants a fix
in squeeze..
nthykier h01ger: can you follow up on the bug asking for a stable update?
h01ger sure
cheers,
Holger
__
This is the maintainer address of Debian's Java team
Hi,
as a workaround one can rebuild xmlgraphics-commons and fop from wheezy. (A
newer version of xml-graphics-common is needed for the newer fop.)
xmlgraphics-commons_1.4.dfsg-3.dsc and fop_1.0.dfsg2-3.dsc built fine for me
in a pure squeeze environment.
cheers,
Holger
__
This is
reopen 575411
thanks
Thanks Gabriel for the clear report ! I have re-open the bug. And I'll
close in the next upload of fop (properly this time) !
Thanks very much !
--
Mathieu
__
This is the maintainer address of Debian's Java team
Your message dated Fri, 16 Sep 2011 14:47:22 +
with message-id e1r4zhk-00073t...@franck.debian.org
and subject line Bug#575411: fixed in fop 1:1.0.dfsg2-3
has caused the Debian Bug report #575411,
regarding fop: log4j not initialized correctly
to be marked as done.
This means that you claim
In fact the bug is not fixed by FOP 1.0.
It is fixed by Debian patch 04_fixqdoxbuildfailure.patch :
[...]
--- /dev/null1970-01-01 00:00:00.0 +
+++ fop-1.0/fop.mf2011-08-26 15:15:10.0 +0200
@@ -0,0 +1,1 @@
+Class-Path: xercesImpl.jar xalan2.jar bsf.jar
Patch dump_exception.patch is probably redundant with a working
logging configuration (3 lines below the exception is logged).
Moreover, it should not print traces to stdout
(the real output of fop might be sent there).
--
Gabriel
__
This is the maintainer address of Debian's Java team
fixed 575411 fop/1:1.0.dfsg2-2
thanks
I cannot reproduce the issue using 1.0 release. Must be 0.95 specific. Closing.
--
Mathieu
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
575411: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: fop
Version: 1:0.95.dfsg-10
Severity: normal
The following
tag 575411 moreinfo
thanks
For some reason I cannot reproduce this issue with latest fop from
testing. Could someone double-check ?
Thanks much
--
Mathieu
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Tags: patch
By default, FOP uses log4j for logging, if it is available. This
behavior can be overridden, however, by setting the
org.apache.commons.logging.Log system property.
Since in Debian the fop package depends on libcommons-logging-java but
not on liblog4j1.2-java, assume that the
Hello,
Shouldn't this be fixed in commons-logging ?
Removing the classpath entry from MANIFEST-MF
(06_classpath_manifest.patch in commons-logging)
should fix the problem in applications.
Individual applications might want to add log4j in their
classpath to make their log4j.properties settings
On 2011-07-11 15:42, Gabriel Corona wrote:
Hello,
Shouldn't this be fixed in commons-logging ?
Removing the classpath entry from MANIFEST-MF
(06_classpath_manifest.patch in commons-logging)
should fix the problem in applications.
Individual applications might want to add log4j in their
clone 575411 -1
reassign -1 libbatik-java
thanks
Hi,
On Fri, Jun 18, 2010 at 1:36 AM, Gabriel Corona
gabriel.cor...@enst-bretagne.fr wrote:
A quick fix is to add either :
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
or
Processing commands for cont...@bugs.debian.org:
clone 575411 -1
Bug#575411: fop: log4j not initialized correctly
Bug 575411 cloned as bug 586288.
reassign -1 libbatik-java
Bug #586288 [fop] fop: log4j not initialized correctly
Bug reassigned from package 'fop' to 'libbatik-java'.
Bug
Hello,
A quick fix is to add either :
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
or
-Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger
in the last command of /usr/bin/fop :
run_java
Package: fop
Version: 1:0.95.dfsg-10
Severity: normal
The following warnings occur every time I run fop:
lakeview ok % fop -v 21 | head -n 2
log4j:WARN No appenders could be found for logger
(org.apache.fop.util.ContentHandlerFactoryRegistry).
log4j:WARN Please initialize the log4j system
18 matches
Mail list logo
