[EPEL-devel] Re: 32 bit revisited

2016-10-20 Thread Kevin Fenzi
On Sun, 16 Oct 2016 21:54:44 -0700 Karsten Wade wrote: > On 10/15/2016 10:43 AM, Kevin Fenzi wrote: > > On Sat, 15 Oct 2016 07:54:25 + (UTC) > > john tatt wrote: > > > >> HiSo almost one year ago, some people asked for a 32bits EPEL 7 > >> repo, as

[EPEL-devel] Orphaned Packages in epel5 (2016-10-20)

2016-10-20 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] Fedora EPEL 6 updates-testing report

2016-10-20 Thread updates
The following Fedora EPEL 6 Security updates need testing: Age URL 470 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 464 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 395

[EPEL-devel] Re: 32 bit revisited

2016-10-20 Thread Matthew Miller
On Thu, Oct 20, 2016 at 12:55:02PM -0700, Karsten Wade wrote: > Part of my thinking is the situation where CentOS SIGs need EPEL > packages and (aiui currently) have to import to git.centos.org and build > the packages on cbs.centos.org. Do you mean for 32-bit in specific, or in general? In that

[EPEL-devel] Re: 32 bit revisited

2016-10-20 Thread Matthew Miller
On Thu, Oct 20, 2016 at 01:45:01PM -0700, Karsten Wade wrote: > > Do you mean for 32-bit in specific, or in general? In that case, why > > import instead of just using the packages directly? > I think it's the same situation that Fedora has -- if it's not built on > CentOS infra, then it can't be

[EPEL-devel] Orphaned Packages in epel7 (2016-10-20)

2016-10-20 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 epel6 (2016-10-20)

2016-10-20 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: 32 bit revisited

2016-10-20 Thread Karsten Wade
cOn 10/20/2016 07:06 AM, Kevin Fenzi wrote: > On Sun, 16 Oct 2016 21:54:44 -0700 > Karsten Wade wrote: > >> On 10/15/2016 10:43 AM, Kevin Fenzi wrote: >>> On Sat, 15 Oct 2016 07:54:25 + (UTC) >>> john tatt wrote: >>> HiSo almost one year ago,

[EPEL-devel] Re: 32 bit revisited

2016-10-20 Thread Karsten Wade
On 10/20/2016 01:17 PM, Matthew Miller wrote: > On Thu, Oct 20, 2016 at 12:55:02PM -0700, Karsten Wade wrote: >> Part of my thinking is the situation where CentOS SIGs need EPEL >> packages and (aiui currently) have to import to git.centos.org and build >> the packages on cbs.centos.org. > > Do