Re: Handling packages with missing dependencies provided by HA-RS repos?

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

 





On Thu, Mar 10, 2022 at 2:17 PM Diego Herrera <dherrera@xxxxxxxxxx> wrote:
I've been checking the packages that won't install on EPEL [1] and found out that drbd-pacemaker cant get installed
because of a missing dependency (pacemaker). While researching why, I saw that pacemaker exists on EPEL7 because it's
provided by the HighAvailability repo, but by policy [2] that repo is not a base for EPEL8 nor EPEL9.

When I asked on how to handle this cases on the steering meeting, some proposed ideas were:

* Rebuild the dependencies as -epel
* Retire the packages
* Bringing back HA & RS repo

The only other package that i've found also has this problem is resalloc-aws that depends on awscli.

Is there a policy on this cases? Are EPEL packages allowed to require packages outside of the policy approved?
I would like more feedback on how to proceed so we can file bugs for this packages correctly.

Package: drbd-pacemaker-9.20.2-1.el9
Error: Problem: conflicting requests - nothing provides pacemaker needed by drbd-pacemaker-9.20.2-1.el9.x86_64

Package: resalloc-aws-1.1-1.el9
Error: Problem: conflicting requests - nothing provides awscli needed by resalloc-aws-1.1-1.el9.noarch

Package: drbd-pacemaker-9.17.0-1.el8
Error: Problem: conflicting requests - nothing provides pacemaker needed by drbd-pacemaker-9.17.0-1.el8.x86_64

[1] https://tdawson.fedorapeople.org/epel/willit/epel8/status-wont-install.html
[2] https://docs.fedoraproject.org/en-US/epel/epel-policy/#_policy

Someone can tell me I'm wrong, but I believe if something is in HA or RS in RHEL8 or 9 it is fair game for EPEL8 or EPEL9.
Those packages are currently not being excluded when you request a package for epel8 or epel9.

So, my opinion, build pacemaker in EPEL.

Troy

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

[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux