Recently, I've been participating in some discussion as to how to enable
C++11 support for EPEL builds. Specifically, R (and its large universe
of addons in CRAN) would benefit significantly from C++11 support.
After much discussion, it seems like the only sane way to do this is to
use the Red Hat
On 01/03/2018 11:17 AM, Stephen John Smoogen wrote:
> 1. Peter Robinson's DTS enablement request
> A. What packages require it (chromium etc)
> B. Is there a version in CentOS?
>i. If not is it possible for it to exist in CentOS?
> ii. If not what work would a CentOS version take and how
On 01/31/2018 10:53 AM, Stephen John Smoogen wrote:
> So we have a problem with what is the canonical place for SCL's. I was
> going from http://mirror.centos.org/centos/7/sclo/ which just says x86_64.
Even just getting x86_64 devtoolset into the potential buildroot for
EPEL would be hugely helpf
On 02/07/2018 05:24 PM, Stephen John Smoogen wrote:
> Status Report:
>
> I have gotten scl's for RH PPCLE and x86_64 downloaded to the Fedora
> Infrastructure batcave. I have not been able to get aarch64
> downloaded. I need help here on getting the cdn address correct.
>
> I need someone from r
https://developers.redhat.com/blog/2018/10/24/gcc-8-and-tools-now-in-beta-for-red-hat-enterprise-linux-6-and-7/
Can we get this beta into the epel build root? Chromium needs this to build
again.
Thanks,
~tom
___
epel-devel mailing list -- epel-devel@li
On 10/30/18 11:19 AM, Stephen John Smoogen wrote:
> On Tue, 30 Oct 2018 at 10:36, Tom Callaway wrote:
>>
>> https://developers.redhat.com/blog/2018/10/24/gcc-8-and-tools-now-in-beta-for-red-hat-enterprise-linux-6-and-7/
>>
>> Can we get this beta into the epel build r
Just checking in on this again, still need this update to build Chromium
for EPEL7.
~tom
On 11/2/18 1:05 PM, Tom Callaway wrote:
>
>
> On 10/30/18 11:19 AM, Stephen John Smoogen wrote:
>> On Tue, 30 Oct 2018 at 10:36, Tom Callaway wrote:
>>>
>>> https://deve
Building chromium-76.0.3809.132-3.el8 for epel8-candidate
Created task: 37499863
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=37499863
It fails with:
37499910 buildArch (chromium-76.0.3809.132-3.el8.src.rpm, x86_64): open (
buildhw-03.phx2.fedoraproject.org) -> FAILED: BuildError
Never mind. I was confused by the fact that epel-8 kicks off two builds for
some reason. Looking in the wrong log. Now I get to figure out why
gnome-keyring-devel doesn't exist in EPEL8.
Tom
On Fri, Sep 6, 2019 at 11:12 AM Tom Callaway wrote:
> Building chromium-76.0.3809.132-3.el8 f
