Bug 1857966
Summary: | javamail fails to build with java-11-openjdk | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | jiri vanek <jvanek> |
Component: | javamail | Assignee: | Stuart D Gathman <stuart> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | decathorpe, java-maint-sig, java-sig-commits, jkang, jvanek, mefoster, mizdebsk, sgehwolf, stuart |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-07-22 13:37:11 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1825969 |
Description
jiri vanek
2020-07-16 19:27:00 UTC
highlight: This was rebuild in sidetag f33-java11. Thus --target is really necessary to reproduce failure. please note: This side tag, f33-java11, will be merged to main f33 buildroot in aprox 14 days. Changes to a dependency were made to fix this build failure: https://src.fedoraproject.org/rpms/apache-commons-compress/c/19527f1155934f27376bf503c44bb3e71190cfbb?branch=master When I try to reproduce/test I see: $ fedpkg build --target f33-java11 Could not execute build: Package javamail-1.5.2-13.fc33 has already been built Note: You can skip this check with --skip-nvr-check. See help for more info. Should I add --skip-nvr-check? Is that safe? mock now uses java11 to build javamail, and it succeeds (with some warnings about implementing deprecated APIs). (In reply to Jie Kang from comment #2) > When I try to reproduce/test I see: > > $ fedpkg build --target f33-java11 > Could not execute build: Package javamail-1.5.2-13.fc33 has already been > built > Note: You can skip this check with --skip-nvr-check. See help for more info. > > > Should I add --skip-nvr-check? Is that safe? No. A single build can only exist once. The release would have to be bumped. Note that mbooth built it in f33 here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1540254 Mind you, its hard-coding to use java-1.8.0-openjdk for building. See below. If you want to reproduce the failure you'd likely need to revert this: https://src.fedoraproject.org/rpms/javamail/c/63f97136fecf964e791a9ad65604e28899b29526?branch=master and rebuild with --scratch (and possibly --srpm). Note: The --target f33-java11 is no longer needed as the f33-java11 builds got merged into f33. (In reply to Stuart D Gathman from comment #3) > mock now uses java11 to build javamail, and it succeeds (with some warnings > about implementing deprecated APIs). Are you sure it's using JDK 11 to build? https://src.fedoraproject.org/rpms/javamail/c/63f97136fecf964e791a9ad65604e28899b29526?branch=master and https://koji.fedoraproject.org/koji/buildinfo?buildID=1540254 suggests it's building with java-1.8.0-openjdk (hard coded). The logs indicate both JDKs are installed. JDK 8 is being selected as build JDK. Scratch build for latest master works: https://koji.fedoraproject.org/koji/taskinfo?taskID=47614124 As expected it's using JDK 8 to build: + export JAVA_HOME=/usr/lib/jvm/java-1.8.0 + JAVA_HOME=/usr/lib/jvm/java-1.8.0 + /usr/bin/python3 /usr/share/java-utils/mvn_build.py --xmvn-javadoc -- -Dmaven.test.failure.ignore=true Getting in to build without hard-coding is another matter. Closing this bug, though. |