[EPEL-devel] po4a problems

[Kevin Fenzi]

On Thu, 30 Apr 2015 20:11:23 +0100
Sérgio Basto <sergio at serjux.com> wrote:

> Hi, epel List 
> In bug 1134624 [1] someone asked to build po4a for EPEL 7.
> I miss some reading and po4a is only need to be build for ppc64 ,
> because in meantime CentOS built it, but only for epel 7 not for 6 and
> according Dominik Mierzejewski on comment #23 "... is part of CentOS
> main distribution, which is x86_64 only". So when packages came from
> CentOS they are x86_64 only and this happens with po4a .
> By guidelines in comment #34 , I shouldn't build it with a new version
> which unfortunately happened, I built po4a-0.45 when CentOS build
> po4a-0.44 , but in comment #39 I concluded that is a copy of Fedora
> source which was completely out-date , so I think the best solution
> was Centos updated it also . If not, we need remove po4a-0.45-3.el7
> from epel7 stable , which I haven't way/permissions to do it ... 
> Suggestions please ? 
> 
> [1]
> https://bugzilla.redhat.com/show_bug.cgi?id=1134624

So, this package is in RHEL. 
It's only x86_64 however. 

I can see two ways forward: 

1. Retire po4a in EPEL, and add ExcludeArch: ppc64 to the things that
need it. They will use the RHEL version, the EPEL version will be gone.
However, they won't exist on ppc64. 

2. Make a new po4a package in EPEL that follows the limited arch
package guidelines (ie, is older than the RHEL one). Push it out and we
make sure the "newer" one is gone. Then, epel stuff can build against
that version on both ppc64 and x86_64 and ppc64 users can get that
version from EPEL. 
https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages

kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/epel-devel/attachments/20150501/fa5bf79c/attachment.sig>