jiebi/CodeConvo huggingface dataset:
Code change:
let <del> requiredPackages = map lib.lowPrio </del> <ins> requiredPackages = map (pkg: setPrio ((pkg.meta.priority or 5) + 3) pkg) </ins> [ config.nix.package pkgs.acl pkgs.attr

Related discussion:
text: The dhcpcd resolvconf hook check if resolvconf is installed and, because the command is in the PATH, it won't fall back to writing directly but will attempt to execute something like this: echo 'nameserver 10.0.1.1' | resolvconf -a wlan0 Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.
Reproducible way to see these collisions: With a file set to I ran in the (the latest commit on the branch), and I get these collision messages:
ping
Hi all nixos-version 03. (Koi) I have the same collision on kill gnutar resolvconf but also on collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/64x64/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/22x22/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/16x16/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/scalable/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.
Code change:
let <del> requiredPackages = map lib.lowPrio </del> <ins> requiredPackages = map (pkg: setPrio ((pkg.meta.priority or 5) + 3) pkg) </ins> [ config.nix.package pkgs.acl pkgs.attr

Related discussion:
text: 0/share/icons/hicolor/48x48/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/64x64/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/22x22/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/16x16/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/scalable/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/48x48/apps/phonon-'
This seems to include many more collisions than related to this issue.
Maybe rather than changing the nix-env priority, a better solution is to remove some of these programs (e.g. delete in util-linux's ).
That seems hacky to me. What if you want util-linux's version of kill? Presumably if the maintainer thinks it's worth including, someone has a use for it. Nixpkgs shouldn't be making these decisions at the derivation level. Something like meta seems ideal because you can change it without effecting the derivation.
Since and were merged, does that mean this issue can be closed now?
I think so, I don't see these collisions anymore.
Let me know if this isn't fixed after all.
sorry, but i see these collisions.
Code change:
let <del> requiredPackages = map lib.lowPrio </del> <ins> requiredPackages = map (pkg: setPrio ((pkg.meta.priority or 5) + 3) pkg) </ins> [ config.nix.package pkgs.acl pkgs.attr

Related discussion:
text: it's a different issue: it seems you're installing both the wrapped and unwrapped version of the same packages. I'd say there's something wrong with your configuration, but if you think otherwise open a new issue.
Code change:
# Rename the binary mv "$out/bin/Pinta" "$out/bin/pinta" <ins> # Copy runtime icons mkdir -p $out/share/icons/hicolor/16x16/ cp -r Pinta.Resources/icons/hicolor/16x16/* $out/share/icons/hicolor/16x16/ </ins> # Install dotnet build installer/linux/install.proj  -target:Install 

Related discussion:
text: I am encountering the following error after launching Pinta 2.0.2. I thought initially that it was a problem in the Adwaita theme itself, but whatever the GTK theme I use, I always have the problem. I tried on two different machines and had the same problem with both. NixOS with unstable channel Ubuntu + Nix 2.5.1 with unstable channel I did not have this problem in the last packaged version of Pinta. Maybe it is there since the 2.0.2 upgrade? Pinta should launch without this error. ! Please run and paste the result.
This looks like exactly the same problem discussed on Except that it should be fixed. Not sure what is happening here, and I don't have access to a Linux machine right now to debug. Maybe can help?
I also have this issue. It also causes the toolbar on the left to not appear.
Can someone show me the contents of the directory inside the package? It should have a directory/file somewhere, inside the icons directory (I don't remember the exact path). If this is missing, this is probably the issue.
It is missing:
Huh... I think I can blindly patch this issue, however someone will need to test on the PR.
Wait, I was wrong, it is there, but not in :
It shouldn't be in , it should be in . This is the issue. This can be probably fixed later correctly by setting some setting on , but since I don't have access to a Linux system for now I will just duplicate the assets for now. Later on I can do a proper fix.
Can someone test this PR please:
Waouh that was fast. Thanks a lot, both of you for your reactivity!
Code change:
<ins> { lib , mkDerivation , fetchurl , extra-cmake-modules , kirigami2 , ktextwidgets , libksane , qtquickcontrols2 }: mkDerivation rec { pname = "skanpage"; version = "1.0.0"; src = fetchurl { url = "mirror://kde/stable/skanpage/${version}/${pname}-${version}.tar.xz"; hash = "sha256-kPVAG64oPkKF3ztHB4V7M2xc1AcvwiHnYpMMLMQNYGA="; }; nativeBuildInputs = [ extra-cmake-modules ]; buildInputs = [ kirigami2 ktextwidgets libksane qtquickcontrols2 ]; meta = with lib; { description = "KDE utility to scan images and multi-page documents"; homepage = "https://apps.kde.org/skanpage"; license = licenses.gpl2Plus; maintainers = with maintainers; [ samuelgrf ]; platforms = platforms.linux; }; } </ins>

Related discussion:
text: Project description Skanpage is a simple no-frills scanner KDE application that is a bit more comprehensive than skanlite. Most importantly, it has multi page support, that skanlite is painfully lacking. cc Metadata homepage URL: source URL: license: gpl2+ platforms: KDE
Code change:
# To avoid this issue, debugpy should be installed using python.withPackages: # python.withPackages (ps: with ps; [ debugpy ]) ./fix-test-pythonpath.patch <ins> # Support disabling process timeouts when set to 0 # See https://github.com/microsoft/debugpy/pull/1286 (fetchpatch { url = "https://github.com/microsoft/debugpy/commit/1569cc8319350afcc5ba8630660f599d514ac3bb.patch"; hash = "sha256-v4GKLb2M20F1egAGtix9cTkSzBnvSgSSphSQST5p63w="; }) </ins> ] ++ lib.optionals stdenv.isLinux [ # Hard code GDB path (used to attach to process) (substituteAll {

Related discussion:
text: Steps to reproduce the behavior: (warning: veeery long) Seems caused by Also previously reported (if I'm reading the many thousands of lines of output right) to be another instance of Breaks: .
This appears to have been fixed somewhere between and
I have no idea how you tested, but after a (pulling branch), I fail to build this same package. Now with the newer hash: I vote for this issue to be marked as "prematurely-closed", and thus re-opened.
debugpy was blocking my nixos rebuilds through . Updating to resolved it for me. That's about all the testing I did at the time, and figured it was good. Sorry about that.
Yep! Looks like this is related to flaky process test timeouts (which are more likely to fail on less powerful / overworked devices). should fix this!
You can checkout to see when the fix will be applied to the channel you're using.
Code change:
r2mod_cli = callPackage ../games/r2mod_cli { }; <ins> r2modman = callPackage ../games/r2modman { }; </ins> racer = callPackage ../games/racer { }; randtype = callPackage ../games/randtype { };

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:
hashType=$NIX_HASH_ALGO hashFormat=$hashFormat format=nix <del> skopeoCmd="skopeo --insecure-policy --tmpdir=$TMPDIR" </del> usage(){ echo  >&2 "syntax: nix-prefetch-docker [options] [IMAGE_NAME [IMAGE_TAG|IMAGE_DIGEST]]

Related discussion:
text: Describe the bug Running fails with To Reproduce Extra info On of that script scopeoCmd isn't called correctly. Seems like introduced the problem in this PR
Code change:
netfilterRPFilter = true; grsecurity = false; xen_dom0 = false; <ins> ia32Emulation = true; </ins> } // features) kernelPatches; intermediateNixConfig = import ./common-config.nix {

Related discussion:
text: I currently cannot execute any 32 bit Linux binaries on my 64 bit system and this breaks updates, since I have 32 bit support enabled in the nix options: I remember that this worked about a week ago, so something has changed. I am new to NixOS, so its possible that I have done something wrong. I used ArchLinux for about 9 years before that and now NixOS for just 3 months and its concepts are still foreign for me. As a long term linux user (about 15 years) I do feel a bit out of place in NixOS. So I am not sure how to fix that myself. Not sure. I have wine installed and support for 32 bit games enabled. Then I normally do just 'nixos-rebuild switch --upgrade' to upgrade, and sometimes 'nix-channel --update'. I also regularly do 'nix-collect-garbage -d'. No idea if that is reproducible or not.
This might be from Could you see if it works without that commit? Also verify that /nix/store/4qj9vzggfzsc34ci79ckaim5cjrwc6ns-bash-4.4-p23/bin/bash executes. I can run it on my system. You can run this to verify that your store is not corrupted:
I solved it now for me. Instead of using the 'linuxPackagestestinghardened' 4.20 linux kernel I switched back to 'linuxPackages419' 4.19.2 kernel and now executing 32 binaries work again. So I guess the hardened kernel does not support executing 32 bit binaries. Does it make sense to have some kind of visible warning here? I normally would not have used the hardened kernel, if that wouldn't have been the only 4.20 version is I get. Its not clear to me when and how those changes in master appear in my nixpkgs/nixos channel (I am on unstable). I would like to use the master branch directly, but I haven't figured out how to best do that yet.
The same here, hardened kernel 4.18.17 and build failed.
Code change:
netfilterRPFilter = true; grsecurity = false; xen_dom0 = false; <ins> ia32Emulation = true; </ins> } // features) kernelPatches; intermediateNixConfig = import ./common-config.nix {

Related discussion:
text: building '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxcdxtn-'... while setting up the build environment: executing '/nix/store/xgf4vra77qrww0n228hd80jsdccdp54w-bash-4.4-p23/bin/bash': Exec format error builder for '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxcdxtn-' failed with exit code 1 building '/nix/store/cfwj5yjby2xvagyj69zd1yx8hdhi27ay-'... cannot build derivation '/nix/store/maynq4fxxjc217figygdrgg5q9xnw6yy-mesa-drivers+txc-': 1 dependencies couldn't be built cannot build derivation '/nix/store/wv9b4ayvgnpkvwz81zkk0lm9w4v5pd1y-opengl-drivers-': 1 dependencies couldn't be built cannot build derivation '/nix/store/q61vc27rdbcsrhxifiw89w1qdjax1amh-nixos-system-brix-': 1 dependencies couldn't be built error: build of '/nix/store/q61vc27rdbcsrhxifiw89w1qdjax1amh-nixos-system-brix-' failed Thanks
Maybe the hardened kernel shouldn't set when NixOS' is an ?
It should be 64 bit for the x86_64-linux stdenv. But some packages use the i686 stdenv.
I am not too familiar with stdenv. Is this expected behaviour that a 64-bit system uses 32-bit binaries? This issue is reproducible building as well.
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.
Code change:
netfilterRPFilter = true; grsecurity = false; xen_dom0 = false; <ins> ia32Emulation = true; </ins> } // features) kernelPatches; intermediateNixConfig = import ./common-config.nix {

Related discussion:
text: 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 . on the on .
This should be resolved by - please reopen if there's still a problem.
Code change:
makeShellWrapper = makeSetupHook { deps = [ dieHook ]; substitutions = { <del> shell = targetPackages.runtimeShell; </del> <ins> # targetPackages.runtimeShell only exists when pkgs == targetPackages (when targetPackages is not  __raw) shell = if targetPackages ? runtimeShell then targetPackages.runtimeShell else throw "makeWrapper/makeShellWrapper must be in nativeBuildInputs"; </ins> }; passthru = { tests = tests.makeWrapper;

Related discussion:
text: Describe the bug I need to list the out paths of cross compiled packages beforehand which causes an eval error. To Reproduce Steps to reproduce the behavior: Expected behavior List all out paths like `. Additional context I need this feature for nixpkgs-review when cross compiling. 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 system: host os: multi-user?: sandbox: version: channels(user): nixpkgs: Maintainer information:
I think its because of the lack of splicing for perl-packages. Note however, that when that is fixed, other package sets will fail with the same issue. cc
Probably multiple issues. Have seen that problem with building xwayland for aarch64 too. Removing makeWrapper helps but probably breaks it :(. But the deps don't cross-build anyway so never got that far for now. Was thinking about opening an issue but got caught up trying to find the issue -- to no avail. Not currently at my machine, might post it later.
I marked this as stale due to inactivity. &rarr;
still important to me
Fix in
Code change:
{ stdenv, fetchurl, gfortran, readline, ncurses, perl, flex, texinfo, qhull <del> , libX11, graphicsmagick, pcre, pkgconfig, mesa, fltk </del> <ins> , libsndfile, libX11, graphicsmagick, pcre, pkgconfig, mesa, fltk </ins> , fftw, fftwSinglePrec, zlib, curl, qrupdate, openblas , qt ? null, qscintilla ? null, ghostscript ? null, llvm ? null, hdf5 ? null,glpk ? null , suitesparse ? null, gnuplot ? null, jdk ? null, python ? null

Related discussion:
text: Octave needs library to process audio (e.g. ). System: NixOS: Nix version: Nixpkgs version:
See
Closing in favor of
Code change:
<del> diff --git a/src/color_dialog/src/main.ts b/src/color_dialog/src/main.ts index 9522499..9911530 100644 --- a/src/color_dialog/src/main.ts +++ b/src/color_dialog/src/main.ts @@ -1,4 +1,4 @@ -#!/usr/bin/gjs +#!/usr/bin/env gjs imports.gi.versions.Gtk = '3.0'; @@ -84,4 +84,4 @@ function launch_color_dialog() { Gtk.init(null); -launch_color_dialog()  No newline at end of file +launch_color_dialog() </del> diff --git a/src/extension.ts b/src/extension.ts index 7417c46..00d5829 100644 --- a/src/extension.ts

Related discussion:
text: In 's tray menu the options "Floating Window Exceptions" & "Active Hint Color" don't work. Steps to reproduce the behavior: & enable pop-shell in GNOME (Wayland). pop-shell's tray menu and try clicking the mentioned options. Further dialogs should open for the respective features.
I found the problem: the compiled (g)js are not executible in filesystem. I do not know a solution yet. Most beautiful solution, fix chmod in pop-shell (but how ...). Or after compiling with an workaround in nix. Other solutions are set path to gjs during patching. Till fixing, you can run this features in your in, with calling it per gjs ...
Code change:
owner = "bpozdena"; repo = "OneDriveGUI"; rev = "v${version}"; <del> hash = "sha256-HutziAzhIDYP8upNPieL2GNrxPBHUCVs09FFxdSqeBs="; </del> <ins> hash = "sha256-d5NAcT3x9R/2DVQKZsw4GH63nTlVFsvkWwMrb42s18s="; </ins> }; <del> nativeBuildInputs = [ copyDesktopItems makeWrapper ]; </del> <ins> nativeBuildInputs = [ copyDesktopItems makeWrapper ]; </ins> <del> propagatedBuildInputs = with python3Packages; [ pyside6 requests ]; </del> <ins> propagatedBuildInputs = with python3Packages; [ pyside6 requests ]; </ins> # wrap manually to avoid having a bash script in $out/bin with a .py extension dontWrapPythonPrograms = true;

Related discussion:
text: A recent update on unstable broke compatibility between OneDriveGui and OneDrive client. Steps to reproduce the behavior: unstable to current version ( ) a OneDrive profile configured in OneDriveGui OneDriveGui window OneDriveGui correctly recognizing the cli client ! After some investigation on their respective repos, it appears that OneDriveGui 1.0.3 is not compatible with OneDrive 2.5.x, now in rc (and in Nixos unstable) so this is going to stay broken until OneDriveGui releases their 1.1.0 version. There's an open issue on their repository... which points to an alpha release of the new gui... it might be of interest to package that one on unstable. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
FYI , v2.5.0 will GA 16th September 2024 AEST
Code change:
<ins> diff -Naur terraform.old/internal/command/init.go terraform.new/internal/command/init.go --- terraform.old/internal/command/init.go +++ terraform.new/internal/command/init.go @@ -3,6 +3,7 @@ import ( "context" "fmt" +	"os" "log" "strings" @@ -55,6 +56,11 @@ var diags tfdiags.Diagnostics +	val, ok := os.LookupEnv("NIX_TERRAFORM_PLUGIN_DIR") +	if ok { +		flagPluginPath = append(flagPluginPath, val) +	} + if len(flagPluginPath) > 0 { c.pluginPath = flagPluginPath } </ins>

Related discussion:
text: Project description OpenTofu is a fork of Terraform, which is no longer under a free license (and should be marked as unfree for releases = 1.6.0). This fork is from the free sources before the license change to a source-available BSL license. Metadata homepage URL: source URL: license: mpl platforms: unix
cc some active maintainers of terraform:
Related issue:
I think it would be a good idea to wait for it to be actually named, see OpenTF is a placeholder name, and at this point OpenTF didn't release an alpha.
Will to take this on later today if nobody else grabs it.
Pull request has been opened, if the current Terraform maintainers are okay with it I can add them to the maintainers section of the new package. Otherwise more than happy to take responsibility for it.
Code change:
python3.pkgs.buildPythonApplication rec { pname = "radicale"; <del> version = "3.1.3"; </del> <ins> version = "3.1.4"; </ins> src = fetchFromGitHub { owner = "Kozea"; repo = "Radicale"; rev = "v${version}"; <del> hash = "sha256-a1oapCktJPvNO+MTsB9COtxSFB/ZIZvJiuqX+s+lncY="; </del> <ins> hash = "sha256-vX6lYiDqpQeWVLotyt2ODwcjskWB6EuCky3/V8m1m7Q="; </ins> }; postPatch = ''

Related discussion:
text: Since won't build () From the above logs: Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Can reproduce on my ZFS system, not on my ext4 system though.
I can't reproduce by running on any system.
I was able to build from that commit nix store is zfs backed
It's more relevant whether is.
The renameat2 syscall used isn't (fully?) supported by ZFS: I'm not sure how that relates to this issue only occurring with , I guess it's related to the sandbox.
/tmp is tmpfs for me
Thanks for filing the upstream issue!
Code change:
<ins> # pkgs.ociTools {#sec-pkgs-ociTools} `pkgs.ociTools` is a set of functions for creating containers according to the [OCI container specification v1.0.0](https://github.com/opencontainers/runtime-spec). Beyond that it makes no assumptions about the container runner you choose to use to run the created container. ## buildContainer {#ssec-pkgs-ociTools-buildContainer} This function creates a simple OCI container that runs a single command inside of it. An OCI container consists of a `config.json` and a rootfs directory.The nix store of the container will contain all referenced dependencies of the given command. The parameters of `buildContainer` with an example value are described below: ```nix buildContainer { args = [ (with pkgs; writeScript "run.sh" '' #!${bash}/bin/bash exec ${bash}/bin/bash '').outPath ]; mounts = { "/data" = { type = "none"; source = "/var/lib/mydata"; options = [ "bind" ]; }; }; readonly = false; } ``` - `args` specifies a set of arguments to run inside the container. This is the only required argument for `buildContainer`. All referenced packages inside the derivation will be made available inside the container - `mounts` specifies additional mount points chosen by the user. By default only a minimal set of necessary filesystems are mounted into the container (e.g procfs, cgroupfs) - `readonly` makes the container's rootfs read-only if it is set to true. The default value is false `false`. </ins>

Related discussion:
text: This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
Hi Already opened a PR for that ().
Code change:
owner = "WerWolv"; repo = pname; rev = "v${version}"; <del> hash = "sha256-H2bnRByCUAltngmVWgPW4vW8k5AWecOAzwtBKsjbpTw="; </del> <ins> hash = "sha256-meOx8SkufXbXuBIVefr/mO9fsUi3zeQmqmf86+aDMaI="; </ins> }; nativeBuildInputs = [ cmake llvm python3 perl pkg-config ];

Related discussion:
text: Package name: imhex Latest released version: 1.27.1 <!-- Search your package here: --- Current version on the unstable channel: 1.26.2 Current version on the stable/release channel: 1.19.3 <!-- 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:
<ins> { lib , python3 , fetchFromGitHub }: python3.pkgs.buildPythonApplication rec { pname = "rstfmt"; version = "0.0.13"; format = "pyproject"; src = fetchFromGitHub { owner = "dzhu"; repo = "rstfmt"; rev = "refs/tags/v${version}"; hash = "sha256-SJRA14CfoT8XMt3hMB7cLdmuLwsJnBSwhKkD1pJvQCI="; }; propagatedBuildInputs = with python3.pkgs; [ black docutils sphinx ]; # Project has no unittest just sample files doCheck = false; pythonImportsCheck = [ "rstfmt" ]; meta = with lib; { description = "A formatter for reStructuredText"; homepage = "https://github.com/dzhu/rstfmt"; license = licenses.mit; maintainers = with maintainers; [ fab ]; }; } </ins>

Related discussion:
text: Project description Formatter for rst (reStructuredText) files Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin, ...