!UNVBThoJtlIiVwiDjU:nixos.org

Staging

319 Members
Staging merges | Find currently open staging-next PRs: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+sort%3Aupdated-desc+head%3Astaging-next+head%3Astaging-next-21.05+is%3Aopen109 Servers

Load older messages


SenderMessageTime
22 Oct 2025
@elvishjerricco:matrix.orgElvishJerricconice, thanks: https://github.com/NixOS/nixpkgs/pull/45445906:49:41
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)
In reply to @elvishjerricco:matrix.org
I can't really think of a good way to workaround this. Just loading all modules in kmod static-nodes is really excessive, since we only need to fix the nodes that would get uaccess. And patching systemd.package seems...... not great
Tbh overriding systemd.package doesn't sound that bad to me...
07:06:15
@dramforever:matrix.orgdramforever maybe a script to run after udev rules to boop everything in /run/udev/static_node-tags/uaccess/? 07:07:08
@vcunat:matrix.orgVladimír Čunát

Next staging-next-25.05? (probably tomorrow, after Hydra cleans trunk-combined and we add also trunk)

I've been looking through the situation again. 25.11 schedule now allows general breaking changes until 25th. I'd really like to have all of these in the next iteration, preferably also with the GNOME upgrade (which has an exception and could break after 25th, too). The first merge inside release-25.05..staging-25.05 is 5-6 weeks old now (5659907ac8f3). So I thought that this moment might fit staging-next-25.05 well.

11:31:21
@adda0:matrix.orgAdda joined the room.17:53:50
23 Oct 2025
@vcunat:matrix.orgVladimír Čunát New staging-next-25.05:
https://github.com/NixOS/nixpkgs/pull/454871
12:12:25
@philiptaron:matrix.orgPhilip Taron (UTC-8) ugh, I didn't have time to package systemd 257.10 for this 16:03:19
@philiptaron:matrix.orgPhilip Taron (UTC-8)* ugh, I didn't have time to package systemd 257.10 for this; guess it's water under the bridge unless we'll do one more 25.05 staging before EOL16:03:51
@vcunat:matrix.orgVladimír Čunáthttps://github.com/NixOS/nixpkgs/pull/45371516:03:56
@philiptaron:matrix.orgPhilip Taron (UTC-8)hell yeah16:04:06
@vcunat:matrix.orgVladimír ČunátIt's in.16:04:07
@elvishjerricco:matrix.orgElvishJerricco Philip Taron (UTC-8): thanks for the comment in the systemd room last week letting me know that was needed :P 16:06:56
@cameronraysmith:matrix.orgcameronraysmith joined the room.18:52:19
@k900:0upti.meK900Can someone that knows ocaml fix the merge conflict on next -> staging20:13:49
24 Oct 2025
@wolfgangwalther:matrix.orgWolfgang WaltherI don't know OCaml, but was involved in one of the two conflicting PRs. Will have a look.07:04:18
@k900:0upti.meK900Merges are still failing btw18:08:12
@winter:catgirl.cloudWinterstill ocaml?18:24:35
@winter:catgirl.cloudWintercan take a peek18:24:37
25 Oct 2025
@yuka:yuka.devYureka (she/her)since the last staging-next merge my ssh sessions are extremely sluggish to unusable. new text does not appear until I press some more keys06:59:43
@k900:0upti.meK900There's a weird openssh bug with multiplexing07:01:08
@k900:0upti.meK900 @Lily Foster found it the other day 07:01:14
@yuka:yuka.devYureka (she/her)I do use multiplexing07:01:20
@yuka:yuka.devYureka (she/her)controlMaster07:01:27
@k900:0upti.meK900It's fixed in openssh master already07:02:14
@k900:0upti.meK900So we should have it with the next update07:02:20
@k900:0upti.meK900AFAIUI07:02:22
@yuka:yuka.devYureka (she/her)If you have a link to the bug or patch in openssh that would be wonderful07:03:33
@k900:0upti.meK900Hold on07:04:26
@k900:0upti.meK900Need to find it07:04:28
@k900:0upti.meK900https://github.com/openssh/openssh-portable/commit/beae06f56e0d0a66ca535896149d5fb0b2e8a1b4 supposedly07:05:10

Show newer messages


Back to Room ListRoom Version: 6