Re: jaxb* packages retired on f35+ (despite still being used)
Hi Endi, On Mon, Oct 11, 2021 at 8:58 AM Endi Sukma Dewata wrote: > Hi, some of JAXB packages failed to build possibly due to Maven/Ant changes > earlier this year, and since there has been no solution we decided to drop > JAXB dependency from Dogtag. We just barely managed to complete the work > recently, so unfortunately this could not be done much earlier before the > freeze deadline. JAXB was already dropped from RHEL, but I did not realize it > was still in use on F35. Sorry for the troubles. Don't lose any sleep over it. It turned out that the JAXB support wasn't needed, and removing dependencies on JAXB was fairly easy. It would be nice to have advance notice of packages disappearing, but the consequences this time weren't too bad. -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jaxb* packages retired on f35+ (despite still being used)
Hi, some of JAXB packages failed to build possibly due to Maven/Ant changes earlier this year, and since there has been no solution we decided to drop JAXB dependency from Dogtag. We just barely managed to complete the work recently, so unfortunately this could not be done much earlier before the freeze deadline. JAXB was already dropped from RHEL, but I did not realize it was still in use on F35. Sorry for the troubles. -- Endi S. Dewata ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jaxb* packages retired on f35+ (despite still being used)
On Fri, Oct 8, 2021 at 4:29 PM Miro Hrončok wrote: > My experience is that even retirements done after a freeze make it to the > repo, > when a compose is done. Not sure if feature or bug, but maybe worth trying. Okay, I have given it a try. Fingers crossed that it all works out. Thanks, Miro. -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jaxb* packages retired on f35+ (despite still being used)
On 08. 10. 21 22:42, Jerry James wrote: On Fri, Oct 8, 2021 at 2:16 PM Jerry James wrote: I think jaxb is only needed for a twitter demo, which we obviously don't need. I'll remove the dependency from jakarta-json and do builds for F35+. I don't see any binary RPM dependencies on jaxb, so I think a freeze exception won't be needed. Let me know if I have analyzed the situation incorrectly, but this looks like a build-time problem only. Regards, There is another dependency. The jakarta-ws-rs package also depends on jaxb, and jakarta-json depends on jakarta-ws-rs. However, it looks like jakarta-ws-rs is only needed for the subpackages jakarta-json-jaxrs and jakarta-json-jaxrs-1x, which nothing seems to depend on. So, in addition to dropping the twitter demo from jakarta-json, I will also remove those two subpackages and remove the dependency on jakarta-ws-rs. I can retire jakarta-ws-rs from Rawhide, but it is too late to do so for F35, of course. Thoughts on what to do about that are welcome. My experience is that even retirements done after a freeze make it to the repo, when a compose is done. Not sure if feature or bug, but maybe worth trying. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jaxb* packages retired on f35+ (despite still being used)
On Fri, Oct 8, 2021 at 2:16 PM Jerry James wrote: > I think jaxb is only needed for a twitter demo, which we obviously > don't need. I'll remove the dependency from jakarta-json and do > builds for F35+. I don't see any binary RPM dependencies on jaxb, so > I think a freeze exception won't be needed. Let me know if I have > analyzed the situation incorrectly, but this looks like a build-time > problem only. Regards, There is another dependency. The jakarta-ws-rs package also depends on jaxb, and jakarta-json depends on jakarta-ws-rs. However, it looks like jakarta-ws-rs is only needed for the subpackages jakarta-json-jaxrs and jakarta-json-jaxrs-1x, which nothing seems to depend on. So, in addition to dropping the twitter demo from jakarta-json, I will also remove those two subpackages and remove the dependency on jakarta-ws-rs. I can retire jakarta-ws-rs from Rawhide, but it is too late to do so for F35, of course. Thoughts on what to do about that are welcome. -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jaxb* packages retired on f35+ (despite still being used)
On Fri, Oct 8, 2021 at 2:06 PM Jerry James wrote: > It looks like antlr4 doesn't depend on jaxb directly, but only > indirectly via jakarta-json. Let me see if that dependency can be > removed. Still, it would have been nice to have a heads up about jaxb > disappearing, and doing so right before final freeze is a really > terrible idea, as you note. I think jaxb is only needed for a twitter demo, which we obviously don't need. I'll remove the dependency from jakarta-json and do builds for F35+. I don't see any binary RPM dependencies on jaxb, so I think a freeze exception won't be needed. Let me know if I have analyzed the situation incorrectly, but this looks like a build-time problem only. Regards, -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: jaxb* packages retired on f35+ (despite still being used)
On Fri, Oct 8, 2021 at 12:01 PM Fabio Valentini wrote: > I want to draw attention to the fact that the jaxb stack (Jakarta XML > Binding for Java) was recently retired for rawhide and F35 (only hours > before the final freeze went into effect). It looks like edewata did > not do a comprehensive check whether those packages are still depended > on by anything other than his own packages, though. > > Since there's not been a successful rawhide compose since the packages > were retired, they now show up in the "orphaned packages" report, > where their dependency trees are listed thusly: > > - Too many dependencies for jaxb, not all listed here > - Too many dependencies for jaxb-dtd-parser, not all listed here > - Too many dependencies for jaxb-fi, not all listed here > - Too many dependencies for jaxb-istack-commons, not all listed here > - Too many dependencies for jaxb-stax-ex, not all listed here > - Too many dependencies for xmlstreambuffer, not all listed here > > They are all part of the dependency tree of antlr4, which is why there > are so many dependent packages the report can't even list them all > (I've CC'd jjames, antlr4's maintainer). > > I'm not sure if the packages could be dropped from the antlr4 > dependency tree, but them getting removed so late before the F35 final > freeze introduced all kinds of problems (including FTBFS and FTI > issues), which now can't be fixed without going through the Freeze > Exception process, at a time when we're all busy doing other things. > :( It looks like antlr4 doesn't depend on jaxb directly, but only indirectly via jakarta-json. Let me see if that dependency can be removed. Still, it would have been nice to have a heads up about jaxb disappearing, and doing so right before final freeze is a really terrible idea, as you note. -- Jerry James http://www.jamezone.org/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
jaxb* packages retired on f35+ (despite still being used)
Hi everybody, I want to draw attention to the fact that the jaxb stack (Jakarta XML Binding for Java) was recently retired for rawhide and F35 (only hours before the final freeze went into effect). It looks like edewata did not do a comprehensive check whether those packages are still depended on by anything other than his own packages, though. Since there's not been a successful rawhide compose since the packages were retired, they now show up in the "orphaned packages" report, where their dependency trees are listed thusly: - Too many dependencies for jaxb, not all listed here - Too many dependencies for jaxb-dtd-parser, not all listed here - Too many dependencies for jaxb-fi, not all listed here - Too many dependencies for jaxb-istack-commons, not all listed here - Too many dependencies for jaxb-stax-ex, not all listed here - Too many dependencies for xmlstreambuffer, not all listed here They are all part of the dependency tree of antlr4, which is why there are so many dependent packages the report can't even list them all (I've CC'd jjames, antlr4's maintainer). I'm not sure if the packages could be dropped from the antlr4 dependency tree, but them getting removed so late before the F35 final freeze introduced all kinds of problems (including FTBFS and FTI issues), which now can't be fixed without going through the Freeze Exception process, at a time when we're all busy doing other things. :( Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
