jiebi/CodeConvo huggingface dataset:
Code change:
Describe the bug Just lost on two different NixOS machine my Signal Desktop history because of this faulty update... I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss To Reproduce Steps to reproduce the behavior: Signal Desktop Signal Desktop you to delete db, if you interact in a wrong way it will delete your data Notify maintainers ( and
Sorry to hear that. I recently lost my history too... It's really frustrating! Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers). AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in ). Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough. (I raged a bit here but after I realized that one cannot even import old backups I had to take a break.)
I just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database). After many things, the easiest fix to ensure proper functionalities IMHO is installing: This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess. That might not fix everything though :upsidedownface: Opened a PR:
FYI, in case anyone has feedback/suggestions: We might merge soon and it should cause another "Database startup error: Error: SQLITE_NOTADB: file is not a database" error (which is really unfortunate but not easily avoidable).
Heads-up: I've just merged to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup first in case the script fails unexpectedly.
Thank you, I just upgraded Signal on my computer and the re-encryption did work as intended

Related discussion:
text: # Symlink to bin mkdir -p $out/bin <del> ln -s $out/lib/Signal/signal-desktop $out/bin/signal-desktop </del> <ins> ln -s $out/lib/Signal/signal-desktop $out/bin/signal-desktop-unwrapped </ins> runHook postInstall ''; <ins> # Required for $SQLCIPHER_LIB which contains "/build/" inside the path: noAuditTmpdir = true; </ins> preFixup = '' <ins> export SQLCIPHER_LIB="$out/lib/Signal/resources/app.asar.unpacked/node_modules/better-sqlite3/build/Release/better_sqlite3.node" test -x "$SQLCIPHER_LIB" # To ensure the location hasn't changed </ins> gappsWrapperArgs+=( --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ stdenv.cc.cc ] }" <ins> --prefix LD_PRELOAD : "$SQLCIPHER_LIB" </ins> ${customLanguageWrapperArgs} )
Code change:
Describe the bug Just lost on two different NixOS machine my Signal Desktop history because of this faulty update... I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss To Reproduce Steps to reproduce the behavior: Signal Desktop Signal Desktop you to delete db, if you interact in a wrong way it will delete your data Notify maintainers ( and
Sorry to hear that. I recently lost my history too... It's really frustrating! Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers). AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in ). Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough. (I raged a bit here but after I realized that one cannot even import old backups I had to take a break.)
I just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database). After many things, the easiest fix to ensure proper functionalities IMHO is installing: This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess. That might not fix everything though :upsidedownface: Opened a PR:
FYI, in case anyone has feedback/suggestions: We might merge soon and it should cause another "Database startup error: Error: SQLITE_NOTADB: file is not a database" error (which is really unfortunate but not easily avoidable).
Heads-up: I've just merged to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup first in case the script fails unexpectedly.
Thank you, I just upgraded Signal on my computer and the re-encryption did work as intended

