Your message dated Sun, 9 Mar 2008 17:03:13 +0100
with message-id <[EMAIL PROTECTED]>
and subject line failure not reproducible in the same conditions
has caused the Debian Bug report #467605,
regarding stringtemplate: FTBFS: The import junit 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 [EMAIL PROTECTED]
immediately.)


-- 
467605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467605
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: stringtemplate
Version: 3.1-2
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20080225 qa-ftbfs
Justification: FTBFS on i386

Hi,

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

Relevant part:
> make[1]: Entering directory `/build/user/stringtemplate-3.1'
> make[1]: Nothing to be done for `update-config'.
> make[1]: Leaving directory `/build/user/stringtemplate-3.1'
> cd . && /usr/lib/jvm/java-gcj/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/antlr.jar:/usr/share/java/ant-antlr.jar:/usr/lib/jvm/java-gcj/lib/tools.jar
>   -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
> -Dcompile.optimize=true     jar
> Buildfile: build.xml
> 
> init:
> 
> prepare-sources:
>     [mkdir] Created dir: /build/user/stringtemplate-3.1/build
>     [mkdir] Created dir: /build/user/stringtemplate-3.1/build/src
>      [copy] Copying 71 files to /build/user/stringtemplate-3.1/build/src
> 
> generator:
> 
> compile:
>      [echo] Compiler    = ${build.compiler}
>      [echo] Optimize    = true
>      [echo] Deprecation = ${compile.deprecation}
>      [echo] Debug       = true
>     [mkdir] Created dir: /build/user/stringtemplate-3.1/build/classes
>     [javac] Compiling 44 source files to 
> /build/user/stringtemplate-3.1/build/classes
>     [javac] ----------
>     [javac] 1. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 30)
>     [javac]   import junit.framework.Assert;
>     [javac]          ^^^^^
>     [javac] The import junit cannot be resolved
>     [javac] ----------
>     [javac] 2. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 31)
>     [javac]   import junit.framework.TestCase;
>     [javac]          ^^^^^
>     [javac] The import junit cannot be resolved
>     [javac] ----------
>     [javac] 3. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 40)
>     [javac]   public class TestStringTemplate extends TestCase {
>     [javac]                                           ^^^^^^^^
>     [javac] TestCase cannot be resolved to a type
>     [javac] ----------
>     [javac] 4. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 97)
>     [javac]   Assert.assertEquals(
>     [javac]   ^^^^^^
>     [javac] Assert cannot be resolved
>     [javac] ----------
>     [javac] 5. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 1221)
>     [javac]   assertTrue(errors.toString().startsWith(expectingError));
>     [javac]   ^^^^^^^^^^
>     [javac] The method assertTrue(boolean) is undefined for the type 
> TestStringTemplate
>     [javac] ----------
>     [javac] 6. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplat
>     [javac] e.java (at line 3882)
>     [javac]   assertEquals(names.size(), 2);
>     [javac]   ^^^^^^^^^^^^
>     [javac] The method assertEquals(String, String) in the type 
> TestStringTemplate is not applicable for the arguments (int, int)
>     [javac] ----------
>     [javac] 7. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 3898)
>     [javac]   assertEquals(names.size(), 2);
>     [javac]   ^^^^^^^^^^^^
>     [javac] The method assertEquals(String, String) in the type 
> TestStringTemplate is not applicable for the arguments (int, int)
>     [javac] ----------
>     [javac] 8. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplat
>     [javac] e.java (at line 4497)
>     [javac]   assertTrue(errors.toString().startsWith(expecting));
>     [javac]   ^^^^^^^^^^
>     [javac] The method assertTrue(boolean) is undefined for the type 
> TestStringTemplate
>     [javac] ----------
>     [javac] 9. ERROR in 
> /build/user/stringtemplate-3.1/build/src/org/antlr/stringtemplate/test/TestStringTemplate.java
>  (at line 5231)
>     [javac]   fail("A parse error should have been generated");
>     [javac]   ^^^^
>     [javac] The method fail(String) is undefined for the type 
> TestStringTemplate
>     [javac] ----------
>     [javac] 9 problems (9 errors)
> 
> BUILD FAILED
> /build/user/stringtemplate-3.1/build.xml:125: Compile failed; see the 
> compiler error output for details.
> 
> Total time: 1 second
> make: *** [debian/stamp-ant-build] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2008/02/25

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 containing a sid i386
environment.  Internet was not accessible from the build systems.

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



--- End Message ---
--- Begin Message ---
Hi,

While rebuilding in the exact same conditions (except the chroot was
updated to current sid, of course), I could not reproduce the failure,
so the bug has probably been fixed by some changes in another package.

I'm closing this bug (or those bugs, since that mail was sent to all the
bugs in that case).

Lucas


--- End Message ---

Reply via email to