jiebi/CodeConvo huggingface dataset:
Change:
let inherit (torch) cudaCapabilities cudaPackages cudaSupport; <del> inherit (cudaPackages) cudatoolkit cudaFlags cudaVersion; </del> <ins> inherit (cudaPackages) backendStdenv cudaVersion; </ins> # NOTE: torchvision doesn't use cudnn; torch does! #   For this reason it is not included.

Discussion:
Since the introduction of in (), derivations should use instead of to further reduce the usage of the attribute.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
docker.succeed( "tar -tf ${examples.exportBash} | grep './bin/bash' > /dev/null" ) <ins> with subtest("Ensure bare paths in contents are loaded correctly"): docker.succeed( "docker load --input='${examples.build-image-with-path}'", "docker run --rm build-image-with-path bash -c '[[ -e /hello.txt ]]'", "docker rmi build-image-with-path", ) docker.succeed( "${examples.layered-image-with-path} | docker load", "docker run --rm layered-image-with-path bash -c '[[ -e /hello.txt ]]'", "docker rmi layered-image-with-path", ) </ins> ''; })

Discussion:
Describe the bug When using and and I get a failure that I think is unexpected. To Reproduce Steps to reproduce the behavior: With the following files: and the following : I get the following error when building like so: Note that everything works fine if I simply don't have the as an entry in the list to . Expected behavior The build to succeed and to be able to see a 'doomed' file created by the root user! Notify maintainers Can't find any: But perhaps the maintainers are good: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information:
I guess it has to do somehow with the fact that this command is running in a virtual machine. A "workaround" is to wrap the folder in a derivation: I don't quite know enough nix to know if this is committing some major crime of misunderstanding or something.
and I are in the "CODEOWNERS" file, and and I are in the test. Did you think of another place where maintainers could be listed? We don't have a standard attribute for attrsets or functions.
Change:
<ins> { callPackage, lib, pkgs, runCommand, concatText, writeText, hello, emptyFile }: let stri = writeText "pathToTest"; txt1 = stri "abc"; txt2 = stri hello; res = concatText "textToTest" [ txt1 txt2 ]; in runCommand "test-concatPaths" { } '' diff -U3 <(cat ${txt1} ${txt2}) ${res} diff -U3 ${concatText "void" []} ${emptyFile} touch $out '' </ins>

Discussion:
In my config I have and when building it gives me the following error: However if I replace it with it builds without errors. Even weirder, If I do it works without problems. The configuration builds normally system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
Tried surrounding the path in quotes?
wouldn't that make a string and not include the file in the store? As it stands, the files does get included in the store because succeds without problems.
Change:
let version = "2.19.2"; svn = subversionClient.override { perlBindings = perlSupport; }; <ins> gitwebPerlLibs = with perlPackages; [ CGI HTMLParser CGIFast FCGI FCGIProcManager HTMLTagCloud ]; </ins> in stdenv.mkDerivation {

Discussion:
start a webserver that is mean to serve for the current repo. In order to do this, it generates an httpd config with But the expression for moves to a separate output. Run in any repo.
Hm, ok, I have fixed the path issue, but it still doesn’t work because perl has no CGI module.
Change:
assert bluezSupport -> bluez != null; <del> assert lib.assertMsg (bluezSupport -> stdenv.isLinux) "Bluez support is only available on Linux."; </del> assert lib.assertMsg (enableFramework -> stdenv.isDarwin) "Framework builds are only supported on Darwin.";

Discussion:
Can't install or run a shell with package on macOS. Same with and . Steps to reproduce the behavior: macOS run an error No error and a shell with python 3.12. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Assertion was introduced in , ping All the derivations override , regardless of platform. For example:
Has always been that way, only now the assertion is more verbose. There is no point in using the variant, since it gives you nothing that is supported on darwin anyway.
Ah right, fair. The cpython derivation has code for handling Darwin + X11 support, so I assume that combination could work at least. So maybe doing this would be fine?
Change:
{ lib , stdenvNoCC , fetchurl <del> , undmg </del> <ins> , _7zz </ins> , pname , version , hash

Discussion:
Package name: losslesscut-bin Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 3.58.0 Current version on the stable/release channel: 3.58.0 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
update title aswell
Hi! Thanks for reminding, and sorry for late response. I just submitted a PR () that tries to automate the update of . Please take a look. (If merged, r-ryantm should be able to do the update from now on. User can update it through or create an update commit through ). If you need the update now, I'll open another PR that updates .
Appreciate it! I can wait until the PR is merged, no problem.
Change:
<ins> { buildGoPackage , fetchFromGitHub , lib , autossh , makeWrapper }: buildGoPackage rec { pname = "guardian-agent"; version = "0.7.2"; src = fetchFromGitHub { owner = "StanfordSNR"; repo = pname; rev = "v${version}-beta"; sha256 = "05269y944hcabn6dqa66387rdhx81vcqcyjv6m1hdbz5ba8j7mqn"; }; nativeBuildInputs = [ makeWrapper ]; goPackagePath = "github.com/StanfordSNR/guardian-agent"; goDeps = ./deps.nix; postInstall = '' mkdir -p $bin/bin $out/share/doc/${pname} cp -v ./go/src/github.com/StanfordSNR/${pname}/scripts/* $bin/bin/ cp -vr ./go/src/github.com/StanfordSNR/${pname}/{AUTHORS,doc,LICENSE,README.md} $out/share/doc/guardian-agent ''; postFixup = '' wrapProgram $bin/bin/sga-guard  --prefix PATH : "$bin/bin"  --prefix PATH : "${autossh}/bin" ''; meta = with lib; { description = "Secure ssh-agent forwarding for Mosh and SSH"; homepage = "https://github.com/StanfordSNR/guardian-agent"; license = licenses.bsd3; maintainers = with maintainers; [ mmahut ]; platforms = platforms.unix; }; } </ins>

Discussion:
Package Request: is a way of being able to do agent forwarding when using mosh. It also allows verifying commands being executed. I don't fully understand how it works, but it seems valuable, especially as I shift back to using on high-latency links.
This project looks abandoned, it has been released as as beta in 2017.
Hm, disappointing, but good point. I opened this to confirm:
I'm not really sure if we should proceed. I was going to close it, based on the response to the issue I filed on the guardian-agent repo, but I see you have a PR open now...
while I thought the same, I changed my mind because of two things. First of all there is sadly no alternative to this and mosh won't implement one, they own recommendation is actually using guardian-agent (as per ). And in the second place, the author of the project, Dima Kogan, did reply to my mail almost instantly, so while this is marked as beta, I think we should ship it with NixOS and help catch any outstanding bugs/problems with it.
Change:
<ins> { lib , python3 , python311 , fetchFromGitHub }: let python = if (builtins.tryEval python3.pkgs.nose.outPath).success then python3 else python311; in python.pkgs.buildPythonApplication rec { pname = "flexget"; version = "3.11.41"; pyproject = true; # Fetch from GitHub in order to use `requirements.in` src = fetchFromGitHub { owner = "Flexget"; repo = "Flexget"; rev = "refs/tags/v${version}"; hash = "sha256-ZSqkD53fdDnKulVPgM9NWXVFXDR0sZ94mRyV1iKS87o="; }; postPatch = '' # remove dependency constraints but keep environment constraints sed 's/[~<>=][^;]*//' -i requirements.txt ''; build-system = with python.pkgs; [ setuptools wheel ]; dependencies = with python.pkgs; [ # See https://github.com/Flexget/Flexget/blob/master/pyproject.toml apscheduler beautifulsoup4 colorama feedparser guessit html5lib jinja2 jsonschema loguru psutil pynzb pyrss2gen python-dateutil pyyaml rebulk requests rich rpyc sqlalchemy # WebUI requirements cherrypy flask-compress flask-cors flask-login flask-restx flask packaging pyparsing werkzeug zxcvbn pendulum # Plugins requirements transmission-rpc qbittorrent-api deluge-client cloudscraper python-telegram-bot ]; pythonImportsCheck = [ "flexget" "flexget.api.core.authentication" "flexget.api.core.database" "flexget.api.core.plugins" "flexget.api.core.schema" "flexget.api.core.server" "flexget.api.core.tasks" "flexget.api.core.user" "flexget.components.thetvdb.api" "flexget.components.tmdb.api" "flexget.components.trakt.api" "flexget.components.tvmaze.api" "flexget.plugins.clients.aria2" "flexget.plugins.clients.deluge" "flexget.plugins.clients.nzbget" "flexget.plugins.clients.pyload" "flexget.plugins.clients.qbittorrent" "flexget.plugins.clients.rtorrent" "flexget.plugins.clients.transmission" "flexget.plugins.services.kodi_library" "flexget.plugins.services.myepisodes" "flexget.plugins.services.pogcal_acquired" ]; # ~400 failures doCheck = false; meta = with lib; { homepage = "https://flexget.com/"; changelog = "https://github.com/Flexget/Flexget/releases/tag/v${version}"; description = "Multipurpose automation tool for all of your media"; license = licenses.mit; maintainers = with maintainers; [ pbsds ]; }; } </ins>

Discussion:
Flexget is not building on python3.12 on NixOS Unstable since nose 1.3.7 does not run on python 3.12 According to flexget website only pything versions 3.7 to 3.11 are supported: Steps to reproduce the behavior: to nixos unstable to install flex A clear and concise description of what you expected to happen. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
unpaddedbase64 = callPackage ../development/python-modules/unpaddedbase64 { }; <ins> unrardll = callPackage ../development/python-modules/unrardll { }; </ins> unrpa = callPackage ../development/python-modules/unrpa { }; untangle = callPackage ../development/python-modules/untangle { };

Discussion:
I'm unable to view cbr files (for example), I get the following Python error: I installed the package with the flag , I'm using Nixos 20.03 on nixpkgs-unstable. Maybe I didn't install the package correctly, I'm using a custom overlay where I overrided the , it seems legit to me.
Sounds legit to me as well. Though that would make sense if was even packaged in NixOS ! You can try to fix it by adding this package to and add this as a dependency to calibre
Setting disables which otherwise removes the rar support directly from the python code. The library should be distrubuted directly with Calibre, opened years ago where this was discussed.
Change:
./services/databases/hbase-standalone.nix ./services/databases/influxdb.nix ./services/databases/influxdb2.nix <ins> ./services/databases/lldap.nix </ins> ./services/databases/memcached.nix ./services/databases/monetdb.nix ./services/databases/mongodb.nix

Discussion:
Project description An lightweight authentication server that provides an opinionated, simplified LDAP interface for authentication: clients that can only speak LDAP protocol can talk to it and use it as an authentication server. Metadata homepage URL: source URL: license: platforms: unix
Here is what I came up with so far (with big help from :heart:):
I marked this as stale due to inactivity. &rarr;
Still relevant
I gave it a try in in case someone would like to take a look at it :)
Change:
Some(Hash(String::from("sha512-foo"))) ); } <ins> #[test] fn parse_lockfile_correctly() { let packages = packages( r#"{ "name": "node-ddr", "version": "1.0.0", "lockfileVersion": 1, "requires": true, "dependencies": { "string-width-cjs": { "version": "npm:string-width@4.2.3", "resolved": "https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz", "integrity": "sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==", "requires": { "emoji-regex": "^8.0.0", "is-fullwidth-code-point": "^3.0.0", "strip-ansi": "^6.0.1" } } } }"#).unwrap(); assert_eq!(packages.len(), 1); assert_eq!( packages[0].resolved, Some(UrlOrString::Url( Url::parse("https://registry.npmjs.org/string-width/-/string-width-4.2.3.tgz") .unwrap() )) ); } </ins> }

Discussion:
Lily and I talked about this in Matrix, this is the requested issue. Basically it all narrows down to this package lock: Steps to reproduce the behavior: it it hangs forever lock it works It should either give an error or just work. If it helps narrowing the npm version down, the package- was created in September of 2020 and was last changed in September of 2021.
To clarify a bit, this isn't something specific to older lockfiles, it just looks like there is a version spec format that our fetcher does not currently support, but probably should
Change:
<del> { lib, stdenv, fetchFromGitHub, autoreconfHook, alsa-lib, fftw, libpulseaudio, ncurses, iniparser }: </del> <ins> { lib , stdenv , fetchFromGitHub , autoreconfHook , alsa-lib , fftw , iniparser , libpulseaudio , ncurses , pkgconf }: </ins> stdenv.mkDerivation rec { pname = "cava"; <del> version = "0.9.0"; </del> <ins> version = "0.9.1"; src = fetchFromGitHub { owner = "karlstav"; repo = "cava"; rev = version; hash = "sha256-W/2B9iTcO2F2vHQzcbg/6pYBwe+rRNfADdOiw4NY9Jk="; }; </ins> buildInputs = [ alsa-lib

Discussion:
Package name: cava Latest released version: 0.9.1 <!-- Search your package here: --- Current version on the unstable channel: 0.9.0 Current version on the stable/release channel: 0.8.3 <!-- 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:
license = licenses.lgpl21; platforms = platforms.linux; maintainers = [ maintainers.bjornfor ]; <ins> broken = stdenv.hostPlatform.isMusl; # Broken at 2022-02-25 # See https://github.com/NixOS/nixpkgs/issues/218274 </ins> }; }

Discussion:
build .#pkgsMusl.directfb Logs at version 1.7.7: After upgrade to last commit (): After patch: adaptation of patch: Patch adapted: Logs: Affects downstream: pkgsMusl.{webkitgtk,erlang,elixir} I will do a bisect of this problem later. Please run and paste the result. Upstream: Alpine:
Note that alpine builds with specific and , meaning they only build a small subset of the directfb code. with the patches you mentioned, plus the following configureFlags, it builds:
is fixed in master. Closing.
Change:
target/*/release/build/sequoia-wot-*/out/sq-wot-path.1 ''; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Rust CLI tool for authenticating bindings and exploring a web of trust"; homepage = "https://gitlab.com/sequoia-pgp/sequoia-wot"; <del> license = licenses.gpl2Only; maintainers = with maintainers; [ Cryolitia ]; </del> <ins> license = lib.licenses.gpl2Only; maintainers = with lib.maintainers; [ doronbehar Cryolitia ]; </ins> mainProgram = "sq-wot"; }; }

Discussion:
Steps to reproduce the behavior: Observed: Full checkPhase log (copied from Garnix): Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The checkPhase still fails with this PR applied, but it is a different error: Error: While creating /homeless- Caused by: Permission denied (os error 13)
Thanks for the report (I thought I rebuilt it successfully before I opened the PR). Now should be ready now (the failing test is skipped, and an upstream issue was created).
Change:
amarok = kde4.callPackage ../applications/audio/amarok { ffmpeg = ffmpeg_2; <ins> stdenv = overrideCC stdenv gcc5; </ins> }; AMB-plugins = callPackage ../applications/audio/AMB-plugins { };

Discussion:
I can't seem to make Amarok play any music. The initial symptom was that printed: ... the play controls looked to be drawn incompletely (only a play button, no skip fwd/back, etc.), and the phonon settings dialog was completely empty. After some digging, I hit upon the distinction between and . Only the latter was set in my environment, because I'm using kde5 and its nix expression (at ) only sets that. However, amarok looked to be wanting the former since it depends on gstreamer-0.10: So I this to (cribbed from ): and to . This instead yielded a crash in . Adding didn't help. Flailing some more, I ; that turned the crash into a hang: the amarok window appears but does not draw completely. At this point I think that the problem is that depends on gstreamer 1.x, while amarok depends on gstreamer 0.x. I tried tweaking the former to use instead of , but that produced a build failure: It doesn't look easily possible to build amarok against , since its dependency comes indirectly via . I'm hoping for some help from whose name is all over the relevant git logs. :) System: (based on @ ) Nix version: Nixpkgs version:
I am not a amarok user but I see same issue here, actually not anything but the interface appears to be working.
There is another fix needed to make the collection work with MySQL / MariaDB:
Just an update on the current state: seems to be about the same as before. On current ( still prints: ... but the UI is responsive. With the and changes from the description reapplied, amarok still hangs on startup.
It looks like amarok has been removed in / . There is still amarok-kf5 (), but I haven't tested that. However, in the course of researching it, I discovered https://www.clementine-, which is in nixpkgs and after a bit of testing seems to do the main things I used amarok for. So, if others are running into this problem, I recommend trying clementine as a replacement.
(triage) If I understand correctly, the problem can no longer be experienced due to amarok being removed?
Yes, I think so; closing.
Change:
f="gradle-${v}-spec.nix" <del> if [ -f "$f" ] </del> <ins> if [[ -n "$1" && "$1" != "$v" ]] </ins> then <del> echo "$v SKIP" </del> <ins> echo "$v SKIP (nomatch)" continue elif [ "$1" == "" ] && [ -f "$f" ] then echo "$v SKIP (exists)" </ins> continue fi

Discussion:
Gradle 7.4 is out, see (I am one of the maintainers, this is a TODO.)
Change:
maintainers = with stdenv.lib.maintainers; [ jcumming ]; }; }

Discussion:
I could not access my USB digital camera as a non-root user, due to insufficient permissions. The file in popped up with user and group set to . I'm new to NixOS and I'm not sure of the best way to solve something like this. Below I'll document a workaround that I used in my that solved the problem, in case that's helpful to others. But if a NixOS option along with some facility in the package could solve it, that would be ideal. Plug camera into USB Ensure it shows up in Run At first it died with "unknown error", but if you do you see the "insufficient permissions" message. System: 16.09.1357. (Flounder) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: 16.09.1357. I these to my : where I copied the file .
Tagging the gphoto2 maintainer thanks.
you can graft a module, which does exactly the steps above to fix this in long term. I did something similar for adb:
I see, thanks. So there's to define the option, and it references which contains the rules, maintained separately from the packages in . I'll aim to put together something similar for gphoto2.
Change:
wg set ${name} private-key ${privKey} ${ optionalString (values.listenPort != null) " listen-port ${toString values.listenPort}"} <del> ${concatMapStringsSep "n" (peer: assert (peer.presharedKeyFile == null) || (peer.presharedKey == null); # at most one of the two must be set let psk = if peer.presharedKey != null then pkgs.writeText "wg-psk" peer.presharedKey else peer.presharedKeyFile; in "wg set ${name} peer ${peer.publicKey}" + optionalString (psk != null) " preshared-key ${psk}" + optionalString (peer.endpoint != null) " endpoint ${peer.endpoint}" + optionalString (peer.persistentKeepalive != null) " persistent-keepalive ${toString peer.persistentKeepalive}" + optionalString (peer.allowedIPs != []) " allowed-ips ${concatStringsSep "," peer.allowedIPs}" ) values.peers} </del> ip link set up dev ${name} <del> ${optionalString (values.allowedIPsAsRoutes != false) (concatStringsSep "n" (concatMap (peer: (map (allowedIP: "ip route replace ${allowedIP} dev ${name} table ${values.table}" ) peer.allowedIPs) ) values.peers))} </del> ${values.postSetup} '';

Discussion:
In there was an option introduced that indefinitely tries to restart the wireguard service until all peer hostnames are resolved. Instead it should use as introduced by instead. This feature will be available in the next snapshot release of wireguard. cc
Alright 0.0. has been released for the purpose of this disaster being fixed. care to cleanup the mess?
I fail to see what mess/disaster you're refering to.
Change:
amsn = throw "amsn has been removed due to being unmaintained."; # added 2020-12-09 antimicro = throw "antimicro has been removed as it was broken, see antimicroX instead."; # added 2020-08-06 arduino_core = arduino-core;  # added 2015-02-04 <ins> ardour_5 = throw "ardour_5 has been removed. see https://github.com/NixOS/nixpkgs/issues/139549"; # added 2021-09-28 </ins> arora = throw "arora has been removed."; # added 2020-09-09 asciidocFull = asciidoc-full;  # added 2014-06-22 asterisk_15 = throw "asterisk_15: Asterisk 15 is end of life and has been removed."; # added 2020-10-07

Discussion:
fails to build as There is an invasive change that fixed it in newer version: . But maybe it's a good time to remove old version? Maintainer information:
Started with commit
Is there a reason to still keep Ardour 5.x in nixpkgs? Edit: The reads: Is that still the case ?
Yes it is, but I'm not sure it's worth the effort to fix Ardour 5.
I prepared a PR which drops ardour_5 if we decide to go this way:
Change:
dpkg -x $src $out cp -av $out/opt/ocenaudio/* $out rm -rf $out/opt <ins> mv $out/usr/share $out/share rm -rf $out/usr substituteInPlace $out/share/applications/ocenaudio.desktop  --replace "/opt/ocenaudio/bin/ocenaudio" "ocenaudio" mkdir -p $out/share/licenses/ocenaudio mv $out/bin/ocenaudio_license.txt $out/share/licenses/ocenaudio/LICENSE </ins> # Create symlink bzip2 library ln -s ${bzip2.out}/lib/libbz2.so.1 $out/lib/libbz2.so.1.0

Discussion:
Issue: Installing Ocenaudio creates no entry in the apps menu. But I am still able to start Ocenaudio from the console. I'm using the latest NixOS 11.23 and Gnome.
Change:
src = fetchFromGitHub { owner = "fcitx"; <del> repo = pname; </del> <ins> repo = "fcitx5-qt"; </ins> rev = version; sha256 = "sha256-bVH2US/uEZGERslnAh/fyUbzR9fK1UfG4J+mOmrIE8Y="; };

Discussion:
fcitx5-qt from libsForQt5 tries to download a nonsensical package from a non-existent repository Steps to reproduce the behavior: try to install/update libsForQt5.fcitx5-qt this workaround works. are you in control of those repositories and planning to update them to actually match what is in nixpkgs ? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The issue is me wrongfully using in place of , would fix soon.