[EPEL-devel] Intent to update openjpeg2 from 2.1.0 to 2.3.0

Openjpeg2 has MANY CVE bugs reported against it and most are fixed with the current release. I have run abi-compliance-checker on the packages and it shows 100% binary compatibility so there should not be a problem. Thanks, Richard ___ epel-devel

[EPEL-devel] Re: CMake 3.11.0 on epel7

On Tue, Apr 10, 2018 at 4:57 AM, Antonio Trande wrote: > Hello everyone. > > I wish to update CMake3 to the version 3.11.0 on epel7. > SRPM: https://sagitter.fedorapeople.org/cmake3-3.11.0-1.fc27.src.rpm > > Any objection about? Not from me. I support a module upstream

[EPEL-devel] Re: EPEL 8 Beta/Alpha?

On Wed, Nov 28, 2018 at 5:29 AM Paul Howarth wrote: > On Wed, 28 Nov 2018 10:53:58 +0530 > > I seem to remember that for EL-7 we generally just branched the f19 > packages for epel7, rebuilt and that was pretty much it. > I thought it was more of an "opt-in" situation, that packages that had a

[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes

Will this also allow more significant upgrades of EPEL packages between minor releases? Thanks, Richard ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora

[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes

On Thu, Feb 14, 2019 at 10:24 AM Stephen John Smoogen wrote: > On Thu, 14 Feb 2019 at 11:19, Richard Shaw wrote: > > > > On Thu, Feb 14, 2019 at 10:14 AM Stephen John Smoogen > wrote: > >> > >> On Thu, 14 Feb 2019 at 09:34, Richard Shaw > wrote:

[EPEL-devel] Re: Proposed EPEL policy change: Minor release based composes

On Thu, Feb 14, 2019 at 10:14 AM Stephen John Smoogen wrote: > On Thu, 14 Feb 2019 at 09:34, Richard Shaw wrote: > > > > Will this also allow more significant upgrades of EPEL packages between > minor releases? > > > > That is the purpose if the package maint

[EPEL-devel] EPEL 8 not finding buildroot overrides

I have hdf5 (amongst others) in a buildroot override but when I tried to build OpenImageIO I got the following errors in root.log: DEBUG util.py:585: BUILDSTDERR: No matching package to install: 'hdf5-devel' I'm I missing something? Ok, as I write this and investigate more it get's weirder...

[EPEL-devel] Re: EPEL 8 not finding buildroot overrides

Here's the link... https://bodhi.fedoraproject.org/overrides/hdf5-1.10.5-3.el8 Which is showing as active. Thanks, Richard ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] 2 weeks in testing for new packages?

Does it make sense for packages to wait in testing for two weeks when they are new packages? For example, all the packages I'm building for the first time in epel8... Even outside of new packages I rarely get karma for my Fedora packages, much less for my EPEL packages and two weeks is a "long

[EPEL-devel] Re: About packages present in epel-7 and missing from epel-8

Packages from EPEL 7 don't make it automatically make it into EPEL 8. The package maintainer has to request EPEL 8 branches. You can either request that the maintainer support an EL 8 branch via email, -ow...@fedoraproject.org, or submit the request in bugzilla (more formal request). Thanks,

[EPEL-devel] Re: Outstanding package requests for EPEL-8

Add txt2man, it got filed against el6 for some reason. I just fixed it. https://bugzilla.redhat.com/show_bug.cgi?id=1741795 Thanks, Richard ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Re: Outstanding package requests for EPEL-8

On Fri, Oct 25, 2019 at 11:14 AM Troy Dawson wrote: > On Fri, Oct 25, 2019 at 9:10 AM Richard Shaw wrote: > > > > On Fri, Oct 25, 2019 at 9:16 AM Troy Dawson wrote: > >> > >> All of the ones I've requested, I waited a few days to see if the > >> main

[EPEL-devel] Re: Outstanding package requests for EPEL-8

On Fri, Oct 25, 2019 at 9:16 AM Troy Dawson wrote: > All of the ones I've requested, I waited a few days to see if the > maintainer would pick it up. And after that I asked if they would > mind if I maintained it in EPEL8. About half of those the maintainer > was fine with me maintaining the

[EPEL-devel] Re: Added arches but no automatic rebuild?

On Wed, Feb 12, 2020 at 9:18 AM Stephen John Smoogen wrote: > > > On Wed, 12 Feb 2020 at 09:46, Richard Shaw wrote: > >> I'm sure it was announced but I've been very busy lately but while trying >> to build a package for EPEL 8 I noticed that two builds (arche

[EPEL-devel] Added arches but no automatic rebuild?

I'm sure it was announced but I've been very busy lately but while trying to build a package for EPEL 8 I noticed that two builds (arches) failed for missing dependencies but two did not. I see that there are a number of arches not originally part of RHEL 8, which is fine, but when the arches

[EPEL-devel] Re: Removal of mingw-* packages from EPEL 7

I agree. If you're actively developing for windows you should be running Fedora not EL. Thanks, Richard ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora

[EPEL-devel] Re: Added arches but no automatic rebuild?

On Wed, Feb 12, 2020 at 9:24 AM Pat Riehecky wrote: > I'm showing: > > # Needed until LibRaw is available on s390x and aarch64 > %if 0%{?rhel} >= 8 > ExclusiveArch: x86_64 ppc64le > %endif > > Within the SPEC file. > Whoops, mea culpa, I forgot about that work around. Slept to many times since

[EPEL-devel] How to deal with dependencies from Power Tools repo

I have build BackupPC for EPEL 8 and got a few of the dependencies in EPEL as well that aren't provided by the base repo. One of the dependencies is provided by the Power Tools repo, but when trying to install of course it just gives the default error that a dependency cannot be met. How can I

[EPEL-devel] Extras not enabled on koji?

I'm trying to build a package that requires swig 3.0.12+. The version in EPEL is way too old but swig3 is provided in the extras repo. I was able to build locally via mock and COPR fine, but when I tried official builds it doesn't look like the "extras" repo is enabled. Is that on purpose?

[EPEL-devel] Re: Extras not enabled on koji?

On Sat, Apr 4, 2020 at 2:27 PM Stephen John Smoogen wrote: > > On Sat, 4 Apr 2020 at 14:54, Richard Shaw wrote: > >> I'm trying to build a package that requires swig 3.0.12+. The version in >> EPEL is way too old but swig3 is provided in the extras repo. >> >>

[EPEL-devel] Hints for manual upgrading from CentOS 8 Stream to CentOS / Alma / Rockey 9

I know upgrades are not supported but its for a small home server that really only does two things: BackupPC and Unifi (which I both maintain) Anyone had success doing manual upgrades or did you start with a reinstall? Thanks, Richard ___ epel-devel