The system-wide LDAP client configuration in is ignored by Openldap client programs. Steps to reproduce the behavior: settings into via or any other Openldap client Openldap client programs should obey the system-wide configuration file in . strace shows it's reading the example configuration from the package instead: Since commit the openldap package no longer passes to configure, it only passes to make instead. Please run and paste the result.
It seems a bit dodgy, but this might be a solution: plus corresponding changes to all the packages and tests that refer to . I'm just rebuilding a gazillion packages on my system from source, so I can check if that works properly...
you probably meant to ping and instead
Oops, sorry about that. I forgot that the maintainer handles listed in the package do not necessarily correspond to their Github usernames.
I realised that changing is probably unwise. Not only does it break some other packages (like python-ldap) and some Nixos tests, it will also break any users who have configured slapd to refer to the schemas under , as I myself have: And changing is not necessary to fix the bug anyway. It seems that the approach of passing differently in compile and install works. I'll send a PR for it.


The change to use at broke evaluation of The expression was changed to reference but that is undefined. It evaluates and builds with the following change? What I'm not sure about is if this is all that is required or if there is anything more before I submit a PR. System: (Flounder) Nix version: nix-env (Nix) 1.11.3 Nixpkgs version: (local git checkout with patches)
Also I'm not sure if any of the other expressions changed were similarly affected. Quickly testing the expression appeared to evaluate successfully despite not having as an input.


Per the , can only be installed on 32-bits systems. Is this still correct? It's a rather old expression, and given that other 32-bits software can be installed on 64-bits NixOS just fine, I'm not sure whether this needs to be changed.
I think there was another attribute for as well, but I am not sure about that.
this should be documented actually
Or the expression could be fixed to transparently install the 32-bit version. Like this does (I think):
You might be refering to there?
I thought there was also something called without the part but I guess I am wrong with that. In any case, the solution proposes looks like a good one?
Does the package work actually? I'm trying to test it, but it seems to be downloading forever.
OK, it seems to play fine.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- 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! --- name: minio <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2022-05-08 desired version: 2022-07-15 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.


When a user starts and opens a file dialog the application crashes with (Jameica 2.10.2:): GLib-GIO-ERROR **: 22:23:21.974: No GSettings schemas are installed on the system Steps to reproduce the behavior: jameica a "workspace" -manage backups -restore different backup Opens a gtk file dialog jameica crashes on every file dialog for me. the backup path is just the easiest accessible and something a user may come along quickly. i was already playing around a bit with the wrapGAppsHook, but i just dont get it running atm. so maybe someone else want to take a look on that. i am running a kde session on wayland, but i doubt that it make any difference on gnome or other DE. <!-- 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.
created a pr for it. my first tries in adding wrapGappsHook did fail as i did not get, that the order for nativeBuildinputs do matter.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- 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! --- name: tutanota-desktop <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 3.95.4 desired version: 3.98.15 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Version 3.95.4 is not supported by Tutao GmbH anymore. I don't know how that exactly works with Nixpkgs, but it would be desirable to update tutanota in the stable 22.05 channel too. Please tag this issue in your PR.


name: flexoptix-app current version: 5.11.0 desired version: 5.12.1 maintainers: Please tag this issue in your PR.


Steps to reproduce the behavior: See . Regression of Blocks: Blocks: porting GSound and GNOME Clocks to macOS Notify upstream: libproxy/libproxy <!-- 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.
A possible fix:
That looks like an upstream bug – the build system should never use functions it is undefining. And either way, on Darwin, I would expect system JavaScriptCore to be used instead of Duktape.


Steps to reproduce the behavior: git-town on MacOS Please run and paste the result.


If I try to run Solaar via Rofi nothing happens, when trying it via terminal the following error occurred: If I open a nix-shell with and run solaar it opens and works without issues. Relevant configuration: Steps to reproduce the behavior: system from unstable to run solaar Solaar GUI main windows opens I've tried to find out more and was directed from that it could be related to missing but regardless where I it it didn't solve the issue. Please run and paste the result. nixos-unstable -
see
Thanks :)


Putting this out here in case anybody else is seeing this. On am Acer Swift SF314-43, the touchpad goes missing with kernel 5.19. Works again with kernel 5.18 and no other changes. Steps to reproduce the behavior: to kernel 5.19 that it's broken With kernel 5.18: With kernel 5.19:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This happended to me as well, on a Tuxedo Aura Gen 1 with an ElanTech clickpad and NixOS 22.05. Comparing the output of between kernel 5.18 and 5.19 I found three modules, which haven't been loaded on 5.19: , and . ~I them to , ran and after rebooting the touchpad is working again.~ Adding them to in my NixOS configuration did not help. Edit: Was on the wrong kernel version, when testing if manually adding the modules would help.
Ah, on 5.19: Kernel rebuilding time. Haven't done that in a while...
So that did it. I didn't need to specify the list of modules, only add the kernel option.
That fixed it on my Tuxedo as well.


Right now, we have sections covering Perl, Python, Ruby, Go, and more. is another popular language and we have an easy/automated way to add new packages to nixpkgs. We should make this easier for people who don't already know how! I plan on tackling this based on instructions I received over at
cc
Some of the entries in the document have a comment like Should I enhance the in and then generate the XML file? Can anyone clue me in to how they're generated?
They are generated in (using pandoc).
Once I've it to , how can I actually generate the XML?
The XML is generated during the build. To have it in the manual you need to include it with in . The confusing part is that refers some files that exists only at build-time (the files generated by ). It is also possible to keep the build directory with to inspect the generated files.


glslc binary in shaderc has invalid signature Steps to reproduce the behavior: to compile shader on aarch64-darwin to SPIR-V should not be killed


Easyeffects crashes when Echo Canceller is used (at least when applied on input). I've been told that it works fine on arch linux. Though it might be my hardware that somehow makes it crash. Steps to reproduce the behavior: Echo Canceller module to the Input Easy Effects to one of recording apps It doesn't crash It doesn't write anything useful in the logs, just exits with code 137. Please run and paste the result.
I can reproduce it but it is not a regular crash – there is not core dump. It appears to be killed. Weirdly when I run it with: The termination is not caught.
For me it reproduced with gdb: Maybe it's terminated when child process is crashed?
hmm, it seems to be something wrong with speex when configured to use the fftw library... not sure what, but this doesn't crash:
The same also happens in Speech Processor effect now:
Unfortunately this didn't seem to do the trick for me, it still crashes with the Echo Canceller.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I have the same problem. The thing is, used to work OK on my system. Then I tried the module, after which this issue appeared. However, now it's persisting. I undid the change, even tried booting into old generation, but is still getting killed with the echo canceller on. For reference, this is what I used to try to enable the echo cancel module (not sure if it ever worked):


When using as a root user the following error is produced: . This needs to be included, see = "source ${}/share/zsh-"; Please run and paste the result.


