Considering to reset the Ruby 3.3 release back to -1

[Vít Ondruch]

Hi,




Looking closer at the power_assert, it seem that



2) We have separate rubygem-power_assert, which has higher NVR in any case.




Cheers,


Vít

Looking at the versions of subpackages, it seems that the only concerning package is rubygem-power_assert, where the version has not changed between Ruby 3.2 and Ruby 3.3. Otherwise all the versions  were bumped. 1) The content is still the same, so having older version around should not be a problem. Therefore, I think it should be safe to reset the release back to -1. Is there any concern or something I am missing?

OpenPGP_signature.asc
Description: OpenPGP digital signature

--
_______________________________________________
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org
To unsubscribe send an email to ruby-sig-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/ruby-sig@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue