Bug 2114533
| Summary: | gnulib: FTBFS in Fedora rawhide/f37: javac: command not found | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Release Engineering <releng> | ||||||||
| Component: | gnulib | Assignee: | Mosaab Alzoubi <moceap> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 37 | CC: | michel, moceap, ppisar, zbyszek | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | i686 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | gnulib-0-47.20230709git.fc38 gnulib-0-47.20230709git.el9 gnulib-0-47.20230709git.el8 gnulib-0-47.20230709git.fc37 | Doc Type: | If docs needed, set a value | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2023-07-18 01:24:04 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: | 2045102, 2117176, 2168842, 2183558 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Fedora Release Engineering
2022-08-02 19:39:39 UTC
Created attachment 1903011 [details]
build.log
file build.log too big, will only attach last 32768 bytes
Created attachment 1903012 [details]
root.log
file root.log too big, will only attach last 32768 bytes
Created attachment 1903013 [details]
state.log
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37. From an i668 build.log: make[1]: Leaving directory '/builddir/build/BUILD/gnulib-9f48fb9/build-tests' + popd ~/build/BUILD/gnulib-9f48fb9 + javac -d lib -source 11 -target 11 lib/javaversion.java /var/tmp/rpm-tmp.ZirDsD: line 146: javac: command not found error: Bad exit status from /var/tmp/rpm-tmp.ZirDsD (%build) From current i686 root.log:
DEBUG util.py:540: Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '128d855c93604f63b35bbaa0f315fe3b', '-D', '/var/lib/mock/f39-build-42349507-5146353-bootstrap/root', '-a', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.81_l5xnc:/etc/resolv.conf', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/var/lib/mock/f39-build-42349507-5146353/root/installation-homedir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--setenv=LC_MESSAGES=C.UTF-8', '--resolv-conf=off', '/usr/bin/dnf', 'builddep', '--installroot', '/var/lib/mock/f39-build-42349507-5146353/root/', '--setopt=install_weak_deps=0', '--disableplugin=local', '--disableplugin=spacewalk', '--disableplugin=versionlock', '/var/lib/mock/f39-build-42349507-5146353/root//builddir/build/SRPMS/gnulib-0-45.20220212git.fc39.src.rpm', '--setopt=tsflags=nocontexts'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/var/lib/mock/f39-build-42349507-5146353/root/installation-homedir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'LC_MESSAGES': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
DEBUG util.py:443: No matches found for the following disable plugin patterns: local, spacewalk, versionlock
DEBUG util.py:443: No matching package to install: 'java-devel'
DEBUG util.py:443: Not all dependencies satisfied
DEBUG util.py:443: Error: Some packages could not be found.
DEBUG util.py:596: Child return code was: 1
*** This bug has been marked as a duplicate of bug 2104044 *** FEDORA-2023-ce173a82f9 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ce173a82f9 FEDORA-EPEL-2023-e5e251ea3d has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e5e251ea3d FEDORA-2023-c193e7171c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c193e7171c FEDORA-2023-c193e7171c has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c193e7171c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c193e7171c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-e5e251ea3d has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e5e251ea3d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-ce173a82f9 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-ce173a82f9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ce173a82f9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-730b82bd39 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-730b82bd39 FEDORA-2023-1ebd33e0c1 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1ebd33e0c1 FEDORA-2023-730b82bd39 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-730b82bd39` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-730b82bd39 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-0a9e760449 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-0a9e760449 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2023-7159543bbd has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7159543bbd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-1ebd33e0c1 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1ebd33e0c1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1ebd33e0c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-1ebd33e0c1 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-0a9e760449 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-EPEL-2023-7159543bbd has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-730b82bd39 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |