On Sun, 15 Jun 2025 at 19:52, Ranjan Maitra via users <
users@lists.fedoraproject.org> wrote:

> I have a program called gbuffy which is very old, but used to compile fine
> in F41 (and even in F42).
>
> I am able to create a RPM but I have a strange problem in that while
> installing it, I get:
>
> $ sudo dnf install ../RPMS/x86_64/gbuffy-0.2.8-3.fc42.x86_64.rpm
>  Updating and loading repositories:
>  Repositories loaded.
>  Failed to resolve the transaction:
>  Problem: conflicting requests
>   - nothing provides libcrypto.so.1.1()(64bit) needed by
> gbuffy-0.2.8-3.fc42.x86_64 from @commandline
>   - nothing provides libssl.so.1.1()(64bit) needed by
> gbuffy-0.2.8-3.fc42.x86_64 from @commandline
>   - nothing provides libssl.so.1.1(OPENSSL_1_1_0)(64bit) needed by
> gbuffy-0.2.8-3.fc42.x86_64 from @commandline
>  You can try to add to command line:
>   --skip-broken to skip uninstallable packages
>
> I do not understand what the issue is. The spec file explicitly disables
> openssl and does not even require it.
>

As Marco implies, I'm pretty sure the rpmbuild process looks at the staged
files during build and package, and calculates the required dependencies
for the packaged binaries.

cf:
https://rpm-software-management.github.io/rpm/manual/dependency_generators.html

So although your SPEC file doesn't explicitly call for libcrypto.so.1.1, if
you examine the rpmbuild steps, you'll probably see one of the steps
ldd-ing the binaries and auto-calculating dependencies.

Regardless of the SPEC, what does `rpm -qp --requires
../RPMS/x86_64/gbuffy-0.2.8-3.fc42.x86_64.rpm` say?
-- 
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to