- Jun 10, 2021
-
-
Ludovico de Nittis authored
Since the commit fce30b8d, this variable was not used anymore. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
This commit addresses most of the warnings printed at compilation time while using clang and `ninja scan-build`. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- Jun 09, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
CI: Set more reasonable permissions in the source package See merge request !318
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
CI: Reduce CI load See merge request !319
-
Ludovico de Nittis authored
Improve compatibility with other mtree implementations See merge request !320
-
- Jun 08, 2021
-
-
Simon McVittie authored
The nochange flag is fully implemented here: it suppresses changing the modification time or permissions. The optional flag is mostly implemented here: it suppresses the error that would ordinarily occur if a file with content does not already exist. The ignore flag is not yet implemented, only parsed, because it only really applies when verifying whether a filesystem tree matches a specification. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
time=1.234 has historically meant 1 second + 234 nanoseconds, or what normal people would write as 1.000000234. Parse it as such, but for now treat this ambiguous format as an error, unless the fractional part is exactly ".0" which is unambiguous - we can relax this to a warning later, if we want to. libarchive and FreeBSD mtree show mtimes with exactly 9 decimal digits, which makes them mean the same thing in either interpretation. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
libarchive allows both, although FreeBSD and NetBSD mtree do not. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
When we push to master it's usually for one of three reasons: 1. We merged a merge request 2. We pushed the "release vX.Y.Z" commit, together with a tag 3. We pushed some other trivial change directly When we merged a merge request, immediately running CI is not necessarily very helpful, because we already ran it for the branch that's getting merged. If we pushed a release commit and a tag, we want the CI pipeline for the tag to take priority over the CI pipeline for the release commit. If we pushed a trivial change, it might not even need CI (if it's just a change to a README, or similar), but if it does, we can trigger it manually. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
If we avoid running pipelines for merge requests, then the status of the pipeline for the branch will show up. The pipeline for the branch can be more comprehensive because it has access to project-specific masked and protected variables. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
To get the deploy job to run, the tags need to be configured as protected so they get to see all the necessary variables. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
It's confusing for it to appear in the job graph when we won't be launching it the majority of the time. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
Publish pressure-vessel releases, separate from scout releases See merge request !317
-
Simon McVittie authored
When combined with changes to SteamLinuxRuntime scripts, this will let us do a new pressure-vessel release and incorporate it into soldier/sniper/etc. depots, without having to do a whole release of scout to provide the new pressure-vessel. These releases don't include anything that we didn't already publish in Gitlab artifacts, and they're relatively small, so they might as well be public immediately (unlike the full scout releases, which we avoid publishing before they are final, both because they are rather large and because game developers could get compatibility issues if they build against a non-finalized scout runtime). Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 07, 2021
-
-
Simon McVittie authored
The production build uses dpkg packages, built with -O2 -g and stripped. This is similar to what we currently extract from a scout SDK build; but if we do it here, we can decouple the pressure-vessel release process from the scout release process, making it possible to issue a new pressure-vessel release for use with pre-existing scout/soldier runtimes much quicker than the time needed to do an entire scout release. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Unusually, libblkid1 and libmount1 have different copyright files despite being from the same package. Ship both. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 04, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- Jun 02, 2021
-
-
Simon McVittie authored
wrap: Set the env var to adjust libshared-library-guard configuration path See merge request !309
-
- Jun 01, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
system-info: Improve diagnostics when layering scout onto soldier See merge request !316
-
- May 27, 2021
-
-
Simon McVittie authored
This is helpful if we're stacking the scout runtime onto the soldier runtime: both pinned_libs_* and overrides are relevant there. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 26, 2021
-
-
Simon McVittie authored
If we're running the scout runtime inside a soldier container, then we want to be reporting facts about the scout runtime. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 25, 2021
-
-
Ludovico de Nittis authored
When inside a Flatpak container, we expect that `libshared-library-guard.so` looks for its blocklist configuration in `/app/etc/freedesktop-sdk.ld.so.blockedlist`. This will not work because we bind `/app` in `/run/parent/app`. For this reason, when we detect this situation, we set the environment variable `SHARED_LIBRARY_GUARD_CONFIG` to point `libshared-library-guard` in the correct path. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
- May 20, 2021
-
-
Simon McVittie authored
Use a more compact output for overrides and pinned libraries See merge request !315
-
Ludovico de Nittis authored
When we list the content of a directory, if a symlink points to a location that is under a known environment variable, we replace its target value with the environment variable. This has the advantage to make it clearer where a symlink is pointing to. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Ludovico de Nittis authored
The entries `pinned_libs_*` and `overrides` are gathered using `find -ls`. However this has the downside to include a lot of information that we usually don't care about like the edit date, the permissions etc... In an attempt to reduce the steam-runtime-system-info report size, without reducing the about of potentially useful info, this commit replaces the `find -ls` output with just a recursive list of directories, files and symlinks. Signed-off-by:
Ludovico de Nittis <ludovico.denittis@collabora.com>
-
Simon McVittie authored
Build capsule-capture-libs from a bundled copy of libcapsule See merge request !311
-
- May 18, 2021
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
- May 17, 2021
-
-
Simon McVittie authored
pv-wrap: Share Pipewire socket with container if available See merge request !314
-
Simon McVittie authored
This gives us direct access to Pipewire using its native protocol, similar to the direct access we already have to PulseAudio, X11 and Wayland. In a Flatpak subsandbox, applications will have to go via xdg-desktop-portal instead, as they do for any other Flatpak app. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Ludovico de Nittis authored
Fix listing overrides in system-info with recent pressure-vessel See merge request !313
-
Ludovico de Nittis authored
pressure-vessel: Sync flatpak_envp_cmp() from Flatpak 1.11.1 See merge request !312
-
- May 12, 2021
-
-
Simon McVittie authored
When pressure-vessel operates in --copy-runtime mode, /overrides is a symlink to /usr/lib/pressure-vessel/overrides. "find /overrides -ls" is useless here: it just lists the symlink, rather than traversing the directory hierarchy. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-