jiebi/CodeConvo huggingface dataset:
Code change:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.

Related discussion:
text: }); let snapshotHash = if stdenv.system == "i686-linux" <del> then "g2h9l35123r72hqdwayd9h79kspfb4y9" </del> <ins> then "7e2f9c82e1af5aa43ef3ee2692b985a5f2398f0a" </ins> else if stdenv.system == "x86_64-linux" <del> then "fnx2rf1j8zvrplcc7xzf89czn0hf3397" </del> <ins> then "4c03a3fd2474133c7ad6d8bb5f6af9915ca5292a" </ins> else if stdenv.system == "i686-darwin" <del> then "3viz3fi2jx18qjwrc90nfhm9cik59my6" </del> <ins> then "4d84d31449a5926f9e7ceb344540d6e5ea530b88" </ins> else if stdenv.system == "x86_64-darwin" <del> then "h2bf3db4vwz5cjjkn98lxayivdc6dflp" </del> <ins> then "f8baef5b0b3e6f9825be1f1709594695ac0f0abc" </ins> else throw "no snapshot for platform ${stdenv.system}"; snapshotName = "cargo-nightly-${platform}.tar.gz"; in
Code change:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.

Related discussion:
text: with rustPlatform; buildRustPackage rec { <del> name = "rustfmt-git-2016-02-15"; </del> <ins> name = "rustfmt-${version}"; version = "2016-03-22"; </ins> src = fetchFromGitHub { owner = "rust-lang-nursery"; repo = "rustfmt"; <del> rev = "65bc5c242de86f0651b34fd913ca338a880696e8"; sha256 = "02rdim0y5zg1r2zkfy6kj53idlbdybf3ckardbjsvdna5idc1hpz"; </del> <ins> rev = "ca757183fedf8e89286372b91ca074c11d99c4f4"; sha256 = "0ngg5m002hwwmsqy9wr50dj3l3zgwk39701wzszm3nrhz6x13dmj"; </ins> }; <del> depsSha256 = "1297vy5sgiq4xqdm27pa8f99qiwrl15hb2r1dydzgk7n4iqyir6c"; </del> <ins> depsSha256 = "0mg4z197iiwjlgqs5izacld25cr11qi3bcrqq204f0jzrnj3y8ag"; </ins> meta = with stdenv.lib; { description = "A tool for formatting Rust code according to style guidelines";
Code change:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.

Related discussion:
text: buildRustPackage rec { name = "exa-${version}"; <del> version = "2016-02-15"; </del> <ins> version = "2016-03-22"; </ins> <del> depsSha256 = "1925nhpfph82wn755zf2nmad24f1hzbxq60gpva9sic6rnap4c1x"; </del> <ins> depsSha256 = "18anwh235kzziq6z7md8f3rl2xl4l9d4ivsqw9grkb7yivd5j0jk"; </ins> src = fetchFromGitHub { owner = "ogham"; repo = "exa"; <del> rev = "252eba484476369bb966fb1af7f739732b968fc0"; sha256 = "1smyy32z44zgmhyhlbjaxcgfnlbcwz7am9225yppqfdsiqqgdybf"; </del> <ins> rev = "8805ce9e3bcd4b56f8811a686dd56c47202cdbab"; sha256 = "0dkvk0rsf068as6zcd01p7959rdjzm26mlkpid6z0j168gp4kh4q"; </ins> }; nativeBuildInputs = [ cmake ];
Code change:
To make sure that we are on the same page: Kernel: (run ) 4.5.0 System: (NixOS: , Ubuntu/Fedora: , ...) (Flounder) Nix version: (run ) 1.11.2 Nixpkgs version: (run ) During testing of I managed to get at least two different hashes for . After some discussion with it seems that this derivation can produce non-deterministic output. Hashes of outputs are always the same. They are not. Build several times.
How would one work around that? It basically means the system cannot be rebuild :cry:
cc
You can work around it by updating SHA checksum in the affected package locally.
:confused: Is there any documentation you could point me too. I know how I would to it for packages that I install as a user: out nixpkgs repo the last commit that build for unstable on hydra that out the exa's file 5 run But I think it's also possible to override it in a nix expression, like the one in , since I installed it as a systems package. The thing is that all ressources I find either explain how to do it for that they link to
I changed my to include that: but to no avail :confused:
Sadly we don't have a mechanism to override (it needs to be supported). However, you can rebuild your whole NixOS from a modified repository:
Another way to do it is to call patched nixpkgs from your :
Thanks for your help! I really appreciate it. I tried your last suggestions, but that leads to: It looks like some network hick up, but I tried it multiple times and I opened the github repository from the same machine and it loads fine. Maybe it has something to do with this line: ?
Hm, unfortunately I have no idea what's going on -- you've fixed the hash, so it seems like another problem in .
Still thanks for the help. I learned a lot!
depends on a git repository in which doesn't work with
maybe fetchcargo could take an argument to pin git-based dependencies on a certain commit?
I can confirm that this is still an issue when building : through AUR/exa-git. cc
Are there any updates on this issue, please?
Should be fixed.

Related discussion:
text: { runCommand, fetchFromGitHub, git }: let <del> version = "2016-03-10"; rev = "5e78a14c1b82522e019586687f7dbfd36ce67fa5"; </del> <ins> version = "2016-03-22"; rev = "f28cdedb698cf76f513fb4514b5ed2892ec89b2f"; </ins> src = fetchFromGitHub { inherit rev; owner = "rust-lang"; repo = "crates.io-index"; <del> sha256 = "0hzhfhlv8qbqb5nm9id36dlzvhalhlrh2k82ks67ap4mdcs3c650"; </del> <ins> sha256 = "05j43pgdlf554y9r781xdc5la55anwiq6k7vml9icak699ywfxqq"; </ins> }; in
Code change:
To reproduce: set to rebuild system with two users that don't have uid specified rebuild system by specifying uid of the first user to match the generated uid of the second user They will now share the uid. Expected behavior: error should be raised cc
this also happens if you force the uid for 1 user, and dont set the uid at all on another, i need to force the uid on every user to avoid collisions
your issue should be fixed in , I'm still verifying if my problem is covered :)
There might be some other edge cases, but now this issue yields:

Related discussion:
text: # TODO add plugins having various licenses, see http://www.vamp-plugins.org/download.html <del> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo, libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate, libsndfile, makeWrapper, pulseaudio, qt4, redland, rubberband, vampSDK </del> <ins> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo , libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate , libsndfile, makeWrapper, pkgconfig, pulseaudio, qt4, redland , rubberband, vampSDK </ins> }: <del> stdenv.mkDerivation { name = "sonic-visualiser-1.8"; </del> <ins> stdenv.mkDerivation rec { name = "sonic-visualiser-${version}"; version = "1.9"; </ins> src = fetchurl { <del> url = http://downloads.sourceforge.net/sv1/sonic-visualiser-1.8.tar.gz; sha256 = "16ik6q9n92wljvnqcv7hyzb9v3yp3ixxp6df9kasf53fii973dh7"; </del> <ins> url = "http://code.soundsoftware.ac.uk/attachments/download/194/${name}.tar.gz"; sha256 = "00igf7j6s8xfyxnlkbqma0yby9pknxqzy8cmh0aw95ix80cw56fq"; </ins> }; buildInputs = [ libsndfile qt4 fftw /* should be fftw3f ??*/ bzip2 librdf rubberband libsamplerate vampSDK alsaLib librdf_raptor librdf_rasqal redland <ins> pkgconfig </ins> # optional jackaudio # portaudio
Code change:
To reproduce: set to rebuild system with two users that don't have uid specified rebuild system by specifying uid of the first user to match the generated uid of the second user They will now share the uid. Expected behavior: error should be raised cc
this also happens if you force the uid for 1 user, and dont set the uid at all on another, i need to force the uid on every user to avoid collisions
your issue should be fixed in , I'm still verifying if my problem is covered :)
There might be some other edge cases, but now this issue yields:

Related discussion:
text: description = "View and analyse contents of music audio files"; homepage = http://www.sonicvisualiser.org/; license = "GPLv2"; <del> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </del> <ins> maintainers = [ stdenv.lib.maintainers.marcweber stdenv.lib.maintainers.goibhniu ]; </ins> platforms = stdenv.lib.platforms.linux; }; }
Code change:
RStudio () fails to build from nixpkgs master with a 404 on downloading sources. Steps to reproduce the behavior: <!-- 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. Maintainer information:

Related discussion:
text: src = fetchFromGitHub { owner = "rstudio"; repo = "rstudio"; <del> rev = version; </del> <ins> rev = "v${version}"; </ins> sha256 = "sha256-9c1bNsf8kJjpcZ2cMV/pPNtXQkFOntX29a1cdnXpllE="; };
Code change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: chirp (chirp-daily) <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: desired version: <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: None (!) - I can probably volunteer to keep this up to date? The last PR was submitted by though. Please tag this issue in your PR.

Related discussion:
text: }: python2.pkgs.buildPythonApplication rec { pname = "chirp-daily"; <del> version = "20210724"; </del> <ins> version = "20211016"; </ins> src = fetchurl { url = "https://trac.chirp.danplanet.com/chirp_daily/daily-${version}/${pname}-${version}.tar.gz"; <del> sha256 = "0wddzls7r0l5b8vvljnmrj5lmmp7zkzl4h73pyigyf9nbhaklybb"; </del> <ins> sha256 = "13xzqnhvnw6yipv4izkq0s9ykyl9pc5ifpr1ii8xfp28ch706qyw"; </ins> }; propagatedBuildInputs = with python2.pkgs; [
Code change:
A URL like generates the following error log: Steps to reproduce the behavior: to download a file that has been uploaded Should download the file Are you seeing this problem on your non-beta versions of Discourse? It looks like maybe the X-Accel-Mapping isn't applying and then the request to download a file is getting fed back into Rails.
I've confirmed this is also an issue on Discourse 2.7.5 for NixOS.
This can be fixed with: However, I think this is probably a bad fix as is, because you might be able to trick discourse into serving arbitrary files in the /nix store. Two possible solutions: Discourse so it serves files with paths like /run/discourse instead a much more specific location regex in nginx to mitigate the issue I noted above Do you have any other ideas?
This works and should be safer:
My hunch is that it's both safer and cleaner to patch Discourse. If I follow the code correctly, I believe this is what would need to be changed to just return : There is already a match in place in the nginx config, so nothing more should be necessary.
That's the same place I followed the code to, so that is probably correct. I'll look into patching it.

Related discussion:
text: # Make sure the notification email setting applies ./notification_email.patch <ins> # Change the path to the public directory reported by Discourse # to its real path instead of the symlink in the store, since # the store path won't be matched by any nginx rules ./public_dir_path.patch </ins> ]; postPatch = ''
Code change:
A URL like generates the following error log: Steps to reproduce the behavior: to download a file that has been uploaded Should download the file Are you seeing this problem on your non-beta versions of Discourse? It looks like maybe the X-Accel-Mapping isn't applying and then the request to download a file is getting fed back into Rails.
I've confirmed this is also an issue on Discourse 2.7.5 for NixOS.
This can be fixed with: However, I think this is probably a bad fix as is, because you might be able to trick discourse into serving arbitrary files in the /nix store. Two possible solutions: Discourse so it serves files with paths like /run/discourse instead a much more specific location regex in nginx to mitigate the issue I noted above Do you have any other ideas?
This works and should be safer:
My hunch is that it's both safer and cleaner to patch Discourse. If I follow the code correctly, I believe this is what would need to be changed to just return : There is already a match in place in the nginx config, so nothing more should be necessary.
That's the same place I followed the code to, so that is probably correct. I'll look into patching it.

Related discussion:
text: <ins> diff --git a/lib/file_store/local_store.rb b/lib/file_store/local_store.rb index 25649532c0..614e062dc1 100644 --- a/lib/file_store/local_store.rb +++ b/lib/file_store/local_store.rb @@ -88,7 +88,7 @@ module FileStore end def public_dir -      File.join(Rails.root, "public") +      "/run/discourse/public" end def tombstone_dir </ins>
Code change:
When trying to build the swift package, it inevitably fails at the same point in two of my machines. In particular, it seems to fail at the following point (): Steps to reproduce the behavior: the following a long time for it to ultimately fail with the above message. I expect the swift package to successfully build. I have not tried to build it using any other method than the way outlined in <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
It looks like swift is using a bundled llvm source tree, so we will have to apply the patch from
Out of curiosity do you know if there is a version of nixpkgs that contains a Swift package I could possibly build? Or is it somehow dependant on how my system is configured?
Certainly, that patch was only needed since bumping our userspace linux headers from 5.12 to 5.14, so I would expect any commit before that would work. According to Hydra, () was the most recent success.

Related discussion:
text: # LLVM toolchain patches. patch -p1 -d llvm-project/clang -i ${./patches/0005-clang-toolchain-dir.patch} patch -p1 -d llvm-project/clang -i ${./patches/0006-clang-purity.patch} <ins> patch -p1 -d llvm-project/compiler-rt -i ${../llvm/common/compiler-rt/libsanitizer-no-cyclades-11.patch} </ins> substituteInPlace llvm-project/clang/lib/Driver/ToolChains/Linux.cpp  --replace 'SysRoot + "/lib' '"${glibc}/lib" "'  --replace 'SysRoot + "/usr/lib' '"${glibc}/lib" "'
Code change:
To make sure that we are on the same page: Kernel: (run ) Linux lapole 3.18.25 -NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x8664 GNU/Linux System: (NixOS: , Ubuntu/Fedora: , ...) 15.09.952. (Dingo) Nix version: (run ) nix-env (Nix) 1.10 Nixpkgs version: (run ) 16.03pre75806. I installed zsh-5.2 from nixpkgs channel to get away from a 5.0.8 bug. After I changed my login-shell to 5.2, ssh logins were no longer functional. Ie. PATH wasn't fully initialized. Reverting to 5.0.8 fixed the problem. I'm not sure why there's a difference between regular login shells and ssh though. Running yields: For 5.0.8 I get the expected /nix/store/... path instead of the strange $out path. The line with $out seems wrong.. Checking the commit log I find Dropping into nix-shell for zsh-5.2, setting and manually running I get: So it seems to me that variables in is not expanded leading to zprofile not being run. It could be something else of course (not everything seems to add up without more investigating), but the $out thing seems wrong either way.
cc
This is fixed by the merge of . Cherry-picked to .

Related discussion:
text: buildInputs = [ ncurses pcre ]; <del> configureFlags = [ "--enable-maildir-support" "--enable-multibyte" "--enable-zprofile=$out/etc/zprofile" "--with-tcsetpgrp" "--enable-pcre" ]; </del> <ins> preConfigure = '' configureFlags="--enable-maildir-support --enable-multibyte --enable-zprofile=$out/etc/zprofile --with-tcsetpgrp --enable-pcre" ''; </ins> # the zsh/zpty module is not available on hydra # so skip groups Y Z
Code change:
To make sure that we are on the same page: Kernel: (run ) Linux lapole 3.18.25 -NixOS SMP Thu Jan 1 00:00:01 UTC 1970 x8664 GNU/Linux System: (NixOS: , Ubuntu/Fedora: , ...) 15.09.952. (Dingo) Nix version: (run ) nix-env (Nix) 1.10 Nixpkgs version: (run ) 16.03pre75806. I installed zsh-5.2 from nixpkgs channel to get away from a 5.0.8 bug. After I changed my login-shell to 5.2, ssh logins were no longer functional. Ie. PATH wasn't fully initialized. Reverting to 5.0.8 fixed the problem. I'm not sure why there's a difference between regular login shells and ssh though. Running yields: For 5.0.8 I get the expected /nix/store/... path instead of the strange $out path. The line with $out seems wrong.. Checking the commit log I find Dropping into nix-shell for zsh-5.2, setting and manually running I get: So it seems to me that variables in is not expanded leading to zprofile not being run. It could be something else of course (not everything seems to add up without more investigating), but the $out thing seems wrong either way.
cc
This is fixed by the merge of . Cherry-picked to .

Related discussion:
text: # TODO add plugins having various licenses, see http://www.vamp-plugins.org/download.html <del> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo, libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate, libsndfile, makeWrapper, pulseaudio, qt4, redland, rubberband, vampSDK </del> <ins> { stdenv, fetchurl, alsaLib, bzip2, fftw, jackaudio, libX11, liblo , libmad, libogg, librdf, librdf_raptor, librdf_rasqal, libsamplerate , libsndfile, makeWrapper, pkgconfig, pulseaudio, qt4, redland , rubberband, vampSDK </ins> }: <del> stdenv.mkDerivation { name = "sonic-visualiser-1.8"; </del> <ins> stdenv.mkDerivation rec { name = "sonic-visualiser-${version}"; version = "1.9"; </ins> src = fetchurl { <del> url = http://downloads.sourceforge.net/sv1/sonic-visualiser-1.8.tar.gz; sha256 = "16ik6q9n92wljvnqcv7hyzb9v3yp3ixxp6df9kasf53fii973dh7"; </del> <ins> url = "http://code.soundsoftware.ac.uk/attachments/download/194/${name}.tar.gz"; sha256 = "00igf7j6s8xfyxnlkbqma0yby9pknxqzy8cmh0aw95ix80cw56fq"; </ins> }; buildInputs = [ libsndfile qt4 fftw /* should be fftw3f ??*/ bzip2 librdf rubberband libsamplerate vampSDK alsaLib librdf_raptor librdf_rasqal redland <ins> pkgconfig </ins> # optional jackaudio # portaudio