Hi Olek,
> I added that in an attempt to override the incorrect flag, but instead
> they are both emitted which still causes the error.
Sorry for the misleading.
I forgot that the "flaky Java autopkgtests" has been disabled. :-)
Yes, It failed once I tried to enable the "java-1-hello" test.
>>
On Thu, 23 Feb 2023, sun min wrote:
>It seems that the build system's local jdk overrides those jvm
>parameters we defined in bazelrc or bashsrcript.
How about asking Doko to locally add that parameter to 17 as a
Debian-specific patch, just ignoring it?
(And, ideally, warning.)
bye,
//mirabilos
Le 2023-02-23 12:48, Thorsten Glaser a écrit :
How about asking Doko to locally add that parameter to 17 as a
Debian-specific patch, just ignoring it?
Patching the JDK is overkill, it's just a flag to change in a script.
The question is, where is this script?
Emmanuel Bourg
On Thu, 23 Feb 2023, Vladimir Petko wrote:
>Notice that ca-certificates-java attempts to process triggers before
>default-jre is set up. This is exactly the condition we are trying to
>avoid.
It should run them again, and there’s got to be a way, but I’m
not a triggers expert and currently ill, p
Hi,
This is possible to do if we update openjdk packaging and make it
trigger certificates-ca-java, so that it always runs after the openjdk
package is installed and remove postinstall update from
ca-certificates-java altogether. This will work, but we might get
several trigger calls in a row if m
On Fri, 24 Feb 2023, Vladimir Petko wrote:
>This is possible to do if we update openjdk packaging and make it
>trigger certificates-ca-java, so that it always runs after the openjdk
We can do that easily. I maintain 8 and doko the rest (I hope).
If that’s needed, i.e. if there’s no other way, th
Hi,
Thank you very much for the advice
I have tested this approach [1] and it looks good - the trigger is
called after update-alternatives in the postinstall script of the
jre-headless and this guarantees that we have a working java when we
try to import certificates.
Libreoffice has no prob
On Fri, 24 Feb 2023, Vladimir Petko wrote:
>The issue is the migration procedure - those packages have to be
>published together to avoid any nasty surprises.
Yeah, we’ll have to pick a time to do that, which is after
the bookworm release anyway (it’s not okay to upload things
to unstable right n
8 matches
Mail list logo
