Bug 2051215 - tzdata fails to build with java-17-openjdk
Summary: tzdata fails to build with java-17-openjdk
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: tzdata
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Patsy Griffin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2024265
TreeView+ depends on / blocked
 
Reported: 2022-02-06 15:57 UTC by jiri vanek
Modified: 2022-02-08 15:31 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-02-08 15:31:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jiri vanek 2022-02-06 15:57:20 UTC
tzdata fails to build with java-17-openjdk as sytem JDK. See https://fedoraproject.org/wiki/Changes/Java17 .
See especially part about known failures: https://fedoraproject.org/wiki/Changes/Java17#common_issues_packagers_can_face_and_gathered_solutions

For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82435206
https://kojipkgs.fedoraproject.org/work/tasks/5250/82435250/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/5250/82435250/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/5250/82435250/state.log
https://kojipkgs.fedoraproject.org/work/tasks/5250/82435250/build.log
https://kojipkgs.fedoraproject.org/work/tasks/5250/82435250/root.log
We run the rebuild in side tag f36-java17, but as fail ratio was small, we expect this side tag to be merged into rawhide 7 or 8 of February 2022.
To reproduce before this date simply: fedpkg clone tzdata; cd tzdata;  fedpkg build --target f36-java17; #The target is crucial.
After this date the usual fedpkg build in f36 and up should do.

We run two reruns your package failed both.

We had also run the mass rebuilds in copr since November. We keep all encountered failures. See them here: https://copr.fedorainfracloud.org/coprs/jvanek/java17//package/tzdata
You may find interesting additional informations here. Also we were spamming maintainers regualrly, check you spam folder.
              

We had tried aprox 500 packages, and aprox 65 had failed, so the java-17-openjdk will be system JDK in f36, and you should fix your package if you want to keep it alive. Usually the fix is simple, and best is to update the package to latest upstream version.
There will be usual mass rebuild once f36 branches. You may got another FTBFS bug.
Let us know here if you have any questions, here in bug, or at java-devel.org .

We'd appreciate help from the people who know this package best, but if you don't want to work on this now, let us know so we can try to work around it on our side if needed.

Comment 1 jiri vanek 2022-02-06 16:18:28 UTC
Initial fix should be trivial:

+ javac -source 1.6 -target 1.6 -classpath . ./rht/too...
warning: [options] bootstrap class path not set in conjunction with -source 6
error: Source option 6 is no longer supported. Use 7 or later.
error: Target option 6 is no longer supported. Use 7 or later.
RPM build errors:

Comment 2 jiri vanek 2022-02-08 15:29:01 UTC
to keep the legacy tzdata, now build requires both jdk8 and system jdk.
I recommend to put legacy tz data to separate subpkg or to drop them at all.

Also I would recomend to  rename legacy tzdat.to versioned ones (eg avazi-1.7) and to keep future, rolling tzdata unversioned, as javazionly


Note You need to log in before you can comment on or make changes to this bug.