[EPEL-devel] Help understanding failing Koji build

Taylor Braun-Jones taylor at braun-jones.org
Sat May 9 05:36:09 UTC 2015


Moving thread to this list (previously on devel at lists.fedoraproject.org)

On Fri, May 8, 2015 at 6:11 PM, Taylor Braun-Jones <taylor at braun-jones.org>
wrote:

> On Fri, May 8, 2015 at 4:26 PM, Orion Poplawski <orion at cora.nwra.com>
> wrote:
>
>> suitesparse was not properly retired in EPEL.  It's being fixed now.
>> Should
>> be working once the next EL6 repo gen is complete, hopefully 30 minutes
>> or so.
>>
>
> Thanks! I'll try it when I get back on network that is not behind an HTTP
> proxy (the HTTP proxy support in fedpkg is broken[1])
>

So x86_64 and i686 are fixed now - thanks. But ppc64 has the same problem.
From:

https://kojipkgs.fedoraproject.org//work/tasks/4419/9694419/root.log

...
DEBUG util.py:388:  Getting requirements for ceres-solver-1.10.0-4.el6.src
DEBUG util.py:388:   --> cmake28-2.8.11.2-1.el6.ppc64
DEBUG util.py:388:   --> eigen3-devel-3.2.3-1.el6.noarch
DEBUG util.py:388:  Error: No Package found for suitesparse-devel >= 3.4.0-9
DEBUG util.py:499:  Child return code was: 1


I'm actually not clear how Koji/mock do ppc64 builds at all since CentOS
does not exist for ppc64.

Taylor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20150509/cba91863/attachment-0001.html>


More information about the epel-devel mailing list