On Fri, Aug 29, 2025 at 08:53:17PM +0200, Michael J Gruber wrote: > Hi there > > This takes possible RHEL/EPEL friction to a new level. We're used to > packages which are built for RHEL but shipped partially only (libs > without devel). "Moving" a package from EPEL to RHEL, i.e. shipping it > in RHEL and thus forcing it out of EPEL, and then dumping some of the > arches is really a new level of unnecessary surprises.
I agree that it's not great, but I'd like to explain why these sorts of things happen: (1) A dependency is needed for another RHEL package, so the package is moved to RHEL. The duplicated package in EPEL gets deleted. (2) Red Hat is on the hook to support everything that is shipped in RHEL Base and AppStream (as in, customers will pick up the phone and call us, and some engineer might be called up to fix it), so we try to remove anything that isn't necessary and/or we don't want to support. (3) But there are unsupported RHEL channels (like CRB), where packages are distributed by Red Hat, but marked as unsupported. (It's possible for different arches to be directed to different channels). Or it could be the developer agrees to support it in AppStream. (4) People are in a hurry, shortcuts are taken, bugs happen. The good news is the process is much more open now than it used to be. All the bugs, comments, the eventual pull request which fixed this, and the build system, are public, which is quite a bit different from Microsoft, Apple, Google, Oracle, etc. Rich. > Thanks for reporting the issue! > > Michael > > Mikel Olasagasti venit, vidit, dixit 2025-08-29 13:34:15: > > Hi Federico, > > > > python-colorama has been included in RHEL and retired from EPEL. It's > > part of awscli's dependency chain and as awscli is only built for > > x86_64 and aarch64 RHEL only ships dependencies for those > > architectures. Issue has been reported to Red Hat in > > https://issues.redhat.com/browse/RHEL-96267 > > > > Check https://bugzilla.redhat.com/show_bug.cgi?id=2391489#c3 for more > > details. > > > > Best regards, > > Mikel Olasagasti > > > > Hau idatzi du Federico Pellegrin (f...@evolware.org) erabiltzaileak > > (2025 abu. 29(a), or. (13:23)): > > > > > > > > > > > > Hello, > > > I'm having some difficulties to understand a failure on Koji on Fedora > > > EPEL10 and was wondering if someone could maybe help me, as I did a few > > > tries but couldn't figure out if I'm doing something wrong (and > > > especially, due to seemingly depending on the arch, I cannot reproduce > > > with mockbuild or similar local tools). > > > > > > The failure is this one for example: > > > https://koji.fedoraproject.org/koji/taskinfo?taskID=136495437 > > > > > > It is a Python package, which requires tox. It seems to work fine for > > > x86_64 and aarch64, but for ppc and s390 seems to be missing a dependency > > > python3.12dist(colorama) which as far as I see should be even noarch (and > > > is found in the x86_64 and aarch64 builds). Colorama is from 10 not > > > anymore in EPEL but went to the base distro I understand. > > > > > > But if I check (assuming I got it right the AppStream repo used) indeed I > > > find it here: > > > https://infrastructure.fedoraproject.org/repo/centos/centos-10/AppStream/x86_64/os/Packages/ > > > https://infrastructure.fedoraproject.org/repo/centos/centos-10/AppStream/aarch64/os/Packages/ > > > > > > but not here in the two failing arch: > > > https://infrastructure.fedoraproject.org/repo/centos/centos-10/AppStream/ppc64le/os/Packages/ > > > https://infrastructure.fedoraproject.org/repo/centos/centos-10/AppStream/s390x/os/Packages/ > > > > > > Is it a bug in AppStream itself therefore? > > > > > > Many thanks! > > > Federico > > > > > > -- > > > _______________________________________________ > > > devel mailing list -- devel@lists.fedoraproject.org > > > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > > > Do not reply to spam, report it: > > > https://pagure.io/fedora-infrastructure/new_issue > > -- > > _______________________________________________ > > devel mailing list -- devel@lists.fedoraproject.org > > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > -- > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
