Bug 25460

Summary: java-1.8.0-openjdk-headless install fails
Product: Mageia Reporter: Jani Välimaa <jani.valimaa>
Component: RPM PackagesAssignee: All Packagers <pkg-bugs>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: ouaurelien
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: java-1.8.0-openjdk-1.8.0.222-1.b10.2.mga8 CVE:
Status comment:

Description Jani Välimaa 2019-09-22 08:48:00 CEST
installing java-1.8.0-openjdk-headless-1.8.0.222-1.b10.2.mga8.x86_64.rpm from /var/cache/urpmi/rpms
error: lua script failed: [string "%pretrans(java-1.8.0-openjdk-headless-1:1.8.0..."]:27: attempt to concatenate a nil value (field 'path')
ERROR: 'script' failed for 
Preparing...                     #############################################
error: java-1.8.0-openjdk-headless-1:1.8.0.222-1.b10.2.mga8.x86_64: install skipped
Comment 1 Lewis Smith 2019-09-22 19:44:14 CEST
Thanks Jani for the alert.
This looks like an issue with the Cauldron version cited above, for I have (presumably like everybody on M7)
 java-1.8.0-openjdk-headless-1.8.0.222-1.b10.1.mga7
                                            ***
Assigning to Nicolas for java-1.8.0-openjdk-1.8.0.222-1.b10.1.mga7.src.rpm

Assignee: bugsquad => mageia

Comment 2 Jani Välimaa 2019-09-24 17:44:23 CEST
I can't reproduce this always. It looks like the installing order and transaction size matters.
David Walser 2019-10-18 20:58:42 CEST

Assignee: mageia => nicolas.salguero

Comment 3 Aurelien Oudelet 2020-11-10 17:23:40 CET
A new update for java-1.8.0-openjdk is on its way in updates_testing.
It will soon be pushed.
Can you test this behaviour on these packages?

CC: (none) => ouaurelien

Nicolas Salguero 2021-01-20 15:40:52 CET

Assignee: nicolas.salguero => pkg-bugs

Comment 4 Aurelien Oudelet 2021-01-20 15:50:59 CET
Package installs well in M7.1 and in M8 from upgrade of a M7 system.

But, it is not installed by default on new M8 install, as the preferred JVM is java11 on such systems.

We will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Resolution: (none) => OLD
Status: NEW => RESOLVED