Closed qubesos-bot closed 2 weeks ago
Package for vm-bookworm was built (build log).
Package for vm-bookworm was uploaded to current-testing repository.
Package for vm-archlinux failed to build (build log) ((("core-qrexec:vm-archlinux-rolling.x86_64:archlinux: Failed to build PKGs: Failed to copy-out: Command '['/usr/lib/qubes/qrexec-client-vm', 'disp1404', 'qubesbuilder.FileCopyOut+-2Fbuilder-2Fcore--qrexec-2Fqubes--vm--qrexec--4.2.22--1--x86_64.pkg.tar.zst', '/usr/bin/qfile-unpacker', '1000', '/home/user/builder-r4.3/components/core-qrexec/4.2.22-1/vm-archlinux/build/pkgs']' returned non-zero exit status 1..",),)).
Package for host was built (build log).
Package for host was uploaded to current-testing repository.
Package for vm-trixie was built (build log).
Package for vm-trixie was uploaded to current-testing repository.
Package for vm-jammy was built (build log).
Package for vm-jammy was uploaded to current-testing repository.
Package for vm-archlinux failed to build (build log) ((("core-qrexec:vm-archlinux-rolling.x86_64:archlinux: Failed to build PKGs: Failed to run '/usr/bin/qvm-run-vm -- disp9412 env -- VERBOSE=1 DEBUG=1 BACKEND_VMM=xen DIST=archlinux PACKAGE_SET=vm bash -c 'sudo cp /builder/plugins/chroot_archlinux/conf/makepkg-x86_64.conf /usr/local/share/devtools/makepkg.conf.d/qubes-x86_64.conf && sudo mkdir -p /builder/cache/qubes-x86_64 && cd /builder/cache/qubes-x86_64 && sudo tar xf /builder/cache/root.tar.gz && sudo /builder/plugins/chroot_archlinux/scripts/generate-pacman /builder/plugins/chroot_archlinux/conf/pacman.conf.j2 /usr/local/share/devtools/pacman.conf.d/qubes-x86_64.conf && sudo rm -rf /etc/pacman.d/gnupg/private-keys-v1.d && sudo pacman-key --init && sudo pacman-key --populate && sudo /builder/plugins/chroot_archlinux/scripts/generate-pacman /builder/plugins/chroot_archlinux/conf/pacman.conf.j2 /usr/local/share/devtools/pacman.conf.d/qubes-x86_64.conf --enable-builder-local && sudo /builder/plugins/build_archlinux/scripts/update-local-repo.sh /builder/cache/qubes-x86_64/root /builder/repository && cd /builder/core-qrexec && sudo qubes-x86_64-build -r /builder/cache -- -d /builder/repository:/builder/repository -- --syncdeps --noconfirm --skipinteg | cat'' (status=1)..",),)).
Package for vm-fc39 was built (build log).
Package for vm-fc39 was uploaded to current-testing repository.
Package for vm-fc40 was built (build log).
Package for vm-fc40 was uploaded to current-testing repository.
Package for vm-fc41 was built (build log).
Package for vm-fc41 was uploaded to current-testing repository.
Complete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024100804-4.3&flavor=update
Test run included the following:
Compared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024091704-4.3&flavor=update
# Test died: command '(set -o pipefail; sudo qubes-dom0-update -y k...
Compared to: https://openqa.qubes-os.org/tests/112766#dependencies
Package for vm-archlinux was built (build log).
Package for vm-archlinux was uploaded to current-testing repository.
Superseded by #5147
Update of core-qrexec to v4.2.22 for Qubes OS r4.3, see comments below for details and build status.
From commit: https://github.com/QubesOS/qubes-core-qrexec/commit/fedd1cfb6f608694232cd42053f142489ac98d90
Changes since previous version: QubesOS/qubes-core-qrexec@fedd1cf version 4.2.22 QubesOS/qubes-core-qrexec@45527be actually sanitize service name
Referenced issues:
If you're release manager, you can issue GPG-inline signed command:
Upload-component r4.3 core-qrexec fedd1cfb6f608694232cd42053f142489ac98d90 current all
(available 5 days from now)Upload-component r4.3 core-qrexec fedd1cfb6f608694232cd42053f142489ac98d90 security-testing all
You can choose subset of distributions like:
Upload-component r4.3 core-qrexec fedd1cfb6f608694232cd42053f142489ac98d90 current vm-bookworm,vm-fc37
(available 5 days from now)Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).
For more information on how to test this update, please take a look at https://www.qubes-os.org/doc/testing/#updates.