jiebi/CodeConvo huggingface dataset:
Change:
, jq , removeReferencesTo , nixosTests <ins> , file </ins> }: let

Discussion:
The package contains compiler toolchain binaries (like ) and libc libraries to be used by the compiler outputs. When is run on the package, it incorrectly adds the internal libc directory to the rpath of the compiler binaries. This causes the compiler binaries to break with an error message like this: This problem was introduced in / This was done because the systemd package wanted to use to add dependencies to its rpath. But using to do this had an undesired side effect of removing glibc from the rpath (for a reason I don't yet understand). So s previous behavior to ignore libc dependencies was changed. a flag to autoPatchelfHook telling it to leave libc in the rpath if it's found. Enable this only on systemd. the libc change to autoPatchelfHook altogether, and instead modify findLibs and make-initrd-ng to automatically check libc. Either solution would restore the old libc behavior of autoPatchelfHook for everyone else. The former would then add different code for systemd, and the latter would change a couple other programs to account for lacking this new behavior
Fixed by
Change:
{ lib , absl-py <ins> , blas </ins> , buildPythonPackage , fetchFromGitHub , jaxlib <ins> , lapack </ins> , numpy , opt-einsum , pytestCheckHook

Discussion:
Build of failed on x86_64-linux as of . Maintainer cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:
Looks to be some test failures: I suspect this is due to the since jax hasn't been changed otherwise.
Change:
enableParallelBuilding = true; <del> postInstall = optionalString enableNumpy '' wrapProgram $out/bin/blender  --prefix PYTHONPATH : ${python3Packages.numpy}/${python.sitePackages} ''; </del> <ins> blenderExecutable = placeholder "out" + (if stdenv.isDarwin then "/Blender.app/Contents/MacOS/Blender" else "/bin/blender"); # --python-expr is used to workaround https://developer.blender.org/T74304 postInstall = '' wrapProgram $blenderExecutable  --add-flags '--python-expr "import sys; sys.path.append("${python3Packages.numpy}/${python.sitePackages}")"' ''; </ins> # Set RUNPATH so that libcuda and libnvrtc in /run/opengl-driver(-32)/lib can be # found. See the explanation in libglvnd.

Discussion:
Describe the bug blender 2.82 built with enableNumpy set to true builds and installs without errors, but at run-time it fails to find numpy. There may be other issues with other libraries not being found as I'm having trouble activating a number of plugins and I don't think all use numpy, though at the moment I can only say for certainty numpy doesn't work. To Reproduce Steps to reproduce the behavior: blender with blender and go to the Scripting tab. in the console. The following comes up: This worked with 2.81. Expected behavior numpy should be imported with no errors. Metadata Result of : Maintainer information:
Change:
###### implementation config = mkIf cfg.enable { <del> assertions = singleton { assertion = cfg.password == null || cfg.passwordFile == null; message = "Cannot use both password and passwordFile for shadowsocks-libev"; }; </del> <ins> assertions = [ { # xor, make sure either password or passwordFile be set. # shadowsocks-libev not support plain/none encryption method # which indicated that password must set. assertion = let noPasswd = cfg.password == null; noPasswdFile = cfg.passwordFile == null; in (noPasswd && !noPasswdFile) || (!noPasswd && noPasswdFile); message = "Option `password` or `passwordFile` must be set and cannot be set simultaneously"; } ]; </ins> systemd.services.shadowsocks-libev = { description = "shadowsocks-libev Daemon";

Discussion:
It looks like shadowsocks service integration is not working at the moment, even with minimal configuration. systemd service doesn't load. Apply this nixos config It looks like nixos will generate ExecStart similar like so Running this will just get a help screen of ss-server (and same for systemd service, confirmed with journalctl) Contents of /nix/store/i74pqxw9wwicclbamqjw2l4w7l48rdpz- is Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is caused by ss-libev's encryption method requiring a password but not set. Refined the assertion in fix pr.
Change:
let majorVersion = "2.6"; <del> version = "${majorVersion}.7"; </del> <ins> version = "${majorVersion}.8"; # http://www.python.org/download/releases/2.6.8/ # md5 taken from webpage, python 2.6 will receive security fixes until Oct 2013 </ins> src = fetchurl { url = "http://www.python.org/ftp/python/${version}/Python-${version}.tar.bz2"; <del> sha256 = "0p0fd8i533zsdm6gc0jmhmdifccx4v064mh0i1hl2s6fcjhc20j5"; </del> <ins> md5 = "c6e0420a21d8b23dee8b0195c9b9a125"; </ins> }; patches =

Discussion:
We need to propagate the pth loader so packages using us process our pth files, but it makes no sense to have the pth loader itself in a pth file.
Change:
let inherit (binutils-unwrapped) targetPrefix; cmds = [ <del> "ar" "ranlib" "as" "dsymutil" "install_name_tool" </del> <ins> "ar" "ranlib" "as" "install_name_tool" </ins> "ld" "strip" "otool" "lipo" "nm" "strings" "size" ]; in <del> # TODO loop over targetPrefixed binaries too </del> <ins> # TODO: loop over targetPrefixed binaries too </ins> stdenv.mkDerivation { name = "${targetPrefix}cctools-binutils-darwin"; outputs = [ "out" "info" "man" ];

Discussion:
clang installed through nix doesn't correctly output DWARF data. system: host os: multi-user?: sandbox: version: channels(fghibellini): nixpkgs:
For reference, we use a dummy dsymutil script due to Apple not releasing the original source. This is found here: and . llvm has its own version that should be available to us soon. I'm not sure which version it is first released in.
Thanks for the quick answer! Based on I would think dsymutil is supposed to be Apple specific. Does the llvm release of dsymutil mean this (separate debug info linking) will become standard across operating systems or the llvm dsymutil is also supposed to be used only on OSX?
dsymutil is for MACH-O binaries only. I think OSX is the only place where those are used. You can do something similar on Linux with objcopy though: But this is a good reminder that we need to get the separate debug symbols to work on MacOS as well.
Change:
gst = callPackage ../applications/version-management/gst { }; <ins> gut = callPackage ../applications/version-management/gut { }; </ins> hred = callPackage ../development/tools/hred { }; hub = callPackage ../applications/version-management/hub { };

Discussion:
Project description Gut is a CLI designed to make Git easier to use. Metadata homepage URL: source URL: license: mit platforms: linux, darwin, windows
Change:
, cmake , extra-cmake-modules , wrapQtAppsHook <ins> , qtbase </ins> , kwin <del> , kdelibs4support </del> <ins> , kcmutils </ins> , libepoxy , libxcb , lib

Discussion:
the package kde-rounded corners does not work with plasma 6 Steps to reproduce the behavior: the package <name.packages = [ ] = true; there should be an effect "shaped corners" in kde settings 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
# Assertion issues "test_textual_env_var" "test_softbreak_split_links_rendered_correctly" <ins> # requires tree-sitter-languages which is not packaged in nixpkgs "test_register_language" </ins> ]; pythonImportsCheck = [

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.
Change:
kakoune-cr = callPackage ../tools/misc/kakoune-cr { crystal = crystal_1_2; }; <ins> kaniko = callPackage ../applications/networking/cluster/kaniko { }; </ins> katana = callPackage ../tools/security/katana { }; katriawm = callPackage ../applications/window-managers/katriawm { };

Discussion:
Project description kaniko is a tool to build container images from a Dockerfile, inside a container or Kubernetes cluster Metadata homepage URL: source URL: license: platforms: Linux
Please test. And provide feedback. You can use tool for that:
Next time you request something certify to follow up. Issue is now closed without you having tested it.
FYI you can do the following to build a container with kaniko in it. Use the kaniko executor on your host system (outside of containers) Note that you may need to build a container with kaniko/executor + credential helpers
Change:
owner = "fabioz"; repo = "PyDev.Debugger"; rev = "pydev_debugger_${lib.replaceStrings ["."] ["_"] version}"; <del> hash = "sha256-1tWiPj30x/ZXIBu2qzUCpyF1bLsJ0wW1QaxklD3h3A8="; </del> <ins> hash = "sha256-aylmLN7lVUza2lt2K48rJsx3XatXPgPjcmPZ05raLX0="; </ins> }; <del> nativeBuildInputs = [ </del> <ins> __darwinAllowLocalNetworking = true; build-system = [ </ins> setuptools ]; <del> __darwinAllowLocalNetworking = true; </del> nativeCheckInputs = [ numpy psutil

Discussion:
Steps to reproduce the behavior: 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I started with but unfortunately there is more to do.
Change:
<ins> #!/usr/bin/env nix-shell #!nix-shell -p bash -p subversion -p common-updater-scripts -i bash die() { echo "error: $1" >&2 exit 1 } attr=netpbm svnRoot=https://svn.code.sf.net/p/netpbm/code/advanced oldRev=$(nix-instantiate --eval -E "with import ./. {}; $attr.src.rev" | tr -d '"') if [[ -z "$oldRev" ]]; then die "Could not extract old revision." fi latestRev=$(svn info --show-item "last-changed-revision" "$svnRoot") if [[ -z "$latestRev" ]]; then die "Could not find out last changed revision." fi versionInfo=$(svn cat -r "$latestRev" "$svnRoot/version.mk") if [[ -z "$versionInfo" ]]; then die "Could not get version info." fi nixFile=$(nix-instantiate --eval --strict -A "$attr.meta.position" | sed -re 's/^"(.*):[0-9]+"$/1/') if [[ ! -f "$nixFile" ]]; then die "Could not evaluate '$attr.meta.position' to locate the .nix file!" fi # h remembers if we found the pattern; on the last line, if a pattern was previously found, we exit with 1 # https://stackoverflow.com/a/12145797/160386 sed -i "$nixFile" -re '/(brevbs*=s*)"'"$oldRev"'"/{ s||1"'"$latestRev"'"|; h }; ${x; /./{x; q1}; x}' && die "Unable to update revision." majorRelease=$(grep --perl-regex --only-matching 'NETPBM_MAJOR_RELEASE = K.+' <<< "$versionInfo") minorRelease=$(grep --perl-regex --only-matching 'NETPBM_MINOR_RELEASE = K.+' <<< "$versionInfo") pointRelease=$(grep --perl-regex --only-matching 'NETPBM_POINT_RELEASE = K.+' <<< "$versionInfo") update-source-version "$attr" "$majorRelease.$minorRelease.$pointRelease" </ins>

Discussion:
no $ Add to installPhase
For some reason netpbm is installing the symlink to . Will be fixed by

Describe the bug Netpbm misses TIFF converters, such as . To Reproduce Steps to reproduce the behavior: to find some commands. Expected behavior TIFF converters installed with Netpbm. Additional context libtiff is required to build the following Netpbm programs: , , and (). Indeed is input for the , but TIFF converters are missed. Metadata output:
Change:
# Version of Pulumi from # https://www.pulumi.com/docs/get-started/install/versions/ <del> VERSION="3.10.0" </del> <ins> VERSION="3.12.0" </ins> # Grab latest release ${VERSION} from # https://github.com/pulumi/pulumi-${NAME}/releases plugins=( "auth0=2.2.0" <del> "aws=4.15.0" "cloudflare=3.4.0" "consul=3.2.0" "datadog=3.3.0" "digitalocean=4.6.0" "docker=3.0.0" </del> <ins> "aws=4.19.0" "cloudflare=3.5.0" "consul=3.3.0" "datadog=4.1.0" "digitalocean=4.6.1" "docker=3.1.0" </ins> "equinix-metal=2.0.0" <del> "gcp=5.15.0" "github=4.2.0" "gitlab=4.1.0" "hcloud=1.2.0" "kubernetes=3.6.0" "linode=3.3.0" </del> <ins> "gcp=5.18.0" "github=4.3.0" "gitlab=4.2.0" "hcloud=1.4.0" "kubernetes=3.7.0" "linode=3.3.2" </ins> "mailgun=3.1.0" "mysql=3.0.0" "openstack=3.3.0" "packet=3.2.2" <del> "postgresql=3.1.0" </del> <ins> "postgresql=3.2.0" </ins> "random=4.2.0" <del> "vault=4.3.0" </del> <ins> "vault=4.4.0" </ins> "vsphere=4.0.1" )

Discussion:
<!-- 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: pulumi-bin <!-- 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: 3.10.0 desired version: 3.12.0 <!-- 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.
Change:
mailcatcher = handleTest ./mailcatcher.nix {}; mariadb-galera-mariabackup = handleTest ./mysql/mariadb-galera-mariabackup.nix {}; mariadb-galera-rsync = handleTest ./mysql/mariadb-galera-rsync.nix {}; <del> mathics = handleTest ./mathics.nix {}; </del> matomo = handleTest ./matomo.nix {}; matrix-synapse = handleTest ./matrix-synapse.nix {}; mediawiki = handleTest ./mediawiki.nix {};

Discussion:
The mathics test does not work because: /cc (commit history)
I see the same error with on the 20.03 beta channel. I think it also happens on Master. It used to work (maybe a few weeks ago? if I have time I'll bisect).
I removing mathics.
Change:
util-linux iptables iproute2 <ins> ] ++ lib.optionals stdenv.isDarwin [ vfkit </ins> ] ++ extraPackages); helpersBin = symlinkJoin {

Discussion:
Project description vfkit - Simple command line tool to start VMs through macOS Virtualization Framework This is (apparently) required by Podman 5.0.x and Darwin. See: Metadata homepage URL: source URL: license: Apache 2.0 platforms: darwin
I can confirm this is required by podman 5 on macOS in order to start the virtual machine uses to run containers
The reason I said "apparently" was because although I had observed that I needed to install to get Podman to work, I wasn't 100% sure there wasn't an alternative configuration.
I know the PR is closed but it's worth mentioning it didn't work.
I know the PR is closed but it's worth mentioning it didn't work. yeah, I could build it with our Darwin SDK, but it seems to disable too many features to make it usable. I think you can use the following:
Could you elaborate a bit on which features needed to be disabled and why,
: I just hit this problem and found this issue. Is there a specific reason that specific package was not yet submitted upstream, or could I (beginner) do that?
Change:
# fix tests substituteInPlace tests/unittest/include/unittest/unittest.h  --replace /usr/include/ "" <ins> # Hack to get `gcc -m32' to work without having 32-bit Glibc headers. mkdir gnu-efi/inc/ia32/gnu touch gnu-efi/inc/ia32/gnu/stubs-32.h </ins> ''; nativeBuildInputs = [ nasm perl python3 ];

Discussion:
pxelinux (from syslinux) is compiled without support for UEFI PXE boot: I had a quick look at getting it to compile uefi support but I didn't get very far. system: host os: multi-user?: sandbox: version: channels(root): channels(peter): nixpkgs:
Does the NixOS netboot image support UEFI boot? I did try netbooting NixOS (18.03) a few weeks ago with a pre-compiled iPXE UEFI loader. It started booting the kernel but failed to mount the initrd (kernel panic no root).
The image is using pxelinux.0 instead of lpxelinux.0 it seems and you need lpxelinux for HTTP support so maybe that's what is going on.
The http support seemed to worked just fine in my case. I did serve the iPXE UEFI loader via tftp, the kernel image and the initrd via http (initrd is too big to load trouble-free via tftp). The iPXE loader pulled bzImage and initrd via http and began booting the kernel. The kernel then failed to mount the ramdisk for some reason I do not understand. I solved the problem by setting 'Legacy mode' in the firmware (Supermicro) and booting everything in classical BIOS/PXE mode (no UEFI components involved). I can try to reproduce the problem and send you some screenshots if that helps. My vague guess is that the NixOS netboot image needs some modifications to be UEFI capable. I just wanted to raise awareness that there are potential problems with UEFI-PXE down the road.
IIRC, specifying on the kernel command line is required with EFI booting for some reason (edit: when booting with iPXE, that is).
would fix this.
Change:
mkdir -p $out/var/lib/hp cp ${hplipState} $out/var/lib/hp/hplip.state <del> rm $out/etc/udev/rules.d/56-hpmud.rules </del> ''; # The installed executables are just symlinks into $out/share/hplip,

Discussion:
Printing with a HP Color LaserJet printer fails due to a crash in the filter when using the driver "hpcups 3.19.1" With the "CUPS+Gutenprint v5.2.14" driver printing works. Try to print anything, a test page would do Please run and paste the results. oops.. let's try again:
I'm having the same problem, and made some observations: hplip 3.18.5 (used in release-18.09) works, even if compiled with pkgs from release-19.03 Here's a bug report with a proposed patch: is probably here: I didn't come around to test any of those patches thoug as I have only very limited access to my HP printer.
Change:
runScript = "decent-sampler"; <ins> extraInstallCommands = '' cp -r ${decent-sampler}/lib $out/lib cp -r ${decent-sampler}/share $out/share ''; </ins> meta = with lib; { description = "An audio sample player"; longDescription = ''

Discussion:
Decent Sampler is supposed to have a standalone app, a VST2 plugin and a VST3 plugin. The package decent-sampler installs only the standalone app. The downloaded archive contains also which is the VST2 plugin and the directory which is the VST3 plugin. Steps to reproduce the behavior: decent-sampler. for the VST plugins 't find them. The VST3 plugin should be installed in of the package and the VST2 plugin too should be in the package, but I don't know where exactly. <!-- 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. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
environment = { DATA_PATH = cfg.dataDir; }; <del> serviceConfig = defaultServiceConfig //{ </del> <ins> serviceConfig = defaultServiceConfig // { </ins> ExecStart = "${cfg.package}/app/actualize_script.php"; }; };

Discussion:
When Freshrss is first taken into use the service presents configuration wizard where it asks for language and complains of invalid file permissions. The service should configure these automatically, but it does not. Steps to reproduce the behavior: freshrss with nixos rebuild "http://<MYDOMAINHERE" to web browser 's web page opens to configuration wizard Freshrss's web page should open to the "Main stream" page. This can be fixed by manually starting which does the configuration. It does not get started automatically when you first enable freshrss though, with no indication that you should start it yourself. Which led in my case to much wasted hours and frustration. Example output from rebuild: ^-- No at the list of new started units Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Can you see if adding the following configuration fixes this for you?
Hi, seems that it does indeed fix it. :+1: Tested this by starting from scratch: freshrss's nix configuration nixos rebuild accessing freshrss's web page and got 404 error to another location freshrss's nix configuration back in and applied your fix nixos rebuild again accessing freshrss's web page and got the expected main stream page Also another side benefit is that it is now possible to change admin's password via . Previously it required also running of manually afterwards.
Change:
stdenv.mkDerivation rec { pname = "bulky"; <del> version = "2.8"; </del> <ins> version = "2.9"; </ins> src = fetchFromGitHub { owner = "linuxmint"; repo = "bulky"; rev = version; <del> hash = "sha256-DZjX4xPyA30TTyOX+VyGSY/FWPX2316CYImDWRma9r0="; </del> <ins> hash = "sha256-eCu7AgL4bzstu8vsqBJImRZm1qMVnnycuOShY5fB+C4="; </ins> }; nativeBuildInputs = [

Discussion:
To reproduce, here is an example: The related code is at Some nice to have: As suggested  should be something that can be accessible by everything and we are likely going to put our "" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.
Change:
<del> { lib, stdenv </del> <ins> { lib , stdenv </ins> , autoconf , automake , c-ares

Discussion:
Describe the bug Latest MEGAsync app fails to start (Segmentation fault), probably because of . Not sure if it is NixOS related or just a MEGAsync bug. To Reproduce Steps to reproduce the behavior: it fault Expected behavior No crash Additional context Crash dump: 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:
Yep I have this too. Actually the most recent commit version doesn't open at all, just dumps core - but the previous commit before that () does open and reopens on startup and everything fine, despite giving me the segmentation fault when I open it manually. <details<summaryCrashdump</summary
Same for me. Reported upstream: Bumping the version to does not help. It is still usable for me on 20.09 stable with this overlay:
Does anyone know how to specify an older version of cryptopp, as a stopgap until this is fixed upstream? I'm in desperate need of getting Megasync to work again. The overlay above isn't working for me on Unstable.
can't you just use michojel's overlay above, or an older version of the megasync package entirely? The latter is what I'm doing rn, just stick this in your : Which pins commit (which still uses megasync 4.3.5.0)
Looks like 4.4.0.0 addressed the issues. Works for me at least. See