Skip to content

staging-next 2025-12-17#471587

Merged
vcunat merged 1342 commits intomasterfrom
staging-next
Dec 30, 2025
Merged

staging-next 2025-12-17#471587
vcunat merged 1342 commits intomasterfrom
staging-next

Conversation

@vcunat
Copy link
Member

@vcunat vcunat commented Dec 17, 2025

This is the first staging-next iteration after branching off stable, and we got quite big changes inside, e.g. gcc15 as default on linux.

Helpful links
Important breakages

nothing so far :-)

@vcunat vcunat added the 1.severity: security Issues which raise a security issue, or PRs that fix one label Dec 17, 2025
@vcunat
Copy link
Member Author

vcunat commented Dec 17, 2025

Requested mention: @Eveeifyeve

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-linux: 501+ This PR causes many rebuilds on Linux and should normally target the staging branches. 10.rebuild-darwin: 501+ This PR causes many rebuilds on Darwin and should normally target the staging branches. 10.rebuild-linux-stdenv This PR causes stdenv to rebuild on Linux and must target a staging branch. 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 2.status: merge conflict This PR has merge conflicts with the target branch labels Dec 17, 2025
@uninsane uninsane mentioned this pull request Dec 18, 2025
Merged
13 tasks
@nixpkgs-ci nixpkgs-ci bot removed the 2.status: merge conflict This PR has merge conflicts with the target branch label Dec 18, 2025
K900 and others added 17 commits December 19, 2025 10:34
@K900
pre-commit: skip another test that hits the network
a49e735
@K900
arrow-cpp: fix arrow-azurefs-test (#472089)
c3f33f4
@nixpkgs-ci
Merge master into staging-next
44c11e4
@philiptaron @K900
tailscale: 1.90.9 -> 1.92.3
69de3b7 
tailscale (1.92.3)

  * Fix panic in client during automatic WireGuard configuration.

tailscale (1.92.1)

  * Feature: Support PROXY protocol in Tailscale Funnel and Serve to forward client source IP and port.
  * Feature: Add support for static Peer Relay endpoints via 'tailscale set --relay-server-static-endpoints'.
  * Feature: Add support for Workload Identity Federation authentication in 'tailscale up' via '--client-id' and '--id-token' flags.
  * Feature: Allow configuring remote targets as destinations for Tailscale Services.
  * Improvement: Enhance Peer Relay connection reliability by sending multiple forward bind packets per handshake.
  * Improvement: Include more candidate IP:port pairs in Peer Relay endpoint advertisements.
  * Improvement: Automatically record node peer information in network flow logs.
  * Improvement: Stabilize JSON output format for 'tailscale lock log'.

(cherry picked from commit 7e7d0c9)
@ghpzin
seahorse: fix build with gpgme 2.0+
4be7ea5 
- add patch from merged upstream MR:
https://gitlab.gnome.org/GNOME/seahorse/-/merge_requests/248
https://gitlab.gnome.org/GNOME/seahorse/-/commit/aa68522cc696fa491ccfdff735b77bcf113168d0

Upstream issue:
https://gitlab.gnome.org/GNOME/seahorse/-/issues/410

Fixes build failure:
```
../pgp/seahorse-gpgme.c: In function 'on_gpgme_event':
../pgp/seahorse-gpgme.c:487:14: error: 'GPGME_EVENT_NEXT_TRUSTITEM'
undeclared (first use in this function);
did you mean 'GPGME_EVENT_NEXT_KEY'?
  487 |         case GPGME_EVENT_NEXT_TRUSTITEM:
      |              ^~~~~~~~~~~~~~~~~~~~~~~~~~
      |              GPGME_EVENT_NEXT_KEY
...
ninja: build stopped: subcommand failed.
```
@jtojnar
seahorse: fix build with gpgme 2.0+ (#472315)
a572397
@nixpkgs-ci
Merge master into staging-next
acd4201
@dotlambda
gpgmepp: propagate gpgme and libgpg-error
73ff618 
It specifies

    find_dependency(LibGpgError "1.47")
    find_dependency(Gpgme "2.0.0")

in lib/cmake/Gpgmepp/GpgmeppConfig.cmake.
@dotlambda
qt6Packages.qgpgme: propagate gpgmepp
50c498c
@dotlambda
readstat: fix stringop-truncation error
d30669d
@dotlambda
mpir: fix build with GCC 15
c0ccd9e
@dotlambda
zug: fix build with GCC 15
44b203e
@dotlambda
imagemagick: 7.1.2-10 -> 7.1.2-11 (#472170)
13eaf3f
@nixpkgs-ci
Merge master into staging-next
dc709e1
@dotlambda
gpgmepp: propagate gpgme and libgpg-error (#472418)
fd720f4
@dotlambda
airspy: fix build with GCC 15
12b64d9
@nixpkgs-ci
Merge master into staging-next
ff78aa9
@vcunat
Copy link
Member Author

vcunat commented Dec 30, 2025

@sternenseemann sternenseemann mentioned this pull request Dec 30, 2025
Closed
3 tasks
This was linked to issues Dec 30, 2025
Update Request: git-annex 10.20250929 → 10.20251114 #468308
Closed
stack: Built against deprecated rio-0.1.23.0 (which has a serious bug), and fails #467614
Closed
@Aleksanaa
Copy link
Member

Aleksanaa commented Dec 30, 2025

How's the plan for this round? Do we continue to fix more packages or are there major blockers?

@vcunat vcunat added this pull request to the merge queue Dec 30, 2025
@vcunat
Copy link
Member Author

vcunat commented Dec 30, 2025

We were just today discussing it in the chat:
https://matrix.to/#/#staging:nixos.org

Merged via the queue into master with commit cad22e7 Dec 30, 2025
45 checks passed
@Aleksanaa Aleksanaa mentioned this pull request Dec 31, 2025
Open
@jfroche jfroche mentioned this pull request Dec 31, 2025
Merged
13 tasks
@kfiz kfiz mentioned this pull request Jan 1, 2026
Closed
11 tasks
0x4A6F pushed a commit to 0x4A6F/nixpkgs that referenced this pull request Jan 3, 2026
@jfroche @0x4A6F
privoxy: 3.0.34 -> 4.0.0
adbee55 
Privoxy 3.0.34 fails with the GCC update
(NixOS#471587).

Privoxy 4.0.0 seems to build and work fine.

See NixOS#475479
github-merge-queue bot pushed a commit that referenced this pull request Jan 3, 2026
@jfroche
privoxy: 3.0.34 -> 4.0.0
c3967d7 
Privoxy 3.0.34 fails with the GCC update
(#471587).

Privoxy 4.0.0 seems to build and work fine.

See #475479
jim-ww pushed a commit to jim-ww/nixpkgs that referenced this pull request Jan 3, 2026
@jfroche @jim-ww
privoxy: 3.0.34 -> 4.0.0
a25267f 
Privoxy 3.0.34 fails with the GCC update
(NixOS#471587).

Privoxy 4.0.0 seems to build and work fine.

See NixOS#475479
@Rhys-T Rhys-T mentioned this pull request Jan 3, 2026
Closed
3 tasks
0x4A6F pushed a commit to 0x4A6F/nixpkgs that referenced this pull request Jan 4, 2026
@jfroche @0x4A6F
privoxy: 3.0.34 -> 4.0.0
d895bdc 
Privoxy 3.0.34 fails with the GCC update
(NixOS#471587).

Privoxy 4.0.0 seems to build and work fine.

See NixOS#475479
@ghpzin ghpzin mentioned this pull request Jan 10, 2026
Closed
3 tasks
@vcunat vcunat mentioned this pull request Jan 12, 2026
Merged
1 task
@nixos-discourse
Copy link

nixos-discourse commented Jan 15, 2026

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/is-there-a-reason-why-typsy-0-14-2-is-not-yet-merged-into-stable-after-a-month/74346/2

@behrangsa
Copy link

behrangsa commented Jan 15, 2026

@vcunat any plans to merge this to the stable channel?

@vcunat
Copy link
Member Author

vcunat commented Jan 16, 2026 •
edited
Loading

This pull request certainly won't merge to stable. You can backport individual changes if they qualify. And assuming they're mass rebuilds, you'd target the staging-25.11 branch, and they would then travel through a staging-next-25.11 iteration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

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 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

Milestone

No milestone