When using incus with openvswitch, incus needs to have openvswitch in its path for features involving openvswitch to work. As a result, when attaching an openvswitch as a bridged interface in incus, we encounter issues such as veth interface remaining active when it should be cleaned up, not being able to use openvswitch to make bridges, etc. It is not so urgent because it's easy enough to add it to the path, but it caused me some trouble until I figured out the cause. Enable openvswitch, enable incus, run "incus network create BRIDGENAME —type bridge " and notice that incus does not detect openvswitch. If openvswitch is enabled, openvswitch will be to incus's path, and the above command will not fail. Can be resolved by adding = [ pkgs.openvswitch ]; Maybe just need to check if openvswitch enabled, and if so, add it to the path by default? <!-- --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Do you have a vswitch configuration you're able to share?
Yes, but if I configure it using nixos, I get other problems (incus is deleting the whole bridge whenever I shut down a container and I don’t know what part of nixos is responsible for it), so I have switched to configuring it with networkmanager, where it all works well, as long as I add openvswitch to path. But here is a very simple example with a nixos configuration: = true; networking.vswitches = { br0 = { interfaces = { eth0 = { }; }; }; }; networking.interfaces.vmbr0.useDHCP = true; Just adjust eth0 to whatever device you want to add to the bridge. Then in incus, we can add a profile. Easy way to do this is set up the default profile. Then we copy it to a new one: incus copy profile default ovstest and edit it incus profile edit ovstest Then replace the networking eth0 part with the below: devices: eth0: name: eth0 nictype: bridged parent: br0 type: nic Then make a container on the profile: incus launch images:debian/bookworm mycontainer —profile ovstest It should work fine, but (this is a bug I think I haven’t reported because it could be my own stupidity) when you stop the container incus stop mycontainer All of your configured bridges will be missing, completely. So the way I do it now is enabling network manager. We can add eth0 to a network manager-defined ovs bridge this way: Setting it up like this, and adding the line below, everything is working as expected. (If I don’t add the path = line, the virtual ethernet devices don’t get cleaned up when incus shuts down a container, which is why I filed the bug report to try to have it included default) = { path = [ pkgs.openvswitch ]; Hopefully this answers what you are looking for.
Thanks! Sounds like you have a workaround until this can get fixed in the module. I'm not quite sure why your bridge is being removed when the container is stopped. You could try creating a bridge instead, but then it looks like you should be setting I tried to test this, but creating an ovs bridge yields:
I think it is because that ovs bridge doesn't exist yet. If you just attach a pre-existing ovs bridge to the container, it will work. Regular linux bridges defined with the nixos configuration also have the same disappearing problem, but with networkmanager work fine.
Actually the error I encountered is a bug.
I'm not able to reproduce your issue where the stopping of the container removes a bridge from the host. Are you on 23.11 or unstable?
This is on 23.11.
If you are able, can you try and reproduce the bridge removal using nixos unstable?
Sure, I will give it a go.
So, yes, I can reproduce it on unstable. Both with linux switches and with openvswitch switches. Here is all of the configuration related to networking. You can see the commented lines would be how I set up the linux bridges when testing them. = true; virtualisation.vswitch.resetOnStart = true; networking.useDHCP = false; networking.hostName = "boss"; = true; = "eth0"; networking.interfaces.vmbr0.ipv4.addresses = [{ address = "192.168.0.2"; prefixLength = 24; }]; = [{ address = "0.0.0.0"; prefixLength = 0; via = "192.168.0.1"; options = { metric = "100"; }; }]; = "eth1"; networking.interfaces.vmbr1.ipv4.addresses = [{ address = "192.168.1.2"; prefixLength = 24; }]; = [{ address = "0.0.0.0"; prefixLength = 0; via = "192.168.1.1"; options = { metric = "101"; }; }]; "" = true; = false; networking.nameservers = ["1.1.1.1" "8.8.8.8”];
I have created a pull request to resolve the path issues.


Decent Sampler is supposed to have a standalone app, a VST2 plugin and a VST3 plugin. The package decent-sampler installs only the standalone app. The downloaded archive contains also which is the VST2 plugin and the directory which is the VST3 plugin. Steps to reproduce the behavior: decent-sampler. for the VST plugins 't find them. The VST3 plugin should be installed in of the package and the VST2 plugin too should be in the package, but I don't know where exactly. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


, it will fail when it can't find check hydra: works, but also generates deprecation warnings. 0.9.3 (as used by Hydra) isn't an official release at Github. 0.9.4 fixes the deprecation warnings (save for flagging a future dependency and one other future.) Bump to version 0.9.4 coming momentarily. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


The searx service is trying to start and it fails because the actual name is of the executable has been changed to Steps to reproduce the behavior: ... use newest unstable branch ... try to deploy searx service with ... searx service fails to start searx service should start without any issues The default searx package on Nixos is in Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for reporting, I just encountered this bug as well after I updated to the latest unstable branch. I believe that a general migration from to naming needs to be done to avoid these kind of issues in the future.


Some packages, e.g. requires nodejs16 (znck/grammarly), but I cannot override the nodejs version of the package to nodejs16 because it is EOF. Steps to reproduce the behavior: nodejs version of some nodejs package by doing the error message. Allow forcing the use of EOL packages, or maybe officially state that this is not supported and mark the package as broken. 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]:
Allow forcing the use of EOL packages, or maybe officially state that this is not supported If you run: , you'll get all the instructions on how to do this. This has been marked as broken:
Sorry, I was not aware that I can get instructions when doing directly. Will do. For marking the package as broken, I mean instead of . Sorry for the bad wording.


the PR template points to instead of Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I kindly ask you to just create the PR the next time with this really trivial change instead of creating an issue.
it's only trivial if you have experience with how github works. i had no idea the template was controlled by a file within the repo and not some option in the settings.


Project description <!-- Describe the project a little: --The hyprland cursor format, library and utilities. Metadata homepage URL: source URL: license: BSD3 platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Sessions are not restored on startup of Firefox 30.0. . firefox. the Preference. tab, select for . and . Ctrl-Q to quit the Firefox. firefox again. Firefox opens and Opens the start page. It works for Firefox 30.0 for Mac, 30.0 for Windows, or 29.0.1 for NixOS.
I can confirm that. The good news is that your session is not lost. It looks like the UI has some issue, but the session is kept fine. So if you re-install version 29.0.1 you will have your tabs (including groups and pinned tabs) back.
I have rollbacked to 29.0.1 and the session is restored.


Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- 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]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…


Project description A simple GTK4 based video player for mobile phones Metadata homepage URL: source URL: license: GPL3 platforms: Linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi. Is this a package you're working on? If not, I packaged it but I'm not sure if it's correct. I can send a PR for it as starter. [It's the first time I built anything on NixOS].
Not currently working on this, but can help test.
I a PR for this. It would be great if you could check it out. Though running it gives this warning but can play videos. Also I couldn't play x265 videos with it. Is this normal?


