This package is present in RHEL8 CRB but not available in EPEL8 for building a package.
No matching package to install: 'http-parser-devel'
Why do you think it's in RHEL8 CRB?
I don't see it.
$ dnf clean all
$ dnf repolist
Red Hat CodeReady Linux Builder for RHEL 8 x86_64 (RPMs) 3.5 kB/s | 4.5 kB 00:01
$ dnf install http-parser-devel
No match for argument: http-parser-devel
Error: Unable to find a match
http-parser is in RHEL8. But not it's -devel package. It's not in appstream, baseos, or CRB.
According to the PES system it should be there. Let me open a BZ.
http-parser-devel is now available for EPEL8.
Please build your packages.
I believe this ticket can be closed.
The packages are from the CentOS Devel repo which should have a repo file like this
# This should work for devel repo
name=CentOS-$releasever - Devel
Metadata Update from @smooge:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)
Note1: The above information is for mock/copr/local builds. You do not have to do anything to build in EPEL8.
Note2: The solution isn't perfect. The biggest problem is that there are no s390x packages. But we figured it was better than no -devel packages at all.
Workaround: In your EPEL8 rpm specs you will have to use ExcludeArch, ExclusiveArch, %ifarch, or %ifnarch so that your builds do not build on s390x, or skip that library for s390x.
Example: Put the following line in your spec file.
@tdawson @smooge Is there a particular reason http-parser-devel is missing from s390x? It does not look like a arch-specific library to me?
We have to use the CentOS development libraries to get this and they do not build against s390 because they have no s390 builder. And even if they are 'no-arch' they may call in items which s390 does not contain elsewhere. We do not have the manpower to go over the list of packages (and we would need to do this everytime there is an update to them) and work it out for this arch.
Ok, makes sense. Would that change when
When RHEL 8.2 (and 8.3 when it comes out) everything that is in CRB at that time will be available for EPEL8, on all arches.
So if your -devel package makes it to CRB, you will be able to take out the s390x exclusion at that time.
to comment on this ticket.