On 08/21/2014 06:31 PM, quickbooks office wrote:
On Wed, Aug 20, 2014 at 4:27 PM, Kevin Fenzi <kevin@xxxxxxxxx> wrote:
The recent mass rebuild for glibc/gcc fixes finished monday. However,
it was discovered that there was a rpm bug present for the last ~1300 or
so builds in the mass rebuild. This bug would cause packages that
override provides/requires to just not add their requires at all.
https://bugzilla.redhat.com/show_bug.cgi?id=1131892
I have just finished scraping the logs for those ~1300 f21 builds and
identified the packages affected. I will be rebuilding them in f21 and
rawhide. Happily it isn't too many packages. Packages outside of the
mass rebuild may also be affected, maintainers are advised to
doublecheck their build.log if they override provides/requires and
built anything the last few days.
kevin
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Wouldn't it be better / safer to just to do the mass rebuild all over
again for all the packages?
I mean what if a package slips through the cracks for the final release?
The window of brokenness is quite well known, there's no point in all
the extra churn for a handful of packages.
In fact, AFAICT affected packages will simply have failed to build. At
least that's what happens on my boxes.
- Panu -
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
