Re: is there a way to disable dnf from ignoring conflicting requests

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

 



On Sun, Jun 15, 2025 at 2:52 PM Ranjan Maitra via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> 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.
>
> The RPM requires libPropList but that RPM (mine) installs without error.
>
> Any suggestions on how I can get around this problem?
>
> Btw, here is the spec file: https://paste.centos.org/view/0e22b18d
>
> However, I am not sure where to put the bz2 or the libPropList RPM, so the spec file can not be compiled without these.
>
> The gbuffy RPM gets built without any error  that it displays.

I can't answer your titular question. However...

    > The gbuffy RPM gets built without any error  that it displays.

OpenSSL 1.1 was deprecated/sunsetted back in September 2023. You
should use OpenSSL 3.x nowadays. Maybe you can rebuild gbuffy using
OpenSSL 3.x? It looks like OpenSSL 3.0 (end of life in September 2025)
or OpenSSL 3.5 (end of life in April 2030) would be good choices.

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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux