jiebi/CodeConvo huggingface dataset:
Code change:
Trying to build zathura on unstable, I get: Additional context I can't really see what might have changed recently (I think it started happening about 2 weeks ago....) for it to no longer find synctex. The texlive package is being included as a build input, which should have synctex Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I can build zathura on master and the hydra has been doing ok. Am I missing something?
Hm, I'm not sure. I can't seem to get it to build.... "nix-build -A zathura" on master gives me the same error
This also builds for me on master. Only thing i can think of is your branch isn't up to date.
What do you think could be wrong? My sources are up to date:
I notice that I get a different drv on my system (), I think you may not be building from the master. IIRC when you run it will build from which may not point to your git checkout. If you want to build expressions from the current directory you need to do nix also can download a tarball with expressions, for example like this:
If no path is given nix-build will read and If doesn't exist it will fail. So, command is fine.
I just checked on another x86_64-linux NixOS system that evaluates to on . If the command is correct then there must be an override or an overlay in or that affects the derivation.
Oh my god, you're totally right. I had an overlay in my , which I think I had to add to disable synctex at one point when it wasn't working. Removing that and it builds fine. So sorry for wasting your guys' time but thanks for the help! (Although I wonder why it says it can't find synctex when it should have been disabled with the overlay?) Anyways, I'll close this issue, thanks again, it was driving me crazy!
What was the overlay? There may still be a bug here.
The build indeed fails with . I don't have time to open a PR now but the fix is pretty easy: can you reopen the issue?
Sure - it also fails to build with synctexSupport = false, not sure if your fix addresses that as well?
The option was introduced in I think we should just drop variant

Related discussion:
text: { config, pkgs # zathura_pdf_mupdf fails to load _opj_create_decompress at runtime on Darwin (https://github.com/NixOS/nixpkgs/pull/61295#issue-277982980) <del> , useMupdf ? config.zathura.useMupdf or (!pkgs.stdenv.isDarwin) , synctexSupport ? true }: </del> <ins> , useMupdf ? config.zathura.useMupdf or (!pkgs.stdenv.isDarwin) }: </ins> let callPackage = pkgs.newScope self;
Code change:
Trying to build zathura on unstable, I get: Additional context I can't really see what might have changed recently (I think it started happening about 2 weeks ago....) for it to no longer find synctex. The texlive package is being included as a build input, which should have synctex Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I can build zathura on master and the hydra has been doing ok. Am I missing something?
Hm, I'm not sure. I can't seem to get it to build.... "nix-build -A zathura" on master gives me the same error
This also builds for me on master. Only thing i can think of is your branch isn't up to date.
What do you think could be wrong? My sources are up to date:
I notice that I get a different drv on my system (), I think you may not be building from the master. IIRC when you run it will build from which may not point to your git checkout. If you want to build expressions from the current directory you need to do nix also can download a tarball with expressions, for example like this:
If no path is given nix-build will read and If doesn't exist it will fail. So, command is fine.
I just checked on another x86_64-linux NixOS system that evaluates to on . If the command is correct then there must be an override or an overlay in or that affects the derivation.
Oh my god, you're totally right. I had an overlay in my , which I think I had to add to disable synctex at one point when it wasn't working. Removing that and it builds fine. So sorry for wasting your guys' time but thanks for the help! (Although I wonder why it says it can't find synctex when it should have been disabled with the overlay?) Anyways, I'll close this issue, thanks again, it was driving me crazy!
What was the overlay? There may still be a bug here.
The build indeed fails with . I don't have time to open a PR now but the fix is pretty easy: can you reopen the issue?
Sure - it also fails to build with synctexSupport = false, not sure if your fix addresses that as well?
The option was introduced in I think we should just drop variant

