Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

From the attached log (scroll to the bottom...):

  Setting up default-jre-headless (2:1.7-52) ...
  Setting up yui-compressor (2.4.7-2) ...
  Setting up libjs-protoaculous (5) ...
  [warning] /usr/bin/yui-compressor: No java runtime was found
  [warning] /usr/bin/yui-compressor: No JAVA_CMD set for run_java, falling back to JAVA_CMD = java
  readlink: missing operand
  Try 'readlink --help' for more information.
  /usr/bin/yui-compressor: 304: exec: java: not found
  dpkg: error processing package libjs-protoaculous (--configure):
   subprocess installed post-installation script returned error exit status 127
  Processing triggers for ca-certificates (20141019+deb8u3) ...
  Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d....
  done.
  done.
  Setting up openjdk-7-jre-headless:amd64 (7u181-2.6.14-1~deb8u1) ...
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmid to provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java to provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/keytool to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/pack200 to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/rmiregistry to provide /usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/unpack200 to provide /usr/bin/unpack200 (unpack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/orbd to provide /usr/bin/orbd (orbd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/servertool to provide /usr/bin/servertool (servertool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/tnameserv to provide /usr/bin/tnameserv (tnameserv) in auto mode
  update-alternatives: using /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jexec to provide /usr/bin/jexec (jexec) in auto mode
  Processing triggers for libc-bin (2.19-18+deb8u10) ...
  Processing triggers for systemd (215-17+deb8u7) ...
  Errors were encountered while processing:
   libjs-protoaculous


cheers,

Andreas

Hi Andreas,

The version of the package in the bug is found in jessie (oldstable)
and doesn't exist in stretch (stable) or buster (testing).  Also, I
believe the problem is with the version of default-jre-headless in
jessie, given that the Depends hasn't changed since 2012.

Are you requesting that the bug be addressed for jessie?  (Do we need to
open a RC-severity bug for oldstable right before the buster freeze?)

Thanks,
tony

Contol: severity -1 normal

Bugs in Jessie not affecting Buster are not release critical.

severity 919917 serious
found 919917 2.4.8-2.1
found 919917 libjs-protoaculous/5+nmu1
thanks

hi,

quoting from https://piuparts.debian.org/sid/fail/libjs-protoaculous_5+nmu1.log
(also attached)

Setting up yui-compressor (2.4.8-2.1) ...
  Setting up libjs-protoaculous (5+nmu1) ...
  [warning] /usr/bin/yui-compressor: No java runtime was found
  [warning] /usr/bin/yui-compressor: No JAVA_CMD set for run_java, falling back to JAVA_CMD = java
  readlink: missing operand
  Try 'readlink --help' for more information.
  /usr/bin/yui-compressor: 304: exec: java: not found
  dpkg: error processing package libjs-protoaculous (--configure):
   installed libjs-protoaculous package post-installation script subprocess returned error exit status 127

Thus the severity raise.

Hi Holger,

I'm pretty sure that this is caused by the circular dependency beween
ca-certificates-java, default-jre-headless and openjdk-11-jre-headless, and
isn't actually a bug in yui-compressor
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929685

Cheers,

Ivo