projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 3d66db2) | patch
deploy: Warn if we find content in the deployment's /var
authorColin Walters <walters@verbum.org>
Wed, 9 Jun 2021 13:44:09 +0000 (09:44 -0400)
committerColin Walters <walters@verbum.org>
Thu, 10 Jun 2021 11:33:17 +0000 (07:33 -0400)
commitedf7477ee9e2c1d238aae35b1a0414e478870837
treed31e5226e914b1498a6b0bc637a95c7dba62c6bctree | snapshot
parent3d66db2baea6a4124eae5ae4a4bdd7441b3e81edcommit | diff
deploy: Warn if we find content in the deployment's /var

This will be ignored, so let's make it very clear
people are doing something wrong.  Motivated by a bug
in a build pipeline that injected `/var/lib/rpm` into an ostree
commit which ended up crashing rpm-ostree because it was an empty db
which it wasn't expecting.

It *also* turns out rpm-ostree is incorrectly dumping content in the
deployment `/var` today, which is another bug.
src/libostree/ostree-sysroot-deploy.c diff | blob | history
tests/kolainst/destructive/deployment-lint [new file with mode: 0755] blob
Unnamed repository; edit this file 'description' to name the repository.