Avoid a 32 bits package from being pushed into 64 bits repository

[Rex Dieter]

Alejandro Alvarez Ayllon wrote:

> Hello,
> 
> I co-maintain a package that contains a library that is used as module
> for a server.
> The 32 bits version of this library is pushed automatically into the 64
> bits repositories (i.e. in epel6),
> which doesn't make much sense, since the 64 bits version of the server
> won't run with the 32 bits
> libraries.
> 
> This wouldn't be a big problem, but the pushed 32 bits rpm has a
> dependency on the 32 bits server, so then I will get complains (with
> reason) about the broken package.
> 
> globus-gridftp-server-progs is the server, and dpm-dsi is the module.
> 
> So my question is: how should I approach this? I got some suggestions in
> this ticket
> https://bugzilla.redhat.com/show_bug.cgi?id=957588
> 
> Is there any way I can prevent this rpm from being copied into the 64
> bits repositories?

Packages that contain shared libraries are multilib'd (usually).

One "fix" here would be to put the shared libraries into some -libs subpkg 
that either has no dependencies or a non-arch'd dependency on the base pkg 
here.

-- rex