On Mon, Aug 26, 2019 at 10:36 AM Vít Ondruch <vondruch@xxxxxxxxxx> wrote: > > > Dne 25. 08. 19 v 14:06 Fabio Valentini napsal(a): > > Hi everybody, > > > > Right now, the snakeyaml package in fedora is out of date by more than > > three years (1.17, released in February 2016). We plan to merge the PR > > rebasing it to the latest version (1.25, released this month) into > > master / rawhide and f31. The new versions include *a lot of bug > > fixes*, and some minor backwards-incompatible changes. > > > > https://src.fedoraproject.org/rpms/snakeyaml/pull-request/3 > > > > I ran test rebuilds of dependent packages in a COPR repository, and > > every package that isn't already broken built successfully, except > > jruby: > > > > https://copr.fedorainfracloud.org/coprs/decathorpe/snakeyaml-pr/monitor/ > > > > I checked JRuby upstream vs. the jruby package in fedora, and the > > version we ship was released in August 2015 (!). I think compatibility > > with the latest snakeyaml versions should be fixed with 9.2.0.0 and > > newer, according to the upstream changelog (the versioning jumped from > > 1.7.x series to "jruby 9000", with 9.x.y.z). > > > > If I ran the repoqueries correctly, JRuby is also only required by two > > packages in fedora, both related to JRuby itself (joni and > > jruby-maven-plugins). > > > Well, JRuby is Ruby interpreter and in theory can run whatever Ruby code > available in Fedora. And better integration with other Ruby packages in > Fedora was always the plan. Yeah, that's what I assumed after skimming the Ruby packaging guidelines. > However, the problem of JRuby is that it is written in Java and I don't > have enough expertise, together with different priorities, to properly > maintain the package. Given this, the situation around java and another > dependency (properties-maven-plugin) which is currently orphaned, it is > probably time to orphan/retire the package from Fedora .... According to the snakeyaml changelog, the "minor backwards-incompatible changes" should be either slightly changed method signatures or renamed methods. So, *in theory*, it shouldn't be too difficult to adapt jruby to these changes. But I agree - if none of the people who are interested in (j)ruby have enough Java expertise to fix this, it might really be time to orphan or eventually retire the package. I'm sad to say that I don't have the Java skills (nor the time) to tackle this myself - the Java code I had to write for university courses didn't prepare me for dealing with this ;) Fabio > Of course any volunteers who could help are welcome. > > > Vít > > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