Related discussion:
text: self = rec { gtk = pkgs.gtk3; <del> zathura_core = callPackage ./core { inherit synctexSupport; }; </del> <ins> zathura_core = callPackage ./core { }; </ins> zathura_pdf_poppler = callPackage ./pdf-poppler { };
Code change:
Describe the bug When I'm trying to install he arduino or ino package on MacOS I get the error message has wrong length for hash type 'sha256'. , one of the MacOS entries has a hash that is longer than all the other hashes. To Reproduce Steps to reproduce the behavior: Run: Expected behavior Arduino is installed in a nix shell. Screenshots ! Metadata Please run and paste the result. Maintainer information:
In the pull request mentioned above I have corrected the obvious error in the hash. I don't have Nix on Darwin to try it on, can you?

Related discussion:
text: }; "build/macosx/avrdude-6.3.0-arduino9-i386-apple-darwin11.tar.bz2" = fetchurl { url = "https://downloads.arduino.cc/tools/avrdude-6.3.0-arduino9-i386-apple-darwin11.tar.bz2"; <del> sha256 = "0rc4x8mcsva4v6j7ssfj8rdyg14l2pd9ivgdm39m5wnz8b06p85z11703f0r82aq3mmkiy7vwa4jfjhs9826qpp724hbng9dx74kk86r"; </del> <ins> sha256 = "0rc4x8mcsva4v6j7ssfj8rdyg14l2pd9ivgdm39m5wnz8b06p85z"; </ins> }; "build/macosx/appbundler/appbundler-1.0ea-arduino4.jar.zip" = fetchurl { url = "https://downloads.arduino.cc/appbundler-1.0ea-arduino4.jar.zip";
Code change:
Project description sasquatch is a varation of the unsquashfs utilty that can unpack a much larger amount of vendor specific flavours of squashfs that the regular unsquashfs utility cannot unpack. It is distributed as a patch to the regular squashfs-tools package (so might need some extra work to work with the squashfs-tools package already in nixpkgs). Metadata homepage URL: source URL: license: gpl2+ platforms: linux

Related discussion:
text: githubId = 11016164; name = "Fedor Pakhomov"; }; <ins> pamplemousse = { email = "xav.maso@gmail.com"; github = "Pamplemousse"; githubId = 2647236; name = "Xavier Maso"; }; </ins> panaeon = { email = "vitalii.voloshyn@gmail.com"; github = "panaeon";
Code change:
Project description sasquatch is a varation of the unsquashfs utilty that can unpack a much larger amount of vendor specific flavours of squashfs that the regular unsquashfs utility cannot unpack. It is distributed as a patch to the regular squashfs-tools package (so might need some extra work to work with the squashfs-tools package already in nixpkgs). Metadata homepage URL: source URL: license: gpl2+ platforms: linux

Related discussion:
text: <ins> { fetchFromGitHub , fetchurl , lz4 ? null , lz4Support ? false , lzma , lzo , stdenv , xz , zlib }: assert lz4Support -> (lz4 != null); let patch = fetchFromGitHub { owner = "devttys0"; repo = "sasquatch"; rev = "3e0cc40fc6dbe32bd3a5e6c553b3320d5d91ceed"; sha256 = "19lhndjv7v9w6nmszry63zh5rqii9v7wvsbpc2n6q606hyz955g2"; } + "/patches/patch0.txt"; in stdenv.mkDerivation rec { pname = "sasquatch"; version = "4.3"; src = fetchurl { url = mirror://sourceforge/squashfs/squashfs4.3.tar.gz; sha256 = "1xpklm0y43nd9i6jw43y2xh5zvlmj9ar2rvknh0bh7kv8c95aq0d"; }; buildInputs = [ lzma lzo xz zlib ] ++ stdenv.lib.optional lz4Support lz4; patches = [ patch ]; patchFlags = [ "-p0" ]; postPatch = '' cd squashfs-tools ''; installFlags = "INSTALL_DIR=${out}/bin"; makeFlags = [ "XZ_SUPPORT=1" ] ++ stdenv.lib.optional lz4Support "LZ4_SUPPORT=1"; meta = with stdenv.lib; { homepage = "https://github.com/devttys0/sasquatch"; description = "Set of patches to the standard unsquashfs utility (part of squashfs-tools) that attempts to add support for as many hacked-up vendor-specific SquashFS implementations as possible"; license = licenses.gpl2Plus; maintainers = [ maintainers.pamplemousse ]; platforms = platforms.linux; }; } </ins>
Code change:
Project description sasquatch is a varation of the unsquashfs utilty that can unpack a much larger amount of vendor specific flavours of squashfs that the regular unsquashfs utility cannot unpack. It is distributed as a patch to the regular squashfs-tools package (so might need some extra work to work with the squashfs-tools package already in nixpkgs). Metadata homepage URL: source URL: license: gpl2+ platforms: linux

Related discussion:
text: samplicator = callPackage ../tools/networking/samplicator { }; <ins> sasquatch = callPackage ../tools/filesystems/sasquatch { }; </ins> sasview = callPackage ../applications/science/misc/sasview {}; scallion = callPackage ../tools/security/scallion { };
Code change:
Project description Metadata homepage URL: source URL: license: lgpl2/lgpl3 platforms: linux
Previously: (which I never finished, sorry, but linking in case helps anyone tackle this).

Related discussion:
text: <ins> { stdenv, fetchFromGitHub, meson, sassc, pkg-config, glib, ninja, python3, gtk3, gnome3, gtk-engine-murrine }: stdenv.mkDerivation rec { pname = "yaru"; version = "19.10.2"; src = fetchFromGitHub { owner = "ubuntu"; repo = "yaru"; rev = version; sha256 = "1azyn8pr0kpbq4wlz91f5amqyxqq0x2mxkglzl488sf39fl0gnbj"; }; nativeBuildInputs = [ meson sassc pkg-config glib ninja python3 ]; buildInputs = [ gtk3 gnome3.gnome-themes-extra ]; propagatedUserEnvPkgs = [ gtk-engine-murrine ]; postPatch = "patchShebangs ."; meta = with stdenv.lib; { description = "Ubuntu community theme 'yaru' - default Ubuntu theme since 18.10"; homepage = https://github.com/ubuntu/yaru; license = with licenses; [ cc-by-sa-40 gpl3 ]; platforms = platforms.linux; maintainers = [ maintainers.jD91mZM2 ]; }; } </ins>
Code change:
Project description Metadata homepage URL: source URL: license: lgpl2/lgpl3 platforms: linux
Previously: (which I never finished, sorry, but linking in case helps anyone tackle this).

Related discussion:
text: yanone-kaffeesatz = callPackage ../data/fonts/yanone-kaffeesatz {}; <ins> yaru-theme = callPackage ../data/themes/yaru {}; </ins> zafiro-icons = callPackage ../data/icons/zafiro-icons { }; zeal = libsForQt5.callPackage ../data/documentation/zeal { };
Code change:
Describe the bug After installing inkscape either in the user or system profile, no icons are found. When opening dialogs such as "Fill and stroke" or "Layers" the program crashes. I've confirmed this on two of my machines. To Reproduce Steps to reproduce the behavior: inkscape that all icons display incorrectly to Object -Fill and Stroke crash Expected behavior Inkscape should have the full set of icons and dialogs should be accessible. Screenshots ! Additional Context <details<summaryConsole log</summary</detailsMetadata system: host os: multi-user?: sandbox: version: channels(root): channels(riley): nixpkgs:
I think you can easily fix this issue by installing an icon theme to your system.
I believe these icons are part of Inkscape. Possibly issue with gdk-pixbuf loaders – though, I cannot reproduce it within plain xterm session. What desktop environment are you running? Does adding to Inkscape’s help?
Sorry, I should have mentioned - I already tried the following overlay for inkscape after reading the gdk-pixbuf issue and related ones. Unfortunately it didn't seem to change anything after rebuilding and compiling. One of my computers is running sway (launched via startx) and the other i3 + sddm.
Maybe does not work because of :
That worked! I to the overlay and all the icons show up, and dialogs work. I tried looking up docs on but I couldn't find much about it, what does it do exactly?
:confused: I thought the issue with strictDeps only touched gobject-introspection
IIRC, it might also affect hook’s not being picked up correctly. Does the following work with enabled?
Yes, that worked! Would the best workaround for now be to add those inputs to the derivation?

Related discussion:
text: , glibmm, libsigcxx, lcms, boost, gettext, makeWrapper , gsl, python2, poppler, imagemagick, libwpg, librevenge , libvisio, libcdr, libexif, potrace, cmake, hicolor-icon-theme <ins> , librsvg, wrapGAppsHook </ins> }: let
Code change:
Describe the bug After installing inkscape either in the user or system profile, no icons are found. When opening dialogs such as "Fill and stroke" or "Layers" the program crashes. I've confirmed this on two of my machines. To Reproduce Steps to reproduce the behavior: inkscape that all icons display incorrectly to Object -Fill and Stroke crash Expected behavior Inkscape should have the full set of icons and dialogs should be accessible. Screenshots ! Additional Context <details<summaryConsole log</summary</detailsMetadata system: host os: multi-user?: sandbox: version: channels(root): channels(riley): nixpkgs:
I think you can easily fix this issue by installing an icon theme to your system.
I believe these icons are part of Inkscape. Possibly issue with gdk-pixbuf loaders – though, I cannot reproduce it within plain xterm session. What desktop environment are you running? Does adding to Inkscape’s help?
Sorry, I should have mentioned - I already tried the following overlay for inkscape after reading the gdk-pixbuf issue and related ones. Unfortunately it didn't seem to change anything after rebuilding and compiling. One of my computers is running sway (launched via startx) and the other i3 + sddm.
Maybe does not work because of :
That worked! I to the overlay and all the icons show up, and dialogs work. I tried looking up docs on but I couldn't find much about it, what does it do exactly?
:confused: I thought the issue with strictDeps only touched gobject-introspection
IIRC, it might also affect hook’s not being picked up correctly. Does the following work with enabled?
Yes, that worked! Would the best workaround for now be to add those inputs to the derivation?

Related discussion:
text: --replace '"python-interpreter", "python"' '"python-interpreter", "${python2Env}/bin/python"' ''; <del> nativeBuildInputs = [ pkgconfig cmake makeWrapper python2Env ] </del> <ins> nativeBuildInputs = [ pkgconfig cmake makeWrapper python2Env wrapGAppsHook ] </ins> ++ (with perlPackages; [ perl XMLParser ]); buildInputs = [ libXft libpng zlib popt boehmgc
Code change:
Describe the bug After installing inkscape either in the user or system profile, no icons are found. When opening dialogs such as "Fill and stroke" or "Layers" the program crashes. I've confirmed this on two of my machines. To Reproduce Steps to reproduce the behavior: inkscape that all icons display incorrectly to Object -Fill and Stroke crash Expected behavior Inkscape should have the full set of icons and dialogs should be accessible. Screenshots ! Additional Context <details<summaryConsole log</summary</detailsMetadata system: host os: multi-user?: sandbox: version: channels(root): channels(riley): nixpkgs:
I think you can easily fix this issue by installing an icon theme to your system.
I believe these icons are part of Inkscape. Possibly issue with gdk-pixbuf loaders – though, I cannot reproduce it within plain xterm session. What desktop environment are you running? Does adding to Inkscape’s help?
Sorry, I should have mentioned - I already tried the following overlay for inkscape after reading the gdk-pixbuf issue and related ones. Unfortunately it didn't seem to change anything after rebuilding and compiling. One of my computers is running sway (launched via startx) and the other i3 + sddm.
Maybe does not work because of :
That worked! I to the overlay and all the icons show up, and dialogs work. I tried looking up docs on but I couldn't find much about it, what does it do exactly?
:confused: I thought the issue with strictDeps only touched gobject-introspection
IIRC, it might also affect hook’s not being picked up correctly. Does the following work with enabled?
Yes, that worked! Would the best workaround for now be to add those inputs to the derivation?

Related discussion:
text: gsl poppler imagemagick libwpg librevenge libvisio libcdr libexif potrace hicolor-icon-theme <ins> librsvg # for loading icons </ins> python2Env perlPackages.perl ];
Code change:
Describe the bug After upgrading to 19.09pre, I am always asked for a password to unlock from . I don't recall this happening in 19.03 Some more info on how to set this up: To Reproduce Steps to reproduce the behavior: KDE with KWallet enabled out and back in to launch chromium that a password is needed Expected behavior Password used for login is used to unlock kwallet. Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(mbauer): nixpkgs: Maintainer information:
What display manager are you using?
This is the sddm display manager.
I've also noticed this.
I wasn't upgrading from stable, only from ~a few months ago, so it must have been relatively recent.
The issue here is with the pam module then if it's not automatically unlocked. ~Do you use Plasma 5 which adds?~ (read it says you use KDE) I believe this was broken with lightdm and I've recently fixed it there Could you try using lightdm and see if there's a difference?
Yeah, I think this one is KDE specific. Noticed this in my log: Looking at the coredump gives me this: Looks like a wrapping issue. This is what kwallet looks like:
I'd agree that it's most likely a wrapping issue since that's the only other major change we could tie it too. cc
I agree that the failure in sounds like a wrapping issue. Could you confirm that exists? Unfortunately, I can't tell which platform integration plugin it's trying to load; I would need to see the environment in which PAM loads.
twmn now crashes in QGuiApplicationPrivate::createPlatformIntegration again as well (I remember this happening a long time ago) I remember before I could do but even now that doesn't work
This looks like it's not happening anymore on my system. Probably fixed by either or
Actually still seeing it...
Not sure what's happening so I'll run a git bisect on it.
Should be fixed with .
It works correctly on 19.09, but regressed on current unstable:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Hi, I get this again on 20.09 stable. In my case this happens cause of: Core was generated by `/run/current-system/sw/bin/kwalletd5'. Program terminated with signal SIGSEGV, Segmentation fault. 0x00007fa0556062ec in QObject::disconnect(QObject const, char const, QObject const, char const) () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase- /run/current-system/sw/bin/kwalletd5 seems to crash only with Plasma sessions

Related discussion:
text: postPatch = '' sed -i pam_kwallet_init -e "s|socat|${lib.getBin socat}/bin/socat|" ''; <ins> postFixup = '' wrapQtApp $out/libexec/pam_kwallet_init ''; dontWrapQtApps = true; </ins> }
Code change:
Project description Oh My Fish provides core infrastructure to allow to install packages which extend or modify the look of fish shell. It's fast, extensible and easy to use. Very similar to Oh-my-zsh that is already in NixOs package repo Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin,
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 .
Any news on this?
I am still trying to understand how oh-my-zsh works.
Well, it just looks like a copy-paste. Just a giant install phase. <details<summaryTREE</summary</details
Isn't this issue about oh-my-fish instead of zsh?
Yes, it is. And I am studying oh-my-zsh in order to use it as a "template".

Related discussion:
text: <ins> { lib , stdenv , fetchFromGitHub , fish , runtimeShell , writeShellScript }: stdenv.mkDerivation rec { pname = "oh-my-fish"; version = "7+unstable=2021-03-03"; src = fetchFromGitHub { owner = pname; repo = pname; rev = "0b1396ad7962073fa25615bf03c43b53eddc2d56"; hash = "sha256-lwMo4+PcYR9kYJPWK+ALiMfBdxFSgB2vjtSn8QrmmEA="; }; buildInputs = [ fish ]; dontConfigure = true; dontBuild = true; installPhase = '' runHook preInstall mkdir -pv $out/bin $out/share/${pname} cp -vr * $out/share/${pname} cat << EOF > $out/bin/omf-install #!${runtimeShell} ${fish}/bin/fish  $out/share/${pname}/bin/install  --noninteractive  --offline=$out/share/${pname} EOF chmod +x $out/bin/omf-install runHook PostInstall ''; meta = with lib; { homepage = "https://github.com/oh-my-fish/oh-my-fish"; description = "The Fish Shell Framework"; longDescription = '' Oh My Fish provides core infrastructure to allow you to install packages which extend or modify the look of your shell. It's fast, extensible and easy to use. ''; license = licenses.mit; maintainers = with maintainers; [ AndersonTorres ]; platforms = fish.meta.platforms; }; } # TODO: customize the omf-install script </ins>
Code change:
Project description Oh My Fish provides core infrastructure to allow to install packages which extend or modify the look of fish shell. It's fast, extensible and easy to use. Very similar to Oh-my-zsh that is already in NixOs package repo Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin,
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 .
Any news on this?
I am still trying to understand how oh-my-zsh works.
Well, it just looks like a copy-paste. Just a giant install phase. <details<summaryTREE</summary</details
Isn't this issue about oh-my-fish instead of zsh?
Yes, it is. And I am studying oh-my-zsh in order to use it as a "template".

Related discussion:
text: fish = callPackage ../shells/fish { }; <ins> oh-my-fish = callPackage ../shells/fish/oh-my-fish { }; </ins> wrapFish = callPackage ../shells/fish/wrapper.nix { }; fishPlugins = recurseIntoAttrs (callPackage ../shells/fish/plugins { });
Code change:
Describe the bug A clear and concise description of what the bug is. Looks like a new failure for mariadb-server: Currently blocking nixpkgs-unstable
I strongly suspect the update in is the culprit

Related discussion:
text: # Media support MEDIA_CAMERA_SUPPORT? y MEDIA_RC_SUPPORT? y <ins> MEDIA_USB_SUPPORT y </ins> ${if kernelPlatform ? kernelExtraConfig then kernelPlatform.kernelExtraConfig else ""} ${extraConfig}
Code change:
, (nixos-19.09) (nixos-19.09) (nixos-19.09) (nixos-19.09) Scanned versions: nixos-19.09: . May contain false positives.
Needs patching on master, 19.09, 19.03. CVE-2019-: CVE-2019-: CVE-2019-: CVE-2019-:

Related discussion:
text: # Media support MEDIA_CAMERA_SUPPORT? y MEDIA_RC_SUPPORT? y <ins> MEDIA_USB_SUPPORT y </ins> ${if kernelPlatform ? kernelExtraConfig then kernelPlatform.kernelExtraConfig else ""} ${extraConfig}