Your message dated Wed, 12 Feb 2014 15:42:54 +0100
with message-id <52fb886e.3020...@pocock.pro>
and subject line Re: [Pkg-javascript-devel] Bug#738385: jscommunicator: FTBFS:
/usr/bin/closure-compiler errors
has caused the Debian Bug report #738385,
regarding jscommunicator: FTBFS: /usr/bin/closure-compiler errors
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.)
--
738385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jscommunicator
Version: 1.1.0-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140208 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> ./make-release
> /usr/bin/closure-compiler: line 1: $'PK\003\004': command not found
> /usr/bin/closure-compiler: line 2: $'\b3\236!D': command not found
> /usr/bin/closure-compiler: line 19: $'\b2\236!D': command not found
> /usr/bin/closure-compiler: line 20: rhino_ast/PK: No such file or directory
> /usr/bin/closure-compiler: line 26: syntax error near unexpected token `)'
> make[1]: *** [override_dh_auto_build] Error 2
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/02/08/jscommunicator_1.1.0-1_unstable.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 ---
On 09/02/14 17:38, David Suárez wrote:
> Source: jscommunicator
> Version: 1.1.0-1
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20140208 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>> make[1]: Entering directory `/«PKGBUILDDIR»'
>> ./make-release
>> /usr/bin/closure-compiler: line 1: $'PK\003\004': command not found
>> /usr/bin/closure-compiler: line 2: $'\b3\236!D': command not found
>> /usr/bin/closure-compiler: line 19: $'\b2\236!D': command not found
>> /usr/bin/closure-compiler: line 20: rhino_ast/PK: No such file or directory
>> /usr/bin/closure-compiler: line 26: syntax error near unexpected token `)'
>> make[1]: *** [override_dh_auto_build] Error 2
> The full build log is available from:
>
> http://aws-logs.debian.net/ftbfs-logs/2014/02/08/jscommunicator_1.1.0-1_unstable.log
The real cause of the error is earlier in the log:
update-binfmts: warning: Couldn't load the binfmt_misc module.
This suggests the build environment is broken and it is not a fault in
the package so I am closing the bug
--- End Message ---
