Le lun. 3 août 2026 à 18:20, Simo Sorce via devel <[email protected]> a écrit : > > On Mon, 2026-08-03 at 17:55 +0200, Nicolas Chauvet wrote: > > Le lun. 3 août 2026 à 15:42, Nicolas Chauvet <[email protected]> a écrit : > > > > > > With the new cryptopp-modern upstream we can expect an official SONAME > > > for a shared build along with a lot of buildsys fixes from the switch > > > to cmake instead of using a separated autotools maintained project. > > > > > > There is a migration guide > > > https://www.cryptopp-modern.com/docs/migration/from-cryptopp/ > > > > > > I'm building the update in a side-tag and rebuilding the following > > > dependencies: > > > - clementine > > > - cryfs > > > - tegrarcm > > > > I had to add amule into the list because it was moved to fedora recently. > > > > Also had to disable s390x tests that were failing. It's reported to > > https://github.com/cryptopp-modern/cryptopp-modern/issues/65 > > > > Bodhi ticket submitted: > > https://bodhi.fedoraproject.org/updates/FEDORA-2026-47ddfc7819 > > > > Best regards, > > I am curious, what requires this library? And can't we use an already > vetted cryptography library instead?
Beyond the above list, there is megasync that is maintained in 3rd part repository. I maintain "tegrarcm" that builds with cryptopp in order to sign some code for some tegra devices in recovery mode. amule also uses cryptopp exclusively. Now clementine could be a leftover after a deeper check. and cryfs (likely still bundled despite using a BuildRequires) is been rewritten in rust with 2.x -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
