On Mon, Mar 24, 2014 at 3:41 PM, Mikolaj Izdebski <mizdebsk(a)redhat.com> wrote:
On 03/22/2014 06:15 AM, Miloslav Trmač wrote:
> Given the known large number of failures (OptionalJavadocs says "80% build
> failure rate" without saying that all are JavaDoc-related), we really
> should do a mass rebuild to identify which packages fail to build *and* to
> file bugs soonish, instead of waiting for a Fedora-wide mass rebuild and
> then scrambling to fix dozens/hundreds of build failures in to avoid
> slipping the schedule. We don't necessarily need an official one, perhaps
> only in a never-to-be-merged side tag (or even scratch builds?)
Agreed.
To do a rebuild in Koji Java 8 must land in there first. That can could
be a separate tag, but rel-eng is quite reluctant to provide them.
java 8 is already in the main repos and had been there since F-19.
It's just not providing things like java-devel and hence isn't used by
default in the build process.
Copr could be a better place to do the rebuild. One big advantage
is
that it doesn't use any ARM builders, but on the other hand it has quite
limited capacity (AFAIK 10 builders only).
That's not an advantage, building ARM packages is a requirement of
something in primary architecture. Also you can't tag copr builds in
Fedora. You need to use a koji f21 side tag.
Besides that, there is already one approved change [1] which
requires
rebuilding most of Java packages. We didn't do a mass rebuild for it
yet because we wanted to sync with Java 8 rebuild.
Well there will also be a mass rebuild in general for gcc 4.9 so you
should coordinate with rel-eng to minimise builds in general.
Peter