[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#928493: marked as done (stretch-pu: package java-common/0.58+deb9u2)



Your message dated Sun, 26 Apr 2020 18:24:54 +0200
with message-id <20200426162454.GA13235@chou>
and subject line Re: Bug#928493: stretch-pu: package java-common/0.58+deb9u2
has caused the Debian Bug report #928493,
regarding stretch-pu: package java-common/0.58+deb9u2
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 owner@bugs.debian.org
immediately.)


-- 
928493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928493
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian.org@packages.debian.org
Usertags: pu

Hi,

the recent updates to openjdk-8, java-common (and related packages) in
stretch made some upgrade issues surface (either they were hidden behind
now fixed issues or they appeared due to changed scores computed by
apt).

openjdk-7/jessie and openjdk-8/stretch are not co-installable (via some
transitive Breaks involving tzdata-java), but on some upgrade paths apt
does not compute this correctly and prefers to keep openjdk-7 installed
instead of switching to openjdk-8.
Adding an explicit Breaks: openjdk-7-jre-headless to
default-jre-headless seems to push apts scores into the right direction
for all the cases I tested.

Andreas
diff -Nru java-common-0.58+deb9u1/debian/changelog java-common-0.58+deb9u2/debian/changelog
--- java-common-0.58+deb9u1/debian/changelog	2019-03-25 21:49:32.000000000 +0100
+++ java-common-0.58+deb9u2/debian/changelog	2019-05-04 16:06:57.000000000 +0200
@@ -1,3 +1,11 @@
+java-common (0.58+deb9u2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * default-jre-headless: Add Breaks: openjdk-7-jre-headless for smoother
+    upgrades from jessie.
+
+ -- Andreas Beckmann <anbe@debian.org>  Sat, 04 May 2019 16:06:57 +0200
+
 java-common (0.58+deb9u1) stretch; urgency=medium
 
   * Remove default-java-plugin as the icedtea-web Xul plugin is going away
diff -Nru java-common-0.58+deb9u1/debian/control java-common-0.58+deb9u2/debian/control
--- java-common-0.58+deb9u1/debian/control	2019-03-25 21:49:32.000000000 +0100
+++ java-common-0.58+deb9u2/debian/control	2019-05-04 16:06:57.000000000 +0200
@@ -35,6 +35,7 @@
 Suggests: default-jre
 Provides: ${jhl:provides}
 Replaces: openjdk-6-jre-headless (<< 6b23~pre8-2~)
+Breaks: openjdk-7-jre-headless
 Description: Standard Java or Java compatible Runtime (headless)
  This dependency package points to the Java runtime, or Java compatible
  runtime recommended for this architecture, which is

--- End Message ---
--- Begin Message ---
Hi Andreas,

On Mon, May 06, 2019 at 03:00:46AM +0200, Andreas Beckmann wrote:
> Package: release.debian.org
> Severity: normal
> Tags: stretch
> User: release.debian.org@packages.debian.org
> Usertags: pu
> 
> Hi,
> 
> the recent updates to openjdk-8, java-common (and related packages) in
> stretch made some upgrade issues surface (either they were hidden behind
> now fixed issues or they appeared due to changed scores computed by
> apt).
> 
> openjdk-7/jessie and openjdk-8/stretch are not co-installable (via some
> transitive Breaks involving tzdata-java), but on some upgrade paths apt
> does not compute this correctly and prefers to keep openjdk-7 installed
> instead of switching to openjdk-8.
> Adding an explicit Breaks: openjdk-7-jre-headless to
> default-jre-headless seems to push apts scores into the right direction
> for all the cases I tested.
> 
I don't think we should mess with the upgrade path now (and generally
post release unless things are genuinely broken).  Users can notice
packages being held back and manually sort them out.

Cheers,
Julien

--- End Message ---

Reply to: