Your message dated Mon, 05 Sep 2016 22:27:41 +0000
with message-id <[email protected]>
and subject line Bug#788445: fixed in openjdk-9 9~b134-2
has caused the Debian Bug report #788445,
regarding src:openjdk-9: leaves alternatives after purge
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.)
--
788445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788445
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:openjdk-9
Version: 9~b64-1
Severity: important
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8:
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails
The leftover files are actually alternatives that were installed by the
package but have not been properly removed.
While there is ongoing discussion how to remove alternatives correctly
(see https://bugs.debian.org/71621 for details) the following strategy
should work for regular cases:
* 'postinst configure' always installs the alternative
* 'prerm remove' removes the alternative
* 'postrm remove' and 'postrm disappear' remove the alternative
In all other cases a maintainer script is invoked (e.g. upgrade,
deconfigure) the alternatives are not modified to preserve user
configuration.
Removing the alternative in 'prerm remove' avoids having a dangling link
once the actual file gets removed, but 'prerm remove' is not called in
all cases (e.g. unpacked but not configured packages or disappearing
packages) so the postrm must remove the alternative again
(update-alternatives gracefully handles removal of non-existing
alternatives).
Note that the arguments for adding and removing alternatives differ, for
removal it's 'update-alternatives --remove <name> <path>'.
Filing this as important as having a piuparts clean archive is a release
goal since lenny.
Several packages built from src:openjdk-9 leave alternatives around,
e.g. openjdk-9-jre-headless:
>From the attached log (scroll to the bottom...):
1m23.2s INFO: Warning: Package purging left files on system:
/etc/alternatives/java-rmi.cgi ->
/usr/lib/jvm/java-9-openjdk-amd64/bin/java-rmi.cgi not owned
/etc/alternatives/jjs -> /usr/lib/jvm/java-9-openjdk-amd64/bin/jjs not
owned
/etc/alternatives/jjs.1.gz ->
/usr/lib/jvm/java-9-openjdk-amd64/man/man1/jjs.1.gz not owned
/etc/alternatives/jstatd -> /usr/lib/jvm/java-9-openjdk-amd64/bin/jstatd
not owned
/etc/alternatives/jstatd.1.gz ->
/usr/lib/jvm/java-9-openjdk-amd64/man/man1/jstatd.1.gz not owned
/usr/bin/java-rmi.cgi -> /etc/alternatives/java-rmi.cgi not owned
/usr/bin/jjs -> /etc/alternatives/jjs not owned
/usr/bin/jstatd -> /etc/alternatives/jstatd not owned
/usr/lib/jvm/java-9-openjdk-amd64/ owned by: openjdk-9-jre-headless:amd64
/usr/lib/jvm/java-9-openjdk-amd64/lib/ owned by:
openjdk-9-jre-headless:amd64
/usr/lib/jvm/java-9-openjdk-amd64/lib/amd64/ owned by:
openjdk-9-jre-headless:amd64
/usr/lib/jvm/java-9-openjdk-amd64/lib/amd64/server/ owned by:
openjdk-9-jre-headless:amd64
/usr/lib/jvm/java-9-openjdk-amd64/lib/amd64/server/classes.jsa not
owned
/usr/share/man/man1/jjs.1.gz -> /etc/alternatives/jjs.1.gz not owned
/usr/share/man/man1/jstatd.1.gz -> /etc/alternatives/jstatd.1.gz not
owned
/usr/lib/jvm/java-9-openjdk-amd64/lib/amd64/server/classes.jsa
is not an alternative, but left anyway.
openjdk-9-jre has many more alternatives and also a directory left in /etc:
/etc/java-6-sun/
that should be shipped by the package (or not being created at all)
cheers,
Andreas
openjdk-9-jre-headless_9~b64-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b134-2
We believe that the bug you reported is fixed in the latest version of
openjdk-9, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthias Klose <[email protected]> (supplier of updated openjdk-9 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 05 Sep 2016 14:14:01 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg
openjdk-9-jre-zero
Architecture: source
Version: 9~b134-2
Distribution: experimental
Urgency: medium
Maintainer: OpenJDK Team <[email protected]>
Changed-By: Matthias Klose <[email protected]>
Description:
openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
openjdk-9-jdk - OpenJDK Development Kit (JDK)
openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 788445
Changes:
openjdk-9 (9~b134-2) experimental; urgency=medium
.
* Build using GCC 6.
* Enable zero build on arm64 and ppc64el.
* Increase thread stack size for ppc* zero builds.
* Don't use Solaris compiler flags on sparc64.
* Port x32 zero patch.
* Don't use the just built jdk for zero builds.
* Don't use getFileStore() during the build, chroots throw an
exception while running jlink.
* Fix removal of jre-headless alternatives. Closes: #788445.
Checksums-Sha1:
417350c04efa961debfce873354fd80234dd644f 4351 openjdk-9_9~b134-2.dsc
26f999c4bb0b2ae0cfa7c03169907641d20b3a84 188876
openjdk-9_9~b134-2.debian.tar.xz
Checksums-Sha256:
8d883f1fec30b32ed89be8b5da190ec9b6aea1b540c1c06f87afda697c56737b 4351
openjdk-9_9~b134-2.dsc
7b351a6ecd3b7ffd8248388dbb7511bfaa2d041495007feedc6dfb27874f8d90 188876
openjdk-9_9~b134-2.debian.tar.xz
Files:
137a29aad07404db950f5ff51c4eb49a 4351 java optional openjdk-9_9~b134-2.dsc
40c7502d6c3e75ad125759b0c442700b 188876 java optional
openjdk-9_9~b134-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQItBAEBCAAXBQJXzdJMEBxkb2tvQHVidW50dS5jb20ACgkQvX6qYHePpvXyRA//
a2ZHzgFquKjBfWm2vheIu1Hmcprz33UwVaiVXLkWe0RA/l0OD7G0I7AzC8ni3CD1
nCD4d9m8fzuKy3GDV+YfzGwDxoQeGNlihS34Mhc3APn0Kp3B5l0yIq9Pm5Rb9P26
uik63U6l67ubZcGiju99t776Ncqgi8zDk+K3XR1aJa01ejhWB7FEoafc56xnH5oR
4recaLRJmZyjwSLFPwqCERvyIlTvzHqmPxpbYQU3JxxtVCALuMPnLFuTnDo4LPBf
ss3LBOogBSo2MxcqEm9LZAWUjaROlGiT7K1X52IMSwaAwvEoKdToeiNWUHN5xosk
IIjvr1LNQwCxWaS+p9F0CKhSvL9k2nnBCFqsS/P3ndR0E2WRtsUl/wJj13DjNO+P
0amxF4gPotyP/3CyBkM7gfRhohwGcaUXO8J1hTU1RnU4fPX2TTrDBfBDZmt1ucIF
3yNEBkmydOgVZrirgD1fibb0r7Fd8yAz9dI6wFylyVpZfZr7kcVEn3SV6jNEVvLX
M++c7CApBzXf2oZ5KHHkLGCSgVnp1lWNjN2DeTAMXgzu8spw7OX7RpaumVmIx5Od
kqqRZClWws77gTK+VhANUO88UCnmMXaVoOXHYuuqwzD24IRH7sG5v7HdgQ//dTae
j/5UJSQmd2OhkGtlODQMGo0eJ0IWnJ7q+5KYFABj0Eg=
=h15K
-----END PGP SIGNATURE-----
--- End Message ---
