Created attachment 261418 [details] v0 currently 1.8.2
requesting exp-run
New failure log: https://pkg-status.freebsd.org/gohan05/data/134i386-default-foo/2025-06-27_16h37m16s/logs/errors/yaru-gtk-themes-22.10.3.log
(In reply to Antoine Brodin from comment #2) This may be a (old) ninja issue rather than meson. In any case ninja has finally been updated and there is also a newer meson major version, for which its test suite takes a while to run.
Created attachment 268491 [details] [PATCH] devel/meson: Update 1.10.1 Update 1.10.1 poudriere-testport devel/meson: 15_0-amd64-release: Pass main-amd64-default: Pass
(In reply to Alastair Hogge from comment #4) Thanks, have you done some light test with ports that uses ninja yourself? If so, do you have a list?
fwiw I've already been using 1.10 privately for a bit but kind of forgot to share. It will need another exp-run, and I need to re-run the test suite.
Stop doing this and get things moving instead, there's no point in not moving to 1.10.1 unless you can prove the opposite.
No release notes for point releases https://github.com/mesonbuild/meson/compare/1.10.0...1.10.1
(In reply to Daniel Engberg from comment #7) Omitting the minor version is to not have to keep changing the title of this bug, because yes, point releases are truly minor. Also fwiw my runs have been with .1.
We keep subjects accurate to what the content is about, if you have issues with that you need to raise that with all committers and get that approved.
Please stop making hard rules up. The title without the point release is still accurate, because the crux of this bug is about updating the major release. meson point releases do not negatively change the results for consumers.
Created attachment 268519 [details] v1 test suite is still running, comments are from running it on 1.9. Some further changes to this area may be forthcoming. This is otherwise good enough for an exp-run.
Please refer to what section in Porters Handbook that says that you shouldn't use the correct version. https://docs.freebsd.org/en/books/porters-handbook/book/#port-upgrading In addition to that, rust should refer to ${RUST_DEFAULT} to follow the framework via MK/bsd.default-versions.mk
Created attachment 268545 [details] v2 two broken tests carry over from 1.9, test_templates Objective-C{,++} subtests may or may not be broken depending on support detection logic. Portions relevant to exp-run are unchanged, if one has been started already.
(In reply to Daniel Engberg from comment #13) 1.10 is still a correct version in this case, nothing there contradicts anything already said. Again, the crux of this bug is to update the major version. The commit message, arguably the more important metadata than the vehicle(s) towards commit, will still contain the full version.