On further investigation, the main difference from a previous successful build
log is:

...
Trying patch debian/patches/01_ant_home_path.patch at level 1...0...success.
Trying patch debian/patches/01_gjdoc_task.patch at level 1...0...success.
Trying patch debian/patches/01_javadoc_maxmemory.patch at level 1...0...success.
Trying patch debian/patches/02_ant_add_xerces.patch at level 1...0...success.
Trying patch debian/patches/03_SplashTaskPatch_a.patch at level 1...success.
Trying patch debian/patches/03_SplashTaskPatch_b.patch at level 1...0...success.
Trying patch debian/patches/03_SplashTaskPatch_c.patch at level 1...0...success.
Trying patch debian/patches/04_UUMailerReflection.patch at level 
1...0...success.
Trying patch debian/patches/05_TaskAvailabilityFix_ANT_PR38260.patch at level 
1...0...success.

So 03_SplashTaskPatch_a is getting applied with the wrong patchlevel.
-- 
Daniel Schepler


_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Reply via email to