!UNVBThoJtlIiVwiDjU:nixos.org

Staging

317 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
14 Nov 2025
@vcunat:matrix.orgVladimír Čunát Yes, staging-next in a few moments. No use blocking that because of the cachix situation. 08:22:49
@vcunat:matrix.orgVladimír Čunáthttps://github.com/NixOS/nixpkgs/pull/46152309:49:27
@leona:leona.isleonathank you09:50:21
@vcunat:matrix.orgVladimír ČunátI'd hope we can merge it around 25th - 26th.09:52:04
@vcunat:matrix.orgVladimír Čunáte.g. the last spacing was 12 days.09:52:27
@ivy:faggot.shivybut still no cachix fix?09:52:53
@vcunat:matrix.orgVladimír ČunátI'm not aware of any.09:53:38
@leona:leona.isleonayes, we probably need to move the branch-off a bit.09:54:18
@vcunat:matrix.orgVladimír ČunátPeople relevant to cachix had been pinged over GitHub mentions and Matrix. I saw also Robert's emoji-reaction on that. I'd hope that a fix won't need any huge rebuild.09:57:53
@dwoffinden:matrix.orgDaniel joined the room.14:27:38
@wolfgangwalther:matrix.orgWolfgang WaltherPeriodic merges are right now failing constantly. This seems to be related to Nixpkgs' repo size on GitHub. The Nixpkgs core team is in touch with GitHub to look into that.18:25:15
@pyrox:pyrox.devdish [Fox/It/She]congratulations to the nixpkgs community for finding yet another github limitation18:30:33
@pyrox:pyrox.devdish [Fox/It/She]* congratulations to the nixpkgs community for finding yet another github issue related to the size of the repo lol18:30:41
@vcunat:matrix.orgVladimír ČunátI've been seeing lots of unicorns in the past few days, too.18:38:10
@wolfgangwalther:matrix.orgWolfgang Waltheryeah me too. We're unsure whether Nixpkgs maybe caused https://www.githubstatus.com/incidents/1jw8ltnr1qrj :D18:40:16
@hexa:lossy.networkhexa maybe get your head checked 18:53:15
@glepage:matrix.orgGaétan Lepage Should protobuf: 33.0 -> 33.1 target staging or staging-next? 23:38:16
15 Nov 2025
@vcunat:matrix.orgVladimír Čunát

Rebuild: linux 4523, darwin 2011

Rebuild-wise that would be OK for either branch at this point. But note that staging won't reach 25.11 whereas this staging-next will. That also implies restrictions on breaking changes.

06:29:17
@glepage:matrix.orgGaétan Lepage Ok thanks, rebased to staging-next. 09:22:50
@vcunat:matrix.orgVladimír Čunát We'll now get a nixpkgs-unstable channel update, within a couple hours. 11:12:32
@k900:0upti.meK900ncurses-abi5-compat is broken14:17:09
@k900:0upti.meK900No idea why or what's pulling it in14:17:19
@winston:winston.shwinstonoh it might've been https://github.com/NixOS/nixpkgs/pull/39088714:30:33
@winston:winston.shwinstonreverting that lets me build it at least14:31:19
@glepage:matrix.orgGaétan Lepage hexa do you think I should bump google-cloud-cpp to 2.43.0? 14:32:53
@hexa:lossy.networkhexatough question at this time14:33:14
@hexa:lossy.networkhexapeople are looking into frigate segfaulting again in protobuf14:33:23
@winston:winston.shwinston this
  ++ lib.optional (unicodeSupport && abiVersion == "5") "--enable-widec"
  ++ lib.optional (!unicodeSupport && abiVersion == "6") "--disable-widec"
would work? but kinda eugh
14:37:47
@winston:winston.shwinston at least i get -A ncurses -A ncurses5 -A libtinfo to all build 14:38:04
@hexa:lossy.networkhexaso it might end up that way14:38:06

Show newer messages


Back to Room ListRoom Version: 6