From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES qemu 0/2] build: more integrity checks of copied sources
Date: Tue, 22 Sep 2026 15:05:40 +0200 [thread overview]
Message-ID: <20260922130652.374790-1-f.ebner@proxmox.com> (raw)
Commit fe22d79a16 ("build: clean copied QEMU sources") made the first
step towards checking the QEMU sources for integrity. It is not enough
however, because it does not detect a dirty state that comes from a
removed file, and does also not ensure anything about the subprojects
directories, which are part of .gitignore. This series improves the
checking with regard to those aspects. See the individual patches for
details.
pve-qemu:
Fiona Ebner (2):
build: check that copied sources are not dirty
build: track and check subproject state
Makefile | 7 +-
debian/verify-subproject-state.pl | 167 ++++++++++++++++++++++++++++++
2 files changed, 173 insertions(+), 1 deletion(-)
create mode 100755 debian/verify-subproject-state.pl
Summary over all repositories:
2 files changed, 173 insertions(+), 1 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-09-22 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 13:05 Fiona Ebner [this message]
2026-09-22 13:05 ` [PATCH qemu 1/2] build: check that copied sources are not dirty Fiona Ebner
2026-09-22 13:05 ` [PATCH qemu 2/2] build: track and check subproject state Fiona Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260922130652.374790-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox