jiebi/CodeConvo huggingface dataset:
Change:
coreFileSystemOpts = { name, config, ... }: { options = { mountPoint = mkOption { example = "/mnt/usb"; <del> type = nonEmptyStr; </del> <ins> type = addCheckDesc "non-empty without trailing slash" types.str (s: isNonEmpty s && (builtins.match ".+/" s) == null); </ins> description = "Location of the mounted the file system."; };

Discussion:
Describe the bug A clear and concise description of what the bug is. I have a separate /nix/ ZFS dataset whose mountpoint I declare in my NixOS config. However when I try to boot that system, it mounts the root dataset, tries to read something out of the nix store (before it's mounted) and fails, prompting me to reboot or ignore. works but doesn't. To Reproduce Steps to reproduce the behavior: a separate ZFS dataset for /nix/ to mount it on /nix and /nix/ respectively that /nix gets mounted before anything is read from the nix store while /nix/ isn't Expected behavior A clear and concise description of what you expected to happen. It should behave the same, no matter the trailing slash. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:
I think this is because of is handled specially, in particular, it is not unmounted. But isn't matched, so it gets unmounted, which breaks everything (because everything lives in ).
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Change:
<del> { alsa-lib , aubio , cmake , dssi , fetchurl , flac , libjack2 , ladspaH , ladspaPlugins , liblo , libmad , libsamplerate , libsndfile , libtool , libvorbis , lilv , lv2 , mkDerivation , opusfile , pkg-config , qttools , qtbase , rubberband , serd , sord , sratom , lib , suil }: mkDerivation rec { pname = "qtractor"; version = "0.9.25"; src = fetchurl { url = "mirror://sourceforge/${pname}/${pname}-${version}.tar.gz"; sha256 = "sha256-cKXHH7rugTJ5D7MDJmr/fX6p209wyGMQvSLbv5T0KXU="; }; nativeBuildInputs = [ cmake libtool pkg-config qttools ]; buildInputs = [ alsa-lib aubio dssi flac libjack2 ladspaH ladspaPlugins liblo libmad libsamplerate libsndfile libtool libvorbis lilv lv2 opusfile qtbase rubberband serd sord sratom suil ]; meta = with lib; { description = "Audio/MIDI multi-track sequencer"; homepage = "https://qtractor.sourceforge.io"; license = licenses.gpl2Plus; maintainers = with maintainers; [ goibhniu ]; platforms = platforms.linux; }; } </del>

Discussion:
Package name: qtractor Latest released version: 0.9.38 Current version on the unstable channel: 0.9.25 Current version on the stable/release channel: 0.9.25 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Updated to 0.9.37
Updated to 0.9.38
Change:
let pname = "lens"; <del> version = "5.3.4"; build = "${version}-latest.20220120.1"; </del> <ins> version = "5.5.3"; build = "${version}-latest.20220602.2"; </ins> name = "${pname}-${version}"; src = fetchurl { url = "https://api.k8slens.dev/binaries/Lens-${build}.x86_64.AppImage"; <del> sha256 = "sha256-9vRLQFSocVkHAfgwdKSPhSAO4G/v/ANd0WQmilcZiVw="; </del> <ins> sha256 = "sha256-lwiwyXoO+7KgDnQ2Ly0QK0oEVHR73nsMZMGOd2j48dg="; </ins> name = "${pname}.AppImage"; };

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: lens <!-- 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: v5.3.4 desired version: v5.4.6 (or maybe v5.5.0 till then) <!-- 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. i am missing features like show logs and open terminal in POD.
Change:
buildGoModule rec { pname = "drone.io${lib.optionalString (!enableUnfree) "-oss"}"; <del> version = "1.10.0"; </del> <ins> version = "2.0.0"; </ins> <del> vendorSha256 = "sha256-cKHX/GnvGELQBfoo0/1UmDQ4Z66GGnnHG7+1CzjinL0="; </del> <ins> vendorSha256 = "sha256-cnbZSnHU+ORm7/dV+U9NfM18Zrzi24vf7qITPJsusU8="; </ins> doCheck = false;

Discussion:
Drone 2.0 has been released: <!-- Note that these are hard requirements --- name: <!-- 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: 1.10.0 desired version: 2.0.0 Please tag this issue in your PR.
Change:
<del> { lib, stdenv, fetchurl, pkg-config, gnome, gtk3, gjs, flex, bison, libxml2, intltool, gdl, libgda, gtksourceview, gsettings-desktop-schemas, itstool, python3, ncurses, makeWrapper }: stdenv.mkDerivation rec { pname = "anjuta"; version = "3.34.0"; src = fetchurl { url = "mirror://gnome/sources/anjuta/${lib.versions.majorMinor version}/${pname}-${version}.tar.xz"; sha256 = "13ql7axw6zz387s7pa1m7wmh7qps3x7fk53h9832vq1yxlq33aa2"; }; passthru = { updateScript = gnome.updateScript { packageName = "anjuta"; attrPath = "gnome.anjuta"; }; }; enableParallelBuilding = true; nativeBuildInputs = [ pkg-config intltool itstool python3 makeWrapper # Required by python3 ncurses ]; buildInputs = [ flex bison gtk3 libxml2 gjs gdl libgda gtksourceview gsettings-desktop-schemas ]; preFixup = '' wrapProgram $out/bin/anjuta  --prefix XDG_DATA_DIRS :  "$GSETTINGS_SCHEMAS_PATH" ''; meta = with lib; { description = "Software development studio"; homepage = "http://anjuta.org/"; license = licenses.gpl2; maintainers = with maintainers; []; platforms = platforms.linux; }; } </del>

Discussion:
If my sources are correct, the Project was archived in 2022 and the link for the Hompage now redirects to an indonesian gambling site. Linking to the could be better, but the Homepage link (on mentioned repo) also links to the gambling site.
The github repo does not look official. That would be But maybe it is time to remove it.
Considering the archived repo also links to the lapsed domain that now redirects to a gambling site, I'd be in favour of removal. However, that will also necessitate the removal of , which hasn't seen any updates since 2015. Neither has any maintainers, so I don't think the removal is likely to be objected to.
Change:
version = "2.1.22"; sha256 = "1wk57dz0kmc6d5y8d8dkx269lzh3ark3751z734gxncwdlclcyz3"; generation = "2_1"; <ins> extraMeta.knownVulnerabilities = [ # Fixed in 3.* but 2.* hasn't been released since "CVE-2020-17516" ]; </ins> })

Discussion:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc
See also , ,
Change:
<del> { lib, stdenv, fetchurl, unzip, makeWrapper, makeDesktopItem, icoutils, jre }: </del> <ins> { lib, stdenv, fetchurl, unzip, makeWrapper, makeDesktopItem, icoutils, jre8 }: </ins> let desktopItem = makeDesktopItem {

Discussion:
Broken package: 'groove' Install package. Run 'groove-simulator'. File -New Grammar... Try to save, get an exception. system: host os: multi-user?: sandbox: version: channels(maestro): channels(root): nixpkgs: Permalink to broken package: It seems that the broken Nix package depends on OpenJDK17. Found that running their latest version (5.8.1) from SourceForge with the much older OpenJDK8 works just fine. Did not test with OpenJDK11. Probably just have to depend on an older Java version. Package version can also be bumped to 5.8.1. Don't have sufficient knowledge of Nix to fix this myself. Thanks
Probably should be assigned to
I think I've fixed it. I'll submit a PR soon. Also, I tested OpenJDK11 and it crashed there as well.
Change:
# Also put git-http-backend into $PATH, so that we can use smart # HTTP(s) transports for pushing ln -s $out/libexec/git-core/git-http-backend $out/bin/git-http-backend <ins> # wrap perl commands gitperllib=$out/lib/perl5/site_perl for i in ${builtins.toString perlLibs}; do gitperllib=$gitperllib:$i/lib/perl5/site_perl done wrapProgram $out/libexec/git-core/git-cvsimport  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-add--interactive  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-archimport  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-instaweb  --set GITPERLLIB "$gitperllib" wrapProgram $out/libexec/git-core/git-cvsexportcommit  --set GITPERLLIB "$gitperllib" </ins> '' + (if svnSupport then

Discussion:
When setting in , the user gets a warning when using any command that use under the hood: The setting is ineffective. Users still need to press the Enter key at each prompt. Add the above mentioned setting to . Notice the warning e.g. with in any Git repository with a dirty working tree. System: 18.03pre116347. (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: 18.03pre116572.
Fixed by
Change:
__structuredAttrs = true; meta = { <del> description = "Vulkan-based translation layer for Direct3D 9/10/11"; </del> <ins> description = "Vulkan-based translation layer for Direct3D 8/9/10/11"; </ins> homepage = "https://github.com/doitsujin/dxvk"; changelog = "https://github.com/doitsujin/dxvk/releases"; maintainers = [ lib.maintainers.reckenrode ]; license = lib.licenses.zlib; <del> platforms = lib.platforms.windows ++ lib.platforms.linux; </del> <ins> badPlatforms = lib.platforms.darwin; platforms = lib.platforms.windows ++ lib.platforms.unix; </ins> }; })

Discussion:
Package name: dxvk Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 2.3.1 Current version on the stable/release channel: 2.3.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --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:
# TODO: Package mapbox-variant postFixup = '' <ins> # Nuke refs to `tg_owt` which is introduced by `__FILE__` in headers. remove-references-to -t ${tg_owt} $out/bin/telegram-desktop </ins> # This is necessary to run Telegram in a pure environment. # We also use gappsWrapperArgs from wrapGAppsHook. wrapProgram $out/bin/telegram-desktop 

Discussion:
, CVSSv3=2.4 (nixos-20.09) Scanned versions: nixos-20.09: . Cc Cc
Fixed by .
Change:
# So what we do here is basically run in postFixup and emulate the same # behaviour as fixupOutputHooks because the setup hook for patchelf is run in # fixupOutput and the postFixup hook runs later. <del> postFixupHooks+=( 'for output in $outputs; do prefix="${!output}" autoPatchelf; done' ) </del> <ins> postFixupHooks+=(' if [ -z "$dontAutoPatchelf" ]; then autoPatchelf -- $(for output in $outputs; do [ -e "${!output}" ] || continue echo "${!output}" done) fi ') </ins>

Discussion:
determines which executables it should patch via: However, PIEs have a type of , as in: Questions: Should also patch PIEs? An alternative is to just call manually, but I'm having trouble finding out how to run it in the correct phase. Is there even a reliable way to distinguish between shared libraries and PIEs? I know in general, shared libs don't have an section, but is this a reliable enough assumption? cc
Actually, executables can also be shared libraries at the same time (eg. and I'm doing exactly that in my as well), so the only thing that distinguishes them is an section (except if statically linked of course). So I guess it's a better idea to just look for in instead of what we currently do. At least if I don't miss something, this should be the most reliable way, after all what we want to do with executables is to patch the section. If nobody else sends a PR in the meantime, I'm going to fix this next week. As for it's a bit more difficult, because it needs to be run after the normal hook, so it might be necessary to add .
Change:
face_recognition_models = face-recognition-models; # added 2022-10-15 fake_factory = throw "fake_factory has been removed because it is unused and deprecated by upstream since 2016."; # added 2022-05-30 faulthandler = throw "faulthandler is built into ${python.executable}"; # added 2021-07-12 <ins> inherit (super.pkgs) fetchPypi; # added 2023-05-25 </ins> filemagic = throw "inactive since 2014, so use python-magic instead"; # added 2022-11-19 flaskbabel = flask-babel; # added 2023-01-19 flask_login = flask-login; # added 2022-10-17

Discussion:
Since , was moved to top level, and and are aliases of from the top level To find the usages of these aliases, you can search for in the repository Note that there are false positives (e.g. when used in overlays) and this also might not include all usages (let inherit)
Change:
buildPythonApplication rec { pname = "gdbgui"; <del> version = "0.15.0.1"; </del> <ins> version = "0.15.1.0"; </ins> buildInputs = [ gdb ]; propagatedBuildInputs = [ <del> flask-socketio </del> <ins> eventlet </ins> flask-compress <ins> flask-socketio </ins> pygdbmi pygments ]; src = fetchPypi { inherit pname version; <del> sha256 = "sha256-bwrleLn3GBx4Mie2kujtaUo+XCALM+hRLySIZERlBg0="; </del> <ins> sha256 = "sha256-YcD3om7N6yddm02It6/fjXDsVHG0Cs46fdGof0PMJXM="; </ins> }; postPatch = '' echo ${version} > gdbgui/VERSION.txt <del> # remove upper version bound sed -ie 's!,.*<.*!!' requirements.in </del> <ins> # relax version requirements sed -i 's/==.*$//' requirements.txt </ins> ''; postInstall = ''

Discussion:
gdbgui fails to start (dump_stack) nixpkgs similar
Same issue for me :cry: Looks related to this cs01/gdbgui/issues/425
Change:
<ins> { lib, buildPythonPackage, fetchFromGitHub, pytestCheckHook, pythonOlder, colormath, cython, oldest-supported-numpy, setuptools, }: buildPythonPackage rec { pname = "color-operations"; version = "0.1.3"; pyproject = true; disabled = pythonOlder "3.8"; src = fetchFromGitHub { owner = "vincentsarago"; repo = "color-operations"; rev = version; hash = "sha256-KsrgilcNK2ufPKrhtGdf8mdlFzhsHB2jHN+WDlZqabc="; }; nativeBuildInputs = [ cython setuptools ]; propagatedBuildInputs = [ oldest-supported-numpy ]; nativeCheckInputs = [ colormath pytestCheckHook ]; preCheck = '' python setup.py build_ext --inplace ''; pythonImportsCheck = [ "color_operations" ]; meta = { description = "Apply basic color-oriented image operations. Fork of rio-color"; homepage = "https://github.com/vincentsarago/color-operations"; license = lib.licenses.mit; maintainers = lib.teams.geospatial.members; }; } </ins>

Discussion:
Project description User friendly Rasterio plugin to read raster datasets. Metadata homepage URL: source URL: license: bsd platforms: unix Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Already packaged by in . Should be easy to add to nixpkgs.
Requires morecantile and pystac, that shoud be to nixpkgs as well.
Change:
''; }; <ins> grammarly-languageserver = prev.grammarly-languageserver.override (old: { meta = old.meta // { # requires EOL Node.js 16 # https://github.com/znck/grammarly/issues/334 broken = true; }; }); </ins> graphql-language-service-cli = prev.graphql-language-service-cli.override { nativeBuildInputs = [ pkgs.buildPackages.makeWrapper ]; postInstall = ''

Discussion:
Some packages, e.g. requires nodejs16 (znck/grammarly), but I cannot override the nodejs version of the package to nodejs16 because it is EOF. Steps to reproduce the behavior: nodejs version of some nodejs package by doing the error message. Allow forcing the use of EOL packages, or maybe officially state that this is not supported and mark the package as broken. If applicable, add screenshots to help explain your problem. 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. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Allow forcing the use of EOL packages, or maybe officially state that this is not supported If you run: , you'll get all the instructions on how to do this. This has been marked as broken:
Sorry, I was not aware that I can get instructions when doing directly. Will do. For marking the package as broken, I mean instead of . Sorry for the bad wording.
Change:
export EMACSNATIVELOADPATH="${newNativeLoadPath[*]}" export emacsWithPackages_siteLispNative=@wrapperSiteLispNative@ <del> exec @prog@ @autoloadExpression@ "$@" </del> <ins> exec @prog@ "$@" </ins>

Discussion:
The file generated by the Emacs wrapper is redundant because the autoload definitions are already processed by the builtin : the is loaded after with the command line option , but loads the package autoloads before . We can understand this better by considering a few scenarios. If we start Emacs with disabled, then the autoloads will not be available in because is not loaded until later: If we modify the wrapper as in so that is not loaded, the autoloads will still be found as long as is enabled: is enough on its own to handle autoloads for the Emacs wrapper. Therefore, I propose to remove in favor of the builtin Emacs functionality.
Somehow, removing this broke from emacs-overlay. I have to manually run or anything depending on autoloaded tramp functions errors out with "no such function". I do disable as my site-lisp directory is managed by Nix. Is this configuration no longer recommended/supported? Is there a way to just engage 's autoload mechanism without allowing it to access the network or install packages?
I also fully disable since all of my emacs packages are installed via nix and noticed this change broke things for me. I'm interested in this as well. Edit: Maybe this:
Change:
patchelf --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  $opt/resources/app.asar.unpacked/node_modules/symbol-provider-ctags/vendor/ctags-linux <del> '' + lib.optionalString (stdenv.hostPlatform.system == "x86_64-linux") '' </del> # Replace the bundled git with the one from nixpkgs dugite=$opt/resources/app.asar.unpacked/node_modules/dugite rm -f $dugite/git/bin/git ln -s ${git}/bin/git $dugite/git/bin/git <del> rm -f $dugite/git/libexec/git-core/git ln -s ${git}/bin/git $dugite/git/libexec/git-core/git </del> <ins> # Not only do we need to replace the git binary itself, we also need to replace # all the symlinks in dugite/git/libexec/git-core. for file in "$dugite/git/libexec/git-core"/*; do if [ -x "$file" ] && file "$file" | grep -q "ELF"; then # Remove ELF executable rm "$file" # Get the corresponding filename in nixpkgs's git filename=$(basename "$file") git_executable="${git}/libexec/git-core/$filename" # Create symlink to $git_executable ln -s "$git_executable" "$file" echo "Replaced $file with symlink to $git_executable" fi done # Was symlinked in previous loop, but actually, nixpkgs has a separate package for git-lfs # Unlink to avoid a "File exists" error and relink correctly unlink $dugite/git/libexec/git-core/git-lfs ln -s ${git-lfs}/bin/git-lfs $dugite/git/libexec/git-core/git-lfs '' + lib.optionalString (stdenv.hostPlatform.system == "x86_64-linux") '' </ins> # We have to patch a prebuilt binary in the asar archive # But asar complains because the node_gyp unpacked dependency uses a prebuilt Python3 itself

Discussion:
Install pulsar 109.0 on nixos stable Steps to reproduce the behavior: pulsar 109.0 on nixos stable to github fatal : 'remote-https' seem to be a git command, but could not be executed. could git-remote-https be broken? Be able to fetch pull and push Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've been able to reproduce the issue and find the root cause. is a independent binary of just . Looking at how to fix this proprely . Not sure I can easily backport it to 23.11 tho Quick update: Turns out there isn't only (which is symlinked up to) which has issue. And I can not simply symlink the whole Git package in its place, , the library used upstream, add other file, which are not included by default in git, but are required at runtime.
Well, it wasn't as hard as I thought it was going to be. Probably not going to be able to backport because of the bump from 1.109.0 to 1.114.0, but feel free to try out the patch in , targeting Unstable :)
Change:
<ins> { lib, python3Packages, fetchFromGitHub, }: python3Packages.buildPythonApplication rec { pname = "makejinja"; version = "2.6.0"; pyproject = true; src = fetchFromGitHub { owner = "mirkolenz"; repo = "makejinja"; rev = "v${version}"; hash = "sha256-sH4m+rcHA6nW21xEJon10lS7e5QiFwUyvV49NZ3UY+s="; }; build-system = with python3Packages; [ poetry-core ]; dependencies = with python3Packages; [ jinja2 pyyaml rich-click typed-settings immutables ] ++ typed-settings.optional-dependencies.attrs ++ typed-settings.optional-dependencies.cattrs ++ typed-settings.optional-dependencies.click; preCheck = '' substituteInPlace pyproject.toml  --replace-fail "--cov makejinja --cov-report term-missing" "" ''; nativeCheckInputs = with python3Packages; [ pytestCheckHook ]; meta = { description = "Generate entire directory structures using Jinja templates with support for external data and custom plugins"; homepage = "https://github.com/mirkolenz/makejinja"; license = lib.licenses.mit; mainProgram = "makejinja"; maintainers = with lib.maintainers; [ tomasajt mirkolenz ]; platforms = lib.platforms.darwin ++ lib.platforms.linux; }; } </ins>

Discussion:
Project description makejinja can be used to automatically generate files from . It is conceptually similar to since both are built on top of Jinja. However, makejinja is a standalone tool that can be used without Ansible and offers some advanced features like custom plugins. A use case for this tool is generating config files for : Using the same language that the built-in templates use, you can greatly simplify your configuration. An can be found in the tests directory. Metadata homepage URL: source URL: license: mit platforms: all Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks guys :)