Related discussion:
text: patchelf --add-needed ${libpulseaudio}/lib/libpulse.so $out/lib/Signal/resources/app.asar.unpacked/node_modules/ringrtc/build/linux/libringrtc.node ''; <ins> postFixup = '' # This hack is temporarily required to avoid data-loss for users: cp ${./db-reencryption-wrapper.py} $out/bin/signal-desktop substituteInPlace $out/bin/signal-desktop  --replace '@PYTHON@' '${python3}/bin/python3'  --replace '@ZENITY@' '${gnome.zenity}/bin/zenity'  --replace '@SQLCIPHER@' '${sqlcipher}/bin/sqlcipher'  --replace '@SIGNAL-DESKTOP@' "$out/bin/signal-desktop-unwrapped" ''; </ins> # Tests if the application launches and waits for "Link your phone to Signal Desktop": passthru.tests.application-launch = nixosTests.signal-desktop;
Code change:
Carry over discussion from IRC #nixos-dev and . Inspired by the doc change in recommending top-level usage of over , we want to reduce confusion for newcomers and unnecessary complexity by making the canonical way to access the Nix library. We may still want to keep to not break external code, and place a or similar at its definition site. There are over files where occurs at least once. Beyond splitting this change across multiple PRs, in what ways can the change be automated? Pinging
In the short term, we could add this check in ofbrorg and , and update any examples in the documentation to reduce new usage of .
Don't forget things like and .
Ah. So 45K occurrences across 11.8K files.
toplevel is done
the xorg dep generator also doesn’t put it in its output anymore
trewide rewrite in
doc changes in
Graph of occurrences over time:
Nice! What scripts did you use to generate it?
There's a source code link now :)
Found another large source of s. Fixing cabal2nix should remove around 24k occurrences in .
Status report
Just found out that counts stuff like as well, so
Is it ok to rewrite to ?
That's the lib output of , so no.
an easy way to find out is to evaluate both in
Subfolders of with <10 changes needed in PR
Around + replacements out of 30k+ are concentrated in - should be trivial to regenerate the file with the new desired contents.
I'm working on it but it's a bit more complicated than I anticipated.
What problems are you running into?
Part of code generation of cabal2nix is in an external dependency, so I had to open two PRs. The dependency is itself on Hackage, so we may have to wait until the change propagates to Stackage LTS and then Nixpkgs, unless peti will use an override or something: I'm not familiar with the cabal2nix workflow.
I think the haskell-updates are mostly done from a local checkout of cabal2nix, so it depends mostly on what version peter is using. You can also probably just ask him, he is generally available for such things on his .
could you help here?
The Haskell infrastructure has switched to the new style with commit . It will land in this Friday. I have also updated the generator code and released new versions to Hackage, so I guess the Haskell infrastructure can be considered done.
Thank you
More accurate regex: (the one above captures stuff like
When is merged, this will be the result Three Nix files remain that use directly.
The last usages of it can be found by commenting out where it is inherited in .
I just got this warning while doing a , but it doesn't give me any info as to which derivations are at fault. Is there any way we could improve the message to identify culprits?
With , you should get a hard error which will allow you to use . Or you can update Nixpkgs, since it has been removed in

Related discussion:
text: <del> { stdenv </del> <ins> { lib , stdenv </ins> , rustPlatform , fetchFromGitHub , nix-update-script
Code change:
Carry over discussion from IRC #nixos-dev and . Inspired by the doc change in recommending top-level usage of over , we want to reduce confusion for newcomers and unnecessary complexity by making the canonical way to access the Nix library. We may still want to keep to not break external code, and place a or similar at its definition site. There are over files where occurs at least once. Beyond splitting this change across multiple PRs, in what ways can the change be automated? Pinging
In the short term, we could add this check in ofbrorg and , and update any examples in the documentation to reduce new usage of .
Don't forget things like and .
Ah. So 45K occurrences across 11.8K files.
toplevel is done
the xorg dep generator also doesn’t put it in its output anymore
trewide rewrite in
doc changes in
Graph of occurrences over time:
Nice! What scripts did you use to generate it?
There's a source code link now :)
Found another large source of s. Fixing cabal2nix should remove around 24k occurrences in .
Status report
Just found out that counts stuff like as well, so
Is it ok to rewrite to ?
That's the lib output of , so no.
an easy way to find out is to evaluate both in
Subfolders of with <10 changes needed in PR
Around + replacements out of 30k+ are concentrated in - should be trivial to regenerate the file with the new desired contents.
I'm working on it but it's a bit more complicated than I anticipated.
What problems are you running into?
Part of code generation of cabal2nix is in an external dependency, so I had to open two PRs. The dependency is itself on Hackage, so we may have to wait until the change propagates to Stackage LTS and then Nixpkgs, unless peti will use an override or something: I'm not familiar with the cabal2nix workflow.
I think the haskell-updates are mostly done from a local checkout of cabal2nix, so it depends mostly on what version peter is using. You can also probably just ask him, he is generally available for such things on his .
could you help here?
The Haskell infrastructure has switched to the new style with commit . It will land in this Friday. I have also updated the generator code and released new versions to Hackage, so I guess the Haskell infrastructure can be considered done.
Thank you
More accurate regex: (the one above captures stuff like
When is merged, this will be the result Three Nix files remain that use directly.
The last usages of it can be found by commenting out where it is inherited in .
I just got this warning while doing a , but it doesn't give me any info as to which derivations are at fault. Is there any way we could improve the message to identify culprits?
With , you should get a hard error which will allow you to use . Or you can update Nixpkgs, since it has been removed in

Related discussion:
text: <del> { stdenv </del> <ins> { lib , stdenv </ins> , autoPatchelfHook , fetchurl , file
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: <del> { lib, stdenv, fetchurl, makeWrapper, jre , version ? "1.6" }: let versionMap = { "1.5" = { flinkVersion = "1.5.5"; sha256 = "18wqcqi3gyqd40nspih99gq7ylfs20b35f4dcrspffagwkfp2l4z"; }; "1.6" = { flinkVersion = "1.11.1"; sha256 = "0338bg2sb427c1rrf2cmsz63sz0yk6gclpli2lskq0mpx72wxpl0"; }; }; in with versionMap.${version}; </del> <ins> { lib, stdenv, fetchurl, makeWrapper, jre }: </ins> stdenv.mkDerivation rec { <del> name = "flink-${flinkVersion}"; </del> <ins> pname = "flink"; version = "1.12.1"; </ins> src = fetchurl { <del> url = "mirror://apache/flink/${name}/${name}-bin-scala_2.11.tgz"; inherit sha256; </del> <ins> url = "mirror://apache/flink/${pname}-${version}/${pname}-${version}-bin-scala_2.11.tgz"; sha256 = "146azc5wg1xby3nqz8mha959qy99z2h8032rfgs2mcl3d5rrsm2l"; </ins> }; nativeBuildInputs = [ makeWrapper ];
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: firestr = throw "firestr has been removed."; # added 2019-12-08 fish-foreign-env = throw "fish-foreign-env has been replaced with fishPlugins.foreign-env"; # added 2020-12-29, modified 2021-01-10 flameGraph = flamegraph; # added 2018-04-25 <ins> flink_1_5 = throw "flink_1_5 was removed, use flink instead"; # added 2021-01-25 </ins> flvtool2 = throw "flvtool2 has been removed."; # added 2020-11-03 foldingathome = fahclient; # added 2020-09-03 font-awesome-ttf = font-awesome; # 2018-02-25
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: fldigi = callPackage ../applications/radio/fldigi { }; flink = callPackage ../applications/networking/cluster/flink { }; <del> flink_1_5 = flink.override { version = "1.5"; }; </del> fllog = callPackage ../applications/radio/fllog { };
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) CVSSv3=7.5 (nixos-20.09, nixos-unstable) CVSSv3=5.3 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: .

Related discussion:
text: stdenv.mkDerivation rec { pname = "p11-kit"; <del> version = "0.23.21"; </del> <ins> version = "0.23.22"; </ins> src = fetchFromGitHub { owner = "p11-glue"; repo = pname; rev = version; <del> sha256 = "1w24brn8j3vwfp07p2hldw2ci06pk1cx1dvjk8jjxkccp20fk958"; </del> <ins> sha256 = "sha256-erWqElJr0iESNUk9EZiJRmSMYhns8GxuFLNw7mIIIWs="; </ins> }; outputs = [ "out" "dev"];
Code change:
, CVSSv3=5.3 (nixos-20.09) CVSSv3=5.3 (nixos-20.09) Scanned versions: nixos-20.09: . Cc Cc Cc Cc

Related discussion:
text: buildGoPackage rec { pname = "vault"; <del> version = "1.6.0"; </del> <ins> version = "1.6.1"; </ins> src = fetchFromGitHub { owner = "hashicorp"; repo = "vault"; rev = "v${version}"; <del> sha256 = "13fasdiijxy87m33wfyd8gylyz556i0bdd7xp706ip2fcckrmz7a"; </del> <ins> sha256 = "1pgyyl2zgnr3wy4k8c5xsk2s5dpl97xdfq67lpfss7fz1bij8x47"; </ins> }; goPackagePath = "github.com/hashicorp/vault";
Code change:
, CVSSv3=5.3 (nixos-20.09) CVSSv3=5.3 (nixos-20.09) Scanned versions: nixos-20.09: . Cc Cc Cc Cc

Related discussion:
text: { stdenv, fetchurl, unzip }: let <del> version = "1.6.0"; </del> <ins> version = "1.6.1"; </ins> sources = let base = "https://releases.hashicorp.com/vault/${version}"; in { x86_64-linux = fetchurl { url = "${base}/vault_${version}_linux_amd64.zip"; <del> sha256 = "0fay6bw31x9kxmc52sh5qp63nfkwji74fbnlx8pj3smz3qnqw143"; </del> <ins> sha256 = "1la2pylcj9y5gr7hr4aaa49427y3lgxi2phhl46pqmr7an62pkbm"; </ins> }; i686-linux = fetchurl { url = "${base}/vault_${version}_linux_386.zip"; <del> sha256 = "0bjks9lpgl39cq55c9cyc0glhmyxzs37a2an8ynzza94gv5mgcxa"; </del> <ins> sha256 = "1a2rhv5bpv43qp74a49msrwr7djzy86irsn73jl0xnkh0k6ijci1"; </ins> }; x86_64-darwin = fetchurl { url = "${base}/vault_${version}_darwin_amd64.zip"; <del> sha256 = "0hl1k35x78y0hi3y5xjnzby1ygisqjyvdak7s61m9f363nsr1shh"; </del> <ins> sha256 = "0snswwai2ya26crm3ksifrmbdnajr36v4vamh7g65plg6vzban9a"; </ins> }; aarch64-linux = fetchurl { url = "${base}/vault_${version}_linux_arm64.zip"; <del> sha256 = "018a5i14x6phhx1axvx0bvqn4ggsimfizs48xbmykgiyfmzkrwgz"; </del> <ins> sha256 = "0ix99da3xd4z200dgvpfc2h1sfx6l8cipichvfjlj39md45grs89"; </ins> }; };
Code change:
, CVSSv3=5.3 (nixos-20.09) CVSSv3=5.3 (nixos-20.09) Scanned versions: nixos-20.09: . Cc Cc Cc Cc

Related discussion:
text: description = "A tool for managing secrets, this binary includes the UI"; platforms = [ "x86_64-linux" "i686-linux" "x86_64-darwin" "aarch64-linux" ]; license = licenses.mpl20; <del> maintainers = with maintainers; [ offline psyanticy mkaito ]; </del> <ins> maintainers = with maintainers; [ offline psyanticy mkaito Chili-Man ]; </ins> }; }
Code change:
, CVSSv3=6.1 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: <del> { stdenv, fetchurl, libiconv }: </del> <ins> { lib, stdenv, fetchFromGitHub, autoreconfHook, libiconv }: </ins> stdenv.mkDerivation rec { pname = "wavpack"; <del> version = "5.3.0"; </del> <ins> version = "5.4.0"; </ins> enableParallelBuilding = true; <ins> nativeBuildInputs = [ autoreconfHook ]; </ins> buildInputs = stdenv.lib.optional stdenv.isDarwin libiconv; <del> src = fetchurl { url = "http://www.wavpack.com/${pname}-${version}.tar.bz2"; sha256 = "00baiag7rlkzc6545dqdp4p5sr7xc3n97n7qdkgx58c544x0pw5n"; </del> <ins> src = fetchFromGitHub { owner = "dbry"; repo = "WavPack"; rev = version; sha256 = "1b6szk2vmnqnv5w7h8yc1iazjlidlraq1lwjbmc3fi0snbn6qj44"; </ins> }; <del> meta = with stdenv.lib; { </del> <ins> meta = with lib; { </ins> description = "Hybrid audio compression format"; <del> homepage    = "http://www.wavpack.com/"; </del> <ins> homepage    = "https://www.wavpack.com/"; changelog   = "https://github.com/dbry/WavPack/releases/tag/${version}"; </ins> license     = licenses.bsd3; platforms   = platforms.unix; maintainers = with maintainers; [ codyopel ];
Code change:
Describe the bug I believe the source for the package might no longer be valid: Accessing it in the browser shows a 404, and the home page -- -- appears to just be a portal for serving sponsored links. The Wayback Machine shows that the has not been archived since February 2020, and also get the same 404. There was a in Septermber 2020, but I'm unsure if this was the cause. Thanks! To Reproduce Steps to reproduce the behavior: . Expected behavior Installation should not hang, and the font should be installed. Screenshots Additional context appears to be an alternative to Helvetica, so I'm unsure how important this package is. But I figured this error should be documented. As far as I can tell, is the only package using , so if this domain is indeed no longer usable then nothing else should be impacted. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
but the link is also dead: so i would ask there where the font is available and if it is freely licensed now. it was also licensed by adobe at some point it seem to ba available from several shady websites, like but that's clearly illegal and shouldn't be packaged in nixpkgs freely licensed alternatives are: (Nimbus Sans)
I marked this as stale due to inactivity. &rarr;
Could the helvetica-neue-lt-std package be removed or at least generate a better error than a 404 when it tries to download the font? I ran into this error while doing a nixos-install so it took a while to find the specific package that was causing my build to fail.
Thank you

Related discussion:
text: { lib, fetchzip }: let <del> version = "2013.06.07"; # date of most recent file in distribution </del> <ins> version = "2014.08.16"; # date of most recent file in distribution </ins> in fetchzip { name = "helvetica-neue-lt-std-${version}"; <del> url = "http://www.ephifonts.com/downloads/helvetica-neue-lt-std.zip"; </del> <ins> url = "https://web.archive.org/web/20190823153624/http://ephifonts.com/downloads/helvetica-neue-lt-std.zip"; </ins> postFetch = '' mkdir -p $out/share/fonts <del> unzip -j $downloadedFile Helvetica Neue LT Std/*.otf -d $out/share/fonts/opentype </del> <ins> unzip -j $downloadedFile "Helvetica Neue LT Std/*.otf" -d $out/share/fonts/opentype </ins> ''; sha256 = "0ampp9vf9xw0sdppl4lb9i9h75ywljhdcqmzh45mx2x9m7h6xgg9"; <del> meta = { homepage = "http://www.ephifonts.com/free-helvetica-font-helvetica-neue-lt-std.html"; </del> <ins> meta = with lib; { homepage = "https://web.archive.org/web/20190926040940/http://www.ephifonts.com/free-helvetica-font-helvetica-neue-lt-std.html"; </ins> description = "Helvetica Neue LT Std font"; longDescription = '' Helvetica Neue Lt Std is one of the most highly rated and complete
Code change:
Describe the bug I believe the source for the package might no longer be valid: Accessing it in the browser shows a 404, and the home page -- -- appears to just be a portal for serving sponsored links. The Wayback Machine shows that the has not been archived since February 2020, and also get the same 404. There was a in Septermber 2020, but I'm unsure if this was the cause. Thanks! To Reproduce Steps to reproduce the behavior: . Expected behavior Installation should not hang, and the font should be installed. Screenshots Additional context appears to be an alternative to Helvetica, so I'm unsure how important this package is. But I figured this error should be documented. As far as I can tell, is the only package using , so if this domain is indeed no longer usable then nothing else should be impacted. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
but the link is also dead: so i would ask there where the font is available and if it is freely licensed now. it was also licensed by adobe at some point it seem to ba available from several shady websites, like but that's clearly illegal and shouldn't be packaged in nixpkgs freely licensed alternatives are: (Nimbus Sans)
I marked this as stale due to inactivity. &rarr;
Could the helvetica-neue-lt-std package be removed or at least generate a better error than a 404 when it tries to download the font? I ran into this error while doing a nixos-install so it took a while to find the specific package that was causing my build to fail.
Thank you

Related discussion:
text: font. The numbers are well spaced and defined with high accuracy. The punctuation marks are heavily detailed as well. ''; <del> license = lib.licenses.unfree; maintainers = [ lib.maintainers.romildo ]; platforms = lib.platforms.all; </del> <ins> license = licenses.unfree; platforms = platforms.all; maintainers = with maintainers; [ romildo ]; </ins> }; }
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: radvd <!-- 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: 2.18 desired version: 2.19 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.

Related discussion:
text: stdenv.mkDerivation rec { pname = "radvd"; <del> version = "2.18"; </del> <ins> version = "2.19"; </ins> src = fetchurl { url = "http://www.litech.org/radvd/dist/${pname}-${version}.tar.xz"; <del> sha256 = "1p2wlv3djvla0r84hdncc3wfa530xigs7z9ssc2v5r1pcpzgxgz1"; </del> <ins> sha256 = "0h722f17h7cra1sjgrxhrrvx54mm47fs039909yhbabigxch8kjn"; </ins> }; nativeBuildInputs = [ pkg-config bison flex check ];
Code change:
Describe the bug dmd keeps references to boostrap compiler. To Reproduce Steps to reproduce the behavior: Expected behavior dmd has no references to boostrap compiler Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(symphorien): nixpkgs: Maintainer information: Note: to prevent future regressions, it would be nice to add to the derivation ()
I marked this as stale due to inactivity. &rarr;
Still an issue
I marked this as stale due to inactivity. &rarr;

Related discussion:
text: { stdenv , lib , fetchFromGitHub <ins> , removeReferencesTo </ins> , makeWrapper , which , writeTextFile