e2fsprogs does not seem to (always) generate multilib-safe packages.
the specfile does:
make -C po update-po
prior to the build, which regens the po files. However, regenerating on
different build machines for different arches leads to different timestamps, and
therefore different md5sums, and multilib conflicts.
There is a patch,
which tries to use sed to remove the date stamps, but it doesn't seem to catch
this case. I think we got lucky before and just happened to get the same
timestamp on all arches; maybe it was brew-built on a slow day. :)
I'll attach the proposed patch, just an extension of the current
requesting 5.1 acks; can't get other 5.1 bugfixes through the errata process w/o
this, I think (packaging issues that cropped up)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.