jiebi/CodeConvo huggingface dataset:
Code change:
### Interpreters <del> Versions 2.7, 3.5, 3.6, 3.7 and 3.8 of the CPython interpreter are available as respectively `python27`, `python35`, `python36`, `python37` and `python38`. The </del> <ins> Versions 2.7, 3.6, 3.7 and 3.8 of the CPython interpreter are available as respectively `python27`, `python36`, `python37` and `python38`. The </ins> aliases `python2` and `python3` correspond to respectively `python27` and `python38`. The default interpreter, `python`, maps to `python2`. The PyPy interpreters compatible with Python 2.7 and 3 are available as `pypy27` and

Related discussion:
text: According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date.
Code change:
''; }; <ins> subcommandPackages = mkOption { type = types.listOf types.package; default = [ ]; internal = true; description = '' List of packages containing tracker3 subcommands. ''; }; </ins> }; };

Related discussion:
text: Pretty much all commands just show the "usage" output, regardless if the input is correct or not. For example, outputs: Steps to reproduce the behavior: , , , and many other commands incorrect output I expect to see the correct output, for example should show the current status of all miners.
How did you determine the commands? The printed help page does not list any of those as supported.
I got the commands from the Tracker documentation: You are right that they aren't listed in the help page. I do have manuals with usage for all those commands installed though.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Code change:
githubId = 1855930; name = "Ertugrul Söylemez"; }; <ins> esau79p = { github = "EsAu79p"; githubId = 21313906; name = "EsAu"; }; </ins> esclear = { github = "esclear"; githubId = 7432848;

Related discussion:
text: Project description aw-watcher-window-wayland is a part of ActivityWatch needed to have it working in a Wayland compositor. At the present time, without this, the ActivityWatch package is not working on Wayland environments Metadata homepage URL: source URL: license: MPL-2.0 license platforms: linux
Code change:
<del> --- a/snappy-test.cc +++ b/snappy-test.cc @@ -46 +46 @@ -DEFINE_bool(run_microbenchmarks, true, +DEFINE_bool(run_microbenchmarks, false, </del>

Related discussion:
text: Describe the bug Because snappy does not install a pkgconfig file, you can't take snappy as a buildInput, packages will never find it. To Reproduce Expected behavior Metadata system: host os: multi-user?: sandbox: version: channels(seb): nixpkgs: Maintainer information: cc
I have opened a PR on the snappy codebase: It is waiting for review and then nixpkgs will need to be updated. Note how the PR has to handle the absolute path being configured in cmake by nix
has decided not to take the patch upstream, so I will work on adding the pkg-config file as part of the nix installation
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 .
Code change:
{ mkDerivation, lib , extra-cmake-modules <del> , hunspell, qtbase, qttools </del> <ins> , aspell, qtbase, qttools </ins> }: mkDerivation {

Related discussion:
text: Currently we build with support for . Sonnet typically looks in for dictionaries That means it won't be able to find any dictionaries and thus spellchecking won't work.
Is this still a problem? It seems that hunspell paths are not hardcoded in hunspelldict.h anymore: But they are still hardcoded in
Yes, this is still a problem. It seems like we should disable hunspell and use aspell, which is configured correctly in NixOS.
I marked this as stale due to inactivity. &rarr;
I marked this with "good first bug" because I think we need only to change to depend on , and do some testing.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Code change:
kermit-terminal = callPackage ../applications/terminal-emulators/kermit-terminal { }; kitty = darwin.apple_sdk_11_0.callPackage ../applications/terminal-emulators/kitty { <del> go = go_1_20; </del> <ins> go = go_1_21; </ins> harfbuzz = harfbuzz.override { withCoreText = stdenv.isDarwin; }; inherit (darwin.apple_sdk_11_0) Libsystem; inherit (darwin.apple_sdk_11_0.frameworks)

Related discussion:
text: Package name: kitty Latest released version: 0.29.2 <!-- Search your package here: --- Current version on the unstable channel: 0.29.2 Current version on the stable/release channel: 0.28.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.
Code change:
dconf gnome.nautilus gnome.nautilus-python <del> gobject-introspection </del> gsettings-desktop-schemas gtk3 python3.pkgs.pygobject3

Related discussion:
text: The is failing to build Steps to reproduce the behavior: Package should build
related to
This is unrelated, GNOME 43 is not yet released. Most likely this was caused by gobject-introspection changes.
gobject-introspection should be in nativeBuildInputs instead of buildInputs
Code change:
] ++ lib.optional cudaSupport cudatoolkit ++ lib.optionals enablePython (with pythonPackages; [python pybind11 ]); <del> patches = lib.optionals enablePython [ </del> <ins> patches = [ # fix build on aarch64-darwin # https://github.com/IntelRealSense/librealsense/pull/9253 (fetchpatch { url = "https://github.com/IntelRealSense/librealsense/commit/beb4c44debc8336de991c983274cad841eb5c323.patch"; sha256 = "05mxsd2pz3xrvywdqyxkwdvxx8hjfxzcgl51897avz4v2j89pyq8"; }) </ins> ./py_sitepackage_dir.patch ./py_pybind11_no_external_download.patch ];

Related discussion:
text: Describe the bug librealsense cannot be built on/for aarch64-linux. I see that the derivation says it is not supported on aarch64-linux but I also know it is possible to compile the library normally on that platform as I have done it before. So I think its just a problem with the derivation for now. I am willing to help in the work to fix the recipe, and test the fixes, but I am relatively new to the nix language and build system. I have attached the error message I get, could someone point me in the direction I should be looking to fix it? To Reproduce Steps to reproduce the behavior: Screenshots Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Maintainer information:
Hello! I tried it and got similar errors building graphite, though I can get it to build when I use the versions of the libraries so maybe that's a good place to start? I'm not sure what the issue is unfortunately.
I fixed the build of on aarch64-darwin and aarch64-linux in PR will not work on aarch64 unless somebody fixes the build of package on aarch64 theoretically should work, but in reality the build of which is a dependency fails on aarch64 Will you please open two new issues for and not available for aarch64? The build failures you see have nothing to do with librealsense.
Code change:
}: let <del> version = "2.11.6"; </del> <ins> version = "2.12.1"; </ins> src = fetchFromGitHub { owner = "paperless-ngx"; repo = "paperless-ngx"; rev = "refs/tags/v${version}"; <del> hash = "sha256-RNX+KS2h9zrOK8QzeQWH55pkNPTDW4gic2HLG+XXLRg="; </del> <ins> hash = "sha256-txqwVGLUel74ObCqwMWSqa4Nd2eDRf0SqAIes5tlMDg="; </ins> }; # subpath installation is broken with uvicorn >= 0.26

Related discussion:
text: Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.6 <!-- 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. --
Code change:
libvmi = callPackage ../development/libraries/libvmi { }; <ins> libutp = callPackage ../applications/networking/p2p/libutp { }; </ins> lifelines = callPackage ../applications/misc/lifelines { }; liferea = callPackage ../applications/networking/newsreaders/liferea { };

Related discussion:
text: Project description Fragments is a modern, responsive and graphical Gnome bittorrent client Metadata homepage URL: source URL: license: gpl3 platforms: linux The new version of Fragments depends on libutp which hopefully gets merged soon. I've opened a pull request for it . for Fragments.
We have transmission and torrential. Maybe that's something for you.
That's true but Fragments is a really neat, easy and modern looking torrent client. It has an adaptive interface which would also work quite well on mobile devices, for example NixOS mobile :+1:
Code change:
subprocess.check_call(["@systemd@/bin/bootctl", "--path=@efiSysMountPoint@", "--no-variables", "install"]) else: # Update bootloader to latest if needed <del> systemd_version = subprocess.check_output(["@systemd@/bin/bootctl", "--version"], universal_newlines=True).split()[1] </del> <ins> systemd_version = subprocess.check_output(["@systemd@/bin/bootctl", "--version"], universal_newlines=True).split()[2] </ins> sdboot_status = subprocess.check_output(["@systemd@/bin/bootctl", "--path=@efiSysMountPoint@", "status"], universal_newlines=True) # See status_binaries() in systemd bootctl.c for code which generates this <del> m = re.search("^W+File:.*/EFI/(BOOT|systemd)/.*.efi (systemd-boot (d+))$", </del> <ins> m = re.search("^W+File:.*/EFI/(BOOT|systemd)/.*.efi (systemd-boot ([d.]+[^)]*))$", </ins> sdboot_status, re.IGNORECASE | re.MULTILINE) <ins> needs_install = False </ins> if m is None: <del> print("could not find any previously installed systemd-boot") </del> <ins> print("could not find any previously installed systemd-boot, installing.") # Let systemd-boot attempt an installation if a previous one wasn't found needs_install = True </ins> else: <del> sdboot_version = m.group(2) if systemd_version > sdboot_version: </del> <ins> sdboot_version = f'({m.group(2)})' if systemd_version != sdboot_version: </ins> print("updating systemd-boot from %s to %s" % (sdboot_version, systemd_version)) <del> subprocess.check_call(["@systemd@/bin/bootctl", "--path=@efiSysMountPoint@", "update"]) </del> <ins> needs_install = True if needs_install: subprocess.check_call(["@systemd@/bin/bootctl", "--path=@efiSysMountPoint@", "update"]) </ins> mkdir_p("@efiSysMountPoint@/efi/nixos") mkdir_p("@efiSysMountPoint@/loader/entries")

Related discussion:
text: shows this for me: When I try to upgrade my system, I get the error “could not find any previously installed systemd-boot”. This is because the script can't deal with systemd-boot versions with a minor version appended to it, since the regex is : Fixing this is not quite straightforward sadly, since the version is later used for comparison, so fixing this requires adding support for proper major/minor version comparison in this script. <!-- 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
Code change:
MemoryDenyWriteExecute = true; NoNewPrivileges = true; PrivateDevices = true; <del> PrivateMounts = true; </del> <ins> PrivateMounts = mkDefault true; </ins> PrivateNetwork = mkDefault false; PrivateTmp = true; <del> PrivateUsers = true; </del> <ins> PrivateUsers = mkDefault true; </ins> ProtectClock = true; ProtectControlGroups = true; # ProtectHome=true would not allow BindPaths= to work across /home,

Related discussion:
text: I have transmission running inside a Nixos container which has been working without issue until I recently updated the system. It now fails to start inside the container, I have tried deleting the container and all its data but the same issue exists when creating a new one. I have also tried creating the path "" on both the host and container but it doesn't seem to care. Steps to reproduce the behavior: Run transmission inside of a container Transmission service starts and runs without issue Service status Here's where I have the container and transmission defined in my config. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Same here, not sure if it's an upstream or nixpkgs issue
For the time being and since it's inside a container anyway I'm overriding the root dir of the systemd unit:
Thanks your fix is working for me!
The problem is that is listed in : Which got introduced in to The original problem was that was not in the chroot. I'd say mounting all of as read-only is going too far, so a better fix would be to just mount and only if is true. It also seems weird to have this logic be part of Transmission, but whatever. So a workaround is: (And I'm not sure why this wasn't a problem for 3 years)
I've stumbled upon this issue as well, and wondering if there is anything we can do about it regarding the Transmission service. I had to disable the following is well, before it played nicely in my setup.
indeed, adding only was one the alternatives suggested in , so we can try your suggestion. IMHO disabling or should not be the default, we could make them use though, would that be enough for you?
This is actually still an issue and it isn't limited to containers. Adding the params that posted, unfortunately, does not work for me ;/
Code change:
check_connection_key_bits(client, "a.example.test", "384") webserver.succeed("grep testing /var/lib/acme/a.example.test/test") <ins> with subtest("Correctly implements OCSP stapling"): switch_to(webserver, "ocsp-stapling") webserver.wait_for_unit("acme-finished-a.example.test.target") check_stapling(client, "a.example.test") </ins> with subtest("Can request certificate with HTTPS-01 when nginx startup is delayed"): switch_to(webserver, "slow-startup") webserver.wait_for_unit("acme-finished-slow.example.com.target")

Related discussion:
text: Describe the bug causes Lego to fail. To Reproduce Steps to reproduce the behavior: set on an enabled certificate. to this configuration. fail. Lego complains about an unrecognized (really misplaced) flag. Expected behavior The certificate will be successfully fetched, with Must-Staple enabled. Screenshots Additional context I think the problematic code is here: should not be in commonOpts, it should instead be in runOpts and renewOpts. Lego runs successfully when is to and . Notify maintainers (the acme team) Metadata Maintainer information:
Thanks for the report :) It appears that the --must-staple option is common to both "run" and "renew" modes, but is not actually a common option that can be specified before the mode. I'll get a PR ready for this.
Code change:
[[package]] name = "edgedb-cli" <del> version = "3.3.0" </del> <ins> version = "3.4.0" </ins> dependencies = [ "anyhow", "arc-swap",

Related discussion:
text: Package name: edgedb Latest released version: 3.2.0 Current version on the unstable channel: 2.3.1 Current version on the stable/release channel: 2.3.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Code change:
} // (args.argsOverride or { })); in <del> { zen = zenKernelsFor zenVariant; lqx = zenKernelsFor lqxVariant; } </del> <ins> zenKernelsFor variants.${variant} </ins>

Related discussion:
text: Mainline / hardened / testing / ... kernels can be painlessly modified via : Sadly, this does not work with a bunch of other kernel variants: All kernels should honor I am not entirely sure how dynamic binding is implemented in kernel stuff, however slightly changing xanmod parts this way seems to fix : zen and lqx look similar to xanmod, no idea about libre Pinging people who seem to update affected packages often Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
same underlying issue as it seems
Can confirm that this patch fix the issue for zen and lqx kernels:
have you submitted these changes as a PR that I can review?
sorry for the late response. I created a new PR with this changes.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Code change:
<ins> { lib , stdenv , yarn , fetchYarnDeps , fixup_yarn_lock , nodejs , electron , fetchFromGitHub , gitUpdater , makeWrapper , makeDesktopItem , copyDesktopItems }: stdenv.mkDerivation rec { pname = "r2modman"; version = "3.1.42"; src = fetchFromGitHub { owner = "ebkr"; repo = "r2modmanPlus"; rev = "v${version}"; hash = "sha256-16sE706iivYoI40JJUkqVmtxkYsgAFBg+0tXOc6scqc="; }; offlineCache = fetchYarnDeps { yarnLock = "${src}/yarn.lock"; hash = "sha256-CXitb/b2tvTfrkFrFv4KP4WdmMg+1sDtC/s2u5ezDfI="; }; nativeBuildInputs = [ yarn fixup_yarn_lock nodejs makeWrapper copyDesktopItems ]; configurePhase = '' runHook preConfigure # Workaround for webpack bug # https://github.com/webpack/webpack/issues/14532 export NODE_OPTIONS="--openssl-legacy-provider" export HOME=$(mktemp -d) yarn config --offline set yarn-offline-mirror $offlineCache fixup_yarn_lock yarn.lock yarn install --offline --frozen-lockfile --ignore-platform --ignore-scripts --no-progress --non-interactive patchShebangs node_modules/ runHook postConfigure ''; buildPhase = '' runHook preBuild yarn --offline quasar build --mode electron --skip-pkg # Remove dev dependencies. yarn install --production --offline --frozen-lockfile --ignore-platform --ignore-scripts --no-progress --non-interactive runHook postBuild ''; installPhase = '' runHook preInstall mkdir -p $out/share/r2modman cp -r dist/electron/UnPackaged/. node_modules $out/share/r2modman ( cd public/icons for img in *png; do dimensions=''${img#favicon-} dimensions=''${dimensions%.png} mkdir -p $out/share/icons/hicolor/$dimensions/apps cp $img $out/share/icons/hicolor/$dimensions/apps/${pname}.png done ) makeWrapper '${electron}/bin/electron' "$out/bin/r2modman"  --inherit-argv0  --add-flags "$out/share/r2modman"  --add-flags "''${NIXOS_OZONE_WL:+''${WAYLAND_DISPLAY:+--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations}}" runHook postInstall ''; desktopItems = [ (makeDesktopItem { name = pname; exec = pname; icon = pname; desktopName = pname; comment = meta.description; categories = [ "Game" ]; keywords = [ "launcher" "mod manager" "thunderstore" ]; }) ]; passthru.updateScript = gitUpdater { rev-prefix = "v"; }; meta = with lib; { description = "Unofficial Thunderstore mod manager"; homepage = "https://github.com/ebkr/r2modmanPlus"; changelog = "https://github.com/ebkr/r2modmanPlus/releases/tag/v${version}"; license = licenses.mit; maintainers = with maintainers; [ aidalgol huantian ]; inherit (electron.meta) platforms; }; } </ins>

Related discussion:
text: Project description A simple and easy to use mod manager for several Unity games using Thunderstore. Support for Risk of Rain 2, Dyson Sphere Program, Valheim, GTFO, Outward, TaleSpire, H3VR, ROUNDS, Mechanica, Muck, BONEWORKS, Lethal League Blaze, and Timberborn. Metadata homepage URL: source URL: license: mit platforms: linux
I marked this as stale due to inactivity. &rarr;
Code change:
github = "lo1tuma"; name = "Mathias Schreck"; }; <ins> loewenheim = { email = "loewenheim@mailbox.org"; github = "loewenheim"; name = "Sebastian Zivota"; }; </ins> lopsided98 = { email = "benwolsieffer@gmail.com"; github = "lopsided98";

Related discussion:
text: fails with the vdirsyncer version from nixos-unstable. it works if I install vdirsyncer with pip. Output of :
Which do you get via ? Is it the old 0.16 branch or the new 0.17 one (which was mostly rewritten in rust)? We have the latest git version of 0.17 in nixpkgs. Unfortunately, so it might be some time before this bug is fixed.
outputs this:
Same problem here. Was there any reason to go for an alpha release except for the issue referenced in ? If not, a downgrade to 0.16.7 should be fine, since the original bug is still open and probably won't be fixed for a while without anyone maintaining vdirsyncer.
There are , so I'd rather not downgrade. I'd be happy with a package for the 0.16 branch though.
That'd be great! I haven't looked into packaging yet, so it would take some time if I tried. Would you mind helping out?
I just opened a PR. It’s my first time contributing to , so I hope it’s up to snuff.
Code change:
<ins> diff --git a/CMakeLists.txt b/CMakeLists.txt index e49fac2..25e3302 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -34,6 +34,14 @@ option(ENABLE_GLIBC_WORKAROUND "Workaround GLIBC symbol exports" OFF) list(APPEND CMAKE_MODULE_PATH "${CMAKE_CURRENT_SOURCE_DIR}/cmake") +IF(APPLE) +    set(CMAKE_THREAD_LIBS_INIT "-lpthread") +    set(CMAKE_HAVE_THREADS_LIBRARY 1) +    set(CMAKE_USE_WIN32_THREADS_INIT 0) +    set(CMAKE_USE_PTHREADS_INIT 1) +    set(THREADS_PREFER_PTHREAD_FLAG ON) +ENDIF() + if(ENABLE_MASON) # versions in use set(MASON_BOOST_VERSION "1.65.1") @@ -405,7 +413,8 @@ endif() if(APPLE) set(CMAKE_OSX_DEPLOYMENT_TARGET "10.10") execute_process(COMMAND xcrun --sdk macosx --show-sdk-path OUTPUT_VARIABLE CMAKE_OSX_SYSROOT OUTPUT_STRIP_TRAILING_WHITESPACE) +  execute_process(COMMAND uname -m OUTPUT_VARIABLE JAMBA_OSX_NATIVE_ARCHITECTURE OUTPUT_STRIP_TRAILING_WHITESPACE) -  set(CMAKE_OSX_ARCHITECTURES "x86_64") +  set(CMAKE_OSX_ARCHITECTURES "${JAMBA_OSX_NATIVE_ARCHITECTURE}") +  message(STATUS "Set Architecture to ${JAMBA_OSX_NATIVE_ARCHITECTURE} on OS X") -  message(STATUS "Set Architecture to x64 on OS X") exec_program(uname ARGS -v  OUTPUT_VARIABLE DARWIN_VERSION) string(REGEX MATCH "[0-9]+" DARWIN_VERSION ${DARWIN_VERSION}) </ins>

Related discussion:
text: Steps to reproduce the behavior: FWIW: my fix is here, - but it is using a fork of . If somebody has the time to create a minimal patch on top of the current source, please feel free to. Please run and paste the result.
Looks like you are on a good path. Unfortunately I have no access to Apple hardware at all, but would be happy to merge a PR.
Yes, is working on it. There is a more active fork of luabind here: - how about we switch to using it? It'll obviate a bunch of patches as well.
I agree, sounds sensible.
Code change:
in stdenv.mkDerivation { name = "hsc3-mode-${version}"; src = fetchurl { <del> url = http://hackage.haskell.org/package/hsc3-0.15/hsc3-0.15.tar.gz; </del> <ins> url = mirror://hackage/hsc3-0.15/hsc3-0.15.tar.gz; </ins> sha256 = "2f3b15655419cf8ebe25ab1c6ec22993b2589b4ffca7c3a75ce478ca78a0bde6"; <del> }; </del> <ins> }; </ins> buildInputs = [ emacs ];

Related discussion:
text: During Hackage downtime, nix builds are needlessly broken. There are mirrors available; we should use them. See: Mirrors include: http://objects-us-east- I'm a third party reporting errors I've heard of, so I don't have precise repro steps. Do certain Haskell-related build stuff during Hackage downtime, I guess?
Mirror list is available at E. g. https://objects-us-east-