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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 30/04/13 12:34, Jens Petersen wrote:
I think you are better off asking for help on the Fedora devel list.
(This packaging list is about RPM Packaging Guidelines.)

Thanks. I'll re-send the mail there.


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
I don't think Rel Eng can fix this directly but it needs to be addressed
in the repo compose tool I believe.
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging

--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging





[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux