The S/390 breakage fix coming to rawhide and f21 soon

Siddhesh Poyarekar siddhesh at redhat.com
Thu Jul 31 19:44:58 UTC 2014


On Thu, Jul 31, 2014 at 09:08:57PM +0200, Dan HorĂ¡k wrote:
> oh, that's actually very bad news, we have no mean to rebuild
> everything just for s390, all rebuilds must be done first in primary.

Ugh, that sucks.

> So the next rebuild can happen for F-22 unless primary decides to do an
> additional mass rebuild after the new glibc lands just for us.

A mass rebuild is probably the best option.  I guess we could wait
till there either is another reason to do an additional mass rebuild.
If that doesn't happen till 2.20 is released, then we request a mass
rebuild in primary when 2.20 is released.

Either way, a mass rebuild seems inevitable, unless Carlos has a
better idea.

I assume a mass rebuild in rawhide is easier to request?

> Isn't there a way how to make the revert compatible with the version
> we have now? 

That would mean dropping that patch (i.e. reverting the revert), which
makes us incompatible with other distros.

> I think we can't ship glibc in Fedora that would maintain different
> ABI than all other distros, or could we?

I'm guessing no, but it's just out of conservatism and I can't think
of a reason to back it.  I don't think we provide any ABI guarantees
for Fedora, but I am not aware of usage in s/390 to know if someone
expects such consistency across distros.  It might be an option to
consider if primary refuses to do a mass rebuild.

The other option would be to stay frozen at this point and never
really become 2.20, which is not a very nice thing, but not the end of
the world either.

Siddhesh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/s390x/attachments/20140801/1572491b/attachment-0001.sig>


More information about the s390x mailing list