summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* pull: Fix some whitespace and a commentpull-fix-whitespacePhaedrus Leeds2021-03-091-16/+17
|
* Merge pull request #2292 from pwithnall/summary-leakOpenShift Merge Robot2021-03-091-1/+1
|\ | | | | ostree-repo-pull: Fix a leak of the summary data if loading from cache
| * ostree-repo-pull: Fix a leak of the summary data if loading from cachePhilip Withnall2021-03-091-1/+1
|/ | | | | | | | | | | | | | If the `summary_sig_not_modified` branch is taken above, both `signatures` and `summary` are loaded from the cache. This makes the `_ostree_repo_load_cache_summary_if_same_sig()` call below redundant (it checks `signatures` matches the file it was just loaded from, and then loads `summary` again) — but that call also currently overwrites `summary` without clearing the old value. Fix this by only making that call if `signatures` was retrieved, but the server said the local `summary` cache was invalid. Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
* Merge pull request #2290 from ostreedev/fix-repo-modes-docsOpenShift Merge Robot2021-03-081-1/+1
|\ | | | | man: Add missing repo mode in config docs
| * man: Add missing repo mode in config docsfix-repo-modes-docsPhaedrus Leeds2021-03-081-1/+1
|/
* Merge pull request #2288 from leograba/masterOpenShift Merge Robot2021-03-042-0/+31
|\ | | | | docs: Add Torizon to related projects and OS
| * docs: Add Torizon to related projects and OSLeonardo Graboski Veiga2021-03-042-0/+31
|/ | | | | | | | | | | The Torizon platform, includin the TorizonCore OS, the TorizonCore Builder Tool and the Torizon OTA, use OSTree as a base for update the host OS, while the user focus on application development using Docker. Add TorizonCore to the list of Operating systems and distributions using OSTree. Add Torizon and its components to the list of related projects.
* Merge pull request #2287 from jlebon/pr/deployment-parsing-commentsOpenShift Merge Robot2021-03-031-1/+11
|\ | | | | lib/sysroot: Add comments and debug statements around sysroot parsing
| * lib/sysroot: Add comments and debug statements around sysroot parsingJonathan Lebon2021-03-021-1/+11
| | | | | | | | | | Was looking at this code more closely today to investigate issues related to bootlink mismatches (#2283).
* | Merge pull request #2285 from cgwalters/log-bootloader-stuffOpenShift Merge Robot2021-02-282-6/+14
|\ \ | | | | | | deploy: Add subbootversion to journal
| * | deploy: Add subbootversion to journalColin Walters2021-02-282-6/+14
| | | | | | | | | | | | | | | | | | To help debug an issue we've seen where `/boot` isn't in sync with the `/ostree/boot` dir, let's log to the journal what we're doing.
* | | Merge pull request #2284 from cgwalters/use-rpmostree-clientOpenShift Merge Robot2021-02-264-57/+6
|\ \ \ | |/ / |/| | tests/inst: Switch to rpmostree-client from git
| * | tests/inst: Switch to rpmostree-client from gitColin Walters2021-02-234-57/+6
| | | | | | | | | | | | | | | See discussion in https://github.com/coreos/rpm-ostree/pull/2569#issuecomment-780569188 Currently pinned to a hash, but after the next stable release let's switch to tags
* | | Merge pull request #2282 from cgwalters/resolve-nullableOpenShift Merge Robot2021-02-181-2/+2
|\ \ \ | | | | | | | | refs: Make ostree_repo_resolve_rev{,_ext}() use (nullable)
| * | | refs: Make ostree_repo_resolve_rev{,_ext}() use (nullable)Colin Walters2021-02-191-2/+2
|/ / / | | | | | | | | | | | | | | | We have an `allow_noent` boolean that controls this, but were missing the `(nullable)` annotation, so the Rust bindings panic when the ref doesn't exist instead of being `Option<GString>`.
* | | Merge pull request #2280 from cgwalters/readme-fix-contributingOpenShift Merge Robot2021-02-171-1/+7
|\ \ \ | |/ / | | | README.md: Fix contributing link, add contact section
| * | README.md: Fix contributing link, add contact sectionColin Walters2021-02-161-1/+7
| | | | | | | | | | | | Came up on #fedora-iot channel.
* | | Merge pull request #2279 from cgwalters/doc-scratch-deltaOpenShift Merge Robot2021-02-121-0/+21
|\ \ \ | |/ / | | | docs: Describe using scratch/empty deltas for initial fetches
| * | docs: Describe using scratch/empty deltas for initial fetchesColin Walters2021-02-111-0/+21
| | | | | | | | | | | | Came up with a user hitting ratelimiting from S3.
* | | Merge pull request #2277 from cgwalters/ci-asanOpenShift Merge Robot2021-02-053-12/+15
|\ \ \ | |/ / |/| | Add --enable-sanitizers, fix `make check` with it
| * | Add --enable-sanitizers, fix `make check` with itColin Walters2021-02-033-12/+15
|/ / | | | | | | | | | | | | | | It's cleaner if this is an build option rather than being kludged into the CI layer. Notably we can't use `LD_PRELOAD` anymore with ASAN, so update our tests to check for `ASAN_OPTIONS`.
* | Merge pull request #2274 from cgwalters/delta-leakOpenShift Merge Robot2021-02-031-1/+1
|\ \ | | | | | | deltas: Fix leak of matches
| * | deltas: Fix leak of matchesColin Walters2021-02-021-1/+1
| | | | | | | | | | | | Found by ASAN.
* | | Merge pull request #2275 from cgwalters/ci-reworkOpenShift Merge Robot2021-02-032-1/+13
|\ \ \ | | | | | | | | CI: run as non-root and add sanitizer build+check
| * | | ci: Add new build-check-sanitized.shColin Walters2021-02-021-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | All C/C++ projects should use the sanitizers (and static analysis) in their CI. We had this but lost it in one of our CI shuffles; let's readd it.
| * | | ci: Don't install deps if running as non-rootColin Walters2021-02-021-1/+1
| |/ / | | | | | | | | | This way we run in Prow too.
* | | Merge pull request #2276 from lucab/ups/tests-enhance-destructiveOpenShift Merge Robot2021-02-032-8/+29
|\ \ \ | | | | | | | | tests/ext/destructive: enhance test logic
| * | | tests/ext/destructive: enhance test logicLuca BRUNO2021-02-032-8/+29
|/ / / | | | | | | | | | | | | | | | This enhances external-tests logic, ensuring that destructive tests have retries and some context to pinpoint failures, and that failed-state services are reset between iterations.
* | | Merge pull request #2273 from cgwalters/link-stb-apt2ostreeOpenShift Merge Robot2021-02-021-0/+3
|\ \ \ | |/ / |/| | README.md: Also link apt2ostree
| * | README.md: Also link apt2ostreeColin Walters2021-01-311-0/+3
|/ / | | | | | | Since the topic of Debian+ostree-for-host comes up fairly often.
* | Merge pull request #2267 from dbnicholson/pull-depth-fixesOpenShift Merge Robot2021-01-124-40/+142
|\ \ | | | | | | Pull depth fixes
| * | pull: Fix local pull with depth and truncated source historyDan Nicholson2021-01-122-5/+75
| | | | | | | | | | | | | | | | | | | | | | | | | | | The local pull path was erroring on any missing commit, but that prevents a depth pull where the source repo has truncated history. As in the remote case, this also tries to pull in a tombstone commit if the source repo supports it. Fixes: #2266
| * | pull: Error on depth pull with missing head commitDan Nicholson2021-01-123-35/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When pulling with depth, missing parent commits are ignored. However, the check was applying to any commit, which means that it would succeed even if the requested commit was missing. This might happen on a corrupted remote repo or when using ref data from a stale summary. To achieve this, the semantics of the `commit_to_depth` hash table is changed slightly to only ever includes parent commits. This makes it easy to detect when a parent commit is being referenced (although there is a minor bug there when multiple refs are being pulled) while keeping references to commits that need their `commitpartial` files cleaned up. It also means that the table is only populated on depth pulls, which saves some memory and processing in the common depth=0 case. Fixes: #2265
| * | tests: Ensure no dangling commit partials on remote depth pullDan Nicholson2021-01-111-0/+10
| | | | | | | | | | | | | | | This was already being done on the local depth pull test, so this just adds the matching logic to the remote depth pull test.
* | | Merge pull request #2263 from cgwalters/createat-nullableOpenShift Merge Robot2021-01-121-1/+1
|\ \ \ | | | | | | | | repo: Make ostree_repo_create_at take nullable options
| * | | repo: Make ostree_repo_create_at take nullable optionsColin Walters2021-01-121-1/+1
| |/ / | | | | | | | | | Hit this when trying to use the Rust bindings.
* | | Merge pull request #2257 from cgwalters/fsverityOpenShift Merge Robot2021-01-115-136/+178
|\ \ \ | |/ / |/| | repo: Move fsverity bits to ostree-repo-verity.c
| * | repo: Move fsverity bits to ostree-repo-verity.cColin Walters2021-01-115-136/+178
|/ / | | | | | | This file will get larger when we start doing more with fsverity.
* | Merge pull request #2261 from cgwalters/boot-ro-moreOpenShift Merge Robot2021-01-115-132/+81
|\ \ | |/ |/| sysroot: Handle ro /boot but rw /sysroot
| * sysroot: Handle ro /boot but rw /sysrootColin Walters2021-01-103-96/+44
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The recent change in https://github.com/coreos/fedora-coreos-config/pull/659 broke some of our tests that do `mount -o remount,rw /sysroot` but leave `/boot` read-only. We had code for having `/boot` read-only before `/sysroot` but in practice we had a file descriptor for `/sysroot` that we opened before the remount that would happen later on. Clean things up here so that in the library, we also remount `/boot` at the same time we remount `/sysroot` if either are readonly. Delete the legacy code for remounting `/boot` rw if we're not in a mount namespace. I am fairly confident most users are either using the `ostree` CLI, or they're using the mount namespace.
| * sysroot: Also maintain canonical boot_fdColin Walters2021-01-103-17/+34
| | | | | | | | | | | | | | Just like we hold a fd for `/sysroot`, also do so for `/boot` instead of opening and closing it in a few places. This is a preparatory cleanup for further work.
| * main: Unconditionally set up mount namespaceColin Walters2021-01-101-19/+3
|/ | | | | | | | I was being very conservative initially here, but I think it's really safe to just unconditionally set up the mount namespace. This avoids having to check twice for a read-only `/sysroot` (once in the binary and once in the library).
* Merge pull request #2254 from dbnicholson/coding-styleOpenShift Merge Robot2020-12-181-11/+13
|\ | | | | pull: Use GNU coding style
| * pull: Use GNU coding styleDan Nicholson2020-12-181-11/+13
|/
* Merge pull request #2253 from dbnicholson/pull-no-verify-bindingsOpenShift Merge Robot2020-12-188-11/+51
|\ | | | | pull: Allow disabling commit binding verification
| * pull: Allow disabling commit binding verificationDan Nicholson2020-12-178-11/+51
|/ | | | | | | | | | | | | | | | 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.
* Merge pull request #2249 from mwleeds/fix-readme-flatpak-typoOpenShift Merge Robot2020-12-021-7/+7
|\ | | | | README: Fix typos of Flatpak
| * README: Fix typos of FlatpakPhaedrus Leeds2020-12-011-7/+7
|/
* Merge pull request #2248 from jjardon/jjardon/more_distrosOpenShift Merge Robot2020-12-021-0/+7
|\ | | | | README.md: Add Apertis and GNOME OS
| * README.md: Add Apertis and GNOME OSJavier Jardón2020-12-011-0/+7
|/
View Lorry Controller Status