[Bug 2051184] New: lancer fails to build with java-17-openjdk
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2051184
Bug ID: 2051184
Summary: lancer fails to build with java-17-openjdk
Product: Fedora
Version: rawhide
Status: NEW
Component: lancer
Severity: high
Assignee: willb(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: didiksupriadi41(a)gmail.com,
java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
jhuttana(a)redhat.com, jvanek(a)redhat.com,
pmikova(a)redhat.com, sgehwolf(a)redhat.com,
willb(a)redhat.com
Blocks: 2024265
Target Milestone: ---
Classification: Fedora
lancer 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...
For the build logs, see:
https://koji.fedoraproject.org/koji/taskinfo?taskID=82430359
https://kojipkgs.fedoraproject.org/work/tasks/374/82430374/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/374/82430374/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/374/82430374/state.log
https://kojipkgs.fedoraproject.org/work/tasks/374/82430374/build.log
https://kojipkgs.fedoraproject.org/work/tasks/374/82430374/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 lancer; cd lancer; 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/lancer
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(a)lists.fedoraproject.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.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2024265
[Bug 2024265] java-17-openjdk as system JDK in F36
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051184
1 week, 1 day
[Bug 2098100] New: ant-contrib, one of important components of aqa java certification gone form fedora
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2098100
Bug ID: 2098100
Summary: ant-contrib, one of important components of aqa java
certification gone form fedora
Product: Fedora
Version: 36
Status: NEW
Component: ant-contrib
Assignee: extras-orphan(a)fedoraproject.org
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: akurtako(a)redhat.com, extras-orphan(a)fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com
Target Milestone: ---
Classification: Fedora
To support java certifications - namely Adoptium aqavid - and thus java build
toolchain, and thus java-stack health in Fedora, ant-contirb is an crucial part
of fedora javabuild toolchain.
Without ant-contrib, vendors of openjdk will need to select different
enviroenmet to pass aqa certification,m which wil be another death blow to
dying javastack.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2098100
1 week, 1 day
[Bug 2096928] New: maven pulls in jdk and jdk-devel even though can work with just java-headless
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2096928
Bug ID: 2096928
Summary: maven pulls in jdk and jdk-devel even though can work
with just java-headless
Product: Fedora
Version: 36
Status: NEW
Component: maven
Severity: medium
Assignee: mizdebsk(a)redhat.com
Reporter: rvkagan(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-sig-commits(a)lists.fedoraproject.org,
mizdebsk(a)redhat.com, msrb(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
maven package depends (via respective maven-openjdkXX subpackages) on
java-XX-openjdk-devel and subsequently on java-XX-openjdk packages, which in
turn pull in various GUI-related stuff.
OTOH java-XX-openjdk-headless appears to be sufficient for a useful maven
setup.
Version-Release number of selected component (if applicable):
maven-3.8.4-3.fc36
How reproducible:
always
Steps to Reproduce:
1. dnf install maven
Actual results:
maven installation pulls in a lot of GUI-related stuff by dependencies
Expected results:
maven installs and runs with a headless java setup
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2096928
1 week, 1 day
[Bug 1988896] New: weird build error with xmvn-mojo:4.0.0:javadoc (default-cli) @ log4j
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1988896
Bug ID: 1988896
Summary: weird build error with xmvn-mojo:4.0.0:javadoc
(default-cli) @ log4j
Product: Fedora
Version: rawhide
Status: NEW
Component: xmvn
Assignee: mizdebsk(a)redhat.com
Reporter: sergio(a)serjux.com
QA Contact: extras-qa(a)fedoraproject.org
CC: java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
mat.booth(a)gmail.com, mizdebsk(a)redhat.com,
msrb(a)redhat.com
Target Milestone: ---
Classification: Fedora
Created attachment 1809992
--> https://bugzilla.redhat.com/attachment.cgi?id=1809992&action=edit
https://kojipkgs.fedoraproject.org//work/tasks/9723/73109723/build.log
Description of problem:
I can build log4j on F34 but not on Rawhide
xmvn-mojo:3.1.0:javadoc (default-cli) @ log4j --- in build.log
and
xmvn-mojo:4.0.0:javadoc (default-cli) @ log4j ---
/builddir/build/BUILD/apache-log4j-2.14.1-src/log4j-slf4j-impl/src/main/java/org/apache/logging/slf4j/package-info.java:22:
warning: a package-info.java file has already been seen for package
org.apache.logging.slf4j
package org.apache.logging.slf4j;
^
/builddir/build/BUILD/apache-log4j-2.14.1-src/log4j-to-slf4j/src/main/java/org/apache/logging/slf4j/SLF4JLogger.java:25:
error: cannot find symbol
import org.slf4j.MarkerFactory;
take a look in the build.log
--
You are receiving this mail because:
You are on the CC list for the bug.
1 week, 1 day
[Bug 2051223] New: xmpcore fails to build with java-17-openjdk
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2051223
Bug ID: 2051223
Summary: xmpcore fails to build with java-17-openjdk
Product: Fedora
Version: rawhide
Status: NEW
Component: xmpcore
Severity: high
Assignee: jjelen(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: cedric.olivier(a)free.fr, didiksupriadi41(a)gmail.com,
java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
jhuttana(a)redhat.com, jjelen(a)redhat.com,
jvanek(a)redhat.com, pmikova(a)redhat.com,
puntogil(a)libero.it, sgehwolf(a)redhat.com
Blocks: 2024265
Target Milestone: ---
Classification: Fedora
xmpcore 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...
For the build logs, see:
https://koji.fedoraproject.org/koji/taskinfo?taskID=82435800
https://kojipkgs.fedoraproject.org/work/tasks/5866/82435866/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/5866/82435866/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/5866/82435866/state.log
https://kojipkgs.fedoraproject.org/work/tasks/5866/82435866/build.log
https://kojipkgs.fedoraproject.org/work/tasks/5866/82435866/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 xmpcore; cd xmpcore; 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/xmpcore
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(a)lists.fedoraproject.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.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2024265
[Bug 2024265] java-17-openjdk as system JDK in F36
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051223
1 week, 2 days
[Bug 2051213] New: serp fails to build with java-17-openjdk
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2051213
Bug ID: 2051213
Summary: serp fails to build with java-17-openjdk
Product: Fedora
Version: rawhide
Status: NEW
Component: serp
Severity: high
Assignee: jjelen(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: didiksupriadi41(a)gmail.com,
java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
jhuttana(a)redhat.com, jjelen(a)redhat.com,
jvanek(a)redhat.com, pmikova(a)redhat.com,
puntogil(a)libero.it, sgehwolf(a)redhat.com
Blocks: 2024265
Target Milestone: ---
Classification: Fedora
serp 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...
For the build logs, see:
https://koji.fedoraproject.org/koji/taskinfo?taskID=82434688
https://kojipkgs.fedoraproject.org/work/tasks/4772/82434772/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/4772/82434772/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/4772/82434772/state.log
https://kojipkgs.fedoraproject.org/work/tasks/4772/82434772/build.log
https://kojipkgs.fedoraproject.org/work/tasks/4772/82434772/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 serp; cd serp; 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/serp
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(a)lists.fedoraproject.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.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2024265
[Bug 2024265] java-17-openjdk as system JDK in F36
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051213
1 week, 2 days
[Bug 2051153] New: hibernate-jpa-2.1-api fails to build with java-17-openjdk
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2051153
Bug ID: 2051153
Summary: hibernate-jpa-2.1-api fails to build with
java-17-openjdk
Product: Fedora
Version: rawhide
Status: NEW
Component: hibernate-jpa-2.1-api
Severity: high
Assignee: jjelen(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: didiksupriadi41(a)gmail.com,
java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
jhuttana(a)redhat.com, jjelen(a)redhat.com,
jvanek(a)redhat.com, lef(a)fedoraproject.org,
pmikova(a)redhat.com, puntogil(a)libero.it,
sgehwolf(a)redhat.com
Blocks: 2024265
Target Milestone: ---
Classification: Fedora
hibernate-jpa-2.1-api 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...
For the build logs, see:
https://koji.fedoraproject.org/koji/taskinfo?taskID=82426726
https://kojipkgs.fedoraproject.org/work/tasks/6838/82426838/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/6838/82426838/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/6838/82426838/state.log
https://kojipkgs.fedoraproject.org/work/tasks/6838/82426838/build.log
https://kojipkgs.fedoraproject.org/work/tasks/6838/82426838/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 hibernate-jpa-2.1-api; cd
hibernate-jpa-2.1-api; 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/hibernate-...
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(a)lists.fedoraproject.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.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2024265
[Bug 2024265] java-17-openjdk as system JDK in F36
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051153
1 week, 2 days
[Bug 2051133] New: apache-commons-fileupload fails to build with java-17-openjdk
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2051133
Bug ID: 2051133
Summary: apache-commons-fileupload fails to build with
java-17-openjdk
Product: Fedora
Version: rawhide
Status: NEW
Component: apache-commons-fileupload
Severity: high
Assignee: jjelen(a)redhat.com
Reporter: jvanek(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: didiksupriadi41(a)gmail.com,
java-maint-sig(a)lists.fedoraproject.org,
java-sig-commits(a)lists.fedoraproject.org,
jerboaa(a)gmail.com, jhuttana(a)redhat.com,
jjelen(a)redhat.com, jvanek(a)redhat.com,
mizdebsk(a)redhat.com, pmikova(a)redhat.com,
sgehwolf(a)redhat.com, SpikeFedora(a)gmail.com
Blocks: 2024265
Target Milestone: ---
Classification: Fedora
apache-commons-fileupload 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...
For the build logs, see:
https://koji.fedoraproject.org/koji/taskinfo?taskID=82423307
https://kojipkgs.fedoraproject.org/work/tasks/3359/82423359/mock_output.log
https://kojipkgs.fedoraproject.org/work/tasks/3359/82423359/hw_info.log
https://kojipkgs.fedoraproject.org/work/tasks/3359/82423359/state.log
https://kojipkgs.fedoraproject.org/work/tasks/3359/82423359/build.log
https://kojipkgs.fedoraproject.org/work/tasks/3359/82423359/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 apache-commons-fileupload;
cd apache-commons-fileupload; 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/apache-com...
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(a)lists.fedoraproject.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.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2024265
[Bug 2024265] java-17-openjdk as system JDK in F36
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051133
1 week, 2 days
[Bug 2106477] New: Warning about uid on installation of tomcat package
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2106477
Bug ID: 2106477
Summary: Warning about uid on installation of tomcat package
Product: Fedora
Version: 36
Status: NEW
Component: tomcat
Assignee: csutherl(a)redhat.com
Reporter: csutherl(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: alee(a)redhat.com, coolsvap(a)gmail.com,
csutherl(a)redhat.com, gzaronikas(a)gmail.com,
huwang(a)redhat.com, ivan.afonichev(a)gmail.com,
java-sig-commits(a)lists.fedoraproject.org,
krzysztof.daniel(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The scriplet that sets up the uid for tomcat throws a warning.
Version-Release number of selected component (if applicable):
tomcat-1:9.0.64-1.fc36.noarch
How reproducible:
Every time
Steps to Reproduce:
1. Install tomcat
2. Observe dnf output for warning message
Actual results:
You will see the following warning:
```
Running scriptlet: tomcat-1:9.0.64-1.fc36.noarch
useradd warning: tomcat's uid 53 outside of the SYS_UID_MIN 201 and SYS_UID_MAX
999 range.
```
Expected results:
There is no warning.
Additional info:
I found https://bugzilla.redhat.com/show_bug.cgi?id=2004911#c3 while searching
around a bit which implies it may be 'fixed' some time? We could also just drop
the UID as I don't think it's required anywhere...
Also the tomcat ID is still reserved as 53 in /usr/share/doc/setup/uidgid
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2106477
1 week, 2 days