jiebi/CodeConvo huggingface dataset:
Code change:
Describe the bug sysklogd fails to build when built against musl-libc To Reproduce Steps to reproduce the behavior: Expected behavior Package should build. Notify maintainers no maintainers, because apparently this is ancient. Metadata Maintainer information:

Related discussion:
text: +#include <sys/stat.h> +#include <sys/socket.h> +#include <sys/un.h> <del> +#include <sys/fcntl.h> </del> +#include <netinet/in.h> +#include <stdlib.h> <ins> +#include <fcntl.h> </ins> +#include <errno.h> +#include <unistd.h> +#include <string.h>
Code change:
I tried adding to , then running and noticed in the diff this still uses , and non-string URLs. To Reproduce Steps to reproduce the behavior: Expected behavior The diff shouldn't contain non-string URLs, and not use via . Notify maintainers
luarocks-nix needs to be updated. Its current state is messy (not clear which branch to use), I will update it.

Related discussion:
text: binaryheap,,,,,vcunat bit32,,,,lua5_1,lblasc busted,,,,, <del> cassowary,,,,,marsam </del> <ins> cassowary,,,,,marsam alerque </ins> cjson,lua-cjson,,,, compat53,,,,,vcunat cosmo,,,,,marsam
Code change:
I tried adding to , then running and noticed in the diff this still uses , and non-string URLs. To Reproduce Steps to reproduce the behavior: Expected behavior The diff shouldn't contain non-string URLs, and not use via . Notify maintainers
luarocks-nix needs to be updated. Its current state is messy (not clear which branch to use), I will update it.

Related discussion:
text: These packages are manually refined in lua-overrides.nix */ <del> { self, stdenv, fetchurl, fetchgit, pkgs, ... } @ args: </del> <ins> { self, stdenv, lib, fetchurl, fetchgit, pkgs, ... } @ args: </ins> self: super: with self; {
Code change:
I tried adding to , then running and noticed in the diff this still uses , and non-string URLs. To Reproduce Steps to reproduce the behavior: Expected behavior The diff shouldn't contain non-string URLs, and not use via . Notify maintainers
luarocks-nix needs to be updated. Its current state is messy (not clear which branch to use), I will update it.

Related discussion:
text: These packages are manually refined in lua-overrides.nix */ <del> { self, lib, stdenv, fetchurl, fetchgit, pkgs, ... } @ args: </del> <ins> { self, stdenv, lib, fetchurl, fetchgit, pkgs, ... } @ args: </ins> self: super: with self; {
Code change:
I tried adding to , then running and noticed in the diff this still uses , and non-string URLs. To Reproduce Steps to reproduce the behavior: Expected behavior The diff shouldn't contain non-string URLs, and not use via . Notify maintainers
luarocks-nix needs to be updated. Its current state is messy (not clear which branch to use), I will update it.

Related discussion:
text: { luarocks, fetchFromGitHub }: luarocks.overrideAttrs(old: { pname = "luarocks-nix"; <del> version = "2019-09-07"; </del> <ins> version = "2021-01-22"; </ins> src = fetchFromGitHub { owner = "nix-community"; repo = "luarocks-nix"; <del> rev = "73b8772e56fd39dfffda9e3b13e9eb31e93d5cde"; sha256 = "00jgshygw439pbaxg7yph3ijia6nid9r1br416wdbyl5wqhlhm1y"; </del> <ins> rev = "v3.5.0_nix"; sha256 = "sha256-Ea3PVkCaUPO/mvVZtHtD1G9T/Yom28M9oN6duY4ovHk="; </ins> }; <del> patches = [ ./darwin-3.1.3.patch ]; </del> })
Code change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.5.2 desired version: 1.8.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
I managed to use this overlay for now:
could you please take for a test run? Thanks
Checked out the branch and it seems to be working :smile:

Related discussion:
text: <del> { stdenv, lib, fetchFromGitHub, autoreconfHook, makeWrapper, pkg-config , zlib, lzma, bzip2, mtools, dosfstools, zip, unzip, libconfuse, libsodium , libarchive, darwin, coreutils }: </del> <ins> { stdenv , lib , fetchFromGitHub , autoreconfHook , DiskArbitration , pkg-config , bzip2 , libarchive , libconfuse , libsodium , lzma , zlib , coreutils , dosfstools , mtools , unzip , zip , which , xdelta }: </ins> stdenv.mkDerivation rec { pname = "fwup"; <del> version = "1.5.2"; </del> <ins> version = "1.8.3"; </ins> src = fetchFromGitHub { owner = "fhunleth"; repo = "fwup"; rev = "v${version}"; <del> sha256 = "05sjdlh450hk474a44yr6kz9dzx72jfxpi1krxbd0pdizlmfypsg"; </del> <ins> sha256 = "sha256-ayfcnIZ7MuBsCy1giwmY2D2C6AukwS+fevmXqGa4c1w="; </ins> }; <del> doCheck = true; patches = lib.optional stdenv.isDarwin [ ./fix-testrunner-darwin.patch ]; </del> <ins> patches = [ ./fix-testrunner-darwin.patch ]; nativeBuildInputs = [ autoreconfHook pkg-config ]; </ins> <del> nativeBuildInputs = [ pkg-config autoreconfHook makeWrapper ]; buildInputs = [ zlib lzma bzip2 libconfuse libsodium libarchive ] </del> <ins> buildInputs = [ bzip2 libarchive libconfuse libsodium lzma zlib ] </ins> ++ lib.optionals stdenv.isDarwin [ <del> darwin.apple_sdk.frameworks.DiskArbitration ]; propagatedBuildInputs = [ zip unzip mtools dosfstools coreutils ]; </del> <ins> DiskArbitration ]; propagatedBuildInputs = [ coreutils dosfstools mtools unzip zip ]; checkInputs = [ which xdelta ]; doCheck = true; </ins> meta = with lib; { description = "Configurable embedded Linux firmware update creator and runner";
Code change:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.5.2 desired version: 1.8.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
I managed to use this overlay for now:
could you please take for a test run? Thanks
Checked out the branch and it seems to be working :smile:

Related discussion:
text: qt-video-wlr = libsForQt5.callPackage ../applications/misc/qt-video-wlr { }; <del> fwup = callPackage ../tools/misc/fwup { }; </del> <ins> fwup = callPackage ../tools/misc/fwup { inherit (darwin.apple_sdk.frameworks) DiskArbitration; }; </ins> fx_cast_bridge = callPackage ../tools/misc/fx_cast { };
Code change:
Describe the bug fails to build on master and unstable Notify maintainers
could you please take a look at ?
Thanks

Related discussion:
text: , isPy3k , lxml , pillow <ins> , psutil </ins> , pybind11 <del> , pytestCheckHook </del> <ins> , pytest-cov </ins> , pytest-helpers-namespace , pytest-timeout <del> , pytest_xdist , pytestrunner </del> <ins> , pytest-xdist , pytestCheckHook </ins> , python-dateutil , python-xmp-toolkit <del> , python3 </del> , qpdf <ins> , setuptools-scm </ins> , setuptools-scm-git-archive <del> , setuptools_scm , lib </del> }: buildPythonPackage rec { pname = "pikepdf"; <del> version = "2.2.0"; </del> <ins> version = "2.5.2"; </ins> disabled = ! isPy3k; src = fetchPypi { inherit pname version; <del> sha256 = "74300a32c41b3d578772f6933f23a88b19f74484185e71e5225ce2f7ea5aea78"; </del> <ins> sha256 = "sha256-j8PpeyTa+9SxrAV8jxRMGEZ85V00KhqMQmiIkOrVjvM="; </ins> }; buildInputs = [
Code change:
Describe the bug fails to build on master and unstable Notify maintainers
could you please take a look at ?
Thanks

Related discussion:
text: nativeBuildInputs = [ setuptools-scm-git-archive <del> setuptools_scm </del> <ins> setuptools-scm </ins> ]; checkInputs = [ attrs hypothesis <del> pillow pytestCheckHook </del> pytest-helpers-namespace pytest-timeout <del> pytest_xdist pytestrunner </del> <ins> pytest-xdist psutil pytest-cov pytestCheckHook </ins> python-dateutil python-xmp-toolkit ]; <del> propagatedBuildInputs = [ defusedxml lxml ]; postPatch = '' sed -i  -e 's/^pytest .*/pytest/g'  -e 's/^attrs .*/attrs/g'  -e 's/^hypothesis .*/hypothesis/g'  requirements/test.txt ''; </del> <ins> propagatedBuildInputs = [ defusedxml lxml pillow ]; </ins> preBuild = '' HOME=$TMPDIR ''; <ins> pythonImportsCheck = [ "pikepdf" ]; </ins> meta = with lib; { homepage = "https://github.com/pikepdf/pikepdf"; description = "Read and write PDFs with Python, powered by qpdf";
Code change:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. Screenshots If applicable, add screenshots to help explain your problem. 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 Please run and paste the result. Maintainer information:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform

Related discussion:
text: mkdir -p $out/${gimp.targetScriptDir}/${name}; for p in "$@"; do cp "$p" -r $out/${gimp.targetScriptDir}/${name}; done } <del> installPlugins(){ mkdir -p $out/${gimp.targetPluginDir}/${name}; for p in "$@"; do cp "$p" -r $out/${gimp.targetPluginDir}/${name}; done </del> <ins> installPlugin() { # The base name of the first argument is the plug-in name and the main executable. # GIMP only allows a single plug-in per directory: # https://gitlab.gnome.org/GNOME/gimp/-/commit/efae55a73e98389e38fa0e59ebebcda0abe3ee96 pluginDir=$out/${gimp.targetPluginDir}/$(basename "$1") install -Dt "$pluginDir" "$@" </ins> } '';
Code change:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. Screenshots If applicable, add screenshots to help explain your problem. 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 Please run and paste the result. Maintainer information:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform

Related discussion:
text: Filters/Generic/FFT Forward Filters/Generic/FFT Inverse */ <del> name = "fourier-0.4.3"; buildInputs = with pkgs; [ fftw ]; </del> <ins> pname = "fourier"; version = "0.4.3"; </ins> src = fetchurl { <del> url = "https://www.lprp.fr/files/old-web/soft/gimp/${name}.tar.gz"; </del> <ins> url = "https://www.lprp.fr/files/old-web/soft/gimp/${pname}-${version}.tar.gz"; </ins> sha256 = "0mf7f8vaqs2madx832x3kcxw3hv3w3wampvzvaps1mkf2kvrjbsn"; }; <del> installPhase = "installPlugins fourier"; </del> <ins> buildInputs = with pkgs; [ fftw ]; postPatch = '' # The tarball contains a prebuilt binary. make clean ''; installPhase = '' runHook preInstall installPlugin fourier runHook postInstall ''; </ins> meta = with lib; { description = "GIMP plug-in to do the fourier transform";
Code change:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. Screenshots If applicable, add screenshots to help explain your problem. 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 Please run and paste the result. Maintainer information:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform

Related discussion:
text: rev = "de4367f71e40fe6d82387eaee68611a80a87e0e1"; sha256 = "1zzvbczly7k456c0y6s92a1i8ph4ywmbvdl8i4rcc29l4qd2z8fw"; }; <del> installPhase = "installPlugins src/texturize"; </del> <ins> installPhase = "installPlugin src/texturize"; </ins> meta.broken = true; # https://github.com/lmanul/gimp-texturize/issues/1 };
Code change:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. Screenshots If applicable, add screenshots to help explain your problem. 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 Please run and paste the result. Maintainer information:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform

Related discussion:
text: url = "https://github.com/pixlsus/registry.gimp.org_static/raw/master/registry.gimp.org/files/wavelet-sharpen-0.1.2.tar.gz"; sha256 = "0vql1k67i21g5ivaa1jh56rg427m0icrkpryrhg75nscpirfxxqw"; }; <del> installPhase = "installPlugins src/wavelet-sharpen"; # TODO translations are not copied .. How to do this on nix? </del> <ins> installPhase = "installPlugin src/wavelet-sharpen"; # TODO translations are not copied .. How to do this on nix? </ins> }; lqrPlugin = pluginDerivation rec {
Code change:
Describe the bug I'm adding gimp like this in 20.09: However the fourier plugin is not being recognized. It should add: Filters/Generic/Forward FFT Filters/Generic/Inverse FFT But these filters are missing. Expected behavior FFT plugin should be recognized by gimp. Screenshots If applicable, add screenshots to help explain your problem. 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 Please run and paste the result. Maintainer information:
I'm not sure about these specific plugins, but gimp-with-plugins comes with G'MIC, which includes a FFT filter under Filters -G'MIC Qt... -Available Filters -Frequency -Fourier transform

Related discussion:
text: buildInputs = with pkgs; [ lensfun gexiv2 ]; installPhase = " <del> installPlugins gimp-lensfun </del> <ins> installPlugin gimp-lensfun </ins> "; meta = {
Code change:
Describe the bug Failed to build . To Reproduce in -rebuild switch Expected behavior Build successful. Screenshots  Additional context Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
New warnings/error are introduced with new GCC releases.
could you please give a try?
Yes, it works.

Related discussion:
text: <del> { lib, stdenv, fetchFromGitHub } : </del> <ins> { lib , stdenv , fetchFromGitHub }: </ins> stdenv.mkDerivation rec { pname = "proxychains"; <del> version = "4.2.0"; </del> <ins> version = "4.4.0"; </ins> src = fetchFromGitHub { owner = "haad"; <del> repo = "proxychains"; </del> <ins> repo = pname; </ins> rev = "${pname}-${version}"; <del> sha256 = "015skh3z1jmm8kxbm3nkqv1w56kcvabdmcbmpwzywxr4xnh3x3pc"; </del> <ins> sha256 = "083xdg6fsn8c2ns93lvy794rixxq8va6jdf99w1z0xi4j7f1nyjw"; </ins> }; postPatch = '' <del> # Temporary work-around; most likely fixed by next upstream release sed -i Makefile -e '/-lpthread/a LDFLAGS+=-ldl' </del> <ins> # Suppress compiler warning. Remove it when upstream fix arrives substituteInPlace Makefile --replace "-Werror" "-Werror -Wno-stringop-truncation" </ins> ''; postInstall = '' cp src/proxychains.conf $out/etc ''; <del> meta = { </del> <ins> meta = with lib; { </ins> description = "Proxifier for SOCKS proxies"; homepage = "http://proxychains.sourceforge.net"; <del> license = lib.licenses.gpl2Plus; platforms = lib.platforms.linux; </del> <ins> license = licenses.gpl2Plus; maintainers = with maintainers; [ fab ]; platforms = platforms.linux; </ins> }; }
Code change:
Describe the bug I have a nextcloud installation in the vhost root: which would redirect to for the NextCloud login. Also I enabled in the nginx settings that a SSL certifcate with the acme service should be used. However, no certificate can be issued - acme claims that it gets 404. To Reproduce Steps to reproduce the behavior: nextcloud and acme configuration to your configuration nix. E.g. will generate a nginx config that contains: first part of that configuration snippet also matches for the folder and hence a 404 is returned. Expected behavior Having SSL cert issued by Let's Encrypt. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Opened with a fix.
Thanks for the quick fix :)
can you confirm that this fixes the issue for you? If so, I'd merge+backport. Just in case you didn't know - you can do
I did manually edit the nginx config in the nix store: Then run the acme command as standalone: So it works.

Related discussion:
text: "~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)".extraConfig = '' return 404; ''; <del> "~ ^/(?:.|autotest|occ|issue|indie|db_|console)".extraConfig = '' </del> <ins> "~ ^/(?:.(?!well-known)|autotest|occ|issue|indie|db_|console)".extraConfig = '' </ins> return 404; ''; "~ ^/(?:index|remote|public|cron|core/ajax/update|status|ocs/v[12]|updater/.+|oc[ms]-provider/.+|.+/richdocumentscode/proxy).php(?:$|/)" = {
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: version = "2.1.22"; sha256 = "1wk57dz0kmc6d5y8d8dkx269lzh3ark3751z734gxncwdlclcyz3"; generation = "2_1"; <ins> extraMeta.knownVulnerabilities = [ # Fixed in 3.* but 2.* hasn't been released since "CVE-2020-17516" ]; </ins> })
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: version = "2.2.14"; sha256 = "1b2x3q1ach44qg07sh8wr7d8a10n36w5522drd3p35djbiwa3d9q"; generation = "2_2"; <ins> extraMeta.knownVulnerabilities = [ # Fixed in 3.* but 2.* hasn't been released since "CVE-2020-17516" ]; </ins> })
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: { callPackage, ... } @ args: callPackage ./generic.nix (args // { <del> version = "3.0.23"; sha256 = "0cbia20bggq85q2p6gsybw045qdfqxd5xv8ihppq1hwl21sb2klz"; </del> <ins> version = "3.0.24"; sha256 = "1yxw4jg9n49dbi1mjdfpxczsznl9m6sxlzkmzjancmjzvj5s6bvz"; </ins> generation = "3_0"; })
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: { callPackage, ... } @ args: callPackage ./generic.nix (args // { <del> version = "3.11.9"; sha256 = "1ckaacc1z0j72llklrc4587ia6a0pab02bdyac6g3kl6kqvcz40c"; </del> <ins> version = "3.11.10"; sha256 = "1wcv0drhb765fda6kkpsxsyfdv4cqf7nqfwc4bimh4c4djap5rxv"; </ins> generation = "3_11"; })
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: # generation is the attribute version suffix such as 3_11 in pkgs.cassandra_3_11 , generation , version, sha256 <ins> , extraMeta ? {} </ins> , ... }:
Code change:
, CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc

Related discussion:
text: platforms = platforms.unix; license = licenses.asl20; maintainers = [ maintainers.roberth ]; <del> }; </del> <ins> } // extraMeta; </ins> }
Code change:
Describe the bug AdGuardHome has the meta platform , but is a . To Reproduce Try to run on (or any architecture other than ). It will fail with : Expected behavior should execute, so that it can be used. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
I will try to get it instead of pulling a pre-compiled binary, but I'm not sure whether I'll get this solved. EDIT: Okay, that looks to be above my packaging skills, as the project consists of both a node component and a golang component, so it's nontrivial to package. An intermediate solution might be to use the architecture to determine the download URL, but that would make the src (and thus the hash) depend on the architecture. The downloads for different architectures .
Hotfix for aarch64 by using :
I marked this as stale due to inactivity. &rarr;
I also have the problem from the thread starter and I was wondering whether there is now official support for aarch64 (trying adguardhome on raspberrypi 3) or do I need to change smth in my config. I just use adguardhome as the inside of the systemPackages and I enable it. I also see this PR: .
the pr wasn't backported to 21.05. the pr will be in the 21.11 release which will be released today or tommorow afaik
great, thx for the info :)

Related discussion:
text: githubId = 2789926; name = "Imran Hossain"; }; <ins> iagoq = { email = "18238046+iagocq@users.noreply.github.com"; github = "iagocq"; githubId = 18238046; name = "Iago Manoel Brito"; keys = [{ longkeyid = "rsa4096/0x35D39F9A9A1BC8DA"; fingerprint = "DF90 9D58 BEE4 E73A 1B8C  5AF3 35D3 9F9A 9A1B C8DA"; }]; }; </ins> iammrinal0 = { email = "nixpkgs@mrinalpurohit.in"; github = "iammrinal0";