jiebi/CodeConvo huggingface dataset:
Change:
{ lib, fetchzip }: let <del> version = "2013.06.07"; # date of most recent file in distribution </del> <ins> version = "2014.08.16"; # date of most recent file in distribution </ins> in fetchzip { name = "helvetica-neue-lt-std-${version}"; <del> url = "http://www.ephifonts.com/downloads/helvetica-neue-lt-std.zip"; </del> <ins> url = "https://web.archive.org/web/20190823153624/http://ephifonts.com/downloads/helvetica-neue-lt-std.zip"; </ins> postFetch = '' mkdir -p $out/share/fonts <del> unzip -j $downloadedFile Helvetica Neue LT Std/*.otf -d $out/share/fonts/opentype </del> <ins> unzip -j $downloadedFile "Helvetica Neue LT Std/*.otf" -d $out/share/fonts/opentype </ins> ''; sha256 = "0ampp9vf9xw0sdppl4lb9i9h75ywljhdcqmzh45mx2x9m7h6xgg9"; <del> meta = { homepage = "http://www.ephifonts.com/free-helvetica-font-helvetica-neue-lt-std.html"; </del> <ins> meta = with lib; { homepage = "https://web.archive.org/web/20190926040940/http://www.ephifonts.com/free-helvetica-font-helvetica-neue-lt-std.html"; </ins> description = "Helvetica Neue LT Std font"; longDescription = '' Helvetica Neue Lt Std is one of the most highly rated and complete

Discussion:
Describe the bug I believe the source for the package might no longer be valid: Accessing it in the browser shows a 404, and the home page -- -- appears to just be a portal for serving sponsored links. The Wayback Machine shows that the has not been archived since February 2020, and also get the same 404. There was a in Septermber 2020, but I'm unsure if this was the cause. Thanks! To Reproduce Steps to reproduce the behavior: . Expected behavior Installation should not hang, and the font should be installed. Screenshots Additional context appears to be an alternative to Helvetica, so I'm unsure how important this package is. But I figured this error should be documented. As far as I can tell, is the only package using , so if this domain is indeed no longer usable then nothing else should be impacted. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:
but the link is also dead: so i would ask there where the font is available and if it is freely licensed now. it was also licensed by adobe at some point it seem to ba available from several shady websites, like but that's clearly illegal and shouldn't be packaged in nixpkgs freely licensed alternatives are: (Nimbus Sans)
I marked this as stale due to inactivity. &rarr;
Could the helvetica-neue-lt-std package be removed or at least generate a better error than a 404 when it tries to download the font? I ran into this error while doing a nixos-install so it took a while to find the specific package that was causing my build to fail.
Thank you
Change:
all = [ xarray ]; }; <ins> pythonRelaxDeps = [ "stanio" ]; </ins> preCheck = '' export HOME=$(mktemp -d) '';

