Re: [EPEL-devel] Help understanding failing Koji build
Thanks, I'll just go with option 1 since ceres-solver itself has some unresolved big endian issues anyway. On Sat, May 9, 2015 at 10:16 AM, Orion Poplawski or...@cora.nwra.com wrote: On 05/08/2015 11:36 PM, Taylor Braun-Jones wrote: Moving thread to this list (previously on de...@lists.fedoraproject.org mailto:de...@lists.fedoraproject.org) On Fri, May 8, 2015 at 6:11 PM, Taylor Braun-Jones tay...@braun-jones.org mailto:tay...@braun-jones.org wrote: On Fri, May 8, 2015 at 4:26 PM, Orion Poplawski or...@cora.nwra.com mailto:or...@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. So, the first thing to clarify is that EPEL builds against RHEL, not CentOS. And unfortunately RHEL ppc64 is missing some packages as well, suitesparse may be one of them. I'll let someone who has direct access confirm. Choices are: - Add ExcludeArch: ppc64 to ceres-solver - Resurrect suitesparse in EPEL as a limited arch package: https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] Help understanding failing Koji build
On 05/08/2015 11:36 PM, Taylor Braun-Jones wrote: Moving thread to this list (previously on de...@lists.fedoraproject.org mailto:de...@lists.fedoraproject.org) On Fri, May 8, 2015 at 6:11 PM, Taylor Braun-Jones tay...@braun-jones.org mailto:tay...@braun-jones.org wrote: On Fri, May 8, 2015 at 4:26 PM, Orion Poplawski or...@cora.nwra.com mailto:or...@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. So, the first thing to clarify is that EPEL builds against RHEL, not CentOS. And unfortunately RHEL ppc64 is missing some packages as well, suitesparse may be one of them. I'll let someone who has direct access confirm. Choices are: - Add ExcludeArch: ppc64 to ceres-solver - Resurrect suitesparse in EPEL as a limited arch package: https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA DivisionFAX: 303-415-9702 3380 Mitchell Lane or...@cora.nwra.com Boulder, CO 80301 http://www.cora.nwra.com ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] Help understanding failing Koji build
Moving thread to this list (previously on de...@lists.fedoraproject.org) On Fri, May 8, 2015 at 6:11 PM, Taylor Braun-Jones tay...@braun-jones.org wrote: On Fri, May 8, 2015 at 4:26 PM, Orion Poplawski or...@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 ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
