jiebi/CodeConvo huggingface dataset:
Change:
charset-normalizer ] ++ lib.optionals (isPy27) [ brotli <ins> chardet </ins> ]; checkInputs = [

Discussion:
nixops doesn't build.
wrong eelco. Use
is it feasible to keep nixops 1.x buildable, which requires python 2.7?
I'm not very active anymore in Nixpkgs so best ask some other Python maintainers. It is labor intensive to keep these packages available, frustrating contributors.
Thanks that answers it for me. Effort is better spent on making NixOps 2 release worthy. NixOps 1 is not sustainable.
I've started a fund for NixOps maintenance on OpenCollective, because NixOps 1 is not sustainable. Please contribute if you or your company can, and spread the word. Especially recurring contributions are highly appreciated. A NixOps 2 release is the main priority, but the fund can cover other deployment tech as well. Let's do this!
Thanks for setting that up! FWIW I did just open to fix this particular rebuild issue though. (Posting explicitly b/c I'm pretty sure GH doesn't automatically notify participants when a PR fixing an issue is opened.)
On a fresh installation of Nix on MacOS, when I run I get . Is there something I need to do to get the fix from ? I'm new to Nix & NixOps, so any help is appreciated! :)
The fix from is . So you can ask to use that exact revision of nixpkgs to provide the instructions for building the package that you've asked it for, like so: Fair warning that, depending on how much of nixops's pre-requisites from that exact commit have been built & cached by hydra, you may have to wait for quite a lot of local builds before that command completes. But of course they'll be cached in your after that first run.
Thank you! Unfortunately, I get this error when I run that (even after running ): This is probably a Nix noob problem, but do you have any tips?
I tried these: adding the flag to the command... no effect. clearing my cache(s) with ... which changed the error to . This new error persists even after uninstalling & reinstalling Nix. :( seems to do nothing.

At least still works :)
The NixOps packages don't bundle their own Nix, so these Nix errors seem to pertain to the Nix you've installed. Maybe the can help?
Thank you, they helped me solve my problem - somehow my was owned by instead of .
For me, at commit (latest release) and at commit (latest in the branch), nixops is still broken, but this time because is not supported for interpreter . It once again seems to be a problem As far as I can see, dropped Python 2 support since release 3.3.0 (nixpkgs commit ) and later this has been enforced within nixpkgs at commit . And is an indirect dependency of . I'm not sure if I should create a separate issue for this or if this issue can be reused.
please open a new issue for that and comment here once you have.
Change:
<del> diff --git a/kvmfr.c b/kvmfr.c index 121aae5b..2f4c9e1a 100644 --- a/kvmfr.c +++ b/kvmfr.c @@ -539,7 +539,11 @@ static int __init kvmfr_module_init(void) if (kvmfr->major < 0) goto out_free; +#if LINUX_VERSION_CODE < KERNEL_VERSION(6, 4, 0) kvmfr->pClass = class_create(THIS_MODULE, KVMFR_DEV_NAME); +#else +  kvmfr->pClass = class_create(KVMFR_DEV_NAME); +#endif if (IS_ERR(kvmfr->pClass)) goto out_unreg; </del>

Discussion:
Steps to reproduce the behavior: kvmfr <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
with subtest("Wait for tayga"): router.wait_for_unit("tayga.service") <del> with subtest("Test ICMP"): </del> <ins> with subtest("Test ICMP server -> client"): server.wait_until_succeeds("ping -c 3 192.0.2.42 >&2") with subtest("Test ICMP and show a traceroute server -> client"): server.wait_until_succeeds("mtr --show-ips --report-wide 192.0.2.42 >&2") with subtest("Test ICMP client -> server"): </ins> client.wait_until_succeeds("ping -c 3 64:ff9b::100.64.0.2 >&2") <del> with subtest("Test ICMP and show a traceroute"): </del> <ins> with subtest("Test ICMP and show a traceroute client -> server"): </ins> client.wait_until_succeeds("mtr --show-ips --report-wide 64:ff9b::100.64.0.2 >&2") router.log(router.execute("systemd-analyze security tayga.service")[1])

Discussion:
When using the provided tayga service, it's not really possible to setup explicit mappings. This seems like an oversight. N/A Some sort of should exist. N/A It is possible to workaround the issue by sticking them into but... uh yeah anyway. :sweat_smile: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (?) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
staging = fetchFromGitHub rec { # https://github.com/wine-staging/wine-staging/releases inherit (unstable) version; <del> sha256 = "sha256-TvTx3vSOyudyC7aravQGcj5KGqI8uHkgHroIJww5buQ="; </del> <ins> sha256 = "sha256-rR5m6D8M3vTXXIHzsF8+o2G5rlRS2HLfCHoatbJwlrQ="; </ins> owner = "wine-staging"; repo = "wine-staging"; rev = "v${version}";

Discussion:
The readme of yabridge says: And my plugins are not loading anymore. I tried this: but that gives me GLIBC2.33' not found (required by /home/user/Bitwig )` plugins loading
Looks like there is a patch that we could apply to wine? Don't know if that one will end up in 6.16 already - that should be just around the corner.
With this shouldn't be a problem anymore!
Change:
buildInputs = [ pkgconfig ffmpeg ]; <del> # XXX This removes the -O2 flag, to avoid errors like: #   cgo-dwarf-inference:2:8: error: enumerator value for '__cgo_enum__0' is not an integer constant # This is a workaround for nixpkgs+golang BUG https://github.com/NixOS/nixpkgs/issues/25959 hardeningDisable = [ "fortify" ]; </del> enableParallelBuilding = true; meta = with stdenv.lib; {

Discussion:
Using go + I am unable to build a simple Go program that makes use of C bindings. The program is a testcase from the Go compiler repository ( ) . The build fails with an error message like this: Another example is geth, the go ethereum client, in version 1.6.1: Switching to clang instead seems to be a workaround for the problem: This last command builds successfully. System: (Hummingbird) Nix version: nix-env (Nix) 1.11.9 Nixpkgs version: Sandboxing enabled: false
I think this has to do with how Go handles GOROOT. It expects to be able to write to $GOROOT even though it's a read-only path. Could you try the buildCommand in go-ethereum:
Aw, I was wondering how to get rid of that warning. The warning is gone, but it doesn't seem to have helped: I originally ran into this issue when I tried to upgrade that linked Nix expression. Version 1.4.7 of go-ethereum compiles just fine, but 1.6.1 doesn't, because now one of the dependencies makes use of some kind of C bindings. While playing around with it I also switched over to using in the Nix expression, but that also didn't help. Switching to clang helped in the end. That version can be found here: But that's just a workaround and I would assume that other Go packages will at some point also run into this problem when they just use or .
I ran into this problem adding seccomp support to the docker package. It's caused by the -O2 optimization flag which is being by the fortify hardening flag. A possible fix would be to add hardeningDisable = [ "fortify" ]; to the buildGoPackage.
I can't no longer reproduce this on my system so I guess the issue is fixed? I created a PR to get rid of the workarounds:
I can confirm that I also cannot reproduce this anymore on my system. I am closing this - thanks!
Change:
1. (legacy) a system string. <del> 2. (modern) a pattern for the platform `parsed` field. </del> <ins> 2. (modern) a pattern for the entire platform structure (see `lib.systems.inspect.platformPatterns`). </ins> <del> 3. (functional) a predicate function returning a boolean. </del> <ins> 3. (modern) a pattern for the platform `parsed` field (see `lib.systems.inspect.patterns`). </ins> We can inject these into a pattern for the whole of a structured platform, and then match that. */ <del> platformMatch = platform: elem: if builtins.isFunction elem then elem platform else let </del> <ins> platformMatch = platform: elem: let </ins> pattern = if builtins.isString elem then { system = elem; } <ins> else if elem?parsed then elem </ins> else { parsed = elem; }; in lib.matchAttrs pattern platform;

Discussion:
I am working on this bug. First reported . The root cause of the problem is that there is no "pattern" (see ) representation for . It is special, unlike all the other platform predicates. It is this way because exists, and because ... in other words, "static-ness" is not represented in the triple for a platform. Right now we try to pretend that you can reconstruct all the pattern-representable aspects of a from its . That isn't really true, because of and , and it's getting more untrue as time goes on. The long-term solution is to stop pretending. I have a possible short-term fix that I'm testing.
Change:
<ins> { lib , argcomplete , jinja2 , meraki , rich , fetchPypi , buildPythonApplication , pytestCheckHook , requests-mock }: buildPythonApplication rec { pname = "meraki-cli"; version = "1.5.0"; format = "setuptools"; src = fetchPypi { pname = "meraki_cli"; inherit version; hash = "sha256-YOyeovqRqt6ZMXgLnIxRvPkcW259K8NIBGdb3PwjkMg="; }; disabledTests = [ # requires files not in PyPI tarball "TestDocVersions" "TestHelps" # requires running "pip install" "TestUpgrade" ]; propagatedBuildInputs = [ argcomplete jinja2 meraki rich ]; nativeBuildInputs = [ pytestCheckHook ]; nativeCheckInputs = [ requests-mock ]; pythonImportsCheck = [ "meraki_cli" ]; meta = with lib; { homepage = "https://github.com/PackeTsar/meraki-cli"; description = "A simple CLI tool to automate and control your Cisco Meraki Dashboard"; license = licenses.mit; maintainers = with maintainers; [ dylanmtaylor ]; platforms = platforms.unix; mainProgram = "meraki"; }; } </ins>

Discussion:
Project description A simple CLI tool to automate and control your Cisco Meraki Dashboard Metadata homepage URL: source URL: license: mit platforms: unix
Change:
<ins> diff --git a/Cargo.lock b/Cargo.lock index f01f824..e00d079 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -328,7 +328,7 @@ dependencies = [ [[package]] name = "swayws" -version = "1.1.1" +version = "1.2.0" dependencies = [ "clap", "env_logger", </ins>

Discussion:
Package name: swayws Latest released version: 1.2.0 <!-- Search your package here: --- Current version on the unstable channel: 2022-03-10 Current version on the stable/release channel: 2022-03-10 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
Change:
bws = callPackage ../tools/security/bws { }; <del> byobu = callPackage ../tools/misc/byobu { # Choices: [ tmux screen ]; textual-window-manager = tmux; }; </del> bsh = fetchurl { url = "http://www.beanshell.org/bsh-2.0b5.jar"; hash = "sha256-YjIZlWOAc1SzvLWs6z3BNlAvAixrDvdDmHqD9m/uWlw=";

Discussion:
Package name: Byobu Latest released version: 6.12Current version on the unstable channel: 5.133 Current version on the stable/release channel: 5.133 Byobu development has permanently moved from Launchpad to GitHub Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
pinging and as maintainers
Change:
sha256 = "0hz1ryimh0w8zyxx4y8chcn54d6b02spflj5k9rcg26an2chkg2w"; }; <ins> # Uber's abandoned this since Jun 2018, so we have to patch a lot. # Yay. patches = let # "Add support for Python3.7 (#151)": py37-support = [ # https://github.com/uber/pyflame/pull/153 (fetchpatch { # "Add support for python3.7" url = "https://github.com/uber/pyflame/commit/5ee674c4b09a29b82a0e2d7a4ce064fea3df1f4c.patch"; sha256 = "19v0yl8frbsq1dkvcmr1zsxf9v75bs8hvlkiv2x8cwylndvz2g5n"; }) (fetchpatch { # "Add python3.7 to travis test matrix" url = "https://github.com/uber/pyflame/commit/610b5281502ff6d57471e84071f17a33d30f3bcf.patch"; sha256 = "13kwzrz0zwmdiirg061wvz7zvdl2w9dnrc81xbkxpm1hh8h0mi9z"; }) (fetchpatch { # "Update ppa and Ubuntu version" url = "https://github.com/uber/pyflame/commit/ec82a43c90da64815a87d4e3fe2a12ec3c93dc38.patch"; sha256 = "1rrcsj5095ns5iyk6ij9kylv8hsrflxjld7b4s5dbpk8jqkf3ndi"; }) (fetchpatch { # "Clang-Format" url = "https://github.com/uber/pyflame/commit/fb81e40398d6209c38d49d0b6758d9581b3c2bba.patch"; sha256 = "024namalrsai8ppl87lqsalfgd2fbqsnbkhpg8q93bvsdxldwc6r"; }) ]; # "Fix pyflame for code compiled with ld -z separate-code": separate-code-support = [ # https://github.com/uber/pyflame/pull/170 (fetchpatch { # "Fix for code compiled with ld -z separate-code" url = "https://github.com/uber/pyflame/commit/739a77d9b9abf9599f633d49c9ec98a201bfe058.patch"; sha256 = "03xhdysr5s73bw3a7nj2h45dylj9a4c1f1i3xqm1nngpd6arq4y6"; }) ]; # "Improve PtraceSeize error output" full-ptrace-seize-errors = [ # https://github.com/uber/pyflame/pull/152 (fetchpatch { # "Print whole error output from PtraceSeize" url = "https://github.com/uber/pyflame/commit/4b0e2c1b442b0f0c6ac5f56471359cea9886aa0f.patch"; sha256 = "0nkqs5zszf78cna0bavcdg18g7rdmn72li3091ygpkgxn77cnvis"; }) (fetchpatch { # "Print whole error for PtraceSeize" url = "https://github.com/uber/pyflame/commit/1abb23abe4912c4a27553f0b3b5c934753f41f6d.patch"; sha256 = "07razp9rlq3s92j8a3iak3qk2h4x4xwz4y915h52ivvnxayscj89"; }) ]; in stdenv.lib.concatLists [ py37-support # Without this, tests will leak memory and run forever. separate-code-support full-ptrace-seize-errors ]; </ins> nativeBuildInputs = [ autoreconfHook pkgconfig ]; <del> buildInputs = [ python36 python2 python35 ]; </del> <ins> buildInputs = [ python37 python36 python2 python35 ]; </ins> postPatch = '' patchShebangs .

Discussion:
fails to build if there are ptrace scope restrictions (e.g. when using the hardened profile.) to configuration (or add to ) already built, modify something in to change the hash build failure on failing tests: <details<summaryLog</summary</detailsPlease run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
doesn't fix this problem because the pyflame build's tests still fail on a NixOS with the hardened profile enabled:
Change:
(http://pypi.python.org/pypi/setuptools/), which represents a large number of Python packages nowadays.  */ <del> { python, setuptools, wrapPython, lib, offlineDistutils, setuptoolsSite }: </del> <ins> { python, setuptools, wrapPython, lib, offlineDistutils, recursivePthLoader }: </ins> { name, namePrefix ? "python-"

Discussion:
We need to propagate the pth loader so packages using us process our pth files, but it makes no sense to have the pth loader itself in a pth file.
Change:
blackmagic-desktop-video = callPackage ../tools/video/blackmagic-desktop-video { }; <del> blockbench-electron = callPackage ../applications/graphics/blockbench-electron { }; </del> blocksat-cli = with python3Packages; toPythonApplication blocksat-cli; bmap-tools = callPackage ../tools/misc/bmap-tools { };

Discussion:
Package name: blockbench-electron Latest released version: 4.9.3 <!-- Search your package here: --- Current version on the unstable channel: 4.8.1 Current version on the stable/release channel: 4.8.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Misc: Noticed this when trying to enter a nix shell with this package, resulting in an electron-25.9.0 EOL error. Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Okay, so I took a look at updating blockbench to a version with uses and but it looks like after 2 seconds, electron crashes. It's probably got to do something with , but I don't have much experience with it. Tried to debug it with , but it didn't really show me anything helpful. I even tried packaging from source, but it has the same issue.
Okay, so I did some more testing, and it looks like itself is the issue, and above work fine. I'll make a PR with the update.
Change:
postPatch = let darwinPatches = '' <ins> bazelLinkFlags () { eval set -- "$NIX_LDFLAGS" local flag for flag in "$@"; do printf ' -Wl,%s' "$flag" done } </ins> # Disable Bazel's Xcode toolchain detection which would configure compilers # and linkers from Xcode instead of from PATH export BAZEL_USE_CPP_ONLY_TOOLCHAIN=1

Discussion:
Describe the bug bazel broken on darwin in nixpkgs HEAD () To Reproduce Steps to reproduce the behavior: to build bazel on darwin Expected behavior Able to build bazel on darwin Additional context might be related to Metadata Please run and paste the result. Maintainer information: cc:
The bazel build is passing LDFLAGS flags to the compiler instead of the linker. Those should be prefixed with or moved somewhere else.
Clang used as a frontend should accept linker flags.
Flags were in .
Change:
<ins> diff --git a/crates/pyxel-platform/build.rs b/crates/pyxel-platform/build.rs index 35cdeef5..68a93ed9 100644 --- a/crates/pyxel-platform/build.rs +++ b/crates/pyxel-platform/build.rs @@ -30,7 +30,7 @@ impl SDL2BindingsBuilder { } fn should_bundle_sdl2(&self) -> bool { -        self.target_os.contains("windows") || self.target_os == "darwin" +        false } fn download_sdl2(&self) { </ins>

Discussion:
Project description Pyxel is a retro game engine for Python. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
oops!
Change:
<del> { lib, stdenv, fetchFromGitHub, fetchpatch, automake, autoconf, libtool , zimlib, cxxtools, tntnet }: stdenv.mkDerivation { name = "zimreader-0.92"; src = fetchFromGitHub { owner = "wikimedia"; repo = "openzim"; rev = "r1.3"; # there multiple tools with different version in the repo sha256 = "0x529137rxy6ld64xqa6xmn93121ripxvkf3sc7hv3wg6km182sw"; }; patchFlags = [ "-p2" ]; patches = [ (fetchpatch { name = "zimreader_tntnet221.patch"; url = "https://github.com/wikimedia/openzim/compare/r1.3...juliendehos:3ee5f11eaa811284d340451e6f466529c00f6ef2.patch"; sha256 = "0rc5n20svyyndqh7hsynjyblfraphgi0f6khw6f5jq89w9i1j1hd"; }) ]; enableParallelBuilding = true; buildInputs = [ automake autoconf libtool zimlib cxxtools tntnet ]; setSourceRoot = '' sourceRoot=$(echo */zimreader) ''; preConfigure = "./autogen.sh"; meta = { description = "A tool to serve ZIM files using HTTP"; homepage = "http://git.wikimedia.org/log/openzim"; license = lib.licenses.gpl2; maintainers = with lib.maintainers; [ robbinch juliendehos ]; platforms = [ "x86_64-linux" ]; }; } </del>

Discussion:
Describe the bug Kiwix fails to build with a C++ code error. To Reproduce Steps to reproduce the behavior: , because the package is marked as insecure, Expected behavior Kiwix builds. Additional context The error: Probably this needs to be solved for . Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(mario): channels(root): nixpkgs: Maintainer information:
I marked this as stale due to inactivity. &rarr;
See
Change:
<ins> { lib , buildGoModule , fetchFromGitHub , installShellFiles , stdenv }: buildGoModule rec { pname = "lilipod"; version = "0.0.3"; src = fetchFromGitHub { owner = "89luca89"; repo = "lilipod"; rev = "v${version}"; hash = "sha256-PqeYNLr4uXe+H+DLENlUpl1H2wV6VJvDoA+MVP3SRqY="; }; vendorHash = null; nativeBuildInputs = [ installShellFiles ]; buildPhase = '' runHook preBuild RELEASE_VERSION=${version} make all runHook postBuild ''; checkPhase = '' runHook preCheck make coverage runHook postCheck ''; installPhase = '' runHook preInstall install -Dm755 lilipod $out/bin/lilipod runHook postInstall ''; postInstall = lib.optionalString (stdenv.buildPlatform.canExecute stdenv.hostPlatform) '' installShellCompletion --cmd lilipod  --bash <($out/bin/lilipod completion bash)  --fish <($out/bin/lilipod completion fish)  --zsh <($out/bin/lilipod completion zsh) ''; meta = { description = "A very simple (as in few features) container and image manager"; longDescription = '' Lilipod is a very simple container manager with minimal features to: - Download and manager images - Create and run containers It tries to keep a somewhat compatible CLI interface with Podman/Docker/Nerdctl. ''; homepage = "https://github.com/89luca89/lilipod"; license = lib.licenses.gpl3Only; mainProgram = "lilipod"; maintainers = with lib.maintainers; [ aleksana ]; platforms = lib.platforms.linux; }; } </ins>

Discussion:
Package request: (a very simple container and image manager) Lilipod is also a nice fallback for when no container-manager is found, or when it's not possible to install one. Being a fully self-contained binary that lives in one directory (LILIPOD_HOME) it makes it easy to install and remove without package managers. Check:
In case anyone needs this shortcut, I already made a package in my NUR repo.
Change:
# Needed on gcc >= 6. env.NIX_CFLAGS_COMPILE = "-Wno-narrowing"; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "A tool for recording audio or data CD-Rs in disk-at-once (DAO) mode"; homepage = "https://cdrdao.sourceforge.net/"; <del> platforms = platforms.linux; license = licenses.gpl2; </del> <ins> platforms = lib.platforms.unix; license = lib.licenses.gpl2; </ins> }; <del> } </del> <ins> }) </ins>

Discussion:
Ripped CD The original issue: The fix linked in the issue: So the fix seems to be either downgrade to 1.2.4 or apply the patch listed in the arch repo. Please run and paste the result.
It's hard to imagine how this specific error could be related to an encoding issue... both of your links point to the same place, do you have a link to the fix you're talking about?
Ah, I found the one used in the Arch package. I'm not presently able to test the fix myself, however; if I give you an amended Nixpkgs branch and instructions to try it, would you be able to see if it works correctly?
I applied the downgrade and it works. If you can give me the patch I can test it as well.
Thanks; please try (patch: ). Sadly it seems like neither cdrdao nor whipper get very much upstream maintainer attention these days...
Gave it a try with the following in my home-manager config: I was able to successfully rip a CD so the patch seems to be effective. :partying_face:
Thanks for testing; opened