error checking jars with same content -- looking for user input #53

deanmalmgren opened this Issue Aug 21, 2012 · 1 comment


None yet

2 participants


I am using the 0.2.5 script from here on an Ubuntu 10.04 (2.6.32-38 x86_64) machine to build the java6 package and I'm running into an error while building:

[x] Installing Java build requirements success
[x] Making build directories success
[x] Removing clones of success
[x] Cloning success
[x] Checking out v6.34-1 success
[x] Getting Java SE download page success
[x] Getting current release download page success
[x] Downloading jdk-6u34-linux-i586.bin : 68.43 MB success
[x] Symlinking jdk-6u34-linux-i586.bin success
[x] Downloading jdk-6u34-linux-x64.bin : 68.7 MB success
[x] Symlinking jdk-6u34-linux-x64.bin success
[x] Getting Java Cryptography Extension download page success
[x] Downloading : 8.89 KB success
[x] Symlinking success
[x] Updating the changelog success
[x] Building the packages success

ERROR! Packages failed to build.

The last few lines of the log file are:

: # check for jars with the same content
set -e; \
    for j in jre/lib/ext/dnsns.jar jre/lib/ext/localedata.jar jre/lib/im/indicim.jar jre/lib/im/thaiim.jar jre/lib/charsets.jar jre/lib/management-agent.jar jre/lib/plugin.jar jre/lib/resources.jar jre/lib/javaws.jar jre/lib/deploy.jar jre/lib/alt-rt.jar jre/lib/alt-string.jar ; do \
      echo "  Comparing $j ..."; \
      d=${j%*.jar}; \
      set -- i586 x64; a1=$1; shift; \
      mkdir -p tmp-$a1/$d; \
      unzip -q -d tmp-$a1/$d $a1-jdk/$j; \
      for a2; do \
        mkdir -p tmp-$a2/$d; \
        unzip -q -d tmp-$a2/$d $a2-jdk/$j; \
        if diff -ur tmp-$a1/$d tmp-$a2/$d; then \
          echo "    OK"; \
        else \
          echo "    differ"; \
          badjars="$badjars $j ($a1, $a2)"; \
        fi; \
      done; \
    done; \
    if [ -n "$badjars" ]; then \
      echo "Differing jar files: $badjars"; \
      exit 1; \
  Comparing jre/lib/ext/dnsns.jar ...
replace tmp-i586/jre/lib/ext/dnsns/META-INF/MANIFEST.MF? [y]es, [n]o, [A]ll, [N]one, [r]ename:  NULL
(EOF or read error, treating as "[N]one" ...)
make: *** [unpack-stamp] Error 1
dpkg-buildpackage: error: debian/rules binary gave error exit status 2 29834's retcode: 2

This was working for me a few days ago on a different machine. Is there something in my environment setup that is causing it to ask about replacing this file during the dpkg-buildpackage (version execution? I'm happy to help debug/write patches/submit pull requests to get this fixed if someone that knows more can point me in the right direction.


I've just test with Lucid, Precise and Raring and everything is working correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment