!UNVBThoJtlIiVwiDjU:nixos.org

Staging

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

Load older messages


SenderMessageTime
25 Sep 2025
@emilazy:matrix.orgemilyI was thinking it might be via some non-free thing, but I guess if anything substantial required people to build GHC themselves we'd hear about it15:00:46
@sternenseemann:systemli.orgsternimysterious I was convinced that we build something that pulls in GHC on i686-linux17:28:26
@sternenseemann:systemli.orgsterniMaybe it was flac? https://github.com/NixOS/nixpkgs/pull/43754317:28:52
@k900:0upti.meK900 Could be 17:29:41
@emilazy:matrix.orgemily yeah, even without that PR it looks like it'd be harmless to drop on i686-linux 18:35:53
@emilazy:matrix.orgemily since we'd just get no man pages for something that is surely only being used as a component of stuff to host on an x86_64-linux system that can get its own flac manpages 18:36:23
26 Sep 2025
@elvishjerricco:matrix.orgElvishJerriccocursed knowledge of the day: the linux kernel depends on systemd because of rsync: https://github.com/NixOS/nixpkgs/pull/44625906:55:26
@elvishjerricco:matrix.orgElvishJerricco(hi I'm trying to at least a little bit minimize the rebuild count of systemd)06:56:47
@vcunat:matrix.orgVladimír Čunát gcc 15 seems to be giving up NixOS 25.11, but glibc upgrade not yet 😅 11:32:44
@vcunat:matrix.orgVladimír ČunátMaybe I'd prefer not to rush it in the last allowed week either, given the concerns (e.g. around executable stack).11:39:25
@marie:marie.cologneMarieFor gcc 15 we would also need this, since gcc 15 cross compilers are broken right now, because our ancient patch doesn't apply anymore https://github.com/NixOS/nixpkgs/pull/445308/13:31:48
@k900:0upti.meK900Beautiful13:32:54
@ghpzin:envs.netghpzin Could you ref gcc15 PR, so people know there is a fix for pkgsCross/pkgsStatic 13:35:22
@ghpzin:envs.netghpzin Could you ref gcc15 PR, so people know there is a fix for pkgsCross/pkgsStatic
13:35:29
@ghpzin:envs.netghpzin Could you ref gcc15 PR, so people know there is a fix for pkgsCross/pkgsStatic
(kind of hard to find these, already had rebase of that patch in my fork)
13:36:12
@ghpzin:envs.netghpzin Could you ref gcc15 PR (https://github.com/NixOS/nixpkgs/pull/440456), so people know there is a fix for pkgsCross/pkgsStatic
(kind of hard to find these, already had rebase of that patch in my fork)
13:36:51
@marie:marie.cologneMariesure13:38:50
@ghpzin:envs.netghpzinMaybe somebody already made PR to update musl bootstrap files, but it is also impossible to find.13:55:23
@ghpzin:envs.netghpzin Maybe somebody already made PR to update musl bootstrap files (to fix pkgsMusl), but it is also impossible to find. 14:00:17
@emilazy:matrix.orgemilyGCC 15 also needs some Darwin stuff I have locally18:31:27
@emilazy:matrix.orgemilyprobably 26.05 makes the most senes at this point18:31:34
@emilazy:matrix.orgemily 💜 to ghpzin for all the fix PRs though 18:31:39
@sliedes:hacklab.fiSami Liedes

Ah, I may have found the room! I've been patching a bit stuff in nixpkgs which I think probably also applies to gcc 15. (Specifically what I've been fixing is packages building with GCC 14 and -D_GLIBCXX_DEBUG, which requires things that declare themselves as random access iterators to have operator<=; but I read in some bug report that gcc 15 is also similarly picky about some iterator operators.)

Is there a branch somewhere where the proposed gcc 15 patches are collected? I could switch to that and start fixing for it with -D_GLIBCXX_DEBUG, so I would likely at the same time fix them for gcc 15.

18:32:26
@emilazy:matrix.orgemily those fixes can go to master just fine 18:34:43
@emilazy:matrix.orgemilywe prefer backported patches already applied upstream, then patches from other distros / unmerged patches already sent upstream by others, then patches we write and submit upstream ourselves, and only then patches that only live in Nixpkgs18:35:15
@sliedes:hacklab.fiSami LiedesYes, that's understandable. My thought was it's easier to get farther faster if there's a working branch with temporary fixes even if they never get to master, because then you get to test also dependencies of what doesn't now build in master.18:36:25
@emilazy:matrix.orgemilyusually we just maintain those locally and clean them up as we push them out18:38:18
@sliedes:hacklab.fiSami LiedesBut obviously I can also maintain a personal branch for that :)18:38:22
@sliedes:hacklab.fiSami LiedesYeah, that's what I've been doing.18:38:29
@emilazy:matrix.orgemilyor just push them out as branches on a fork18:38:40

Show newer messages


Back to Room ListRoom Version: 6