java-sig-commits February 2022

java-sig-commits@lists.fedoraproject.org

1 participants
218 discussions

[Bug 1988896] New: weird build error with xmvn-mojo:4.0.0:javadoc (default-cli) @ log4j
by bugzilla＠redhat.com 25 May '23

25 May '23

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 6

[Bug 2051223] New: xmpcore fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

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_f… 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 3

[Bug 2051213] New: serp fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

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_f… 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 3

[Bug 2051153] New: hibernate-jpa-2.1-api fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

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_f… 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-jp… 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 3

[Bug 2051133] New: apache-commons-fileupload fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

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_f… 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-commo… 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 5

[Bug 2051188] New: maven-scm fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2051188 Bug ID: 2051188 Summary: maven-scm fails to build with java-17-openjdk Product: Fedora Version: rawhide Status: NEW Component: maven-scm Severity: high Assignee: guido.grazioli(a)gmail.com Reporter: jvanek(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: dbhole(a)redhat.com, didiksupriadi41(a)gmail.com, guido.grazioli(a)gmail.com, jaromir.capik(a)email.cz, java-maint-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jhuttana(a)redhat.com, jvanek(a)redhat.com, mizdebsk(a)redhat.com, pmikova(a)redhat.com, sgehwolf(a)redhat.com Blocks: 2024265 Target Milestone: --- Classification: Fedora maven-scm 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_f… For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82431779 https://kojipkgs.fedoraproject.org/work/tasks/1826/82431826/mock_output.log https://kojipkgs.fedoraproject.org/work/tasks/1826/82431826/hw_info.log https://kojipkgs.fedoraproject.org/work/tasks/1826/82431826/state.log https://kojipkgs.fedoraproject.org/work/tasks/1826/82431826/build.log https://kojipkgs.fedoraproject.org/work/tasks/1826/82431826/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 maven-scm; cd maven-scm; 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/maven-scm 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=2051188

1 2

[Bug 2046731] New: maven-scm: FTBFS in Fedora rawhide/f36
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2046731 Bug ID: 2046731 Summary: maven-scm: FTBFS in Fedora rawhide/f36 Product: Fedora Version: rawhide Status: NEW Component: maven-scm Assignee: guido.grazioli(a)gmail.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: dbhole(a)redhat.com, guido.grazioli(a)gmail.com, jaromir.capik(a)email.cz, java-sig-commits(a)lists.fedoraproject.org, mizdebsk(a)redhat.com Blocks: 1992484 (F36FTBFS) Target Milestone: --- Classification: Fedora maven-scm failed to build from source in Fedora rawhide/f36 https://koji.fedoraproject.org/koji/taskinfo?taskID=81983935 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild Please fix maven-scm at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, maven-scm will be orphaned. Before branching of Fedora 37, maven-scm will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails… Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1992484 [Bug 1992484] Fedora 36 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2046731

1 5

[Bug 2051200] New: portlet-2.0-api fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2051200 Bug ID: 2051200 Summary: portlet-2.0-api fails to build with java-17-openjdk Product: Fedora Version: rawhide Status: NEW Component: portlet-2.0-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, pmikova(a)redhat.com, puntogil(a)libero.it, sgehwolf(a)redhat.com Blocks: 2024265 Target Milestone: --- Classification: Fedora portlet-2.0-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_f… For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82433716 https://kojipkgs.fedoraproject.org/work/tasks/3838/82433838/mock_output.log https://kojipkgs.fedoraproject.org/work/tasks/3838/82433838/hw_info.log https://kojipkgs.fedoraproject.org/work/tasks/3838/82433838/state.log https://kojipkgs.fedoraproject.org/work/tasks/3838/82433838/build.log https://kojipkgs.fedoraproject.org/work/tasks/3838/82433838/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 portlet-2.0-api; cd portlet-2.0-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/portlet-2.0-… 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=2051200

1 5

[Bug 2051198] New: plexus-component-api fails to build with java-17-openjdk
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2051198 Bug ID: 2051198 Summary: plexus-component-api fails to build with java-17-openjdk Product: Fedora Version: rawhide Status: NEW Component: plexus-component-api Severity: high Assignee: yyang(a)redhat.com Reporter: jvanek(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: didiksupriadi41(a)gmail.com, huwang(a)redhat.com, java-maint-sig(a)lists.fedoraproject.org, java-sig-commits(a)lists.fedoraproject.org, jhuttana(a)redhat.com, jvanek(a)redhat.com, mizdebsk(a)redhat.com, pmikova(a)redhat.com, sgehwolf(a)redhat.com, yyang(a)redhat.com Blocks: 2024265 Target Milestone: --- Classification: Fedora plexus-component-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_f… For the build logs, see: https://koji.fedoraproject.org/koji/taskinfo?taskID=82433052 https://kojipkgs.fedoraproject.org/work/tasks/3077/82433077/mock_output.log https://kojipkgs.fedoraproject.org/work/tasks/3077/82433077/hw_info.log https://kojipkgs.fedoraproject.org/work/tasks/3077/82433077/state.log https://kojipkgs.fedoraproject.org/work/tasks/3077/82433077/build.log https://kojipkgs.fedoraproject.org/work/tasks/3077/82433077/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 plexus-component-api; cd plexus-component-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/plexus-compo… 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=2051198

1 4

[Bug 2046846] New: portlet-2.0-api: FTBFS in Fedora rawhide/f36
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2046846 Bug ID: 2046846 Summary: portlet-2.0-api: FTBFS in Fedora rawhide/f36 Product: Fedora Version: rawhide Status: NEW Component: portlet-2.0-api Assignee: jjelen(a)redhat.com Reporter: releng(a)fedoraproject.org QA Contact: extras-qa(a)fedoraproject.org CC: java-sig-commits(a)lists.fedoraproject.org, jjelen(a)redhat.com, puntogil(a)libero.it Blocks: 1992484 (F36FTBFS) Target Milestone: --- Classification: Fedora portlet-2.0-api failed to build from source in Fedora rawhide/f36 https://koji.fedoraproject.org/koji/taskinfo?taskID=81985245 For details on the mass rebuild see: https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild Please fix portlet-2.0-api at your earliest convenience and set the bug's status to ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks, portlet-2.0-api will be orphaned. Before branching of Fedora 37, portlet-2.0-api will be retired, if it still fails to build. For more details on the FTBFS policy, please visit: https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails… Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1992484 [Bug 1992484] Fedora 36 FTBFS Tracker -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2046846

1 6

← Newer
1
2
3
4
5
6
7
...
22
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

java-sig-commits February 2022