!UNVBThoJtlIiVwiDjU:nixos.org

Staging

312 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
21 Sep 2025
@k900:0upti.meK900We have it applied there yes19:23:04
@emilazy:matrix.orgemily we really need to revert the recommendation in the docs to use fetchpatch2 19:23:05
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/commit/8ce92ef095913dd1ed37f8235cdd30a279e6a46819:23:46
@k900:0upti.meK900Anyway I'm going to bed I think19:30:23
@k900:0upti.meK900I'll leave the webkits to build overnight19:30:28
@k900:0upti.meK900If anyone wants to figure out the dotnets that would be great19:46:42
@k900:0upti.meK900Also python313Packages.ocrmypdf is broken somehow19:46:57
@k900:0upti.meK900(it's always paperless)19:47:05
@k900:0upti.meK900(it's ALWAYS PAPERLESS)19:47:09
@winter:catgirl.cloudWinter Alyssa Ross if I test/confirm the rustc build flags thing for #401281, i imagine it’s too late for this -next, or you think we might be able to manage? fine with it going into next -next but 19:52:21
@k900:0upti.meK900Please no more cursing this cycle19:53:32
@winter:catgirl.cloudWinterfine19:54:19
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i got most of the libxml2 fallout fixed, you want to merge that? :P (please don't, and its also too late - rebuilds docbookxml and cmake and stuff)19:59:51
@emilazy:matrix.orgemilyuh, I have in-flight stuff overlapping with this20:15:53
@emilazy:matrix.orgemilyI don't think this is how we should do it20:16:00
@emilazy:matrix.orgemilycan you hold off on it? I spent quite a while looking into and addressing this and think you are adjusting the knobs in the wrong place here20:16:30
@emilazy:matrix.orgemily(btw, this type of issue affects many packages before even getting to Rust, fwiw, though I have addressed a significant amount of it locally)20:19:05
@winter:catgirl.cloudWinterunfortunately ~4 months ago me could not see into the future, but yeah, sure ig20:23:17
@winter:catgirl.cloudWinterwhat are the right knobs to adjust then?20:23:47
@winter:catgirl.cloudWinter * 20:25:41
@emilazy:matrix.orgemilyI didn't mean it like that, sorry :(20:34:08
@emilazy:matrix.orgemilyI didn't see your PR before writing stuff myself20:34:14
@emilazy:matrix.orgemilyheading out the door but can share my patches in a couple hours20:34:31
@winter:catgirl.cloudWinterit’s fine, i don’t mind as long as it gets fixed20:35:06
@winter:catgirl.cloudWinterthanks, sounds good20:35:12
@emilazy:matrix.orgemily basically Cargo has native support for this upcoming but in the meantime I think it probably makes more sense to do it in the rustc wrapper. there's also an explicit flag to the rustc bootstrap we can use, and some misc. stuff like installation logs that need cleaning up 20:35:20
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) emily You have a good idea about how to disable this test (https://gitlab.gnome.org/GNOME/librsvg/-/blob/7a19a9216b4d81ba48c834351ab1e75793ae80f7/rsvg/tests/errors.rs#L17) in librsvg (https://github.com/NixOS/nixpkgs/blob/8eaee110344796db060382e15d3af0a9fc396e0e/pkgs/by-name/li/librsvg/package.nix#L50) ? I tried checkFlags = [ "--skip=too_many_elements" ]; but the test is still being run. Its meson shelling out to cargo, so our tooling is wonky... You know our rust/llvm stack, so maybe you have a good idea? If not i'll just substitute it away (https://gitlab.gnome.org/GNOME/librsvg/-/blob/7a19a9216b4d81ba48c834351ab1e75793ae80f7/rsvg/meson.build#L383). 21:19:04
@emilazy:matrix.orgemilythis is cursed21:24:54
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)well yes XD21:25:07
@emilazy:matrix.orgemily @qyliss:fairydust.space turns out people nix Meson and Cargo after all 21:25:11

Show newer messages


Back to Room ListRoom Version: 6