When changing an SVP option during playback or the played file in mpv, starting from mpv 0.37.0, due to , it spams: and SVP no longer reports any connected player at the bottom of its window after that. top left logo, "Open file via mpv", pick a video the video is playing, switch back and forth between one of the buttons under "Do frame rate conversion" like "To screen" and "Movie x2" In mpv 0.36 and earlier, it says: and SVP keeps working normally. SVP has no source code available and new versions haven't been released on Linux since 2021, while mpv 0.37 came out in November 2023, making it unlikely to be fixed upstream any time soon. I've made a dirty workaround by to re-add the option, and overriding the source of the mpv package in my flake + home-manager setup. Handling both the external mpv package and the one within SVP's (the mpv that gets used by SVP's in-GUI "Open file") gets complicated - here are the relevant parts: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks for your investigation! Indeed it looks like modifying mpv to add the option back is the best way. Based on the diff on your fork, the change seems small enough for us to maintain. On the other hand, patching SVP is impossible due to its tamper protection.
A couple questions: the mpv package gets updated, it might break building SVP with the patch. Do github checks catch these cases, or will the SVP package just be broken until someone else notices? I give you push access to the forked repo, to rebase and regenerate the patch as needed? I rarely update my system, so the repo will likely be left randomly outdated until I have to take care of it. you make the SVP package take and overridable parameters, so that it isn't so hard to e.g. add scripts to the internal mpv? to make a standard external mpv connect to SVP will fail since it won't be patched, is there a good way to indicate to users that they should install in their environment? The parameters mentioned above should probably also be made known.
package in nixpkgs will be broken. However I also have this SVP package on my NUR, and have daily CI runs to rebuild packages, so once it breaks I will notice and make a fix. isn't necessary. I can rebase the patch on mainline mpv as needed. will add them. can't think of any good way for now.


Steps to reproduce the behavior: stig If I try to install it from my config, I get . If I try to run it by nix-shell: is the nixpkgs commit I'm currently using to get a working version of this program. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The different experience you get with vs is a problem in your Nix environment - probably an old version of nixpkgs you use for vs how you build "your config". However the test failing mark this package is now completely broken. See also discussion with upstream at: . I opened that marks stig as broken, and it will close this issue when merged.
stig works for me with this overlay: I think since addresses
It'd be great if you'd share this in a PR.
Opened at !


Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: - -
Thanks and !


Steps to reproduce the behavior: .config.contentAddressedByDefault = true; .firefox.package = pkgs.wrapFirefox pkgs.firefox-devedition-unwrapped {}; to build I also have march/mtune set and can't/won't use firefox-bin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is $outPath of gcc
I think my fix worked


Package name: koreader Latest released version: 2024.03.1 <!-- Search your package here: --- Current version on the unstable channel: 2023.04 Current version on the stable/release channel: 2023.04 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
please test


fails to find libcdparanoia and flac at runtime. This is a regression from , and appears to be more or less the same issue, except for Plasma 6. Steps to reproduce the behavior: to rip a CD with K3b It works, and lists Flac as a supported format. If applicable, add screenshots to help explain your problem. The fix from should still apply in some form? Manually adding flac to and libcdparanoia to works around the problem. also (maintainer for Plasma 5 K3b) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Please test


Project description A waveform viewer with a focus on a snappy usable interface, and extensibility. <!-- Describe the project a little: --Metadata homepage URL: https://surfer- source URL: license: eupl12 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I tried to package it myself however, the following derivation fails: Error: Similar issue: Looks like the real issue has been solved couple years ago. I should update the derivation accordingly.


Project description A .NET Core global tool to display and update outdated NuGet packages in a project Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Package name: halloy Latest released version: 2024.5 <!-- Search your package here: --- Current version on the unstable channel: 2024.3 Current version on the stable/release channel: 2023.5 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Package name: zombietrackergps Latest released version: 1.15 <!-- Search your package here: --- Current version on the unstable channel: 1.10 Current version on the stable/release channel: 1.10 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Steps to reproduce the behavior: Authy, stable or unstable channel No additional context, seems like the package of one of the dependencies was taken off snap for some reason Could not run for some reason... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It seems that Twilio have deprecated the desktop apps. . Looking on it seems that they have pulled the snap from Snapcraft. It also seems that the Flatpak has been removed. See and .
Well, i suppose there is nothing that can be done. Thanks for explaining the situation to me!
I'm not sure that issue is really resolved, as I think we need to remove the package from nixpkgs as its deprecated. I believe you are the package maintainer. Should it maybe be removed?
Thanks for the tag and explanation, I had read the announcement when it came out and the apps were still available on Snapcraft. It must have been pulled after a while. It's better to remove the package now. I'll do it sometime this week.


When installing latest Elixir with Erlang 20 via , several of these warnings are emitted through the build process: I'm installing through with (on Vultr FWIW). Though I believe on a new system may be enough to reproduce. The only way I've gotten the warnings to subside if by specifying . System: Nix version: Nixpkgs version: Sandboxing enabled:
/cc: (by request from )
I will look into this.
I see that you have dropped the override. Is this because of these are just harmless warnings? I've switched to the same nixpkgs and could not reproduce the warnings on Ubuntu: Output is here: I'll try to reproduce this on NixOS machine now.
I was able to reproduce this on NixOS machine:
Thanks


This link is invalid: It is used to download the build Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Project description <!-- Describe the project a little: --BlastEm is an open source, highly accurate emulator for the Genesis/Megadrive. Nightly release should be packaged as stable is five years out of date. Metadata homepage URL: source URL: license: GPLv3 platforms: unix Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


After a recent update, xonsh is no longer able to launch. Launch Xonsh should start without issue If applicable, add screenshots to help explain your problem. I've found a change of python env that reached recently (). Perhaps it is the change that breaks xonsh. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
May not be the same issue, but this doesn't work either:
That's a different issue. You should probably use instead. However, if you really need the full python env, unfortunately there's no way to use it outside the xonsh derivation for now. Maybe we should add it to .


On aarch64-darwin, while neovide does build and install successfully and I can launch it from the terminal, there is no app bundle that can be found in finder to launch neovide from there or pin it to the dock to launch from. Once opened the global menu calls it .neovide-unwrapped and the icon in the dock is a blank white page as a generic icon. I can only assume that once is fixed, that this will also be applicable to x86_64-darwin Steps to reproduce the behavior: neovide as either a system app in nix-darwin or a user app in home-manager on aarch64-darwin An app bundle name that will be linked into or depending on and usage I'd like to point out that the global menu title is .neovide-unwrapped to for sure indicate that this is the nix neovide and not the homebrew neovide ! ! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Following PR MacOS app information a few days ago: We can install the files with next release of neovide.


Run it. No error. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Workaround is to symlink your flake to /etc/nixos or to supply flake flag with path to your flake.
Supplying the flake with a flag works for me. Did not try the symlink.
Could you please be more specific? I don't understand what you mean.
Are you using flakes for your configuration?
Yes. I think I got it, the command to run is:
Just to be clear, how would you normally use here? I might have jumped the gun in changing the name of the issue, and maybe it's more like "nixos-rebuild: better error messages when missing and flakes both"
The point is that you don't need to search / know where the config is located if you're just listing generations
I always have to use the argument. And yes I agree with this. The current title, "nixos-rebuild: Don't search for config when using list-generations" is better IMO.
As a workaround until the PR lands, you can run to suppress the error.
Thank you, this served well to confirm my assumptions. And yes, exactly what I had in mind as the root cause.


It looks like shadowsocks service integration is not working at the moment, even with minimal configuration. systemd service doesn't load. Apply this nixos config It looks like nixos will generate ExecStart similar like so Running this will just get a help screen of ss-server (and same for systemd service, confirmed with journalctl) Contents of /nix/store/i74pqxw9wwicclbamqjw2l4w7l48rdpz- is Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This is caused by ss-libev's encryption method requiring a password but not set. Refined the assertion in fix pr.


Project description BrainFlow is a library intended to obtain, parse and analyze EEG, EMG, ECG and other kinds of data from biosensors. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Steps to reproduce the behavior: Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
there is now a captcha on the page at "" <img width="381" alt="image" src=""
Looks like it's the original website request captcha, I've submitted a PR to prompt it.
The captcha seems to have been removed.


Steps to reproduce the behavior: python3.12-django-4.2.11 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]:
Here is what I see on my side so far : You should wait until nose support the python3.12 interpreter.
This doesn't mention explicitly, but the issue only exists in currently (PR ). On Hydra e.g. These tests now regressed on *-linux, both pythons, django_4 only.
I was looking upstream but it may not be related to this issue then : still I'll mention it, apparently a fork for the nose lib is better maintained upstream and compatible with python3.12. There has been test failures reported as well on Python 3.11 upstream :
Fixed in


Package name: rnnoise Latest released version: 0.2 <!-- Search your package here: --- Current version on the unstable channel: 2021-01-22 Current version on the stable/release channel: 2021-01-22 <!-- 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 Note for maintainers: Please tag this issue in your PR. Tried building with but it got a missing file. There’s also warning about not using SSE3/AVX/AVX2, but Nix only supports the bottom of the barrel, common x86 instructions, but I usually compile this one out with some flags. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [^1] or offering a non-proprietary, non-US-corporate-controlled mirror for this free software project. I wish to delete this Microsoft account in the future, but I need more projects like this to support alternative methods to send patches & contribute.
The missing file is downloaded as part of the '' It looks like they a step to the build process.
Perhaps it can be fetched using fetchurl/fetchpatch?
You're correct. The relevant file is retrieved in the script . It fetches a single file from the URL , where the version is extracted from the file , currently set to . Hence, we can emulate the download script and execute something similar to:
Alternatively you could use instead of a separate model + . While we are at it, we should be using the main repository instead just Microsoft GitHub which is explicitly listed as a mirror, not the primary code forge. Something like Referencing both mirrors would be more resilient for when one of these platforms goes down.
Made a PR , but still having trouble designing a .


When I try opening the new version of albert (), it crashes and reports that no frontend plugin is found. Steps to reproduce the behavior: albert to 0.23.0 albert Albert opens normally. This issue exists under Wayland and X11. : : Also notifying the author of the last commit Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think I have relevant infos in my logs. I included the full log (including application restarts and the full stacktrace) as there are some unique messages on consecutive restarts. Note that I use systemd to run Albert. Beware wall of text :eyes: <details<summaryHardware</summary</details<details<summaryAlbert Details</summary</details<details<summaryLog</summary</details


Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
done in


Package name: calibre Latest released version: 7.9.0 Current version on the unstable channel: 7.8.0 Current version on the stable/release channel: 7.0.0 Notify maintainers https://calibre- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


XOrg crashes when certain applications are launched. More details here: Steps to reproduce the behavior: any of the IntelliJ IDEs. You may have to set anti aliasing to greyscale. Xorg will crash. Xorg doesn't crash. This is the bug: It looks like a security fix caused this regression. Ubuntu has already applied patches that fix this for Xorg and Xwayland: see this message from the above Ubuntu thread: NixOS should use the same patches until this is fixed upstream in XOrg. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Sounds like this will be addressed by this update:
xwayland too: looks like updating xorg and xwayland to their latest versions will do the trick then
xwayland was bumped to the latest version in PR


fails while compiling The same thing happens with Steps to reproduce the behavior: or: is successfully installed. Here is the output:
Fix in
Thanks On the same system that I encountered the error on, I checkout out the branch with your fix and then ran: The installation worked and is runnable. I'll be doing more testing later today/tomorrow.


Package name: emscripten Latest released version: 3.1.57 <!-- Search your package here: --- Current version on the unstable channel: 3.1.51 Current version on the stable/release channel: 3.1.47 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
tl;dr: 3.1.57 is not currently compatible with the version of llvm in tree (18.1.5). The latest compatible version with llvm 18.1.5 appears to be Emscripten 3.1.54. The emscripten nixpkg (3.1.51) currently uses an LLVM17 environment which needs be migrated to LLVM18. The configuration as it exists today doesn't work in some cases. (Godot4.3dev6 web template builds failed missing in , prompting finding this issue) Emscripten 3.1.51 seems to be compatible with the LLVM 18.1.5 currently in nixpkgs unstable. Emscripten 3.1.59 (current as of this comment) and 3.1.57 are not compatible with that version of LLVM (In my usage, ran into errors with and ). These flags were introduced in Emscripten 3.1.55 making the last compatible version against the current in-tree dependencies 3.1.54. <details<summaryThis override was able to successfully build the godot4.3dev6 web templates using Emscripten 3.1.54</summary<p</p</details


Project description LXGW WenKai TC is the Traditional Chinese Edition of LXGW WenKai, where the latter has already been packaged as . Metadata homepage URL: <https URL: ofl platforms: all Below is a working package build script I tested locally, which is largely based on 's script: (I commented out field.
If that snippet is working, could you turn it into a PR? It looks good enough for inclusion to me.


N/A No maintainers are defined, but was last to update it Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Package name: fluent-gtk-theme Latest released version: 2024-04-28 <!-- Search your package here: --- Current version on the unstable channel: 2023-06-20 Current version on the stable/release channel: 2023-06-20 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


uses and to convert PCI device ID to human-readable product name. Currently their paths are hard coded as and . It won't work with NixOS of course. I found some packages that have similar issues. They are patched directly before building: Fastfetch needs to be patched too. Steps to reproduce the behavior: N/A Fastfetch can properly find and N/A Reference: Fastfetch provided cmake config option  for but not for . I can add one if needed. N/A Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi thanks for the detailed issue report! This should be pretty straightforward to fix. If you could add a config option for the path that would be great! Many thanks.
.
was released with support
Many thanks! Much appreciated.


On nixpkgs commit , running Tailscale with Tailscale SSH connected, then trying to connect to it, results in an error: . Steps to reproduce the behavior: the tailscale node service with (in my case, using a systemd service). to use Tailscale SSH to access the node (e.g. ). that no shell is opened and the connection is closed immediately. A shell opens (if the default SSH behavior is unchanged). This appears to the result of The underlying patch sets the systemd hardening option , along with an allowlist of devices. This prevents from accessing , which is needed to open a PTY for the shell. Please run and paste the result.


Affects our 3.12.17, 3.13.10 and 3.14.1.
Only 3.13 is vulnerable now, but I don't know what to do about it. Personally I'd drop it, but it's also possible to follow the Ubuntu-maintained branch if people care for it, or just leave it as it is...
Removing 3.13 is fine - we were going to initially keep it because grsecurity was going to use it, but it looks like they've chosen the 3.14 kernel instead.
I have no idea if anyone else can depend on it, but reverting will be easy.
After finishing build tests locally, I'll push to release and close this.
Well, doesn't build on release (it does on master), but it's probably not worth debugging. The rest builds fine.


Updating my falke to latest nixpkgs unstable gives an error that vault is non-free. But my package doesn't use or need vault. My package at has: This gives the error: If I comment out the it works. Steps to reproduce the behavior: to use nixpkgs-unstable instead of nixpkgs 23.11 Should build without errors. As above. ` Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
helm-secrets depends on vault
What happened to vault? It use to be open source I thought. Did the license change?
Does helm-secrets really depend on vault? From the it says: Which seems to indicate that it should be able to use any secret manager, not just vault.
the vault license change, which sparked quite the outrage. you ask a question and follow with the answer, that's both rare and impressive ^^'' You can see it here: I suggest you follow the recommendation and accept the new license for vault. If you dont need it, you can remove support for it as well from helm-secrets (but will require some nix skills though you can search the web for plenty of examples)
How about switching the dependency from vault to OpenBAO - would that be possible?
Heh, I didn't realize LF forked Vault too. :popcorn: It's certainly possible, but might have unintended side effects for Nix users. (I realize how annoying that might sound, given your recent experience.) By default, helm-secrets supports and . After a quick glance, it looks like both sops and vals use the Vault Go library, so maybe we don't even need at runtime anyway... I wonder if sops and vals will have to alter their licenses... Edit: It seems the is still .
I've just tried a modified helm-secrets derivation, removing all references to , against a repo that uses helm-secrets (with AWS KMS backend) and it worked fine. I then switched the config to point use a Vault backend, and that also worked. Note that I used to get a token, but assuming exists or the env var is set somehow, it seems doesn't need a binary at runtime at all. So, I suggest we drop the dependency.
might you be able to test It Works on my Machine, and I'm fairly confident, but I'd love some additional verification.
It seems to work OK on my system, so far. Don't have a good test case for vault though. Will think about additional ways to test this.


