Your message dated Sat, 23 Mar 2019 16:08:07 +0100 with message-id <[email protected]> and subject line closing remaining openjdk-6 bugs has caused the Debian Bug report #614176, regarding openjdk-6-jre-headless: binfmt deregistration on package removal broken 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.) -- 614176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614176 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: openjdk-7-jre-headless Version: 7~b147-2.0~pre6-1 Severity: normal I removed openjdk-6 some time ago, and just got the following on an upgrade of openjdk-7: <-- snip --> .... Setting up openjdk-7-doc (7~b147-2.0~pre6-1) ... Setting up openjdk-7-jre-headless (7~b147-2.0~pre6-1) ... Installing new version of config file /etc/java-7-openjdk/security/java.security ... update-binfmts: warning: current package is openjdk-7, but binary format already installed by openjdk-6 Setting up openjdk-7-jre-lib (7~b147-2.0~pre6-1) ... .... <-- snip --> The problem boils down to the following code in the prerm of openjdk-{6,7}-jre-headless: <-- snip --> .... if which update-binfmts >/dev/null; then # try to remove and ignore the error if [ -e /var/lib/binfmts/openjdk-7 ]; then update-binfmts --package openjdk-7 \ --remove jar /usr/bin/jexec || true fi fi .... <-- snip --> There is no /var/lib/binfmts/openjdk-{6,7}, instead there is a /var/lib/binfmts/jar . And I wonder why there are not (anymore?) version specific files: A common sequence when installing a new Java version is to first install the new version (so that dependencies are always fulfilled) and then remove the obsolete old version. If I understand that correctly, this leaves users without binfmt registration? And when this happens during an upgrade from oldstable to stable, the binfmt registration might not happen until the upgrade to the next stable release (or a DSA for OpenJDK). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---Version: 6b41-1.13.13-1+rm Hi, openjdk-6 was last released with Debian 7.0 (wheezy), which had its LTS support end nearly a year ago and which has now been archived. I'm therefore closing the remaining openjdk-6 bugs, assuming they are no longer relevant for newer (and still supported) openjdk releases. Andreas
--- End Message ---
