-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Update to 4.19.0 #185
Update to 4.19.0 #185
Conversation
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024071323-4.3&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2024070519-4.3&flavor=update
Failed tests11 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/105374#dependencies 6 fixed
Unstable tests
|
Use new builderv2 functionality to fetch Xen directly from git, instead of using release tarballs. This allows updating to arbitrary version before release tarballs are generated.
1a62d32
to
bf2a325
Compare
PipelineRetry |
Rebase all the patches, drop patches included upstream already: - all "backports" - all HWP-related (with except to switching the default, which is moved to qubes-specific section) - MSI-X patches - 1013-libxl-do-not-force-qdisk-backend-for-cdrom.patch - appears to be not necessary anymore Renumber the patches to have clean ordering, and also drop patch number from the title so further rebases generate smaller diff. Other changes: - disable pygrub via (now existing) configure option, this removes libxenfsimage too - add --enable-systemd - the default in -rc2 is disabled, likely due to a bug - remove traces of xencons and xentrace_format - both removed upstream - don't fail the build on missing build-id in xen.efi.elf.
Legacy builder doesn't support R4.3, so drop related files too.
Qubes OS used Linux's PAT to prevent graphics corruption, but that corruption was actually due to a Linux core memory management bug that has since been fixed.
bf2a325
to
0dcde71
Compare
QubesOS/qubes-issues#9420