Skip to content

staging-next-25.11 iteration 3 - 2026-01-25#483601

Merged
vcunat merged 178 commits intorelease-25.11from
staging-next-25.11
Feb 7, 2026
Merged

staging-next-25.11 iteration 3 - 2026-01-25#483601
vcunat merged 178 commits intorelease-25.11from
staging-next-25.11

Conversation

r-burns and others added 30 commits December 18, 2025 06:11
(cherry picked from commit 32119d4)
IDK what unl0kr is. The tests have been broken on aarch64 since the
beginning and it's not part of systemd. The maintainer of unl0kr can be
responsible for maintaining the unl0kr tests

(cherry picked from commit 58f613d)
They're all broken on aarch64-linux and makes it impossible
for me to test systemd bumps by building the passthru tests

Disable them on the platforms in question. We can fix them
later.

(cherry picked from commit 19c82da)
…ses; set updateScript

(cherry picked from commit d9a76d1)
Fixes some regressions
https://lists.x.org/archives/xorg-announce/2025-November/003643.html

Not-cherry-picked-because: package was refactored and renamed on unstable.

PR on unstable: #471756
Picking these from nixpkgs master, as that fixes build/tests failures:
https://hydra.nixos.org/build/320673594/nixlog/3/tail
@vcunat
Copy link
Member Author

vcunat commented Feb 2, 2026

Ah, right, thanks for nudging me the right way. (I could've remembered better, too.) I'll try at least to make these succeed manually, e.g. by deleting those store paths on builders.

@vcunat
Copy link
Member Author

vcunat commented Feb 4, 2026

ambroisie and others added 5 commits February 4, 2026 09:57
The package is currently failing to build due to its pytest
configuration erroring out on deprecation warnings.

Override this behaviour by disabling the `warnings` plug-in entirely.

(cherry picked from commit 744cdd3)
https://gitlab.nic.cz/knot/knot-resolver/-/releases/v6.2.0
The enablement of DoQ costs us only 48 KiB of runtime closure increase,
thanks to sharing the costs with knot-dns libs.

(cherry picked from commit 9a49c1f)
This reverts commit 610f414.

While it is not supported on 3.13 I'm doing everything to keep it alive
because by accident it is the default Django on the default Python version.
@mweinelt
Copy link
Member

mweinelt commented Feb 4, 2026

652c495 was not supposed to be picked. I disabled the failing test because we need to support DJango 4 throughout 25.11, because it is the default Django on the default Python.

@mweinelt
Copy link
Member

mweinelt commented Feb 4, 2026

Broken due to backport of #481900.

@friedow
Copy link
Member

friedow commented Feb 5, 2026

We're running into a deadlock here.

I'll try whether we can patch weasyprint to use a tinycss2 version <1.5.0.

While this is an optional dependency and it doesn't block bleach itself
it does block notebook, which uses a stricter transitive dependency
constraint validation.
@mweinelt
Copy link
Member

mweinelt commented Feb 5, 2026

Unpinng tinycss2 in bleach fixes notebook.

vcunat and others added 4 commits February 6, 2026 12:26
It's a successful build on Hydra but it's got broken binaries,
and thus it's breaking other builds, e.g.:
https://hydra.nixos.org/build/320614180/nixlog/4/tail
there are many and the codebase is a mess. I don't feel like
dealing with this. If someone feels strongly they can re-enable
but I prefer we ship updates again.

wore maintainers needed.

(cherry picked from commit 197277f)
https://hydra.nixos.org/build/320496536#tabs-buildsteps
@vcunat vcunat added this pull request to the merge queue Feb 7, 2026
Merged via the queue into release-25.11 with commit bec415e Feb 7, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1.severity: security Issues which raise a security issue, or PRs that fix one 4.workflow: staging A staging-next or staging-next-XX.YY branch 8.has: package (update) This PR updates a package to a newer version 9.needs: reviewer This PR currently has no reviewers requested and needs attention. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-darwin: 5001+ This PR causes many rebuilds on Darwin and must target the staging branches. 10.rebuild-darwin-stdenv This PR causes stdenv to rebuild on Darwin and must target a staging branch. 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-linux: 5001+ This PR causes many rebuilds on Linux and must target the staging branches. 10.rebuild-linux-stdenv This PR causes stdenv to rebuild on Linux and must target a staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.