Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-11 Thread Jerry James
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

Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-11 Thread Endi Sukma Dewata
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 th

Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-08 Thread Jerry James
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.

Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-08 Thread Miro Hrončok
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 t

Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-08 Thread Jerry James
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 ne

Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-08 Thread Jerry James
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

Re: jaxb* packages retired on f35+ (despite still being used)

2021-10-08 Thread Jerry James
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 ch

jaxb* packages retired on f35+ (despite still being used)

2021-10-08 Thread Fabio Valentini
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