| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In some cases such as backups or mirroring you may want to pull commits
from one repo to another even if there commits that have incorrect
bindings. Fixing the commits in the source repository to have correct
bindings may not be feasible, so provide a pull option to disable
verification.
For Endless we have several repositories that predate collection IDs and
ref bindings. Later these repositories gained collection IDs to support
the features they provide and ref bindings as the ostree tooling was
upgraded. These repositories contain released commits that were valid to
the clients they were targeting at the time. Correcting the bindings is
not really an option as it would mean invalidating the repository
history.
|
|\
| |
| | |
README: Fix typos of Flatpak
|
|/ |
|
|\
| |
| | |
README.md: Add Apertis and GNOME OS
|
|/ |
|
|\
| |
| | |
test-pull-summary-sigs: Set timestamps to serve expected files
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If this is not done, the test can fail when the temporary directory is
a tmpfs: for example this happens during build-time testing with /var/tmp
on tmpfs or TEST_TMPDIR pointing to a tmpfs, or installed-tests with
gnome-desktop-testing-runner allocating the test directory on a tmpfs.
In particular, many of Debian's official autobuilders now do the entire
build and test procedure in a chroot hosted on a tmpfs, to improve build
performance and prevent fsync overhead.
In this situation, it appears that overwriting summary.sig with a copy
of summary.sig.2 is not sufficient for the web server to tell the
libostree client that it needs to be re-downloaded. I'm not completely
sure why, because tmpfs does appear to have sub-second-resolution
timestamps, but forcing a distinct mtime is certainly enough to
resolve it.
Resolves: https://github.com/ostreedev/ostree/issues/2245
Bug-Debian: https://bugs.debian.org/975418
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|\
| |
| | |
templates: add release-checklist
|
| |
| |
| |
| | |
This collects all release steps in a release-checklist template.
|
|\ \
| |/
|/| |
workflow/release: further refinements
|
|/
|
|
|
|
|
| |
This tweaks the release GH workflow further so that it only triggers
when the `configure.ac` file (which owns the version) changes.
Plus it properly checkouts the PR branch to avoid wrongly looking
at a synthetic merge commit.
|
|\
| |
| | |
ostree commit --tree=tar: Import xattrs from tarballs
|
| |
| |
| |
| |
| | |
If you specify an `xattr_callback` the xattrs will still be taken from
there for now.
|
|\ \
| |/
|/| |
Release 2020.8
|
| | |
|
|/ |
|
|\
| |
| | |
workflows/release: pattern-match on PR title
|
|/
|
|
|
| |
This adds an additional condition in order to run sanity check all
PRs starting with `Release` (case-insensitive).
|
|\
| |
| | |
ci: run ci-release-build.sh on GitHub
|
|/
|
|
|
| |
This adds a GitHub action in order to run ci-release-build.sh on
release PRs (detected via the `kind/release` label).
|
|\
| |
| | |
deployment: Add a bunch of docs and fix annotations
|
| |
| |
| |
| |
| | |
We were missing docs for these, also add some nullability annotations.
Motivated by using these from the Rust bindings.
|
|\ \
| | |
| | | |
bin/checkout: Port some to new style
|
| | |
| | |
| | |
| | |
| | | |
I was reading this code for unrelated reasons and noticed it
was still old style; port most (but not all) to new style.
|
|\ \ \
| |_|/
|/| | |
deployment: Ensure query_deployments_for returns nullable values
|
|/ /
| |
| |
| |
| | |
Since that's a common case; hit this while working on rpm-ostree
code using the ostree-rs bindings.
|
|\ \
| | |
| | | |
ci/travis: move to newer base distro
|
|/ /
| |
| |
| |
| | |
This removes the old pinned distro (Ubuntu Trusty 14.04) from Travis,
moving to the newer default distro (Ubuntu Xenial 16.04).
|
|\ \
| |/
|/| |
sysroot: Fix up some GI nullable annotations
|
| |
| |
| |
| |
| | |
Hit `ostree_sysroot_repo()` shouldn't be nullable while using
the ostree Rust bindings.
|
|\ \
| | |
| | | |
Drop use of `volatile`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As detailed in
gitlab.gnome.org/GNOME/glib/-/issues/600#note_877282, volatile
isn't actually needed in these contexts because the atomic operations
already give us strong enough guarantees. In GCC 11, this triggers a
diagnostic due to the volatile qualifier getting dropped anyway.
There is a WIP to do the same in glib:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1719
This obsoletes this downstream patch:
https://src.fedoraproject.org/rpms/ostree/c/b8c5a6fb
|
|\ \ \
| |_|/
|/| | |
pull: Don't save into cache passed in GByte summaries
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
The cache shouldn't be affected by the user passing in some other
summary as it may not be the "official one".
I ran into this in flatpak where the passed summary was correct, but
the re-saving of the cache updated the mtime of the cached file which
led to later http If-Modified-Since calls failing to update.
|
|\ \
| |/
|/| |
lib/deltas: Annotate from checksum as nullable
|
|/
|
|
|
| |
Without this you can't create a scratch delta from GI. While here,
switch the deprecated allow-none annotations to nullable.
|
|\
| |
| | |
ostree_repo_gpg_sign_data: Fix API doc argument name
|
| |
| |
| |
| |
| | |
I got:
src/libostree/ostree-repo.c:5232: Warning: OSTree: ostree_repo_gpg_sign_data: unknown parameter 'out_signature' in documentation comment, should be 'out_signatures'
|
|\ \
| | |
| | | |
Bootloader probing and construction refactoring
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
I've made this use functions to make it easier to add support for more
bootloaders. Seeing as there will be a big diff anyway I've also adjusted
the formatting to make it pep8 compliant.
|
| | |
| | |
| | |
| | |
| | | |
This is more regular, so will make it easier to add more bootloader types
in the future.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
...with the `sysroot.bootloader` configuration option. This can be useful
when converting a system to use `ostree` which doesn't currently have a
bootloader configuration that `ostree` can automatically detect, and is
also useful in combination with the `--sysroot` option when provisioning a
rootfs for systems other than the one you're running `ostree admin deploy`
on.
|
| | |
| | |
| | |
| | |
| | |
| | | |
It's easier to extend and it centralises the config parsing. In other
places we will no longer need to use `g_str_equal` to match these values,
a `switch` statement will be sufficient.
|
| | |
| | |
| | |
| | | |
In preparation for enhancing `_ostree_sysroot_query_bootloader`
|
| |/
| |
| |
| | |
I think this may affect bindings too.
|
|\ \
| |/
|/| |
lib/fetch-curl: Unref timeout source
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The timeout timer should always be one-shot, so let's just always
destroy it in the callback. The main context has its own ref on it, so
it won't be freed behind its back.
This *should* fix a leak that was brought up in
https://bugzilla.redhat.com/show_bug.cgi?id=1891761.
Reported-by: Milan Crha <mcrha@redhat.com>
|
|/
|
|
|
|
| |
They're equivalent, though I prefer the former because it's more
descriptive and it makes it really obvious that it's a `GSource`
callback.
|