| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| | |
app: Only remount /sysroot if needed
|
|/
|
|
|
|
|
|
| |
We should only try to remount `/sysroot` if we're actually handling the
sysroot repo and the repo isn't writable. We already have public APIs to
check each of those, so let's use them.
Closes: #2485
|
|\
| |
| | |
lib/prune: Avoid unnecessary object serialization
|
|/
|
|
|
|
| |
`repo_prune_internal` was deserializing each object and passing the
components to `maybe_prune_loose_object`, which promptly reserialized
it.
|
|\
| |
| | |
lib: Avoid dereferencing NULL error values
|
|/
|
|
|
|
| |
Otherwise, this will segfault when callers don't need any exact errors.
Signed-off-by: Ryan Gonzalez <ryan.gonzalez@collabora.com>
|
|\
| |
| | |
ci: Require `libcap2-bin` for `capsh`
|
| |
| |
| |
| |
| | |
This was previously pulled in indirectly, but it looks like we need
to require it explicitly in newer Ubuntu.
|
|\ \
| | |
| | | |
Add Fedora Kinoite link
|
| |\ \
| | |/ |
|
| | | |
|
|\ \ \
| |_|/
|/| | |
lib: Fix a bad call to g_file_get_child
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In Glib, since commit 3a6e8bc8876e149c36b6b14c6a25a718edb581ed,
`g_file_get_child` does not accept absolute path as paramater anymore.
The broken assertion was encountered during `ostree admin deploy`
command for the checkout of subpath `etc`.
Example of error log:
```
(ostree admin deploy:1640): GLib-GIO-CRITICAL **: 03:42:00.570: g_file_get_child: assertion '!g_path_is_absolute (name)' failed
(ostree admin deploy:1640): GLib-GIO-CRITICAL **: 03:42:00.570: g_file_query_info: assertion 'G_IS_FILE (file)' failed
**
OSTree:ERROR:src/ostree/ot-main.c:232:ostree_run: assertion failed: (success || error)
Bail out! OSTree:ERROR:src/ostree/ot-main.c:232:ostree_run: assertion failed: (success || error)
```
|
|\ \
| |/
|/| |
prepare-root: Set up sysroot readonly in initramfs
|
|/
|
|
|
|
|
|
| |
Let's ensure things are right from the start in the initramfs;
this closes off various race conditions. Followup to
https://github.com/ostreedev/ostree/pull/2113/commits/35642259175973617da937f3cab6ce5f13c95077
Closes: https://github.com/ostreedev/ostree/issues/2115
|
|\
| |
| | |
prepare-root: check for read-only sysroot status early on
|
|/
|
|
|
|
|
|
| |
This moves read-only sysroot checks upfront, so that they are not
intermixed with mount operations.
It has no immediate side-effects, but allow these check to be
independent from the rest of the mounting logic (and future changes
to it).
|
|\ |
|
| |
| |
| |
| |
| | |
This adds checks around all `snprintf` calls in order to detect
failures and gracefully abort.
|
|\ \
| |/
|/| |
|
|/
|
|
|
| |
This moves a global mutable variable to a smaller local scope,
as it is not really used outside of that.
|
|\
| |
| | |
prepare-root: make all mount operations silent
|
|/
|
|
|
|
|
| |
This adds a `MS_SILENT` flag to all `mount(2)` calls, reducing the
amount of kernel logs produced on each boot.
Those messages do not contain actionable details, and in the "mount
plus read-only remount" case they can easily become highly redundant.
|
|\
| |
| | |
tests/var-mount: tweak test setup
|
|/
|
|
|
|
|
|
| |
This reworks the var-mount destructive test in order to properly use
the datadir for the current stateroot instead of a duplicated one.
In turn, it ensures that the resulting `var.mount` after reboot is
correctly pointing to the same location which hosted `/var` on the
previous boot.
|
|\
| |
| | |
ci: Enable -fanalyzer
|
| |
| |
| |
| | |
To pacify gcc's `-fanalyzer`.
|
|/
|
|
|
|
|
|
|
| |
Followup to https://github.com/ostreedev/ostree/pull/2463
One thing I noticed here is we lost usage of `build-check.sh`
which also invokes `clang`, which doesn't speak `-fanalyzer`
and would be broken by this if we try to enable `build-check.sh`
again. But that can come later.
|
|\
| |
| | |
Attempt to update packit flow to build in COPR
|
| |
| |
| |
| |
| | |
No idea if this will really work, but at least `packit srpm`
does work now.
|
|\ \
| |/
|/| |
|
|/
|
|
|
|
| |
Various fixes there, including one for `gcc -fanalyzer`.
Update submodule: libglnx
|
|\
| |
| | |
Fix various mostly theoretical gcc `-fanalyzer` issues
|
| |
| |
| |
| |
| | |
Add some not-NULL assertions for return values from glib,
and upgrade some `g_return_if_fail` to `g_assert`.
|
| |
| |
| |
| | |
Again this one is just in theory, but let's add an assertion.
|
| |
| |
| |
| |
| |
| | |
Flagged by `gcc -fanalyzer`. I didn't study this really deeply
but I think it's not actually reachable. Anyways, let's catch
it on general principle.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In general, we're probably going to need to change most of our
`g_return_if_fail` to `g_assert`. The analyzer flags that
the function can return `NULL`, but the caller isn't prepared for
this.
In practice, let's abort.
|
|\ \
| |/
|/| |
repo/private: move OstreeRepoAutoTransaction to a boxed type
|
| |
| |
| |
| |
| |
| |
| | |
This defines `OstreeRepoAutoTransaction` as a boxed type, in order
to support auto-generating bindings for it.
That first requires adding internal reference-counting to it, to
allow freely copying/freeing references to a single transaction guard.
|
|\ \
| |/
|/| |
docs: Do not convert -- & --- to en/em-dash
|
|/
|
|
|
| |
'--' is frequently used for command line options and was thus
incorrectly rendered as a special en-dash symbol.
|
|\
| |
| | |
prepare-root: tweak log messages to clarify errors
|
|/
|
|
|
|
|
|
| |
This rewords errors and log messages in the functions which take care
of preparing sysroot in initramfs.
Depending on the boot flow, it is possible to reach this logic
with a sysroot mounted (unexpectedly) as read-only.
In that case, let's clearly point out the problematic mountpoint.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We filter out everything named `-private.h` from scanning,
which differs from the gtk-doc exclude. Eventually this will
be solved when we switch to the new gir-based docs.
Came up in https://github.com/ostreedev/ostree-rs/pull/34#discussion_r723337772
|