After installation notation shell completion is not available. Steps to reproduce the behavior: notation completion Shell completion should be installed. N/A N/A <!-- 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]:


After installation kcl-cli shell completion is not available. Steps to reproduce the behavior: kcl-cli completion Shell completion should be installed. N/A N/A <!-- 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]:


Steps to reproduce the behavior: unicode-emoji-15.0 :frowning_face: Here's an example log from my system building with substitutes disabled ( being a dependency of ) Note that the logs from building don't contain anything else. The fetched URL () from the Unicode website seems to be restricted in favor of the 15.1 version, which breaks building. A report has already been sent to Unicode, Inc via on their website. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
As a bit of a context: this error only occurs on forced local rebuilds, eg. because of disabled substition!


Package name: feishin Latest released version: 0.7.1 <!-- Search your package here: --- Current version on the unstable channel: 0.6.1 Current version on the stable/release channel: 0.5.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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for reporting this, just noticed I hadn't subscribed to release notifications. Shouldn't miss any from now on :) Fixed by (awaiting review).


Gives this error: , yet installing doesn't fix the problem. Steps to reproduce the behavior: Meteo That the Maps section works. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have this exact issue. Hoping for some clarity.
should be here:


Package name: tracker-miners Latest released version: 3.7.3 <!-- Search your package here: --- Current version on the unstable channel: 3.7.2 Current version on the stable/release channel: 3.6.2 <!-- 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. -- Tracker was updated in , however tracker-miners wasn't. It currently suffers from this bug: (and generates a lot of failures on a running gnome system). It was fixed in 3.7.3. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
PRs are welcomed.


Package name:material-symbols Latest released version: 2024.05.04 <!-- Search your package here: --- Current version on the unstable channel: 2023.11.17 Current version on the stable/release channel: 2023.11.17 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Are there any relevant changes in the font definition?
there should be some new symbols or some symbols' code changed.
please do replace OLDVERSION and NEWVERSION in the issue title with the actual version names. In this case this would be like:


There is an option to save the configuration state that does not work because it tries to run which is not located at this path in NixOS the GUI to File -Save Configuration filename and click save It should save a file to the filesystem with the current configuration state.


Project description <!-- Describe the project a little: --Metadata homepage URL: https://mqtt- source URL: license: creative commons platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
AppImage works fine with appimage-run. There is also a deb and snap package
I use this one
That package looks great. Maybe even worth to try to contribute to nixpkgs.
Unfortunately I don't think the appImage version would be accepted since the source code is available with a build manual so imho a PR to nixpkgs would need to be with a source build. I might look into it
I maybe have a potentially working version. I'll try to find some macs to test out the Darwin versions and if that's gonna be okay I'll then submit a PR
Great news, I can test on darwin.


System: 18.03pre118631. (Impala) Nix version: nix-env (Nix) 1.11.15 Nixpkgs version: "18.03pre118631." Sandboxing enabled: build-use-sandbox = true
See, I thought I had fixed it somewhere but cannot find it ATM.


Project description "A general purpose HTTP reverse proxy and forwarding tool." Metadata homepage URL: source URL: license: agpl-3.0 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


hydra went from to as per on a . Steps to reproduce the behavior: to nvimpager <details<summarytest failing on this update:</summary</details
To my knowledge the actual functionality of nvimpager is not affected but the default colorscheme in neovim changed and my test depend on it. So a quickfix might be if that is acceptable.
this will be fixed by .
The neovim update has been reverted in . Closing.


When enabling freshrss and rebuilding, no freshrss systemd service is started. Steps to reproduce the behavior: (as well other requirements for minimal config) (with , for me) The only freshrss units are and . to in browser. Unable to connect. A service with (or something?) is created and runs automatically. The http server is accessible from a browser. I initially tried running in a container, but running on the host OS had the same result Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Freshrss doesn't run as a systemd service. It runs under php-fpm. The associated systemd service is . This is then exposed via nginx. I believe the default nginx configuration will expose freshrss on port 80, so http://localhost may work for your current configuration. The used by nginx for freshrss is . My guess is you'll need to configure it. If you want to access freshrss via "http://localhost:8080" you could use a config like:
Sorry I never responded to this! This worked, thank you.
i guess we can close this then? please report back if i am wrong.
I do agree with qyriad that this could be explicitly documented better, but I don't have any further issue to specifically track
any specific location where you want this documented? where would you look something like this up?
I would probably put in the description of the option.


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]:


Steps to reproduce the behavior: <details<summaryBuild log</summary</detailsOut of the few packages I've tried installing using , all of them failed with "detected dubious ownership in repository". It builds successfully if I use the commit that introduced : Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Git bisect says is the first bad commit.
not sure if the error is intentional, but the changes in that version are explained in
Okay, it seems intentional: So we have to change the julia builder accordingly, since anything in is presumably owned by , which is not the user used in the build. Not sure if that'd require an upstream fix, I'm not familiar with julia.
PR here:


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


Package name: Latest released version: 46.0 <!-- Search your package here: --- Current version on the unstable channel: 46.0 Current version on the stable/release channel: 46.0 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: Fixes very annoying bug for users with nvidia dGPU notebooks on gnome using external displays. Reports of the Bug:


Package name: python312 Latest released version: 3.12.4 <!-- Search your package here: --- Current version on the unstable channel: 3.12.3 Current version on the stable/release channel: 3.12.3 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Package name: monado Latest released version: 2024-06-07 (24.0.0) <!-- Search your package here: --- Current version on the unstable channel: 2024-01-02 Current version on the stable/release channel: 2024-01-02 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
PR at
Thank you!


Hostname being unset (resulting in ) causes issues for logging. Specifically, with journald, the same boot (identified by (see systemd.journal-fields(7)) has both and with the switch happening at the rootfs pivot of the boot. This makes filtering by hostname difficult. Even more so, when doing log aggregation from multiple machines, filtering by hostname will yield incomplete results. Instead one must build a pipeline that makes looks up all bootids of a hostname and querying all those instead. Steps to reproduce the behavior: behavior described above journal contains the the same as long as it not changed by the user. Hostname should be generally available, even during early boot(?). N/A I'm filing this as a bug instead of a pull request because I'm not sure if there are any unintended consequences of doing this. Aside from the usual Hoping for your input here. There's a reference in the docs giving an example of setting the hostname by hand: (from ). Why this was chosen as an example and not just standard behavior, I don't know. CC/FYI , who the example/was tagged in the commit. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Me neither. I don't see a reason not to have that file. may be more knowledgeable, but I'd say go for it. Also systemd-based initrd is somewhat young, so I feel like the probability for spacebar heating is somewhat low.
I think the main reason was to have the initrds be more substitutable between different hosts as this would be a difference between all of them (when having different systems with only different hostnames). I'm not sure how well adding the hostname file would work. My memory is a bit fuzzy on the details (I did a lot of other projects at that time) but I think an issue was that when journald starts up, it imports the kernel logs BEFORE the hostname was set (causing the pre-systemd lines to be mapped to localhost). An alternative implementation that would probably solve that as well (if it's still/even an issue) would be adding the kernel parameter rather than adding the file to the initrd.
If I read the code correctly, journald reads the hostname from /proc: -: So the hostname needs to be set system-wide before journald starts up. Systemd does this in --: So on bare metal we can either set on the kernel cmdline or it seems.
It seems this is the best choice then, but maybe also as that's more standard and picked up even earlier in the boot process. Unless you're running an old kernel though. () We could just set both.
I'll run an experiment to see if even solves my problem or one must use . On that note, I also realized there's an equivalent (or slightly harder?) problem with as well :-.
(So, setting /etc/hostname in the initrd works. Every message from that boot has the correct hostname.) I was also thinking about your folks' usecase some more, and was wondering about one thing ... how are you approaching the UKI/secureboot? None of the mentioned approaches work for that, right?
Why not? Most people use for that which signs whatever UKI you have locally with a local key
Because changing files or the kernel cmdline will cause different images to be created? Your design shares a single one among multiple hosts, no?
Yes, that's the downside. Although, the cmdline is only baked into the UKI which is not in the nix store anyway. This way we could substitute the initrd and have differing hostnames. I must mention, however, that I personally don't care about the substitutability of the initrd. My main focus was to keep the state as it was before, but if people decide it's time to change that, I'm not opposed to that ;)


The service will ask docker to mount the binary which is not provided by the Nvidia driver v470. Using NixOS 24.05 with nixpkgs . Steps to reproduce the behavior: should not be mounted when the binary is missing. <img width="1234" alt="image" src=""<img width="854" alt="image" src="" Edited: a workaround Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for the report You can also set in the meantime. I'll open a PR as soon as possible.


Package name: fluent-gtk-theme Latest released version: 2024-06-12 <!-- Search your package here: --- Current version on the unstable channel: 2024-04-28 Current version on the stable/release channel: 2024-04-28 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Commit seems to have broken rexml. How to reproduce the behavior: It should work as it did in commit . It looks like this is related to , but currently fails on master. system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Shoot! Looks like it's already fixed upstream: Looking to submit another upgrade PR. I just want to check if there would have been a way to catch this, so that it doesn't happen again.
A test running would've been enough in this case. Do you want me to look into creating one, or to help you with that?
I confirmed that the upgrade to 3.3.0 fixes github-pages, but I wanted to make sure it doesn't break any other gems. It looks like kramdown-rfc2629 is the only one causing issues. kramdown-rfc2629 was fixed by pinning the old version of rexml as a temporary solution for the issue. I'll pin the old version of kramdown-rfc2629 (the only difference is the rexml pin) and submit a PR upstream to remove the pin (now that rexml has been fixed).
Should fix it.
it has not fixed it for me, using selenium-webdriver gem. Details at Should we be opening a new issue for it?
Nevermind, I think this is the entire issue,


Steps to reproduce the behavior: This seems to have been caused by although I'm not familiar with the package, so I could be wrong. It is causing to fail as a result. I don't quite understand the organization of the structure, so I'm not sure who the appropriate maintainer is. As a fallback, and were involved in the above linked PR, so they may be of help here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
sorry for the breakage, i opened to fix this
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Had the same issue. But I think it's fixed in PR as mentioned You can track the progress of the PR , apparently it hasn't been merged into nixpkgs-unstable yet.


Steps to reproduce the behavior: floorp Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, Please elaborate - there does not seem to be any actual build failure here. What's the actual error? Are you sure your build machine has enough resources? A browser build is pretty demanding and can take even multiple hours on low-to-mid-end machines. Can you please also post the complete derivation log, as obtained using ?
I have the same problem (with floorp and floorp-unwrapped). Here’s the error: ! That feature was removed in February, so either update the qcms crate to 0.3 or downgrade the rust compiler version (1.76 could work).
is the log in the link not enough ?
Oh, I see, Github just truncated the file in the UI. That's what you get from hosting projects on crappy, proprietary software .. Pointing out the exact error too from the get-go would have been helpful in any case. Anyway - seems it broke with a recent rustc upgrade in nixpkgs. This is already fixed with 11.14.1, as it updates the firefox base source. See .
Okay, I will host my opengist instance for the next time ;) Thanks for your prompt response, waiting for your pr to be merged.
Any ETA on the PR merge?
Floorp is now in version 11.14.1 on unstable.


Project description Sysmenu is a simple and efficient application launcher written in gtkmm4 Metadata homepage URL: source URL: license: wtfpl platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Package name: bcachefs-tools Latest released version: 1.9.1 <!-- Search your package here: --- Current version on the unstable channel: 1.7.0-unstable-2024-05-09 Current version on the stable/release channel: 1.7.0-unstable-2024-05-09 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


The gitlab  script depends on , which was removed by in . Steps to reproduce the behavior: The update scripts succeeds. (myself) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Also looks like nix-update could be used here.
Ok. looks like switching to nix-update would require some other major refactoring because the writes out some json file out. But here is a simpler approach:


Mealie was updated from 1.7.0 to 1.9.0, and it's now failing to launch, even though I'm using the exact same configuration. It actually seems that just enabling Mealie, with no configuration isn't working. What's weird is that the error is referring to , which is a sops-nix directory. I even rebooted, but it's still getting that particular error Use the following configuration: Mealie successfully starts. Here's my original Nix configuration: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Tested on VM, works fine with the base configuration. The problem comes from the part of your configuration, it seams that you need the setup the user to get access to the directory. I'm not familiar with , is there a group you could add the user to so that it can access the directory ?
You can allow a specific user/group access to the decrypted sops secret file using the options. See this example in my config:
It still doesn't work after doing that. I wonder if it's some state getting left over that screws something up, because it's weird it would still not work after removing everything but . I deleted though, and it's still happening, and it also still works if I role back to 1.7.0. Although, I am using PostgreSQL so maybe it's something in there? Note that it's happening in . Here's my updated Nix file:
The issue seems to have something to do with this mealie commit: Mealie 1.9.0 works when the commit is reverted:
Somebody opened a PR to get this fixed upstream:
I've also opened , which prevents mealie from exploding when it encounters a secrets directory that it doesn't have permission to read. I've verified that it fixes this issue in my own NixOS deployment.
has been merged and should be out in the next release. In the meantime, we can pull in to the currently available v1.11.0 to fix the bug. I'll create a PR for this.
I'm still experiencing this issue when Mealie first starts after boot, but it goes away after restarting the service. I'm guessing it's because sops-nix hasn't setup the directory yet? Should I open a new issue?
That warning message seems to be intentional. The patch always prints a warning before the directory is ignored.


Steps to reproduce the behavior: gerbolyze Test failures: and Upstream issue . While upstream is working on a fix, the issue can be worked around using the shell (run ) from the following : Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Application crashes with when scrolling back chat to images/videos. I'm not really sure what exactly triggers a crash, but the project's README says that when viewing media. Steps to reproduce the behavior: . a chat room with images/videos. a crash No crash. Nope. I've also tried overriding the package locally by adding gst plugins to , and when it didn't work, to like so: but that didn't help. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


notes that this is a fixme.
cc
I use Nix as a package manager in Ubuntu, so I can't really test this. In Ubuntu, drops the file in , and the user is expected to change on their own.
I think the best approach would be to generate an script that returns the path to . Then it would work in the cases where it's installed in a random profile too. As long as it's on the PATH you can use
PR ^


Steps to reproduce the behavior: unstable defined, enable the ollama service with pkg overridden to point at unstable: without show-trace: with --show-trace: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi! Can you confirm your nixpkgs revision has this change incorporated and you're not overriding the package manually?


Project description Session persistence tool: "Think tmux, then aim... lower" Metadata homepage URL: source URL: (Cargo Rust) license: Apache-2.0 platforms: linux note: primarily useful for nixos servers, not workstations!


shell completion does not work with fastfetch fastfatch fish and shell completion works ! Add any other context about the problem here. system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Steps to reproduce the behavior: spotdl/asciinema/binwalk/gpodder/autotiling/... Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I am getting the same issue from binwalk after updating flake inputs: the same error also occurs when trying to install the package xsser or pwndbg. So it seems to affect a lot of packages using python.
Also having this, I do not have Spotdl installed however. I think it might be a underlying issue with some dependency
Got the same error with gpodder
Same with blender It seems multiple builds are failing here
I also had issue with Blender-hip but different error I am not sure if it is related or not it was issue with OpenUSD which is NVIDIAs weird model format or something(?)
getting the same issue for & asciinema logs: autotiling/i3ipc
Same issue for and .
I fixed in . The PR just replaces the package (unsupported in python 3.12) with () .
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Same error with plex-mpv-shim Created for plex-mpv-shim EDIT: appears to be fixed on master already
seems to be the latest working commit (one before )
Same with plasma-hud and gnuradio for library thrift.
upd: also yep, and is also have this issue hi! same think, this time with , im not a big expert on flake and nix, but maybe there some simple fix like to pin old python version or something?
Binwalk is also having this issue:
Same issue with
see and fixed by
the issue is still there. Here the trace:
My issue will be fixed by
I have issue during nix-darwin update
Issue persist for nix-darwin update using flakes
Same issue for pony-0.7.17 (pgadmin)
Please open separate issues for all packages that haven't been fixed on master yet. This issue was about spotdl. Btw, nose will work on Python 3.12 once or is merged.


Steps to reproduce the behavior: build .#hplip Looks like more fallout from Python 3.12. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


Package name: dbeaver-bin Latest released version: 24.1.2 <!-- Search your package here: --- Current version on the unstable channel: 24.1.1 Current version on the stable/release channel: 24.0.5 <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Steps to reproduce the behavior: floorp or floorp-unwrapped The important bit at the end of the log: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Yep, got the same.
It probably needs something like For now, I've just this overlay:
Yep, seems like the cause/fix. I'll send the update to v11.15.0 soon anyway and include this fix as necessary. The package in the binary cache is fine though, so if you just pull it from there instead of rebuilding this massive thing you'd be just fine too.


I'm running an issue with overriding the rust toolchain since , I pass the following to crate2nix: to set the toolchain when building something, since I don't want to override the toolchain globally. But after this PR it doesn't work because it uses the toolchain in instead of the one I'm passing in. Now I don't really know how to override the rust toolchain to the version I want. is a nightly version I got from This problem is caused by this optimization: Another issue is that the attribute is missing in rust-overlay:
I'm having this issue as well. I've overridden my input to my flake to as a workaround for now.
Hi, sorry for the delay, I'm back home now from "holiday". Can any of you give me a minimal flake that reproduces the issue so I can experiment and find the best way to fix it?
I'm also hitting this. I don't have a minimal flake but I can at least offer the error message which seems to be missing from the OP.
Let me know if this fixes it.
unfortunately it does not, because it still defaults to for the rustc compiler. I've created a reproduction here: As you can see in I'm overriding rustc and cargo to the specific nightly version I want, but when I run I get the following output: This is the rustc version that's current in nixpkgs, not the nightly I specified. Thanks a lot for looking into this
One problem with your reproducer is that it uses the for which takes an arg called not . I think that still wouldn't have solved it. I made some changes in the PR that would allow passing a custom toolchain via the but also using . I did some refactoring to get rid of the and variables.


gamescope 3.14.23 seems to be packaged incorrectly, looks like this automatic upgrade missed some new runtime dependency, as the command now fails when run. Steps to reproduce the behavior: A window is displayed ! I am running on KDE Plasma 6.1, but this issue seems to happen on a standalone session as well. I'm also running Nvidia hardware, RTX 4090, on driver 555.58.02 Written logs: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Did a quick test to tryout the previous gamescope version, 3.14.22: Seems like the issue was definitely introduced in 3.14.23. !
Are you running it from nix-shell or something? should be in the package and thus on your PATH.
No, it's part of my system configuration flake. Sharing the relevant host file for context, is the only part of my configuration that is related to gamescope (): My configuration lives here: Some changes I haven't pushed yet. You can see by my that 'unstable' referes to nixos-unstable channel, and stable to the latest stable release, 24.05.
At the very least you can't mix unstable gamescope and stable WSI.
Thank you for pointing that out, I changed it to both be on "unstable" but the issue persists.
It looks to me like "gamescoperreaper" is a new binary that Valve recently with 3.14.23 that gamescope calls at some point. I was looking into their releases . Not a CPP developer so I am making a some assumptions about the nature of gamescopereaper and the layout of their project. Perhaps gamescopereaper needs to be packaged as part of the gamescope derivation? It doesn't look like it does that currently.
The binary is there in our gamescope package, though?
Agh, seems like adding though the was not enough to add into the path. I solved the issue by adding the package explicitly inside of .
I think the issue is with the module -- looks like it doesn't actually add the gamescope package into , but instead a wrapper.
I can confirm that adding the package through the gamescope module makes gamescope not work. Adding it through other means such as does work.
Ok, so possible solutions: 1 - simple but less optimal: add a symlink below this line: 2 - complex but more Nix-friendly: find the exec portion in C code and patch it to find the executable in $out/bin/ 3 - alternative similar to (1): add $out/bin to wrapper's PATH (using makeWrapper argument) Good opportunity to open a PR with any of these solutions, tag the module and package's maintainers, and make the requested changes (which might be even a change of which strategy). Don't worry, the worst thing that could happen is your PR being closed to favorite a committer's PR, it's still seen as a good contribution (and good opportunity to learn).
Opened to attempt to resolve.


Ansel installs well, and can be launch from console with … but it does not appear in Gnome’s application menu, nor it cannot be find in Gnome launcher search Steps to reproduce the behavior: to from channel 24.05 or from unstable to launch it or to find it in applications menu Like every other application (and Darktable), I expect to find Ansel in the application menu, launcher search, and so on
I don't know anything about gnome, but there's definitely a desktop file in the correct spot: also, is a bot, FYI Probably try rebooting or something.
The desktop file is broken: Sounds like the upstream build system is broken – see
Good catch, thanks. I've sent a PR


I believe converted the following generated line of Bash: into: , so it's , and is the empty string; but when escaped, it became . The result is that the passthru does not generate a lockfile. After I manually change the two into in the definitions of and , I successfully start getting a NuGet restore. Failing passthru: Add any other context about the problem here. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hm, that is weird. Note that cannot be null.
This should be (plural). Introduced in .
I even checked the implementation of and discovered that it's secretly a function rather than as documented, and didn't make the connection. I clearly need to go to sleep.


Package name: wasm-pack Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.1 Current version on the stable/release channel: 0.12.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. I just tried to make a PR with the change, but I got when I tried to build (while compiling ), and used all of my RAM while running (it did not finish). I'm using a x86-64 machine with Debian.
I encountered that error too. After reading I tried this: That resulted in a new error log. I don't know what to do but I thought I'll leave it here in the case that I could be useful to someone else


Package name: Latest released version: 1.4.3 Current version on the unstable channel: 1.4.2-1-unstable-2024-07-10 Current version on the stable/release channel: none 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


doesn't seem to work as a module Steps to reproduce the behavior: livebook service any env variables or use environment file with any variables first of all, its systemd unit does not appear to start by default. so i did and but it doesn't work, i can't access it either by IP or by domain, which is set up in my nginx configuration as a reverse proxy. some strange things happen while the unit is active [1st screenshot]. also there's nothing in the journal except info messages about the unit itself as i see it, livebook fails to start, but the service is active because something is going on with inside this wrapper script i tried to make it work several different ways: from using option instead of my environment file to writing my very own systemd unit in NixOS configuration file, also using home-manager like so: but that doesn't work too. surely i tried starting livebook manually - and it works as expected [2nd screenshot] module/service works and is accessible systemd livebook unit works and is accessible |
---------------| NixOS 24.05.3214. (Uakari) x86_64 running on a VPS cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thank you for reporting this issue. I am ashamed to admit that I have actually known about this for a while now, without doing anything about it. Now that someone else is having problems with the service, I'll prioritize getting something done soon. I'm not actually sure what's going wrong, but it seems like the service hangs in the command. As far as I remember it ends up using 100% cpu and just loop forever. I'll try to take a look at it later this week.
Perhaps you have encountered this issue as well?
I've seen this before and I think it was because livebook was trying to generate a in some weird way. This is my current configuration which works: Could you try manually setting a in your service setup, please?
a screenshot from filtering cpu usage ! not so much is used i've tried setting up a cookie and you can see it works - :pleading_face: thanks!!!! ~<
The issue seems to have been described and debugged here: The solution is to set in the systemd service configuration. I'll mint a PR.


Switcheroo fails with the error in the title. This does not happen in the Flatpak version (tested). (the formats might not matter, but I've specified them just in case) Steps to reproduce the behavior: a PNG file in Switcheroo to a JPEG file. the output filename. should happen. The image should convert without any errors. ! 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]:
Oops, I had in my path when I originally packaged and tested this. I have it as a dependency in and tested it with this time. Thank you for trying the flatpak and reporting it here first instead of upstream :slightlysmilingface:


doesn't work with channel configuration. Output: Only with channels. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
That should be enough to fix it, I think?
Did you try it and did it work? If so, feel free to shoot a PR with that patch.
works for me. I didn't check any other flag combinations though. But I guess working sometimes is better than working never.
It'd be great if you could create a PR then :)


A clear and concise description of what the bug is. Steps to reproduce the behavior: lack of directory with executables In contrast this command works as expected: Create directory with executables to invoke Guake. Observe that nixpkgs 24.05 has and in the "Programs provided" section. <img width="989" alt="image" src=""And unstable does not despite both claiming to have version 3.10 of Guake: <img width="1201" alt="image" src=""And both branches provide the same package definition. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Seems like the cause is the below. Oddly the command fails but the build doesn't.


Alpaca does not use system theme configuration. (probably has something to do with flatpak) Affected: GTK4 theme GTK4 polarity Cursor theme Steps to reproduce the behavior: customized NixOS system, example: up and run nixpkgs#alpaca on nixos-unstable: App follows system theme settings: GTK4 Theme GTK4 Polarity Cursor theme ! <!-- 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 works for me, with . Maybe there's something to do with your theme? (Is that some simple libadwaita stylesheets?) Also try setting .
didn't help, I will provide my gtk settings files. (they are symlinks to /nix/store btw) the theme is generated by stylix but under the hood it uses In any other situation I would assume it's a problem with my theme but this is the first time this happened to me on NixOS and I use a lot of gtk apps.
Yes, I've tried with , and it behaves the same. But there are probably other applications that behave similarly, because I set this environment variable a long time ago for similar reasons. I will try to read its source code later. (this may also be caused by me setting XDG paths)


Package name: matrix-synapse Latest released version: v1.112.0 <!-- Search your package here: --- Current version on the unstable channel: 1.111.0 Current version on the stable/release channel: 1.111.0 <!-- 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 Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
They released 1.112.0 very quickly after 1.111.1, so I changed the issue.


Steps to reproduce the behavior: mysql-workbench-8.0.38 Might be related to or Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Steps to reproduce the behavior: ncdns.goModules with or 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]:
The goModules derivation can't be built since go 1.17, see I don't think I can fix it.


Running the package fails, apparently because it uses as input instead of as would be required to run:


Project description Microsoft Azure Command-Line Tools Storage-preview Extension Metadata homepage URL: source URL: license: mit platforms: unix, linux, windows This package is distinct from the package that is already in 24.05 and unstable. It enables azcopy utility in the azure-cli, which is useful for interacting with large storage accounts in Azure.
Code for extension
please give a try and leave some feedback. :)


Looks like CHADtree was updated recently, and it needs a new . was to in a week ago. Steps to reproduce the behavior: CHADtree to open the tree view Should work. :) (Skipping this, since I'm going to push a patch myself.) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


When installing the package and rebooting the desktop takes longer to load then usual and then only displays a black screen even without selecting the whitesur theme. Opening applications e.g. via shortcuts still works. I am new to nix so please wirte if further information is needed. Steps to reproduce the behavior: whitesur-kde package in the your nix configuration Desktop works as expected ! My current configuration: <details</summary</details<details</summary</details<details</summary</details<details</summary</detailsjournctl log: <details<summaryjournalctl</summary</details<!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
can you review , please?


Package name: qrtool Latest released version: 0.11.4 <!-- Search your package here: --- Current version on the unstable channel: 0.11.4 Current version on the stable/release channel: 0.10.10 <!-- 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. -- qrtool 0.11.4 was , and was updated in , but now (homepage), (repo) and even (owner) become 404 Not Found. I have no idea what have happened… Besides, still works. Update Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Sad! I'm camping for the next week... but unless the package and author reappears, we'll need to delete it, sadly.
Could we wait for one or two weeks? It looks like that is fine, but GitHub somehow locks the account.
Yes, I received an email and will update the source to later today.
I've opened to resolve this issue.
Hi, The flag has been removed from my account a few hours ago, so this change can be reverted.


crackmapexec fails to run on the unstable branch. Full backtrace : Steps to reproduce the behavior: Should be marked as broken for python 3.12 and above due to not being maintained anymore, it should be recommended to use the maintained fork . If applicable, add screenshots to help explain your problem. I may PR a proper fix later if I find time to do so <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I don't know if removal was the best choice for this tool but maybe has all the features that had so it's alright. It's just that I'm not aware if there are any bugs that are not in that are in but I understand why removal makes sense since later we'll move onto later version of Python such as 3.13 and further more
As is a fork, I guess that the feature set is comparable or even bigger in the meantime. is still available for 24.05 and could still be used after 24.11 with some magic.
I ran into this issue where didn't have it, it is just a minor issue so it's alright on my side, but not sure if there will be any more issues I'll ran into later :


After that upgraded openssh to 9.8p1, variant is broken on M1 darwin. Run: it results in the following error during build: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Adding to fixes the issue for me, I'm now trying to figure out why it only shows up on darwin-aarch64.
Seems that 9.7p1-9.8p1 change removed the include directive: -- so it's not clear to me why this succeeds on linux/FreeBSD and fails on darwin.
I'm now trying to fix this upstream, in freebsd ports, where we pull hpn patches from.


All expressions in nixpkgs are supposed to be MIT licensed, but is licensed under GPL-3.0. as an externally developed project under different licensing terms that we use for nixpkgs. It was merged into nixpgks in without the license being changed to MIT or a compatible license. Every package using is using improperly licensed expressions, which at the time of writing looks to be a bit more than 25 packages. I have two proposed solutions, neither of which are particularly appealing: -license under MIT This would require assembling relicensing signatures from all existing yarn2nix authors which include both contributors when it was in nix-community & in nixpkgs. It's gonna take some time and keep us in license non-compliance in the mean time. , migrate packages to something else The newly looks like a good contender as pointed out by in chat. CCing authors and other relevant parties Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Just to repeat what I said on Matrix, if we can’t figure out something better in a few days I will open a relicensing issue and start the work of pinging all the contributors. Reimplementing it sounds nice, but I suspect it would take quite a while given the speed at which Nixpkgs language ecosystems tend to move.
yarn2nix can be easily misused and trigger IFD. I think too that in the long run we should replace it. Maybe yarnBuildHook/yarnConfigHook from are already enough and the package can easily be migrated?
(Nixpkgs potentially actually being GPLv3 is very much a bug IMO.) Migration is all well and good, but we probably ought to try to relicense anyway: we can’t change old revisions of Nixpkgs and it’s not good for multiple years of Nixpkgs history to be under unclear licensing conditions.
I guess re-licensing is the better way for now? We can ping all the contributors, from a glance I read most of the names before.
Yes, I think we should probably at least try. I will open a new GitHub issue for it today so that we can discuss here without it getting bogged down in rote responses.
Okay, here we go I guess:
Oof, thank you for trying to clean up that mess. I just got the notification from the tracking issue and I feel that a big portion of any blame should go towards my direction because of the introduction in , rather than While I (try to) put a lot more thought into licenses today, it didn't cross my mind back then that vendoring with the included license could have such implications.
No worries – thanks for trying to improve the Node packaging situation in Nixpkgs and for your quick reply to the ping! This is an institutional failure IMO, and I think that it would have been caught before merge these days.
seems still active. It might be worth posting the same as on Discourse if you want people's replies to be public (unlike with email).


Package name: kodi Latest released version: 21.1 Current version on the unstable channel: 21.0 Current version on the stable/release channel: 21.0 Notify maintainers Release: Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
thanks for the ping! i am on it in the next day or two


Steps to reproduce the behavior: Attempt to build vmware-workstation from the unstable branch using the following command: sudo nixos-rebuild switch --flake ~/nixos#framework --show-trace Observe the build failure with the following error related to the --docdir option in the configure flags. Build log Running phase: updateAutotoolsGnuConfigScriptsPhase Updating Autotools / GNU config script to a newer upstream version: Updating Autotools / GNU config script to a newer upstream version: Running phase: configurePhase fixing libtool script patching script interpreter paths in ./configure ./configure: interpreter directive changed from "#! /bin/sh" to "/nix/store/4bj2kxdm1462fzcc2i2s4dn33g2angcc-bash-5.2p32/bin/sh" configure flags: --disable-static --prefix=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3 --bindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/bin --sbindir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/sbin --includedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --oldincludedir=/nix/store/f8yb3rhalwdpaig8lwxd4plgbqn8vagk-gdbm-1.8.3-dev/include --mandir=/nix/store/64jmdcjmdl94l4hbadwqsz7j8qg16dwb-gdbm-1.8.3-man/share/man --infodir=/nix/store/vs7bglvjl3pxp2ffc98v5w7xlinn0q5j-gdbm-1.8.3-info/share/info --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm --libdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/lib --libexecdir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/libexec --localedir=/nix/store/6gzwn3dm5qzbvj5009ind2ihvi84csi2-gdbm-1.8.3-lib/share/locale --enable-libgdbm-compat configure: error: unrecognized option: --docdir=/nix/store/9lclanzcvqmx0jc15i06125phchhsbsp-gdbm-1.8.3/share/doc/gdbm Try `./configure --help' for more information. Additional context I tried building the package on NixOS 24.05 with the following command, and the build succeeded without any issues: Notify maintainers cc Metadata [user nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Please update the issue's title with the actual package name ()
do we really need specific gdbm version during the build? or as a buildInputs?
I removed the override from and I can build and run vmware just fine. Could you just update the dependency version to 1.24 and remove the install override?
How can I do it myself? Download and edit the nixpkg and edit it?
Sorry, I didn't mean "you" as in you specifically, but more generally as a third person pronoun. I don't know how either, never contributed to nixpkgs before . I meant for the question to be at nixpkgs contributors to know if what I proposed makes sense. EDIT: Oh, might have misunderstood you. If you want to do the same thing I did then yes, get a local clone of nixpkgs, edit the file and point your system nixpkgs to the local clone. Here's the patch that worked for me: <details<summaryClick to show patch </summary</detailsNote that it doesn't pin the version of gdbm, it will always use the latest version from nixpkgs which may cause with future versions. I'm assuming there was a reason the original was pinned to 1.8.3.
Thanks it's very informative!


system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Steps to reproduce the behavior: X 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]:
Awesome. Now I have malware with 200M+ size and a libcef within.
Interesting you actually have a fsverity-enabled build directory, so this is probably an upstream issue that nobody has run into while running the tests. Specifically it looks like this line is detecting something is not behaving as it should: I recommended that you open this issue upstream. You can temporarily fix the build locally by overriding the package and setting to .
Also, could you post the rest of the line starting with . It is getting cut off by your pager and seems to contain the actual error from the mount attempt.


Keeweb opens an empty window, hangs for a few seconds and then the program simply crashes. Looks like a missing libGL dependency. <details<summaryLog without libGL</summary</detailsSteps to reproduce the behavior: Keeweb from Terminal or .desktop file. Keeweb not crashing. Just an empty window with only an icon and title. Can be started with following Command: <details<summaryUsing this overlay to launch it without having to use the terminal.</summary</details<!-- 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]:


has an assertion on enableSSL that requires certFile, keyFile, and caFile, but caFile is optional with SSL and only used for client certificate validation. ttyd is able to serve over SSL with valid certificates Steps to reproduce the behavior: builds with the provided options Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've committed a fixed file to my own flake that fixes the assertion (as well as adding the "--ssl" flag, which was missing)
please view


Since Zettlr is an Electron app, it needs to be run with certain command-line arguments on Wayland (specifically ). In NixOS, setting the environment variable to should automatically tell packages to use this command-line argument, but this requires integrating it into the package file (see ) for an example. The Zettlr package does not currently do this, which results in pixelated and glitchy graphics on Wayland unless it is manually run with the correct command-line arguments. This should be a pretty simple fix, as it has been implemented before for many other Electron apps by creating a binary wrapper.


I'm trying to use GZDoom, but the Vulkan backend isn't working. No errors, but it will silently fall back to OpenGL. Apparently this is the case if GZDoom can't find the correct Vulkan drivers. I have a Radeon RX 5700 XT, so my GPU definitely supports Vulkan. Steps to reproduce the behavior: basic without any mods <kbdesc</kbdthen <kbd~</kbdAt the end of its loading it should say what renderer it is using This is a screenshot of it running with Vulkan from someone else's system: ! This is a screenshot of what it looks like when it's using OpenGL: ! Note the lines. GZDoom uses Vulkan Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


I noticed that nvim wasn't loading any of my treesitter plugins. I decided to check the plugin directory. hm. something is very wrong here. it isn't pulling in any grammars. let's investigate: ok, so it's looking for a file at . what does the grammar derivation look like? So the parser is ending up at instead of . What does the grammar derivation's source look like? Checking , this code has been in place for years. Checking for , I find It was merged three weeks ago. I see that is open. I couldn't find any information on this problem with GitHub search... Could that PR be merged quicker please? My editor setup is broken now :( system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I think this is not actually the direct cause of the issue you're seeing since the grammars go through (see the below, which precisely corrects the observed discrepancy) You're not seeing the grammars when you because the grammars are in . I explain how to properly build it in The PR is broken, don't get me wrong, but I think not this directly :p. For why your is broken, see I think it's because of your dependency on and which pulls in a without any grammars but I'm not sure. You can try giving an approval, I'm in the same boat as you (I don't have merge permissions). Apologies for breaking your setup!


package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- 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]:
That's a bot.
Thank you for the quick turnaround!