Fedora EPEL - sequoia-sq package and "cli breakages"

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

 




Hi,

Has something changed in the Fedora EPEL packaging policy in regards to package stability?

Since the updates which has arrived since early December 2024, the updates to sequoia-sq has twice broken my automated scripts.

The first update which broke my scripts changed --recipient-file to --for-file. And on Friday another update arrived which added now a required --without-signature or a --signer-* argument.

Rest assure, I understand the importance of upgrading packages, add improvements and even the signing aspect in PGP. But my understanding has been that the EPEL packages should be more stable than this.

Or is the command line interface excluded from the stability aspect in the Fedora EPEL policy?

* <https://docs.fedoraproject.org/en-US/epel/epel-policy/#guidelines_and_backgrounds_for_this_policy> * <https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/>


--
kind regards,

David Sommerseth

--
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux