Due to several ongoing bugs, we are updating plasma in epel8 to the latest
5.24 version, 5.24.7.
The previous version in epel8 was 5.24.6
It is currently in epel8-testing. You can update to it now with
dnf --enablerepo=epel-testing update
If you would like to leave karma, the bodhi link is her
Hello,
The new ansible (5.x) is in the EPEL stable which works great until
one tries to use some non-trivial modules which require some Python
modules to be available… At that point you realize that the new
Ansible is built against Python 3.8 (default is 3.6) and we don't have
many python38-* pack
EPEL Playground was shut down in January 2022
EPEL 8 Playground was a place that developers and maintainers could "play
around" with updated, or changed packages in epel. EPEL Playground never
really worked out and ended up being more of a burden than helpful.
If developers or maintainers want so
Hello,
I am currently in the middle of retiring all of the epel8-playground
branches.
I apologize for not sending an email ahead of time.
For informations sake, I am retiring them with
fedpkg retire "epel8-playground decommissioned :
https://pagure.io/epel/issue/
136"
Just so people know where
Since the CentOS Devel repo was first created, it has been a part of the
EPEL8 buildroot. It supplied some of the missing devel packages that were
not in any of the RHEL 8 public repos. It was a good concept, and did help
some, but it didn't completely fix the problem.
EPEL eventually came up wit
Hello folks,
I've just noticed that some packages in EPEL 8 are broken when used in
CentOS 8 Stream. One example:
https://bugzilla.redhat.com/show_bug.cgi?id=1989062
which has been broken for a long time now (from well before I decided to
finally report the bug).
EPEL 8 is fundamental for me, I
Hello,
I've opened the following two pull requests to introduce %py3_check_import to
EPEL8 and EPEL7:
https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/31
https://src.fedoraproject.org/rpms/epel-rpm-macros/pull-request/32
So far, there has been no response. Is there anybody will
I just tried to build an R package in copr, and it failed because an R
dependency (which I maintain) needs rebuilding for R 4.
Apart from the question of why R was updated to an incompatible version,
what was supposed to happen about rebuilding things as a consequence? I
got a large amount of noi
My epel8 build for python-extras succeeded just fine (using
python-testtools from a build override as a dependency -
https://bodhi.fedoraproject.org/overrides/python-testtools-2.4.0-3.el8),
but the epel8-playground build claims python-testtools is not available:
epel8:
https://koji.fedoraproje
There does not appear to be an explicit conflict policy for EPEL8:
https://fedoraproject.org/wiki/EPEL/FAQ#Does_EPEL_replace_packages_provided_within_Red_Hat_Enterprise_Linux_or_layered_products.3F
I got a report against python3-s3transfer and python3-botocore
conflicting with the CentOS 8 High
Hi,
I got the request to package `neofetch` for EPEL8 [1]. It's already in
Fedora for quite some time [2]. I have the intention to grant this
request. According to the EPEL packaging guidelines I need to inform
you first of this intention [3]. The package should work fine. If there
are no objecti
DEBUG util.py:596: No available modular metadata for modular package
'python2-rpm-macros-3-38.module+el8.1.0+3111+de3f2d8e.noarch', it cannot
be installed on the system
DEBUG util.py:596: Error: No available modular metadata for modular package
https://koji.fedoraproject.org/koji/taskinfo?tas
After the announcement today of centos-stream, I wonder if it would make
sense to move epel8-playground to build against that instead of the
latest rhel8 release?
It would make playground less usefull for testing new radical changes
against the current stable point release, but on the other hand,
Hi,
I've noticed that (mostly Smooge) has been using the minor release bump
(e.g., the .1 after the ?dist)
[.][.]%{?dist}[.]
in initial EPEL8 package versions that have been branched from Fedora. I
just want to understand the reasoning behind this. I would think the main
motivation would
On 6/4/19 6:25 AM, Miroslav Suchý wrote:
> What is the status of EPEL8? Or more precise - can I - as Mock maintainer -
> do something so we can have EPEL available
> immediately when RHEL is out? Obviously it is too late for RHEL 8, but I am
> looking in future (RHEL9).
>
In the immediate ter
What is the status of EPEL8? Or more precise - can I - as Mock maintainer - do
something so we can have EPEL available
immediately when RHEL is out? Obviously it is too late for RHEL 8, but I am
looking in future (RHEL9).
--
Miroslav Suchy, RHCA
Red Hat, Associate Manager ABRT/Copr, #brno, #fedo
greetings.
As everyone knows, rhel8 was just released. Hurray!
We have been thinking and gathering input from many many people to come
up with a plan for epel8. It will not be as simple or direct as epel7
was, but I think we will have something great when we are done.
Short term:
* We (Fedora i
17 matches
Mail list logo
