| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
The README was getting long and unweildy
|
| | |
|
| |\
| |
| | |
Update Swedish translation
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
flatpak-utils-http: Ensure to wake up the main context on error
|
| |/
|
|
|
|
|
|
|
|
| |
All the other code paths which set `data->done` or `data->error` ensure
to wake up the main context so its loop exit conditions can be checked
again — this code path was missing a wakeup though.
Spotted by code inspection; I haven’t hit this in the wild.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
| |\
| |
| | |
Add test coverage for our seccomp filter
|
| | |
| |
| |
| |
| |
| |
| | |
In particular, this checks that CVE-2017-5226, CVE-2019-10063 and
CVE-2021-41133 are still prevented.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| |/
|
|
|
|
|
|
|
| |
This exercises various syscalls. It's heavily based on the one from
<https://github.com/containers/bubblewrap/pull/459>, but with the
addition of a mode to output the numeric values of various expected
errno codes, which are not otherwise available to shell scripts.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | |
|
| | |
|
| |\
| |
| | |
build-init: Use SDK arch for SDK extensions...
|
| | |
| |
| |
| | |
...instead of the app we're building arch.
|
| |\ \
| | |
| | | |
tests: Generate Makefile-test-matrix.am.inc in $(srcdir)
|
| | |/
| |
| |
| |
| |
| |
| | |
Files that are generated manually by a maintainer and committed to git
should be in the srcdir, not the builddir.
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | |
|
| | |
| |
| |
| | |
This would have been helpful in my work on #4453
|
| | |
| |
| |
| |
| |
| |
| | |
Currently the output produced when assert_remote_in_installation() or
assert_remote_not_in_installation() fails is not helpful: it doesn't
mention the remote name or where the assertion was called from. Fix
those problems by rewriting it as a #define.
|
| | |
| |
| |
| | |
It's easier to reason about the tests if they don't leave state behind.
|
| | |
| |
| |
| |
| | |
This will make the next commit simpler, and in my opinion this makes the
code more readable.
|
| |/
|
|
| |
Per the documentation, g_assert_null() is meant for unit tests.
|
| |\
| |
| | |
tests: Allow FLATPAK_BINARY=flatpak for exports
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
https://github.com/flatpak/flatpak/commit/a99b748931e6444dadb0d0c8c1565da23f755800 introduced an environment variable for changing the flatpak path for exports.
On NixOS, we do not have a stable path we could use so we used to patch Flatpak to use `flatpak` program from `PATH`.
With the recent change, we drop our downstream patch in favour of setting the environment variable to `flatpak` but the tests do not expect that.
This is the test part of our former downstream patch so that tests can pass with exports using `flatpak` instead of an absolute path.
It still expects the binary path to end with `flatpak` so arbitrary `$FLATPAK_BINARY` will not work but we do not pass the environment variable to tests so we cannot do much better.
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Update Polish translation 211017 for the main branch
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
| |
g_key_file_get_boolean() only accepts lower case "true" and "false", so
correct some instances of "False" in key files. This makes no functional
difference as long as the error pointer isn't checked since
g_key_file_get_boolean() also returns false when it can't parse the
value as a boolean. But it still seems good to be correct, and someone
could interpret the existence of "IsRuntime=False" as implying that
"IsRuntime=True" will work, which it doesn't.
|
| | |
|
| |\
| |
| | |
Fix some warn_unused_result warnings
|
| | |
| |
| |
| | |
While building on gcc 9.3.0
|
| |\ \
| | |
| | | |
Switch to GitHub forms
|
| | | |
| | |
| | |
| | |
| | | |
This MR switches to GitHub forms to improve user experience when opening an issue.
It includes a bug template and a feature request template.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
flatpak 1.12.2
Git-EVTag-v0-SHA512: 5e6e119c2d8f39bdbc55735a5819235de430712a049793b1a64a94bcd2a8a7a7ade5dedaf5098c51b25366cf0d3b3029302cc8f8b42821f76b6db493142ac7ea
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | | | |
|
| |\ \ \ \
| |/ / / |
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Even though we are going to check all the `LC_*` environment variables,
if one of them is not set, we still need to consider LANGUAGE, LC_ALL
and LANG; there is no guarantee that *every* `LC_*` environment variable
is set (and in particular, during our build-time tests, they will usually
not be).
Resolves: https://github.com/flatpak/flatpak/issues/4471
Signed-off-by: Simon McVittie <smcv@collabora.com>
(cherry picked from commit ae59fb7aca24cd2579aae51978f64bf762f78569)
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Simon McVittie <smcv@collabora.com>
(cherry picked from commit 53bde36585b88a2b96bf896ed79b40ccb6a72c54)
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was incorrectly looking at errno instead of -r.
Fixes: 0b38b0f0 "run: Handle unknown syscalls as intended"
Signed-off-by: Simon McVittie <smcv@collabora.com>
(cherry picked from commit 3fc8c672676ae016f8e7cc90481b2feecbad9861)
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