consists mostly of syscalls (including ). There are even Ruby-specific workarounds. C/C++ would be a better language for the task. This should also reduce closure size and startup time of FHS-sandboxed apps (Ruby needs to load itself and its libraries from disk).
Can't we just use to setup the chroot?
I'm not sure if it's capable of doing all things that we need for this, but it should be worth checking. Can it run a container as a process (not as a systemd service), and can it be used not by a superuser?
needs root privileges. btw has C code to set them up, the rest is probably bash only?
D: A pity. Well, let's continue with the old plan then. Unfortunately we can't do much more in Bash than we already do because we need to do mounts in the same process we set the namespaces, in children necessary privileges are already gone. I'm not completely sure about this but I remember that when I tried to write this in Bash completely long time ago (using for setting up namespaces mounts and chroot were a problem.
How about using this one?
bind mounts, sysfs, tmpfs and procfs should be
I can confirm that these mounts are possible from using unprivileged lxc containers. But you cannot bind mount something from the host this way, because it needs to be done after . UPDATE: ok even that should be possible if the correct order is maintained: unshare -mount -chroot.
Oh, I should look at it! cc in case he's interested in this thread. I think that checks if the user is root -- that's why this doesn't work. This means that we need to call by ourselves... (I was going to hit "Comment" but you were faster ~_^) I expect that LXC containers do user maps such that you have UID 0 in new userns -- we, however, need to retain user uid.
why do we have to retain user id?
Multiple user apps use uid and username for their purposes -- we don't want to lie to them. I can't give a complete example (I remember that Steam breaks) but for example we have directories which apps can find based on uid.
I have another suggestion: the Go programming language. Bear in mind that I'm generally not a super big fan of Go (in fact, while I use Go extensively at work, I generally use Haskell for my personal projects); however, I think that a higher level, simple (in terms of specification) language would be conducive to maintenance and further development. The binaries should be pretty small, and the closure should be pretty small, too. I might give that a go (no pun intended) and see what we think.
Several possible issues: need native and then before any calls to pthreads (or you'll get or something close); I remember that Go has a runtime so there may be problems; need several syscalls which may not be readily available, namely , and others. In Ruby I import them from libc dynamically and redefine constants from C by hand, but doing this (especially redefining constants) is one of the reasons I want to move from Ruby in the first place. However these are only potential problems -- I don't know if they actually exist! I'm actually interested in how this turns out.
You cannot use clone() properly because of the language runtime. That's why docker uses a little C for that job.
Ah, you must be referring to this from : I'll need to give that a thorough reading before I understand why the runtime gets in the way (unless, perhaps, you have an explanation of why/how pthreads mucks things up).
Oh, I'm guessing that's probably stuff like this: Though, if there are other details, I'd love to hear them :smile:.
If you refer to my remark about fork and pthreads, it's actually 's limitation. You can look at how I workaround this in Ruby by calling imported instead of Ruby's builtin. You will know if you encounter it -- will just fail. I think the best way to find out is with an experiment. (notice that I don't know about Go runtime and haven't even used Go before, so, as I underline again, those might be non-issues)
Interesting. I referred to the , but I don't see any mention of failure when used with pthreads. I don't doubt you; I'd just like to know how all this stuff works.
No problem even if these were doubts ~^. From man page:
Ah, dunno why I didn't try reading the man page -- thanks for pointing that out :wink:.
Anybody done any more work on this? Also, this should probably be tagged with security, due to
a rewrite in a different language will not solve your grsecurity problems. I also do not see how the rewrite discussed here is related to security.
Anything related to grsecurity is security-related. A rewrite into a compiled language means that a setuid wrapper can be created, which means I don't have to run shit as root.
You can drop your privileges via right after you enter the environment as -- it's less convenient but you get roughly what you want.


Steps to reproduce the behavior: build -L 'nixpkgs#curlie' <details</detailsNot a go developer. I think the issue is the same as . That requires a fix from upstream; I don't know whether this is the same, though, and my attempts to patch the build (and thus demonstrate it needs an upstream fix) have been unsuccessful. I used with the following patch. This resulted in the following error. I tried vendoring the derivation and adding the call to (using ) but at this point I hit the time limit I'd set to investigate this. Please run and paste the result.
You need to update vendorSha256, too. IF you get it working please create a PR.


In GNOME keyboard shortcut settings, the list of categories based on and on my own experience with GNOME on other distros should be: Launchers Navigation Screenshots Sound and Media System Typing Universal Access Windows However, only the following categories are available: Launchers Screenshots Sound and Media System Typing Universal Access So I'm missing Navigation and Windows. Install gnome package and use GNOME. Open keyboard settings (press Super, type "keyboard", choose Keyboard). See the list of categories on the left panel. System: (NixOS: , Ubuntu/Fedora: , ...)Nix version: (run )Nixpkgs version: (run )
I am affected too. Moreover doesn't lock the screen.
I got that, too. Seems like that might be .
Another possible source of not working (if you're using GDM):
Apparently the Control Center derivation only provides some keybindings: the others are part of other packages like GNOME Shell or GPaste. The Control Center loads the bindings , basically using to locate them. But even explicitly passing the path does not make the Windows section appear – though, strace confirms the file being read. Edit: Nevermind, it looks like the navigation and windows keybindings come from .
Hey, have you somehow managed to get it to work using ? (Not quite sure how to interpret your edit). I tried messing around with that but so far I’ve only been able to break :
Try . The error you are seeing is caused by missing GNOME shell SCHEMAS, which will most likely be in the current variable.
It looks like the error I was seeing was related to fish shell not having setup properly and was failing even if I didn’t attempt to change anything. I switched to bash and that particular problem disappeared, however I am now getting a different error message: However, this schema seems to exist in mutter, so I sadly have no idea what is going on here:
Right, for that you also need to add share/gsettings/mutter-3.28.0 or something like that.
Thanks a ton! I finally got it to work using that!
I was able to get it to work using .
The mutter keybindings are not available in control center in NixOS when . Explicitly adding mutter to fixes it. Should mutter perhaps be to ?
I think adding it to dependencies of g-c-c is more in line with Nix. We can do it after we merge 3.32.


On current , (4.2.4) group voice chat will be stuck on "connecting" forever, while private group voice works. This issue exists when connecting from different countries, using different account, with or without proxy, so it seems not really a "connection issue". a voice chat in a private group. it stuck on "connecting" phase forever. Successfully starts or joins a voice chat. chat and live stream are broken. (one to one) voice chat works without issues. 's version of telegram works. (Its font is broken though) Please run and paste the result.


Try building
Just ran into the same problem when updating my system flake. For bisecting purposes, nixpkgs was my previous (working) configuration. EDIT: bisection in progress, have to do some large builds now:
Excerpt from : which seems to be the change that breaks , so we probably need to file an upstream issue.
As a workaround, something like this should work:
Note that the downgrade would undo some security fixes; see PR ... which is also why we backported this problem to 22.05.
I see...I'll wait to re-enable qtile then
Depending on how much value you place on the failing test, something like this worked for me: Modifying the package in a general overlay triggered huge rebuilds for me, so I've just replaced it inside my derivation, which is what pulls in in my system configuration.
How would you modify the package with a general overlay? Something like this didn't work for me:
This global overlay works for me, without annoying rebuilds: Note, I'm using and this is imported in . I don't know if you can use it without modifications otherwise.
I have a similar setup, I have (minus the let bindings I have in my config): So I don't see the difference between our configs...
Somehow, the overlay proposed by worked. This reaches about the limits of my Nix knowledge, but maybe is required instead of simply ? Is the only difference I can notice.


When one installs mastodon via the following minimal config: Then there is no obvious way to run tootctl. or any other login user doesn't have the executable by default, nor can this be enabled in an obvious way. is not a login user, so can't (and shouldn't?) log in as and execute . Steps to reproduce the behavior: mastodon as per minimal config above ... nope. ... nope. ... nope. ... nope. Any of: a setting such that is installed for that user an explanation in the docs what to do as a login user (probably bad idea?) Workaround: CC
I think upstream intends only to be run by the mastodon user. My way for doing that is just running and continuing in that shell. The reason why doesn't work is probably because sudo inherits PATH from the user you are coming from? I'm not sure I understand the concept of a login user enough. How would mastodon become a login user and why would that be a bad idea?
In the mastodon docs, it is described the following way: But is not possible, it gives the error They do recommend (which is what I meant by it shouldn't be a login user), but still they seem to do something different than nixos does. Maybe that's fine, and it would be helpful to document this somewhere, so people don't spend a long time trying to find it out.
This is default for almost all service users because they have no login shell. Use ` This is wrong. Sudo resets all path like variables like PATH and PYTHON PATH. Also inheriting needs to be turned on explicitly and PATH mist always ve inherited explicitly. Other services like nextcloud include a wrapper that sudos to the right user. This should be for mastodon, too.
Sounds like a good solution. Then we could make the command globally available.
That isn't? I would have expected that it is very similar to nextcloud-occ.
No currently it is only available to the mastodon user, so tootctl never gets called as the wrong user.
There is a hack in the nixos nextcloud-occ script that automatically sudoes if called by a different user. This could be adapted to tootctl I think.
Yes, this should be adapted. Changing the mastodon to a login user would not be the correct fix.


When exporting the graph, logseq throws a permission exception. Steps to reproduce the behavior: a new graph a few pages them public ()) the graph The graph should successfully export and opening it should show a read-only view of the graph. The logseq documentation itself is an example thereof. If applicable, add screenshots to help explain your problem. Bug was first reported in the original repo When running the AppImage with it's fine because it's extracted into , but when the app is in then it won't work because of the read-only status. I tested the flatpak version because I suspected the same problem would occur, but the directories are mounted read-write in a read-only volume. So, 2 options exist as I see it: fix it upstream, but I don't know Clojure nor Electron start the AppImage with instead of extracting it Please run and paste the result.


On my M1 Mac, with homebrew-installed libvirt / qemu-system-aarch64, I'm able to run the VM defined in the config below without issue. However with libvirt / qemu installed via nix, I get: Some possibly related discussion . Looking at the , they're explicitly setting ; adding this seems to resolve the issue: I'm not sure whether disabling those failing tests is a reasonable thing to do. Steps to reproduce the behavior: to in A clear and concise description of what you expected to happen. Should run without , like it does with homebrew. Please run and paste the result.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
FWIW, I also encountered this issue, and have to use the following workaround: And -ing the efi firmware & vars manually. Fixing this bug can lead to great user experience: virt-manager can work out of box.
Where did you get ?


To reproduce, here is an example: The related code is at Some nice to have: As suggested  should be something that can be accessible by everything and we are likely going to put our "" there and next we are going to import in basically every file. Adding to in is probably not a good idea since this is a desktop shell package you will end up having this variable everywhere, I imagine a treewide will be likely needed.


When running , I get Restarting the system did not help. Steps to reproduce the behavior: The program should launch without crashing. If applicable, add screenshots to help explain your problem.
Hello Thanks for reporting this issue, and sorry for breaking the nvtop package! I made a pull-request to fix nvtop: What do you think about this fix?
Thank you for your fast reaction ! The PR looks good to me. I hope it will get merged soon :)


pam_p11 causes login segfault in NixOS 22.11. GDM and Gnome lock screen are also affected. Steps to reproduce the behavior: to log in on the console or run `: Bug was not present in 22.05.
Reverting does not help.
Fixed by: Can someone with commit access apply this patch?
Can you open a pull request with that patch?
I hope that NixOS can be unbureaucratic enough that PRs are not required for this kind of patch.
It's generally preferred to do basically everything through PRs, so some basic CI checks can run & maintainers can be pinged automatically. We can just self-merge though. I created containing your diff and adding a comment for explanation.
This seems to be whats causing my 22.11-beta19 install on an Alder Lake 12700H (no gpu) to not boot into GDM. This is a pretty heinous issue that should be tested for. The graphical installer doesn't install Vim, WPA_Supplicant or anything useful for figuring out what went wrong, despite having Vim and WPA Supplicant available on the installation media/calamares.
Well I just did - you're welcome. That's what beta releases are for, aren't they?


i3 has been updated to 4.13. I attempted to update our derivation but they switched to and I don't know how that works :) If somebody could update i3, I would really appreciate that. /cc maintainers
FYI, for to work it is sufficient to add to the (see ).
Thanks :) I think with the main i3 the issue was that the needed to change and I did not know what to set them to.
Yes, and indeed the and are already included with the source distribution for , but I had to add the for .


The srb2 assets are outdated. Steps to reproduce the behaviour: the game or run the command while in game The that the assets are being downloaded from hasn't been updated since 2020
I just noticed this pr, but it seems to have gone dead 3 months ago
closing as I'm making a new issue


Specifically systems with AVX but without BMI2 Same as this debian bug: They solved it by pulling the latest stable 2.35 patches: ;a=history;f=sysdeps/x86_64;hb=refs/heads/release/2.35/master For NixOS, one workaround is to install a NixOS system to a usb drive with microcode updates enabled, and use that for the installation. This is because for this series of CPUs (Haswell, 3rd/4th gen) the BMI2 instructions are via a microcode update. Rebuilding the iso with this overlay also works, but this is a mass-rebuild: The diff is produced like this: Where corresponds to 2.35-220 and corresponds to 2.35-163 (our previous state).
It was attempted to update glibc to the latest stable patches in , but this led to some issues.
A temporary fix without rebuilds would be via , I suppose. EDIT: or 22.05 release in the meantime, as I expect it shouldn't be affected and it's still supported for a few weeks. Real fix (taking more time, etc.): most likely update glibc to latest 2.35.x and somehow resolve the regression (and possibly others), and then backport to 22.11 as well.
Redoing update as PR for now.
The glibc update is contained in and channels now.


Running Dwarf Fortress () on darwin-aarch64 opens a window that is completely white. It receives inputs and sound also plays, but nothing is displayed. This might be due to the package not having an app bundle as an output (e.g. 'Applications/Dwarf Fortress' next to bin) Steps to reproduce the behavior: dwarf-fortress on macOS Window opens with graphics displayed ! <!-- 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.
I should have tested the files from the official website first, since it turns out it has the same issue. Changing PRINT_MODE to STANDARD made it display correctly. I don't know if the should still be patched in nixpkgs to include this so that you can leave the link to the store for the file. Feel free to close this otherwise.


The postStart script of elasticsearch fails when a special values like or ( ) is used for services.elasticsearch.listenAddress as the script expects an IP or a hostname. Using an ip as listenAddress ist not always a viable option especially when generating NixOS images upfront for a dynamic deployment (e.g. on Azure or EC2) I am not sure how to address this issue. Perhaps one shall check netstat output to find out which ip was bound to? /cc
Yes i agree, we should implement another option for es url, I'm fine even with removing postStart. You can create pull request if you need fix asoap, I will put it on to-do.


Can't launch discordcanary with NIXOSOZONEWL=1 Steps to reproduce the behavior: NIXOSOZONEWL = "1"; in environment.variables discordcanary with Discord should open without any errors I got this error Please run and paste the result.
Library should be from
Please try with


In the pre-start script for , we symlink the template from the nix store into : However, if changes are made to CUPS via the GUI -- for example, enabling network access -- this symlink is overwritten with a plain file. And it contains a line with paths into the nix store. This effectively freezes some version of the cups binaries into this config file, which is no longer managed by nix. As a result, CUPS can break, e.g. when deletes the referenced store paths. For me, this meant nothing would print, and I started seeing this error in : Manually editing to update the store paths on the line (while the systemd service was stopped) got printing working again for me. I guess we could make the pre-start script do this (with a sed or something), but that seems kind of hacky ... cc commit seems especially relevant here. System: Nix version: Nixpkgs version:
Hm, maybe the right approach is to make just put in the template, and then have it also ensure that points to the correct location in the nix store? Then CUPS can write whatever other changes it wants to its config file, while the nix expression continues to have control over the "final destination" of the path ... ?
I think we want Nix to take priority here because that's what would be expected of declarative configuration and what's already done in other places. So as a quick fix towards this we can force replacement by symlinks. This should also be documented. However, we can leave some option (like currently exists for users) that reverses this and instead makes just insert and other required options. The best of both worlds, of course, would be to split the configuration into generated by Nix and values changed in CUPS on top but I doubt this can be implemented. Thoughts?
For the record, I had the same problem in OctoPrint service. It was solved by writing a small piece of software for updating YAML trees (like in Nix) and making "patch" current configuration with Nix-overridden values. Works perfectly but it would be much more difficult in CUPS ( is some kind of ad-hoc mix between XML and custom plain format).
Yeah, I don't see any directive on the manpage for . :-( Overwriting the config file on every restart of might lead to confusion if folks are trying to use the GUI to get things configured the way they want. In particular, when I made changes in the GUI to enable remote access, it modified some of the stanzas that're currently hard-coded in at So I'm not sure how I would preserve that under this approach. (I tried to just set via , but that wasn't enough -- I don't really understand why ...)
Its man page says: ... but a bit of googling didn't turn up any pre-existing programs designed to read / write that format. (Maybe there is something buried in apache , who knows?)
There is But then you need to write Perl, which might not be an improvement.


<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- 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! --- name: openshot-qt <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2.6.1 desired version: 3.0.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package -- Please tag this issue in your PR.


explanation pnpm version is a little bit old. May I ask for update in unstable channel to v7.24.3? Project description Fast, disk space efficient package manager: Fast. Up to 2x faster than the alternatives (see ). Efficient. Files inside node_modules are linked from a single content-addressable storage. . Strict. A package can access only dependencies that are specified in its Deterministic. Has a lockfile called pnpm- Works as a version manager. See . Works everywhere. Supports Windows, Linux, and macOS. Battle-tested. Used in production by teams of since 2016. . Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin


Project description A cursor theme based in the capitaine cursors but themed with gruvbox and nord. Metadata homepage URL: source license: lgpl3 platforms: linux since it's based in capitaine cursors that use lgpl3 i think it's gpl3 too.


The version of pillow rmfuse uses is vulnerable to CVE-2022-.
Since rmfuse is packaged using poetry2nix you are basically the only one willing to update it or its dependencies. That's problematic given that you don't do so even two weeks after being notified of a vulnerability.
I don't think interacting in this way is very constructive. There are different points of view regarding packaging Python packages, that's it. That an issue like this does not get picked up is not strange, people are typically busy. If you like to I suppose you could add the CVE to the expression. Whether the CVE can be considered a security issue in case of rmfuse should be considered as well.
Why not? I'm just articulating a problem with the way rmfuse is packaged right now that is obviously an actual problem. It's not technical though, just organizational.


Steps to reproduce the behavior: in nixos-unstable -note build will failed 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.
You can override paper-note by adding the following section and it should work fine.


Project description It would be nice to have libreoffice-still-qt, to have a stable version of libreoffice (still) with kde integration (qt). In my undestranding, so far we only have libreoffice-qt which is the fresh version cf.


Project description Metadata homepage URL: source URL: license: SIL Open Font License 1.1 platforms: all


gamescope crashes with this error when run from within steam's fhsenv: This check in wlroots causes that error because inside steam's fhsenv the /tmp/.X11-unix directory is owned by nobody:nogroup. I have tried simply removing the check from wlroots but in that case gamescope simply hangs. (Note that it's gamescope that depends on wlroots so this bug happens under x11 window managers too.) Steps to reproduce the behavior: steam to the launch options of any game the game
This seems to be a very old issue with NixOS
would allow to run with without having to manually chown /tmp/.X11-unix but running from within steam as described above is still broken. gamescope dies with this error: However : So that symbol is actually defined but Xwayland thinks it's not for some reason.
I've encountered this issue too! I know got gamescope to run on NixOS - maybe we're missing something? See my comment here: Related:
Hi, I just wanted to real quickly add some context with my knowledge of how Steam works. this part is not the issue and is an ""issue"" about the steam overlay, it happens because there is both a 32 bit and 64 bit version of the overlay both of which are loaded when you launch a 32bit or 64bit game, so this is not related. It happens every time you launch a game on any distro without fail since a game cannot both be 32 and 64 bit. ERROR: object '' from LDPRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. Everything else in this log seems normal, outside of this part: which could point to a missing library. the mentioned "" might be what we need to look at here. Also, thank you so much to for posting the workaround too, I was getting a headache dealing with this.
Hi, i wanted to ask if someone is working on this issue?
It's an open-source project, so unless someone with the necessary knowledge is interested in the issue (could be yourself), then you'll probably have to wait.
I ran into this same issue before. The only thing that let me run gamescope through steam so far has been the solution from , but I am not sure why it works.
I'm trying to add the patch in in , eagering for testing from you.
There seem to be multiple issues conflated here. The original issue with X11 socket ownership has been addressed. If there's another issue that prevents running gamescope in Steam, please report it separately.


Steps to reproduce the behavior: to build from source Please run and paste the result.
cc maintainers
Can you check if is working? Looks very close to the regression fixed in (did not get to yet).
is there a cache for that branch? using with that started building the world
does have an incomplete cache. If you are accessing at inopportunate time you might catch a few rebuilds. You can pick a specific commit from with most builds done. Most recent it yesterday's
that commit did not fix the issue
edit: scratch that, tried a fresh build. works now
Closing since it sounds like this was fixed by the merge of . Happy to reopen if I'm mistaken.


Using with seems to be broken with and . It fails with . also notes this. Running yields . The contains just an empty and I am using this flake's devShell: The same also occurs when using a shell with only and when trying to use inside a nix build. I am pretty sure that this is caused by in containing instead of (which it does for ). I don't know yet, what the root cause for that is or how to fix that. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (So it shows up in the tracking issue )
Apologies for the delay in getting to this. Minimizing your example ultimately leaves me with: Staring at the output of ^ with reveals that is a linker script that appears to be passing in : For LLVM 14 this file looks like: But for LLVM 15: EDIT: whoops, my bad; just noticed that you already mentioned this in your post, I totally missed it Looking through the source, this file appears to be generated ; specifically the should be coming from based on . For Linux/macOS (i.e. platforms using libc++-abi) that should be set . Poking around a bit suggests that this is a bug in upstream; is not an interface library so it has no (though it has an ) and its is never set. And sure enough, looking at upstream reveals that has been (see ).
Applying that patch and rebuilding locally seems to fix the issue; I'll open a PR (and add regression tests for this) shortly.
Thanks for looking into this! Building from the PR-branch now no longer fails in the way I described and the example works for me again. I have now found a new issue, tho: Importing fails with: For example, this causes this error (using the same flake as above, just built from the PR branch). I was able to work around this, by adding to the end of the phase of locally, but I am not sure if that's the right approach here.
(Re I have a proposed fix for the _cxxabiconfig.h issue on llvmPackages_16: -- currently I'm inserting an additional include search dir for it. I also don't know if this is the best approach or alternatively if that header (and friends?) should be copied into libcxx or similar.
I ran into the same missing header issue compiling using on . Maybe the fix isn't enough, and should be copied?
this change is missing from 15
running into the same problem compiling some static libraries in nixpkgs using pkgs.llvmPackages_16.libcxxStdenv. Does this warrant its own issue?
Yes, file a new issue. Please also provide reproducibility bits, including the error message you see, the package expression you're trying to build, and the nixpkgs revision. I'm guessing the issue you're seeing is failing to build, which is a different problem specific to static builds.
(If my guess is accurate, the problem you're seeing is a variant of ).
sorry for bothering you, turns out it wasn't really this issue. Using my limited knowledge on the matter from what I understand, is not installed to like . Now, turns out (and ) is a default system header path (for CXX of course) and so is BUT is not so if one were to they would just run into since that is nowhere to be found. There are two solutions to this is as a system header path like we simply just install everything under on non darwin systems as well. I actually do not know why these are all not copied on non darwin systems. Please correct me if wrong. I might be completely wrong.
check
No bother. I'm sticking my oar in because I'm interested in getting to the bottom of issues exactly like this. It's difficult to fix things it without precise reproduction steps, though. What you're describing there sounds very much like something I tried to address in (see ), which is on nixos-unstable. So it sounds like you may have found further issues, but I can't do much to help without a reproducer. In any case what you're describing sounds like a different issue to the original (which was ), so I suggest posting a new issue pretty much as you described but with a reproducer I can run at the terminal, since it is meant to be in the system include path already (per the link above). If it's not, that sounds like a bug worth filing.
Okay I found the problem, and the "obvious" solution as well, you can find it here


Build of failed on x86_64-linux as of . This is currently breaking . python39Packages.tensorflow-datasets maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: - -
huh this is a weird failure to me since fasteners==0.18 at the time of this commit which should be working... building locally on this commit i get a different failure: very peculiar...


Currently, most functions work without problem. However, when I try to add new paths to search dictionaries, it crashes with the following error message: Steps to reproduce the behavior: goldendict Edit Dictionaries Source Add crashes A dialog should pop up to select the path. Reproduced using the latest master branch of this repo. Using startx and qtile as the window manager I've submitted a PR to fix this issue (see ) <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --


sakura terminal emulator terminates when trying to change color by context menu with following error: GLib-GIO-ERROR *: No GSettings schemas are installed on the system [1] 9932 trace trap sakura run sakura, right click to popup context menu : options -select colors -(click on color field to open color chooser) Here is a thread that discusses the issue. it seems that the color-chooser gui description is missing that is needed by sakura. should include gsettings as runtime dependency. actually it has gtk3 package as dependency which provides those schemata, however it obvious doesn't look in the right path. this kind of error got fixed for System: (17.03pre98008. (Gorilla)) Nix version: (nix-env (Nix) 1.11.4) Nixpkgs version: ("17.03pre98008.")


Steps to reproduce the behavior: package is marked as broken I marked this package as broken starting with linux 6.2 because enables by default. The binary blobs included with the nvidia driver are not compiled with support for IBT and nvidia hasn't been able to update their internal toolchain to support it at this point. Rather than leave it broken, we should probably check if the driver is built using the proprietary blobs and add the kernel parameter starting with linux 6.2. <!-- 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.


A ends with the following: commit -rebuild switch System: NixOS: Nix version:nix-env (Nix) 1.11.4 Nixpkgs version:
Do you have grub on an encrypted partition and have ?
no, I don't have that option specified anywhere at all. Also, the error has since disappeared after moving to a fresher .
GRUBENABLECRYPTODISK=y' in file That seemed to say that, no idea what the issue was then, so I'm closing this, please reopen if it occurs again.


The script does not (consistently) follow symlinks in the parameter, which it uses to locate the system closure to activate. This breaks when used with , which creates a symlink. When the kernel command line has , the script looks for , which does not exist. ~(Workaround: generationsDir users can pass instead.)~ Update: That doesn't work either. with will fail in strange ways, ultimately stemming from not calling . System should boot successfully when using generationsDir and systemd-initrd together. Symlink resolution was partially addressed in , but only for cases where is a symlink. Booting also fails if the given is a symlink, or if any part of the path to is an absolute symlink (because filesystems are mounted at , not ). I took a stab at fixing this in (), but it does not handle absolute symlinks correctly. Since generationsDir creates absolute symlinks to , this fix alone does not fix compatibility. ( changes those symlinks to relative, and together the PRs fix the compatibility issue.) Ideally, the script should follow symlinks in any part of the param, even if they cross filesystems. One option is to resolve the links inside the chroot. I couldn't figure out a clean way to make this work. (Can we trust that will have the we're looking for? We can't use because we're still trying to establish which system that is.) Another option is to somehow . (At time of writing, this question has no answers.) (guessing based on git log):


Package name: wpgtk Latest released version: 6.5.7 <!-- Search your package here: --- Current version on the unstable channel: 6.5.5 Current version on the stable/release channel: 6.5.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.


Changes introduced in forcing package (or whatever the option is set to) installation even if the set to . This is because the module is unconditionally adding the package to the : Steps to reproduce the behavior: both and to in order to avoid enabling the service or systemd overriding the package with . installed packages, for example using the command. An package is installed into the system: An package should not be installed into the system. I am on a quest to build a minimal NixOS system for usage in LXC containers and trying to trim things down to the minimum, without having to resort to forking, overriding, patching and maintaining individual modules. I am happy to open up a PR to move the package assignment to the block: but would like to check if anyone has any objections or reasons why I shouldn't be doing so. appreciate any insights  Please run and paste the result.
As the author of that PR I have no objections to restoring the old behaviour.


Steps to reproduce the behavior: (the current version in ) I was having the same issue that was fixed by until a few days ago and built and worked flawlessly. I am currently using the version it is supposedly trying to build. returns , so I do not understand why the build is needed in the first place. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (because you made the last commit) Please run and paste the result.
I tried rebuilding today after the fix you committed (thank you for being so quick), I am still receiving the same error. Is there something in particular I need to do for the fix to propogate? I know that there is a little lag before a commit comes in from , but I thought 3 days later would be enough?
The fix is now on and , so if you are on either, I guess you just need to update the channel. Otherwise, the following command should work:
FWIW, is also a handy tool for checking the status of a PR's movement into the various channels.
that worked, thank you. this is also very useful, will put it in my bookmarks!


Steps to reproduce the behavior: -shell -p quickbms Please run and paste the result.
It's possible that this package just isn't buildable One of the errors encountered is: is not supported in recent openssl versions.


Project description CLI for interacting with Scalr. Metadata homepage URL: source URL: license: apache 2 platforms: windows, linux, darwin


Package name: oracle-instantclient Latest released version:21.9.0.0.0 <!-- Search your package here: --- Current version on the unstable channel:19.16.0.0.0 Current version on the stable/release channel:19.16.0.0.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! -- looks like it tried to upgrade v19 of instant client, but it is stale and not targeting v21. 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.
It looks like you were the last one to touch instant client.
Package sources:


Package name: swayws Latest released version: 1.2.0 <!-- Search your package here: --- Current version on the unstable channel: 2022-03-10 Current version on the stable/release channel: 2022-03-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. --Note for maintainers: Please tag this issue in your PR.


This is a continuation of the topic from the initial "upgrade datadog-agent to v7" ticket - see for details on that. The is a metrics and log collection agent intended to run on linux systems for use with 's paid service. On other linux distributions, installing the datadog-agent includes the integration/plugin code, there is no separate install for those, or post-install steps to install the plugins (only config to activate/configure them). Configure the in , and add some extra integration, such as the docker integration. and look at the installed, the plugins are not available. You should see logs from the agent about those. When configuring the datadog-agent, the standard integrations/plugins (docker, nginx, apache, postgres, etc, etc) should be installed and available to the agent if the agent is configured to use them. Please run and paste the result.
There's still something wrong with the Python environment.
Most likely we need to use pyproject to build it properly: That results into missing ddtrace package, which needs to be .
Looks like setuptools wasn't building the and modules. and should fix the integrations. Datadog is planning on dropping setuptools, so we should switch over to pyproject. The blocker is that there are a number of missing dependencies that aren't on nixpkgs yet, but I've started working on that. the Docker integration was rewritten in Go and is now built together with the . You can enable it with: I have no idea why they're now called Yeah, we need to rethink how these integrations are enabled. Now that some of them are part of the , it's become quite a pain to set up.
Fixed in
Thanks! Note that, to get this to run for me, nixpkgs needed an overlay specifying that all packages wanting would get . That looks liked: It seems that, while is deprecated and python 3 is "the default", the package maps to , so a lot of packages effectively default to python 2. Thanks to for coming up with that workaround. I haven't yet see the docker integration work, but I've seen the plugins and such install, so that is promising, and it's likely the last bits are in my config to sort out.
are you on an older release of nixpkgs? has been set to for the datadog integrations since .
We determined the evaluation error came from here: Did we mess that up somehow?
There's a good chance that can be removed from there with no impact. We recently did so for the systemd service.
is a vestige of the old agent. It was a python wrapper that launched that jmx java thing. can most definitely be removed check is broken. I imagine we'd need to package


Project description Gut is a CLI designed to make Git easier to use. Metadata homepage URL: source URL: license: mit platforms: linux, darwin, windows


libnfc from the cache does not seem to work for me: ~ What happens is a null-pointer dereference somewhere inside IOKit: ~ I am really not sure what is going on, but what troubles me is that I cannot reproduce the build on my laptop: apparently, the examples depend on readline, which is not listed as a dependency. ~ How does the manage to succeed on Hydra? What’s wrong with libnfc or libusb built on Hydra? After I as a dependency the build succeded and the resulting libnfc is fully functional.
Do you use sandboxing?
I honestly do not know how it works and if it is enabled by default.
I have opened to address the readline issue (which is probably completely unrelated).
I ask because it could account for the difference (that is, there could be an impurity in the build, causing it to break in unsandboxed environments EDIT: or allowing it to succeed, whichever). It's not enabled by default, but I'm not sure about how stuff works on MacOS wrt sandboxing.
Hm, you have a point. I guess it’s not sandboxing but something similar: building in a pure nix-shell yields non-functional utils.
Ok, now I see. Without it found Homebrew (as the expression does not depend on and therefore the system is not shadowed) and it told it about libusb installed from Homebrew. So, apparently libusb is the culprit.
On my end, I've found that with to the build environment, the readline error manifests (whereas it builds fine otherwise); adding both & allows it to build. There's no segfault, however. As a side note, FWIW, is much weaker than the isolation provided by the build sandbox (it just clears most of the shell environment, you can still traverse the rootfs & pick up all sorts of impurities).
How did you build this? Do you see the same result with ?
Try running: in your nix-shell. see
We need some proper way to fix that.
We could have it set in at least temporarily. There are no real side effects to just setting it besides the potential impurities.
I spent most of yesterday trying to debug the issue but with no luck: I did not manage to build libusb and libnfc with debug symbols (I have no idea how works on macOS; apparently it puts debug symbols into but does not copy them to the resulting binary, therefore, when the library is installed into the store, debug symbols are gone. It would be great if someone taught me how to do this properly).
What exactly is that impure thing that makes pull system CF?
In this case it's the framework, that's linked against the system CoreFoundation, I'm still testing some stuff but I'm pretty sure that I have a proper solution.


Steps to reproduce the behavior: rustdesk None
Should be fixed in , thanks if you can test it.
tested and it works! Will close once it gets merged lands on unstable.


Package name: django-sesame Latest released version: 3.1 - <!-- Search your package here: --- Current version on the unstable channel: 1.7 Current version on the stable/release channel: 1.7 <!-- 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.
https://django- The docs for django-sesame ensure compatibility with Django 3.2 and 4.1, which are the versions covered by unstable and the latest stable releases. There is no guarantee that 1.7 would have been compatible with the current Django versions.


Installing and using fzf breaks with the following error message: Steps to reproduce the behavior: fzf with tmux integration, I did it via home manager modules fzf with tmux integration within tmux The tmux pop up appears with history to filter If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result. Looks like this got introduced with The runtime dependency was with that new version: Line 183 of file I wasn't able to find a proper URL to link to that line within the diff.
Workaround: Install as another package.
due to providing the update to 0.39.0 at
Should be fixed by , would be helpful if you could test it.
Thanks I'm pretty new, is there any doc how I could test this on my machine?
If you're using Nix channels then you can replace your channel with and rebuild, which will build all your packages from my PR branch, including . If you're using Nix Flakes then you can change the nixpkgs input to be which has the same effect.


It would be nice if the packages provided a icon. the following in your : up a graphical application launcher and search for Wootility. Please run and paste the result. <pre<samp- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: </samp</pre
PR submitted that, among other things, adds a desktop-entry file.


Codux is a visual IDE for React that enables users to visually edit their projects and see changes reflected instantly in their code editor. It aims to streamline the development process and provide a more intuitive way to design and develop React applications. <!-- Describe the project a little: --Metadata homepage URL: source URL: (unfree) license: unfree platforms: windows, linux, osX


does not appear to be supported on ; this is possible via , and works with no issue, so it does not appear to be a technical limitation. I am not familiar enough with Nix to port over the homebrew packaging, but was planning on taking a stab if this issue does not get traction. or and System: Nix version: Nixpkgs version:


Currently, it asks for password four times to create a hotspot, such as reported at It was fixed in I think in NixOS, polkit is disabled by default, so I enabled it with , but it does not seem to make a difference. Please run and paste the result.
Thank you for the bug report! Which command are you using to create a hotspot?
I'm using the gui . It asks for password once. Then enter SSID, Password, Wifi interface, Internet Interface, go to Advanced and check 2.4Ghz. Press Create hotspot. It now asks for password thrice.
Ah, again it's linux-wifi-hotspot assuming it's located in /usr/bin


When typing something here: <img src="https://user-" width=50%The desktop crashes and you have to re-login (well it's Chinese in the screenshot but I hope you get the idea) <img src="https://user-" width=50%Steps to reproduce the behavior: budgie menu something crash No crash. See above. I don't see this issue before the GNOME 44 update. Probably another issue but I haven't go deep yet. I am on right now, it's nixos-unstable with pull request picked.
Backtrace points to <details</detailsLooks like there are changes on that touches after 10.7.1, I am testing that right now.
I gave the latest HEAD (i.e. ) a try and cannot reproduce the issue so probably some of the commits fixes the issue. I wonder if this can be reproduce by others and if some fixes can be backported before 23.05
Ohhh goooooood and now I am reading , let me make some noise there Edit:
And now I am on , which has glib 2.74 ( has 2.76). This is going to be weird because with G_SLICE=always-malloc I also cannot reproduce the crash (budgie-desktop 10.7.1), so probably not related to the slice allocator. Edit: and it's vala 0.56.4 on (no crash) and 0.56.6 on (crash)
Okay I guess I can basically confirm it's caused by vala update because I am now on and cannnot reproduce the crash, wow it's first time I know valac can really cause issues :seenoevil: Bisect is too painful for my slow laptop :upsidedownface:
Could you try compiling and running this Vala code on the broken version to see if it also crashes? It should do the same thing as the crashing Budgie code, just without crashing your desktop. If this ends up being a Vala issue, we need a minimal reproduction program to send. Build and run with (assuming you put it in a file called ):
I am now on and my desktop crashes, so the current range is :upsidedownface: I am away from keyboard for the next few hours because it's midnight here but feel free to drop questions :upsidedownface: I built the program with vala 0.56.5, it exits normally with
Well, crap. I was hoping that would crash. Maybe this version when you get back? It's closer to the code in Budgie: Of those commits, the only one that really looks suspicious to me is at a glance.
I am still here (for now) :laughing: but this runs normally for me as well (hmmm can we really guarantee "if I can trigger the desktop crash, then using same vala same laptop same setup we can trigger a crash with some different program"?)


One uses to create a new tree of files for generating a web site. So the intent is to edit those files. But the files produced are read-only, so user must do a before each new file can be edited. I haven't looked at the source yet, but I imagine this is because jekyll copies the site template out of an installed gem or something, and all the files there are 444 (read-only) because it's in the Nix store. System: NixOS 16.09.1600. (Flounder) Nix version: nix-env (Nix) 1.11.6 Nixpkgs version: 16.09.1698.
Have you tried reporting this upstream?
I have not. Will consider that – it seems that a fix would be a one-liner after to do or so. But I'm not able to test easily if that's all that would be needed – the nixpkgs expression is quite behind, carrying jekyll 3.0.1 when current release is 3.4.1. I tried updating too, but ran into bundler problems, and I don't know much about ruby.
You seem to have idea how to fix it. Should really bring this up with upstream. I don't know much about ruby, but nixpkgs manual has a step by step guide: Turned out to be very easy:
So I ran into bundler problems)
Ok, I've pushed a workaround for that


Package name: tracker-miners Latest released version: 3.5.1 Current version on the unstable channel: 3.5.0 <p</p- The package update itself is trivial, but I got stuck at addressing . There is now a ioctl check that runs: The program seems to build fine, but does not exit with 0: This makes the Btrfs subvolume feature disabled: I am not sure where to get start to enable this since in they decide this will be a hard check on next major bump (well, it should be possible to opt-out but it should be possible I guess). :seeno_evil: Note for maintainers: Please tag this issue in your PR.
I am getting , even though I do not use BTRFS so I assume this depends on the kernel version of the builder? (I am using .) That does not really sound like a good idea since users can use completely different kernel version than Hydra. Maybe it should be an and the check performed only when it is . Though I am not sure what the consequences are when incorrectly configured is used. Maybe it will need to be a runtime check instead?
I saved the program as a separate and compiled & ran with as root user and it exits with 1 for me as well. says I am on 6.3.0. I use btrfs so as root runs fine for me (if that matters). Hmmm then this is weird since it sounds like is introduced (is this the correct place to check such info?). But later I found in the BTRFS subvolumes feature is disabled as well :thinking: Edit: Looks like the fedora link is broken,
Apparently, it falls back to success since I do not use BTRFS: (both inside and outside the sandbox) <details<summaryModified <codetest.c</code</summary</detailsSo that does not really sound like a good test. Edit: I .
Hmmm now I wonder if their original idea is to check whether the code , probably knowing is there is already enough? (I assume they are not supporting < 2.6.34 kernels then I expect all linux should have it?) It looks like they already has some .
Could you try running the modified in build sandbox to find out why specifically it fails for you?
This is using and putting in : This is not in builder sandbox and run as root:
The fix is now merged upstream:


Given you have PHP installed on your host and one installed in your Nix shell + symfony-cli, eg. with these packages , running will always prefer PHP installed by host. This is not an issue with Nix per se but symfony-cli, but I suggest here that symfony-cli package should be patched so that this does not happen. Steps to reproduce the behavior: Terminal 1 terminal 2 Curl statement should return PHP/8.2.5, as that's the one installed by Nix. Not 8.1.2. Current workaround is replacing symfony-cli with which strips out everything {php}/bin Please run and paste the result.
That does not make sense. Why does Symfony not use the correct PHP from PATH? I would expect any proper PATH respecting program to return the same thing as .
I agree after making a couple of tests, I believe that wrapping the binary with the PHP path is not necessary... Check the screenshot in
I don't know, but this is what they use for discovery of php versions I've not dig depeer than having a brief looks though. And I have to remind that this is about command. command does look to be honoring $PATH correctly.
Does this means that does not employ the same mechanism for locating in the and commands? which seems totally uncommon. It would be nice to have the confirmation from one of the maintainers ( ?)
I've prepared a patch at I hope they will merge it soon. Otherwise we should consider adding a patch for this here.
I think this issue can be closed now.
Yup, thanks again!
After thinking twice, the issue will be definitely fixed as soon as you publish a new tag and we provide an update in Nix, I'll leave it open in the meantime.
7 has been released now.
PR is made, I'll wait for the CI to be done before merging and closing this issue.


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.


Project description A simple GTK wrapper that installs and updates the skin. Metadata homepage URL: source URL: license: gpl3 platforms: linux


The steam client (beta) is attempting to access gsettings schemas and fails. Exporting manually as fixes the issue. into the (likely don't have gtk3/gsettings-desktop-schema already addressable on the host, not steam-run, path) steam the following error GSetting should be looking for schema files in BuildFHSEnv moves schemas to XDGDATADIRS in the fhsenv doesn't include is being pulled into the fhsenv via It's possible just adding to the end of the environment variable is the fix. I'm unfamiliar with gsettings. Attempting does not work as in the fhsenv is missing things adds in . Please run and paste the result.
Exporting GSETTINGSSCHEMADIR manually did not work for me. I left beta participation by removing the file:
+1 affected by this. Edit: this results when you participate in Steam-beta. This is from recent update - however recent major update worked perfectly (new sleeker interface and all that), breakage appeared around 24 hours ago and it was pulled by Steam. This breaks for all users in system. Removing beta flag (as in McDread solution above) works, causing Steam to downgrade. Upgrading into Steam-Beta after this will cause Steam to break again.
Setting GSETTINGSSCHEMADIR worked once for me, but no longer after a reboot.
Try setting it in the extraProfile attribute in steam.override like this
I was able to fix this by overriding steam, adding and setting :
This works great! Tested with reboot.
This worked
For me, this was in the location . Removing that file worked.
+1 affected by this. workaround does fix it.


I'm using , and I'm trying to perform an update: The update works. (information found from )
What does have to do with ? Can you reproduce the problem with just & ?
Beginner here. I think that is using under the hood. I don't know how. Should I report this issue to instead?
Sounds like breaks vscodium darwin build :upsidedownface: I will do a PR


Project description A command line editor for HCL Metadata homepage URL: source URL: license: mit platforms: darwinarm64, linuxarm64, windows_arm64 Release page: Copied install info from readme: If you are macOS user: Download the latest compiled binaries and put it anywhere in your executable path. If you have Go 1.20+ development environment:


IntelliJ (and I'm assuming other jetbrains products) uses a Python script to restart itself whenever needed (e.g. a plugin update), and if it detects that there is no Python, it shutdowns instead. Steps to reproduce the behavior: intellij. In the menu, select "File" -"Invalidate Caches..." there is no python in path, the opened window will have a button "Invalidate and Exit" run from , it will have "Invalidate and Restart" Same thing happens whenever it needs to restart, with/without python it shows "Restart"/"Shutdown" buttons respectively, and in some conditions it just asks "Restart now?" and then does not come back up when you agree. I know it's easy to fix on my end, but it's not super clear that that's even an issue, and I think python should be to dependencies and made visible to jetbrains IDEs. And yes I don't have system-wide python installed, that's the whole point of NixOS, is it not? :) I guess
I can confirm this affects the other JetBrains IDEs as well. Adding to the solves this problem. I'll open a PR for it shortly.


Project description Interact privately with your documents using the power of GPT, 100% privately, no data leaks Metadata homepage source license: asl-2 platforms: all?
i am really new to nix, and i made this by adding dependency until it worked.. but hopefully a good starting point now just need to do is, which will download the models and to run it.


A clear and concise description of what the bug is. You can browse files and it'll show them but playing a song (in my case an MP3 file) results in this error: On the next start, the song is greyed out. I've d it and it seems to try (and fail?) to load libavcodec. That might be why. is in spotify's library path but somehow it's not loading. Investigating now. <!-- 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.
Fallout from , PR incoming.


When opted in to the latest Steam Beta (version ) starting Steam fails with the error Looking at the log output, it looks like it fails to load : Steps to reproduce the behavior: into Steam Beta steam Steam runs ! stdout when running : Please run and paste the result.
i'm able to reproduce this as well
In case anyone experiences this and wants a temporary workaround, you can opt out of the Steam Beta by running
I think this might be due to a change in nixpkgs rather than steam, since this works for me on: But it breaks for me when I update to:
Building with running with and using the bad commit is part of cc
Please test .


Steps to reproduce the behavior: Error: There should be a working matplotlib for 3.8, and the newer one for 3.9+, I guess Commit caused this regression. For 3.7.0: Latest matplotlib that worked for 3.8 is 3.6.2. by simply taking the old version of (before the said commit), which builds but fails to work with tk (I'm not sure tbh how to approach it). Please run and paste the result.
also cc
Maybe, try poetry2nix or using older nixpkgs.
I tried with but it gave me a error when trying to compile some boost library...
Sorry, but I don't have the energy to provide full support for the python package sets we don't recurse (3.8, 3.9) into. As such they're untested and the fast pace at which python libraries move makes it cumbersome to keep everything in working order.
greetings ! lists python 3.8 as compatible ( sorry you need to look at html title tag to see that its for version 3.7.1 matplotlib builds with this change, tested at I appreciate how much work you put into this, so I am happy to create a PR for this you should be able to just override attribute of derivation, you can refer to nixpkgs manual for that, or let us know if you need some assistance
Thank you! you can try now to use the master branch of nixpkgs with the shell you tried before
Thank you very much everybody. This fixes it :)


Since , was moved to top level, and and are aliases of from the top level To find the usages of these aliases, you can search for in the repository Note that there are false positives (e.g. when used in overlays) and this also might not include all usages (let inherit)


Project description This is a CLI keyboard layout switcher for Gnome 3 and 4x. It is not based on the X interface but rather implements direct D-Bus messaging with the Gnome Shell. Metadata homepage URL: source URL: license: bsd platforms: unix, linux, darwin, ...


Project description aw-watcher-window-wayland is a part of ActivityWatch needed to have it working in a Wayland compositor. At the present time, without this, the ActivityWatch package is not working on Wayland environments Metadata homepage URL: source URL: license: MPL-2.0 license platforms: linux


now has an available file (). There are two implications here: should no longer use a generated/patched lockfile can use now because is avoided (which means the custom can be deleted as well) n/a n/a
, I ran the update script but ran into
Thank you! I'll keep an eye on it as well.
Is this going to work with still open?
it would still run, but the package would fail to build, so r-ryantm wouldn't make a successful update until is merged


is using the memory GSettings backend on my unstable NixOS system. Because of that it forgets any change in its settings done by the user. The window manager used is . The system configuration has in . Before the latest change () was to in an explicitly wrapper, which was replaced by . There is no explicitly mention of anymore in the nix expression after this change. Can it be related? System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )
Yeah, this is related -- my fault. Thanks!


Project description linux-wallpaperengine aims to reproduce the background functionality of Wallpaper Engine on Linux systems. There already is a wallpaper-engine implementation packaged, but it only works on KDE, while this project should work with most Wayland-compositors and window-managers. Metadata homepage URL: source URL: license: gpl3 platforms: linux I tried to package it myself, but the "just compare with other packages" approach of the nixpkgs documentation was very confusing to me. If someone can point me to other documentation or anything helpful I'd be happy to try it again.
Sort of, it still runs under X fyi My rough process: check the repo of whatever you're packaging to see what language and tooling it uses read the nixpkgs manual for the language and tooling that you're building with find examples of other expressions in nixpkgs that use the same tooling to get an idea of the structure use something like to generate the boilerplate for the expression , get an error, use to find the required dependency (repeat this step until there are no more build errors) submit PR


Applications are starting to allocate more times than allowed by the default value of vm.maxmapcount, . For instance, this situation arises in applications such as Ryujinx () and newer Windows games like Hogwarts Legacy (). SteamOS has already addressed this matter by augmenting the aforementioned value, while Fedora intends to implement the same modification in Fedora 39 (, ).
Please feel free to send PRs, it's hard to track those issues as you don't mention any owner.
The line to add is: The questions are: How big should n be? ? ? In which file should I add it? At the bottom of
You mentioned other distros were thinking about bumping it, let's follow Fedora lead In the relevant file, a quick grep shows indeed that sysctl is one of the best candidate. :)
For the policy discussion: I'm all in favor of doing this soon(m). It is not really dangerous and as people have explained to me the previous default has been there for historical reasons and 32 bit systems.


Originally spotted by (thank you!). Steps to reproduce the behavior (assuming and are both ): The environment variable contains semicolons and must be quoted, otherwise bash will interpret the semicolons as command separators.
- Hey, I am not sure how to clean up the mess I just made on . Really embarrassed. I intended to rebase and hit merge instead, which pulled in 10k changes.
No worries, Happens to everyone at some point :) Personally, I'd just open a new PR.
Here it is: . Does the commit history look clean enough? I'll try to rebase it later, but I am concerned about retagging all of those folks.
I'd say don't worry about it -- as far as best practice goes, I'm actually not sure what's recommended for commits. do we recommend squashing before merge? I know I typically just do force pushes to avoid any commit history :l
I went ahead and squashed, and I'll post a nixpkgs-review when it's finished.
I don't think we have an official stance on this. Contributors use their best judgement for whatever keeps the commit history simplest and easiest to use


the sway test is flaky, both because ocr itself seems to flaky and because ocr seems to be very slow. Steps to reproduce the behavior: a couple times, we haven't gotten it to work even once this seems to be blocking nixos-unstable channel updates. there are a number of timeouts in the hydra build logs that we can very clearly attribute to either ocr not working, or ocr timing out because it gets only one shot at finding the gpg prompt (and if that fails, loops forever on the empty desktop).
I found it failing quite reliably, exactly since merging the .
scrolling throug hydra logs it's been flaky before too though, something is definitely up. there's failures in early may that look exactly like what we see now
Where do you see this? Looking through I only see successful builds (apart from the cancelled builds and dependency failures). I also don't remember it ever failing when working on it. So this definitely seems to be a regression from staging-next (either it just causes issues with (some of) the OCR tests or it can even affect users - in which case it would be very good that the test is failing). Unfortunately I don't really have time to look into it right now (maybe Thursday or Saturday). It could be due to a font rendering regression. Hm, that's strange - the GnuPG pinentry-gnome3 passphrase prompt shouldn't disappear automatically / after a short timeout (if that's the case than we definitely need to change that part).
Both and failed consistently at this point: So it looks like either doesn't start when using the Wayland backend or the font rendering is broken then (with the X11 backend (XWayland) the test succeeds).
Some of the “cancelled” builds are cancelled due to it timing-out, e.g. and ; the reason there may be unrelated, though. Indeed most appear to be non-timeout cancellations.
run locally here the things the tests wants to happen did always happen, but OCR was incredibly flaky and either did not detect them at the first try, or not at all. this is especially bad for pinentry because it closes after 10 seconds for reasons we have not dug into. it looks like this is squarely a failure of OCR (and the way it's used here does seem at least somewhat suspect, maybe using other tooling to list windows would be more appropriate? would almost certainly not take three minutes per attempt to find a window)
Ah, right, thanks for the examples :) Indeed, that seems to be to the gnome3-pinentry timeout that I wasn't aware of (so that part would be fixable). Weird, that shouldn't happen. OCR is slow but should be reliable. Not sure if this could be setup dependant. On Hydra it doesn't seem to be an issue. That is indeed bad. Luckily already found a solution for the timeout in . I intentionally chose OCR to ensure that the (font) rendering works but it isn't required for ensuring that the windows are there. The slowness of OCR is certainly a drawback though.


Project description pyenv lets you easily switch between multiple versions of Python. It's simple, unobtrusive, and follows the UNIX tradition of single-purpose tools that do one thing well. It is a critical application for Python development. Metadata homepage URL: source URL: license: MIT platforms: ALL


Spideroak GUI does not work in NixOS unstable. When running , I get this error: As far as I am able to tell, headless mode runs fine. Install spideroak and try to run . System: 17.09pre102667. (Hummingbird) Nix version: nix-env (Nix) 1.11.7 Nixpkgs version: "17.09pre102667."
Python uses the default zlib which is currently 1.2.11. I see the following options: override Python expression and use an older version of zlib let spideroak use our version of libpng. cc
Well the package's approach is strange to me. It installs private versions of libs that depend on libs not installed (e.g. freetype), and at the same time, some of the missing libs naturally depend on libs that are also installed privately (on zlib, for example). You can try such tweaks to find what will work now, but I'm afraid it's likely to remain fragile.


Project description A fork of Golden Dictionary which fixes many old bugs, provides improvement, and is being actively developed. It might be better to switch to altogether instead of continuing to maintain . Metadata homepage URL: source URL: license: gplv3 platforms: linux
doesn't seem too inactive now: they even had a new release last month (based on Qt WebKit, though).
I think it might be a good idea to have both versions as provides extra features and bug fixes if that's possible.


reaper can't export video (wrong ffmpeg version) in nixos 23.05 Steps to reproduce the behavior: the package reaper -Render : "Video (ffmpeg/libav encoder)" is missing There should be an option in the list where you can use ffmpeg as encoder If you override the ffmpeg dependency with: (reaper.override { ffmpeg = pkgs.ffmpeg_4-full; }) then it works.


Package name: ultrastardx Latest released version: Current version on the unstable channel: 2021-04-03 Current version on the stable/release channel: 2021-04-03 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.


Steps to reproduce the behavior: davinci-resolve Uh, also while checking, in the source link for davinci-resolve points to instead of Please run and paste the result.
I tried building off of and it seemed to build fine How are you building it so I can try to replicate the issue?
I updated my home-manager flake, and the reported commit hash it now uses says its from 2 days ago so I just have to wait then. Thank you.
According to the PR tracker (), the PR behind is available in But when I try to use it using: ( is currently at ) I'm getting the same error, do I need something else to try it?
I just ran your nix build command without error. What version of nix are you using? Also can you put more info about the curl error you're seeing? Just want to make sure its the derivation and not nix being the one throwing the error. I figured I would try too but that seems fine also
I was also on Nix 2.15.1, testing with 2.16.1 give the same error.
When you have a moment can you post the full build log -
Adding an echo of the resolved url immediately shows the issue: And the log is: Maybe the registration payload changed?
Running into the same issue and error message myself
Yeah, is right. Even the where a lot of this is source from is suffering from the same error. Trying to see if I can get it to work rn, stay tuned
Ah, they a street requirement for the form haha. Im going to set it to the chamber of commerce in Utrecht since thats where the Nix foundation is registered
Should be able to build off of:
Now I can DL the sources, but uncompressing fills up the build folder and ends in a error :/ (which is seemingly not catched as the execution seems to follow afterward) I tried setting to a folder on a partition with lot's of space without success :/ Do you know how to avoid this? <details<summarydf -h</summary</details
Honestly im not sure. Checking my it looks like the source is about 3.0GiB So it filling up your at makes sense.. Reading up on some other issues I think this might be what you are looking for if you are on NixOS, just adjust the tmpfs size larger than the default 50%:
Thanks, I confirm that works, I can build davinci-resolve (now I just need to find a suitable GPU.... )
I tested 's patch to the package, and it wasnt working for me. I found out that the Host for the second curl request to blackmagic's download site was mismatched, so I updated the host to their new site and also updated the street address to the actual location of the nix non-profit (found on the KVK's business lookup). I've tested on all (3) my machines and it builds successfully so if anyone else here would like to try, that would be great. Heres the PR: And my fork is at #davinci-resolve
Just tried rebuilding today and having the same issue. Looks like blackmagic moved back to the host and have blocked Maybe we should just remove the host header entirely from the curl command? If we are having hashed outputs verified, then it wouldnt matter which host it comes from?
Yeah, sounds like they may be doing some sort of canary release for new infrastructure or something. I agree, that makes sense to remove it.
Should I submit a new pull?
Sure! Ping me and Ill give it a review. Thanks!
New PR at
This issue has been mentioned on NixOS Discourse. There might be relevant details there:


Package name: MuseScore Latest released version: 4.1 Current version on the unstable channel: 4.0.2 Current version on the stable/release channel: 4.0.2 Notify maintainers Note for maintainers: Please tag this issue in your PR.
Thanks for the notification! Your review is welcome at .


Project description Language Server for Perl Metadata homepage URL: source URL: license: artisticlicense2_0 platforms: unix, linux, darwin, ...


I've been trying to see why vscode had rather laggy scrolling and high cpu usage when scrolling on wayland with set to 1, and upon discovering and , I saw that the library isn't found by it, causing the app to fall back to software rendering. Disabling the env variable and starting vscode like that shows that on xwayland it does start up with gpu acceleration. Doing the same thing described , VScode does start with GPU acceleration working. and no longer complains about the library Steps to reproduce the behavior: VScode with set and with the flag, so it starts with wayland support and outputs details about the startup and other stuff how it complains about the library. to see check that it's indeed using software rendering. The library is found, there are no complaints, and GPU acceleration is enabled. I am on an Intel laptop. Please run and paste the result.
Whats the exact log? vscode vendors that library and it is located in our package at
Relevant lines from [(44)] Failed to load GLES library: cannot open shared object file: No such file or directory [(186)] Exiting GPU process due to errors during initialization [(44)] Failed to load GLES library: cannot open shared object file: No such file or directory [(186)] Exiting GPU process due to errors during initialization
Same error happens on VSCodium where running with on Wayland frequently crashes on startup. ing yields a lot of lines before the logged error, including this particularly interesting one: The file doesn't actually exist, only does, so apparently VSCodium is looking for while only is vendored. If is to the , is found as a symlink to the actual library and ing again confirms that this library is loaded by VSCodium. Edit: Adding to fails with different error messages, so probably there's something broken with the vendored library:
I would guess that's because the drivers to not abi match. I would recommend to rm the vendored shared object and symlink libglvnd to the correct location. Also we should investigate if we can remove/replace the other vendored libraries.
Adding to the library path did the trick for me, thanks!
I can't get it to work with vscode sadly. vscode = (super: { libPath = lib.makeLibraryPath [pkgs.libglvnd]; });
How soon will the changes get into nixos-unstable?
2 days max ?
You can follow the PR here:
This is still broken for me: In fact, that file is missing. is missing too. As expected, due to last PR merged. I can confirm that the wrapper script contains: So what gives? How did this work for others but not me?
I'm guessing the last PR fixed it for wayland/ but broke it for others? Edit: I can confirm that I have gpu acceleration when I pin vscode nixpkgs to which is the parent commit of . I also tried the following, linking libglvnd's libGLESv2 into vscode directory. The error changed and terminal rendering completely broke with a black screen:
please open a bug !


Self hosting server for Rust Desk remote desktop the rustdesk client app is available, but it would be great to be able to self-host. Metadata homepage URL: source URL: license: GNU AFFERO GENERAL PUBLIC LICENSE platforms: linux, windows, mac, android, ios
Wow, that was speedy. Thanks!


Project description An unofficial GoXLR App replacement for Linux, Windows and MacOS. Metadata homepage URL: source URL: license: MIT platforms: linux
Moving conversation back here to avoid spamming goxlr-utility maintainers :sweat_smile: I made a draft PR that you can find from It's closer to what the official .deb and .rpm packaging is doing, i.e. including some of the relevant resources, shell completion etc. I wouldn't mind adding you as a maintainer but to do that it probably requires adding you to the maintainer list as well. Should be easy to fix if you want to add PR to the branch.
Hey wow you are fast :D Yes, you can add me as a maintainer for this package. But as I understand it, I need to add me to the maintainer list first, right?
Hah, had some free time during the night and since I wanted to get my GoXLR setup working anyways thought I might as well sort this out. For the question: Yup, the requires to be on . The file itself lists the mandatory/optional fields in the metadata, but basically "a name and at least one contact/identity information" (e.g. a github id). Oh, and the list needs to stay in alphabetical order ^^ Feel free to make PR against this branch, I'll merge it as soon as I notice the PR :)
Added the module to the PR as well. I guess it might be hard to wait for someone with GoXLR to come in and review the PR (though I'd prefer someone to check that it doesn't violate any major guidelines) so if you don't mind I think it's possible for you to try it out and do a PR review, which likely speeds up the process at least :)
Managed to get the PR reviewed and should now be code-wise idiomatic enough to pass. I think based on the main thing remaining is getting thumbs up from you functionality-wise so that's it's not only "works on my machine" :sweat_smile:
I saw your PR and tried using nixpkgs-review to download it to my local machine and try to run it. I used these steps: Do you know if my approach is wrong? This is the first time I've tried a Nix PR. Unfortunately, I haven't found much information about it. EDIT: Got it working
Glad to hear you got it working! :) The nixpkgs-review tool seems nice, hadn't used it myself but for building the PR it seems to do exactly what one would expect. I guess in this case there's a limit what it can do though as the udev rules are being on the module side and it probably doesn't handle that so some manual work is required :shrug: But again, all is good since you did manage to test the build!


Another Problem:
patch welcome !
in , the call to generate completion should be moved to before the wrapping. And it should be called for luarocks-admin too thanks for noticing. Let me know if you wanna do it.
If u wanna test


A CLI program that renders Markdown timeline as HTML Announced: <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ...
Since upstream has a this should be pretty simple using .


bunx is missing in the bun package. - command must be present. - Please run and paste the result.


Package name: expressvpn Latest released version: 3.52.0.2 Current version on the unstable channel: 3.25.0.13 Current version on the stable/release channel: 3.25.0.13 Notify maintainers Note for maintainers: Please tag this issue in your PR.