!UNVBThoJtlIiVwiDjU:nixos.org

Staging

391 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/128 Servers

Load older messages


SenderMessageTime
20 May 2026
@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
@jkarlson:kapsi.fiEmil Thorsøe
In file included from /nix/store/q9ksx8c79jfj1cawwwzmpq3qapvpvab7-glib-2.88.1-dev/include/glib-2.0/glib/gstring.h:37,
                 from /nix/store/q9ksx8c79jfj1cawwwzmpq3qapvpvab7-glib-2.88.1-dev/include/glib-2.0/glib/giochannel.h:36,
                 from /nix/store/q9ksx8c79jfj1cawwwzmpq3qapvpvab7-glib-2.88.1-dev/include/glib-2.0/glib.h:56,
                 from ../src/vtegtk.cc:44:
../src/vtegtk.cc: In function 'char* vte_terminal_get_selection(VteTerminal*)':
../src/vtegtk.cc:4362:59: error: 'to_integral' is not a member of 'vte'
 4362 |         return g_strdup (IMPL(terminal)->m_selection[vte::to_integral(vte::platform::ClipboardType::PRIMARY)]->str);
      |                                                           ^~~~~~~~~~~
/nix/store/q9ksx8c79jfj1cawwwzmpq3qapvpvab7-glib-2.88.1-dev/include/glib-2.0/glib/gstrfuncs.h:324:38: note: in definition of macro 'g_strdup'
  324 | #define g_strdup(x) g_strdup_inline (x)

Does someone recognize off-hand, why staging-next merge invoked this error, I don't know much C++, but somehow looks like internal inconsistency, that I would not expect to compile anywhere

10:48:53
@vcunat:matrix.orgVladimír ČunátPerhaps write at least which package is triggering this glib error?10:51:41
@jkarlson:kapsi.fiEmil Thorsøevte10:51:58
@vcunat:matrix.orgVladimír ČunátThere was a major glib upgrade, so that's the trigger, most likely.10:52:00
@jkarlson:kapsi.fiEmil Thorsøecan it affect this, if it's C library?10:52:36
@jkarlson:kapsi.fiEmil Thorsøebut I guess10:52:42
@vcunat:matrix.orgVladimír ČunátWell we do see that they use this C header from this .cc file (transitively?)10:53:44
@vcunat:matrix.orgVladimír Čunát* Well we do see that they use this C header from this .cc file (transitively maybe)10:53:48
@vcunat:matrix.orgVladimír Čunát But on hydra all vte seems green: https://hydra.nixos.org/eval/1825558?filter=vte 10:54:01

Show newer messages


Back to Room ListRoom Version: 6