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

Bug#1040925: marked as done (bookworm-pu: package ca-certificates-java/20230620~deb12u1)

Your message dated Sat, 07 Oct 2023 09:59:38 +0000
with message-id <E1qp45y-00A4AH-I6@coccia.debian.org>
and subject line Released with 12.2
has caused the Debian Bug report #1040925,
regarding bookworm-pu: package ca-certificates-java/20230620~deb12u1
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.)


-- 
1040925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040925
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian.org@packages.debian.org
Usertags: pu
X-Debbugs-Cc: Matthias Klose <doko@debian.org>

This request comes without a patch since I don't know how to properly
fix it in stable. But it definitively needs to be addressed for the
point release because the bookworm-security upload of openjdk-17 broke
the very fragile assumption in ca-certificates-java that a jre can be
used even before it was configured for the first time.

As a result new installations of openjdk-17-jre-headless from
bookworm-security (or -pu) (and its circular dependency
ca-certificates-java from bookworm) will fail, #1039472, (but
upgrades seem to work fine, since the jre has been configured at
least once in the past).

bookworm had the packages prepared to move the java certificate setup to
trigger processing (after the jre got configured) and break the
dependency loop, but in the end this was not activated before the
bookworm release. It is now enabled in sid.

I tried rebuilding the sid package for bookworm, but that is not
installable since it has Breaks against jre versions newer than what
is in bookworm-security. I'm not sure if the Breaks really need to be
that strict (because some new feature is being used) or whether they
could be relaxed for bookworm.


Andreas

--- End Message ---
--- Begin Message --- 
Version: 12.2

The upload requested in this bug has been released as part of 12.2.

--- End Message ---
Reply to: