v0.41.0 meson has numerous regressions that stop vala based apps compiling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
meson (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Artful version of budgie-desktop has recently been sync'd from Debian Experimental.
It has failed to build. Further investigations has revealed that the current version of meson in Artful proposed is the culprit. Upstream has also other reports of Vala based apps failing to compile
https:/
The version of meson in Universe is ok (v0.40.1)
Looking upstream there are numerous regressions reported for v0.41.0 that are due to be fixed for v0.41.1 - it is unknown when v0.41.1 is going to be released nor if that version will resolve current Vala based build issues.
This bug-report was discussed on IRC #ubuntu-devel today (16June) with JBicha - recommendation to raise a bug-report with tag block-proposed
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: meson 0.41.0-1
ProcVersionSign
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Jun 16 22:33:50 2017
InstallationDate: Installed on 2017-06-10 (6 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170610)
PackageArchitec
SourcePackage: meson
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in meson (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in meson (Ubuntu): | |
status: | Fix Committed → Fix Released |
0.41.1 is planned to be released Sunday (that is tomorrow). If it is possible for you to test if current trunk + this MR fixes the issues it would be helpful: https:/ /github. com/mesonbuild/ meson/pull/ 1951
While we're at it Meson currently can't because it is blocked by a regression on ARM as reported here:
http:// people. canonical. com/~ubuntu- archive/ proposed- migration/ update_ excuses. html#meson
However that is _not_ a regression in Meson. It is a GCC bug that only appears now because we have more tests than the previous release. The bug has been reported to Debian but there has been no activity on it:
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 862514