New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[0.57.2] run_target with a missing quoted command started requiring the binary to exists #8641
Comments
Oh, this has another impact:
(The "true" is a placeholder, required because run_target requires a command to be specified.) This now started printing:
|
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
This is probably caused by #8526. I think it's the right thing to do, but I agree it probably should not be in a point release. That change was needed to fix another bug, and we probably overlooked the fact that the program was not required before. If your target is optional, do something like: rsync = find_program('rsync', required: false)
if rsync.found()
run_target(..., command: [rsync, ...])
endif |
Yep, systemd/systemd#19297 does exactly this. |
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
find_program() supports |
Oh, you mean that we could do rsync = find_program('rsync', required: false)
run_target(..., command: [rsync, ...]) In systemd we still support meson-0.46 sadly… |
Oh well, leave it as a |
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25)
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) (cherry picked from commit f6435a0)
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) (cherry picked from commit f6435a0) (cherry picked from commit f4a1812)
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) Related: #2017033
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) Related: #2030027
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) Related: #2030027
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) Related: #2039326 Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25) Related: #2039326 Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here.
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25)
mesonbuild/meson#8641 Our CI started to fail. Even if the change is reverted in meson, we need a quick workaround here. (cherry picked from commit 7c5fd25)
Describe the bug
A clear and concise description of what the bug is.
We have the following code in systemd:
This target is only used when manually invoked. So far, the presence of
rsync
was not probed, so it was OK ifrsync
was not installed (until the target was executed). This changed in 0.57.2 (0.57.1 was still OK). So for example CI builds started failing. Please consider reverting the change, it doesn't seem to be something suitable for a point release.With meson-0.57.2-1.fc35.noarch, this fails.
The text was updated successfully, but these errors were encountered: