!UNVBThoJtlIiVwiDjU:nixos.org

Staging

394 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%3Aopen127 Servers

Load older messages


SenderMessageTime
20 May 2026
@k900:0upti.meK900So one systemd and all the nixos tests12:03:24
@limwa:matrix.orgAndré LimaAre autostart entries not running, is that it? And is this also a problem for upstream or just for NixOS? Also, just to make sure I understand it, iirc GNOME hasn't supported autostart desktop entries in a while, is it also affected by this regression?12:18:57
@k900:0upti.meK900Autostart entries are not running12:19:30
@k900:0upti.meK900Problem kinda for upstream in weird cases, NixOS always12:19:38
@k900:0upti.meK900GNOME presumably uses the same standard systemd generator as everything else12:19:50
@limwa:matrix.orgAndré LimaRight. I just checked and GNOME didn't stop supporting autostart, it just removed it's built-in service manager. Autostart entries are handled via systemd, like you said12:24:09
@vcunat:matrix.orgVladimír ČunátI see context in the systemd room, which is maybe https://matrix.to/#/!SsuQHVzf59iBgk6YIm:0upti.me?via=nixos.org&via=matrix.org&via=tchncs.de (at least my Element thinks so; behaves weird)12:45:58
@hexa:lossy.networkhexafirefox on nixos-unstable contains a known rce22:08:02
@hexa:lossy.networkhexa150.0.222:08:05
@hexa:lossy.networkhexa I updated 150.0.2 -> 150.03 on May 12th fwiw 22:08:42
@hexa:lossy.networkhexa and -> 151.0 on may 18th 22:09:03
@hexa:lossy.networkhexathose delays are bonkers22:09:16
@9hp71n:matrix.orgghpzin Isn't it 150.0.3 on both channels now ?
Unless "known rce" part is about 150.0.3 and not 150.0.2
22:22:59
@hexa:lossy.networkhexait is about 150.0.322:29:54
@hexa:lossy.networkhexanixos-unstable indeed has 150.0.322:30:34
@hexa:lossy.networkhexathrough a half-cancelled eval that advanced22:30:47
@hexa:lossy.networkhexagod, these are confusing22:30:51
21 May 2026
@vcunat:matrix.orgVladimír ČunátI just look at the git branches for this.05:08:13
@zowoq:matrix.orgzowoqAll of the new nspawn container nixosTests seem to be broken since staging-next was merged? e.g. https://github.com/NixOS/nixpkgs/pull/52139705:44:31
@k900:0upti.meK900staging-nixos merged with xdg fixes, will start evals in a bit07:56:17
@k900:0upti.meK900Literally 5 minutes after a timer eval08:02:15
@k900:0upti.meK900Killed that, started a new one08:02:16
@vcunat:matrix.orgVladimír ČunátThat was manual eval by me after merging the systemd fix.08:04:28
@vcunat:matrix.orgVladimír ČunátI didn't know that staging-nixos was expected.08:04:56
@k900:0upti.meK900Uhh08:05:26
@k900:0upti.meK900I merged the systemd fix into staging-nixos08:05:30
@k900:0upti.meK900And then staging-nixos into master08:05:39
@k900:0upti.meK900The only other change on staging-nixos is a ty upgrade08:05:48
@k900:0upti.meK900 So I don't think we're going to have a problem there 08:05:57
@vcunat:matrix.orgVladimír ČunátAh, I overlooked the target branch.08:06:28

Show newer messages


Back to Room ListRoom Version: 6