Bug 2109048

Summary: relative symlinks are breaking cjc
Product: [Fedora] Fedora Reporter: jiri vanek <jvanek>
Component: java-latest-openjdkAssignee: jiri vanek <jvanek>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 37CC: ahughes, jerboaa, jvanek, pmikova
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-12-05 21:12:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jiri vanek 2022-07-20 10:36:02 UTC
https://src.fedoraproject.org/rpms/java-latest-openjdk/c/f206f3a913ea440f99ef441b70cabd3ef18383ad

had introduced relative symlinks, instead of absolute one, to enable test in %check.
This have actually caulsed CJC to stop working (as it crawls only through absolute symlinks) and thus is casuing config files in jdk no longer updating

The symlinks myust be reverted back to absolute, the $check workarounded and cjc investigated why it crawls through absolute symlinks only. Jdk17 is also affected, jadk11 and 8 should be not

Comment 1 jiri vanek 2022-07-20 10:38:08 UTC
see also https://bugzilla.redhat.com/show_bug.cgi?id=2109050

Comment 3 Andrew John Hughes 2022-08-01 15:41:37 UTC
I don't believe this is a bug in the JDK packages. We reverted the fix in RHEL due to the immediacy of the release, not because of a fault in the change. I would still like to bring this change to RHEL and the older JDKs. I think it is important that our RPM tests are testing what we ship as closely as possible. There are other advantages too; this means the RPM can be extracted and the contents used without having to install it on a system and displace an existing JDK, which is helpful for debugging purposes. With an absolute symlink, such a deployment would either have broken symlinks or use configuration from the system rather than what is part of the RPM.

Note that this worked before the configuration files were moved into /etc and relative symlinks are already used for the debuginfo, which is where I got the idea.

I would like to hear why copy-java-configs has an issue with relative symlinks before considering reverting this change. If we must keep absolute symlinks, we need to find an alternate way of testing RPMs. At present, it sounds to me as if copy-java-configs is the only application that has a problem with these symlinks and no-one even knows why it skips them.

Comment 4 Ben Cotton 2022-08-09 13:22:39 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.

Comment 5 Aoife Moloney 2023-11-23 00:15:58 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 6 Aoife Moloney 2023-12-05 21:12:02 UTC
Fedora Linux 37 entered end-of-life (EOL) status on None.

Fedora Linux 37 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.