(Moving to EPEL list)
On 8/15/19 10:22 PM, Richard Shaw wrote:
I assume this is because LibRaw is available in RHEL but only for x86_64
and ppc64le?
So I'm assuming there is some sort of procedure to build only for s390x
and aarch64 for EPEL?
Yes, many libs appear to be missing on those
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
Troy,
I did fedpkg request-branch epel8 and it did indeed make two issues.
Looking back at all issues that I previously had requested, last time it
only made one issues for epel8 and did not make the epel8-playground
issue. I wonder how many other people had or will have the same
problem. I
The following builds have been pushed to Fedora EPEL 6 updates-testing
clustershell-1.8.2-1.el6
procenv-0.51-1.el6
python-regex-2019.06.08-1.el6
Details about builds:
clustershell-1.8.2-1.el6
Note: I am not an expert of gcc-objc.
I just see that it wasn't built with the RHEL8 gcc and I'm answering
accordingly.
Someone else might have different, better answers.
On Thu, Aug 15, 2019 at 9:14 AM Orion Poplawski wrote:
>
> What to do about missing gcc-objc from RHEL8?
Open a customer
The following builds have been pushed to Fedora EPEL 8 updates-testing
Lmod-8.1.10-2.el8
aalib-1.4.0-0.37.rc5.el8
byobu-5.129-2.el8
clustershell-1.8.2-1.el8
cros-guest-tools-1.0-0.16.20190815git4e1b573.el8
dar-2.6.5-2.el8
hdf-4.2.14-5.el8
libxsmm-1.13-2.el8
On 8/15/19 7:31 AM, Troy Dawson wrote:
> Oh ... then there really is a problem. 12 hours (or longer) is a very
> long time for a package to not make it into the repo. The longest I
> had to wait was 4 hours, because I was doing things in the middle of
> the F31 mass rebuild.
> I'm afraid helping
What to do about missing gcc-objc from RHEL8? Are there alternative compilers
yet that we can access? Will we have to package gcc-objc for EPEL8 separately?
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380
Oh ... then there really is a problem. 12 hours (or longer) is a very
long time for a package to not make it into the repo. The longest I
had to wait was 4 hours, because I was doing things in the middle of
the F31 mass rebuild.
I'm afraid helping with this is above my fedora permissions. I
That's not the error I was getting. I gave it a try also, and got the
same error as you.
I'd say, re-request the branches. When they try to re-make a branch
that is already there, it will just say that the branch is already
there, if it isn't, then it will make it. No real harm in
10 matches
Mail list logo
