jiebi/CodeConvo huggingface dataset:
Change:
{ lib , stdenv <del> , buildPythonPackage </del> , aiohttp , aioresponses <ins> , buildPythonPackage </ins> , cachetools , cryptography , fetchPypi

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: -
Hmm I'm not quite sure if urllib3 should be to on or on
Change:
license = licenses.gpl1Plus; homepage = "https://github.com/dave-theunsub/clamtk"; platforms = platforms.linux; <del> maintainers = with maintainers; [ jgarcia ]; </del> <ins> maintainers = with maintainers; [ jgarcia ShamrockLee ]; </ins> }; }

Discussion:
When executing with , it complains that . Maybe the package needs to be wrapped with some environment variables set or patched against hard-coding or something. Steps to reproduce the behavior: ClamTk runs with . ! ]() 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.
I can't seem to reproduce this. Have run both on nixos and nix on another linux. Can you give me some more info? Does the program work and run correctly? Is it missing any icons (screenshot?). What desktop are you running? Many thanks.
It exits with exit status 2 right after the command being invoked inside the terminal emulator and the error message printed out. No window is shown. The desktop environment I use is LxQt, which inherently doesn't come with the KDE breeze icons. The screenshot and the Asciinema cast is updated into the issue description.
I switched my DE over to LxQt and everything worked for me. Basically the error is between the program logic (it shouldn't crash if it can't find icon files) and your DE set-up (it should provide the correct icon files). It's not a packaging error as far as I can tell. So you could try either: 1. messing around with your DE settings, 2. trying another DE and / or 3. filing a bug report upstream to clamtk. !
p.s. I wonder if this could just be fixed by installing some icons? You could try installing and / or on your system and see if that helps.
Change:
wantedBy    = [ "multi-user.target" ]; serviceConfig = { <del> ExecStart = "${pkgs.hologram}/bin/hologram-server --debug --conf ${cfgFile}"; </del> <ins> ExecStart = "${pkgs.hologram.bin}/bin/hologram-server --debug --conf ${cfgFile}"; </ins> }; }; };

Discussion:
NixOS services that depend on binaries are now broken (eg ) after This is because the attribute path for binaries has now changed. For example should now be .
I can do it tomorrow.
Change:
changelog = "https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/plain/NEWS?h=v${version}"; license = with licenses; [ lgpl21Plus gpl2Plus ]; # GPLv2+ for tools platforms = platforms.unix; <ins> maintainers = with maintainers; [ artturin ]; </ins> }; }

Discussion:
After update can't properly reload zram module. Reproducible only with . journalctl -eu zram-reloader.service Steps to reproduce the behavior: zram and switch to ; ; switch to ; the logs. Successful module reload. None. None. Maintainer information:
i assume a reboot fixed this? its probably because the booted kernel and the updated kernel versions mismatched i suspect that this line may be causing it it was in this pr but it states that extra info at
Yes, after reboot everything works fine.
is different from what it was in nix-info ?
No. The system has already been rebooted after the update.
I can't find in paths: It is there where the kernel is:
find doesn't work with symlinks fd with -L does
i got this same issue and before rebooting i tested changing the path order in kmod expr and it worked
Progress of the pr can be tracked at
Change:
"stylelint-prettier": "^2.0.0" }, "name": "Zammad", <del> "version": "5.1.0" </del> <ins> "version": "5.1.1" </ins> }

