Skip to content

pve-qemu: use upstream QEMU release tarball#238

Open
booxter wants to merge 2 commits into
SaumonNet:mainfrom
booxter:fix-hash-pve-qemu
Open

pve-qemu: use upstream QEMU release tarball#238
booxter wants to merge 2 commits into
SaumonNet:mainfrom
booxter:fix-hash-pve-qemu

Conversation

@booxter

@booxter booxter commented May 28, 2026

Copy link
Copy Markdown
Contributor

This should fix hash mismatches due to non-reproducible meson download src.

booxter added 2 commits May 27, 2026 20:19
Some packages need to update a metadata source separately from their
main build source. Allow callers to choose the source and version
attribute paths instead of assuming src and version everywhere.

Use argv-style subprocess calls for the touched commands while plumbing
those dynamic attributes. That keeps attribute paths and Debian versions
out of shell command construction.
The previous fixed-output fetch cloned pve-qemu with submodules and then
ran Meson subproject downloads in postFetch. That made the source hash
depend on download behavior outside the pinned Proxmox commit, which can
drift underneath CI.

Use the official QEMU release tarball as the build source instead. It
already includes the release packagecache for Meson subprojects, while
the Proxmox git checkout is kept separately for patches, helper scripts,
and update metadata.

The update script now updates the Proxmox patch source first and then
refreshes the upstream QEMU tarball hash for the same package version.

Note: the patch also cleans up more issues in the package, e.g.
redundant build dependencies or wrong phases used.
@booxter booxter force-pushed the fix-hash-pve-qemu branch from a6b7078 to 38cbf69 Compare May 28, 2026 00:39
@booxter booxter mentioned this pull request May 28, 2026

@KiaraGrouwstra KiaraGrouwstra left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks - fixed it for me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants