Your message dated Fri, 09 Oct 2009 23:47:05 +0000
with message-id <e1mwpav-0006tz...@ries.debian.org>
and subject line Bug#534029: fixed in proguard 4.4-1
has caused the Debian Bug report #534029,
regarding proguard: FTBFS: src/proguard/retrace/ReTrace.java:23: error: The
import proguard.obfuscate cannot be resolved
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.)
--
534029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 |
--- End Message ---
--- Begin Message ---
Source: proguard
Source-Version: 4.4-1
We believe that the bug you reported is fixed in the latest version of
proguard, which is due to be installed in the Debian FTP archive:
proguard_4.4-1.diff.gz
to pool/main/p/proguard/proguard_4.4-1.diff.gz
proguard_4.4-1.dsc
to pool/main/p/proguard/proguard_4.4-1.dsc
proguard_4.4-1_all.deb
to pool/main/p/proguard/proguard_4.4-1_all.deb
proguard_4.4.orig.tar.gz
to pool/main/p/proguard/proguard_4.4.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 534...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Sam Clegg <s...@debian.org> (supplier of updated proguard package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 09 Oct 2009 16:17:49 -0700
Source: proguard
Binary: proguard
Architecture: source all
Version: 4.4-1
Distribution: unstable
Urgency: low
Maintainer: Sam Clegg <s...@debian.org>
Changed-By: Sam Clegg <s...@debian.org>
Description:
proguard - java class file shrinker, optimizer, and obfuscator
Closes: 534029 548810
Changes:
proguard (4.4-1) unstable; urgency=low
.
[ Onkar Shinde ]
* Merge from Ubuntu. (Closes: #534029, #548810)
.
[ Sam Clegg ]
* Thanks Onkar for the above fixes!
* New upstream release
Checksums-Sha1:
3e3b2a1eb312d065a716af3eaeb1d82ab7ff70f5 962 proguard_4.4-1.dsc
4454e29e849eae82de29ff5af444e65801ea0953 1821537 proguard_4.4.orig.tar.gz
e6bef7d7fd1fec19e92c17854d2b98dc6519defb 2830 proguard_4.4-1.diff.gz
e733a419bcbc865bc1c0fc6631376c36acc39a13 795318 proguard_4.4-1_all.deb
Checksums-Sha256:
735c8f5ba1bfce2163c311d7735e340be0ecb77ce059091c68b7d547ea3f6be9 962
proguard_4.4-1.dsc
a15ee7abd3b67f1c2df162e4c1b7ad6dab51163225f5714b7fb80adfcaa1a3e1 1821537
proguard_4.4.orig.tar.gz
8b69eed3c7c82c294cb369ab7a686cdb86622541b02fbbf329683def15980fc8 2830
proguard_4.4-1.diff.gz
2515f60d5b76c68f4aaaebb41d00c66ba3a811fb90fe263bfa56fa1da2007021 795318
proguard_4.4-1_all.deb
Files:
53daf24d455842b4676d0ea3d4d4244a 962 devel optional proguard_4.4-1.dsc
18b8d00951be8d9f85a813c67a46b8ec 1821537 devel optional
proguard_4.4.orig.tar.gz
4171edc186aaa12ffef4ef4efe936124 2830 devel optional proguard_4.4-1.diff.gz
73102014593c6b9e452aeac85e9c949b 795318 devel optional proguard_4.4-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkrPyAQACgkQLOvxONke42lijACeNJIaMy/8Y24FvfOi+uCoXdHQ
+W8An3BB0kWk2VoEn5Lp4YTlWrdo+bLP
=kKJw
-----END PGP SIGNATURE-----
--- End Message ---
