Source: jaxe
Version: 3.3-2
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20110313 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
>  /usr/bin/fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -fr build dist
> rm -fr source/api
> dh_clean
>  dpkg-source -b jaxe-3.3
> dpkg-source: warning: no source format specified in debian/source/format, see 
> dpkg-source(1)
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building jaxe using existing jaxe_3.3.orig.tar.gz
> dpkg-source: info: building jaxe in jaxe_3.3-2.diff.gz
> dpkg-source: warning: the diff modifies the following upstream files: 
>  source/jaxe/Export.java
>  source/jaxe/SchemaRelaxNG.java
>  source/jaxe/ValidationFrame.java
>  source/log4j.properties
> dpkg-source: info: use the '3.0 (quilt)' format to have separate and 
> documented changes to upstream files, see dpkg-source(1)
> dpkg-source: info: building jaxe in jaxe_3.3-2.dsc
>  debian/rules build
> dh_testdir
> mkdir -p plugins
> mkdir -p source/lib
> CLASSPATH=/usr/share/java/fop.jar:/usr/share/java/jazzy.jar:/usr/share/java/jing.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/xalan2.jar:/usr/share/java/cortado.jar:/usr/share/java/xmlgraphics-commons.jar
>  ant -buildfile build.xml
> /bin/sh: ant: not found
> make: *** [build-stamp] Error 127

The full build log is available from:
   http://people.debian.org/~lucas/logs/2011/03/13/jaxe_3.3-2_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to