!UNVBThoJtlIiVwiDjU:nixos.org

Staging

364 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%3Aopen116 Servers

Load older messages


SenderMessageTime
7 Apr 2026
@vcunat:matrix.orgVladimír ČunátUh, I triggered eval yesterday but I forgot to push the merge of staging->staging-next. Fixed now, and opened the new staging-next PR: https://github.com/NixOS/nixpkgs/pull/50747003:45:55
@hexa:lossy.networkhexahttps://seclists.org/oss-sec/2026/q2/30 samba update on thursday15:17:37
8 Apr 2026
@reckenrode:matrix.orgRandy Eckenrode Ah, crap. I think I caused a merge conflict from master to staging. I merged the Darwin by-name migration into master, but a sigtool change landed recently in staging. 00:28:47
@reckenrode:matrix.orgRandy Eckenrode * Ah, crap. I think I caused a merge conflict from master to staging. I merged the Darwin by-name migration into master (due to no rebuilds), but a sigtool change landed recently in staging. 00:28:58
@hexa:lossy.networkhexafeel free to resolve :p00:38:11
@reckenrode:matrix.orgRandy EckenrodeI resolved the merge conflict. It actually made its way all the way to staging-next. (Fortunately, still no rebuilds from the conflicting change …..)01:19:47
@k900:0upti.meK900
       > +(json.sh:54) script -e -q /dev/null -c 'nix eval --json --expr \{\ a.b.c\ =\ true\;\ \}'
       > script: unexpected number of arguments
       > Try 'script --help' for more information.
05:51:07
@k900:0upti.meK900nix-functional-tests on staging-next05:51:12
@k900:0upti.meK900 CC @Sergei Zimmerman (xokdvium) 05:51:17
@k900:0upti.meK900Also yeeted some other misc fixes to -next that I found building all of my things overnight06:15:30
@sampointon:matrix.orgsampointon joined the room.06:36:57
@k900:0upti.meK900 I assume it's this 10:00:40
@k900:0upti.meK900https://github.com/util-linux/util-linux/commit/70507ab9eaed10b8dd77b77d4ea25c11ee726bed10:01:35
@k900:0upti.meK900 @Sergei Zimmerman (xokdvium) should we just fix the test for now? 10:02:50
@k900:0upti.meK900Or maybe skip it in nixpkgs10:02:57
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Skipping is ok. Patching it out is fine, not at the keyboard now though10:05:19
@k900:0upti.meK900Ouch10:06:10
@k900:0upti.meK900There's already a skip in there10:06:12
@k900:0upti.meK900That I'm not sure we even need anymore10:06:17
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/commit/5cf4e4a70ea305be8f1f425e4bc009bf10ebf47210:06:47
@xokdvium:matrix.orgSergei Zimmerman (xokdvium)Yeah it did get fixed with the toml bump10:07:23
@k900:0upti.meK900OK, unspeakable horrors have been shipped10:13:08
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/commit/64d65a80f2c844edb3b22277c6ebe2a33c5cdf6d10:13:21
@k900:0upti.meK900Also, emacs-nox is broken by something something tree-sitter something10:31:49
@k900:0upti.meK900https://github.com/emacs-mirror/emacs/commit/d587ce8c65a0e22ab0a63ef2873a3dfcfbeba16610:36:50
@k900:0upti.meK900OK I think this should help10:36:54
@k900:0upti.meK900Oh great10:52:54
@k900:0upti.meK900libarchive is busted on Darwin10:53:12
@k900:0upti.meK900So I can't test the other emacs10:53:24
@k900:0upti.meK900
┃        > Undefined symbols for architecture arm64:
┃        >   "__libiconv_version", referenced from:
┃        >       _archive_version_details in archive_version_details.o
┃        >       _archive_libiconv_version in archive_version_details.o
┃        > ld: symbol(s) not found for architecture arm64
┃        > clang: error: linker command failed with exit code 1 (use -v to see invocation)
10:53:39

Show newer messages


Back to Room ListRoom Version: 6