[EPEL-devel] Re: execstack on epel 7 ppc64le?

2016-01-05 Thread Orion Poplawski
On 12/23/2015 10:57 PM, Peter Robinson wrote: >> I'm trying to build the ppc64le branch of OpenBLAS on EPEL7. But, I get the >> following error message in the setup phase: >> >> DEBUG util.py:393: Error: No Package found for /usr/bin/execstack >> >> Why would this binary not exist on ppc64le? >

[EPEL-devel] Orphaned Packages in epel6 (2016-01-05)

2016-01-05 Thread opensource
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If

[EPEL-devel] Orphaned Packages in epel5 (2016-01-05)

2016-01-05 Thread opensource
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If

[EPEL-devel] Re: Mass rebuild of EPEL6

2016-01-05 Thread Petr Šabata
On Wed, Dec 23, 2015 at 02:13:09PM -0600, Jason L Tibbitts III wrote: > perl-HTML-Mason-1.42-2.el6.src.rpm Should be fixed in perl-HTML-Mason-1.42-3.el6. P signature.asc Description: PGP signature ___ epel-devel mailing list

[EPEL-devel] Re: Which python3 versions to package for EPEL7?

2016-01-05 Thread Jason L Tibbitts III
> "TK" == Toshio Kuratomi writes: TK> We would have been in a lot better place today if we had separate TK> packaging of python2 and python3 packages in Fedora so that they TK> were never in sync there but that's not something we can probably TK> change now Nothing

[EPEL-devel] Which python3 versions to package for EPEL7?

2016-01-05 Thread Orion Poplawski
So, I've started packaging up a bunch of python3 only packages for EPEL7 for packages that were already in RHEL7. I've started by packaging the latest version of the modules: python34-py.noarch 1.4.30-2.el7 epel-testing python34-setuptools.noarch 19.2-3.el7

[EPEL-devel] Error: No Package found for LibRaw-devel

2016-01-05 Thread Ding Yi Chen
When I am building evas-generic-loaders-1.16.0-1.el7.src.rpm, I see this: Error: No Package found for LibRaw-devel LibRaw-devel for epel7 is retired, but is available in @rhel-7-workstation-optional-beta-rpms What should I do to let koji know where to get LibRaw-devel? Regards, -- Ding-Yi Chen

[EPEL-devel] Fedora EPEL 5 updates-testing report

2016-01-05 Thread updates
The following Fedora EPEL 5 Security updates need testing: Age URL 808 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2013-11893 libguestfs-1.20.12-1.el5 573 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2014-1626 puppet-2.7.26-1.el5 422

[EPEL-devel] Re: Which python3 versions to package for EPEL7?

2016-01-05 Thread Toshio Kuratomi
On Tue, Jan 05, 2016 at 08:07:22PM -0700, Orion Poplawski wrote: > So, I've started packaging up a bunch of python3 only packages for EPEL7 for > packages that were already in RHEL7. I've started by packaging the latest > version of the modules: > > python34-py.noarch 1.4.30-2.el7

[EPEL-devel] Fedora EPEL 7 updates-testing report

2016-01-05 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 303 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 95 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-925e9374c9 python-pymongo-3.0.3-1.el7 65