jiebi/CodeConvo huggingface dataset:
Change:
buildGoModule rec { pname = "katana"; <del> version = "1.0.3"; </del> <ins> version = "1.0.4"; </ins> src = fetchFromGitHub { owner = "projectdiscovery"; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-0OXpA+sa97YjbHhIq3Uj65OWg53PH9y2cY8bjCqC3tQ="; </del> <ins> hash = "sha256-wpGRpgRJtywkTJ3YBk5TzXc2taPPWjOhj+Kg8hAgm7M="; </ins> }; <del> vendorHash = "sha256-rb0fNAOP4y2yvJb7FIlAIfXF0uw0eLKgup75f9cwT6U="; CGO_ENABLED = 0; </del> <ins> vendorHash = "sha256-qqivaKipe7lfUq3Neod8JMvtMVQN4O03JpDMSMHf8YY="; </ins> subPackages = [ "cmd/katana" ];

Discussion:
Steps to reproduce the behavior: that build exited with success code, but directory is empty. Removing the following fixes the issue for me. Disclaimer: I'm not familiar with golang so I'm not sure what this does or why it was in the first place. <!-- 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.
thank you for your bugreport, we need cgo because a dependency needs cgo
Change:
teams = callPackage ../applications/networking/instant-messengers/teams { }; <del> teams-for-linux = callPackage ../applications/networking/instant-messengers/teams-for-linux { electron = electron_29; }; </del> teamspeak_client = libsForQt5.callPackage ../applications/networking/instant-messengers/teamspeak/client.nix { }; teamspeak5_client = callPackage ../applications/networking/instant-messengers/teamspeak/client5.nix { }; teamspeak_server = callPackage ../applications/networking/instant-messengers/teamspeak/server.nix { };

Discussion:
Package name: teams-for-linux Latest released version: 1.9.2 <!-- Search your package here: --- Current version on the unstable channel: 1.4.27 Current version on the stable/release channel: 1.4.27 <!-- 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:
serviceConfig = { Type = "oneshot"; <del> MemoryDenyWriteExecute = true; </del> PrivateDevices = true; PrivateNetworks = true; ProtectControlGroups = true;

Discussion:
The guix-gc.service doesn't work. Steps to reproduce the behavior: in `systemctl status guix-gc.service I think this is because the JIT needs write and execute permissions but the service disallows it with . I changed it to and it works now. The guix-gc service should run normally and collect the garbage. Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(maxsilvester): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I can reproduce the error and so does the fix. Thank you for reporting!
Change:
else throw "buildRubyGem: don't know how to build a gem of type "${type}"" ); <ins> # See: https://github.com/rubygems/rubygems/blob/7a7b234721c375874b7e22b1c5b14925b943f04e/bundler/lib/bundler/source/git.rb#L103 suffix = if type == "git" then builtins.substring 0 12 attrs.source.rev else version; </ins> documentFlag = if document == [] then "-N"

Discussion:
Describe the bug fails to build when the gem configured in the is pointing to a git repository. <details<summaryGemfile</summary</details<details</summary</details<details</summary</details<details<summarynix-build output</summary</detailsTo Reproduce Run with the configuration posted above. Expected behavior The package should build like it does when the gem is pointed to a released version. Metadata Maintainer information:
Can confirm this, I have the same issue trying to package
I ran into this issue today. Both in my scenario and the recipe above the issue happens bundlerApp tries to of the gem. The directory find is call with doesn't exist. While I don't know the proper way to fix bundlerApp, a work around is to set the installManpages attributes to false. ej.
I'm having issue as well, is there any temporal fix atleast? Its annoying, and making my setup not-so-reproducible, I'm bundling puppet and it says: Its actually been created with rev: at and haven't been copied over.
Seems like you're right not installing manpages did somehow fix it, but not sure how you figured out... What I find post trying that is that the problem resides exactly in these lines:
I figured out the workaround by reading the error from nix log . Seeing the call to find being the error and looking for the expression responsible for making the call. Found it was the the installManpages option as you linked above. However I'm not familiar enough with the process to know what is the proper way to fix this. It seems the reason it fails is because in only has the dependencies of the gem we are building, not the gem itself. Should the man page installation happen in a latter phase? Should it look for the gem man pages in a different place? In what phase it is running?
I started a PR for the fix, can you please try building packages from this PR branch?
Change:
<ins> { lib , fetchFromGitHub , rustPlatform , dbus , pkg-config }: rustPlatform.buildRustPackage rec { pname = "ianny"; version = "1.0.0beta.1"; src = fetchFromGitHub { owner = "zefr0x"; repo = "ianny"; rev = "v${version}"; hash = "sha256-Bnr+wtusvTM690IISBs0wKj0ChBoIrMHyVZ8wdGgK08="; }; cargoHash = "sha256-/8C+hDq/z+h1uxO9prLbKHgyfMGrMODAs5/yUrutaAM="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ dbus.dev ]; postPatch = '' substituteInPlace src/main.rs  --replace-fail '/usr/share/locale' $out/share/locale ''; preFixup = '' mkdir -p $out/etc/xdg/autostart mkdir -p $out/usr/share/local cp io.github.zefr0x.ianny.desktop $out/etc/xdg/autostart/ ''; meta = with lib; { description = "Desktop utility that helps preventing repetitive strain injuries by keeping track of usage patterns and periodically informing the user to take breaks."; homepage = "https://github.com/zefr0x/ianny"; license = licenses.gpl3; mainProgram = "ianny"; maintainers = with maintainers; [ max-amb ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description <!-- Describe the project a little: --Simple, light-weight, easy to use, and effective ) desktop utility helps preventing by keeping track of usage patterns and periodically informing user to take breaks. Metadata homepage URL: source URL: license: gpl3.0, platforms: linux
Change:
pythonImportsCheck = [ "wlroots" ]; <ins> passthru.tests = { inherit qtile; }; </ins> meta = with lib; { homepage = "https://github.com/flacjacket/pywlroots"; description = "Python bindings to wlroots using cffi";

Discussion:
Steps to reproduce the behavior: Qtile This log comes from a system update (nixos-rebuild switch --upgrade). I have been using Qtile for a long time, even before I recently changed to NixOS from Gentoo, and I am quite sure that Qtile currently needs <wlroots-0.16.0, i.e. wlroots-0.15.x. A few days ago, in commit , pywlroots is updated from 0.15.x to 0.16, pinning wlroots to 0.16, and therefore breaks the dependency of Qtile. I notify both maintainers of Qtile and pywlroots, because this may require a change to both packages, providing a pywlroots015 and using that for qtile. Please run and paste the result.
Yeah, I didn't update the package on purpose when the latest version was released. The build failure can be fixed by bumping the wlroots derivation used by qtile to 0.16 as well but that breaks the Wayland backend at runtime. It's a bit unfortunate that i wasn't notified of the package being updated, since qtile is the only reverse dependency, so the update wasn't necessary at all.
Alternatively, if qtile is the only package depending on pywlroots, why not downgrade pywlroots to 0.15 and pin it to wlroots015? Later on when the new qtile is released that supports 0.16, upgrade them in tandem?
PR to revert in
cc (since you did the pywlroots bump) The pywlroots bump from and the last staging-next broke qtile (the only reverse dep of pywlroots) since qtile currently requires pywlroots 0.15 until a new release supports 0.16
So pywlroots is behind on wlroots support and qtile is behind on pywlroots support. Name a better trio, I'll wait. :clap: On a more serious note: Feel free to do the revert, I have no strong opinion on the matter. If this becomes a regular fallout on may become an option.
pywlroots is not behind on wlroots. It's only qtile which is behind on pywlroots (but qtile hasn't had a release since pywlroots 0.16).

Ah ok, so requires 0.16, but defaults to 0.15, hence the requirement for the pin. Got it.
Change:
{ source = "${pkgs.syslinux}/share/syslinux"; target = "/isolinux"; } <ins> { source = config.isoImage.efiSplashImage; target = "/EFI/boot/efi-background.png"; } </ins> { source = config.isoImage.splashImage; target = "/isolinux/background.png"; }

Discussion:
It points at this: ! I'm not sure anyone's made updated splash images with the new logo, but it'd be good to standardize.
Basically an instance of
Oh, true. Unsure whether to leave this open as a concrete thing that can be fixed, since isn't very specific about what's left to be fixed. Or just to close it and add more detail there?
Best to fix it immediately ;-)
That is actually the ISOLINUX background only. There's a separate on for GRUB:
Change:
buildGoModule rec { pname = "gitleaks"; <del> version = "8.19.0"; </del> <ins> version = "8.19.2"; </ins> src = fetchFromGitHub { owner = "zricethezav"; repo = "gitleaks"; rev = "refs/tags/v${version}"; <del> hash = "sha256-p4Va6qI/khXetN1ECRvFrsza5vqPVKKoUobhERWxDhI="; </del> <ins> hash = "sha256-VC8Bf6jcxXdBws7IParh9Srk34JiYVx5Tk2LLilrNJ4="; </ins> }; vendorHash = "sha256-DgCtWRo5KNuFCdhGJvzoH2v8n7mIxNk8eHyZFPUPo24=";

Discussion:
Package name: gitleaks Latest released version: 8.19.2 <!-- Search your package here: --- Current version on the unstable channel: 8.19.0 Current version on the stable/release channel: 8.18.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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Since Version 8.19.0 isn't available for me, the flag access fix introduced in Version 8.19.1 is particularly useful.
Change:
SDL2_mixer SDL2_net SDL2_ttf <del> boost </del> curl glew icu

Discussion:
name: widelands current version: 1.0 desired version: 1.1 maintainers: The widelands devs sent us an email about the release. I think this is a first for me.
I'm working on a PR for this (and once I figure out the github UI, I'll assign it to myself)..
Closing since fixes this. Please reopen if I'm wrong.
Change:
cmake ninja gfortran <ins> ] ++ lists.optionals cudaSupport [ cuda-native-redist </ins> ]; buildInputs = [

Discussion:
Per , assuming NVIDIA continues with its current compute capability naming scheme, will run into issues with the launch of Blackwell. This is a followup from <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
-    echo 'Creating stateful directory' -    mkdir -p ${DESTDIR}${LOCALSTATEDIR}/lib/fwupd #fi <del> diff --git a/plugins/flashrom/fu-plugin-flashrom.c b/plugins/flashrom/fu-plugin-flashrom.c index 598e0c42..a0a2c4a7 100644 --- a/plugins/flashrom/fu-plugin-flashrom.c +++ b/plugins/flashrom/fu-plugin-flashrom.c @@ -52,7 +52,7 @@ fu_plugin_startup (FuPlugin *plugin, GError **error) g_autoptr(GError) error_local = NULL; /* we need flashrom from the host system */ -	data->flashrom_fn = fu_common_find_program_in_path ("flashrom", &error_local); +	data->flashrom_fn = fu_common_find_program_in_path ("@flashrom@/bin/flashrom", &error_local); /* search for devices */ hwids = fu_plugin_get_hwids (plugin); diff --git a/plugins/uefi/fu-plugin-uefi.c b/plugins/uefi/fu-plugin-uefi.c index 9293715c..e2e77c58 100644 --- a/plugins/uefi/fu-plugin-uefi.c +++ b/plugins/uefi/fu-plugin-uefi.c @@ -416,7 +416,7 @@ fu_plugin_update (FuPlugin *plugin, fu_plugin_add_report_metadata (plugin, "MissingCapsuleHeader", str); /* record boot information to system log for future debugging */ -	efibootmgr_path = fu_common_find_program_in_path ("efibootmgr", NULL); +	efibootmgr_path = fu_common_find_program_in_path ("@efibootmgr@/bin/efibootmgr", NULL); if (efibootmgr_path != NULL) { if (!g_spawn_command_line_sync ("efibootmgr -v", &boot_variables, NULL, NULL, error)) diff --git a/plugins/uefi/fu-uefi-pcrs.c b/plugins/uefi/fu-uefi-pcrs.c index 5c7e5239..01acbf7f 100644 --- a/plugins/uefi/fu-uefi-pcrs.c +++ b/plugins/uefi/fu-uefi-pcrs.c @@ -147,7 +147,7 @@ fu_uefi_pcrs_setup (FuUefiPcrs *self, GError **error) /* old name, then new name */ argv0 = fu_common_find_program_in_path ("tpm2_listpcrs", NULL); if (argv0 == NULL) -			argv0 = fu_common_find_program_in_path ("tpm2_pcrlist", error); +			argv0 = fu_common_find_program_in_path ("@tpm2_tools@/bin/tpm2_pcrlist", error); if (argv0 == NULL) return FALSE; if (!fu_uefi_pcrs_setup_tpm20 (self, argv0, error)) diff --git a/src/fu-common.c b/src/fu-common.c index bd6faeef..45ba2a60 100644 --- a/src/fu-common.c +++ b/src/fu-common.c @@ -436,7 +436,7 @@ fu_common_firmware_builder (GBytes *bytes, g_return_val_if_fail (error == NULL || *error == NULL, NULL); /* find bwrap in the path */ -	bwrap_fn = fu_common_find_program_in_path ("bwrap", error); +	bwrap_fn = fu_common_find_program_in_path ("@bubblewrap@/bin/bwrap", error); if (bwrap_fn == NULL) return NULL; </del>

Discussion:
Describe the bug As I am trying to upgrade my XPS 13, fwupd can't find To Reproduce Expected behavior Update completes Additional context I am using nixos-unstable Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Looking back at this patch that's probably not right. Probably all calls to need to be removed and it should just be a string to the executable.
If we're already wrapping the executables with , why not set the instead of patching?
Change:
# # If a directory with the same basename ending in .d exists next to the unit file, it will be # assumed to contain override files which will be parsed as well and handled properly. <del> sub parseUnit { my ($unitPath) = @_; </del> <ins> sub parse_unit { my ($unit_path) = @_; </ins> # Parse the main unit and all overrides <del> my %unitData; parseSystemdIni(%unitData, $_) for glob("${unitPath}{,.d/*.conf}"); return %unitData; </del> <ins> my %unit_data; # Replace  with  so glob() still works with units that have a  in them # Valid characters in unit names are ASCII letters, digits, ":", "-", "_", ".", and "" $unit_path =~ s///gmsx; foreach (glob "${unit_path}{,.d/*.conf}") { parseSystemdIni(%unit_data, "$_") } return %unit_data; </ins> } # Checks whether a specified boolean in a systemd unit is true

Discussion:
Switching NIxOS configurations when using produces the following warning: Steps to reproduce the behavior: (current master) file in the directory with the following content: test fails and produces the warning should not produce warnings. It looks like currently can't handle service file names containing a . I tracked the first failing commit down to . The warning seems to not create any problems for me at the moment and all services are running.
Great… I'll take a look
Change:
dst = interfaceCfg.interfaceNamespace; ip = nsWrap "ip" src dst; wg = nsWrap "wg" src dst; <del> in nameValuePair "wireguard-${interfaceName}-peer-${unitName}" </del> <ins> dynamicRefreshEnabled = peer.dynamicEndpointRefreshSeconds != 0; # We generate a different name (a `-refresh` suffix) when `dynamicEndpointRefreshSeconds` # to avoid that the same service switches `Type` (`oneshot` vs `simple`), # with the intent to make scripting more obvious. serviceName = peerUnitServiceName interfaceName peer.publicKey dynamicRefreshEnabled; in nameValuePair serviceName </ins> { description = "WireGuard Peer - ${interfaceName} - ${peer.publicKey}"; requires = [ "wireguard-${interfaceName}.service" ];

Discussion:
On NixOS 20.09, steps to reproduce the behavior: setting up wireguard, change to another port still shows the old port:
This seems to be fixed by my PR
Change:
cat ${escapeShellArgs cfg.hostFiles} > $out ''; <ins> # /etc/netgroup: Network-wide groups. netgroup.text = mkDefault '' ''; </ins> # /etc/host.conf: resolver configuration file "host.conf".text = '' multi on

Discussion:
Describe the bug I'm a little bit unsure if this is a bug or an expected behavior. At least is stumbled over it during my NixOS evaluation. At least it's a little bit disturbing when evaluating logs. To Reproduce Default installation of NixOS 19.03. Expected behavior Option 1) should disable caching Option 2) If no file exist an empty one should be created
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:
<ins> { lib, rustPlatform, fetchFromGitHub , fetchpatch , fuse , pkg-config }: rustPlatform.buildRustPackage rec { pname = "catfs"; version = "unstable-2020-03-21"; src = fetchFromGitHub { owner = "kahing"; repo = pname; rev = "daa2b85798fa8ca38306242d51cbc39ed122e271"; sha256 = "0zca0c4n2p9s5kn8c9f9lyxdf3df88a63nmhprpgflj86bh8wgf5"; }; cargoSha256 = "0v6lxwj4vcph32np68awpncafvf1dwcik9a2asa0lkb7kmfdjsjk"; cargoPatches = [ # update cargo lock (fetchpatch { url = "https://github.com/kahing/catfs/commit/f838c1cf862cec3f1d862492e5be82b6dbe16ac5.patch"; sha256 = "1r1p0vbr3j9xyj9r1ahipg4acii3m4ni4m9mp3avbi1rfgzhblhw"; }) ]; nativeBuildInputs = [ pkg-config ]; buildInputs = [ fuse ]; # require fuse module to be active to run tests # instead, run command doCheck = false; doInstallCheck = true; installCheckPhase = '' $out/bin/catfs --help > /dev/null ''; meta = with lib; { description = "Caching filesystem written in Rust"; homepage = "https://github.com/kahing/catfs"; license = licenses.asl20; platforms = platforms.linux; maintainers = with maintainers; [ jonringer ]; }; } </ins>

Discussion:
Project description caching file-system, written in rust. Designed to work with Metadata homepage URL: source URL: license: Apache2 platforms: unix, linux, darwin
I don't see any activity for 6+ months, I think I should close my PR and this ticket
I didn't mean activity in my PR, I meant in the upstream repo
Change:
openfortivpn = callPackage ../tools/networking/openfortivpn { }; <del> opensnitch = callPackage ../tools/networking/opensnitch/daemon.nix { }; </del> <ins> opensnitch = callPackage ../tools/networking/opensnitch/daemon.nix { # Build currently fails on Go > 1.18 # See https://github.com/evilsocket/opensnitch/issues/851 buildGoModule = buildGo118Module; }; </ins> opensnitch-ui = libsForQt5.callPackage ../tools/networking/opensnitch/ui.nix { };

Discussion:
Steps to reproduce the behavior: opensnitch against nixos-unstable Probably related to the recent bump to gcc 12. Please run and paste the result.
Change:
(optionalString (cfg.defaultMode == "norouting") "--routing=none") ] ++ cfg.extraFlags); <ins> profile = if cfg.localDiscovery then "local-discovery" else "server"; </ins> splitMulitaddr = addrRaw: lib.tail (lib.splitString "/" addrRaw); multiaddrToListenStream = addrRaw:

Discussion:
ipfs-pre-start hangs on on startup. ??? sometimes (quite often) it hangs on startup. IPFS starts up successfully. Startup can be forced via There were no migrations that needed to be run. Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(kevincox): channels(root): nixpkgs: Maintainer information:
I tried to debug further and didn't get far: So works but fails the command. Maybe we can just try to run this command for now, ignoring failures. At least it won't indefinitely block startup. No matter what args I give I can't get any more than that first log message.
Sounds like we probably need to report this upstream.
I found a workaround. Run then you can apply profiles again. It sounds like sometimes the daemon isn't shutting down cleanly or something. I think the daemon was sometime hung and had to be killed so maybe that is the problem.
Sounds like an IPFS bug where isn't cleaning up a crashed state properly. We can consider a terrible workaround like doing something like this at startup.
I've reported the issue upstream:
Change:
}; nativeBuildInputs = [ autoreconfHook bison flex pkgconfig perl ]; <del> buildInputs = [ libuuid cppunit protobuf3_1 zlib avahi libmicrohttpd python3 ]; </del> <ins> buildInputs = [ libuuid cppunit protobuf3_1 zlib avahi libmicrohttpd python36 ]; </ins> propagatedBuildInputs = [ <del> (python3Packages.protobuf.override { protobuf = protobuf3_1; }) python3Packages.numpy </del> <ins> (python36.pkgs.protobuf.override { protobuf = protobuf3_1; }) python36.pkgs.numpy </ins> ]; configureFlags = [ "--enable-python-libs" ];

