Your message dated Wed, 06 Jun 2018 12:21:46 +0000
with message-id <[email protected]>
and subject line Bug#893849: fixed in java-common 0.67
has caused the Debian Bug report #893849,
regarding default-jre: Recommends default-java-plugin, which is no longer built
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.)


-- 
893849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893849
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: default-jre
Version: 2:1.9-62
Severity: important

default-jre 2:1.9-62 still has:

  Recommends: default-java-plugin

but default-java-plugin is no longer built.

Because of that, aptitude refuses to upgrade default-jre without
a manual intervention:

The following packages depend on version 2:1.8-59 of default-jre, and will be  ▒
broken if it is upgraded.                                                      ▒
                                                                               ▒
  * default-java-plugin (held/unchanged, 2:1.8-59) depends on default-jre (=   ▒
    2:1.8-59)                                                                  ▒

(I suppose that aptitude doesn't try to remove the automatically
installed default-java-plugin package because it would break a
Recommends, as signaled by the second resolution choice.)

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages default-jre depends on:
ii  default-jre-headless  2:1.9-62
ii  openjdk-9-jre         9.0.4+12-2

Versions of packages default-jre recommends:
pn  default-java-plugin  <none>

default-jre suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: java-common
Source-Version: 0.67

We believe that the bug you reported is fixed in the latest version of
java-common, 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.
Emmanuel Bourg <[email protected]> (supplier of updated java-common 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: SHA512

Format: 1.8
Date: Wed, 06 Jun 2018 14:02:34 +0200
Source: java-common
Binary: java-common default-jre default-jre-headless default-jdk 
default-jdk-headless default-jdk-doc
Architecture: source
Version: 0.67
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 
<[email protected]>
Changed-By: Emmanuel Bourg <[email protected]>
Description:
 default-jdk - Standard Java or Java compatible Development Kit
 default-jdk-doc - Standard Java or Java compatible Development Kit 
(documentation)
 default-jdk-headless - Standard Java or Java compatible Development Kit 
(headless)
 default-jre - Standard Java or Java compatible Runtime
 default-jre-headless - Standard Java or Java compatible Runtime (headless)
 java-common - Base package for Java runtimes
Closes: 893849 897039
Changes:
 java-common (0.67) unstable; urgency=medium
 .
   * Team upload.
   * Added riscv64 to the list of Java 10 architectures (Closes: #897039)
   * default-jre no longer suggest default-java-plugin (Closes: #893849)
Checksums-Sha1:
 5a55a9c6023db2a3db5a4764628ba84534677a1a 1985 java-common_0.67.dsc
 d3603c6c3bdfa7c6be22f939da12ea7f3132ec8e 13000 java-common_0.67.tar.xz
 83223258a1ef2ef8593b6d9044a224069ee60be8 5856 java-common_0.67_source.buildinfo
Checksums-Sha256:
 c1ec68dd9663ea72165afc7d471e73fcd58f4d9016497af47c4f22d4d94b039f 1985 
java-common_0.67.dsc
 b16e4532122f75d39cfacddc4df29dba43f4e66f5a4188ed926dbf5ff40758b9 13000 
java-common_0.67.tar.xz
 35741da3b185f9462bec253408e3dc8797dbbdef27b10d9f09d6ef2baffb8b61 5856 
java-common_0.67_source.buildinfo
Files:
 a9cde2bef85712aba01ae9414d4ed90f 1985 java optional java-common_0.67.dsc
 b097bdbddc73d0c90ca9716c3829063c 13000 java optional java-common_0.67.tar.xz
 b0f22da82fb5c380911b9e21e825a129 5856 java optional 
java-common_0.67_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlsXzaMSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCscKMP/2k9w/rGR01EYSY3e6IS0PURqHfb0OUx
pYVnQLk5Yqpb1oHwx7n/AJLhgQ/4t4rXEHv27Zpu5CXnVIgP5LEDC6nrs5jpZ4fG
ql3+fPkIRCQjVzP/mlP7bbhmrjIlE2nQVohYLy5M10Jymo8UCyxinBmy7UP9GC0v
XrP9rckTE9fR2NjZeT64PQ7m61TJ6uKv2L8bjKykgQPt6X9zMF/DL/KC6/v3+PXk
K5wUPbe7uU3HNcuCPgNG9hk/ltmlqYVawRNrbd11Xoh8RTaSxCCgPhnsJ2Zje5Wa
jPqjya8JxlyzNB94ek664NS7QkPJICPUaDsuO2oDI4chFpoGI+9hSjWEgc5Khgyq
WZiyv35hwlZ3uKiySaoMWhyIKRumFhLmkbPiA0TsycFYFfPWlofES/kx9mFYoZzA
k6jCglHbgtTWlZm8FoKu+Fyj8CH8Ixu3QLl1OcM1SvuocL6tuJ7kHo72m3LCs6Sk
oHsofJy5w9rzrdmiQSdaO7E4hkp+chyRop0m8au9Gc2alAd3AUMMPpZCHD8+70zG
Be3EUwoRR8qP2bEOhceqWq2zkonq3NOlyHJdTsa+sAzrRRBmhSE8mjJvw2n3IfCj
r499Sis2YUFZLVW4MWEXnTNTsbbfQRHv4k749Omkhbv8gnejayFL8ZHUoQ7GsdYc
VvoFbDmO+3un
=JyAL
-----END PGP SIGNATURE-----

--- End Message ---
__
This is the maintainer address of Debian's Java team
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
 Please use
[email protected] for discussions and questions.

Reply via email to