Skip to content

staging-next-25.11 iteration 4 - 2026-02-24#493587

Open
vcunat wants to merge 141 commits intorelease-25.11from
staging-next-25.11
Open

staging-next-25.11 iteration 4 - 2026-02-24#493587
vcunat wants to merge 141 commits intorelease-25.11from
staging-next-25.11

Conversation

sternenseemann and others added 30 commits November 30, 2025 21:04
Changes: https://github.com/kristapsdz/lowdown/releases/tag/VERSION_2_0_3

- 2.0.3 notably adds support for building a proper Darwin dylib, but
  messes up the naming scheme of versioned dylibs, so we still have to
  rename them in postInstall.
  See kristapsdz/lowdown#168.
- make regress no longer ignores failures (?!), so we can no longer run
  the test suite on darwin if sandboxing is enabled.
  See kristapsdz/lowdown@4bfd934330ffdb92126.

Co-authored-by: sternenseemann <sternenseemann@systemli.org>
(cherry picked from commit 44da5f3)
This version finally installs correctly named .dylibs on darwin!

(cherry picked from commit 5d1fa9f)
- Updates gnupg 2.4.8 to 2.4.9

- Update freepg patches to source-2.4.9-freepg

- Use `substituteInPlace` with `--replace-fail` to make keyserver change
  more robust.

- Update `static.patch` to generated `configure` (Thanks alyssais)

(cherry picked from commit 88088f7)
(cherry picked from commit 9d0740c)
Tested that 6.18 and 6.19 now build without this.

(cherry picked from commit 5d4365c)
(cherry picked from commit 466bc97)
@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-darwin-stdenv This PR causes stdenv to rebuild on Darwin and must target a staging branch. 10.rebuild-darwin: 5001+ This PR causes many rebuilds on Darwin and must target the staging branches. 10.rebuild-linux: 5001+ This PR causes many rebuilds on Linux and must target the staging branches. 9.needs: reviewer This PR currently has no reviewers requested and needs attention. 4.workflow: staging A staging-next or staging-next-XX.YY branch labels Feb 24, 2026
mdaniels5757 and others added 17 commits February 24, 2026 13:21
CPython fixed python/cpython#141732 in
python/cpython#141736, but exceptiongroup 1.3.1,
including its test suite, still matches the old repr behavior.
The CPython fix has only been backported to 3.13 so far, where it was
first included in version 3.13.12, so we only need to patch for 3.13
and 3.15+.

Upstream issue: agronholm/exceptiongroup#154

(cherry picked from commit 294b175)
#492079 introduced a patch for CVE-2026-25068, which was backported to
staging-25.11 in #492453. However, the patch fails to compile when
ported directly to 25.11 since the way of doing error handling changed
from an `SNDERR` macro to an `snd_error` function between v1.2.14 (which
is on 25.11) and on v1.2.15. In order to fix this, we vendor the patch
and change the offending line like so:

```diff
- +			snd_error(TOPOLOGY, "mixer: unexpected channel count %d", map->num_channels);
+ +			SNDERR("mixer: unexpected channel count %d", map->num_channels);
```

Not-cherry-picked-because: fix that does not apply to unstable since it is on a later version of package
This is only supported when running with `python -m test` through
libregrtest.

(cherry picked from commit ed44282)
https://hydra.nixos.org/build/322755322/nixlog/3/tail
This package currently fails to build during the patch application step
as it includes patches that were incorporated into libsoup 3.6.6. These
patches were introduced in #468891 and #489681. Since they are now part
of a regular release, we thus drop these patches.

The List of commits where these changes are present can be seen at
https://gitlab.gnome.org/GNOME/libsoup/-/compare/3.6.5...3.6.6.

(cherry picked from commit fa66658)
https://hydra.nixos.org/build/322622408/nixlog/1/tail
Without the change the `gtwebengine` fails to buil as:

    /nix/store/...-minizip-1.3.2/include/minizip/ioapi.h:74:10: fatal error: ints.h: No such file or directory
       74 | #include "ints.h"
          |          ^~~~~~~~

(cherry picked from commit 373ddfd)
We're affected also here:
https://hydra.nixos.org/build/322951570/nixlog/1
@sylr
Copy link

sylr commented Mar 2, 2026

Any chance this could wait for go1.25.8 to be released on March 5th ?

@vcunat
Copy link
Member Author

vcunat commented Mar 2, 2026

I don't think it can really "wait". But once the go release is out, we'll see how the rebuild/benefits ratio looks at that point.

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.