Re: Thoughts: epel-release auto-enable crb repo

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

 



Am 13.06.22 um 13:41 schrieb Josh Boyer:
On Sun, Jun 12, 2022 at 6:50 AM Sérgio Basto <sergio@xxxxxxxxxx> wrote:

On Sun, 2022-06-05 at 00:54 +0200, Neal Gompa wrote:
Let me start with examples that I get *regularly*: Pagure fails to
install from EPEL on RHEL/CentOS/Alma/etc. because python3-markdown
is
not available. KDE Plasma fails to install because of a mass of
missing dependencies.

if epel use  crb to build some package, crb should be enabled when we
install epel repo, yes , that is my opinion

If the dependency is only needed at build time, which is what CRB
content is intended for, then there is no reason to default to having
CRB enabled because nothing will be installed from CRB anyway.  The
issue that people are running into is that EPEL packages have
developed *runtime* dependencies on CRB content.  For a subset of
users, that is probably fine.  However, if a package needs something
at runtime it would be better to first inquire about putting that
dependency in BaseOS or AppStream rather than just blindly using it
from CRB.


Not sure if there is a misconception but crb repo has all kind of
packages also runtime ones. The concept that RH is applying against
crb is; supported or not supported period. Everthing else would mean
that RH should move everything without -devel in %{NAME} into appstream or baseos.

Example (powertools aka crb):

#repoquery --repoid=powertools  ladspa
Last metadata expiration check: 1 day, 1:43:56 ago on Sun Jun 12 13:02:39 2022.
ladspa-0:1.13-20.el8.x86_64

# rpm -ev --test ladspa.x86_64
error: Failed dependencies:
	ladspa is needed by (installed) rubberband-1.9.0-1.el8.x86_64

# repoquery --repoid=epel rubberband
Last metadata expiration check: 1 day, 1:44:41 ago on Sun Jun 12 13:02:40 2022.
rubberband-0:1.9.0-1.el8.x86_64

# repoquery --repoid=powertools  ladspa-devel
Last metadata expiration check: 1 day, 1:46:06 ago on Sun Jun 12 13:02:39 2022.
ladspa-devel-0:1.13-20.el8.i686
ladspa-devel-0:1.13-20.el8.x86_64


--
Leon
_______________________________________________
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