Discussion:
Steps to reproduce the behavior: stanio bump caused a build faliure. <!-- 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]:
It turns out it's actually an issue with he python package. It looks like the fact that uses the new builder made it so that it even if builds without complaining (probably something to do with the legacy builder), trying to include it as a dependency of will detect the version error. I'll try to open a PR, which updates to use the new builder (and I'll relax the dependency constraint too).
Thank you Toma for fast response and resolution!
Change:
<del> { lib, fetchPypi, buildPythonPackage </del> <ins> { lib, fetchFromGitHub, buildPythonPackage </ins> , lxml, pycryptodomex, construct , argon2_cffi, dateutil, future <ins> , python </ins> }: buildPythonPackage rec { pname   = "pykeepass"; version = "4.0.0"; <del> src = fetchPypi { inherit pname version; sha256 = "1b41b3277ea4e044556e1c5a21866ea4dfd36e69a4c0f14272488f098063178f"; </del> <ins> src = fetchFromGitHub { owner = "libkeepass"; repo = "pykeepass"; rev = version; sha256 = "1zw5hjk90zfxpgq2fz4h5qzw3kmvdnlfbd32gw57l034hmz2i08v"; </ins> }; postPatch = ''

Discussion:
Describe the bug fails due to To Reproduce Steps to reproduce the behavior: nixos-unstable, or nixos-unstable-small a derivation depending on , for example or Expected behavior Build succeeds Screenshots Additional context With I was able to narrow this down to the merge from that happened in . Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Hello pass-import maintainers! Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Change:
installTargets = "install datainstall"; <del> hardeningDisable = [ "format" ]; </del> postInstall = '' wrapProgram $out/bin/torcs  --prefix LD_LIBRARY_PATH : ${mesa}/lib

Discussion:
failed to build with Full building log exists but I am not sure how to apply it correctly. Could be easy for anyone who know the process. $ cd /nix/nixpkgs/; git rev-parse HEAD $ nix-shell -I nixpkgs=/nix/nixpkgs -p torcs 2&1 | tee System: NixOS: (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: "18.03pre117327." Sandboxing enabled: build-use-sandbox = true
Change:
<ins> { config, lib, ... }: with lib; let enabled = elem "displaylink" config.services.xserver.videoDrivers; displaylink = config.boot.kernelPackages.displaylink; in { config = mkIf enabled { boot.extraModulePackages = [ displaylink ]; boot.kernelModules = [ "evdi" ]; # Those are taken from displaylink-installer.sh and from Arch Linux AUR package. services.udev.extraRules = '' ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="17e9", ATTR{bNumInterfaces}=="*5", TAG+="uaccess" ''; powerManagement.powerDownCommands = '' #flush any bytes in pipe while read -n 1 -t 1 SUSPEND_RESULT < /tmp/PmMessagesPort_out; do : ; done; #suspend DisplayLinkManager echo "S" > /tmp/PmMessagesPort_in #wait until suspend of DisplayLinkManager finish read -n 1 -t 10 SUSPEND_RESULT < /tmp/PmMessagesPort_out ''; powerManagement.resumeCommands = '' #resume DisplayLinkManager echo "R" > /tmp/PmMessagesPort_in ''; systemd.services.displaylink = { description = "DisplayLink Manager Service"; after = [ "display-manager.service" ]; wantedBy = [ "graphical.target" ]; serviceConfig = { ExecStart = "${displaylink}/bin/DisplayLinkManager"; Restart = "always"; RestartSec = 5; }; preStart = '' mkdir -p /var/log/displaylink ''; }; }; } </ins>

Discussion:
DisplayLink, as far as I can tell, seems to be unfortunately emerging as the only choice for connecting external monitors to laptops without display ports (for example, via the ). It would be great if NixOS could support it. I have no idea what is involved in this. There is an Ubuntu driver. DisplayLink the company claims that it should be possible to port (). The says it's difficult to get working.
Do you have hardware for testing this? The driver itself seems fairly straightforward and I could help packaging it.
I do - I have the Dell adapter linked above.
Change:
./qtwebkit-darwin-no-readline.patch ./qtwebkit-darwin-no-qos-classes.patch ]; <ins> qttools = [ ./qttools.patch ]; </ins> }; mkDerivation =

Discussion:
We are currently stuck on qt 5.11 on darwin/macOS. To get things consistent, this should update to qt 5.12 (or even 5.13) soon. Please run and paste the results.
If qt512 builds on darwin we should change the default version:
is currently broken:
Fixed in

When running the provided by the package, it complains about not finding the tool, which is provided by . I have not found a suitable workaround, since it seems like the location of the scanner is hardcoded inside Invoke on a project using Qt. How to use this tool is explained here: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(raskolnikov): nixpkgs:
The error is as follows:
Hi I tried withyour latestchanges from . The fact that Qt 5.12 now works on Darwin again is great news! However, this issue seems to not be resolved. Now the does not bail out inmmediately as it did before. It does indeed do something for a while, but then later I get: Maybe there is some other part of the code where it is missing the path correction? Thanks a lot!
My bad, I was actually using the old one by mistake... I am getting new errors though: I will investigate...
I think I found the issue. The problem is this line: is returning , which is incorrect. I think lines 1258-1260 can be discarded altogether since without the tool is still correctly using , which is a better way of passing the import paths, since inside Nix we actually need multiple import paths anyways due to the modularized Qt installation. Would you be happy to extend the patch with such a modification?
Ok... I have further investigated and I was wrong... One must indeed pass to to really make it work. One can indeed pass multiple times, and probably we shall do it for every entry in . Probably this can be patched... but it seems like we are getting into non trivial patching territory...
Thanks Mathew for reopening the issue. I opened a corresponding issue on Qt:
I marked this as stale due to inactivity. &rarr;
Actually this still stands and it'd be nice to have it fixed some day. There are other issues that are blocking me on Mac these days though, like .
I marked this as stale due to inactivity. &rarr;
Change:
preConfigure = "unset CC"; <del> patches = stdenv.lib.optionals stdenv.isDarwin [ </del> <ins> patches = stdenv.lib.optionals stdenv.isDarwin [ </ins> (fetchurl { url = "https://trac.macports.org/export/70964/trunk/dports/audio/cdparanoia/files/osx_interface.patch"; sha1 = "c86e573f51e6d58d5f349b22802a7a7eeece9fcd";

Discussion:
Using version
Hello! Can you confirm this patch works on OSX + ? I get the following error above.
This might be the same issue that's breaking
Change:
<ins> diff --git a/decomment.c b/decomment.c index 400707a..aea29fd 100644 --- a/decomment.c +++ b/decomment.c @@ -11,6 +11,10 @@ #include "getopt.h" #endif +#ifdef __APPLE__ +#include "getopt.h" +#endif + #ifdef NEED_OPTIND extern int optind; #endif </ins>

Discussion:
Hello, Huge thanks for contributing to nix! I am trying to use this great package manager with a Mac, and I am having some issues trying to install my favourite email client. When I try to install mu with nix-env -I mu, I get the following error: I checked the pmccabe derivation, and it has indeed a constraint on the platform: platforms = ;. Any way this derivation can work on Mac OS X x64? Thanks, Andrea System: Mac OS X Sierra 10.12.4 Nix version: 1.11.8 Nixpkgs version: 17.09pre104948.
It seems the dependency is not used or at least optional, this builds fine without it.
cc it, I think. iirc, that dep is for the test suite.
This isn't the first time I'm breaking the build on Darwin. How do other people test properly without access to a mac?
Thanks, this works!
You can use to check evaluation for darwin or other platforms. That should catch simple cases like this if you don't have enabled in your config.
Thanks for the pointer I think the trick is to get darwin running in a VM instead...
Change:
'!defined(__ANDROID__) && !defined(__OpenBSD__) && 0' ''; <del> outputs = [ "bin" "dev" "out" "man" ]; </del> <ins> outputs = [ "bin" "dev" "out" "man" ] ++ optional withDocs "doc"; </ins> setOutputFlags = false; separateDebugInfo = stdenv.hostPlatform.isLinux;

Discussion:
The .out path contains about 18MB of html docs
To clarify, openssl10 does not, so this is a regression in that sense.
Change:
["libsForQt5" "qtstyleplugins"] ["libsForQt5" "qt5ct"] ["lxqt" "lxqt-qtplugin"] <ins> ["libsForQt5" "plasma-integration"] </ins> ]; description = '' Selects the platform theme to use for Qt5 applications.</para>

Discussion:
The reason why I didn't open a PR, is described in . I'm aware of four platforms for Qt's themes right now: Using GTK themes through + ; Using GNOME themes through + ; Using Qt themes, with the non-KDE solution , which uses ; Using Plasma-targeted Qt themes, with as , as done natively in a plasma session, using the theme's colorscheme. Steps to reproduce the behavior:  and it does not provide ; equivalent to  providing ; , then add some Pasma-target themes like , then adjust envvars , set the theme in or with , you'll get the right theme with the proper color scheme. should provide (or ) as an option, it should add only the required packages to the system, and set the proper envvars. (or maybe rename it, since qt6 also uses the same variables and envvars) qbittorrent + breeze + + dark: ! qbittorrent + breeze + + dark: ! qbittorrent + (ignored my theme): ! qbittorrent + (also ignored my theme): ! I tried to discover what package that is being when evaluating provides this platform-theme, but I failed miserably. stated as maintainers of plasma-integration: stated as maintainer of qt5ct: qt5 module contributors: cc Please run and paste the result.
Not exactly your bug, but we should remove and integrate it with configs instead.
is another QT platform theme that can be integrated into config.
Change:
import ./make-test-python.nix { name = "zram-generator"; <del> nodes.machine = { ... }: { zramSwap = { enable = true; priority = 10; algorithm = "lz4"; swapDevices = 2; memoryPercent = 30; memoryMax = 10 * 1024 * 1024; </del> <ins> nodes = { single = { ... }: { virtualisation = { emptyDiskImages = [ 512 ]; }; zramSwap = { enable = true; priority = 10; algorithm = "lz4"; swapDevices = 1; memoryPercent = 30; memoryMax = 10 * 1024 * 1024; writebackDevice = "/dev/vdb"; }; }; machine = { ... }: { zramSwap = { enable = true; priority = 10; algorithm = "lz4"; swapDevices = 2; memoryPercent = 30; memoryMax = 10 * 1024 * 1024; }; </ins> }; }; testScript = '' <ins> single.wait_for_unit("systemd-zram-setup@zram0.service") </ins> machine.wait_for_unit("systemd-zram-setup@zram0.service") machine.wait_for_unit("systemd-zram-setup@zram1.service") zram = machine.succeed("zramctl --noheadings --raw")

Discussion:
One of the features of zram (and of systemd-zram-generator) is that a swap partition (and hopefully someday in the future a swap file too) can be used to store incompressible pages instead of holding them in ram. It's (you're the last person I saw touch the zramSwap module.) Please run and paste the result.
Our current zram module is implemented by retrofitting the old interface for our own set of bash scripts onto zram-generator, thus it's only possible to create multiple zram devices of identical configurations. However it should be illegal to share a single backing device among multiple zram devices, leaving us two choices in implementing this: allow creating a single zram device when backing device is set the module to expose the full features of zram-generator What's your opinion?
:thinking: It's not stated that the module uses zram-generator under the hood, and I'd say that I don't really think a lot of people use multiple zram devices, so perhaps  is fine.
Change:
, pkg-config , withGstreamer ? true , gst_all_1 <ins> , withOmemo ? true , qca-qt5 , libomemo-c </ins> }: mkDerivation rec {

Discussion:
Steps to reproduce the behavior: kaidan <!-- 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]:
Thanks for notifying me!
Change:
inherit meta; # shebang interpreters buildInputs = (args.extraBuildInputs or [ ]) ++ [ bash perl ] ++ (lib.attrVals (args.scriptExts or [ ]) extToInput); <ins> nativeBuildInputs = extraNativeBuildInputs; </ins> # absolute scripts folder scriptsFolder = lib.optionalString (run ? outPath) (run.outPath + "/scripts/" + args.scriptsFolder or pname); # binaries info

Discussion:
texlive's texdoc has imported a . Maybe we can support it. can work, will search to get the package names but So there is still something needed to be done :cry:
Change:
stdenv.mkDerivation rec { name = "xml-tooling-c-${version}"; <del> version = "1.6.0"; </del> <ins> version = "1.6.3"; </ins> src = fetchgit { url = "https://git.shibboleth.net/git/cpp-xmltooling.git"; <del> rev = "db08101c3854518a59096be95ed6564838381744"; sha256 = "0rhzvxm4z3pm28kpk34hayhm12bjjms2kygv1z68vnz8ijzgcinq"; </del> <ins> rev = version; sha256 = "09z2pp3yy3kqx22vwgxyi3s0vlpdv9camw8dpi3q8piff6zxak3q"; </ins> }; buildInputs = [ boost curl openssl log4shib xercesc xml-security-c ];

Discussion:
There are at least two open security issues (CVE-2017-,CVE-2017-) which affect shibboleth-se and opensaml. The details can be obtained from the upstream annoucement: There are new releases & patches available that fix those open issues. Either updating or marking those packages as broken/insecure seems sensible to me. CC current maintainers:
Sorry for the late response. Thanks for bringing this to my attention. I will fix the packages in the next few days. I actually think the bigger issue is this one, which affects the xml parser: So xml-tooling-c also needs to be fixed, and should be marked broken if not fixed.
Change:
"-DMEDIA_RUN_TEST_SUITE=OFF" ]; <ins> NIX_CFLAGS_COMPILE = lib.optionalString (stdenv.hostPlatform.system == "i686-linux") "-D_FILE_OFFSET_BITS=64"; </ins> nativeBuildInputs = [ cmake pkg-config ]; buildInputs = [ libva libpciaccess intel-gmmlib ]

Discussion:
The build of fails on i686. Fails with: Found with Please run and paste the result. Maintainer information:
if you don't ping any maintainer likely nothing will happen ping
I think I never tried compiling intel-media-driver on i686 but only fixed an eval error in nixGL. The problem seems to be that it compiles 64 bit code on 32 bit.
I did a quick look what other distros do and found this helpful Debian patch () at least fixes. There are still some other compile errors that need fixing. Edit1: and with it compiles
Change:
{ lib , buildPythonPackage <del> , chainer </del> , fetchFromGitHub , hatchling , jupyter

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: python311Packages.chainer maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: -
fixed in master
Change:
nativeBuildInputs = [ pkg-config cmake ninja yasm ]; <del> buildInputs = [ </del> <ins> propagatedBuildInputs = [ </ins> libjpeg openssl libopus

Discussion:
After updating my system flake from nixpkgs commit to , started to fail with the following error. This happens on both Plasma Wayland and Gnome X11. I was able to start after adding the following missing library paths to : - - The channel shown below is no longer relevant, since I'm using flake and don't have any channels configured on the system.
That's weird, maybe there were some changes to gcc, I see libpipewire- in the output of , but no RPATH for it...
maybe you can give some insight on this?
The same happened to tdesktop days ago:
See PR
Ah OK, so maybe you'd like a different resolution than I whipped up. Feel free to choose any.
The right fix would be moving all tg_owt buildInputs to propagatedBuildInputs I guess as it's a static library
I'm currently testing , this will take a while though as both my hardware and GitHub Actions build each of tg_owt and kotatogram multiple hours.
Change:
publicKey = mkOption { example = "xTIBA5rboUvnH4htodjb6e697QjLERt1NAB4mZqp8Dg="; <del> type = types.str; </del> <ins> type = types.singleLineStr; </ins> description = lib.mdDoc "The base64 public key of the peer."; };

Discussion:
If a contains newlines, e.g. when using , this bit of code in doesn't substitute the newline, and nix fails with an error like "store path contains illegal character ' '". Steps to reproduce the behavior: newline is replaced with some useful character maybe
May be related to

Describe the bug If a has a linebreak (), then it will fail when building with the following To Reproduce Use something like Expected behavior Somewhat expect it to remove suffix "n", but not entirely sure if this should be fixed. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Fixed by doing Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Hope it is OK I tag you, just to have a discussion about it: Metadata Please run and paste the result. Maintainer information:
I don't think that the wireguard module should concern itself with this kind of thing, attempting to santise or modify user input here seems like a somewhat sisyphean task that will result in unexpected behaviour and unnesscessary maintaince overhead. As a side note are you aware of ?
But shouldn't the type just not allow linebreaks?
Which one of the would you use for this?
Hmm. well it should be OK I guess. I thought str would not allow newlines. However a option could be to add to this :) Or assert a error if it contains newlines, so that it does not fail silently.
Change:
{ lib, stdenv, fetchFromGitHub, openssl, nss, nspr, libkrb5, gmp, zlib, libpcap, re2 <del> , gcc, python3Packages, perl, perlPackages, makeWrapper, fetchpatch }: </del> <ins> , gcc, python3Packages, perl, perlPackages, makeWrapper, }: </ins> stdenv.mkDerivation rec { pname = "john"; <del> version = "1.9.0-jumbo-1"; </del> <ins> version = "rolling-2404"; </ins> src = fetchFromGitHub { owner = "openwall"; <del> repo = pname; rev = "1.9.0-Jumbo-1"; sha256 = "sha256-O1iPh5QTMjZ78sKvGbvSpaHFbBuVc1z49UKTbMa24Rs="; </del> <ins> repo = "john"; rev = "f9fedd238b0b1d69181c1fef033b85c787e96e57"; hash = "sha256-zvoN+8Sx6qpVg2JeRLOIH1ehfl3tFTv7r5wQZ44Qsbc="; </ins> }; <del> patches = [ (fetchpatch { name = "fix-gcc-11-struct-allignment-incompatibility.patch"; url = "https://github.com/openwall/john/commit/154ee1156d62dd207aff0052b04c61796a1fde3b.patch"; sha256 = "sha256-3rfS2tu/TF+KW2MQiR+bh4w/FVECciTooDQNTHNw31A="; }) (fetchpatch { name = "improve-apple-clang-pseudo-intrinsics-portability.patch"; url = "https://github.com/openwall/john/commit/c9825e688d1fb9fdd8942ceb0a6b4457b0f9f9b4.patch"; excludes = [ "doc/*" ]; sha256 = "sha256-hgoiz7IgR4f66fMP7bV1F8knJttY8g2Hxyk3QfkTu+g="; }) ]; </del> postPatch = '' sed -ri -e ' s!^(#defines+CFG_[A-Z]+_NAMEs+).*/!1"'"$out"'/etc/john/!

Discussion:
ssh2john produce error while trying to process ssh key Steps to reproduce the behavior: john in any way - ssh key with password - KALI: Please run and paste the result.
This seems like an upstream issue. See
This issue 2 years long! Can we bundle older python with john or apply workaround stated in mentioned issue?
In the meantime, I believe you should be able to work around this by overriding the python version locally:
Change:
popd ''; <del> postInstall = '' cat >$out/bin/dsymutil << EOF #!${stdenv.shell} EOF chmod +x $out/bin/dsymutil ''; </del> passthru = { inherit targetPrefix; };

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.