On Mon, Mar 18, 2013 at 9:59 AM, Juerg Haefliger <juergh@gmail.com> wrote:

On Mon, Mar 18, 2013 at 9:40 AM, Sandro "red" Mathys
<red@fedoraproject.org> wrote:
> On Mon, Mar 18, 2013 at 9:21 AM, Juerg Haefliger <juergh@gmail.com> wrote:
>>
>> > cloud-utils has broken dependencies in the epel-6 tree:
>> > On i386:
>> > cloud-utils-0.27-0.2.bzr216.el6.noarch requires qemu-img
>> > On ppc64:
>> > cloud-utils-0.27-0.2.bzr216.el6.noarch requires qemu-img
>> > Please resolve this as soon as possible.
>>
>> Is this something that I need to fix or can I ignore it?
>
>
> You should fix this. But unless cloud-utils can somehow work without
> qemu-img, the solution will simply be to stop building for i386 and ppc64.
> RHEL only provides qemu-img for x86_64 and attempts to bring it to the other
> architectures through EPEL were met with issues (see
> https://bugzilla.redhat.com/show_bug.cgi?id=877259).
>
> The line you need for EL6 builds would be:
> ExclusiveArch: x86_64

That make sense, thanks. Now how would I go about this process-wise?
I'd like to keep the same spec file for both Fedora and EPEL and could
do some %{?rhel} magic but then I need to update all branches master,
f18 and el6 and push a new f18 package? Or does it make more sense to
update the el6 branch only?

Figure there's several ways to do this. I'd do some macro magic and commit the same spec file to all branches. But as there's no changed in f18 / f19 / rawhide, I'd only initiate a new build on el6 though doing builds on all platforms without pushing them as updates won't do much harm, either.

But since this problem is only really relevant to koji (i.e. the users are unaffected), I think building it once for only just el6 is enough - you shouldn't even need to push an update at all. It's just about stopping koji from trying to build packages for those architectures.

-- Sandro