On Tue, Sep 15, 2020 at 10:53:10AM +0200, Pavel Raiskup wrote:
> Hi, we ship epelplayground-8-x86_64.cfg file in mock-core-configs so users can
> reproduce builds locally with mock. Initially the configuration worked, but
> it
> has been failing for quite some time now. Dnf isn't able to --insta
The following Fedora EPEL 8 Security updates need testing:
Age URL
11 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-2390c71f9c
chromium-85.0.4183.83-1.el8
7 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-0214580ca4
mbedtls-2.16.8-1.el8
4 https://bodhi.fedorap
On Mon, Sep 14, 2020 at 09:42:36AM -0700, Michel Alexandre Salim wrote:
> I wonder if these are two separate concerns though? I agree that being
> able to indicate a package should always be branched would be great,
> but... epel-sig / epel-wranglers might not find a package relevant in a
> new EL
This is the second draft. It has added a section in the developer
section saying to clean your packages up when you are done playing and
testing them.
Edit's are still welcome, but I think it covers everything that has
been discussed and approved.
This will be published about the same time that
-
On Tue, Sep 15, 2020 at 1:53 AM Pavel Raiskup wrote:
>
> Hi, we ship epelplayground-8-x86_64.cfg file in mock-core-configs so users can
> reproduce builds locally with mock. Initially the configuration worked, but
> it
> has been failing for quite some time now. Dnf isn't able to --installroot:
Hi, we ship epelplayground-8-x86_64.cfg file in mock-core-configs so users can
reproduce builds locally with mock. Initially the configuration worked, but it
has been failing for quite some time now. Dnf isn't able to --installroot:
No matches found for the following disable plugin patterns:
