jiebi/CodeConvo huggingface dataset:
Change:
{ lib , stdenv <ins> , fetchFromGitHub </ins> , fetchurl , fetchpatch , aqbanking

Discussion:
application can't find help files Install from nixos release channel, go to main application screen, click on Help menu and select either "tutorial and concepts guide" or "contents". Application complains with a modal reporting "GnuCash could not find the files for the help documentation. This is likely because 'gnucash-docs' package is not installed." system: host os: multi-user?: sandbox: version: channels(root): channels(zarel): nixpkgs:
As a workaround: the very same documentation is available online at this address:
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 . on the on .
still happening
Pinging maintainers
There is more to it. Gnucash installs its document files into plain without subdirectory. Because of that common files like do have collisions with analogous files in other packages. Edit: Ah, that's another issue. Which was resolved in
Documentation for Gnucash is a separate project: It should be separately build and installed in order for help files to be available.
I marked this as stale due to inactivity. &rarr;
I've built the documentation and put the documentation in the XDGDATADIRS. I can browse the manual and the tutorial via but running gnucash in debug mode says "Unsupported action" and according to strace the application doesn't try to open the documentation directories... and the same happens for evince (can see the documentation in yelp but the application won't display it), maybe it's the same issue
Not stale, I'm still having this issue
I marked this as stale due to inactivity. &rarr;
issue remains.
Thank you for the fix! Do you think is there a way to warn the user about not having yelp in a profile?

I don't think there are any convenient/good ways to tell the user about it. At best, we could add it to the description?
If gnucash documentation depends on yelp, would it make sense to express this dependency in the gnucash derivation?
Apparently, it must also be in MIME. This sort of stupid behaviour looks like an upstream bug to me.
If an application shipped its help files as HTML and required you to have a web browser installed to view them, I think it would be silly to add a dependency on any specific web browser. Likewise with help files - if (at least theoretically) Yelp is just one of several possible help file viewers, I don't think it makes sense to add a dependency on it. A better indication of what's wrong ("you need to install a help viewer" rather than "couldn't find the docs") would be nice, though, which I presume is only really doable upstream.
Change:
, python3 , fetchFromGitHub , gobject-introspection <del> , gtk3 </del> , wrapGAppsHook <ins> , killall </ins> }: python3.pkgs.buildPythonApplication rec {

Discussion:
is missing command dependency and will fail to update wallpaper without it. Steps to reproduce the behavior: a system without , any background is not changed. on stdout A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. 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.
Change:
in with libretro; ([ ] ++ optional (cfg.enable4do or false) _4do <ins> ++ optional (cfg.enableBeetlePCEFast or false) beetle-pce-fast ++ optional (cfg.enableBeetlePSX or false) beetle-psx ++ optional (cfg.enableBeetleSaturn or false) beetle-saturn </ins> ++ optional (cfg.enableBsnesMercury or false) bsnes-mercury ++ optional (cfg.enableDesmume or false) desmume ++ optional (cfg.enableFBA or false) fba

Discussion:
Please rename the libretro-mednafen- cores packages to libretro-beetle- or similar; the RetroArch/libretro project does not have permission nor blessings to use "Mednafen" branding for their forks, and have been cooperative in renaming the cores in light of this.
cc
Superseded by .
Change:
# don't remove runtime deps dontPatchELF = true; <del> nativeBuildInputs = [ autoPatchelfHook makeWrapper dpkg ]; </del> <ins> nativeBuildInputs = [ autoPatchelfHook makeWrapper wrapGAppsHook dpkg ]; </ins> buildInputs = (with xorg; [ libXi libXcursor libXdamage libXrandr libXcomposite libXext libXfixes libXrender libX11 libXtst libXScrnSaver

Discussion:
Seems to be related to and Try to open a folder with vscode. system: host os: multi-user?: sandbox: version: channels(root): channels(okina): nixpkgs:
VSCode still crashes for me when attempting to open a folder. I am using the unstable channel and I've uninstalled, collected garbage, reinstalled without any improvement.
The unstable channel hasn't really updated yet, or at least it hasn't for me.
Change:
SYSVIPC            = yes;  # System-V IPC <ins> AIO                = yes;  # POSIX asynchronous I/O </ins> UNIX               = yes;  # Unix domain sockets. MD                 = yes;     # Device mapper (RAID, LVM, etc.)

Discussion:
Describe the bug Since switching from to I needed to switch from to , otherwise the system does not boot anymore. To Reproduce Steps to reproduce the behavior: system on lvm-inside-luks using either or channel password - gets accepted correctly - LUKS seems to be working does not boot - complains about missing root device Expected behavior Would boot :) Screenshots : ! : ! Additional context All my config for this machine starts from - I link this file in place of Notify maintainers maybe ? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. ^ using channel with kernel right now Happy to help debug this if needed :)
What filesystem are you using? If it's a mainlined filesystem, I don't believe hardened should've broken that. But it's probably depending on which is disabled in hardened.
Thanks so much for the reponse :) It's for , hopefully still mainlined ? ;) I can try to compile the kernel with set but otherwise with hardened settings enabled and see if it helps ?
Sorry, this is my fault! Yeah, my guess is that we need to re-enable AIO. I did notice some additional harmless-seeming warnings at boot that seemed AIO-related when writing (which switched to a patchset that disables AIO by default), but I guess it didn't affect any of my systems because they use ZFS. I was hoping AIO was only required by marginal things (like Oracle...), but LVM is pretty important. Given that nginx also uses AIO per , it might be worth explicitly turning it on in the default shared Kconfig (as I did for System V IPC in the original PR). I'm not sure if the AIO code is known to be particularly crufty by Linux standards or if it's just a general attack surface reduction thing; a few of the linux-hardened defaults are a bit better-suited to the Android environment than a desktop Linux distro. credits to the original linux-hardened author's Android-based which makes me suspect this might be the case here. Here's a nixpkgs diff to re-enable AIO: It'd definitely be good to know if this fixes things for you. should be enough to test this.

