On Tue, 01 Aug 2017 at 00:38:58 +0300, Adrian Bunk wrote:
> Some recent change in unstable makes flatpak FTBFS on amd64/arm64:
>
> https://tests.reproducible-builds.org/debian/history/flatpak.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flatpak.html
I can't reproduce this in my local sbuild, but it's still happening on
the reproducible-builds infrastructure. It might be related to the use
of pbuilder on reproducible-builds?
Have you reproduced this yourself, or are you reporting it purely based on
what you see on reproducible-builds.org?
> # random seed: R02Sbf4ab0218f9346d8617da03c0d7234c9
> # flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed (status
> == 0): (256 == 0)
This is status from:
g_spawn_sync (NULL, (char **)argv, NULL, flags, NULL, NULL, NULL, NULL,
&status, &error);
where argv is { "flatpak", "remote-add", ... } and error indicates that
g_spawn_sync() did not immediately fail (therefore status is a waitpid()
result). Applying WIFEXITED() and WEXISTATUS() indicates that
"flatpak remote-add ..." exited 1.
The next step is to make this fail in an environment where g_test_verbose()
would return true (or patch out that check), so that we see flatpak's stderr.
I'm not entirely sure why upstream suppressed its stderr here.
S
_______________________________________________
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