Discussion:
Hi ! When I upgrade my Nixos on unstable channel, I can see a build error for python3.7-protobuf. How can I debug this ? How can I known which packet should I debug ? nixos-rebuild build --upgrade (with nixos unstable channel) system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The package that's broken is . You will see in that the protobuf python package is overridden: It seems like OLA will support Protobuf 3.6 only after the next update: I've opened to address the issue.
Change:
}; enableParallelBuilding = true; <del> inherit enableMultilib; </del> <ins> inherit enableMultilib enableShared; </ins> inherit (stdenv) is64bit;

Discussion:
EDIT: I am also getting this now trying to build in CI under Linux To Reproduce Screenshots 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:
Looks like this is also similar to and and
As I mentioned in the audiofile ticket, my attempted workaround is this: However this doesn't appear to work because the .la files are not generated by the time of the preBuild hook. Can anyone help with this?
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I marked this as stale due to inactivity. &rarr;
Change:
doit pygments pillow dateutil docutils Mako markdown unidecode lxml Yapsy PyRSS2Gen Logbook blinker natsort requests piexif Babel # requirements-extras.txt <del> phpserialize jinja2 toml notebook ruamel_yaml </del> <ins> phpserialize jinja2 toml notebook ruamel_yaml aiohttp watchdog </ins> ]; src = fetchPypi {

Discussion:
system: host os: multi-user?: sandbox: version: channels(davidak): channels(root): nixpkgs:
Feel free to make a PR adding these two as dependencies.