-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
manager v4.3.7-1 (r4.3) #5236
Comments
Package for vm-bookworm was built (build log). |
Package for vm-bookworm 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 host was built (build log). |
Package for host was uploaded to current-testing repository. |
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. |
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024112604-4.3&flavor=update Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024111705-4.3&flavor=update
Failed tests8 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/119126#dependencies 3 fixed
Unstable tests
|
Package for vm-noble failed to build (build log) ((('manager:vm-ubuntu-24.04.amd64:debian: Failed to build packages: Failed to run '/usr/bin/qvm-run-vm -- disp7704 env -- VERBOSE=1 DEBUG=1 BACKEND_VMM=xen bash -c 'mkdir -p /builder/cache/aptcache && /builder/plugins/build_deb/scripts/create-local-repo /builder/repository ubuntu noble && sudo -E pbuilder create --distribution noble --configfile /builder/pbuilder/pbuilderrc --othermirror "deb [trusted=yes] file:///tmp/qubes-deb noble main" && sudo -E pbuilder build --override-config --distribution noble --configfile /builder/pbuilder/pbuilderrc --othermirror "deb [trusted=yes] file:///tmp/qubes-deb noble main" /builder/build/qubes-manager_4.3.7-1+noble1.dsc && /builder/plugins/build_deb/scripts/patch-changes /builder/build/qubes-manager_4.3.7-1+noble1.dsc /builder/pbuilder/results/qubes-manager_4.3.7-1+noble1_amd64.buildinfo /builder/pbuilder/results/qubes-manager_4.3.7-1+noble1_amd64.changes'' (status=1).',),)). |
Package for vm-noble was built (build log). |
Package for vm-noble was uploaded to current-testing repository. |
Update of manager to v4.3.7-1 for Qubes OS r4.3, see comments below for details and build status.
From commit: QubesOS/qubes-manager@ea26574
Changes since previous version:
QubesOS/qubes-manager@ea26574 version 4.3.7-1
QubesOS/qubes-manager@15f6792 Adjust dependencies for new devices API
QubesOS/qubes-manager@d2e0eeb Merge branch 'qdev'
QubesOS/qubes-manager@a7b52bd Adjust pylint mockups for device_protocol.py
QubesOS/qubes-manager@12ff450 q-dev: Fix detecting already assigned devices on setting apply
QubesOS/qubes-manager@00cec57 q-dev: fix detecting attached devices in settings
QubesOS/qubes-manager@6dd8ca7 q-dev: use simplify DeviceAssignment creation
QubesOS/qubes-manager@2fa90b5 q-dev: direct import of device_protocol classes
QubesOS/qubes-manager@127beb7 q-dev: implements device_id
Referenced issues:
QubesOS/qubes-issues#9325
If you're release manager, you can issue GPG-inline signed command:
Upload-component r4.3 manager ea26574539b3e19d01342151d29855439fabb30f current all
(available 5 days from now)Upload-component r4.3 manager ea26574539b3e19d01342151d29855439fabb30f security-testing all
You can choose subset of distributions like:
Upload-component r4.3 manager ea26574539b3e19d01342151d29855439fabb30f 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.
The text was updated successfully, but these errors were encountered: