[Piuparts-devel] Bug#635449: Will troubleshoot ...

Scott Schaefer saschaefer at neurodiverse.org
Tue Jul 26 01:14:41 UTC 2011


I am fairly certain the problem is actually in openjdk-6-jre-headless 
(6b18-1.8.7-5) package ...

Warning: last time I tried to troubleshoot piuparts problem, I was 
"wrong in several ways".  So, consider analysis below accordingly.


 From eclipse-cdt log:

Setting up openjdk-6-jre-headless (6b18-1.8.7-5) ...
   update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/java 
to provide /usr/bin/java (java) in auto mode.
   update-alternatives: using 
/usr/lib/jvm/java-6-openjdk/jre/bin/keytool to provide /usr/bin/keytool 
(keytool) in auto mode.
   update-alternatives: using 
/usr/lib/jvm/java-6-openjdk/jre/bin/pack200 to provide /usr/bin/pack200 
(pack200) in auto mode.
   update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/rmid 
to provide /usr/bin/rmid (rmid) in auto mode.
   update-alternatives: using 
/usr/lib/jvm/java-6-openjdk/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode.
   update-alternatives: using 
/usr/lib/jvm/java-6-openjdk/jre/bin/unpack200 to provide 
/usr/bin/unpack200 (unpack200) in auto mode.
   update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/bin/orbd 
to provide /usr/bin/orbd (orbd) in auto mode.
   update-alternatives: using 
/usr/lib/jvm/java-6-openjdk/jre/bin/servertool to provide 
/usr/bin/servertool (servertool) in auto mode.
   update-alternatives: using 
/usr/lib/jvm/java-6-openjdk/jre/bin/tnameserv to provide 
/usr/bin/tnameserv (tnameserv) in auto mode.
   update-alternatives: using /usr/lib/jvm/java-6-openjdk/jre/lib/jexec 
to provide /usr/bin/jexec (jexec) in auto mode.

THIS IS THE ROOT CAUSE OF THE PROBLEM
************
   update-binfmts: warning: Couldn't load the binfmt_misc module.
************

The last version of this package that was tested by piuparts was version 
6b18-1.8.7-2.  It passed.  Now, the newer package is failing when it is 
installed as dependency of newly-tested package(s), causing (misleading) 
failure report.  Yes; piuparts SHOULD be made smart enough to examine 
version #; however, that's a somewhat low priority.

However, 6b18-1.8.7-5 is new in testing.  Examining the diff 
(openjdk-6_6b18-1.8.7-5.diff.gz from testing source packge) between the 
1.8.7-2 and 1.8.7-5 shows that there are a significant # of changes 
relating to update-binfmt.

Indeed, one of the additions is:

--------------------
openjdk-6-6b18-1.8.7/debian/JB-jre-headless.overrides.in
..
...
+# empty directory by intent
+ at basename@-jre-headless binary: package-contains-empty-directory 
usr/share/binfmts/
--------------------


We could probably verify this by scanning logs of recently-tested failed 
packages vs. 'successful' ones with dependency of openjdk.  However, 
that requires access to piatti logs; IMHO, it's not worth effort to do 
this via http, and I don't have other, better access.

It is poor timing, since Holger and others who may be able to help are 
at Debconf.







More information about the Piuparts-devel mailing list