jiebi/CodeConvo huggingface dataset:
Change:
<del> { lib, fetchFromGitHub, python3, makeDesktopItem, copyDesktopItems }: </del> <ins> { lib, fetchFromGitHub, python3, tk, makeDesktopItem, copyDesktopItems }: </ins> with python3.pkgs;

Discussion:
fails to launch due to tkinter error, Steps to reproduce the behavior: the current unstable channel. "Thonny" fails. Thonny launching and not crashing. I tried building with python38 (fails due to Mathplotlib version) and python39 (same issue). <!-- 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.
Change:
<ins> { lib , stdenv , fetchzip }: stdenv.mkDerivation (finalAttrs: { pname = "unrar"; version = "7.0.7"; src = fetchzip { url = "https://www.rarlab.com/rar/unrarsrc-${finalAttrs.version}.tar.gz"; stripRoot = false; hash = "sha256-S7BMywydetDh1GINcK3k3fN9ciDoKTCAe/1tkgykoAQ="; }; sourceRoot = finalAttrs.src.name; postPatch = '' substituteInPlace unrar/makefile  --replace "CXX=" "#CXX="  --replace "STRIP=" "#STRIP="  --replace "AR=" "#AR=" ''; outputs = [ "out" "dev" ]; # `make {unrar,lib}` call `make clean` implicitly # separate build into different dirs to avoid deleting them buildPhase = '' runHook preBuild cp -a unrar libunrar make -C libunrar lib make -C unrar -j1 runHook postBuild ''; installPhase = '' runHook preInstall install -Dm755 unrar/unrar -t $out/bin/ install -Dm644 unrar/{acknow.txt,license.txt} -t $out/share/doc/unrar/ install -Dm755 libunrar/libunrar.so -t $out/lib/ install -Dm644 libunrar/dll.hpp -t $dev/include/unrar/ runHook postInstall ''; setupHook = ./setup-hook.sh; meta = with lib; { description = "Utility for RAR archives"; homepage = "https://www.rarlab.com/"; license = licenses.unfreeRedistributable; mainProgram = "unrar"; maintainers = with maintainers; [ wegank ]; platforms = platforms.all; }; }) </ins>

Discussion:
Package name: unrar Latest released version: 7.00 beta 3 Current version on the unstable channel: 6.2.12 Current version on the stable/release channel: 6.2.12 I receive more and more RAR files which are created with Unrar 7.00 beta versions / require a more recent version tan 6.2.12 I would appreciated if the existing unrar package can be updated or a new unrar-beta package be proposed .. Changelog : Notify maintainers
There was an automatic update in that I marked as draft, exactly because it's in beta. I'd much rather add a new package. what do you think?
I don't think we should update to the beta either. Sometimes I think about adding beta and release candidate versions to package , but that would be a nixpkgs policy discussion.
If people are still creating new RAR files then I don't want to be maintainer of this package. Stop using RAR.
Change:
fast-neural-doodle = throw "fast-neural-doodle has been removed, as the upstream project has been abandoned"; # Added 2020-03-28 fastnlo = fastnlo_toolkit; # Added 2021-04-24 fedora-coreos-config-transpiler = throw "fedora-coreos-config-transpiler has been renamed to 'butane'"; # Added 2021-04-13 <ins> feedreader = throw "feedreader is no longer activily maintained since 2019. The developer is working on a spiritual successor called NewsFlash."; # Added 2022-05-03 </ins> fetchFromGithub = throw "You meant fetchFromGitHub, with a capital H"; ffadoFull = throw "'ffadoFull' has been renamed to/replaced by 'ffado'"; # Converted to throw 2022-02-22 ffmpeg-sixel = throw "ffmpeg-sixel has been removed, because it was an outdated/unmaintained fork of ffmpeg"; # Added 2022-03-23";

Discussion:
This project is no longer activily maintained! there is a spiritual successor, so maybe package that instead cc maintainer
I marked this as stale due to inactivity. &rarr;
Change:
nvim-colorizer-lua = buildVimPluginFrom2Nix { pname = "nvim-colorizer.lua"; <del> version = "2020-06-11"; </del> <ins> version = "2022-09-10"; </ins> src = fetchFromGitHub { <del> owner = "norcalli"; </del> <ins> owner = "nvchad"; </ins> repo = "nvim-colorizer.lua"; <del> rev = "36c610a9717cc9ec426a07c8e6bf3b3abcb139d6"; sha256 = "0gvqdfkqf6k9q46r0vcc3nqa6w45gsvp8j4kya1bvi24vhifg2p9"; </del> <ins> rev = "2664070cd04f2b9f803a10dd328a562be8ab15ca"; sha256 = "16myjv2hrqr2kk14mqidyrhdnz1i3p00yf0w97f4kxrdd158p1nz"; </ins> }; <del> meta.homepage = "https://github.com/norcalli/nvim-colorizer.lua/"; </del> <ins> meta.homepage = "https://github.com/nvchad/nvim-colorizer.lua/"; </ins> }; nvim-comment = buildVimPluginFrom2Nix {

Discussion:
<!-- 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 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: <!-- The current version can be found easily with the same process as 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: 2020-6-11 desired version: Latest on <!-- 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.
Change:
license = licenses.gpl2Plus; maintainers = with maintainers; [ jonafato turion ]; platforms = platforms.linux ++ platforms.darwin; <ins> broken = stdenv.isDarwin;  # see to https://github.com/NixOS/nixpkgs/issues/172165 </ins> }; }

Discussion:
<!-- 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 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: keepassxc <!-- The current version can be found easily with the same process as 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.6.6 desired version: 2.7.0 <!-- 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.
There's a PR now:
Thanks for the information
Change:
DEBUG_SG              = yes; SCHED_STACK_END_CHECK = yes; <del> REFCOUNT_FULL = whenOlder "5.5" yes; </del> <ins> REFCOUNT_FULL = whenOlder "5.4.208" yes; </ins> # Randomize page allocator when page_alloc.shuffle=1 SHUFFLE_PAGE_ALLOCATOR = whenAtLeast "5.2" yes;

Discussion:
Steps to reproduce the behavior: linuxKernel.kernels.linux54hardened (with ) This causes many failure in Hydra (one per module). The non-hardened version works fine. Other kernel versions work fine. (for previous ZHF discussion) ZHF: Please run and paste the result.
This is linked with commit (Feb 21 23:41:34 2023): "use , not assert"
linuxKernel.kernels.linux54_hardened was introduced in and seems to build fine at this commit. I am going to from this point.
The commit breaking linuxKernel.kernels.linux54_hardened is (found via bisect).
Could this be the same as ? Since the build failure is actually in , not the actual kernel build.
I confirm that the build failure is linuxKernel.kernels.linux54hardened.configfile. It seems that specifies that uses gcc10: but adding in outputs . There is definitely something off in these Nix expressions. I don't understand why the derivation sees gcc12 rather than gcc10.
: It looks like there is another definition here which doesn't override the stdenv: But since the failures are happening in the kernel package-set, I don't believe the kernel with the missing stdenv is related.
Change:
stdenv.mkDerivation (finalAttrs: { pname = "vym"; <del> version = "2.8.42"; </del> <ins> version = "2.9.26"; </ins> src = fetchFromGitHub { owner = "insilmaril"; repo = "vym"; <del> rev = "89f50bcba953c410caf459b0a4bfbd09018010b7"; # not tagged yet (why??) hash = "sha256-xMXvc8gt3nfKWbU+WoS24wCUTGDQRhG0Q9m7yDhY5/w="; </del> <ins> rev = "v${finalAttrs.version}"; hash = "sha256-5cHhv9GDjJvSqGJ+7fI0xaWCiXw/0WP0Bem/ZRV8Y7M="; </ins> }; <ins> outputs = [ "out" "man" ]; </ins> patches = [ (substituteAll { src = ./000-fix-zip-paths.diff;

Discussion:
Package name: vym Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 2.8.42 Current version on the stable/release channel: 2.8.42 <!-- 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]:
Change:
<ins> { lib , stdenv , fetchFromGitHub , meson , ninja , pkg-config , ncurses }: stdenv.mkDerivation rec { pname = "rmw"; version = "0.9.0"; src = fetchFromGitHub { owner = "theimpossibleastronaut"; repo = "rmw"; rev = "v${version}"; hash = "sha256-KOYj63j/vCG7I63bgep03HzufOj/p/EHaY8lyRMHCkY="; fetchSubmodules = true; }; nativeBuildInputs = [ pkg-config meson ninja ]; buildInputs = [ ncurses ]; meta = with lib; { description = "Trashcan/ recycle bin utility for the command line"; homepage = "https://github.com/theimpossibleastronaut/rmw"; changelog = "https://github.com/theimpossibleastronaut/rmw/blob/${src.rev}/ChangeLog"; license = licenses.gpl3Only; maintainers = with maintainers; [ dit7ya ]; }; } </ins>

Discussion:
Project description rmw (ReMove to Waste) is a trashcan/recycle bin utility for the command line. It can move and restore files to and from directories specified in a configuration file, and can also be integrated with your regular desktop trash folder (if your desktop environment uses the Trash specification). One of the unique features of rmw is the ability to purge items from your waste (or trash) directories after x number of days. Metadata homepage URL: https://remove-to- source URL: license: gpl3+ platforms: unix, linux, darwin, bsd
Change:
Type: drv -> drv */ <del> forceLlvmCodegenBackend = haskellLib.overrideCabal (drv: { </del> <ins> forceLlvmCodegenBackend = overrideCabal (drv: { </ins> configureFlags = drv.configureFlags or [ ] ++ [ "--ghc-option=-fllvm" ]; buildTools = drv.buildTools or [ ] ++ [ self.llvmPackages.llvm ]; });

Discussion:
Hi, I didn't know that Hackage permits multiple versions under same number. They are called revisions, nix function interface doesn't have any argument for revision. I am updating packages, because of migration to GHC9 and I noticed a trend - several packages instead of bumping version - reuse old version and revision to disambiguate. The typical scenario - I set version (e.g. "1.0.0"), I need, and fake SHA to get the correct one on the first run, because it is convenient. nixpkgs gives me some SHA. It turns out that it picks SHA for oldest revision! I think I am not the one who use the function such a way. It would nice to check package version for multiple revisions and print hashes and dates for all of them! Minimum is to extend callHackageDirect comments about Hackage revisions.
Revision don't cause a new tarball to be uploaded, so the hash is indeed correct (and stays correct). Instead revisions need to be handled separately because the only thing exposed by hackage are the updated cabal files (so it is limited what you can change in a revision). That there's no convenient interface in for revisions is unfortunate indeed and we should consider adding this. In the meantime the following workaround should work:
I marked this as stale due to inactivity. &rarr;
Change:
if ! [ "$targetHost" = "$buildHost" ]; then if [ -z "$targetHost" ]; then logVerbose "Running nix-copy-closure with these NIX_SSHOPTS: $SSHOPTS" <del> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyClosureFlags[@]}" --from "$buildHost" "$1" </del> <ins> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyFlags[@]}" --from "$buildHost" "$1" </ins> elif [ -z "$buildHost" ]; then logVerbose "Running nix-copy-closure with these NIX_SSHOPTS: $SSHOPTS" <del> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyClosureFlags[@]}" --to "$targetHost" "$1" </del> <ins> NIX_SSHOPTS=$SSHOPTS runCmd nix-copy-closure "${copyFlags[@]}" --to "$targetHost" "$1" </ins> else <del> buildHostCmd nix-copy-closure "${copyClosureFlags[@]}" --to "$targetHost" "$1" </del> <ins> buildHostCmd nix-copy-closure "${copyFlags[@]}" --to "$targetHost" "$1" </ins> fi fi }

Discussion:
says but in flake mode, it uses , not , and the flag has no effect. I guess this is technically as documented, but a bit surprising. Should it pass to as well?
Is there any workaround for now?
Change:
<ins> { lib, buildPythonPackage, fetchFromGitHub, chromadb, langchain-core, numpy, poetry-core, pytestCheckHook, nix-update-script, }: buildPythonPackage rec { pname = "langchain-chroma"; version = "0.1.1"; pyproject = true; src = fetchFromGitHub { owner = "langchain-ai"; repo = "langchain"; rev = "refs/tags/langchain-chroma==${version}"; hash = "sha256-PW4vfZVccuYnaR0jtOfHVaXXYoUyQbCfB8NwM+mXFGc="; }; sourceRoot = "${src.name}/libs/partners/chroma"; build-system = [ poetry-core ]; dependencies = [ langchain-core chromadb numpy ]; pythonImportsCheck = [ "langchain_chroma" ]; nativeCheckInputs = [ pytestCheckHook ]; passthru.updateScript = nix-update-script { extraArgs = [ "--version-regex" "langchain-chroma==(.*)" ]; }; meta = { description = "Build context-aware reasoning applications"; homepage = "https://github.com/langchain-ai/langchain"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ natsukium ]; }; } </ins>

Discussion:
Project description LangChain is a framework for developing applications powered by large language models (LLMs). <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
deadpixi-sam = deadpixi-sam-unstable; debian_devscripts = debian-devscripts; # added 2016-03-23 deepin = throw "deepin was a work in progress and it has been canceled and removed https://github.com/NixOS/nixpkgs/issues/94870"; # added 2020-08-31 <ins> deepspeech = throw "deepspeech was removed in favor of stt. https://github.com/NixOS/nixpkgs/issues/119496"; # added 2021-05-05 </ins> desktop_file_utils = desktop-file-utils; # added 2018-02-25 devicemapper = lvm2; # added 2018-04-25 digikam5 = digikam; # added 2017-02-18

Discussion:
<!-- 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: tts <!-- 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: 0.0.9 desired version: 0.0.11 maintainers: mozilla fired the team and they founded a new company to continue their work new releases can be found here
We are aware of the forks, we'll probably get to it before the branch-off. STT (DeepSpeech) was recently packaged, but does not build from source, so my interest in that package is limited.
Same also not a STT user.
can you update deepspeech to the new repo, call it stt and deprecate deepspeech? how to deprecate a package is documented here: please add a review. when anything is unclear, i would like to improve it
How about we call it instead?
i don't think that is very helpful for the end-user. the package name should match the upstream project name
do you want to update tts again?
Hello, just wanted to say that there has been a new release , in case someone wants to give it a shot.
Change:
if builtins.isNull (baseConfig.server.override_resource_path or null) then "${unwrapped}/${python3.sitePackages}/maubot/management/frontend/build" else baseConfig.server.override_resource_path; <del> })})} $out/${python3.sitePackages}/maubot/example-config.yaml </del> <ins> })} $out/${python3.sitePackages}/maubot/example-config.yaml </ins> rm -rf $out/bin ''} mkdir -p $out/bin

Discussion:
Steps to reproduce the behavior: maubot with sqlite db in nixos config my config:
this isn't a build failure (as build failure is for packages failing to build, not module issues), but thanks for the notice. The problem is a missing when checking for local Postresql databases with credentials. It can be fixed by switching to in I'll only be able to open a PR tomorrow, you can open it now if you want to try contributing, or you can wait for me to open it
sorry for wrong issue type, i'll wait for PR ;)
i disabled assertions just to test it out and got error during build
Change:
./darwin.patch ]; <del> nativeBuildInputs = [ cmake autoconf /* for vendored jemalloc */ ]; </del> <ins> nativeBuildInputs = [ cmake autoconf /* for vendored jemalloc */ ] ++ stdenv.lib.optional stdenv.isDarwin fixDarwinDylibNames; </ins> buildInputs = [ boost brotli double-conversion flatbuffers gflags glog gtest lz4 rapidjson snappy thrift uriparser zlib zstd python.pkgs.python python.pkgs.numpy

Discussion:
On macOS arrow-cpp produces a library which has "id" "". This seems to be different from all the other libraries I have which use an actual path starting with "/nix" and an executable linking against such a library fails to load at runtime. Fixing by hand the path with: fixes the issue and the executable linking to it works as expected. Is there anything particular which should be done to relocate the id of a dynamic library which needs to be explicitly done in nix?
Good catch! I've opened a PR to fix this.
Change:
[ librsvg sane-backends sane-frontends ] ++ (with perlPackages; [ Gtk3 <ins> Gtk3ImageView </ins> Gtk3SimpleList Cairo CairoGObject Glib GlibObjectIntrospection GooCanvas2 <ins> GraphicsTIFF IPCSystemSimple </ins> LocaleCodes LocaleGettext <del> PDFAPI2 </del> <ins> PDFBuilder ImagePNGLibpng </ins> ImageSane SetIntSpan PerlMagick

Discussion:
Describe the bug in seems to be broken, in a way (I think) related to how other things have broken in the past, e.g. . From looking at examples of fixes, e.g. , it looks like it might be necessary to patch the Perl source in , but I don't really understand what's going on so I don't know how. To Reproduce Steps to reproduce the behavior: to for this package so that the tests actually run, as in my PR tests fail Expected behavior I tried making a package that depends on , and got the following error at runtime: Maintainer information:
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
Change:
, SDL2 , SDL2_mixer , zlib <ins> , unzip , makeWrapper , makeDesktopItem , copyDesktopItems </ins> }: <del> let assets_version = "2.2.5"; assets = fetchurl { url = "https://github.com/mazmazz/SRB2/releases/download/SRB2_assets_220/srb2-${assets_version}-assets.7z"; sha256 = "1m9xf3vraq9nipsi09cyvvfa4i37gzfxg970rnqfswd86z9v6v00"; }; assets_optional = fetchurl { url = "https://github.com/mazmazz/SRB2/releases/download/SRB2_assets_220/srb2-${assets_version}-optional-assets.7z"; sha256 = "1j29jrd0r1k2bb11wyyl6yv9b90s2i6jhrslnh77qkrhrwnwcdz4"; }; in stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "srb2"; <del> version = "2.2.10"; </del> <ins> version = "2.2.11"; </ins> src = fetchFromGitHub { owner = "STJr"; repo = "SRB2"; <del> rev = "SRB2_release_${version}"; sha256 = "03388n094d2yr5si6ngnggbqhm8b2l0s0qvfnkz49li9bd6a81gg"; </del> <ins> rev = "SRB2_release_${finalAttrs.version}"; hash = "sha256-tyiXivJWjNnL+4YynUV6k6iaMs8o9HkHrp+qFj2+qvQ="; </ins> }; nativeBuildInputs = [ cmake nasm p7zip <ins> makeWrapper copyDesktopItems </ins> ]; buildInputs = [

Discussion:
The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020
I just noticed this pr, but it seems to have gone dead 3 months ago
closing as I'm making a new issue
Change:
let tortoisehgSrc = fetchurl rec { meta.name = "tortoisehg-${meta.version}"; <del> meta.version = "5.2.1"; url = "https://bitbucket.org/tortoisehg/thg/get/14221e991a5b623e0072d3bd340b759dbe9072ca.tar.gz"; sha256 = "01rpzf5z99izcdda1ps9bhqvhw6qghagd8c1y7x19rv223zi05dv"; </del> <ins> meta.version = "5.6"; url = "https://www.mercurial-scm.org/release/tortoisehg/targz/tortoisehg-${meta.version}.tar.gz"; sha256 = "031bafj88wggpvw0lgvl0djhlbhs9nls9vzwvni8yn0m0bgzc9gr"; </ins> }; tortoiseMercurial = mercurial.overridePythonAttrs (old: rec { inherit (tortoisehgSrc.meta) version; src = fetchurl { url = "https://mercurial-scm.org/release/mercurial-${version}.tar.gz"; <del> sha256 = "1pxkd37b0a1mi2zakk1hi122lgz1ffy2fxdnbs8acwlqpw55bc8q"; </del> <ins> sha256 = "1hk2y30zzdnlv8f71kabvh0xi9c7qhp28ksh20vpd0r712sv79yz"; </ins> }; });

Discussion:
tortoisehg 5.2.1 does not exist. The URL is dead and there is no authoritative "5.2.1" tarball listed anywhere. This package was upgraded to an unreleased version because of the python2 to 3 work by . We can upgrade to 5.6 which mirrors the version of mercurial in master or 5.4.2 for nixos-20.09. Will verify locally for 5.4.2 on nixos-20.09 <!-- 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: tortoisehg , nixpkgs.tortoisehg <!-- 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: 5.2.1 desired version: 5.6, 5.4.2 <!-- 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.
Current version is also a little buggy with the error described here: 2 works for me.