Discussion:
, CVSSv3=7.5 (nixos-unstable) CVSSv3=7.5 (nixos-unstable) A lack of password length restriction in Zammad v5.1.0 allows for the creation of extremely long passwords which can cause a Denial of Service (DoS) during password verification. A lack of rate limiting in the 'forgot password' feature of Zammad v5.1.0 allows attackers to send an excessive amount of reset requests for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages. Scanned versions: nixos-unstable: . Cc Cc Cc
Change:
, subversion, glibcLocales, sshSupport ? true, openssh ? null }: <del> { url, rev ? "HEAD", md5 ? "", sha256 ? "" </del> <ins> { url, rev ? "HEAD", md5 ? "", sha256 ? "", hash ? "" </ins> , ignoreExternals ? false, ignoreKeywords ? false, name ? null , preferLocalBuild ? true }:

Discussion:
Most of fetchers are using as possible hash parameter, but fetchsvn is not.
See also the discussion in
I marked this as stale due to inactivity. &rarr;
Change:
aarch64-darwin = "darwin-arm64"; }.${system} or (throw "Unsupported system ${system}"); <ins> esbuild' = esbuild.override { buildGoModule = args: buildGoModule (args // rec { version = "0.16.17"; src = fetchFromGitHub { owner = "evanw"; repo = "esbuild"; rev = "v${version}"; hash = "sha256-8L8h0FaexNsb3Mj6/ohA37nYLFogo5wXkAhGztGUUsQ="; }; vendorHash = "sha256-+BfxCyg0KkDQpHt/wycy/8CTG6YBA/VJvJFhhzUnSiQ="; }); }; </ins> # replaces esbuild's download script with a binary from nixpkgs patchEsbuild = path : version : '' mkdir -p ${path}/node_modules/esbuild/bin jq "del(.scripts.postinstall)" ${path}/node_modules/esbuild/package.json | sponge ${path}/node_modules/esbuild/package.json <del> sed -i 's/${version}/${esbuild.version}/g' ${path}/node_modules/esbuild/lib/main.js ln -s -f ${esbuild}/bin/esbuild ${path}/node_modules/esbuild/bin/esbuild </del> <ins> sed -i 's/${version}/${esbuild'.version}/g' ${path}/node_modules/esbuild/lib/main.js ln -s -f ${esbuild'}/bin/esbuild ${path}/node_modules/esbuild/bin/esbuild </ins> ''; in stdenv.mkDerivation rec {

Discussion:
Steps to reproduce the behavior: or see: Can someone nail the problem down to a specific pr or commit? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Broken because of PR
Now broken because is insecure.
waiting for as nodejs 18 migration is blocked
Change:
# SourceForge. sourceforge = [ <ins> http://downloads.sourceforge.net/ </ins> http://prdownloads.sourceforge.net/ http://heanet.dl.sourceforge.net/sourceforge/ http://surfnet.dl.sourceforge.net/sourceforge/

Discussion:
Multiple packages are broken over using links which are temporary. Some directly refer to a specific mirror so they succeed so long as the server isn't down-throttled by sourceforge. Others are completely broken. The correct syntax for sourceforge source packages should be "mirror://sourceforge/...". The following is a partial list compiled from git grep | grep tar and some light manual editing. It might have false negatives and there could be other offending packages that aren't listed: Also note that occasionally sourceforge crashes to "disaster recovery mode" and requires javascript to download tarballs.
Is adding a travis check to prevent addition of links a good idea?
The problem is that is actually the official way to download tarballs from SourceForge. What makes it so unreliable is the same ticketing and load-balancing system SourceForge wants us to use... That's to say, before modifying travis, the list in pkgs/build- should be edited to start with the official to give SF a chance to regulate itself, and only fallback on the known servers list if the download fails or hangs.
No wonder people don't like SF. :/ Okay, I'm opening a new PR to update mirrors. Will follow up with editing out the links to use mirrors, and then add a travis job to enforce the convention.
We actually lucked out here. Windows users get their binaries packed with extra malware... Sounds great :) I'll close this issue now that you're on it. Thanks!
Change:
nativeBuildInputs = [ autoreconfHook ]; patches = [ ./no-var-spool-install.patch ]; <ins> postPatch = '' substituteInPlace libuptimed/urec.h  --replace /var/spool /var/lib ''; </ins> meta = with lib; { description = "Uptime record daemon"; longDescription = ''

Discussion:
Despite beeing installed for a few days now: it seems like the uptimed service does not find its database properly and prints just the current uptime. I guess this is because the database file gets recreated every boot. But that's only a shot into the blue guess. System: 17.03pre99626. (Gorilla) Nix version: nix-env (Nix) 1.11.6 Nixpkgs version: "17.03pre99626."
Some logs from the journal: Pinging maintainers of the service (there is no maintainer in the pkg):
Probably a permission problem or the said directory does not exists.
Yep, looks like it,... though I have no time to investigate, so I'll just leave this here and hope it gets fixed.
In the meantime you can use this one instead:
:smile:
Still no love for this?
Still no love for this?
Does the following (untested) code help?
Tried yours and but fails with: tested on System: 18.03pre124015. (Impala) Nix version: nix-env (Nix) 1.11.16 Nixpkgs version: "18.03pre124015." Sandboxing enabled: build-use-sandbox = true (diff applied on )
It seems that it did not saved my updated change (I forgot to prefix first)
I know nothing about , sorry.
close as unresolved?
Closed as unresolved.
The issue is still present under 18.09 and (I presume) as  does not seem to contain any of the changes proposed here. Why is this issue closed?
Because I do not care anymore and nobody else seems to care either. Do you want me to reopen?
I probably do. I have some extra details on the issue: So it seems that the user cannot write to the directory even though it owns it.
It seems that is a workaround. Not sure about its safety though.
So now it works, but in a roundabout way: The next steps are making the directory world-readable and bringing into user scope.
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 . on the on .
As people seemed to interested in this and it is a bug: still important to me
Should be made a tmpfiles rule or if possible changed to /var/lib/uptime, in which case we can set .
I marked this as stale due to inactivity. &rarr;
Change:
if (!defined($action) || ($action ne "switch" && $action ne "boot" && $action ne "test" && $action ne "dry-activate")) { print STDERR <<"EOF"; <del> Usage: $0 [switch|boot|test] </del> <ins> Usage: $0 [switch|boot|test|dry-activate] </ins> switch:       make the configuration the boot default and activate now boot:         make the configuration the boot default

Discussion:
The script is apparently trying to stop and start changed .mount units, presumably to cause a ? If that happens the script fails and the new configuration is not activated. Worse, the system is left in a broken state with some of the stopped (as part of the switch) units never restarted. Steps to reproduce the behavior: the value of , for example from to . The unit should probably not be stopped and the switch should succeed. If using remotely also the SSH connection drops. NixOS version: 23.05.1194. (Stoat) The filesystem entry is: cc:
I just ran into this error myself. I am unsure of which configuration change caused this. But I was changing config and I think was saying some setting conflicts with my , which was at . So I updated to and then flashed me this error: before giving me a black screen and send me to the login prompt.
were you ever able to fix your issue?
No fix, I'm pretty sure changing the unit will still trigger a stop.
Unfortunately, you are correct. I do have a fix in the pipeline though. improves the handling of mount units () and I plan to adapt this to fstab mounts as well (). This is currently being blocked by the fstab parser not having any tests but I plan on writing them. Will keep this issue in mind.
Now that I look at the code again… it already looks correct. Can someone with this issue post a diff of their fstab? Something like should do.
Change:
meta.homepage = "https://github.com/chikamichi/mediawiki.vim/"; }; <ins> melange-nvim = buildVimPluginFrom2Nix { pname = "melange-nvim"; version = "2023-04-06"; src = fetchFromGitHub { owner = "savq"; repo = "melange-nvim"; rev = "f15922543dd70b360335effb61411c05c710b99c"; sha256 = "19swmv0xzlxp7bcmgdm2qfam28wi9igqvfn5q7wq8qshb2wqzph1"; }; meta.homepage = "https://github.com/savq/melange-nvim/"; }; </ins> mini-nvim = buildVimPluginFrom2Nix { pname = "mini.nvim"; version = "2023-05-07";

Discussion:
Project description Warm color scheme for Neovim and beyond Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ...
Change:
pkg-config clang ffmpeg <ins> makeWrapper </ins> ]; buildInputs = [

Discussion:
I think this is not actually a build failure, but it does make the package unusable without manually specifying an additional dependency. Steps to reproduce the behavior: using the package on a system without a pre-existing ffprobe installation (for example in a ) on a local mp4 or png file To try and solve the problem, I read the error message and tried to install ffprobe, so I searched for in nix packages, and tried re-running with the first result : , and it worked fine. So I hope the fix is trivial and can be done quickly. As I'm a newcomer to nix and NixOS, I prefer not to try and fix it myself, but i'll make sure to read the PR to hopefully by able to make such a simple fix myself next time <!-- 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]:
Change:
"github:vim-scripts/a.vim" "github:vim-scripts/align" "github:vim-scripts/tabmerge" <ins> "github:vim-scripts/wombat256.vim" </ins> "github:wakatime/vim-wakatime" "github:wincent/command-t" "matchit.zip"

Discussion:
nixpkgs version: nixos-unstable (rev: ) configuration: steps: error: If I remove the wombat256 plugin from my configuration, then vim-env builds fine. Currently, wombat256 seems to be the only plugin in nixpkgs affected by this issue. However, I have auto-generated another plugin which is also affected. What these two plugins have in common is that they are both using , and are downloading files rather than archives. cc
Isn't it a better idea to download those plugins from github? And add them to as ? Because I personally don't like fetching from vim site. I can change the behavior to load them from vim-scripts repo.
Yes, downloading from github works well and is better I think. I'll update wombat256 and use github when adding plugins from now on.
Change:
''; description = '' Extra configuration lines appended to the network block. <del> See wpa_supplicant.conf(5) for available options. </del> <ins> See <citerefentry> <refentrytitle>wpa_supplicant.conf</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> for available options. </ins> ''; };

Discussion:
References to (5) should have hyperlinks to the article/section.
These are references to man pages so there can't easily be a hyperlink. I made a PR that makes sure these are referenced to using , though. So that they at least carry some semantic meaning.
My bad I didn't think about the man pages. There are man pages online, too. I found this site: but it'd be nice to have them generated into the NixOS documentation. Having the man page sources piped into HTML would be useful I not a huge space waster.
Change:
sourceProvenance = listOf lib.types.attrs; maintainers = listOf (attrsOf anything); # TODO use the maintainer type from lib/tests/maintainer-module.nix priority = int; <del> platforms = listOf (oneOf [ str (attrsOf anything) (functionTo bool) ]);   # see lib.meta.platformMatch </del> <ins> platforms = listOf (either str (attrsOf anything));   # see lib.meta.platformMatch </ins> hydraPlatforms = listOf str; broken = bool; unfree = bool;

Discussion:
I am working on this bug. First reported . The root cause of the problem is that there is no "pattern" (see ) representation for . It is special, unlike all the other platform predicates. It is this way because exists, and because ... in other words, "static-ness" is not represented in the triple for a platform. Right now we try to pretend that you can reconstruct all the pattern-representable aspects of a from its . That isn't really true, because of and , and it's getting more untrue as time goes on. The long-term solution is to stop pretending. I have a possible short-term fix that I'm testing.
Change:
<del> { lib, buildGoModule, fetchFromGitHub, testers, notation }: </del> <ins> { lib, buildGoModule, fetchFromGitHub, installShellFiles, testers, notation }: </ins> buildGoModule rec { pname = "notation";

Discussion:
After installation notation shell completion is not available. Steps to reproduce the behavior: notation completion Shell completion should be installed. N/A N/A <!-- 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]:
Change:
cp ./bazel_src/scripts/packages/bazel.sh $out/bin/bazel mv ./bazel_src/output/bazel $out/bin/bazel-real <del> wrapProgram "$out/bin/bazel" --add-flags --server_javabase="${runJdk}" # generates the system bazelrc # warning: the name of the repository depends on the system, hence # the reference to .name mkdir $out/etc echo "build --override_repository=${remote_java_tools.name}=${remote_java_tools}" > $out/etc/bazelrc echo "build --distdir=${distDir}" >> $out/etc/bazelrc </del> # shell completion files mkdir -p $out/share/bash-completion/completions $out/share/zsh/site-functions mv ./bazel_src/output/bazel-complete.bash $out/share/bash-completion/completions/bazel

Discussion:
Describe the bug By default and according to bazel documentation (), bazel is looking for a system-wide configuration is . In I decided to override this path and make it point in . It was the easiest solution to pass arguments to bazel in order to fix a few runtime issues. However it breaks the assumption that user can configure bazel using . To Reproduce Use bazel from nixpkgs with . Set some bazel settings in your file Observe that bazel ignores this file Expected behavior I'm opening this bug report to discuss what should be the expected behavior here? Should we respect the ? If yes, I'll open a pull request to restore the previous behavior.
I'll be in favour of keeping support for all paths specified in the documentation - having a system-wide is something people might want to make use of, so we shouldn't take away that possibility. We currently set the following options in bazelrc: We should either patch these as defaults into nixos, or introduce reading from a distro-provided location (should be coordinated with bazel upstream). I think adding a wrapper is a bit too much for all these options.
I do agree with your point of view. I'll try to propose a PR which restore the old behavior. In the meantime, I'm open to other comments on this issue. Regarding the options you quote, they are used in a local during build only. The global bazelrc that I provide is way simpler: Both were ad hoc solution for different problems, respectively issue and commit .
Change:
<ins> { lib , buildDotnetModule , fetchFromGitHub , dotnetCorePackages , gtk4 , libadwaita , pkg-config , wrapGAppsHook4 , glib , shared-mime-info , gdk-pixbuf , blueprint-compiler , python3 , ffmpeg }: buildDotnetModule rec { pname = "parabolic"; version = "2023.12.0"; src = fetchFromGitHub { owner = "NickvisionApps"; repo = "Parabolic"; rev = version; hash = "sha256-mbGByw/wgovo81l2LDtDE5p+Mh6aJ5DOcZCNzVfmAtA="; fetchSubmodules = true; }; dotnet-sdk = dotnetCorePackages.sdk_8_0; dotnet-runtime = dotnetCorePackages.runtime_8_0; pythonEnv = python3.withPackages(ps: with ps; [ yt-dlp ]); projectFile = "NickvisionTubeConverter.GNOME/NickvisionTubeConverter.GNOME.csproj"; nugetDeps = ./deps.nix; executables = "NickvisionTubeConverter.GNOME"; nativeBuildInputs = [ pkg-config wrapGAppsHook4 glib shared-mime-info gdk-pixbuf blueprint-compiler ]; buildInputs = [ gtk4 libadwaita ]; runtimeDeps = [ gtk4 libadwaita glib gdk-pixbuf ]; postPatch = '' substituteInPlace NickvisionTubeConverter.Shared/Linux/org.nickvision.tubeconverter.desktop.in --replace '@EXEC@' "NickvisionTubeConverter.GNOME" ''; postInstall = '' install -Dm444 NickvisionTubeConverter.Shared/Resources/org.nickvision.tubeconverter.svg -t $out/share/icons/hicolor/scalable/apps/ install -Dm444 NickvisionTubeConverter.Shared/Resources/org.nickvision.tubeconverter-symbolic.svg -t $out/share/icons/hicolor/symbolic/apps/ install -Dm444 NickvisionTubeConverter.Shared/Linux/org.nickvision.tubeconverter.desktop.in -T $out/share/applications/org.nickvision.tubeconverter.desktop ''; makeWrapperArgs = [ "--prefix PATH : ${lib.makeBinPath [ pythonEnv ffmpeg ]}" ]; passthru.updateScript = ./update.sh; meta = with lib; { description = "Download web video and audio"; homepage = "https://github.com/NickvisionApps/Parabolic"; license = licenses.mit; maintainers = with maintainers; [ ewuuwe ]; mainProgram = "parabolic"; platforms = platforms.linux; }; } </ins>

Discussion:
Project description A GUI for yt-dlp A basic yt-dlp frontend () Supports downloading videos in multiple formats (mp4, webm, mp3, opus, flac, and wav) Run multiple downloads at a time Supports downloading metadata and video subtitles Metadata homepage URL: source URL: license: mit, platforms: linux
Change:
opencv ]; <ins> postFixup = '' wrapProgram $out/bin/tplay  --prefix PATH : "${lib.makeBinPath [ ffmpeg ]}" ''; </ins> meta = { description = "Terminal Media Player"; homepage = "https://github.com/maxcurzi/tplay"; platforms = lib.platforms.linux; license = lib.licenses.mit; <del> maintainers = with lib.maintainers; [ demine colemickens ]; </del> <ins> maintainers = with lib.maintainers; [ demine colemickens ]; </ins> }; }

Discussion:
I think this is not actually a build failure, but it does make the package unusable without manually specifying an additional dependency. Steps to reproduce the behavior: using the package on a system without a pre-existing ffprobe installation (for example in a ) on a local mp4 or png file To try and solve the problem, I read the error message and tried to install ffprobe, so I searched for in nix packages, and tried re-running with the first result : , and it worked fine. So I hope the fix is trivial and can be done quickly. As I'm a newcomer to nix and NixOS, I prefer not to try and fix it myself, but i'll make sure to read the PR to hopefully by able to make such a simple fix myself next time <!-- 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]: