jiebi/CodeConvo huggingface dataset:
Change:
buildPythonApplication rec { pname = "nile"; <del> version = "1.0.0"; </del> <ins> version = "unstable-2023-10-03"; </ins> format = "pyproject"; src = fetchFromGitHub { owner = "imLinguin"; repo = "nile"; <del> rev = "f5f3b96f6483c59cfc646afbda6e97cb0bd94778"; hash = "sha256-HibY3U9/MibEDwHY+YiErW/pz6qwtps8wwjhznTISgA="; </del> <ins> rev = "8f7ab2650fc730efc8960b5fcd71421d724a4108"; hash = "sha256-Vhjp9JX8VX0PWsvEh5eOhz7vsIEaiCyPNPOjibE8GXo="; </ins> }; disabled = pythonOlder "3.8";

Discussion:
Heroic Launcher while trying to install a game from gog will download it, but won't install it. You can see downloaded installer inside your directory. After "installation", launcher will say on the game's details screen that It should install. ! You can't just use the gog installer like in a normal linux distribution: So you need to use steam-run to install it. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --heroic-launcher: 2.9.2 - unstable nixpkgs
This sounds exactly like a bug I encountered in a previous version of Heroic, but they have since fixed it, and I have not run into it on 2.9.2. Could you please attach the Heroic log file from right after trying to install the game? It's accessible via the sidebar Settings-Log.
<details</details
It looks like it successfully installs, going by that log. I seem to vaguely recall now having some issues with my GOG library in Heroic 2.9.2, and I eventually removed (with Heroic closed) and logged in to GOG through Heroic again, and it's been behaving since. You might try that, otherwise I don't see anything indicating this would be an issue specific to the Heroic package, so I think it would be appropriate to go to upstream's support channel, which is .
I will try moving to nixpkgs unstable and see if it was an issue of using stable and unstable in the same time. It should not, but maybe it is. Thank you for your help PS. I tried different game and the situation is still the same.
I found that heroic needs unzip to be installed to extract the gog linux installers. When I have somewhere in my installed packages (home or system), it just works. Probably it will have to be to the heroic wrapper.
Could you please try changing in your Nix config to the following and see if that fixes your problem?
By using: Everything started to work.
Change:
"OvmfPkg/OvmfPkgX64.dsc" else if stdenv.hostPlatform.isAarch then "ArmVirtPkg/ArmVirtQemu.dsc" <ins> else if stdenv.hostPlatform.isRiscV then "OvmfPkg/RiscVVirt/RiscVVirtQemu.dsc" </ins> else throw "Unsupported architecture";

Discussion:
Steps to reproduce the behavior: pkgsCross.aarch64-multiplatform.edk2 Full log here: Few last lines: EDK2 package was updated in nixpkgs, and after that cross-compilation from x86_64 to aarch64 stopped working. The issue appeared in latest update commit: The package has no maintainers set in meta. The breaking change was introduced by: I see cross-compilation fixes have been made previously by: Other contributors who have contributed over the past year, I got from and : "Sandro Jäckel" and Please run and paste the result.
Actually I had binfmt for aarch64-linux emulated, I disabled it and now build fails even earlier when it tries to run antlr built for aarch64-linux:
Unable to reproduce: I just cross compiled EDK2 with .
Wait, I had a dinosaur nixpkgs there on a feature branch, testing again.
I concur, antlr is trying to be executed but it's not a binary for the right platform. This seems to be a breakage upstream as they seem to ship their own ANTLR binaries.
I won't have time to tackle it as I have too much on my plate right now.
Any change on looking at this now as we are going towards NixOS 23.11?
Thank you!
Change:
}; testScript = '' <del> machine.succeed("findmnt --kernel --type overlay /etc") machine.fail("stat /etc/newgen") machine.succeed("echo -n 'mutable' > /etc/mutable") </del> <ins> with subtest("/etc is mounted as an overlay"): machine.succeed("findmnt --kernel --type overlay /etc") </ins> <del> machine.succeed("/run/current-system/specialisation/new-generation/bin/switch-to-configuration switch") </del> <ins> with subtest("switching to the same generation"): machine.succeed("/run/current-system/bin/switch-to-configuration test") </ins> <del> assert machine.succeed("cat /etc/newgen") == "newgen" assert machine.succeed("cat /etc/mutable") == "mutable" </del> <ins> with subtest("switching to a new generation"): machine.fail("stat /etc/newgen") machine.succeed("echo -n 'mutable' > /etc/mutable") machine.succeed("/run/current-system/specialisation/new-generation/bin/switch-to-configuration switch") assert machine.succeed("cat /etc/newgen") == "newgen" assert machine.succeed("cat /etc/mutable") == "mutable" </ins> ''; }

Discussion:
Steps to reproduce the behavior: /run/current-system/bin/switch-to-configuration test Does not crash system/systemd This can be reproduced using this test in sops-nix: Edit to have this change <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Related to
It seems like it's reusing the same loop device when mounting the new overlay...
Change:
src = fetchurl { url = "https://codeberg.org/dnkl/foot/raw/tag/${version}/scripts/generate-alt-random-writes.py"; <del> sha256 = "019bdiqfi3wx2lwrv3nhq83knc1r3lmqd5zgisa33wwshm2kyv7p"; </del> <ins> sha256 = "0w4d0rxi54p8lvbynypcywqqwbbzmyyzc0svjab27ngmdj1034ii"; </ins> }; dontUnpack = true;

Discussion:
Project description The terminal is already packaged in nixpkgs. As foot uses its own terminfo, this terminfo is needed on any remote servers you connect to using foot. It would be useful to have this terminfo packaged as its own output as with other terminals: alacritty, kitty, rxvt-unicode to name a few. ping foot maintainer for feedback Metadata homepage URL: source URL: license: mit platforms: linux
That is a very good idea! Unfortunately it doesn't seem to be possible to specify a separate install directory for foot's terminfo so far (it is installed to along with the license etc.). I'll open an upstream ticket, they are usually very helpful, and then we'll be hopefully be able to set this pretty soon.
Change:
oguri = callPackage  ../tools/wayland/oguri { }; <ins> shikane = callPackage ../tools/wayland/shikane { }; </ins> shotman = callPackage ../tools/wayland/shotman { }; slurp = callPackage ../tools/wayland/slurp { };

Discussion:
Project description <!-- Describe the project a little: --A dynamic output configuration tool for wlroots that automatically detects and configures connected outputs based on a set of profiles. Metadata homepage URL: source URL: license: mit platforms: linux
I already got the package made in my config, will see about sending a pr tomorrow
Sorry, I didn't notice your post and submitted a PR. Could you please check it? Also, would you like to become a maintainer?
No worries, I will get around checking it today. Yeah I would not mind doing so, it was partially why I took a stab at writing a pkg config in the first place.
just to update, everything works. Did not know whether to post here or on the PR. Also since the PR is already posted and it works, is there anything extra on my end that you would like me to do about maintaining it?
Sorry, I'm late. Thanks for your confirmation. Since it seems difficult to edit this branch with you, could you please add yourself to the maintainer-list in another PR? Once it is merged, I will add you to the maintainers.
Done will be waiting for the merge.
Change:
systemd = let <del> service = </del> <ins> sshd-service = </ins> { description = "SSH Daemon"; wantedBy = optional (!cfg.startWhenNeeded) "multi-user.target";

Discussion:
If you have no hostkeys and try to connect to the openssh server, it will generate the keys but also send quite a bit of information to the client. I am not sure if this is an actual security issue but I wanted to bring it up just to make sure. hostkeys in /etc/ssh. with output will include System: (NixOS: , Ubuntu/Fedora: , ...) (Gorilla) Nix version: (run ) nix-env (Nix) 1.11.4 Nixpkgs version: (run ) ""
This is happening because of I'll create a PR with a fix tomorrow.
Yikes! Seems like way over-sharing to me.
Change:
owner = "Textualize"; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-4ehq36j2n2wRMgos5x4LQ0QeELpWAOgpgTxEWjqFLJs="; </del> <ins> hash = "sha256-+3bxc0ryHtbEJkB+EqjJhW+yWJWxMkxlSav4v6D3/gw="; </ins> }; nativeBuildInputs = [

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:
tart = callPackage ../applications/virtualization/tart { }; <del> viber = callPackage ../applications/networking/instant-messengers/viber { }; </del> wavebox = callPackage ../applications/networking/instant-messengers/wavebox { }; sonic-pi = libsForQt5.callPackage ../applications/audio/sonic-pi { };

Discussion:
Steps to reproduce the behavior: the last commit removed the use of webarchive <!-- 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]:
Hello, I'm not the maintainer. I think you meant to ping :+1:
I think there is one issue with latest viber update - it use url downloaded directly from viber instead of former practice using which lead to the hash mismatch issues. I tried following overlay to fix them The latest file from viber for linux with the hash have some hard code that result failed to launch with message that on NixOS
Change:
{ stdenv, fetchFromGitHub, autoreconfHook, pkgconfig, glib, syslogng <del> , eventlog, perl, python, yacc, riemann_c_client, libivykis, protobufc </del> <ins> , eventlog, perl, python, yacc, protobufc, libivykis </ins> }: stdenv.mkDerivation rec { name = "syslog-ng-incubator-${version}"; <del> version = "141106-54179c5"; </del> <ins> version = "0.5.0"; </ins> src = fetchFromGitHub { owner = "balabit"; repo = "syslog-ng-incubator"; <del> rev = "54179c5f733487fe97ee856bc27130d0b09f3d5a"; sha256 = "1y099f7pdan1441ycycd67igcwbla2m2cgnxjfvdw76llvi35sam"; </del> <ins> rev = name; sha256 = "00j123ya0xfj1jicaqnk1liffx07mhhf0r406pabxjjj97gy8nlk"; </ins> }; <ins> nativeBuildInputs = [ pkgconfig autoreconfHook yacc ]; </ins> buildInputs = [ <del> autoreconfHook pkgconfig glib syslogng eventlog perl python yacc riemann_c_client libivykis protobufc </del> <ins> glib syslogng eventlog perl python protobufc libivykis </ins> ]; configureFlags = [ <del> "--without-ivykis" </del> "--with-module-dir=$(out)/lib/syslog-ng" ];

Discussion:
I'm upgrading my systems from NixOS 16.03 to 16.09 and I'm trying to get syslog-ng working again. It's currently configured as: The issue is that systemd is not noticing that syslog-ng has started: I do see that syslog-ng is running: Note that the systemd syslog-ng service is with This that syslog-ng should notify systemd when it has started up. My current hypotheses is that with the systemd upgrade to 231 something in the notification protocol has changed causing the syslog-ng notification to fail.
It has strange config: how could this work ? could you test this? syslog-ng at least starts for me
thanks with those changes syslog-ng starts up correctly.
means that the syslog-ng unit will be activated (started) if gets activated. By itself this relation defines no order. That's why you can add and relations as you wish. As I've mention in , the root problem is that our current version of syslog-ng can't be built with our current version of systemd and thus the sd-notify feature is not present.
Hi I did some work on the syslog-ng upgrade. I've managed to get syslog-ng-3.9.1 to build with I will now test this a bit.
Change:
}; in (python.withPackages (ps: [ unwrapped ])).overrideAttrs (_: { <ins> # otherwise will be exported as "env", this restores `nix search` behavior name = "${unwrapped.pname}-${unwrapped.version}"; </ins> # export underlying qtile package passthru = { inherit unwrapped; }; })

Discussion:
After running , the command shows the correct package but with the wrong version and description. Steps to reproduce the behavior: the reported version being and description being "A high-level dynamically-typed programming language" The version reported should state , and the description should read "A small, flexible, scriptable tiling window manager written in Python", as per ! It appears that the Qtile search has taken on the version and description of the Python version it depends on, as opposed to the items defined in the nix file.
ah yea, this was me
Change:
serviceConfig = defaultServiceConfig // { User = cfg.user; ExecStart = '' <del> ${pkgs.python3Packages.gunicorn}/bin/gunicorn  </del> <ins> ${pkg.python.pkgs.gunicorn}/bin/gunicorn  </ins> -c ${pkg}/lib/paperless-ngx/gunicorn.conf.py paperless.asgi:application ''; Restart = "on-failure";

Discussion:
I'm using paperless 1.8.0 from unstable on a nixos-22.05 system. (via the services.paperless.package option) The paperless 1.6.0 in 22.05. does work without issue. When editing a document in the web interface the preview is missing. The Firefox Web Developer Tools shows a 500 error for requests to /metadata URLs. In the server log Django shows import error for PIL: Steps to reproduce the behavior: the paperless service, configure a superuser and login in the Web UI the top right click the username and go to settings. Make sure that 'Use PDF viewer provided by the browser' is enabled. Save. a document (e.g. a PDF) in the Web UI the document, notice missing preview on the right side logs for error message, e.g. via See the PDF document while editing.
It looks like it's an issue specific to using the unstable package on the stable release. My guess is that the service config invokes the webserver with stable gunicorn (with gunicorn) but with the unstable paperless package environment, which doesn't mix well (esp. when they both use different Python versions). See and
Does fix this?
Change:
inherit buildCommand name; passAsFile = [ "buildCommand" ] ++ (derivationArgs.passAsFile or []); <ins> } // lib.optionalAttrs (! derivationArgs?meta) { </ins> pos = let args = builtins.attrNames derivationArgs; in if builtins.length args > 0 then builtins.unsafeGetAttrPos (builtins.head args) derivationArgs

Discussion:
Hello I was trying to review just now the source code that 'rstudioWrapper' uses. When I hit source from nixos-search I was redirected to this link However after checking in , I noticed that the expression that runs 'rstudioWrapper' is this one I'm not sure why this is happening, nor if the report should be here or in nixpkgs. In case I made a mistake, I would appreciate if you let me know so I can open another report. Thank you very much for nixos-search, I can't imagine the Nix experience without this amazing search engine.
This is indeed a nixpkgs issue as nixos-search just links to . The default position is determined by , so things like usually get their position reported at the definition of rather than at its call site. Maybe that could be fixed by making use the position of one of its arguments, but I don't think there's anything to be done in the case where the second argument is empty ().
Oh, that was fast. Thanks for your help! I stay tuned if I can/should do anything.
Hello again! I'm just seeing that your PR has already been merged. Do you agree if we close this issue, or is there anything left? nix-search unstable already perfectly references rStudioWrapper! Thank you very much for your help.
This is probably not completely solved yet (uses of without arguments would still have incorrect position information) but there's nothing actionable left to do so we might as well close it.
Change:
''; }; <ins> phpExtraExtensions = mkOption { type = with types; functionTo (listOf package); default = all: []; defaultText = "all: []"; description = '' Additional PHP extensions to use for nextcloud. By default, only extensions necessary for a vanilla nextcloud installation are enabled, but you may choose from the list of available extensions and add further ones. This is sometimes necessary to be able to install a certain nextcloud app that has additional requirements. ''; example = literalExample '' all: [ all.pdlib all.bz2 ] ''; }; </ins> phpOptions = mkOption { type = types.attrsOf types.str; default = {

Discussion:
Many nextcloud extensions like need additional php extensions that are not part of the . It would be great to either: Provide an option to override the php package nextcloud uses, i.e. Or: Provide an option , and make the current extension selection its default value I'm opening this as an issue to get some feedback on what the better option is, and to get the naming right. CC maintainers
Meta: I'm not sure all labels I've applied make sense here. Feel free to remove inappropriate ones. Also: There is no PHP label?
cc
Change:
propagatedBuildInputs = [ cloudpickle crcmod <del> cython </del> dill fastavro <ins> fasteners </ins> grpcio hdfs httplib2 numpy <del> oauth2client </del> <ins> objsize </ins> orjson proto-plus protobuf

Discussion:
Build of failed on x86_64-linux as of . This is currently breaking . python39Packages.tensorflow-datasets maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: - -
huh this is a weird failure to me since fasteners==0.18 at the time of this commit which should be working... building locally on this commit i get a different failure: very peculiar...
Change:
{ stdenv, fetchurl, qt48 }: let <del> baseVersion = "2.7"; revision = "1"; </del> <ins> baseVersion = "2.8"; revision = "0"; </ins> version = "${baseVersion}.${revision}"; qt4_for_qtcreator = qt48.override { developerBuild = true;

Discussion:
I don't think exists in Bash?
See and
Okay, then why am I seeing this?
Because this is not how you should use . Look for examples in nixpkgs. Try this:
Ah, I see. Thanks for your help!
Change:
in stdenv.mkDerivation rec { pname = "gnome-shell"; <del> version = "44.1"; </del> <ins> version = "44.2"; </ins> outputs = [ "out" "devdoc" ]; src = fetchurl { url = "mirror://gnome/sources/gnome-shell/${lib.versions.major version}/${pname}-${version}.tar.xz"; <del> sha256 = "C/vkOU0mdiUVTQjQFGe9vZnoFXUS/I30XVwC3bdVHKY="; </del> <ins> sha256 = "VfJ57GMDt8DIkkbs7YEkfIf8HHOUj0XrISpkchjRtj8="; </ins> }; patches = [

Discussion:
Package name: gnome-shell Latest released version: 44.2 <!-- Search your package here: --- Current version on the unstable channel: 44.1 Current version on the stable/release channel: 44.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.

Since the Gnome 44 (under wayland) update, on multiple devices reproducible errors with Qt based applications. nextcloud-client: The application does not show itself after first start, it is only visible in Activities as an empty frame. You have to restart the application and it works. keepassxc: The Drag-and-Drop functionality does not work. This are only two errors that I found, but I think many Qt-applications are affected. The solution is to set inside a shell and start the application. The errors vanish. Currently, my workaround is setting it global with Perhaps, can you add the variable as a default setting for each gnome under wayland session? Thank you <!-- 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.
Could you please try if fixes it?
Does not solve the problem.
QT has also issue with wireshark (QTSTYLEOVERRIDE)
strawberry player is also affected. Outputs: When running: drag and drop works, without that env variable drag and drop does not work. Did not found a way that works on X11.
I am also experiencing this issue, under x11. 's drag and drop does not work, which renders the program almost unusable.
Also experiencing this issue with QGIS.
has possible fix for
Will this get backported to stable?
Already happened
Change:
in [ "--buildtype" "release" <del> "--cross-file" "build-win${arch}.txt" </del> "--prefix" "${placeholder "out"}" <del> ]; </del> <ins> ] ++ lib.optionals isCross [ "--cross-file" "build-win${arch}.txt" ] ++ lib.optional glfwSupport "-Ddxvk_native_wsi=glfw"; doCheck = isDxvk2 && !isCross; </ins> meta = { description = "A Vulkan-based translation layer for Direct3D 9/10/11";

Discussion:
In future releases of dxvk the setup script won't be included anymore so this issue is just to notify so something can be figured out for how the nix package should handle it beforehand. (Hope such an issue is okay) See
CC
Thanks for the heads up. The DLLs are already available via a output, but this will break anyone’s set up that relies on . A short term solution would be to vendor the script. Longer term, it would be ideal if there were a way to declaratively create and manage a Wine prefix.
1 has been released with the script removed
I saw that. It can also build natively on Linux, which is interesting. I need to think about how I want to do things and maybe see what other distributions that package it are doing.
God speed
There is a nix-gaming repository that contains such derivation: It also handles vkd3d-proton:
One approach I’m considering is splitting dxvk into dxvk110 (for Darwin and hardware no longer supported by 2.0) and dxvk2x (or just dxvk_2, not sure). The plain DXVK derivation could continue to provide the script (most likely copied from before upstream removed it) while the versioned ones would be built for the native platform only (Linux and Windows). Well, I guess if it builds on Darwin, I can set the platform to then mark it broken on Darwin. I doubt DXVK 2.0 will work on Darwin any time soon. There are a number of extensions DXVK needs that aren’t implemented yet in MoltenVK, and since DXVK is always adding and using new ones, it’s a moving target.
I created to add the script and bump DXVK. It also exposes native builds on Linux.
Change:
{ stdenv, fetchurl, makeWrapper, pkgconfig, cmake, fcitx, gtk3, isocodes, gnome3 }: stdenv.mkDerivation rec { <del> name = "fcitx-configtool-0.4.8"; </del> <ins> name = "fcitx-configtool-0.4.9"; </ins> meta = with stdenv.lib; { description = "GTK-based config tool for Fcitx";

Discussion:
after a , fcitx cannot switch to mozc only in chromium. journalctl gives me System: (NixOS: , Ubuntu/Fedora: , ...) 09pre106117. (Hummingbird) Nix version: (run ) nix-env (Nix) 1.11.8 Nixpkgs version: (run ) "17.09pre106117." fcitx version: 4.2.9.1 Chromium 57.0.2987.133
Thanks for reporting! Will look into this.