RFC: incompatible upgrade of catch for EPEL; packages that do not rebuild to be retargeted to catch2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

I plan to upgrade catch in epel8 and epel9 to the latest 3.5.4 from Fedora, and introduce catch2 for packages that are currently using EPEL's catch (v2) and won't rebuild against catch v3

❯ fedrq pkgs -P catch-devel -b epel8
catch-devel-2.13.8-1.el8.x86_64

❯ fedrq pkgs -P catch-devel -b epel9
catch-devel-2.13.8-2.el9.x86_64

Plan of action:
- this announcement
- start COPR repos
- rebuild Fedora's latest catch for epel9 and epel8 in the COPR repos
- rebuild Fedora's latest catch2 in the COPR repos
- rebuild dependent packages
- if any of them fail, switch to catch2 and try again

(until this point, nothing will be committed to dist-git or built - per the incompatible upgrade policy, I'm waiting for a week of discussion first)

- build new catch and catch2 in side tag
- submit PRs to packages that need change, with instructions on how to build against the side tag
- merge and build the unbuilt packages with provenpackager after another week

The list of potentially affected packages:

❯ fedrq whatrequires --src -P catch-devel -b epel8
cppzmq-4.4.1-1.el8.src
et-6.2.1-2.el8.src
flamethrower-0.11.0-7.el8.src
gulrak-filesystem-1.5.14-1.el8.src
rttr-0.9.6-3.el8.src

❯ fedrq whatrequires --src -P catch-devel -b epel9
Pencil2D-0.6.6-24.el9.src
cli11-2.2.0-1.el9.src
cppzmq-4.8.1-2.el9.src
et-6.2.1-2.el9.src
gulrak-filesystem-1.5.14-1.el9.src
libopenshot-0.3.2-1.el9.src
rttr-0.9.7-0.1git7edbd58.el9.src
spdlog-1.10.0-1.el9.src
tomlplusplus-3.4.0-1.el9.src

Best regards,

--
 _o) Michel Lind
_( ) identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2

Attachment: OpenPGP_0x8B229D2F7CCC04F2.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux