jiebi/CodeConvo huggingface dataset:
Change:
Describe the bug The default configuration for generates a systemd service that does not depend on nginx to be up. However, the nginx prometheus exporter fails at startup if nginx is not running: To Reproduce Steps to reproduce the behavior: restart nginx nginx-prometheus-exporter unlucky with restart parallelism Expected behavior Proper dependencies are required. Maintainer information:

Discussion:
services.prometheus.exporters.minio.minioAccessSecret = mkDefault config.services.minio.secretKey; })] ++ [(mkIf config.services.rspamd.enable { services.prometheus.exporters.rspamd.url = mkDefault "http://localhost:11334/stat"; <ins> })] ++ [(mkIf config.services.nginx.enable { systemd.services.prometheus-nginx-exporter.after = [ "nginx.service" ]; systemd.services.prometheus-nginx-exporter.requires = [ "nginx.service" ]; </ins> })] ++ (mapAttrsToList (name: conf: mkExporterConf { inherit name;
Change:
Describe the bug Since upgrading to 19.09, my laptop's boot process is delayed by about one minute due to entropy starvation during the boot process To Reproduce Steps to reproduce the behavior: configuration: { device = "/dev/disk/by-id/yadayada-part2"; = true; = "/dev/random"; } [possibly configure other services that also need entropy during boot] Expected behavior A quick boot as in 19.03 with max 1 second used by the swap initalization. Screenshots $ systemd-analyze plot | fgrep mkswap <text class="left" x="1018.920" y="694.000"mkswap-dev-disk-byx2did-nvmex2dSamsungSSD970EVO2TBS464NB0M401994Dx2dpart2.service (1min 723ms)</textAdditional context This is on physical hardware, not on VM. Replacing random with urandom leads to instant boot, but has the obvious problem with the missing entropy. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Basically there are two ways to fix this issue: 1) Find out why 19.03 had enough entropy but 19.09 seems to lack entropy during swap initialization and mitigate this 2) setup swap at a later time during boot, which obviously only works if the swap is not critical to the boot process I'm going to work on this later, but if you have any ideas or suggestions, feel free to comment.
I had a similar issue. it might be related to changes in the kernel ? I had a similar problem in VMs, managed to work around it with via (+virtio but you should only need this setting)
cannot solve this, as it starts after swap configuration and thus after the long delay. It may be possible to move it to an earlier point in the boot process, as it just requires hardware devices that should be available before swap.

Discussion:
{ description = "Initialisation of swap device ${sw.device}"; wantedBy = [ "${realDevice'}.swap" ]; before = [ "${realDevice'}.swap" ]; <ins> # If swap is encrypted, depending on rngd resolves a possible entropy starvation during boot after = mkIf (config.security.rngd.enable && sw.randomEncryption.enable) [ "rngd.service" ]; </ins> path = [ pkgs.utillinux ] ++ optional sw.randomEncryption.enable pkgs.cryptsetup; script =

description = "Hardware RNG Entropy Gatherer Daemon"; <ins> # rngd may have to start early to avoid entropy starvation during boot with encrypted swap unitConfig.DefaultDependencies = false; </ins> serviceConfig = { ExecStart = "${pkgs.rng-tools}/sbin/rngd -f" + optionalString cfg.debug " -d"; <ins> # PrivateTmp would introduce a circular dependency if /tmp is on tmpfs and swap is encrypted, # thus depending on rngd before swap, while swap depends on rngd to avoid entropy starvation. </ins> NoNewPrivileges = true; PrivateNetwork = true; <del> PrivateTmp = true; </del> ProtectSystem = "full"; ProtectHome = true; };
Change:
Project description snore is sleep with feedback Metadata source URL: license: mit platforms: linux
I'm confused by your name... lol

Discussion:
<ins> { stdenv, fetchFromGitHub }: stdenv.mkDerivation rec { version = "0.1"; pname = "snore"; src = fetchFromGitHub { owner = "clamiax"; repo = pname; rev = version; sha256 = "1ic1qy6ybnjlkz5rb1hpvq6dcdmxw5xcx34qcadrsfdjizxcv8pp"; }; makeFlags = [ "PREFIX=${placeholder "out"}" ]; meta = with stdenv.lib; { description = "sleep with feedback"; homepage = "https://github.com/clamiax/snore"; license = licenses.mit; maintainers = [ maintainers.marsam ]; platforms = platforms.unix; }; } </ins>

snakemake = callPackage ../applications/science/misc/snakemake { python = python3Packages; }; <ins> snore = callPackage ../tools/misc/snore { }; </ins> snowman = qt5.callPackage ../development/tools/analysis/snowman { }; sparse = callPackage ../development/tools/analysis/sparse { };
Change:
Describe the bug A clear and concise description of what the bug is. when doing nixos-rebuild build -I nixos-config=./nix- -I nixpkgs=/mnt/vmpool/jkarlson/repos/nixpkgs po4a-0.55 build gets stuck in a busyloop in command perl po4a --previous --no-translations --msgid-bugs-address --package-name po4a --package-version 0.55 This dependency is caused by enabling = true; To Reproduce Steps to reproduce the behavior: master or release-19.09 to nixpkgs path attached config nixos-rebuild build -I nixos-config=./nix- -I nixpkgs=/path/to/nixpkgs Expected behavior build to complete Additional context Installing po4a as a normal package just fetches the binary cache, I am not sure where this package actually builds. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(jkarlson): nixpkgs: Maintainer information: yaml attribute: po4a module:
The config in question.
I have exactly the same problem on due to being enabled on my system (which has as a build dependency). Based on a command i see in ps it is exactly the same version of po4a:
Here is inlined config that posted above
Problem still exists on latest channel. cc you in to this as an original package maintainer, maybe you have some ideas on why this is happening.
Problem still persists sadly :( Not sure what possible solutions to this would be. Any help on this is appreciated.
One can apparently just remove Po4a from sssd build inputs, not sure what we would be missing this way.
It's used at build time to produce the documentation in all available languages
Yeah, maybe that would be a good temporary solution. Having working package beats the lacking documentation I think.
I solved this on my system by dropping po4a from list of dependencies for sssd: My overrides: :
since you asked (between the lines) whether there was more hacky but shorter way to do this. As Po4a is only used as buildInputs, you can feed it whatever you want without touching sssd files.
Oh did not think about that, pretty clever! Will use this instead.

Discussion:
sha256 = "1qss4q5df3nsydsbggb7gg50bn0kdxq5wn8riqm9zwkiq6a4bifg"; }; nativeBuildInputs = [ docbook_xsl docbook_xsl_ns ModuleBuild ]; <del> propagatedBuildInputs = [ TextWrapI18N LocaleGettext TermReadKey SGMLSpm UnicodeLineBreak PodParser YAMLTiny ]; </del> <ins> propagatedBuildInputs = [ TextWrapI18N LocaleGettext SGMLSpm UnicodeLineBreak PodParser YAMLTiny ]; # TODO: TermReadKey was temporarily removed from propagatedBuildInputs to unfreeze the build </ins> buildInputs = [ gettext libxslt glibcLocales docbook_xml_dtd_412 docbook_sgml_dtd_41 texlive.combined.scheme-basic opensp ]; LC_ALL = "en_US.UTF-8"; SGML_CATALOG_FILES = "${docbook_xml_dtd_412}/xml/dtd/docbook/catalog.xml";
Change:
Describe the bug Since 19.09 redis ships a unit called this oneshot unit fails on every start of a container with redis, because containers have a read-only sysfs. To Reproduce Steps to reproduce the behavior: in nixos-container container See something like in the journal of the container. Maintainer information:
ping
We can probably fix this by setting via the NixOS module system, which should have the same effect (on systems that can set this value), and not cause a failing systemd unit when run inside a container. can you test whether the following works for you?
That snippet has a problem with the which shouldn‘t affect the hugepages option.
Yes, this obviously shouldn't be inside the attrset after the . ;-)

Discussion:
config = mkIf config.services.redis.enable { <del> boot.kernel.sysctl = mkIf cfg.vmOverCommit { "vm.overcommit_memory" = "1"; }; </del> <ins> boot.kernel.sysctl = { "vm.nr_hugepages" = "0"; } // mkIf cfg.vmOverCommit { "vm.overcommit_memory" = "1"; }; </ins> networking.firewall = mkIf cfg.openFirewall { allowedTCPPorts = [ cfg.port ];

environment.systemPackages = [ cfg.package ]; <del> systemd.services.disable-transparent-huge-pages = { description = "Disable Transparent Huge Pages (required by Redis)"; before = [ "redis.service" ]; wantedBy = [ "redis.service" ]; script = "echo never > /sys/kernel/mm/transparent_hugepage/enabled"; serviceConfig.Type = "oneshot"; }; </del> systemd.services.redis = { description = "Redis Server";
Change:
Describe the bug The build of package () fails because returns a 403 error code (and no useful data) To Reproduce Steps to reproduce the behavior: in the nixpkgs directory, on current master Expected behavior Build succeeds Screenshots Additional context Metadata Please run and paste the result. Maintainer information:
Possible hotfix: Use as url which provides the needed source, but sadly no https, and this is not a mirror with versions in the url.
It seems the homepage moved to
The versioned ~yusa/ricty/ricty_generator- also exists

Discussion:
version = "4.1.1"; src = fetchurl { <del> url = "https://www.rs.tus.ac.jp/yyusa/ricty/ricty_generator-${version}.sh"; </del> <ins> url = "http://www.yusa.lab.uec.ac.jp/~yusa/ricty/ricty_generator-${version}.sh"; </ins> sha256 = "03fngb8f5hl7ifigdm5yljhs4z2x80cq8y8kna86d07ghknhzgw6"; };

meta = with stdenv.lib; { description = "A high-quality Japanese font based on Inconsolata and Migu 1M"; <del> homepage = https://www.rs.tus.ac.jp/yyusa/ricty.html; </del> <ins> homepage = http://www.yusa.lab.uec.ac.jp/~yusa/ricty.html; </ins> license = licenses.unfree; maintainers = [ maintainers.mikoim ]; };
Change:
Describe the bug Since this commit: Whenever I run commands like: I get the following error: Additional context My default shell is zsh, which has been the cause of some issues at times. Metadata Paging in particular. Let me know how I can help!
You need recent bash (=4) as macOS has outdated bash by default. I'm not sure how nix behaves on macOS, but try either of the following: you have environment variable, unset it. your system bash or install it via nix:
Thanks. I personally solved it by: Which installed an ambient bash v5.0. Feel free to close this if you think you're done tracking this concern.
Nix should use bashInteractive from Nixpkgs. I suspect it's hitting some error and falling back here:
I could also solve the issue for me with these steps.
I got this issue on macOS, and installing via comment worked out well (which was also the solution you mentioned). I am running macOS Catalina, and wanted a pure nix/macOS machine, so for me this was a better solution.
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 .
It might still be important.
I marked this as stale due to inactivity. &rarr;

Discussion:
set -eu set -o pipefail <ins> if [ -n "${BASH_VERSINFO-}" ] && [ "${BASH_VERSINFO-}" -lt 4 ]; then echo "Detected Bash version that isn't supported by Nixpkgs (${BASH_VERSION})" echo "Please install Bash 4 or greater to continue." exit 1 fi </ins> if (( "${NIX_DEBUG:-0}" >= 6 )); then set -x fi
Change:
Describe the bug Eagle does not start anymore. When starting it from the command line I get the following message: To Reproduce Steps to reproduce the behavior: eagle it by calling Expected behavior Instead of getting an error message on the console, I'd expect the software to show a graphical window. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(matthias): nixpkgs: Maintainer information:
cc
I noted this as well
CC maintainer
it has to do with the qt wrapping, and i keep forgetting the best practices
AFAIK, the eagle expression should use mkDerivation from qt instead of stdenv. And perhaps look into using autoPatchelfHook.
I tried that, but it needs some non-qt libraries, and felt like i was wasting too much time on it, so i moved on
Hmm, I'll try to look into the issue this week.
I think this should fix it:
It's probably going to be wrapped several times because of the old logic
How can I apply this patch locally? I tried to load eagle from nixos-unstable, but that patch isn't there yet.
Thanks for merging it :)

Discussion:
<del> { stdenv, fetchurl, makeDesktopItem </del> <ins> { stdenv, mkDerivation, fetchurl, makeDesktopItem </ins> , libXrender, libXrandr, libXcursor, libX11, libXext, libXi, libxcb , libGL, glib, nss, nspr, expat, alsaLib , qtbase, qtdeclarative, qtsvg, qtlocation, qtwebchannel, qtwebengine

qtbase qtdeclarative qtsvg qtlocation qtwebchannel qtwebengine ]; in <del> stdenv.mkDerivation rec { </del> <ins> mkDerivation rec { </ins> pname = "eagle"; version = "9.5.0";
Change:
Here's the error message: Here's the full log:
cc
My installation command was wrong. I had when I should have had

Discussion:
buildGoPackage rec { pname = "nomad"; <del> version = "0.10.5"; </del> <ins> version = "0.11.0"; </ins> rev = "v${version}"; goPackagePath = "github.com/hashicorp/nomad";

owner = "hashicorp"; repo = pname; inherit rev; <del> sha256 = "0i9104anf3qaydm1izlwrzvpzizd6p1zy651hsynscnnxa56cmyk"; </del> <ins> sha256 = "0jg7h52wlgd2aslx13fs97j3b8g5xfgil3p2jsc4j95l7lmqn7bv"; </ins> }; # ui:

noip = callPackage ../tools/networking/noip { }; <del> nomad = callPackage ../applications/networking/cluster/nomad { buildGoPackage = buildGo112Package; }; </del> <ins> nomad = callPackage ../applications/networking/cluster/nomad { }; </ins> notable = callPackage ../applications/misc/notable { };
Change:
Describe the bug VIber package in nixpkgs repo is broken/outdated. Getting this errors when trying to install it: To Reproduce Steps to reproduce the behavior: to install viber via config file/nix-env. Expected behavior Successful viber installation. Metadata system: host os: multi-user?: sandbox: version: nixpkgs:
have the same issue
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 .

Discussion:
version = "13.3.1.22"; src = fetchurl { <del> url = "https://download.cdn.viber.com/cdn/desktop/Linux/viber.deb"; </del> <ins> # Official link: https://download.cdn.viber.com/cdn/desktop/Linux/viber.deb url = "http://web.archive.org/web/20210602004133/https://download.cdn.viber.com/cdn/desktop/Linux/viber.deb"; </ins> sha256 = "0rs26x0lycavybn6k1hbb5kzms0zzcmxlrmi4g8k7vyafj6s8dqh"; };
Change:
I don't really know why my system configuration for an XPS 13 is pulling this in, either: EDIT: I had set in my system configuration, thus causing me to (fail to) build .
I have the same problem on 3 laptops As mentioned in above post issue is related to enableAllFirmware = true; Chnaging to enableRedistributableFirmware = true; fixed the issue for now another example
cc maintainers:
I think, the new url could be found on this page
I'll try to find time over the weekend to update new offsets and hashes for the new download path. In the meantime, facetimehd users can extract the firmware from their OSX partition with this override: ``
See

Discussion:
let <del> version = "1.43_4"; </del> <ins> version = "1.43_5"; </ins> # Updated according to https://github.com/patjak/bcwc_pcie/pull/81/files

# and https://github.com/patjak/bcwc_pcie/blob/5a7083bd98b38ef3bd223f7ee531d58f4fb0fe7c/firmware/extract-firmware.sh # From the Makefile: <del> dmgUrl = "https://support.apple.com/downloads/DL1877/en_US/osxupd10.11.5.dmg"; dmgRange = "205261917-208085450"; # the whole download is 1.3GB, this cuts it down to 2MB </del> <ins> dmgUrl = "https://updates.cdn-apple.com/2019/cert/041-88431-20191011-e7ee7d98-2878-4cd9-bc0a-d98b3a1e24b1/OSXUpd10.11.5.dmg"; dmgRange = "204909802-207733123"; # the whole download is 1.3GB, this cuts it down to 2MB </ins> # Notes: # 1. Be sure to update the sha256 below in the fetch_url # 2. Be sure to update the homepage in the meta

inherit version; src = fetchurl { url = dmgUrl; <del> sha256 = "0xqkl4yds0n9fdjvnk0v5mj382q02crry6wm2q7j3ncdqwsv02sv"; </del> <ins> sha256 = "0s8crlh8rvpanzk1w4z3hich0a3mw0m5xhpcg07bxy02calhpdk1"; </ins> curlOpts = "-r ${dmgRange}"; };

meta = with stdenv.lib; { description = "facetimehd firmware"; <del> homepage = https://support.apple.com/downloads/DL1877; </del> <ins> homepage = https://support.apple.com/kb/DL1877; </ins> license = licenses.unfree; maintainers = with maintainers; [ womfoo grahamc ]; platforms = [ "i686-linux" "x86_64-linux" ];
Change:
Describe the bug arion package doesn't build on Mac OS X using nixpkgs current master (2019-10-25). It could be a build failure in the python docker package in docker-compose's closure, as suggested by To Reproduce Minimal file: eventually fails with a build error. Expected behavior arion and its dependencies (docker and docker-compose) should build on Mac OS. Screenshots n/a Additional context It appears that the . This could be related. I'm also referencing where this issue was first discussed. Full error log: Metadata failed with: Maintainer information: CC - thanks for your time and effort. Happy to help in any way if I can.
hmm, this is a darwin related issue i think the fix might be _allowLocalNetworking = true; or something to that effect. I'll have to check after work Thanks for submitting a ticket though :)
This looks like an instance of . We probably should just disable the failing tests.
now package fails
Thanks for looking into it. Current builds fine, though on a different setup (MacBook's keyboard being, err, replaced): Using:
I've gotten a bit farther, playing around with ( master) And then command fails with this error: Here's the content of file being generated: There could be a mix of and somewhere.
Could you check that sets the parameter? This was missing from the . If you use the or functions in Nix, make sure they're from a linux .
Indeed, the parameter was missing on my setup - I'm unsure how I missed that part. I confirm that now builds successfully using as a remote builder. Output of : Thanks for taking the time to look into this. I'm still getting started in nix and looking forward to contribute back.

Discussion:
]; # Other tests touch network <ins> # Deselect socket tests on Darwin because it hits the path length limit for a Unix domain socket </ins> checkPhase = '' <del> ${pytest}/bin/pytest tests/unit/ </del> <ins> ${pytest}/bin/pytest tests/unit/ ${stdenv.lib.optionalString stdenv.isDarwin "--deselect=tests/unit/api_test.py::TCPSocketStreamTest"} </ins> ''; meta = with stdenv.lib; {
Change:
We seem to have unpatched vulnerabilities (noticed by nixpkgs monitor):
The first one was explicitly claimed to be fixed in 2.21 NEWS, although the CVE entry claims that version still suffers from it.

Discussion:
buildGoPackage rec { pname = "nomad"; <del> version = "0.10.5"; </del> <ins> version = "0.11.0"; </ins> rev = "v${version}"; goPackagePath = "github.com/hashicorp/nomad";

owner = "hashicorp"; repo = pname; inherit rev; <del> sha256 = "0i9104anf3qaydm1izlwrzvpzizd6p1zy651hsynscnnxa56cmyk"; </del> <ins> sha256 = "0jg7h52wlgd2aslx13fs97j3b8g5xfgil3p2jsc4j95l7lmqn7bv"; </ins> }; # ui:

noip = callPackage ../tools/networking/noip { }; <del> nomad = callPackage ../applications/networking/cluster/nomad { buildGoPackage = buildGo112Package; }; </del> <ins> nomad = callPackage ../applications/networking/cluster/nomad { }; </ins> notable = callPackage ../applications/misc/notable { };
Change:
Describe the bug See the ; the relevant issue seems to be here: Most of is online verbatim. To Reproduce Steps to reproduce the behavior: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
I confirm I see the same issue here when I run with the channel.
It seems the only package that needs is . Do you need or specifically in your configuration?
i bisect'ed it to
lutris has it as a transitive dependency
I guess it's used by dolphin
to follow up, gnutls-kdh doesn't build with nettle-3.5.1. Seeing as the repo is quite inactive, either we get rid of it, or freeze nettle. I'm personally in favor of getting rid of it

Discussion:
# Dolphin bluez ffmpeg gettext portaudio wxGTK30 miniupnpc mbedtls lzo sfml gsm <del> wavpack gnutls-kdh orc nettle gmp pcre vulkan-loader </del> <ins> wavpack orc nettle gmp pcre vulkan-loader </ins> # DOSBox SDL_net SDL_sound
Change:
Describe the bug Because snappy does not install a pkgconfig file, you can't take snappy as a buildInput, packages will never find it. To Reproduce Expected behavior Metadata system: host os: multi-user?: sandbox: version: channels(seb): nixpkgs: Maintainer information: cc
I have opened a PR on the snappy codebase: It is waiting for review and then nixpkgs will need to be updated. Note how the PR has to handle the absolute path being configured in cmake by nix
has decided not to take the patch upstream, so I will work on adding the pkg-config file as part of the nix installation
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .

Discussion:
stdenv.mkDerivation rec { pname = "snappy"; <del> version = "1.1.8"; </del> <ins> version = "1.1.9"; </ins> src = fetchFromGitHub { owner = "google"; repo = "snappy"; rev = version; <del> sha256 = "1j0kslq2dvxgkcxl1gakhvsa731yrcvcaipcp5k8k7ayicvkv9jv"; </del> <ins> sha256 = "sha256-JXWl63KVP+CDNWIXYtz+EKqWLJbPKl3ifhr8dKAp/w8="; </ins> }; <del> patches = [ ./disable-benchmark.patch ]; </del> outputs = [ "out" "dev" ]; nativeBuildInputs = [ cmake ];

cmakeFlags = [ "-DBUILD_SHARED_LIBS=${if static then "OFF" else "ON"}" "-DCMAKE_SKIP_BUILD_RPATH=OFF" <ins> "-DSNAPPY_BUILD_TESTS=OFF" "-DSNAPPY_BUILD_BENCHMARKS=OFF" </ins> ]; postInstall = '' substituteInPlace "$out"/lib/cmake/Snappy/SnappyTargets.cmake  --replace 'INTERFACE_INCLUDE_DIRECTORIES "''${_IMPORT_PREFIX}/include"' 'INTERFACE_INCLUDE_DIRECTORIES "'$dev'"' <ins> mkdir -p $dev/lib/pkgconfig cat <<EOF > $dev/lib/pkgconfig/snappy.pc Name: snappy Description: Fast compressor/decompressor library. Version: ${version} Libs: -L$out/lib -lsnappy Cflags: -I$dev/include EOF </ins> ''; <del> checkTarget = "test"; </del> <ins> #checkTarget = "test"; </ins> <del> doCheck = true; </del> <ins> # requires gbenchmark and gtest but it also installs them out $dev doCheck = false; </ins> meta = with lib; { homepage = "https://google.github.io/snappy/";

<del> --- a/snappy-test.cc +++ b/snappy-test.cc @@ -46 +46 @@ -DEFINE_bool(run_microbenchmarks, true, +DEFINE_bool(run_microbenchmarks, false, </del>