On Fri, Aug 14, 2020 at 7:07 PM Fabio Valentini <decathorpe(a)gmail.com>
Since ~2 days ago, the rawhide koji buildroot has exhibited some
*really weird* issues when building Java packages with maven (when
building packages locally with "mock -r fedora-rawhide-x86_64
--enablerepo local foo.src.rpm").
During installation of the build dependencies, some random (?) Java
package will have a scriptlet failure like this: "Error in <unknown>
scriptlet in rpm package mockito" (the package that this error occurs
in is not always the same). This is always the last scriptlet run
before the "Verifying" stage of "dnf install".
Then, later, during execution of %build, the following errors show up,
which make the it fail:
/usr/share/maven/bin/mvn: Failed to set JAVACMD
The JAVA_HOME environment variable is not defined correctly
This environment variable is needed to run this program
NB: JAVA_HOME should point to a JDK not a JRE
Experiencing the same problem. Haven;t found any usefull info about this
Sometimes, scrubbing the mock buildroot makes the next build succeed,
sometimes it doesn't. I tried entering the buildroot with "mock shell"
but it didn't yield any useful information.
I see that the scripts setting up JAVA_HOME etc. try to find a java +
javac executable, but they're all there, and the alternatives setup
also looks sane (no broken links in /etc/alternatives).
The only Java related updates I see in the buildroot for the "critical
time frame" are builds of java-11-openjdk, but I'm not sure how they
could have introduced such inconsistently buggy buildroot behaviour :(
Does anybody have an idea what might be the problem here? It's really
annoying to be unable to build Java packages locally most of the time
(curiously, I haven't seen this issue happen in any koji builds yet).
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines