On Wed, 2017-11-15 at 20:15 +0900, Tristan Van Berkom wrote:
Hi all,

GNOME 3.27.2, the second unstable release in the 3.28 development
cycle, is now available.

The porting of more modules to meson continues (which is great!), but
It's still causing some problems for some modules. See the build
failures below, along with a short list of other build errors.
Build Failures
Instead of including a skip list of failing modules, I will just note
here which modules were unable to build and for what reason, it looks
like the majority of failures are due to lack of fresh tarballs:

  o gnome-chess:     Changed to use meson, need new release tarball
with meson
  o gnome-documents: Changed to use meson, need a new release tarball
with meson

It wasn't. Autotools support is still there, but the jhbuild moduleset
was changed to use meson as the default. Reverting this for the release
would have been enough in this case.

  o gnome-boxes:     Changed to use meson, new release tarball exists
but lacks the
  o gnome-terminal:  Depends on vte 0.51.1, only 0.50.2 is available
(need new vte tarball)

  o gnome-system-monitor: Build failure

    looks like source schema xml is missing from EXTRA_DIST:

    No rule to make target 'org.gnome.gnome-system-
monitor.gschema.xml', needed by 'org.gnome.gnome-system-
monitor.gschema.valid'.  Stop.

  o fwupd: Stack trace encountered in po/make-images (this seems to
           a bug in the runtime / sysdeps, I will investigate

  o gnome-software: Now depends on fwupd, which did not build

Do you have a list of bugs for those build failures?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]