Your message dated Fri, 14 Nov 2014 09:57:18 +0100
with message-id <1415955438.8446.4.ca...@ellert.tsl.uu.se>
and subject line Re: Bug#769266: canl-java: FTBFS in jessie/i386: cp: cannot
stat 'target/apidocs': No such file or directory
has caused the Debian Bug report #769266,
regarding canl-java: FTBFS in jessie/i386: cp: cannot stat 'target/apidocs': No
such file or directory
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 ow...@bugs.debian.org
immediately.)
--
769266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: canl-java
Version: 2.1.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141112 qa-ftbfs
Justification: FTBFS in jessie on i386
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
Relevant part (hopefully):
> fakeroot debian/rules binary
> dh_testdir
> dh_testroot
> dh_prep
> dh_testdir
> dh_testroot
> dh_installdocs
> cp: cannot stat 'target/apidocs': No such file or directory
> dh_installdocs: cp -a target/apidocs
> debian/libcanl-java-doc/usr/share/doc/libcanl-java-doc returned exit code 1
> make: *** [binary-indep] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/12/canl-java_2.1.1-1_jessie-i386.log
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 EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Control: notfound -1 2.1.1-1
> > As I already explained in the previous bug you reported for the same
> > issue (bug #768747) this FTBFS is due to a known bug in openjdk-7. There
> > is nothing to fix in the canl-java source package. You just need to wait
> > for the openjdk-7 maintainers to fix the bug in their package. If you
> > want this to be fixed more quickly then say so in your previous bug
> > report that was reassigned to openjdk-7.
The openjdk-7 bug is now fixed (7u71-2.5.3-2) and canl-java builds
again.
Mattias
signature.asc
Description: This is a digitally signed message part
--- End Message ---
