Jakub Jelen via devel venit, vidit, dixit 2026-07-24 10:45:31: > Sounds like the so version is confusingly based on the major openssl > version so I guess this should have been caught by the openssl 4 rebuild. > > Anyway, I just built the openssl-pkcs11 (libp11) in side tag > (f45-build-side-144557): > > https://koji.fedoraproject.org/koji/taskinfo?taskID=148239999 > > Please, rebuild the rng-tools and nextcloud-client (it fails to build due > to requirement on openssl engine and is in the non-responsive maintainer > territory now): > > fedpkg build --target=f45-build-side-144557 > > rng-tools should work without any issues (at least worked in mock for me): > > fedpkg mockbuild -- --addrepo=' > https://kojipkgs.fedoraproject.org/repos/f45-build-side-144557/latest/x86_64 > > the nextcloud-client needs removal of openssl-devel-engine and migration to > OpenSSL 4, which did not happen. Currently the build still fails: > > /builddir/build/BUILD/nextcloud-client-4.0.7-build/desktop-4.0.7/src/libsync/clientsideencryption.cpp: > In member function ‘std::pair<QByteArray, OCC::PKey> > OCC::ClientSideEncryption::generateCSR(OCC::PKey, OCC::PKey)’: > /builddir/build/BUILD/nextcloud-client-4.0.7-build/desktop-4.0.7/src/libsync/clientsideencryption.cpp:2030:42: > error: invalid conversion from ‘const X509_name_st*’ to ‘X509_NAME*’ {aka > ‘X509_name_st*’} [-fpermissive] > 2030 | ret = X509_NAME_add_entry_by_txt(x509_name, v.first, > MBSTRING_ASC, (const unsigned char*) v.second, -1, -1, 0); > | ^~~~~~~~~ > | | > | const X509_name_st* > In file included from /usr/include/libp11.h:34, > from > /builddir/build/BUILD/nextcloud-client-4.0.7-build/desktop-4.0.7/src/libsync/clientsideencryptionprimitives.h:11, > from > /builddir/build/BUILD/nextcloud-client-4.0.7-build/desktop-4.0.7/src/libsync/clientsideencryption.h:11, > from > /builddir/build/BUILD/nextcloud-client-4.0.7-build/desktop-4.0.7/src/libsync/clientsideencryption.cpp:6: > /usr/include/openssl/x509.h:1072:43: note: initializing argument 1 of ‘int > X509_NAME_add_entry_by_txt(X509_NAME*, const char*, int, const unsigned > char*, int, int, int)’ > 1072 | int X509_NAME_add_entry_by_txt(X509_NAME *name, const char *field, > int type, > | ~~~~~~~~~~~^~~~
FTR: There's an easy fix for that one, which can be backported. The more severe problem is the lack of engine support. Even on its develop branch (34.something), nextcloud-client includes openssl/engine.h. Now, curiously, nextcloud-client 4.0.11 (with the const fix, engine dep removed) builds until this one: /usr/bin/ld.bfd: ../../bin/libnextcloudsync.so.4.0.11: undefined reference to `ENGINE_get_default_RSA' Does this mean we still have the header in Fedora's openssl, but not the symbol in the lib? Is Fedora doing something different in openssl compared to upstream? Otherwise every distro would face the same problem as we do. Michael -- _______________________________________________ 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
