!UNVBThoJtlIiVwiDjU:nixos.org

Staging

349 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%3Aopen115 Servers

Load older messages


SenderMessageTime
7 Oct 2025
@niklaskorz:matrix.orgniklaskorz

basically:

I think the warning-avoiding fix in gettext.h works only for gcc,
because gcc recognizes 'gettext', 'dgettext', 'dcgettext' as built-ins.

11:06:31
@niklaskorz:matrix.orgniklaskorzfollowed by:11:06:48
@niklaskorz:matrix.orgniklaskorz

the more pragmatic way is to just accept the fact that clang
produces more warnings than gcc, and to filter out / triage the warnings
from the compilation log

11:06:54
@niklaskorz:matrix.orgniklaskorzso unless you happen to know a way to make clang also treat gettext as a built-in, I'll open the PR to disable the warning now on coreutils11:08:54
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)Hey, so uh, i made a mistake, and i am wondering what the best way of fixing it is: https://github.com/NixOS/nixpkgs/pull/444579 This was targetting staging, and i merged it before i saw the cycle was started. This means the break is now in master, the fix was merged to staging, but is not yet at master. Do i just open a new PR against master with the same exact patch and merge that?11:27:39
@hexa:lossy.networkhexayes11:37:13
@reckenrode:matrix.orgRandy EckenrodeNo. I’m surprised there’s not an annotation for it.11:40:29
@niklaskorz:matrix.orgniklaskorzbuild passing: https://github.com/NixOS/nixpkgs/pull/44947413:02:14
@k900:0upti.meK900I'm cooking qt 6.1013:03:57
@k900:0upti.meK900Hopefully will be done in like an hour13:04:08
@vcunat:matrix.orgVladimír ČunátWe're still changing stdenvs at this point, so I believe that's OK.13:08:24
@k900:0upti.meK900https://github.com/qt/qtconnectivity/blob/1b09545fb02a112b59148ea26ad2ca734dc0526a/src/nfc/configure.cmake#L1513:13:02
@k900:0upti.meK900Love how they've been shipping a typo for nine months13:13:09
@k900:0upti.meK900And no one notice13:13:19
@k900:0upti.meK900* And no one noticed13:13:20
@k900:0upti.meK900AAAAA SHEEEEEET WHYYYY13:52:34
@k900:0upti.meK900There's a Vulkan SDK update too13:52:41
@k900:0upti.meK900This is not how I wanted to spend today13:52:46
@k900:0upti.meK900BUT OK13:52:49
@vcunat:matrix.orgVladimír Čunát staging-next opened:
https://github.com/NixOS/nixpkgs/pull/449539
15:17:58
@vcunat:matrix.orgVladimír Čunát(big eval running now)15:18:05
@vcunat:matrix.orgVladimír ČunátBut sure, we can still add important-enough stuff.15:18:18
@hexa:lossy.networkhexahrm15:25:05
@hexa:lossy.networkhexapython 3.13.815:25:10
@hexa:lossy.networkhexabut also staging-25.05 🫣15:25:20
@k900:0upti.meK900I have Qt 6.10 very soon15:30:51
@k900:0upti.meK900I HOPE15:30:55
@k900:0upti.meK900And then Vulkan SDK15:30:58
@k900:0upti.meK900Python is stdenv rebuild on Darwin15:31:32
@k900:0upti.meK900So we need to do that fast15:31:37

Show newer messages


Back to Room ListRoom Version: 6