Hello fellow java package maintainers!
We are planning to bump the JDK from java-1.8.0-openjdk to java-11-openjdk for F33. Please see https://fedoraproject.org/wiki/Changes/Java11
Short Story: * if you have some java package, be aware that we are bumping JDK in rawhide * Ensure your package builds and runs fine with JDK11 (see the https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/) * there is special tooling ready for this, before mass rebuild is launched ** See https://fedoraproject.org/wiki/Changes/Java11#copr_preliminary_rebuild * If you do not want Fedora rotten with JDK8 for ever, continue reading
Long Story: We ran a preliminary mass rebuild of javastack in copr repo https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ (select "all" instead of "25" at the bottom), on packages requiring java,javac, java-devel, maven-local, ant, ivy & comp for build. You can see, the result was quite dramatic: 1225 total; attempted to rebuild 483 failed; from those 191 are trivial failures (but if you fix it, there is no guarantee real troubles are not hidden behind that) 186 succeeded 556 orphans or dead or otherwise tragic so the build did not even start
I would kindly ask you to search yourself in this list: https://jvanek.fedorapeople.org/java11/people If you are here, please check status of your package in https://jvanek.fedorapeople.org/java11/init (pain text of https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds). * If your package is "succeeded", congratulations nothing to do, and just keep en eye on JDK bump * If there is "failed" but contains "- -" then it is probably orphan. If you wish to resurrect it, please ensure it runs against JDK11 (see lower) * If there is "failed" but failed in "seconds", then those packages failed so quickly, that the build was in initial phases. That usually mean that you build with source/target lower then 1.6 JDK11 supports 1.6 and up. We recommend to bump the source/target to 1.8, to allow existence of compact 1.8 packages alongside main javastack. See https://fedoraproject.org/wiki/Changes/Java11#Wrong_source.2Ftarget_version. Don't forget to upstream the patch, or maybe it is enough to update to more fresh upstream release which supports JDK11? it may happen, that after the fix, your build will fail in more terrible way (see below) * If there is "failed", and its none of above, then your package simply failed. Very often the scary error may be fixed by bump to latest upstream version. JDK 11 is out for several years. Please, try to fix the package. Don't hesitate to ask on devel@fedoraproject.org or java-devel@fedoraproject.org or directly to me jvanek@redhat.com. If you fix the fail, feel free to share your fix, it may help others. We are trying to gather the most common issues at https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_fa... . Feel free to enhance the page, or write us your case (possibly both with solution and without) so we can add it here.
Debugging Your failures. The copr repo we maintain, contains builds of java-11-openjdk as system JDK, javapackages-tools honoring that, and java-1.8.0-openjdk as non system JDK. Also it contains successfully rebuilt packages. You can directly use this copr repo in several ways. * first glance on error. On https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ find your build (select "all" instead of "25" at the bottom), ** Click its number, select chroot (currently fedora-32-x86_64 ) and check the logs. Main log is build.log.gz. * anything you push to rawhide, will automatically rebuild here in f32 chroot (we have a JDK in rawhide broken a bit currently) ** It is the best approach. If you can fix your package in rawhide directly, without breaking the rawhide too much, go for it ** If yo need to experiment, I have a mock config for you (generated from copr-cli mock-config jvanek/java11 fedora-32-x86_64) which you can copy to your /etc/mock and use - https://jvanek.fedorapeople.org/java11/jvanek-java11-fedora-32-x86_64.cfg . Eg:
sudo cp downloaded-fedora-32-x86_64.cfg /etc/mock/jvanek-java11-fedora-32-x86_64.cfg # change spec, bump sources, apply patches fedpkg srpm mock -r jvanek-java11-fedora-32-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the copr repo. Thank you very much for your help, there are 500 failures, and 1000 java packagers, but only 2 active members of java sig. Without your help, the JDK bump will be very hard.
Thank You!
On behalf of Fedora java group J. _______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapro...
Hello fellow java package maintainers!
We are planning to bump the JDK from java-1.8.0-openjdk to java-11-openjdk for F33. Please see https://fedoraproject.org/wiki/Changes/Java11
Short Story: * if you have some java package, be aware that we are bumping JDK in rawhide * Ensure your package builds and runs fine with JDK11 (see the https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/) * there is special tooling ready for this, before mass rebuild is launched ** See https://fedoraproject.org/wiki/Changes/Java11#copr_preliminary_rebuild * If you do not want Fedora rotten with JDK8 for ever, continue reading
Long Story: We ran a preliminary mass rebuild of javastack in copr repo https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ (select "all" instead of "25" at the bottom), on packages requiring java,javac, java-devel, maven-local, ant, ivy & comp for build. You can see, the result was quite dramatic: 1225 total; attempted to rebuild 483 failed; from those 191 are trivial failures (but if you fix it, there is no guarantee real troubles are not hidden behind that) 186 succeeded 556 orphans or dead or otherwise tragic so the build did not even start
I would kindly ask you to search yourself in this list: https://jvanek.fedorapeople.org/java11/people If you are here, please check status of your package in https://jvanek.fedorapeople.org/java11/init (pain text of https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds). * If your package is "succeeded", congratulations nothing to do, and just keep en eye on JDK bump * If there is "failed" but contains "- -" then it is probably orphan. If you wish to resurrect it, please ensure it runs against JDK11 (see lower) * If there is "failed" but failed in "seconds", then those packages failed so quickly, that the build was in initial phases. That usually mean that you build with source/target lower then 1.6 JDK11 supports 1.6 and up. We recommend to bump the source/target to 1.8, to allow existence of compact 1.8 packages alongside main javastack. See https://fedoraproject.org/wiki/Changes/Java11#Wrong_source.2Ftarget_version. Don't forget to upstream the patch, or maybe it is enough to update to more fresh upstream release which supports JDK11? it may happen, that after the fix, your build will fail in more terrible way (see below) * If there is "failed", and its none of above, then your package simply failed. Very often the scary error may be fixed by bump to latest upstream version. JDK 11 is out for several years. Please, try to fix the package. Don't hesitate to ask on devel@fedoraproject.org or java-devel@fedoraproject.org or directly to me jvanek@redhat.com. If you fix the fail, feel free to share your fix, it may help others. We are trying to gather the most common issues at https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_fa... . Feel free to enhance the page, or write us your case (possibly both with solution and without) so we can add it here.
Debugging Your failures. The copr repo we maintain, contains builds of java-11-openjdk as system JDK, javapackages-tools honoring that, and java-1.8.0-openjdk as non system JDK. Also it contains successfully rebuilt packages. You can directly use this copr repo in several ways. * first glance on error. On https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ find your build (select "all" instead of "25" at the bottom), ** Click its number, select chroot (currently fedora-32-x86_64 ) and check the logs. Main log is build.log.gz. * anything you push to rawhide, will automatically rebuild here in f32 chroot (we have a JDK in rawhide broken a bit currently) ** It is the best approach. If you can fix your package in rawhide directly, without breaking the rawhide too much, go for it ** If yo need to experiment, I have a mock config for you (generated from copr-cli mock-config jvanek/java11 fedora-32-x86_64) which you can copy to your /etc/mock and use - https://jvanek.fedorapeople.org/java11/jvanek-java11-fedora-32-x86_64.cfg . Eg:
sudo cp downloaded-fedora-32-x86_64.cfg /etc/mock/jvanek-java11-fedora-32-x86_64.cfg # change spec, bump sources, apply patches fedpkg srpm mock -r jvanek-java11-fedora-32-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the copr repo. Thank you very much for your help, there are 500 failures, and 1000 java packagers, but only 2 active members of java sig. Without your help, the JDK bump will be very hard.
Thank You!
On behalf of Fedora java group J.
\o Hey Jiri,
I don't see two of our packages in the copr:
https://src.fedoraproject.org/rpms/pki-core/ https://src.fedoraproject.org/rpms/dogtag-pki/
Is there a way to know why they were excluded?
Thanks!
- Alex
----- Original Message -----
From: "Jiri Vanek" jvanek@redhat.com To: "Development discussions related to Fedora" devel@lists.fedoraproject.org, "Fedora Java Development List" java-devel@lists.fedoraproject.org Sent: Thursday, April 30, 2020 12:31:43 PM Subject: F33 system wide change, java-11-openjdk as system jdk
Hello fellow java package maintainers!
We are planning to bump the JDK from java-1.8.0-openjdk to java-11-openjdk for F33. Please see https://fedoraproject.org/wiki/Changes/Java11
Short Story:
- if you have some java package, be aware that we are bumping JDK in rawhide
- Ensure your package builds and runs fine with JDK11 (see the
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/)
- there is special tooling ready for this, before mass rebuild is launched
** See https://fedoraproject.org/wiki/Changes/Java11#copr_preliminary_rebuild
- If you do not want Fedora rotten with JDK8 for ever, continue reading
Long Story: We ran a preliminary mass rebuild of javastack in copr repo https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ (select "all" instead of "25" at the bottom), on packages requiring java,javac, java-devel, maven-local, ant, ivy & comp for build. You can see, the result was quite dramatic: 1225 total; attempted to rebuild 483 failed; from those 191 are trivial failures (but if you fix it, there is no guarantee real troubles are not hidden behind that) 186 succeeded 556 orphans or dead or otherwise tragic so the build did not even start
I would kindly ask you to search yourself in this list: https://jvanek.fedorapeople.org/java11/people If you are here, please check status of your package in https://jvanek.fedorapeople.org/java11/init (pain text of https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds).
- If your package is "succeeded", congratulations nothing to do, and just
keep en eye on JDK bump
- If there is "failed" but contains "- -" then it is probably orphan. If
you wish to resurrect it, please ensure it runs against JDK11 (see lower)
- If there is "failed" but failed in "seconds", then those packages failed
so quickly, that the build was in initial phases. That usually mean that you build with source/target lower then 1.6 JDK11 supports 1.6 and up. We recommend to bump the source/target to 1.8, to allow existence of compact 1.8 packages alongside main javastack. See https://fedoraproject.org/wiki/Changes/Java11#Wrong_source.2Ftarget_version. Don't forget to upstream the patch, or maybe it is enough to update to more fresh upstream release which supports JDK11? it may happen, that after the fix, your build will fail in more terrible way (see below)
- If there is "failed", and its none of above, then your package simply
failed. Very often the scary error may be fixed by bump to latest upstream version. JDK 11 is out for several years. Please, try to fix the package. Don't hesitate to ask on devel@fedoraproject.org or java-devel@fedoraproject.org or directly to me jvanek@redhat.com. If you fix the fail, feel free to share your fix, it may help others. We are trying to gather the most common issues at https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_fa... . Feel free to enhance the page, or write us your case (possibly both with solution and without) so we can add it here.
Debugging Your failures. The copr repo we maintain, contains builds of java-11-openjdk as system JDK, javapackages-tools honoring that, and java-1.8.0-openjdk as non system JDK. Also it contains successfully rebuilt packages. You can directly use this copr repo in several ways.
- first glance on error. On
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ find your build (select "all" instead of "25" at the bottom), ** Click its number, select chroot (currently fedora-32-x86_64 ) and check the logs. Main log is build.log.gz.
- anything you push to rawhide, will automatically rebuild here in f32
chroot (we have a JDK in rawhide broken a bit currently) ** It is the best approach. If you can fix your package in rawhide directly, without breaking the rawhide too much, go for it ** If yo need to experiment, I have a mock config for you (generated from copr-cli mock-config jvanek/java11 fedora-32-x86_64) which you can copy to your /etc/mock and use
https://jvanek.fedorapeople.org/java11/jvanek-java11-fedora-32-x86_64.cfg . Eg:
sudo cp downloaded-fedora-32-x86_64.cfg /etc/mock/jvanek-java11-fedora-32-x86_64.cfg # change spec, bump sources, apply patches fedpkg srpm mock -r jvanek-java11-fedora-32-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the copr repo. Thank you very much for your help, there are 500 failures, and 1000 java packagers, but only 2 active members of java sig. Without your help, the JDK bump will be very hard.
Thank You!
On behalf of Fedora java group J. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Hi Alex, both your packages "BuildRequires: java-1.8.0-openjdk-devel" So I could not pull it. According to the packaging guidelines you should require only "java-devel" (exactly for this case:)). Thus I could not found your packages by using build-requires queries. Even If I found, It would be useless, because java-1.8.0-openjdk-devel will still be providing itself. Please adapt your packages to java-devel only. And when in int, bump them to build n that copr of mine. I will happily include them to the copr once you fix the BR. Crossing fingers! TYVM!
Jiri (sorry for different email, only github login worked for me today)
Ah cool, so my guess was correct. :-) We're working on fixing this upstream and then we'll get it pulled into Fedora. Mind if we ping you for a rebuild when we're ready?
- Alex
----- Original Message -----
From: judovana@email.cz To: devel@lists.fedoraproject.org Sent: Friday, May 1, 2020 2:19:17 PM Subject: Re: F33 system wide change, java-11-openjdk as system jdk
Hi Alex, both your packages "BuildRequires: java-1.8.0-openjdk-devel" So I could not pull it. According to the packaging guidelines you should require only "java-devel" (exactly for this case:)). Thus I could not found your packages by using build-requires queries. Even If I found, It would be useless, because java-1.8.0-openjdk-devel will still be providing itself. Please adapt your packages to java-devel only. And when in int, bump them to build n that copr of mine. I will happily include them to the copr once you fix the BR. Crossing fingers! TYVM!
Jiri (sorry for different email, only github login worked for me today) _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
On 30. 04. 20 18:29, Jiri Vanek wrote:
- Ensure your package builds and runs fine with JDK11 (see the
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/)
The builds are from Fedora 33 sources, but in Fedora 32 buildroot. The Java11 change is for Fedora 33. Is this an error, or is there some benefit with this setup I don't understand?
- If there is "failed" but contains "- -" then it is probably orphan.
Packages don't stop building just because they are orphaned. Do you mean retired? And if so, why do you attempt to build retired packages? Is this caused by the above (e.g. are you repoquerying Fedora 32, but attempting builds from the master branch)?
sudo cp downloaded-fedora-32-x86_64.cfg /etc/mock/jvanek-java11-fedora-32-x86_64.cfg
Or you can copy it to ~/.config/mock instead, not using sudo.
Thanks for doing the preliminary builds in Copr.
Hi Miro! The build is in f32 chroot, because jdk8 in rawhide segfaults due to new glibc. The glibc update had overlap with the initiation of this effort, so I stuck on f32 for now. It may happen that once we fix jdk8, I will fix also the copr. Also you could notice, that both rawhide and f32 are being build from the rawhide sources.
Yes, I "rebuilt" also packages retired in rawhide. Originally it was by accident, then I let it here stoned by the number of thems.
Ah, sure, ~/.config/mock. I always forgot about that. Thanx!
J.
Hi Miro! The build is in f32 chroot, because jdk8 in rawhide segfaults due to new glibc. The glibc update had overlap with the initiation of this effort, so I stuck on f32 for now. It may happen that once we fix jdk8, I will fix also the copr. Also you could notice, that both rawhide and f32 are being build from the rawhide sources.
Yes, I "rebuilt" also packages retired in rawhide. Originally it was by accident, then I let it here stoned by the number of thems.
Ah, sure, ~/.config/mock. I always forgot about that. Thanx!
J.
Hello!
An raw schedule of mass rebuilds was added to the Java11 feature list: https://fedoraproject.org/wiki/Changes/Java11#Expected_schedule
You can expect second copr-based mass rebuild, in 1st June 2020. Please try to fix your packages until then, as on the result of this mass rebuild, future steps will be based.
Thanx! J. On 4/30/20 6:29 PM, Jiri Vanek wrote:
Hello fellow java package maintainers!
We are planning to bump the JDK from java-1.8.0-openjdk to java-11-openjdk for F33. Please see https://fedoraproject.org/wiki/Changes/Java11
Short Story:
- if you have some java package, be aware that we are bumping JDK in rawhide
- Ensure your package builds and runs fine with JDK11 (see the
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/)
- there is special tooling ready for this, before mass rebuild is launched
** See https://fedoraproject.org/wiki/Changes/Java11#copr_preliminary_rebuild
- If you do not want Fedora rotten with JDK8 for ever, continue reading
Long Story: We ran a preliminary mass rebuild of javastack in copr repo https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ (select "all" instead of "25" at the bottom), on packages requiring java,javac, java-devel, maven-local, ant, ivy & comp for build. You can see, the result was quite dramatic: 1225 total; attempted to rebuild 483 failed; from those 191 are trivial failures (but if you fix it, there is no guarantee real troubles are not hidden behind that) 186 succeeded 556 orphans or dead or otherwise tragic so the build did not even start
I would kindly ask you to search yourself in this list: https://jvanek.fedorapeople.org/java11/people If you are here, please check status of your package in https://jvanek.fedorapeople.org/java11/init (pain text of https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds).
- If your package is "succeeded", congratulations nothing to do, and just keep en eye on JDK bump
- If there is "failed" but contains "- -" then it is probably orphan. If you wish to resurrect it,
please ensure it runs against JDK11 (see lower)
- If there is "failed" but failed in "seconds", then those packages failed so quickly, that the
build was in initial phases. That usually mean that you build with source/target lower then 1.6 JDK11 supports 1.6 and up. We recommend to bump the source/target to 1.8, to allow existence of compact 1.8 packages alongside main javastack. See https://fedoraproject.org/wiki/Changes/Java11#Wrong_source.2Ftarget_version. Don't forget to upstream the patch, or maybe it is enough to update to more fresh upstream release which supports JDK11? it may happen, that after the fix, your build will fail in more terrible way (see below)
- If there is "failed", and its none of above, then your package simply failed. Very often the
scary error may be fixed by bump to latest upstream version. JDK 11 is out for several years. Please, try to fix the package. Don't hesitate to ask on devel@fedoraproject.org or java-devel@fedoraproject.org or directly to me jvanek@redhat.com. If you fix the fail, feel free to share your fix, it may help others. We are trying to gather the most common issues at https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_fa... . Feel free to enhance the page, or write us your case (possibly both with solution and without) so we can add it here.
Debugging Your failures. The copr repo we maintain, contains builds of java-11-openjdk as system JDK, javapackages-tools honoring that, and java-1.8.0-openjdk as non system JDK. Also it contains successfully rebuilt packages. You can directly use this copr repo in several ways.
- first glance on error. On https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ find your
build (select "all" instead of "25" at the bottom), ** Click its number, select chroot (currently fedora-32-x86_64 ) and check the logs. Main log is build.log.gz.
- anything you push to rawhide, will automatically rebuild here in f32 chroot (we have a JDK in
rawhide broken a bit currently) ** It is the best approach. If you can fix your package in rawhide directly, without breaking the rawhide too much, go for it ** If yo need to experiment, I have a mock config for you (generated from copr-cli mock-config jvanek/java11 fedora-32-x86_64) which you can copy to your /etc/mock and use - https://jvanek.fedorapeople.org/java11/jvanek-java11-fedora-32-x86_64.cfg . Eg:
sudo cp downloaded-fedora-32-x86_64.cfg /etc/mock/jvanek-java11-fedora-32-x86_64.cfg # change spec, bump sources, apply patches fedpkg srpm mock -r jvanek-java11-fedora-32-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the copr repo. Thank you very much for your help, there are 500 failures, and 1000 java packagers, but only 2 active members of java sig. Without your help, the JDK bump will be very hard.
Thank You!
On behalf of Fedora java group J. _______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapro... _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
On Tue, May 19, 2020, 15:40 Jiri Vanek jvanek@redhat.com wrote:
Hello!
An raw schedule of mass rebuilds was added to the Java11 feature list: https://fedoraproject.org/wiki/Changes/Java11#Expected_schedule
You can expect second copr-based mass rebuild, in 1st June 2020. Please try to fix your packages until then, as on the result of this mass rebuild, future steps will be based.
Would it be possible to make javadoc (11) less strict by default? Right now, most package failures I've looked at should be solved with "-Xdoclint:none" and I really don't have time to manually check that for 800 packages
Fabio
Thanx! J. On 4/30/20 6:29 PM, Jiri Vanek wrote:
Hello fellow java package maintainers!
We are planning to bump the JDK from java-1.8.0-openjdk to
java-11-openjdk for F33. Please see
https://fedoraproject.org/wiki/Changes/Java11
Short Story:
- if you have some java package, be aware that we are bumping JDK in
rawhide
- Ensure your package builds and runs fine with JDK11 (see the
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/)
- there is special tooling ready for this, before mass rebuild is
launched
** See
https://fedoraproject.org/wiki/Changes/Java11#copr_preliminary_rebuild
- If you do not want Fedora rotten with JDK8 for ever, continue reading
Long Story: We ran a preliminary mass rebuild of javastack in copr repo https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ (select
"all" instead of "25" at the
bottom), on packages requiring java,javac, java-devel, maven-local, ant,
ivy & comp for build. You
can see, the result was quite dramatic: 1225 total; attempted to rebuild 483 failed; from those 191 are trivial failures (but if you fix it,
there is no guarantee real
troubles are not hidden behind that) 186 succeeded 556 orphans or dead or otherwise tragic so the build did not even start
I would kindly ask you to search yourself in this list:
https://jvanek.fedorapeople.org/java11/people
If you are here, please check status of your package in
https://jvanek.fedorapeople.org/java11/init
(pain text of
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds).
- If your package is "succeeded", congratulations nothing to do, and
just keep en eye on JDK bump
- If there is "failed" but contains "- -" then it is probably
orphan. If you wish to resurrect it,
please ensure it runs against JDK11 (see lower)
- If there is "failed" but failed in "seconds", then those packages
failed so quickly, that the
build was in initial phases. That usually mean that you build with
source/target lower then 1.6
JDK11 supports 1.6 and up. We recommend to bump the source/target to
1.8, to allow existence of
compact 1.8 packages alongside main javastack. See
https://fedoraproject.org/wiki/Changes/Java11#Wrong_source.2Ftarget_version. Don't forget to
upstream the patch, or maybe it is enough to update to more fresh
upstream release which supports
JDK11? it may happen, that after the fix, your build will fail in more
terrible way (see below)
- If there is "failed", and its none of above, then your package simply
failed. Very often the
scary error may be fixed by bump to latest upstream version. JDK 11 is
out for several years.
Please, try to fix the package. Don't hesitate to ask on
devel@fedoraproject.org or
java-devel@fedoraproject.org or directly to me jvanek@redhat.com. If
you fix the fail, feel free to
share your fix, it may help others. We are trying to gather the most common issues at
https://fedoraproject.org/wiki/Changes/Java11#common_issues_packagers_can_fa... .
Feel free to enhance the page, or write us your case (possibly both
with solution and without) so
we can add it here.
Debugging Your failures. The copr repo we maintain, contains builds of java-11-openjdk as system
JDK, javapackages-tools
honoring that, and java-1.8.0-openjdk as non system JDK. Also it
contains successfully rebuilt
packages. You can directly use this copr repo in several ways.
- first glance on error. On
https://copr.fedorainfracloud.org/coprs/jvanek/java11/builds/ find your
build (select "all" instead of "25" at the bottom), ** Click its number, select chroot (currently fedora-32-x86_64 ) and
check the logs. Main log is
build.log.gz.
- anything you push to rawhide, will automatically rebuild here in f32
chroot (we have a JDK in
rawhide broken a bit currently) ** It is the best approach. If you can fix your package in rawhide
directly, without breaking the
rawhide too much, go for it ** If yo need to experiment, I have a mock config for you (generated
from copr-cli mock-config
jvanek/java11 fedora-32-x86_64) which you can copy to your /etc/mock and
use -
https://jvanek.fedorapeople.org/java11/jvanek-java11-fedora-32-x86_64.cfg . Eg:
sudo cp downloaded-fedora-32-x86_64.cfg
/etc/mock/jvanek-java11-fedora-32-x86_64.cfg
# change spec, bump sources, apply patches fedpkg srpm mock -r jvanek-java11-fedora-32-x86_64 *.src.rpm
Or any other packaging workflow you use, and you can use against the
copr repo.
Thank you very much for your help, there are 500 failures, and 1000 java
packagers, but only 2
active members of java sig. Without your help, the JDK bump will be very
hard.
Thank You!
On behalf of Fedora java group J. _______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to
devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapro...
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
-- Jiri Vanek Senior QE engineer, OpenJDK QE lead, Mgr. Red Hat Czech jvanek@redhat.com M: +420775390109 _______________________________________________ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapro...
-
Alex Scheel -
Fabio Valentini -
Jiri Vanek -
judovana＠email.cz -
Miro Hrončok