I have one question there because of the impact on package closure size of +78.35 MB (46.52%): Should gstreamerSupport be false by default (thus the effect of this PR be a non-default option)?
This is relatively simple PR but it touches the core of the python build system and is therefore a mass rebuild. I need some assistance in testing and reviewing.
The issue is I don’t have a darwin machine so I can’t fix the darwin build without putting in unreasonable amounts of effort. Maybe some darwin wizard will help me out.
Here are two similar patches waiting for boost17x that improve the closure size usage of packages which depend on boost17x (such as nheko). If either one will be merged it’d be great:
My PR doesn’t build on aarch64. I got “error: linker aarch64-linux-gnu-gcc not found” and I have no idea if it’s a problem with one of the Rust dependencies or if it’s a problem with the aarch64 builder.
This PR exists to upgrade fontconfig (the current version is now nearly 3 years out of date), and introduces breaking changes to fontconfig’s configuration. Because of this, it’s causing issues for lots of people who use nix on non-NixOS, because both system’s fontconfig and nix’s fontconfig will try to read configuration from /etc. As far as I can tell the PR is fine, and the only blocker seems to be the huge number of reverse-dependencies (i.e. hydra rebuilds). There’s also something about backporting old versions of fontconfig to generate font caches for older versions, but I’m not really sure what’s going on there.
I have a not too big nodePackages fix for an issue which passes all tests possible, but every once in a while it reaches a merge conflict status… And what’s annoying even more is that running node’s generate.sh takes about half a day (for me) and afterwards I have to cherry-pick only the relevant changes to the commit and discard the rest …
This one is docs-only: crucial steps are missing from the manual in the instructions for nixos lustration. Someone else figured out a solution and posted it in an issue back in 2018, all I did was add the solution to the docs. The PR doesn’t seem to have had any attention yet. It could do with someone who is familiar with bootloaders having a look at whether there is a better way of doing it, and maybe suggesting some commentary for the new steps.
This one isn’t terribly important or complicated. A new package for the virtual ANS microtonal synthesizer. It’s been approved and seems to be waiting for a merge. However, as I have no means of testing the darwin version, it’s simply disabled, even though it would probably work. So perhaps someone with a Mac could test it there. https://github.com/NixOS/nixpkgs/pull/90624
I wrote a package for ILSpy, but the reviewer demands building it from source, something I don’t need or have the time to do, so maybe someone else wants to pick it up?
Hello, I’m trying to upgrade the broken Mesos package, currently failing because autoconfigure cannot find Python package google.protobuf and I don’t know how to fix that issue.
I’m trying to get the EC2 metadata fetcher to use IMDSv2. I have built imported and tested images on AWS EC2, but the script is also used by OpenStack and I’d really appreciate someone with an OpenStack setup testing that I didn’t break their compute services.
Also note that the script being changed runs in initramfs and uses busybox, so some of it is a bit subtle:
This is a very simple change but it has important consequences on the security of Nixpkgs. It would need feedback from security people because the maintainer and I are not confortable merging it.