0.60 fails to build GNOME components
See original GitHub issueUsing the new meson 0.60, either from upstream or Debian, GNOME components started to fail to build
Example of the eog snap build https://launchpadlibrarian.net/565502418/buildlog_snap_ubuntu_focal_amd64_eog_BUILDING.txt.gz
Configuring org.gnome.eog.desktop.in using configuration
../src/data/meson.build:25:5: ERROR: Function does not take positional arguments.
Trying to build the current eog deb in Ubuntu with the new meson 0.60 deb from Debian unstable leads to a similar error
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:12 (9 by maintainers)
Top Results From Across the Web
ERROR: Got unknown keyword arguments - Platform - GNOME ...
Hello, when trying to run Meson on Windows 11 64-bit I am getting the error: meson.build:96:0: ERROR: Got unknown keyword arguments “darwin_versions”, ...
Read more >254772 – qtcurve fails to build - Gentoo's Bugzilla - Gentoo Linux
Emerge of x11-themes/qtcurve-0.60.0 fails with "make failed" error. Reproducible: Always Steps to Reproduce: 1. emerge qtcurve Actual Results: Emerge fails.
Read more >206663 – x11/gnome-shell: shell and desktop failed
This doesn't terminate gnome-session, and existing apps in the session can keep running. As your gnome-shell seems to work fine, you can use...
Read more >[SOLVED] Gnome Shell "Something has gone wrong" after ...
The upgrade updated both the Linux kernel & the Nvidia package which ... failed to process components/component/id[text()='archlinux.www.
Read more >201791 – Gaim dbus GNOME-VFS crash - Red Hat Bugzilla
So maybe, 1) the gnome-vfs filesystem backend should fail if threads aren't ... I would not make this conditional on Gaim D-Bus usage,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
There is more than enough time between now and the next feature release of meson, for projects to fix their code.
It’s a simple and backwards-compatible fix, just remove a completely ignored argument and backport it to any stable maintenance branches you have.
It’s not even incorrect to fail here. It was never allowed. Meson has added a lot of improved type checking in recent years, which made many things that used to be silently ignored, turn into errors. We didn’t add deprecation warnings for any of it. Anyone who is passing incorrect arguments should in fact be told what they’re doing isn’t actually doing what they think it is doing, and their meson.build files are buggy.
That’s not a matter of backwards compatibility! That is a matter of bug-level compatibility.
This deprecation warning is being added as a courtesy gesture, because it turns out this one thing is surprisingly common among related projects and we want to give you time to fix things before your projects become unbuildable.
This is NOT permission to keep on using invalid arguments for another few years and another few major versions of meson! Fixing these bugs in the meson.build files should be prioritized IMO.
We should turn it into a deprecation warning for 0.60.1 and keep it removed in master. Does it break many GNOME projects? I guess it’s the kind of mistake that got copy pasted everywhere?