If you don't want to use a custom nixpkgs then you can do a fiddly thing like the definition of  in .
Also, this would be pretty easy to test for, so if this change fixes it then we should also update the hardened test to use LVM.
Heya, good news ! One kernel compilation later - I'm back to running thanks to you :) I tried the route and indeed it worked. For the test - I think that would be awesome, to catch things like this in the future :)
Change:
<del> { lib , aiohttp , aioresponses , beautifulsoup4 , buildPythonPackage , fetchFromGitHub , html5lib , pytest-asyncio , pytest-aiohttp , pytestCheckHook , pythonOlder , requests , requests-mock , setuptools , setuptools-scm , urllib3 </del> <ins> { lib, aiohttp, aioresponses, beautifulsoup4, buildPythonPackage, fetchFromGitHub, html5lib, pytest-asyncio, pytest-aiohttp, pytestCheckHook, pythonAtLeast, pythonOlder, requests, requests-mock, setuptools, setuptools-scm, urllib3, </ins> }: buildPythonPackage rec { pname = "raincloudy"; version = "1.2.0"; <del> format = "setuptools"; </del> <ins> pypriject = true; </ins> <del> disabled = pythonOlder "3.7"; </del> <ins> # https://github.com/vanstinator/raincloudy/issues/65 disabled = pythonOlder "3.7" || pythonAtLeast "3.12"; </ins> src = fetchFromGitHub { owner = "vanstinator"; <del> repo = pname; </del> <ins> repo = "raincloudy"; </ins> rev = "refs/tags/${version}"; hash = "sha256-qCkBVirM09iA1sXiOB9FJns8bHjQq7rRk8XbRWrtBDI="; }; <del> nativeBuildInputs = [ setuptools setuptools-scm ]; </del> postPatch = '' # https://github.com/vanstinator/raincloudy/pull/60 substituteInPlace setup.py  <del> --replace "bs4" "beautifulsoup4"  </del> <ins> --replace-fail "bs4" "beautifulsoup4"  </ins> # fix raincloudy.aio package discovery, by relying on # autodiscovery instead. sed -i '/packages=/d' setup.py ''; <del> propagatedBuildInputs = [ </del> <ins> build-system = [ setuptools setuptools-scm ]; dependencies = [ </ins> aiohttp requests beautifulsoup4

Discussion:
Steps to reproduce the behavior: python312Packages.raincloudy It seems it's related to building the test suite of . The package imports which appears to be deprecated from . Building from current . Appears to be an upstream bug, . <!-- 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:
(fetchNuGet { pname = "CommandLineParser"; version = "2.9.1"; sha256 = "1sldkj8lakggn4hnyabjj1fppqh50fkdrr1k99d4gswpbk5kv582"; }) (fetchNuGet { pname = "Concentus"; version = "1.1.7"; sha256 = "0y5z444wrbhlmsqpy2sxmajl1fbf74843lvgj3y6vz260dn2q0l0"; }) (fetchNuGet { pname = "DiscordRichPresence"; version = "1.1.3.18"; sha256 = "0p4bhaggjjfd4gl06yiphqgncxgcq2bws4sjkrw0n2ldf3hgrps3"; }) <del> (fetchNuGet { pname = "DynamicData"; version = "7.13.5"; sha256 = "088ry176ba314m4hc1vbcxisflqzs7p7vvn8vqzxy3kj1rimgfmf"; }) </del> <ins> (fetchNuGet { pname = "DynamicData"; version = "7.13.8"; sha256 = "10ywbzk58046kgsbd9rybpa9m1v11as45jvf1qvxnl42hyc7q654"; }) </ins> (fetchNuGet { pname = "ExCSS"; version = "4.1.4"; sha256 = "1y50xp6rihkydbf5l73mr3qq2rm6rdfjrzdw9h1dw9my230q5lpd"; }) (fetchNuGet { pname = "Fizzler"; version = "1.2.1"; sha256 = "1w5jb1d0figbv68dydbnlcsfmqlc3sv9z1zxp7d79dg2dkarc4qm"; }) (fetchNuGet { pname = "FluentAvaloniaUI"; version = "1.4.5"; sha256 = "1j5ivy83f13dgn09qrfkq44ijvh0m9rbdx8760g47di70c4lda7j"; })

Discussion:
Package name: ryujinx Latest released version: 1.1.747 <!-- Search your package here: --- Current version on the unstable channel: 1.1.743 Current version on the stable/release channel: 1.1.327 Notify maintainers Note for maintainers: Please tag this issue in your PR. Finally, for anyone who stumbles upon this issues, and wants an overlay to get them to 1.1.747 without waiting for the package to be updated:
An update to this package will require updating using the script (a process I'm unfamiliar with) and changing the testProjectFile attribute because all of the source was moved into the src/ directory. Other than that and updating the source, no other changes to the derivation should be necessary
Updating a package with an update script (if it's written correctly) should be as simple as: Thanks for detailing the testProjectFile change, that's super helpful. I'm in the process of updating now.
Change:
(if atLeast "9.6" then ./patches/less-is-more-96.patch             else ./patches/less-is-more.patch) (if atLeast "9.6" then ./patches/hardcode-pgxs-path-96.patch       else ./patches/hardcode-pgxs-path.patch) ./patches/specify_pkglibdir_at_runtime.patch <ins> ./patches/findstring.patch </ins> ] ++ lib.optional stdenv.isLinux ./patches/socketdir-in-run.patch; installTargets = [ "install-world" ];

Discussion:
postgresql is littered with files in out/share/postgresql. Please run and paste the results.
Weird. Not sure why GH did not close this.
Change:
xorg.libX11 xorg.libxcb xorg.libXcomposite xorg.libXcursor xorg.libXext xorg.libXfixes xorg.libXi xorg.libXrender xorg.libXtst <del> nss nspr atk at-spi2-atk dbus gdk-pixbuf pango cairo </del> <ins> xorg.libxshmfence libxkbcommon nss nspr atk at-spi2-atk dbus gdk-pixbuf pango cairo </ins> xorg.libXrandr expat libdrm mesa alsa-lib at-spi2-core cups ]; in stdenv.mkDerivation rec { <del> version = "4.1.6"; </del> <ins> version = "5.1.0"; </ins> pname = "staruml"; src = fetchurl { <del> url = "https://staruml.io/download/releases-v4/StarUML_${version}_amd64.deb"; sha256 = "sha256-CUOdpR8RExMLeOX8469egENotMNuPU4z8S1IGqA21z0="; </del> <ins> url = "https://staruml-7a0.kxcdn.com/releases-v5/StarUML_${version}_amd64.deb"; sha256 = "sha256-da1mY3OW24g6Ix0L57CBPbaMeSLzhOOjoBsyZszmNOc="; </ins> }; nativeBuildInputs = [ wrapGAppsHook dpkg ];

Discussion:
Steps to reproduce the behavior: on master Detected when reviewing locally Likely fixed by <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --unmaintained Please run and paste the result.

Package name: staruml Latest released version: 4.1.6 <!-- Search your package here: --- Current version on the unstable channel: 4.1.6 Current version on the stable/release channel: 4.1.6 <!-- 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. --No maintainers. Last update in version was automated by and last major package change by Note for maintainers: Please tag this issue in your PR.
Change:
xmind = callPackage ../applications/misc/xmind { }; <del> xneur = callPackage ../applications/misc/xneur { enchant = enchant1; }; </del> <ins> xneur = callPackage ../applications/misc/xneur { }; </ins> gxneur = callPackage ../applications/misc/gxneur  { inherit (gnome2) libglade GConf;

Discussion:
Enchant 2 (now the default) is long supported by most packages. The following packages need to be updated or removed: [x] gtkspell2 (dead): [x] xiphos: [x] subtitleeditor: [x] xneur: (contains the removal of enchant1) [x] gnome2.gtkhtml (dead): [x] gnome2.gtkhtml4 (dead): [x] gnome.gtkhtml (dead?): [x] php.extensions.enchant:
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 . on the on .
This issue is still relevant.
the list from is not up-to-date. e.g. is already fixed maybe we can also close it, because defaults to version 2 and to version 1.
I marked this as stale due to inactivity. &rarr;
Updated the list.
Now with xiphos merged You can thick both xiphos and gnome2.gtkhtml4 off the checklist
Pushed the enchant1 removal commit to
Change:
x86_64-darwin-version = "4.38.121"; x86_64-darwin-sha256 = "1w0s6j8z8961sv4y00jxpy5gjlj0dswyxs15c7isb26ii11nn1i2"; <del> x86_64-linux-version = "4.38.121"; x86_64-linux-sha256 = "0qp7wxmdg2lpvbx7gshgbqxf7jjvgnwx20cfjwgw6wwzanb0gi96"; </del> <ins> x86_64-linux-version = "4.38.125"; x86_64-linux-sha256 = "sha256-BJeFXZ8STbMCmGvYRoFsfsyIpGukQkuwv0m2NzE+89c="; </ins> aarch64-darwin-version = "4.38.121"; aarch64-darwin-sha256 = "161z947p7a2d7584hybl77chab8y027cqpph2hd2s4b5k6bchkj5";

Discussion:
Slack reproducibly crashes: Steps to reproduce the behavior: to Sway Slack It should not crash If applicable, add screenshots to help explain your problem. 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:
libraryToolDepends = [ CoreServices ]; description = "File/folder watching for OS X"; license = stdenv.lib.licenses.bsd3; <del> platforms = stdenv.lib.platforms.none; </del> <ins> platforms = [ "x86_64-darwin" ]; </ins> }) {inherit (pkgs.darwin.apple_sdk.frameworks) Cocoa; inherit (pkgs.darwin.apple_sdk.frameworks) CoreServices;};

Discussion:
The issue is due to an inverted logic error marking not supported on darwin when it should be marked as only supported darwin instead. cc an expression depending on Nix 2.0.4 on x86_64-darwin on Travis
Tried this again with travis with nixpkgs pinned to this commit, but it still fails for some reason, any ideas?
That commit configures which generates that file, so it takes another run of that tool before the configured changes take effect. has the update.
Is a full regen expected on 19.03 as well before release? Right now, the job does not eval because of this, but I guess we don't need to manually poke it if it's going to be regenerated. :)
I don't think we'll re-generate on the release branch any time soon, so manually submitted changes there are probably the way to go. I might do a complete update at some point in the future, but I can't say for sure. Updating a branch that's supposed to be stable is a lot of work.
Change:
patches = [ ./xfce4-panel-datadir.patch ]; patchFlags = "-p1"; <ins> postPatch = '' for f in $(find . -name *.sh); do substituteInPlace $f --replace gettext ${gettext}/bin/gettext done ''; </ins> outputs = [ "out" "dev" "devdoc" ]; buildInputs =

Discussion:
System: 18.03pre116572. (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: "18.03pre116572." Sandboxing enabled: false
Change:
githubId = 62279738; name = "Håkon Arvidsen"; }; <ins> HaskellHegemonie = { name = "HaskellHegemonie"; email = "haskellisierer@proton.me"; github = "HaskellHegemonie"; githubId = 73712423; keys = [ { fingerprint = "A559 0A2A 5B06 1923 3917  5F13 5622 C205 6513 577B"; } ]; }; </ins> haslersn = { email = "haslersn@fius.informatik.uni-stuttgart.de"; github = "haslersn";

Discussion:
Battery status notifications <!-- Describe the project a little: --Metadata homepage URL: source URL: license: Mozilla Public License 2.0 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
dontBuild = true; dontConfigure = true; <ins> noDumpEnvVars = true; </ins> installPhase = '' runHook preInstall

Discussion:
Describe the bug Running on vscode binary says that it depends only on gtk3: While the package depends on both gtk2 and gtk3: Probably there are some packaging issue? To Reproduce Steps to reproduce the behavior: vscode Expected behavior It depends only on gtk3 Notify maintainers Metadata Maintainer information:
Also gconf vs. dconf and libgnome-keyring vs. libsecret. See also
Hmm yeah, I removed and from , and both vscode and vscodium seem to still run fine. Not sure where the gconf/dconf thing is determined, possibly that that's an Atom issue
libsecret is the replacement for libgnome-keyring, not the other way around. It will probably be used at runtime when it needs to access keyring. dconf is used by GTK, gconf should not be used at all.
I marked this as stale due to inactivity. &rarr;
Still an issue
Change:
index 8d3df15..6156206 100755 --- a/setup.py +++ b/setup.py <del> @@ -2359,10 +2359,7 @@ if v4l2_ENABLED: v4l2_pkgconfig = pkgconfig() #fuly warning: cython makes this difficult, #we have to figure out if "device_caps" exists in the headers: -    ENABLE_DEVICE_CAPS = False -    if os.path.exists("/usr/include/linux/videodev2.h"): -        hdata = open("/usr/include/linux/videodev2.h").read() -        ENABLE_DEVICE_CAPS = hdata.find("device_caps")>=0 +    ENABLE_DEVICE_CAPS = True kwargs = {"ENABLE_DEVICE_CAPS" : ENABLE_DEVICE_CAPS} make_constants("xpra", "codecs", "v4l2", "constants", **kwargs) </del> <ins> -2322,11 +2322,7 @@ if v4l2_ENABLED: videodev2_h = "/usr/include/linux/videodev2.h" constants_pxi = "xpra/codecs/v4l2/constants.pxi" if not os.path.exists(videodev2_h) or should_rebuild(videodev2_h, constants_pxi): -        ENABLE_DEVICE_CAPS = 0 -        if os.path.exists(videodev2_h): -            with open(videodev2_h) as f: -                hdata = f.read() -            ENABLE_DEVICE_CAPS = int(hdata.find("device_caps")>=0) +        ENABLE_DEVICE_CAPS = 1 with open(constants_pxi, "wb") as f: f.write(b"DEF ENABLE_DEVICE_CAPS=%i" % ENABLE_DEVICE_CAPS) </ins> cython_add(Extension("xpra.codecs.v4l2.pusher", diff --git a/xpra/x11/bindings/keyboard_bindings.pyx b/xpra/x11/bindings/keyboard_bindings.pyx index bd7023d..064c6b5 100644 --- a/xpra/x11/bindings/keyboard_bindings.pyx

Discussion:
Describe the bug NixOS currently has Xpra 2.5.3. Metadata Maintainer information:
cc
please test
Change:
default = if lib.versionOlder config.system.stateVersion "24.05" then "${httpConf.scheme}://${httpConf.host}:${builtins.toString httpConf.port}/media/" else null; <ins> defaultText = literalExpression '' if lib.versionOlder config.system.stateVersion "24.05" then "${httpConf.scheme}://${httpConf.host}:${builtins.toString httpConf.port}/media/" else null; ''; </ins> description = '' Base path which uploads will be stored at. Whilst this can just be set to a subdirectory of the main domain, it is now recommended to use a different subdomain.

Discussion:
Seems like introduced a dependency on inside the default of , which make fail to build with: Steps to reproduce the behavior: to build a based on System builds fine Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: