Package: proguard
Version: 4.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> javac -d build/retrace -sourcepath src src/proguard/retrace/ReTrace.java
> src/proguard/retrace/ReTrace.java:23: error: The import proguard.obfuscate 
> cannot be resolved
>       import proguard.obfuscate.MappingReader;
>              ^^^^^^^^^^^^^^^^^^
> src/proguard/retrace/ReTrace.java:83: error: StackTrace cannot be resolved to 
> a type
>       StackTrace stackTrace = new StackTrace(verbose);
>       ^^^^^^^^^^
> src/proguard/retrace/ReTrace.java:83: error: StackTrace cannot be resolved to 
> a type
>       StackTrace stackTrace = new StackTrace(verbose);
>                                   ^^^^^^^^^^
> src/proguard/retrace/ReTrace.java:84: error: MappingReader cannot be resolved 
> to a type
>       MappingReader reader = new MappingReader(mappingFile);
>       ^^^^^^^^^^^^^
> src/proguard/retrace/ReTrace.java:84: error: MappingReader cannot be resolved 
> to a type
>       MappingReader reader = new MappingReader(mappingFile);
>                                  ^^^^^^^^^^^^^
> 5 problems (5 errors)
> make: *** [build] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/06/20/proguard_4.3-1_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
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to