On Wed, Nov 30, 2016 at 4:36 PM, Petr Šabata <con...@redhat.com> wrote:
> during the Tuesday's Modularity WG meeting I was talking about the status
> of the Base Runtime prototype build and the package build failures we
> encountered during our latest attempt. The meeting log is here:
> In short: To bootstrap the Modularity infra (yeah, it's still not done)
> we took a (fairly large) set of packages directly from Fedora 25 RC3
> and put them all in one, self-hosting module, currently misleadingly
> labeled as base-runtime. The next step was to rebuild this set using
> only the packages in it, preferrably twice, to prove it works, produces
> the same, reproducible builds (or as close as we can get) and to save us
> from sudden, unexpected breakage later when we need to touch components
> deep in the [build] dependency chain.
> (Since this is a common question: No, the final Base Runtime module,
> or the Generational Core stack it is part of, won't be self-hosting and
> we won't be shipping the entire set we're currently working with under
> that name.)
> We attempted to rebuild 2943 SRPMs and encountered 152 failures.
> The reasons vary and include undiscovered conditional build dependencies,
> undeclared build or runtime dependencies in combination with recent
> buildroot and other package dependency chains changes, packages no
> longer being compatible with their updated dependencies, random hangs
> or non-deterministic, randomly failing test suites, to name a few.
> Some but not all of those affect, and can be reproduced in, the traditional
> Fedora release, too, and fixing these issues is not only crucial for the
> upcoming modular Fedora 26 Server but will benefit the standard Fedora
> release as well.
> We'll be working on resolving these failures during the upcoming few weeks
> -- via FTBFS bug reports or immediate fixes in the most trivial cases.
> We'll use the following tracker bug for this purpose:
> For the curious, the logs are here:
Would be nice to get name of packages + their (co-)maintainer list.
> And the modulemd input for this build is here:
Wondering why rubygem*, jboss*, nodejs* and gstreamer* are there...
> If you maintain some of these FTBFS'd packages, feel free to fix them
> even before we get to you! :) Just, please, let us know if you do.
> Finally, some quick test instructions: Make sure your package builds
> in F25 and Rawhide. If it does, check whether it also builds in mock
> using this configuration file: https://paste.fedoraproject.org/494173/
> If it works there as well, chances are it's fine.
> Thank you in advance,
> devel mailing list -- email@example.com
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
devel mailing list -- firstname.lastname@example.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org