{"_id":"doc-en-nixpkgs-451cab574cc9604bc25a466d5ad6197d77eaf3bdd7635fc351b5f0063a70ef0f","title":"","text":"I am new to nixos... When I try to use printScr Key on keyboard. it not responding. non of the printScreen optins working.. Steps to reproduce the behavior: ... press Key PrintScr ... ... Should take a screen shot ask for location to save to. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.\nI am not too sure but according to the , cinnamon does not have a \"native\" screenshot tool but gnome-screenshot could be used. I am not too sure if enabling cinnamon auto includes gnome-screenshot. If it doesn't you can just add it and see if it solves your problem."}
{"_id":"doc-en-nixpkgs-d9a33bad1cb2c4531fc66b7125ef13adfa638e5653c165d3dc66f35cda9b466f","title":"","text":"I have user-installed Cinnamon applets, desklets, extensions, themes, which have been installed in the home folder by a different OS (as far as i remember). Many of them work under NixOS (some do not: ). However, i cannot update them. When i try, i get the message: The same happens if i try to install a new applet. Steps to reproduce the behavior: up Cinnamon desktop on NixOS and log in. to install an applet. Should be able to install and update user-installed applets, desklets, extensions, themes. ! I am just beginning to switch over to Cinnamon from GNOME 3 (having been fed up with GNOME, especially under NixOS).\nInstalling [][gettext] that provided solved the issue. Shouldn't be a dependency of Cinnamon desktop then? [gettext]:"}
{"_id":"doc-en-nixpkgs-223cef7c22aa61065d81adbd18cc512bba5549a667251b389b0a127cf6c9835f","title":"","text":"Describe the bug building the package fails. To Reproduce Steps to reproduce the behavior: and wait Expected behavior Successfully building swift to be used. Notify maintainers Maintainer: Last 4: … Metadata Error\nSeems as is used for building rather than . Probably happened during experiments to declare . Apart from that I'm not a swift maintainer, so if the issue is more complex, I can't help I'm afraid.\nI think the Python warning is actually benign. I see a build error related to a change in the handling of . Commit appears to break it for me. I can offer a , which you can try like this: But I am not sure what the proper fix is. I would like to ask for comment.\nI have pushed a new fix to my . This uses the proper fix as suggested by It would be nice, if someone can confirm it works. I have also opened PR with this fix."}
{"_id":"doc-en-nixpkgs-d1a02ea7952c941bfbfebdac5c41d0e473bb9ac28f81c4b47858e9f0d59145b7","title":"","text":"Project description Formatter for rst (reStructuredText) files Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin, ..."}
{"_id":"doc-en-nixpkgs-ec41fca4432cd870f5a0c5ce983796b821d16975477176673efef1063f917ea5","title":"","text":"OpenSCAD seems to be built without support for PDF exports. (This is a very useful feature to print projections on paper to check the dimensions of a design for example). Version: OpenSCAD version 2021.01 On nixpkgs: master (2022-09-18) Open OpenSCAD Go to File -Export -Export as PDF… Save to some file Observe the following error in the OpenSCAD console: CC package maintainers:\nAny idea what dependency they need for PDF? (image file export has been enough for me so I never looked)\nI think cairo. (I was looking into this earlier today.)\nYes, cairo was missing:"}
{"_id":"doc-en-nixpkgs-4a3c6189e5d1d387adbf5134af3d69535c71bc6dae70796d526d19c4125113e8","title":"","text":"Describe the bug Running fails with To Reproduce Extra info On of that script scopeoCmd isn't called correctly. Seems like introduced the problem in this PR"}
{"_id":"doc-en-nixpkgs-2273bc5198fe9d09243e56c93bfc55a3b191530a572f22968cb9eebf7a48c3ed","title":"","text":"\"ownCloud Infinite Scale Stack\" or owncloud rewritten in Go. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: asl20 platforms: unix\nThere are some hassles to deal with on this one. PNPM usage: Image assets downloaded with curl (and no hashes or revisions) Code generation tools and code repositories downloaded by\nNote that ownCloud provide prebuilt binaries for oCIS. It's fairly simple to get these working on NixOS: Perhaps this can be used as a temporary solution until we can build it ourselves?\nI used your derivation and opened . I tested it a bit, and will work on a proper module over next few days/weeks, can you share if you are already using above derivation, and if yes, how stable are rc releases?\nI've been using the rc for a while and haven't had any major issues. It's probably better to go with the stable release by default though. Perhaps we could package both?\nHas the situation changed where the OCIS can be built from source now? I'd rather not use a proprietary binary."}
{"_id":"doc-en-nixpkgs-8a1c6ae106e8db119aef0432a222f7254e2d237cefe07c6e3dfd78ba39f1fc52","title":"","text":"Configuration snippet like this: yield a configuration like: However nbd-server expects section to always appear before export sections, otherwise it complains about not being able to find general section. I'd say this is upstream's fault because this order should not matter, but here we are. section to always appear before export sections. <!-- 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.\nThis looks like it should be easy to fix. I'll probably get around to it tomorrow morning.\nFor reference, the error looks like this:"}
{"_id":"doc-en-nixpkgs-3d383d756599a96b799426e2a72c2e0d7a88670b2221ff42bbd7fe466456b82d","title":"","text":"Project description Neofetch like tool that can lookup IPs. :earth_americas: Metadata homepage URL: source URL: license: gpl3 platforms: posix shell\nI'll do this myself."}
{"_id":"doc-en-nixpkgs-75c1d393b74b29f186ac9b604f809b10b3071452308074024f0e7f8b5f4f0133","title":"","text":"When I update nix I can't copy to our binay cache anymore. All I get is I bisected nixpkgs and found that the bug was introduced by . Run The parent commit works: This error here is fine because our cache has a different name of course. Please run and paste the result.\nJust wondered if here is the right place for the issue but I’m quite lost on this. Maybe this is a nix bug?\nNo you're correct to open this here, this is a good place to start. I'll try to bisect further to see which aws-sdk-cpp commit broke this functionality, hopefully that will tell us more about how to proceed.\nBisected to , but unfortunately the commit is very large so I don't see an obvious cause. Maybe it's best to take this upstream to the Nix repo now.\nThanks for reporting, and sorry if this broke your workflow. I've bookmarked this issue and I'm going to look into adding an installCheck regression test to ensure s3 stays functional on future updates.\nThank you all for the quick response. This was a really sneaky one. Luckily nix allows rollbacks. That would be great. I’m sorry I cannot think of anything better than checking the error message of . When I do I let you know."}
{"_id":"doc-en-nixpkgs-e87139c77f8d56b847076ec94c446b985f2cfb2b44a4dd1f7a45a3d3f9b93fb0","title":"","text":"I have installed a very barebones server with NixOS. Whenever I run it shows the following warnings: I get that it does not matter that much which of these are used, but it makes these commands not very transparent. Why is being used from and not , while is apparently part of ? Should we make sure these packages will not both be part of or should we make sure the files are only available in one of the two packages? up a minimal version of NixOS. the log\nThese are usually fixable by just setting priority values. coreutils should probably have a lower priority as they are usually cross platform but not as many supported features. The getconf and getent are interesting because they are actually symlinks to glibc. But we might as well make unixtools lower priority as well.\nIs this something we should do nixpkgs-wide? Will that avoid the warning messages? I was thinking why these are providing the same files and why both packages are being used. For instance, do we really need openresolv or is that included unintentionally? The priorities is a way to solve this safely, but I feel like there shouldn't be any conflicts for the base packages at all.\nMaybe openresolv we can leave out of systemPackages. But, some of these collisions are kind of unavoidable. We need both procps and coreutils even though they both provide kill bunary. It might be interesting to see which other distros use but IIRC they are almost identical\nFor coreutils, ArchLinux seems to leave out the kill binary: This also feels a bit wrong, as it isn't the original package anymore. Changing the priority does indeed sound like a better option. Coreutils should have a lower priority.\nI tried giving coreutils a lower priority, but it doesn't seem to have made a difference for those warnings.\noh it already has lowprio: but it doesn't really work when everything has the same priority.\nsystemd-resolved is not enable by default so resolvconf shouln't be really pointing to resolvectl. I think the dummy command provided for compatibility doesn't work correctly if resolved is not running and dhcpcd needs it to configure interfaces.\nShould we just give openresolv a higher priority than systemd?\nYes, correct."}
{"_id":"doc-en-nixpkgs-7a533f7094d5554de168cbf34e65f916e73b5ed3dd23cf2ad4024b8b1ada7707","title":"","text":"The dhcpcd resolvconf hook check if resolvconf is installed and, because the command is in the PATH, it won't fall back to writing directly but will attempt to execute something like this: echo 'nameserver 10.0.1.1' | resolvconf -a wlan0 Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.\nReproducible way to see these collisions: With a file set to I ran in the (the latest commit on the branch), and I get these collision messages:\nping\nHi all nixos-version 03. (Koi) I have the same collision on kill gnutar resolvconf but also on collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/64x64/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/22x22/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/16x16/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/scalable/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9."}
{"_id":"doc-en-nixpkgs-0c0286ec4a376d984d7b5e58af7caf1173aa279a3886f9473695e83b4bea7318","title":"","text":"0/share/icons/hicolor/48x48/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/128x128/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/64x64/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/22x22/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/16x16/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/scalable/apps/phonon-' collision between /nix/store/mrfyscriilpbyqvnfpgwa87ly4hky3jr-phonon-backend-gstreamer-qt5-4.9.0/share/icons/hicolor/48x48/apps/phonon-'\nThis seems to include many more collisions than related to this issue.\nMaybe rather than changing the nix-env priority, a better solution is to remove some of these programs (e.g. delete in util-linux's ).\nThat seems hacky to me. What if you want util-linux's version of kill? Presumably if the maintainer thinks it's worth including, someone has a use for it. Nixpkgs shouldn't be making these decisions at the derivation level. Something like meta seems ideal because you can change it without effecting the derivation.\nSince and were merged, does that mean this issue can be closed now?\nI think so, I don't see these collisions anymore.\nLet me know if this isn't fixed after all.\nsorry, but i see these collisions."}
{"_id":"doc-en-nixpkgs-b96b372ef1cf0d291944b721f81d54dc023a050bb1e4a78b2669f5c4b7ab3c32","title":"","text":"it's a different issue: it seems you're installing both the wrapped and unwrapped version of the same packages. I'd say there's something wrong with your configuration, but if you think otherwise open a new issue."}
{"_id":"doc-en-nixpkgs-58bc82587b05d8ab6f9751ba00c1203544440411387654478311769a2571be30","title":"","text":"Package name: wasm-bindgen-cli Latest released version: 0.28.4 Current version on the unstable channel: 0.2.84 Current version on the stable/release channel: 0.2.84 Notify maintainers and I'd really appreciate an update it's causing me problems with a trunk build similar to Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-ff0e7b11df9136b17ef7cd18ce0ca1f0f608664b604cd31272327fde2be33887","title":"","text":"The package (and the related ones) don't offer completions, only Npm's. At least for bash Node offers it through . I'd like this bash completion to be . Install Node, see that there is no completion in the completions dir (I'm using home-manager, so that'd be ).\nFixed by"}
{"_id":"doc-en-nixpkgs-26eafa341055a96be439ed731ae42169101ceda928b6ca6cb816857128698109","title":"","text":"none Please run and paste the result.\nI started to bisect this with at nix started to download ~4GB of derivations and I aborted the process. The is\nit seems like the issue already got fixed upstream in but there is no new release yet. We either have to target commit which contains the fix, or wait for the new release.\nyou are right, pdfpc/pdfpc fixes this. I tried it with this patch on nixpkgs:"}
{"_id":"doc-en-nixpkgs-be49301a1c0fa1324defcd43e2652a8fec86711d2562f0e92b9e72d5e06f30d3","title":"","text":"Describe the bug I copied a closure from one system (19.03) to a USB thumb drive and from that to another system (19.09), but the program don't work. I think nix packages should be pure and work also on another system running a different NixOS channel. (Right?) To Reproduce Steps to reproduce the behavior: sweethome3d installed in thumb drive thumb drive (i use pantheons files app and open a terminal from there, then ) a folder on the thumb drive. mine is \"nixpkgs\" to that folder: the nix store path of the program: the usb drive into another system and mount it, get the path the nix store path to your system: you can install it for the current user if you like: or just open a nix shell: run the program: Expected behavior Program just work. Additional context I moved to a new flat with most of my computers and want to plan where to put my furniture. I installed sweethome3d on my notebook, but it is not powerfull enough. So i want to copy the program to my iMac. I have internet from my tethered mobile phone, so i can't just install it from the internet! sweethome3d is about 500 MB, that would be 1/4 of my data plan!!! Metadata X230: system: host os: multi-user?: sandbox: version: channels(davidak): channels(root): nixpkgs: imac: system: host os: hangs after that Maintainer information:\nLooks like this problem again: cc\nWhen i run the package from unstable on stable, i get the same error: (but it will hopefully work on the imac when i copy it there again)\nI get the same error when i run the package from unstable on my 19.09 branch. So it might be generally broken on unstable.\nYes, looks like be some kind of impurity. It runs on my NixOS 19.03 system, both from the stable and unstable channels. And I did the \"nix run\" thing you said and it works there too (I'm not sure how much isolation gives, apparently not enough)."}
{"_id":"doc-en-nixpkgs-c26cfdd1b4cf87eaad1aaf8447559db180f072fe2611a92cd762dabe437f05d4","title":"","text":"It looks like the program copies some so files to on start-up: Two of the programs match to libraries in the but I could not match the other two; also I do not have the same filenames as you. Not sure what libraries’ RPATH should be patched but perhaps adding the following to wrapper would work as well:\nFor the reference, the libraries loaded are listed here:\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on ."}
{"_id":"doc-en-nixpkgs-715e282baa50adcc5941a0fa30bcffd9fbaa7953cad9ae694e6191b8fcf0814c","title":"","text":", CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc"}
{"_id":"doc-en-nixpkgs-a7079e198aca988098951b4fa76cc9c83dc618ebe0d3503c23f6bfa32d8f7208","title":"","text":"Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -\nThere is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?\nThe package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.\nI think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.\nSee as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.\nCan you provide a list of packages that need updating?\nBased on a quick grep: pkgs/development/tools/build-\nI believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)"}
{"_id":"doc-en-nixpkgs-271cc78d174da36f32a4a2d69e23cae5ba269e47da0ad532cbc0947ea64afa0d","title":"","text":"Source no longer apparently available from upstream website. They recommend using pypi. Attempt to build , as in :"}
{"_id":"doc-en-nixpkgs-a2208ba5659daaaabe5723e3ff15318bd4e1fbb7ac5c248ef8fbb4e919cf7b90","title":"","text":"Project description A simple server for sending and receiving messages in real-time per WebSocket. Includes a web UI, also has an Android client for receiving notifications and an optional CLI program (distributed separately) for sending notifications. Metadata homepage URL: source URL: license: MIT platforms: anything Go runs on\nI started an attempt locally, however it failed due to some timeouts while fetching Go dependencies... will retry during this week :)\nI think the main difficulty is the UI, which needs to be compiled with NPM. In essence, I think the build is three-staged: fetch UI dependencies, fetch Go dependencies, do the actual build.\nYou may want to take a look at ."}
{"_id":"doc-en-nixpkgs-9f8d973790633895f03ad38a4f631455a31557eec5a27e134b30bdf71fed07df","title":"","text":"The ssmtp program is dead/unmaintained. The commonly suggested substitute is msmtp. While [home-manager has a module for msmtp][1], NixOS lacks one. [1]: Let's: [x] Done in We should probably also: [x] Remove the ssmtp NixOS module and add migration instructions to the release notes () [x] Remove the ssmtp package ()\nI marked this as stale due to inactivity. &rarr;\nThe module works really well. Thanks for the module"}
{"_id":"doc-en-nixpkgs-777348a90017a07a7256e52c4e04bea8f69f252116fc335d27cb71f122cb95da","title":"","text":"Mainline / hardened / testing / ... kernels can be painlessly modified via : Sadly, this does not work with a bunch of other kernel variants: All kernels should honor I am not entirely sure how dynamic binding is implemented in kernel stuff, however slightly changing xanmod parts this way seems to fix : zen and lqx look similar to xanmod, no idea about libre Pinging people who seem to update affected packages often Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nsame underlying issue as it seems\nCan confirm that this patch fix the issue for zen and lqx kernels:\nhave you submitted these changes as a PR that I can review?\nsorry for the late response. I created a new PR with this changes.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-8d5c740bdb78d6c578a989c0f7616fe42fbc3923340ef85ecdfc027a30955794","title":"","text":"Looks like it now uses .NET 8 which probably made all existing plugins incompatible - Package name: ArchiSteamFarm Latest released version: 5.5.0.11 <!-- Search your package here: --- Current version on the unstable channel: 5.4.13.4 Current version on the stable/release channel: 5.4.12.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThe package/module has no official way to use plugins, so there is no way to use them unless people are using overlays which should be constructed in a smart way to re-use the same methods as archisteamfarm does. Anyway, here is the update"}
{"_id":"doc-en-nixpkgs-145f84e70c85b75197420fec78efc6cf98f4f5090b43f464c5a76c42dfcf9fe6","title":"","text":"Project description This flag is available in most other major distros. It is necessary to enable screen sharing on wayland inside of chromium, combined with xlr-desktop-portal-wlr and pipewire. It requires the build flag and a dependency on libpipewire02. See as an example. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...\nthat would definitely be nice to have :) I actually also noticed this but unfortunately cannot test this easily as I'm not using screen sharing. If you could contribute a PR that would be awesome (but be aware that Chromium does unfortunately take quite some time to compile). Alternatively (but less preferably) we could make the required changes with the next update and test the core functionality (as always) and you could test screen sharing after the new version is available in the binary caches. Additionally we would need to package in Nixpkgs to make this work on wlroots based compositors. On Gnome/KDE this might work out-of-the-box, but I don't know what they currently implement/provide.\nwas just merged w/ . I'll try building chromium w/ the flag - as you say it takes a while, so I can leave it overnight and give it a shot.\nhow does the situation look like with ? Is the flag available there, as in, screensharing with wayland already works there?\nyes, it's available in google-chrome. ! I'm still trying to get it to work with xlr-desktop-portal-wlr - I've done this in the past, but it's not working out of the box yet with\nAnd just to make sure, you also did set as described there?\nyes I did. I'm almost got it working I think. There are a few issues out of the box: -chrome is missing the pipewire 0.2 runtime dependency, so I it as (I'm on 20.03 so pkgs.pipewire is 0.2): .pipewire service doesn't work - it doesn't seem to be setting up the path correctly. I'm trying to fix this now: My current config on 20.03 looks like: Where is the same package that was recently merged."}
{"_id":"doc-en-nixpkgs-7ccd36625602dcfdb3a12985933672f8e2d341077e5da484385887c02b0d4bbd","title":"","text":"yeah, I'm currently already looking at it - pipewire wants to execute , but it's not in . We can patch to contain the absolute path. I'll check if it works and will get back to you.\nBtw, we /really/ need a sway NixOS test, and better documentation on how to use sway. I was trying stuff until it worked, and does autologin me into a sway, but there might be a smarter way to do this, without also starting X.\nThe sway recommendation is to just run sway from the terminal after login - that's how I do it at least. I was able to workaround the environment issue by doing (but this is a kludge I think and shouldn't be necessary). But unfortunately it's now crashing and I'm not sure why:\nYeah, even my sddm config I also had to , otherwise pipewire complained about not being able to reach dbus: Afterwards, it segfaulted, as it wasn't able to find ; I patched to be able to find the path to , and that error message is gone. Now (apart from not being able to find bluez or rtkit) it /might/ only be some version incompatibilities, not sure: I'll see if I can get as far with your chromium PR, will merge that then, and also submit the pipewire patch.\nOkay, with the pipewire patch and , It seems I'm able to share at least my own application window :tada:. I don't know yet why the alacritty window nearby isn't shown, and why \"Entire Screen\" is black, but that's probably due to me running sway inside X via ssdm.\npipewire PRs:\nI don't think you're using pipewire in that case. xdg-desktop-portal-wlr only supports full screen sharing atm. If it is black that means it's not working. By the way I had to add pipewire02 to my system packages to prevent xdg-desktop-portal from crashing. But now there seems to be some incompatibility in the pipewire service logs when chrome tries to connect:\nyou should be able to cherry-pick the to not have to manually add this to $PATH.\nThanks! I'm suspecting google-chrome is compiled with a too old version of pipewire."}
{"_id":"doc-en-nixpkgs-4c6dd215a406a5a8cb5db72b0dde002afd7c69cb2eb16addaa4c985d69bb41dd","title":"","text":"Enabling pipewire debug logs, it seems to be sending an incompatible format to the pipewire server (similar to ). I have got this working with chromium compiled against pipewire 0.2.7 in the past, so I'm pretty sure it should work assuming the client library is recent enough. Once the chromium package has that flag enabled I'll try to retest.\nI just confirmed my last comment by building chromium locally w/ rtcusepipewire=true. It works perfectly for fullscreen sharing.\nHmm take that back - it worked the first time but not anymore :/. Not sure what lib is missing where.\nSeems like xdg-desktop-portal is crashing:\nThis might be yet another version incompatibility problem. I propose merging (as it's built with 0.2 everywhere else too), and then see if we can get it to work if the system pipewire also is 0.2. I asked upstream about these problems in - maybe 0.3 needs to support 0.2 clients for some time until we should switch.\nHeads-up: the bad client situation should have been fixed with the latest pipewire release, PR at\nThanks for your help! I'm still getting the xdg-desktop-portal crash, however. I'm guessing there is something missing from my dbus environment - or perhaps it's trying to access a file/directory not available in nixos.\ncould you open a new issue with some more details, like logs etc.?\nOkay, I made"}
{"_id":"doc-en-nixpkgs-97d8924f10e6a56d52afb9e840cd06c42a6c1b80c9b8b068b5c08e2e0bf626ea","title":"","text":"Freenet installs successfully but fails to run for both the service and the package with Steps to reproduce the behavior: Failure with Or alternatively with the service = true; to config For Freenet to start and be able to access setup wizard on 127.0.0.1:8888 Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-f98506825b595fd3ff1bc9dc83f153017251a54bd4785f7960ffbf3abf3a2f9e","title":"","text":"On today's master () - and probably others - building the attribute of many package produces an output that differs from the output on another architecture. Nix will display a hash mismatch. I tried with x8664-linux and aarch64-linux. Execute this on aarch64 and x8664. The aarch64 build produces the below output while x8664 is happy with the hash in nixpkgs. Please run and paste the results. system: host os: multi-user?: sandbox: version: nixpkgs: and system: host os: multi-user?: sandbox: version: channels(root): channels(andi): nixpkgs:\nx8664 build produces same output for me: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nI noticed something similar on macOS in Could some recent change have caused this? Perhaps ?\nI reverted in a branch on my fork. My x86_64-linux laptop doesn't complain about the hash sum - as before. The aarch64-linux community box also doesn't complain anymore. Can anyone else confirm this?\nI just made a diff of : The left side is aarch64, the right side is x86_64. Both are done on the same git revision ().\nWhat a weird behavior that is missing.\nProbably related:\nI think this may be related: I also see different hashes on NixOS 19.03 vs. stable. I use the branch, but when CI builds the derivation on 19.03, the hashes do not match. If I build on NixOS 19.03 with from master, the hashes do match. This is quite annoying, because it makes it impossible to have package sets that work on NixOS stable and unstable without using rustPlatform from a nixpkgs newer than 19.03. I'll try to revert and see if I get the same hashes on 19.03 and master.\nThat's indeed it. When I revert , I get the same as 19.03. Maybe this change should be reverted? Since NixOS is not a rolling distribution and people run both stable and unstable, it would really be nice if package sets and overlays work on both versions. This also makes backporting changes easier."}
{"_id":"doc-en-nixpkgs-bec270205f323fd2015087f3fde4d936318d62b4a00573925da9edaa783b9fc6","title":"","text":"Diff between the vendored dependencies: Here the differences also seem to be missing dotfiles (e.g. and ). I think this is the upstream PR that changed this behavior: (Edit: oops, I just saw that already mentioned the associated commit.)\nis a critical update and reverting it will break multiple Rust packages. Rather I think we should get that change pushed into the channel, and then update any Rust packages whose changes as a result.\nThe only bummer is that it also breaks people's own packages on the channel as well.\nYeah, it would be bad to break people's derivations as an update to a stable release. At any rate, the 19.09 release notes should probably have a blurb that points out that hashes will change due to changes, so that people who update from 19.03 to 19.09 are prepared. There are probably also derivations in that have incorrect hashes now, since the file that is generated by is now excluded vendored dependencies.\nI’ve updated the title of the issue to better reflect what I think we now know. Additionally, I’ve opened to update the hashes for all packages that haven’t been updated in master yet. I would appreciate a review on it. Once that’s merged, I can do the same thing for the affected release branch.\nLooks like I misunderstood and this hasn’t made its was into a release branch yet, so we’re almost done here. Somebody just needs to add the release note for 19.09.\nwith the changelog PR () being merged, is there anything else missing?\nDon't think so. :) Somebody can shout if I'm wrong."}
{"_id":"doc-en-nixpkgs-42ab45fcd210910749ba8d5deaf7a9d917158a9f5dc45f94bd0bd2dbf0301552","title":"","text":"Describe the bug The new version of Agda is working fine on other systems, but not NixOS. I've reported a bit more about what is known at To Reproduce Steps to reproduce the behavior: Agda 2.6.1 any file (e.g, ) Expected behavior Agda checks the file quickly and exits. Additional context Issue in the Agda repository: agda/agda Metadata Maintainer information:\nI believe that this is fixed by rework of our Agda setup ! (Which is included in the most recent nixos-unstable.) Can you confirm? :-) $ echo module Main where && time agda Checking Main (). real 0m0.132s user 0m0.104s sys 0m0.028s Looks reasonable!\nI haven't had chance to test the new stuff, but this issue probably should be closed anyway, as it's being worked on upstream (). I'm doing fine now using the workaround of adding option ."}
{"_id":"doc-en-nixpkgs-7e1995b296b17d46c821c111332fa5bd2fa6c17b9eb6ab997f9a3978f24da6c9","title":"","text":"Project description A Python-3 (CPython = 3.9.0) Interpreter written in Rust Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin\nI tried to package it here: but run into compilation failure:\nRustpython master builds just fine. PR in"}
{"_id":"doc-en-nixpkgs-92985bc3acb0613dfdf5a05bf9ffce0abdce2777b9a7bebb504487a722d847b3","title":"","text":"Describe the bug I encountered this bug when trying to use that does FFI. The particular call in general was the equivalent dlopen on the libc library and resolving to the system one which would cause a SIGSEGV. Digging into the source some more, you discover that Java sets a default value for if it's not explicitly set. Adding system libraries (i.e. /usr/lib) breaks/invalidates the hermetic invariant needed by Nix. These library paths are also searched first before those set in the DTRUNPATH of the ELF header as documented. I suggest the OVERRIDELIBPATH is either set to empty string maybe or even the contents of the ELF RUNPATH header itself. To Reproduce I was using JRuby which makes it easy to reproduce by using a gem which ultimately calls the JNR FFI. (The following reproduction results in the SIGSEGGV) Expected behavior Expected behavior is for the FFI call to work! This can be resolved by setting to the correct lib. NOTE: I could not merely set LDLIBRARYPATH because that would apply to everything in my nix-shell. Furthermore, wrapping java is somewhat tedious, seemed pragmatic for now. Notify maintainers Metadata Maintainer information: All JDK derivations\nIf you are curious for the JNR call that loads the C library:\nOVERRIDELIBPATH is not sufficient, because it still SYSEXTDIR/lib, which is somewhere in . We'll need a patch. This also means we might as well write C code to get the right rpath value, even when . Although less useful, I'd be ok with a patch that just makes it . At least that will give a somewhat useful error message instead of a crash. ~It seems like OVERRIDELIBPATH was designed for cases like ours. Setting it to a static rpath value is tricky because that way we're duplicating it in a way that can't be later. It a statically known value. So I'd go with the empty value.~\nI'm hoping (haven't tested) that with an empty OVERRIDELIBPATH the DTRUNPATH at least will be searched for. Do you want to work on this change together ?"}
{"_id":"doc-en-nixpkgs-b18d55610cdfefcb9164e6ba3ad7f64a93875b143cb2a0e8d947f049e8cb56ae","title":"","text":"I don't have a lot of experience yet with the JDK derivation (8.nix etc..)\nI don't have a lot of experience with that either, but I do implement RubberDuck and I'm happy to review Nix+Java ecosystem stuff.\nTagging who seems to do a lot of JVM Java work as well.\nReopening: more versions to be done\nI marked this as stale due to inactivity. &rarr;\n[x] OpenJDK 8: [x] OpenJDK 11: [ ] OpenJDK 17\nwhy does openjdk 17 not have a mr?\nDo you have a specific problem? With the example above I could not reproduce the jvm crash.\nsorry, i thought i was hitting this bug, but turns out that the bug i hit is different\nIs there a way to reproduce this issue for openjdk17? Otherwise I'd propose to close the issue.\nAfaict, it has not been written yet. You may not have the \"right\" libraries in to make it crash. I don't think we need a reproducer. We know that the unpatched behavior is bad, and it is highly unlikely that upstream's behavior changes, because the rest of the world depends on it. did you have a specific reason not to patch OpenJDK 17? Could you patch it?\nThat patch does not seem to be too complicated. I could prepare it, but I'd feel better if I had some use case to test if the patch is working.\nI mostly just forgot about it sadly. Some other stuff picked up and it kind of fell by the wayside sorry about that. On Thu, Jul 28, 2022, 2:19 AM Benjamin Asbach\nClosing since it looks like the last bit of this was fixed by . Happy to reopen if I'm mistaken."}
{"_id":"doc-en-nixpkgs-92b14e6173137c0a37b55493ebed2edffc15393ffbe0c79634a221cfd529baf3","title":"","text":"Data that was once config and recorded on doesn't get updated when the configuration changes. This is a violation of purity. And more than that, it's very surprising when trying to install, hesitating between pgsql and sqlite, and struggling before understanding that the configuration doesn't get used anyway :p cc\nthat's a bit tough. We have a unit, that's supposed to do the installation. We use the command to install nextcloud (passing the configured database and adminpass settings as command parameters). This CLI generates , and installs nextcloud. The script checks the presence of , and skips installation on following starts. If you now change configuration from the module, we won't run the install command again, as the config file already exists, and assumes nextcloud is already installed.\nHmm… Maybe it would be possible to generate the somewhere in the store, and symlink to it? This way the next time runs it can in addition check whether points to the correct store path. Now, I don't really know what exactly does, so maybe it's not actually possible to do this because eg. one would need to re-run on certain configuration changes? In which case it'd be hard :/ but at least we can maybe make fail or something like that, so that the issue is at least noisy?\nI don't recommend to do this, I just tried that (after upgrading one of my personal systems) and this tries to recreate a database schema which can end in very bad results. Unfortunately I doubt that this will work properly, nextcloud wants to merge this during the runtime. E.g. it adds a after a successful or adds trusted domains when running the corresponding command. I'm using this as well now and hitting these issues, unfortunately I don't have useful ideas either ATM, but I'm happy to discuss better solutions :)\nNextcloud edits it's in a lot of different places, so having it generated through Nix currently isn't possible. digs into that already, I a comments about our use case here too.\nto avoid other people running into the reconfiguration issue for now, what about documenting that, maybe in ?\nThat's certainly a good thing to do."}
{"_id":"doc-en-nixpkgs-c4e56eafb4795d6fe067848a15c32dddf2be7d2dfa8a8db4e6140162b43d60cc","title":"","text":"If nobody else wants to take over, I'd volunteer to do this during the next week as investing time on improving the nextcloud module is one item on my todo list :) I was aware of being stateful, but thanks a lot for linking the corresponding ticket! I'll have a look at this as soon as I have sufficient time to :)\nIn the light of this issue, what's the correct way to upgrade nextcloud to a new major version? Do I just pull a newer , upgrade my system and hope that the systemd job will do the right thing?\nThe service runs an that should apply all changes like database migrations needed for the new Nextcloud version (beware, downgrades aren't possible). As long as you let Nextcloud do its job, you shouldn't get that much issues. IMHO the actual problem here is the configuration of the software within Nix(OS).\njust a simple question (could not come to a conclusion after the lengthy thread) but I recently updated my nextcloud via nixops deploy and the update disabled the calendar module. Did I mess up or is that expected ? any way to configure this from nix ?\nAssuming that you installed the calendar module via the UI, it is installed in . The beginning of my config reads: So in principle nextcloud can edit the apps installed via the web interface (otherwise you couldn't install them via the interface in the first place).\nI don't think there's anything actionable here - the nextcloud nixos module is limited by how Nextcloud (imperatively) manages its configuration. The current state is properly documented in , and we raised our concerns to upstream in - closing this issue, feel free to reopen if there's more to be done.\nI think one actionable item would be to have the nextcloud service fail with an explicit error if the configuration being used is not compatible with the configuration defined in the .nix. At least the user would be warned in practice that configuration is not really applied, and not only by the manual that they are relatively unlikely to actually read. Reopening for now, feel free to reclose if you think that's not a reasonable “solution” :)\nThe problem is we don't know whether the configuration on disk containing database connection information () differs from the one that would be generated through an installation via - we don't render the configuration on our own, but the installer writes it out as a side-effect."}
{"_id":"doc-en-nixpkgs-e4cf0a48ca0407b14e74a8a4d6172973ee0007ab7182b6a4f2414eba4f2b1982","title":"","text":"If I'm not missing something obvious, checking configuration changes would translate to parsing/evaluating on every nextcloud startup as an , comparing every \"interesting\" key with the one provided through nixos configuration, and eventually then bailing out if they differ. I'm not sure if that's a road we'd like to go and keep up to date, while the underlying bug is a missing distinction between configuration and state upstream…\nSince upstream mixes state and config it's questionable whether their configuration format is somehow supposed to be backwards-compatible (as it's only supposed to be used internally by Nextcloud). Hence I'm afraid that this will make i.e. upgrades even harder in case of configuration changes, so :-1: from me. As the issues are documented in the manual now, folks are warned and I think that this is a better option in contrast to adding more complexity to . I suggest we either close this for the reasons already stated or wait for an appropriate upstream fix.\nI really don't feel good having stuff in that's actually a disguised command line… :/ Something that would sound nicer to me would be an executable that the user would have to manually run, and a bare-bones module that does not handle setup or configuration and just makes sure that the systemd unit is setup. At least the error is obvious (enabling the module without having run the executable would fail), all module options actually mean something, and the impure operation is made explicit. Either that or, similar to , rename all the options so it's explicit that they're used only for initial configuration. Would one of these solutions make sense to you?\nMe neither, but currently we don't have much choice… I really like the fact that we can set up the Nextcloud instance in an unattended fashion, without having to worry about manual setting things up. I really don't want to end with more imperative setup steps than necessary. In theory, we could move some of the options in to to make it more obvious what isn't applied continuously. But TBH, I'd rather like to see the state/config mixing fixed upstream than having to introduce more mental complexity here, especially if this gets fixed and we end up with both incarnations. Really, this issue only occurs while a user changes nextcloud database parameters (mostly while tweaking his initial setup), and not having read the module documentation, where the behaviour is documented."}
{"_id":"doc-en-nixpkgs-c18de52bf5cfd2a2f4ec3e5fa95428d955562611c8e8ba19985e2786aaf847a4","title":"","text":"What about adding the following (subtile) log statement, to point users to the docs when they peek into the logs while things are not working as expected?\nI agree that the log statement is the minimum we can do, and would at least give a hint about the way in which things are broken. Now, I guess the reason we're kind of disagreeing on the path forward is that you're much more hopeful than me that nextcloud will ever fix its stuff -- I'm assuming it'll get fixed in years at best (and even then…) -- and if it's in years then I'd much rather live with for years then spend a year deprecating it by making it conflict with new options than try to live with from now on and have users fail to understand what is going on. Now urhm, I'm investigating the module a bit deeper, and… is there any reason we can't put the database configuration etc. in ? We could then refresh on each activation, and it should be enough? If we have a way to couple it with something that automatically runs iff the database is not ready yet then the setup would actually be… almost perfect?\nAfter having a deeper look at the sources ( at github, (6 commits ahead of v16.0.0RC1)) I guess that this should be possible (I didn't test it yet though). Configs will be loaded from using PHP's function[1] while all files ending with will be taken into account. Hence works as all config arrays will be merged together. This config will be loaded at [2] and is available as which is then used in the DI container[3]. If I understand the code correctly, I assume that it should be possible to render all config options in as config files found by glob will override values from [4]. [4]\nNice catch! This might indeed be possible - we should make very sure that config overrides work the way we think they will - seems to write the merged configuration, and not just the overrides (and merging this with other config in the wrong order can lead to wonderfully weird to debug issues) ;-) While I'd still prefer nextcloud splitting config and state properly, and being able to cope with read-only (base) config - it might be a direction worth exploring. What do you think?"}
{"_id":"doc-en-nixpkgs-04af33963a42328dbf0c54ed988ae388dd41d8a53fa37fa4fce1f7fa5bd4d355","title":"","text":"Well, for the record it was actually idea :sweat_smile: I guess so, all the stuff from is also in my at the moment. I'll probably have sufficient time next weekend to check if I can trigger such a case. I can't promise that, but unless anybody beats me, I can hopefully prepare a fix for this :)\nDid you gain some new insights on this?\nUnfortunately not... I was pretty busy back then. But as this only requires some fiddling in the module and no patching of the actual package, the change shouldn't be too painful, so if you'd like to take over... :sweat_smile:\nthere's with a fix now :)"}
{"_id":"doc-en-nixpkgs-355f1e65454d3a22d1adae4d5042a4a1aef1b152f318fb62bcc71937034d1b3a","title":"","text":"Steps to reproduce the behavior: Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --CC\nI don't have time to look at this right now, but if anyone could run git bisect that would be helpful.\nLikely caused by the libgpiod update in\nIf so, maybe we should bring back libgpiod 1.x for openocd?\nHow many users does it even have? Might be a good idea to do the same thing that is done for ffmpeg and llvm, i.e. separate libgpiod1 and libgpiod2 packages."}
{"_id":"doc-en-nixpkgs-8c66a3f4dbf4f106f63a258754f846179469a06c3f7adc61f7e8750b1193f7d9","title":"","text":", CVSSv3=9.8 (nixos-21.05) The package glances before 3.2.1 are vulnerable to XML External Entity (XXE) Injection via the use of Fault to parse untrusted XML data, which is known to be vulnerable to XML attacks. Scanned versions: nixos-21.05: . Cc Cc Cc\nThis was resolved by"}
{"_id":"doc-en-nixpkgs-ff7b26f229ec22629feef5d8d699a8c2aea5ff26ba56eb87047b30f330d230f9","title":"","text":"Describe the bug Putting a valid certificate name in will cause nixos-rebuild to fail. To Reproduce Steps to reproduce the behavior: this line in . This command will fail. Expected behavior finishes sucessfully. Additional context This error message is related to : I guess this error is caused by switching to python 3. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:\nisn't compatible with Python 3, it seems. We'll need to update or carry a patch.\nMRTC:"}
{"_id":"doc-en-nixpkgs-ac6e02f765ba6c5ecbeffd792e24c90524f0e2480bfe17b497e4e411d1628dbf","title":"","text":"Today one of my containers wouldn't start after I updated the docker-compose file and it was due to the docker engine being too old to support a certain feature. Easy enough to fix in config but is there a specific reason the attribute points at rather than ? Last time the attr was touched was\nThe reason is basically this: Quoting a recent comment in that PR:"}
{"_id":"doc-en-nixpkgs-c1bb4e3c2848cbd672d8e167d97c192d60d606358246e27c396a6bc49290abee","title":"","text":"Building with (on nixpkgs unstable) leads to I found identical issue from 2019 in RedHat. They claim this patch fixes the issue, however I haven't tested this. (Mainly because I don't know how) I'd be happy to try to fix this, looks like just adding that patch will do the trick, but I'm new to nixpkgs Notify maintainers Metadata Please run and paste the result. Maintainer information:\nThe patch works. I'll submit a PR.\nIs this different from ? Is the patch superfluous?\nOh I didn't see that, if that fixes it then this should probably be closed. The redhat issue makes me think that it is an issue with allegro so perhaps it should be merged anyhow to ensure it doesn't crop up later. But I don't really mind\nI'm not sure that it should be closed just yet. I'd need to try building at the latest master without it. I did also run into the same problem you had.\nI'm pretty sure this is fixed now"}
{"_id":"doc-en-nixpkgs-495c18e3ca77e8da1c3c0109327c2c5c7d0f41335b5f9c3ae383a18aab1bebb9","title":"","text":"If you serve files from , nginx will set last-modified header to unix timestamp 1. The result is that browser will cache indefinitely. Not sure what we should do about it really, following nginx configuration helps:\nWhy do you need to turn etag off?\nAh, I see. nginx's etags aren't hashes.\nI wonder if we could find a way to pull the hash out of the nix store path and put it into an etag header.\nThanks for finding this. I've been having issues with broken caching on my nginx/nixos server. Even when the files on the server were updated (files in the nix store), the browser was told that no change had happened. If I'm understanding this correctly, since nginx's etags are based on filesystem modification time; you can't have proper cache invalidation (ie. it will always send 304 not modified). Or is there a workaround?\n+1 this is a problem. And turning off etag seems like overkill. Is there some way to 1) set the date on a file so that Nginx can pick it up, or 2) do something else awesome?\nIs the zero-timestamp rule set in stone in Nix, or is there some way to override it if you really want a file in /nix/store to have a particular timestamp?\nI think we could get away with: It's not perfect, as it will change on each Nix evaluation instead of being content addressed. Another way would be to turn the store path passed to nginx directive to translate into an etag.\nThe etag function is at called from and . Making it dependent on the realpath of the file seems doable.\nExplanation how to configure nginx to use the hash from the nix path:\nIn my testing, this sends the correct etag, but does not send the 304 not modified, when the etag matches. Also, the header gets stripped out when compression is enabled.\nIt's working perfectly for me. I've gzip compression enabled, the etag header is sent and the browser gets a 304 when querying the header.\nNice! An example with a directory would be more common:\nI've to correct what I said. your statement seems to be correct. What happens in my case is that Cloudflare is actually handling the caching of the ETag correctly, not nginx."}
{"_id":"doc-en-nixpkgs-a1a14ffffcdc205977352a838963db7bd22bec60ca086b144b4e4ffb998c6d6f","title":"","text":"So this approach is completely useless without external caching. I'll investigate further and see if I can come up with a solution.\nHere is a patch: If real path (after dereferencing symlinks) of is in Nix store, it will use path's hash as ETag. For example: I'll take some time to double check everything and only then send a PR. However, feel free to test: nix { pkgs, ... }: { = { enable = true; package = with pkgs; nginx.overrideAttrs (super: { patches = (super.patches or []) ++ [(fetchpatch { url = ; sha256 = \"16pa1vwcm7kibkjsxpk3szaa2vnxdinml6v0fp4038i2qaav113k\"; })]; }); }; }\nThis is really great! or anyone, do you have a moment to write an explanation of this new feature and its practical ramifications for anyone configuring an nginx server? Since it isn't typical nginx behavior, I think the nixos manual should explain it somewhere so it doesn't catch people by surprise.\nI think is a good explanation, just needs to be put into the manual.\nCool, submitted ."}
{"_id":"doc-en-nixpkgs-bff2fa0dbc53c6fd487822461dc5e3616c0d4c7b319dbc5da82224f83acb5133","title":"","text":"Package name: bottles Latest released version: 51.11 <!-- Search your package here: --- Current version on the unstable channel: 51.9 Current version on the stable/release channel: 51.9 <!-- 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! --- Old/incorrect PR Notify maintainers (for last modified) <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-e5878603e436c18b9c294723687d062ed8e906f48f1f0622f9c2daafaf5cd6d7","title":"","text":"ChefDK is deprecated and no longer maintained by Chef. This package is currently maintained by and I believe ChefDK should be dropped and replaced by Chef Workstation (see issue ). This has been deprecated since 2021."}
{"_id":"doc-en-nixpkgs-480d0e8ca931622f689fc743d9b4188bf303b3a253df5012dde2ba4f906f0c3a","title":"","text":"Build of failed on x86_64-linux as of . Maintainer cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:"}
{"_id":"doc-en-nixpkgs-c40a8e485681d613a3f4c0deb6a7398dc9ac790c901422340df6e5a558dabde0","title":"","text":"According to the 3.5 life-cycle () , the final release has already occurred and is now considered EOL. The jump from 3.5 to 3.6 has already happened in the majority of python packages and should not be a similar situation in which we had to extend python2's life long after its official EOL date."}
{"_id":"doc-en-nixpkgs-8cf27bd0629ffe6d9f006067ff2336c6fc0f68d8948f81ba2373a771efe48503","title":"","text":"Steps to reproduce the behavior: python311Packages.pymatting Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8845864b5cea8be83a9e0186e93991b942335e02f33544fa5a6049b0a7ad2d55","title":"","text":"python-kasa recently updated to 0.6.x from 0.5.x. The home-assistant project does not yet support 0.6.x, as a result kasa functionality is degraded. Using HomeAsisstant from latest nixpkgs, attempt to get emeter data from kasa devices. I reported this issue upstream and they advised on the version issue. There are more logs visible there. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI guess that if we would run the unit tests then the issue with 0.6.0 would have been detected."}
{"_id":"doc-en-nixpkgs-0a11484bf7a4e19a4d31e2b8e84f47246d06c8841b7be06f7ffc2b9df5e5bbc5","title":"","text":"All ceph tests are currently broken on release-21.11 and master. First broken in ( to ), likely due to a snappy update, like ). Steps to reproduce the behavior: -build -A etc. Tests should complete. 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. -- Maintainer information:"}
{"_id":"doc-en-nixpkgs-a466ca4012427d5bc49ebfe12d6fd319dea26d4e39e0368fa79f9ae46dc106bd","title":"","text":"Fetchers are hard to test because when the output sha is verified, Nix won't download it again. This leads to confusion and PRs that are effectively untested because the others do not realize that they need to remove the store path before testing. Examples: Steps to reproduce the behavior: a fetcher -build the fetcher -build \"success\" but the fetcher is broken a PR effort The fetcher runs every time. This is expected but not realistic, because Nix can not guess what to re-fetch. Instead, we can make fetcher testing easier by adding fetcher tests following the pattern: So this uses IFD which is probably ok for ofborg? Regarding ; instead of somewhere, we'll have to use to set on the fetchers because they're functions. The salt may need to be passed externally in case of pure evaluation. We could make it a Nixpkgs parameter that defaults to . <!-- 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. Maintainer information:\nWorkaround: Use followed by\nOr we can just put the salt in the parameter. Nix isn't clever enough to find same-hash renames in the store :)\nAnd the salt can be derived from the unsalted drv path, which is exactly what we want. See"}
{"_id":"doc-en-nixpkgs-29e09d15c1c23084f97e6bea142f52d2f6938f7c7e626ec2fa32d05f522e3238","title":"","text":"When using ffsend from nixpkgs, after uploading a file, the program segfaults. Using Nix on macOS with an M1 chip, but also tested it in a NixOS VM (arm64). Don't know if it works on x86. Steps to reproduce the behavior: The link to the file should be shown. Using the version from homebrew on macOS works. It even works when compiling it from source using cargo through nixpkgs (on macOS): only changed the version last time and last edit was four years ago Please run and paste the result. macOS: NixOS:\nWhat version of rustc are you using to compile ffsend outside of nix?\nI'm not familiar with Rust, I just ran in the ffsend git directory and it \"just worked\" so whichever version is currently in nixpkgs (at least on macOS). I haven't installed Rust on my machine.\nThanks, I have performed a bisection on nixpkgs and the regression was introduced in , so I just wanted to check that it could work with the latest rustc"}
{"_id":"doc-en-nixpkgs-9eea13c16fa8dbdb821772eb59a2b59016b6f3205254d1caa0cee475d2007891","title":"","text":"Project description awatcher is a window watcher designed to be used in combination with Activitywatch, an open-source time tracker that is already in nixpkgs. Activitywatch needs a window watcher program running to get info on what programs are open and for how long. nixpkgs already includes the default window watcher (aw-watcher-window) and the WIP wayland version (aw-watcher-window-wayland), but awatcher supports both X11 and Wayland, while featuring better Wayland support than aw-watcher-window-wayland. This would allow using Activitywatch in combination with KDE or Gnome on Wayland or when running Hyprland. Metadata homepage URL: source URL: license: Mozilla Public License 2.0 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-b1b85e410221878c14a7563eb0e409eaf09fe5c4d37d1e7a7d9358549c97a163","title":"","text":"A recent update on unstable broke compatibility between OneDriveGui and OneDrive client. Steps to reproduce the behavior: unstable to current version ( ) a OneDrive profile configured in OneDriveGui OneDriveGui window OneDriveGui correctly recognizing the cli client ! After some investigation on their respective repos, it appears that OneDriveGui 1.0.3 is not compatible with OneDrive 2.5.x, now in rc (and in Nixos unstable) so this is going to stay broken until OneDriveGui releases their 1.1.0 version. There's an open issue on their repository... which points to an alpha release of the new gui... it might be of interest to package that one on unstable. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nFYI , v2.5.0 will GA 16th September 2024 AEST"}
{"_id":"doc-en-nixpkgs-f5ba073f5bc6d619e3d989b9be764b6784ecf5dc628995e0bb9653655e01eba8","title":"","text":"Describe the bug When running the Mixxx package it fails to open and prints: Steps to reproduce the behaviour: 1) Run 3) Run from the command line. Expected behavior Mixxx opens its GUI Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nthis needs a fix in\nCan confirm running for example on my machine works.\nDoes not fix this for me. I've created: which does"}
{"_id":"doc-en-nixpkgs-451a553fefb11d4deb83ca838f127929e126cb1973ab880b6d39513dad78038e","title":"","text":"Describe the bug causes Lego to fail. To Reproduce Steps to reproduce the behavior: set on an enabled certificate. to this configuration. fail. Lego complains about an unrecognized (really misplaced) flag. Expected behavior The certificate will be successfully fetched, with Must-Staple enabled. Screenshots Additional context I think the problematic code is here: should not be in commonOpts, it should instead be in runOpts and renewOpts. Lego runs successfully when is to and . Notify maintainers (the acme team) Metadata Maintainer information:\nThanks for the report :) It appears that the --must-staple option is common to both \"run\" and \"renew\" modes, but is not actually a common option that can be specified before the mode. I'll get a PR ready for this."}
{"_id":"doc-en-nixpkgs-f4b4248b7d3f4fe3920132b57941315892a100dd9204020ceeaeea3a3ba27ff8","title":"","text":"Steps to reproduce the behavior: system configuration with Freetube in it. See and for the exact same issue with Morgen. Electron version lock seems to have been introduced with . Upstream seems to be at Electron 27: . and\nMaybe we could add the patches from It looks like they were waiting for a nixos user to test it and eventually gave up on us.\nare you able to test ?\nLooks good as far as I can tell.\nfails on this branch, for whatever reason."}
{"_id":"doc-en-nixpkgs-9a3f7b990409fab56c2ed4b0037154bb854b46024694979547e05b388b83c7a6","title":"","text":"does not start on the Mac. Steps to reproduce the behavior: via symlink, sandbox violation the app into the Application folder, sandbox violation 1Password should start Please run and paste the result.\nI should have noted, that also doesn't work\nDid it work prior to the update? Regardless, I cannot offer help with the Darwin side of things, I only use 1password-gui on NixOS.\nthat I can't say for sure"}
{"_id":"doc-en-nixpkgs-8cf1f7117d457ae29b5d19dbf0dd61e7bc7658c904df29209ba73840724f8099","title":"","text":"Related to Project description Jitsi Meet desktop application powered by Electron Metadata homepage URL: source URL: license: Apache-2.0 platforms: unix, linux, darwin,\n+1 as the App seems to have some benefits over using just a browser. Whoever starts working on this, please remember to deactivate the auto-update functionality.\nAlso I would suggest to make sure we are using a recent version of Electron and nodejs, as don in this fork:\nThere was a 2.0.0 release two days ago: I think this fixes the outdated dependencies issue mentioned in the previous comment.\nYes a pull request from the fork I mentioned before was accepted.\nI fixed the outstanding issues and PR is ready for review"}
{"_id":"doc-en-nixpkgs-b79fdb1126143f304181dcc8b16981adeafd415853f12f6d8c969e2d35c1f0b9","title":"","text":"When building chromium with args like this and the gn args aren't known/accepted by chromium (like the above one actually is that is still given incorrectly in 18.03), it will print: but continue to build anyway, which can be super surprising when your build doesn't do what you expect. We should catch that when building. Unfortunately doesn't seem to have a feature to warn. But we can run to see the in stdout and grep for it: I have confirmed that only seems to work that way when giving a build target, like . CC\nSuggestion: We switch to\nPR\npull request was merged."}
{"_id":"doc-en-nixpkgs-7e3875ddf580eb79f3e4440df607bae8fb544f5dd780ae8e21ba1a72342cd3a6","title":"","text":"Describe the bug I'm trying to use NixOS in a UPS client (not server). When , the and services shouldn't be running. There is a note that says that is not used currently. To Reproduce Steps to reproduce the behavior: Error: and fail. Expected behavior only upsmon should be running Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Maintainer information: See also\nLooks like there's a pretty simple workaround:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-f42455fa63faa260588e21bb0034eaf58f1498ea931b3c7b82da3096e74cc480","title":"","text":"Describe the bug The following snippet: results in services failing to start due to missing config files etc. : : ( fails too, but that could be down to the fact that I haven't plugged the UPS in yet -- but for the record, it complains ) Expected behavior I'd expect the services to start successfully (and probably complain about the missing actual UPS). Notify maintainers (The UPS module appears to have received only drive-by changes for the last several years, so no idea who to bug personally). Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nOK, should've read the whole module: I'm supposed to supply the missing /etc/nut files myself because it's unwise to keep them in the store (they could contain passwords and whatnot, I guess?). Declaring (in the service definitions) the state directory to be but creating for the purpose appears to be a real bug, though :)\nAlso (sorry for the semi-off-topic) what are best practices for referencing hand-written config files without their contents winding up in the store? Double-symlinking? If this is documented somewhere, then I haven't found where.\nI was struggling with the same problem as until I noticed this bug report. After copying and editing , , and from to (and setting on all those files), I was able to get it to work. I think this should be more discoverable. If it's not appropriate to copy those sample files to on the users behalf, there should at least be detailed instructions on the option to explain what else needs to be done.\nI marked this as stale due to inactivity. &rarr;\nAgreed this should be more discoverable. Perhaps at least could be defaulted to empty and written, since I seem to be getting away without anything in there. In case it helps anyone, I got it working with something like this:\nI was hit this bug today, too. Maybe we can fix it by using a startup unit that handles the secrets and setup the state directories like nextcloud or syncthing do\nBeen working on today and wanted to put some notes here. Using version 2.7.4. First, isn't used by for PIDs and it will try to write to ."}
{"_id":"doc-en-nixpkgs-b9aa03afc140411f7cb98b1a75ef1428e8e2733962d63403f6fbd21ed1ddfa08","title":"","text":"flags , , may be needed instead of environment variables until a 2.7.5 release. Ref: Using for debug makes it non-forking, requiring a change to the systemd unit . I was able to get to run as non-root: I'm still working on understanding how to manage state directories in NixOS but this was needed:\nI set out to get my UPS (cyberpower CP1500 AVR UPS) working with NixOS today. This was the first issue I came across, I figured this was the best place to share my configuration. I probably made this more complex than it needed to be because I have no idea what I am doing, and it is definitely not secure; one problem at a time.\nNot stale; still relevant\nThanks for providing your standalone config! I learned a ton tweaking it into a netserver config! The below config creates a working NUT netserver that other machines on your local network can be connected to. The only thing I have yet to figure out is a secure way to include passwords in .nix files that won't show up if I push my local copy to github. Any ideas? If you want to tweak when NUT shuts down your computers you can modify the values of \" = <percentage\" and \" = <seconds\" under \"directives\". SHUTDOWNCMD will be triggered when both conditions are met. The \"ignorelb\" directive is necessary to have NUT ignore the UPS's defaults. Anyone using this config may want to make sure SHUTDOWNCMD and NOTIFYCMD point to the correct binaries in their filesystem. One other thing of note is to check the value of the \"schedulerRules\" field under below. You must give it the path to your file. I just put a copy of it inside my /etc/nixos. Could probably add another variable to hold the path for convenience. `\nFor secrets in nix config, I think the current recommendation is to put it in a separate file and not include it in the repo. See also\nI have been using sops-nix to commit encrypted passwords to my NixOS repo, but I have yet to put in the elbow grease to make this work with my upsmon password.\nis my attempt at making generate the config files necessary for basic operation. If you are using , could you try out the changes and leave a review?"}
{"_id":"doc-en-nixpkgs-de3c44f7c15042dc88ab31b652d941b25511100479613c66dae9fb87d51fc784","title":"","text":"Using the latest packages from the unstable channel I am unable to enable the default virsh network. The error indicates an issue with the firewall backend, but I disabled the firewall systemwide through: = false; What am I missing here? system: host os: multi-user?: sandbox: version: channels(root): channels(tim): nixpkgs:\nHave you looked into libvirtd logs for a better characterization of the issue ?\nYes but I could not find anything meaninful, but I'll continue trying to find something\nI'm seeing this the 2019-12-19 04:34:37.251+0000: 4078: error : virFileReadAll:1431 : Failed to open file '/sys/class/net/virbr0-nic/operstate': No such file or directory 2019-12-19 04:34:37.251+0000: 4078: error : virNetDevGetLinkInfo:2460 : unable to read: /sys/class/net/virbr0-nic/operstate: No such file or directory Also, I noticed that ebtables was updated recently.\nI'm facing the same issue. I have the nixos firewall enabled, and it complains it can't find ebtables. If I install it separately that error goes away but I still see the errors posted by above\nI confirmed that reverting ebtables to 2.0.10-4 fixes this. Not sure what the next step is.\nIdea: set EBTABLES_PATH=/sbin/ebtables-legacy in libvirt config.\nWhen bumped from 2.0.10-4 to 2.0.11, the binary was renamed to , so the configure script fails to find it at build time.\nImpure workaround for the desperate: add the package to , and symlink to . (I also tried from the package, which does not seem to work.)\nAnother workaround for less desperate: in your overlay.\nI verified that providing an to the right binary in the derivation allows my VMs to work again. I tested in a overlay I maintain, from which a minimal (untested) extract to work around the issue until someone has time to come up with a more correct patch to submit upstream is:\nI've confirmed that the overlay in works.\nI also have the issue."}
{"_id":"doc-en-nixpkgs-1802838b65f6d6922dcec50cf654484e7965712a3356f1a66df51ec2019df858","title":"","text":"This is actually a major issue, if libvirt does not work anymore.\nHad the same issue with unstable. The overlay above fixed it. Do we just need a PR to staging-next that adds that environment variable to the build? I'll submit that PR if that is all that is necessary -- didn't see any submitted yet."}
{"_id":"doc-en-nixpkgs-95c43717e355b49bdbcc0ca7a5ab7d68235315a48d7e26b6b01c3d46127a37a7","title":"","text":"nix-shell -p supercollider [anders $ nixos-version (Flounder) [anders $ nix-env --version nix-env (Nix) 1.11.2 [anders $ nix-instantiate --eval '<nixpkgs' -A lib.nixpkgsVersion \"\"\nyou use supercollider ?\nno, sorry.\nSame here:"}
{"_id":"doc-en-nixpkgs-0839a3cf8f3d337ffc20841cb22ba32b405c4e27f129818234393a0685821eca","title":"","text":"Steps to reproduce the behavior: nomachine-client Seems like nomachine changed their tar file. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nIt seems that NoMachine has removed the from their website and the link is now a redirect to the homepage. The new latest version is .\n? this url works"}
{"_id":"doc-en-nixpkgs-4b05af73330ecfb2f37032eb86d1e4e733a13af001d562e5795d7d251274cef4","title":"","text":"fails while compiling The same thing happens with Steps to reproduce the behavior: or: is successfully installed. Here is the output:\nFix in\nThanks On the same system that I encountered the error on, I checkout out the branch with your fix and then ran: The installation worked and is runnable. I'll be doing more testing later today/tomorrow."}
{"_id":"doc-en-nixpkgs-fdde2313ed10591f0fd4ca594ce4c99d5bf31d932b903922cb2e7aa20ca2121d","title":"","text":"Package name: mythtv Latest released version: 34.0 Current version on the unstable channel: 32.0 Current version on the stable/release channel: 32.0 Notify maintainers Announcement: Changelog: Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-b95d43a6f265df1a632cd08902e081b118fa535e7200e68172bd54c27071c614","title":"","text":"Project description Youtube client in terminal for music ( lightweight youtube client ) Metadata homepage URL: source URL: license: gpl2 platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-f8cff2a6b64a7d20c4d5fc35cd36f74c29031455ce1240673825fb3965e950d5","title":"","text":"Package name: nix23 Latest released version: 2.3.17 (see ) Current version on the unstable channel: 2.3.16 Current version on the stable/release channel: 2.3.16 Notify maintainers Note for maintainers: Please tag this issue in your PR. See for context. The release script apparently doesn't upload source tarballs anymore, so 2.3.17 sources look more like the other ones. There's a bunch of expressions in that might need to be revisited."}
{"_id":"doc-en-nixpkgs-6d58d99560c981a886e182ffd9e34172321fd5e291759e87076fffd91a7c0367","title":"","text":"Here is result of — I'll try to do something about it when I have time but it'll most likely be next year, so please go ahead and fix it if you have time for minor issues.\nScreenshot?\npavucontrol has no binary wrapper, thus icons won't show unless relevant icon themes are installed in the system.\nFixed in master."}
{"_id":"doc-en-nixpkgs-19937891805111cefc118a44e5ecf744723b2a1e7b7470022d0516e7284e1da3","title":"","text":"The current process for renames puts out-of-tree modules in a situation where users are confronted with warnings they can't solve, and neither can the maintainers. Steps to reproduce the behavior: one change, create the new option/package/..., create the alias with a deprecation warning that goes into effect immediately -of-tree modules, such as home-manager, nix-darwin, start emitting warnings reports warning -of-tree module maintainer can't do anything, because stable release does not have the new option All generated warnings can be resolved by the user. Suggested process: one change, create the new option/package/... and the alias but no deprecation warning 1-7 months pass. All current branches now support the new way. enable the warning on master (more on that) -of-tree modules, such as home-manager, nix-darwin, start emitting warnings warnings can now be fixed To facilitate the process, we can add an argument to functions like to indicate the first release that will support the change. We'll maintain two (hidden?) version numbers that we update during the NixOS release process. For example, at the time of writing, the only supported stable version is 21.11 and 22.05 has not been released yet. To enable warnings on , we only need to update . Interestingly, we'll be deprecating functions that deprecate without . Sounds meta, but it's not complicated. It just means that some old style deprecations will slip through the net for some more time. (also a big one, but no complaints yet)\nThis is also related to NixOS/rfcs, which was a previous attempt at establishing general such deprecation behaviors"}
{"_id":"doc-en-nixpkgs-6700785ee95cad356b59d39c3c69cca406fe80be77af5945976459f5c8d284fd","title":"","text":"I've just set on my laptop while on holiday. The timezone never updates (tried restarting, waiting a while). Running I see: I see in that the service is run as the user. If I run: I also see the message . Whereas if I run there is no output and the timezone immediately updates (as shown by an immediate change in the time in my status bar, and confirmed by running ). It seems that the user just doesn't have permission to set the timezone. in (and unset ) to see if timezone changes , look for messages with \"Failed to set timezone\" (will only appear if the timezone it would need to set is different than the current timezone) system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nIt worked for me after a reboot. Maybe the polkit rules are not getting appliead during a ?"}
{"_id":"doc-en-nixpkgs-d0aec231e7560b23979af6de47eeb323350169cf4927ea6e1e45e260c036cdc4","title":"","text":"Steps to reproduce the behavior: unar from Full build: <!-- 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.\nThis could be related to GNUstep being updated??\nYes, that PR is the cause.\nOuch, sorry. Could've sworn I ran nixpkgs-review against it, but maybe I didn't. I'll try to see what I can do, although maybe only next week. We can also revert, if I can't find the time or nobody else comes up with a fix.\nFor the status on Hydra:"}
{"_id":"doc-en-nixpkgs-4abf4696f5d1db60a2a8fa5eb6a63fc23a424771ce7ea14dab8fcb91fb3c8f4c","title":"","text":"Project description Granian is a Rust HTTP server for Python ASGI/WSGI/RSGI applications. It fulfills a similar purpose as daphne, gunicorn, uvicorn or uwsgi, but . Metadata homepage URL: source URL: license: bsd3 platforms: unix Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-b89228646d76091bc3f0513cc290668bedb1e618a2fc26d2fd01742b2cd12846","title":"","text":"shows this for me: When I try to upgrade my system, I get the error “could not find any previously installed systemd-boot”. This is because the script can't deal with systemd-boot versions with a minor version appended to it, since the regex is : Fixing this is not quite straightforward sadly, since the version is later used for comparison, so fixing this requires adding support for proper major/minor version comparison in this script. <!-- 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. Maintainer information:\nrelated"}
{"_id":"doc-en-nixpkgs-7f3f54c1e2007726f39b9de266f4ba7c8bc07cf8bc9daedaa2c3efa5be1a005e","title":"","text":"Despite the bintools for riscv64-linux advertises the existence of , it is actually missing. Steps to reproduce the behavior: , returns the output, there is only , no the same process for , is both advertised and available. Either evaluates to , or is available in <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nLooking at ;a=blob;;h=;hb=HEAD is not supported on riscv64. tracks it upstream. I don't expect progress implementing the support any time soon.\nThen we should accept the second solution: mark as false, we should also double check the availability of gold on other ELF platforms."}
{"_id":"doc-en-nixpkgs-545bf6523fc9d6de2cb0be50d6dcad6eb5fcdb96d7cbfe2dc861b2781083548e","title":"","text":"Project description Python app to work with pictures and associated metadata from Apple Photos on macOS. Also includes a package to provide programmatic access to the Photos library, pictures, and metadata. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis was the most complex package i ever tried to write :sweat_smile:"}
{"_id":"doc-en-nixpkgs-23dcd32176e58d627c7949f705d2e3b76bbf0f6f15f0db9a0ae8c4712787a07c","title":"","text":", CVSSv3=7.5 (nixos-unstable) CVSSv3=5.3 (nixos-unstable) CVSSv3=5.3 (nixos-unstable) In InvoicePlane 1.5.11 a misconfigured web server allows unauthenticated directory listing and file download. Allowing an attacker to directory traversal and download files suppose to be private without authentication. In InvoicePlane 1.5.11, the upload feature discloses the full path of the file upload directory. InvoicePlane 1.5.11 doesn't have any rate-limiting for password reset and the reset token is generated using a weak mechanism that is predictable. Scanned versions: nixos-unstable: . Cc"}
{"_id":"doc-en-nixpkgs-169b9833d0a3e6822846495fb97f3b91341100eba21d7dc923017d48f61796ea","title":"","text":"Describe the bug fcitx-qt5 fails to build on unstable: To Reproduce Metadata nixos unstable\nIt's trying to install into qtbase . Probably should set this to be within the proper prefix.\nyep I've seen that as well. Seems like some packages set to work around this but haven't had the time to test it yet. EDIT: that fixed the first problem but not the second one:\nwill fix this.\nThis is still an issue on stable -- Installing: /nix/store/phkl5sfpn4jvncjd2sa29g182gpmmja7-fcitx-qt5-1.2.3/share/locale/zhCN/LCMESSAGES/fcitx- -- Installing: /nix/store/phkl5sfpn4jvncjd2sa29g182gpmmja7-fcitx-qt5-1.2.3/share/locale/zhTW/LCMESSAGES/fcitx- -- Installing: /nix/store/g83143pyn6sc1x1nqqjcamap4c2b1rbw-qtbase-5.12.0-bin/lib/qt- CMake Error at (file): file INSTALL cannot copy file \"\" to \"/nix/store/g83143pyn6sc1x1nqqjcamap4c2b1rbw-qtbase-5.12.0-bin/lib/qt-\"."}
{"_id":"doc-en-nixpkgs-794d9244448d8e33df43be78155ffcd2679446762df86834d442814adf4f3acb","title":"","text":"Call Stack (most recent call first): (include) make: * [Makefile:106: install] Error 1 builder for '/nix/store/ypfmrmajq452nmskg0ffwa27hm58l492-fcitx-qt5-' failed with exit code 2 cannot build derivation '/nix/store/hdsvn6hc7h7wf29kdnpvr7iaivplyyb8-fcitx-with-plugins-': 1 dependencies couldn't be built cannot build derivation '/nix/store/4lwxfbacn5fcymlm3jpv6wl4anllxmzd-system-': 1 dependencies couldn't be built cannot build derivation '/nix/store/d4k8dywj47xrbxfmvdaw4gywnwdn874r-xsession-': 1 dependencies couldn't be built cannot build derivation '/nix/store/fj8xinm3fjd7sp9s20iqg23yx27zc193-nixos-system-voyagertwo-': 1 dependencies couldn't be built error: build of '/nix/store/fj8xinm3fjd7sp9s20iqg23yx27zc193-nixos-system-voyagertwo-' failed Note that I have a following setting in environment.extraOutputsToInstall = [\"out\"]; environment.pathsToLink = [ \"/share/locale\" ];\n:confused: Didn't expect that to broken the same way on stable. please open a separate issue requesting some sort of backport for the relevant commit\nStill seems to fail on unstable?"}
{"_id":"doc-en-nixpkgs-298449895834755ab223f6107a62516b2a9e2794cdf06e4d4964a0aae3c69310","title":"","text":", (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.\nOn it\nDone"}
{"_id":"doc-en-nixpkgs-51744b584962c3d27ea51d51e75c2e10bbd8ac275d8a4f9b3b30d6986611d6d8","title":"","text":"Describe the bug build of OpenEXR fails to find -lImath24 To Reproduce Expected behavior Successful build. Screenshots Additional context Add any other context about the problem here. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(jfelice): nixpkgs: Maintainer information:\nSomething seems to be mangling the library names incorrectly? The ilmbase package contains: Notice the periods.\ncc.\nI lack the hardware to debug this. any ideas?\nRepro'd on 10.14\nseems to indicate that autoconf-based builds are only supported on linux - we may want to switch this to cmake. Building outside of nix via cmake is working fine for me.\ncan you give a try?\nI can confirm this still builds on at least.\nappears to fix this for me (macos 10.14). Reopen if it's still a problem for you."}
{"_id":"doc-en-nixpkgs-f436a026752f3cca24e6e1bff4bbe992f50c1f183e476c9e00b179d376622c29","title":"","text":"While deploying a machine via deploy-rs, I had this error: Then stop docker or deploy the service from scratch, my belief is that docker-prune can start before docker.service and thus fail since it can't access the docker daemon. No systemd error whatever the configuration. I believe a patch like this should fix it but I am no systemd expert: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- from blame current unstable\nI think the patch you propose makes sense. Could you open an PR for it?"}
{"_id":"doc-en-nixpkgs-8b079c60add143fe3189a7e566bf9a2dacaaae41e29fa2be40ed61d60bf98967","title":"","text":"Building RStudio fails with the following error message (seems to be something to do with the fact that QMake got upgraded): Run . System: (NixOS: , Ubuntu/Fedora: , ...) . Nix version: (run ) Nixpkgs version: (run ) Sandboxing enabled: (run )"}
{"_id":"doc-en-nixpkgs-43489a7e3cf31d4305c9acb2439c6c5bec7ab264d1923520abb8f38250ffb7d8","title":"","text":"It's interesting that this doesn't happen on (x86_64-)linux, apparently."}
{"_id":"doc-en-nixpkgs-64f7e18f21d07e13d99552e3e1c632ac911ce53da1a243a90ad612eb3c8dbf72","title":"","text":"Project description Yet Another way to use Windows VST plugins on Linux. Yabridge seamlessly supports using both 32-bit and 64-bit Windows VST2 and VST3 plugins in a 64-bit Linux VST host as if they were native VST2 and VST3 plugins, with optional support for plugin groups to enable inter-plugin communication for VST2 plugins and quick startup times. Its modern concurrent architecture and focus on transparency allows yabridge to be both fast and highly compatible, while also staying easy to debug and maintain. If I understand correctly, this provides similar functionality to the airwave package. I think the big plus to this package though is that it emulates as if they were native which means the build process doesn't need to require the user to go to the steinberg site and download the VST SDK (as airwave currently does). I used this on Arch with Reaper and it was extremely easy to get going. I had a much easier time using yabridge than trying to get carla set up and running. There are multiple AUR packages for installing from source or just pulling in the binaries. I've tried to package this myself but it's just a bit beyond my means. I think that if someone is more familiar with packaging wine related binaries or compiling with meson from source this would be a quick win. homepage URL: source URL: license: GPL 3.0 platforms: linux\nI probably won't have time today, but I can take a look at this later. I'm pretty familiar with the nixpkgs wine build, and I've worked with the ZynAddSubFx build to add support for the Zyn-Fusion ui.\nAmazing. I was able to take your PR and get Upright Piano working with Reaper as well. Thank you so much for the quick turn around, I really appreciate it.\nHi! I don't use NixOS myself, but if it helps, there's one person in the yabridge Discord currently using yabridge's master branch with NixOS. And I've also ran into another Nix build definition on GitHub in the past (but that one's pretty outdated by now).\nI've just released with a lot of important new features, fixes and improvements including the first ever Linux <-Windows VST3 plugin bridge."}
{"_id":"doc-en-nixpkgs-ab79459cd6bff10b94d8ea2c1df1b311d1857d7c001cc621262ac669a40bdccd","title":"","text":"I saw that the package created by for yabridge 2.2.1 has not been merged yet, but please let me know if you want to update the yabridge and yabridgectl packages for yabridge 3.0.0 and need any help! One additional dependency is now a patched version of the VST3 SDK which is patched to compile under winegcc and with support for Meson. I'm not quite sure how Nix packaging handles those things.\nThanks, I have it building right now. I'm just testing out vst3 plugins right now :smile:\n:cry: For some reason neither the vst2 or vst3 plugins are working, even though they get synced. I think it might be an issue with my system installed wine. I'll submit my changes anyway so other people can test it out.\nSo they are found but yabridge fails to load them? Which Wine are your derivations using?\nYou can try running manually to see if that is the issue. A plain call should print: And should print:\nI'm able to sync them with yabridgectl, but they fail to load in Reaper. I'm using (currently version 6.0) to build yabridge, but I have a custom build of wine staging 6.0 currently installed. seems to be working fine:\nThat indeed seems to work as expected, that's great news! If you start REAPER with and then take a look at after trying to scan/load a plugin then you'll probably be able to figure out what's wrong very quickly.\nHmm, apparently the path to the VST host is too long :stuckouttongue:\nHuh I can't think of from the top of my head what would be throwing such an exception. That message printed after comes from a try-catch around the entire plugin startup that catches and prints any . Windows (and thus Wine, because it has to be compatible haha) has a path name limit of 255 characters, but none of those paths sound like they should come close to that.\nYeah, sorry. It was just a problem with my home environment. I was trying to test it without installing because I lost the nixpkgs commit I used to generate my home-manager environment."}
{"_id":"doc-en-nixpkgs-bff0973e05890e41d3e17165d9d9d763c9dacf84015e330faa69449159693e4e","title":"","text":"REAPER was just loading the old 2.2.1 yabridge- :woman_facepalming: I just finished rebuilding my home environment with a new nixpkgs commit, and it's working now :smile: ."}
{"_id":"doc-en-nixpkgs-9b9331376ca40c134a0e8538fd7ab89ac55b0be730acef400227ae454145ade0","title":"","text":"Currently, our Android SDK derivations contain only binary files. This is unfortunate during development, when one wants to jump to a definition of a particular symbol in the SDK and it is not found. For comparison, ArchLinux is doing this in their packages, e.g. System: 16.09pre-git (Flounder) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: \"16.09beta335.\" /cc\nCreated PR ."}
{"_id":"doc-en-nixpkgs-130f3eed45275e57abee326ca0931c2dd96236e95e4be957a211eaf50a484a06","title":"","text":"Describe the bug Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(hyper): channels(root): nixpkgs: Maintainer information:\nI've also encountered this. I bisected it to . says there's a newer version (1.) whose release notes say \"Fix two test failures on newer versions of gtk+/gnome-shell/mutter\". However, updating to it does not fix this test failure. :( With 1., the exact failure I'm getting is:\nWhen updating to GNOME 3.34 I did indeed notice this and tried the exact things did. We probably need to report it so it can be fixed, I just didn't have the time to do this. Guess the testsuite could be disabled.\nDisabling tests got it to build for me. I'll try to find some time to open a PR for that, and to report it upstream.\nReported upstream:\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on ."}
{"_id":"doc-en-nixpkgs-a776d404298b566c6275a48ca6161fde4f51d2f1d4ee99708f511a5e095b631f","title":"","text":"Describe the bug Keyboard backlight keys don't work out of the box on LXQT. Pressing one brings up a polkit dialog for authorization to run as superuser. Of course, changing the backlight brightness should not require authorization. liblxqt provides an function in which I believe is the problematic code path. This function calls a helper utility as follows: FILE lxqtbacklightbackendgetwritestream() { FILE stream = popen(\"pkexec lxqt-backlightbackend --stdin\", \"w\"); return stream; } There is a polkit rule for this: $ cat <?xml version=\"1.0\" encoding=\"UTF-8\"?<!DOCTYPE policyconfig PUBLIC \"-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN\" \"\"<policyconfig<action id=\"\"<messageAuthentication is required to Change Brightness</message<iconnamebattery</iconname<defaults<allowanyno</allowany<allowinactiveno</allowinactive<allowactiveyes</allowactive</defaults<annotate key=\"\"${CMAKEINSTALLPREFIX}/bin/lxqt-backlightbackend</annotate</action</policyconfigHowever, this rule ends up expanding to e.g.: <annotate key=\"\"/nix/store/k1w634ib02dxqh046icm2i7ml28iycq5-liblxqt-0.17.0/bin/lxqt-backlightbackend</annotateand polkit is presumably just finding the binary in . It appears that pkexec doesn't resolve symlinks, as if I run on the path, I get the prompt, whereas if I run on the resolved path, I don't get prompted, and I can adjust the brightness from the command line. I'm not sure what the proper solution is here. I don't know enough about polkit to have an opinion on its symlink handling. Maybe we can provide another polkit rule for the path? To Reproduce Steps to reproduce the behavior: LXQT and boot into it. a display brightness key on your keyboard. polkit dialog appear. Expected behavior Display brightness should be adjustable without entering your password. Screenshots If applicable, add screenshots to help explain your problem. Additional context I'm running NixOS 20.09, and have hit this bug both with the shipped LXQT, as well as when I backported 0.17.0 from ."}
{"_id":"doc-en-nixpkgs-76b224dd9dcc9a8661aacfcf522b676f85bd40343536ba369e18aee29b6d383e","title":"","text":"Notify maintainers Hi there thanks for providing an update to 0.17 so quickly! Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(khumba): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-d78135cb146bdd6251779094471be19e059d934d71aec3238e9b172539574fa9","title":"","text":"LLVM 12 (not yet released, currently at RC3) will be required for building Chromium M90+ (currently in the beta channel; stable release planned for 2021-04-13; s. ). cc I couldn't find a draft PR for LLVM 12 yet. Are you already working on it or currently busy? LLVM Release Schedule: 12.0.0: Jan 26: release/12.x branch, 12.0.0-rc1 Feb 23: 12.0.0-rc2 Mar 2: 12.0.0-final\nI have't started yet. But I think I have a few minutes now!\nJust a heads-up, we have Should that transition to ?\nI have to hand this over to you, Borg says the unit tests fail (on both platforms, consistently). Maybe the testing framework needs a bump?\nActually, LLVM is not enough I tested with and the key commit seems not included into You have to either wait for compile LLVM now cherry-pick to or related\nThe match is a bit out of context: We have so everything should be fine. ok, thanks for that information! If I understand that correctly you've tried compiling or with and it requires cherry-picking as well (which would be unfortunate because that commit might not be part of the final release; they don't seem to have a dedicated branch for the LLVM 12 release and I don't know where/how/if they track and provide that information - Edit: Oh, they have a branch (the GitHub UI doesn't seem show all branches that a commit is part of) but wasn't cherry-picked so far).\nI built (from llvm master, simple replacing with fetchFromGitHub and removing some lines in ) and it builds Chromium 91\nRC3 in"}
{"_id":"doc-en-nixpkgs-c25c9fe1c9c0d8d4c4ba450a012eacb3da15e02949d569f1943141cfa4a43fdb","title":"","text":"Upstream , but we still have many packages depending on it. I know of no issues since the last release, so I'm not marking it as vulnerable yet, but the dependents would better start migrating in advance. Stable: it's unclear to me what we do about these in 19.09, but perhaps there won't be any notable vulnerabilities before 19.09 support ends :-) 1.0.2 is the default in 19.03, but we don't support that anymore.\nList of files:\nI think we should mark it vulnerable. Other EOL packages have been marked vulnerable because of the EOL before, e.g. Firefox, and if there’s any package we should be extra-careful with, its OpenSSL.\nI bumped it to fix the last CVE minutes before opening this ticket, so I was obviously biased against marking it immediately ;-)\nBTW, it's still a decision to make, as there's surely some LTS distro that will keep shipping 1.0.2 for some time, so patching the worst probably won't be too difficult. I'm personally not willing to invest significant time into it, though :-)\nBest way to motivate somebody to volunteer is to mark it as insecure. ;)\nOK, I think the we've given enough time and now we should press on a bit:"}
{"_id":"doc-en-nixpkgs-d3eac81df11863ef754f5a3e12ebbd6fedc16ed9aa092cc976f25c4b60974e17","title":"","text":"Package name: surrealist Latest released version: 2.0.1 <!-- Search your package here: --- Current version on the unstable channel: 1.11.7 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 Surrealist has now officially moved to the SurrealDB Github org, see Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nNvm the nix package is actually built from source, just Tauri builds a deb in that process\nWorking on it. I'm currently stuck at an issue with the frontend build. There is a transitive dependency to that does not get installed by pnpm."}
{"_id":"doc-en-nixpkgs-9c0a7a3adf3e4456c655edd43aeae3c43e673e0c782e4cea5eecb79e6d60412f","title":"","text":"Project description <!-- Describe the project a little: --Sunshine has already been packaged here in nixpkgs: But it doesn't come out of the box just by , according to and and , at least it needs a and maybe . It would be better if we could add a NixOS module for it to make it availale just by sth. like or . CC maintainer Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis has been on my to-do list for ages :) The module itself wouldn't be a huge deal, and I think I have a plan for tests, just need some time to work on it.\nI actually started working on this a while ago. My module can create valid and files (i.e. they work when I start sunshine manually) and open the necessary ports, however I couldn't get the systemd service to function properly. If I recall correctly, the issue was related to getting access to the screen. Here is what I have so far, maybe it can help someone:\nThanks I used yours as inspiration and opened for this. It's still a draft -- I need to work on the tests -- but any testing or comments are welcome. I've tested on Plasma 6 + Wayland + AMD and seems to work, have not tested much with Xorg or NVIDIA.\nThink it's got all the functionality I had planned -- marked as ready for review."}
{"_id":"doc-en-nixpkgs-f144e303753e75b05688c52f08dfc92a927b9ebb9e4a56279818fc0a488fd0f0","title":"","text":"c.f. If using --patterns-from, all of the paths to back up are (or can be) read from the pattern file, and specifying paths on the command line is optional. But the nixos configuration won't let you omit the paths, and since they aren't stored in a variable you can't even do something awkward with preHook or preCreate to unset them.\nWhile investigating this, I found the related issue that since it requires \"paths\" rather than \"strings\" it also only works for absolute paths; if you want to back up relative paths (using preHook to make sure they're relative to the right directory) this is impossible. Not sure if that's worth opening a separate issue for.\nI changed it to .\nThank you!"}
{"_id":"doc-en-nixpkgs-93353bf6d001245084cbc4e9cbeafb0df395e19593084781507ca8bbfd7d27db","title":"","text":"Package name: podman-tui Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.18.0 Current version on the stable/release channel: 0.12.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --I attempted to update this package myself and create a PR, however, there appears to be a major changes to how this package is built that are outside my ability to address. Attempting to build the package after a , both with and without the changes in , results in the following build log: Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-3905ebb4e7a4b39ecdf51c6ed879db7bb4d6f61aea8df45747e2bb023d3402a2","title":"","text":"XRootD failed to access the files following the URL, complaining that isn't found and the authentication handler couldn't be loaded. However, does present in the output directory. Steps to reproduce the behavior: Enter the top directory of Nixpkgs See Run See the detailed output A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Terminal output during execution: Short: Long: is packaged by myself, but I haven't found the solution. Suggestions and helps are more than welcom. Please run and paste the result.\nThis is probably because has the wrong . How to fix that though? No idea."}
{"_id":"doc-en-nixpkgs-a863339e4d69b124b6134169ef15732db79d781e89353e07942cbf47465c26c9","title":"","text":"Package name: electrum Latest released version: 4.4.4 <!-- Search your package here: --- Current version on the unstable channel: 4.4.0 Current version on the stable/release channel: 4.4.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Reporters Note: Tried the update locally and got the error Looking at the diff on the electrum github I see the substituteInPlace pattern will no longer match: In:\nPR in"}
{"_id":"doc-en-nixpkgs-6a2aa1f70bebf6f1a73e8e97ae5b5675107c006fd34427ee516315e9ba82f704","title":"","text":"Project description Unity is changing the way they deliver the editor via the UnityHub. They have shifted away from the appimage and have started Debian and RHEL repositories. They are not producing the appimage anymore. Would it be possible to add the new UnityHub to NixOS? The new download instructions are here:\nExtracting the binary from the .deb is fairly simple and has been done in similar situations in nixpkgs before.\nIs there any quick fix to use unity right now?\nNot that I have found. You could use an old version of the appimage if you still have one. The flatpak is available but is a really old version.\nI am currently building a derivation locally to extract the binary from the .deb package and make it run. Lets see how long it takes\nhave you had any success? I have but it yells about and crashes when I try to use it\nI thought that unityhub is an electron app. My current attempt results in a f mismatch from electron. Here is my . I build it via .\nYeah it is electron but I'm just trying to package the prepackaged electron binary instead of using system electron\nYes you are right. When trying to use the included electron binary it will result in the same error. Hm when I have some time I will investigate with . Or maybe you had any luck?\nUnfortunately not, I've seen one other mention of the same error with electron with no solution, and I'm not sure how to do deeper debugging personally.\nI've managed to do something: by adding to LDLIBRARYPATH, I can get it to not , but now instead it just hangs... I'll keep trying but I'm not sure what it is this time.\nI've made a tad more progress, I forgot to enable gnome-keychain so that was causing the hang, but now it's segfaulting :sweat: I do see it looking for but I'm not sure what that even is\nFinally, got it working. It boots up and I can install everything properly. The remaining issue is that hub-installed versions of Unity aren't patched so the hub fails to launch them. It seems that since the previous version used appimages, the library paths were passed to the editor as well as the hub, but I'm not sure how to do it with this. Do I need ?"}
{"_id":"doc-en-nixpkgs-e702fb798c52ceff6f17f0f6bb62082578caee9aa7dadaeb68d26796b4e9ec2b","title":"","text":"I'll try that but I'm not sure if there's a more optimal solution.\nLooking at the code seems to be the way. !\n<details open<summaryWeird error I'm getting when I'm trying to open say Preferences or the Package Manager in the unity editor.... I have no idea what this is from, am I missing gtk stuff?</summary<br</details\nHopefully the final bit of the saga, it turns out the GTK issue I had isn't unique to NixOS, it occurs on other distros too, see the . In that case, it seems my derivation for the updated Unity Hub is working properly in all other regards, and can be found . All the need to be cleaned up, I may have a few unnecessary ones, and there's a lot of leftover testing with the QML paths :sweat_smile:. If it looks good, perhaps we can update Unity Hub in nixpkgs too? I've also made a describing how to use Rider with Unity on NixOS as well, might help someone out.\nThanks for that looking forward to seeing that on master!\nHehe thanks for the reminder, forgot to make a PR for updating the package!\nI just copied your derivation meanwhile and was the only thing it make unity work (installing the 2021.3.4), thanks!\nHello I use Unity and just tried out file. It works great! However, I cannot find your PR. Would you be able to point me in the right direction? I would love to see this in nixpkgs soon!\nI've been kinda busy recently with other prs and such, but I'm definitely planning to make a PR in nixpkgs, if not later today, definitely by this weekend. Thanks for the support :)"}
{"_id":"doc-en-nixpkgs-4acdae627bd8e4db1d364b53b353550ecd6fb4680c18c16e883a80d22dcd7971","title":"","text":"I use enabled. I also have a web server service that specifies: Because my web server is a bit long to start, the timeout and its systemd unit fails. To Reproduce Use the following example module: Expected behavior The acme systemd units created by  should wait that nginx is started before starting. Metadata Maintainer information:\nShould adding to what is already to  fix the issue?\nMaking a note that has the same code and presumably the same issue so any fix on should likely be ported to .\nThank you for the issue and reproducer. I'll have a closer look at this today\nwhat exactly do you mean by \"timeout\" here by the way. could you provide some journal logs of this failure? I can try reproduce when I'm home, but maybe the logs are enough to understand what is going wrong\nI mean \"Timeout during connect (likely firewall problem)\" in the logs below. Note that the hostname, email and domain have been redacted. Also notice the long time between and . nginx was not started when the Let's Encrypt tried to retrieve the challenge:\nI'm scared that won't work. The lack of here is very deliberate pulls in (Through and ) to create fake certs, as nginx crashes hard when certificate paths aren't present. We want to start up before the acme challenge is initiated, as nginx is responsible for serving the director to complete it. If starts before nginx, it will always fail. It's all a bit mind-boggling and the dependencies are a bit complicated. I wish it was a bit more simpler too. However; isn't what we want here instead? We want to guarentee that is running before the certificate request is fired off. So adding a to might work? I'll see if that fixes it..\nAbsolutely, that is what I meant but I wrote it wrongly.\nShould we go for the solution proposed?\nYep. I have a PR in the works on my machine. I'll try to get it out this week"}
{"_id":"doc-en-nixpkgs-c903591d27824029d140694d09cd87fc1228cdd4720380a4bf1c2ddf0c9bea17","title":"","text":"When trying to use rocprofv2: This might have something to do with some predefined paths in Steps to reproduce the behavior: an executable with hipcc it with rocprofv2 <!-- 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.\nI need to do some work with . need to make a patch that strips. I need to fix itself. I wonder if it's because I'm stripping out the test directories? Also yes, it looks like you're right. You can fix that by prepending too, so I'm not entirely sure it'll work. Try setting `. You may just be able to run it from that as well.\nI don't think that removing hsa-amd-aqlprofile-bin is a good idea, because without it, it loses performance counters support. I think there should at least be a rocprof derivation with aqlprofile.\nMy bad, I forgot to add that the patch is optional.\nRight. Could you tell me your test environment and the source of the hip executable (or just some stub) so I can replicate this? I've never actually used rocprofiler.\nYou can try this, it just prints 10 numbers, it can be compiled with hipcc without any flag. I am using a radeon rx6600m(gfx1032).\nsee"}
{"_id":"doc-en-nixpkgs-a125bebc13260856fdaa510aa15fe6769838d0872f0d7bae16059e849fd97fef","title":"","text":"Steps to reproduce the behavior: odin If you run the resulting binary through you'll see this strange backtrace: I think it has to do with the version of the C++ standard library that is getting linked. Adding and to the and updating the file to explicitly link allows it to run without segfaulting. (But thats just a workaround I'm using). EDIT: During more testing with the built binary, it also doesn't use the correct linker, which can cause problems if you are linking with Objective-C code/frameworks (not sure if this is a problem with how Odin is packaged with nix, or if its a problem that the Odin devs need to solve). Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: Note: Was fixed by\nmacOS Odin support is kinda scuffed anyway with any deviation from what's expected. do you have the code for your workaround somewhere? then i can see if i can patch it in\nI'm using for my project. It doesn't have any switching based on OS, and my override probably isn't necessary either. Honestly, the is probably the only thing needed to stop the seg faulting.\nupdating to llvm17 is not a bad idea either"}
{"_id":"doc-en-nixpkgs-3bcc9afc710a4f1aac129e22d50a2e28395b11769be638665bf1f86e37f12744","title":"","text":"When using an option with , the type description references the nested type's name instead of its description. This can lead to type descriptions like \"function that evaluates to a(n) functionTo\". Nix expression to reproduce: Reproduction in NixOS: The Nix expr should print something like \"function that evaluates to a(n) function that evaluates to a(n) string\". The command should print a type description like \"function that evaluates to a(n) list of packages\"."}
{"_id":"doc-en-nixpkgs-57ea3a6d7fa315428a587283ea2f522682c22657d7fab2b3d12e57ef6e201332","title":"","text":"Project description A VSCode extension that integrates Vue features with TypeScript features Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-bafc509c3284f7b2087ad8beaaed7ea07ee55bb93263d3fe43f68315a7689e4d","title":"","text":"Project description Convert bibtex file to yaml which typst needed. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit, apache platforms: unix, linux, darwin, ..."}
{"_id":"doc-en-nixpkgs-b5e63824a7e802e876d2af94e978c286d8f7fcec199af7e8893d749a3aa387ca","title":"","text":"Package name: imhex Latest released version: 1.27.1 <!-- Search your package here: --- Current version on the unstable channel: 1.26.2 Current version on the stable/release channel: 1.19.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-e10cb6b39703151d29342b8d37d61a57a2903f7df70881e769bd16e60fd5f2a8","title":"","text":"Project description Upgrade 389-ds-base Apparenty its new 1.4.4.4 release is a bit different. Metadata homepage URL: source URL:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-79049c5363a9d094575659568f43e53af40d759bfbe42d4b7700c73fb51d5d64","title":"","text":"I'm trying to build octave with QT5 and with GUI (of course, when I try to build it with GUI, right?). Unfortunately, after the build: Apply this patch: and then system: host os: multi-user?: sandbox: version: channels(m): nixpkgs:\nI just noticed that I do not even get the GUI feature when building octave from nixpkgs (neither nor has a GUI).\nPinging: touched the package recently, is the maintainer of the package.\nI’ll try to have a look when I have some time. I’ll let you know what I can achieve.\nHere is what the configure script says:\nyes, I got that and I fixed it. See for my attempt to build with Qt5 (which succeeds, but starting octave with gui fails - see PR)."}
{"_id":"doc-en-nixpkgs-0bc8b55feef4ec326584cb76fdc974aa3288d1c8b5ec21189cfa3763bccb5a8c","title":"","text":"libxls, one of the optional dependencies for sc-im has 6 open CVEs for arbitrary code execution, which were reported on github 5 months ago and the issue hasn't even been responded to. I think this dependency should be made optional and probably should not be included by default. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-40dcb6d317f33e0a6f2c1784cc6759514423c34cb8a1fb9083abc68dfa212c28","title":"","text":"Project description A modification of the Mesa Vulkan overlay. Including GUI improvements, temperature reporting, and logging capabilities. Metadata homepage URL: source URL: license: gpl3 platforms: linux\nI tried myself at this and have a working package now for NUR based on But I haven't yet figured out how to create a 32 and 64-bit version. Depending on the game both are necessary. To just get a 32bit version I currently just use: instead of just\nIt might make sense to just build the 32bit and 64bit packages separately and then merge them together in a wrapper.\nokay I did something similar, though not with a wrapper which is probably a little hackish I am not sure: but this allows me now to use mangohud with 64 and 32 bit applications\nThat seems like a reasonable solution, although it is a little bit hackish. I'm running into a similar issue with , and it's not really clear what the best approach is. recommended keeping the two builds separate for vkBasalt. However, to ensure we can install both builds we would have to do extra patching, and use separate names for the 32bit and 64bit build. Users might also expect to have both builds in one package like on other distros. I'm leaning towards something like this or like what I've done in my .\nwas just released but that changed quite a few things around. instead of using two different binaries it now uses  to decide where the 32/64bit libaries are, but it seems to me that this always expands to 'lib' on NixOS This is what I have so far. Having to ignore collisions is also not really that cool. Well having a running 0.4.1 version would be nice enough, just thought I write about this somewhere\nThe commit in question:\nI marked this as stale due to inactivity. &rarr;\nStill important to me."}
{"_id":"doc-en-nixpkgs-ffea68cd59c077ebc12ede578220fa2d5b3d55c0b43576fc5846fd99e2e28235","title":"","text":"blackbox-2.0.0 fails to build with test failures. Steps to reproduce the behavior: -env -i blackbox blackbox builds Please run and paste the result.\nDon't really know why this would fail on darwin\nfails on aarch64-linux but for a different reason"}
{"_id":"doc-en-nixpkgs-5738173aaed70b03aa1fac0c2e8bdf7c49928523b877480c8f61363ab1017571","title":"","text":"Project description Whisper is a general-purpose speech recognition model. It is trained on a large dataset of diverse audio and is also a multi-task model that can perform multilingual speech recognition as well as speech translation and language identification. Metadata homepage URL: source URL: license: mit platforms: all\nPTAL."}
{"_id":"doc-en-nixpkgs-f409bdd1fd587531537aece1ee47ff2433e2027499307610156d68618ed1a227","title":"","text":"For some reason, rasdaemon doesn't work. dmesg: systemctl: Steps to reproduce the behavior: rasdaemon should work. Unfortunately, ras-mc-ctl doesn't check if the daemon is working so it took me some time to discover that the daemon actually doesn't work. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nperhaps some build-time hardening is messing with it?\nLooks like the latest tagged version is broken on AMD because it doesn't include Now I'm running from the latest commit and it works fine\noh, thanks for finding a solution! i'll open a PR with that patch in a few hours unless you beat me to it :)\nadds that patch"}
{"_id":"doc-en-nixpkgs-91942a73a4d7479ac6d572d6ef687e3345403eafe756c4efe29b30cfee12f20a","title":"","text":"is meant to show the current timezone. It doesn't. (I have some reason to believe that this is connected to Steam game failures, but still working on that. In any case...) Set time.timeZone to anything other than UTC. Rebuild your system. Run The output will be in UTC, with no timezone shown: lists only UTC. System: 17.03pre92039. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: 17.03pre92039.\nI think this is because of this line: We can patch this to not check prefix, but still wouldn't work. For discoverability of timezones we can add to and look for them in but I'm not sure this is a good idea.\nSee ,"}
{"_id":"doc-en-nixpkgs-e1935d4e526e1c579ecf52a30a6856a7493fda3e8a5ea998d878aea504657783","title":"","text":"Describe the bug To Reproduce Steps to reproduce the behavior: Expected behavior no fail Additional context it seem to be fixed upstream, but no new release it made yet Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-8b4375d5d3bb7e5be445cc6ad4ef2472d0292526460714f3606d0c90bfacef4e","title":"","text":"When used through the command line, complains about imports and fails. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI've opened but haven't had the time to test it quite yet. If you get around to it before me feel free to merge it\nI suggest another fix in"}
{"_id":"doc-en-nixpkgs-f54d61059432063d29aa2e33d55991097364f18374a212ad698ec4930adda5c8","title":"","text":"Describe the bug I cannot install anything that depends on splinter (such as searx), as it doesn't seem cached and fails to build To Reproduce Steps to reproduce the behavior: Additional context this was on nixos-unstable ()"}
{"_id":"doc-en-nixpkgs-b82978e60eecc691ae933eecb8185668502db649d652503be51f9fc63919a6c2","title":"","text":"Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )"}
{"_id":"doc-en-nixpkgs-172fb2ea3dc0f1211498575edb61bcb911e81c3b0ab4e7110fe3cc911e53b863","title":"","text":"grub fails with nixos-rebuild switch -I nixpkgs=/home/lethal/nixpkgs\nThe issue title here is highly uninformative, which is why I didn't find this when checking for duplicates. :P"}
{"_id":"doc-en-nixpkgs-eec53659f4ba5ffbeb0bd0aee72ebfc8c57a13f33c24303ad0447d9327028a71","title":"","text":"I'm reporting this for a friend of mine who wanted to install NixOS and ran into this issue. I hope that's okay. The problem is: fails if you have in your host's kernel config (which, I think, is reasonable if you're compiling it yourself and don't need swap). I took a cursory look into and saw that it reads from . This fails, apparently, because the file doesn't exist on systems without swap support. Can this be easily fixed by assuming there are no swap devices if the file cannot be found?\nI'd say already assume this, but don't handle it gracefully."}
{"_id":"doc-en-nixpkgs-1f005bcbe9a6b3d7ff9b702eea736ec04919b26d8c04ca27763ba564f669b44f","title":"","text":"Describe the bug On current nixos-unstable Scipy fails to build with a segmentation fault during testing: To Reproduce Steps to reproduce the behavior: the following as Expected behavior Should not segfault during test. Additional context SciPY seems to build just fine on current 20.03 release. Notify maintainers cc , Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(ente): nixpkgs:\nAlso fails with\nParticular stacktrace is:\nI believe the fix is contained in: and upstream tracking issue is: and Debian issue:\nOpened to bump openblas to a version with that fix\nfixes this for me - can you confirm?\nbuilds for me\nWorks, thanks!\nThis still affects . Is there a simple fix we can backports (either in nixpkgs, or here locally)?\nBackport openblas updates:\nThanks, I’ll try that. Would such a backport be eligible to go to ?\nI don't really do backports, but since it fixes something known to be broken I assume it would be fine.\nPull request should target not ."}
{"_id":"doc-en-nixpkgs-0bd20df068de7da01e3735e612fa4dd37832def5e79086413611c93fccf04288","title":"","text":"ArmCord's wrapper seems unable to launch under Wayland, always chooses to launch under Steps to reproduce the behavior: sure and are properly set: Armcord: . ... 's on XWayland (as shown by ). I expect it to launch with Wayland instead of XWayland. Custom wrapper: Test case: Log output: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nprobably need makeShellWrapper instead of makeBinaryWrapper in the package\nThanks for jumping on a PR will review this evening."}
{"_id":"doc-en-nixpkgs-cc4a548fd0cfb6b7e7765f5cac6a6e74e30eed2a7adedf6e5777e59c7adef35f","title":"","text":"Project description Fragments is a modern, responsive and graphical Gnome bittorrent client Metadata homepage URL: source URL: license: gpl3 platforms: linux The new version of Fragments depends on libutp which hopefully gets merged soon. I've opened a pull request for it . for Fragments.\nWe have transmission and torrential. Maybe that's something for you.\nThat's true but Fragments is a really neat, easy and modern looking torrent client. It has an adaptive interface which would also work quite well on mobile devices, for example NixOS mobile :+1:"}
{"_id":"doc-en-nixpkgs-29e4b31badfc940063994b7da06ed856598c55de4a504a89843f751b14fbeadd","title":"","text":"I'm trying to use GZDoom, but the Vulkan backend isn't working. No errors, but it will silently fall back to OpenGL. Apparently this is the case if GZDoom can't find the correct Vulkan drivers. I have a Radeon RX 5700 XT, so my GPU definitely supports Vulkan. Steps to reproduce the behavior: basic without any mods <kbdesc</kbdthen <kbd~</kbdAt the end of its loading it should say what renderer it is using This is a screenshot of it running with Vulkan from someone else's system: ! This is a screenshot of what it looks like when it's using OpenGL: ! Note the lines. GZDoom uses Vulkan Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-5b8b34f4f9312a8e818b8d83e8f5fe3cde49f683456d78b74c6d9e3617e7b737","title":"","text":"The pan-0.139 package builds without gpg2, and as a result it produces a segmentation fault: The steps to reproduce happen to be the example from the \"Managing Build Environments\" section of the Nix guide:\nI can reproduce, investigating. Update is available (139 -144) so exploring that as well.\nHi, thanks!"}
{"_id":"doc-en-nixpkgs-b6ea841f379afe99afeed917e22b22dd36ee0872fc80bb4450ed32699235f6ee","title":"","text":"Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . nix-build '<nixpkgs' -A ... --check --keep-failed You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: nix-store --read-log $(nix-instantiate '<nixpkgs' -A ...) Seems to be a file ordering issue while generating : vs\nLooks like this list is generated with the standard Ruby function, which in 2.x leaves the sorting up to the filesystem, but from 3.x onwards itself. So perhaps we should just update to Ruby 3.x. In general 2.7 is in mode, so it will only receive security updates and we should probably plan to move things to 3.x"}
{"_id":"doc-en-nixpkgs-123829393930069415d9904447800401a8c966db2b48960252e152b20cb4681a","title":"","text":"The version of pillow rmfuse uses is vulnerable to CVE-2022-.\nSince 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.\nI 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.\nWhy 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."}
{"_id":"doc-en-nixpkgs-d98d63ae63b93308a02c12d13118b2222c209cb30aa52863c272253b1411cf07","title":"","text":"vkBasalt is a Vulkan post processing layer to enhance the visual graphics of games. Metadata homepage URL: source URL: license: zlib platforms: linux\nHello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as \"still important to me\". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at ."}
{"_id":"doc-en-nixpkgs-cdc07344f81d43e11466c6eead40935f4648ae53130d433c0452fa505f81b3c7","title":"","text":"default: cc Until then, just edit manually.\nRemember you can do this too: = [ \"/ip4/0.0.0.0/tcp/4001\" \"/ip6/::/tcp/4001\" ]; It seems reasonable to have this default, however, since the nixos module has no way of getting the daemon to reset options when the user removes an explicit option from Incidentally, some config needs special handling, since it can't be set without re-initializing the leveldb, etc. I don't like the idea of having to duplicate every default setting into a , but I guess there's no other way until the ipfs devs make the daemon's config less stateful. I would prefer they move this type of runtime config into command-line args whose absence indicates that defaults should be used. Perhaps we should file that upstream."}
{"_id":"doc-en-nixpkgs-41cd1901b1d686f771801b7df66a84f54310a0fd6a82d6b54c59293050ead388","title":"","text":"The script should report all sources used to build a package. It currently lacks support for patches? If we run find-tarballs on nethack, we should find the patch defined in nethack named we should get the url to download in the output, along with its name, hash and type.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI found why patches are skipped, they have \"postFetch\" attribute that has to be run to obtain the same file expected by nix. By applying this diff, patches are included in the result, but they won't have the expected checksum before applying postFetch on it. I don't know how to apply postFetch on the result right now.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-50de2949aa3f53eb18d0829ddfd27ff661bcef97ef00043d4e325b2f61ef8549","title":"","text":"This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nHi Opened PR for this."}
{"_id":"doc-en-nixpkgs-8be0a0a098c182f9f28bade8bc5f5bf704c65dcf4fc32b5c88967ac84a1cac27","title":"","text":"is built without X11 support on darwin because the Meson build file disables it. The GTK build system was changed to Meson by , and it removed the configure flags that enabled X11 on darwin: But the file of GTK3 disables X11 support on darwin, and : should provide X11 support on darwin. I was trying to fix on darwin and I found that is marked as broken () because of a missing GKT/X11 header. It seems that it is the same problem that motivated to change Vim to use \"gtk2\" (same missing header ). Maintainer information:\nIn that case I'd probably take the discussion upstream.\nIt was disabled in 3.24.9 by commit , without much explanation. But that commit never landed into master and GTK 4.x does build with X11 support as I understand ( and )."}
{"_id":"doc-en-nixpkgs-11862c58ecdf9f68e9ab680012bf52611e87269c02977f921e8327fa65a1c002","title":"","text":"Describe the bug peek fails to build on macOS To Reproduce Clone then Notify maintainers Log\nI marked this as stale due to inactivity. &rarr;\nsadly its not supported though getting keybinder3 to compile would be good\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-09a28b90cb2dac6d2d08d5817d16f5fdc6bbb356feff6282c545fc7fcce711bc","title":"","text":"Describe the bug seems to be unused in NixOS. Instead it seems to be a duplicate of . When greping for the option, only references of the later are found. Metadata Maintainer information:\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-908b3eedbbad67f28241ccb54998f54ea2d17606bbe5298f37676a0597ce3414","title":"","text":"Neovide fails to install via Steps to reproduce the behavior: up a terminal (currently I'm on aarch64-darwin, but I think this should be reproducible on different platforms) (or use home-manager/nix-darwin/nixOS) for it to give the mentioned error Neovide should install and run as expected <img width=\"1398\" alt=\"image\" src=\"https://user-\"(text form) Might be a result of this: Please run and paste the result. Maintainer information:\nCan you try this?"}
{"_id":"doc-en-nixpkgs-acfb4e7feefdedf68da4361d4a01cd78f525067b5e91d9c69377e196d25df0ff","title":"","text":"The meson build doesn't compile the schemas, opting to do it instead in a package shell script. Unfortunately it seems that compiling the schemas aren't enough to make all the extensions work. In particular at least and still won't work (seems to fix though). With the schemas installed Tweaks simply complains that the extension is incorrectly installed. complains about lacking any typelib file for . I'm not sure how well these extensions worked before 3.28, but a report on irc indicated that at least worked before. cc Run Tweaks on nixos-unstable, try to enable eg. the extension under or . Running a schema fix on top of system: host os: multi-user?: sandbox: version: channels(hed): channels(root): nixpkgs:\nThe extension works for me when I manually change the directory structure to: As for the , I removed from dependencies so that might explain this failure. The extension should probably be fixed like .\nYou're able to switch switch themes in in Tweaks? Might be something wrong on my end. I'll submit a PR fixing the schemas at least.\nTesting out a fix for .\nHmm, I can enable it but the theme switching does not work. I seems to require the extension schemas in when running Tweaks. Maybe it got picked up from global for bash users, but the option was always disabled for me with fish.\nWe might want to add as a dependency to Tweaks so that it could work for non-bash users. Then we will need to fix the schemas: the schemas in and find a hack similar to to add the schemas path to the extension. like the following to put the schemas where extensions can find them and add symlink for Tweaks. same thing as the second point but accomplished by patching files.\nYour suggested fix worked for at least :) I went with basically adding the code from to to fix the schema problem. Generating the directory structure you quoted above seems the most sane and keeping with upstream. Tested things out in a vm with bash, and didn't seem to work there either. So not sure if the problem is non bash. Anyway, adding to fixes , so I think that's appropriate. I should've got everything now, will submit a PR :)\nI think it only works in bash and globally installed packages or something."}
{"_id":"doc-en-nixpkgs-b66ac587919c34b68d8e55f748fd939f288f4863add5c49462c8ba286d9db67d","title":"","text":"I would not rely on it since I consider it an ugly impurity. I would prefer the first solution since it will be the cleanest and could be possibly automated in the future, but number two is fine too."}
{"_id":"doc-en-nixpkgs-375ee70b91cf87e2dfa6a70f79e42cf2195823409af1d632fa62d2a9fc373c4e","title":"","text":"flameshot has two backends, one that works in KDE, and one that works in wlroots-based compositors, but the flag USEWAYLANDGRIM must be set in order to enable it. Steps to reproduce the behavior: to use flameshot in wlroots-based compositor like sway It works [nix-shell:~]$ env XDGCURRENTDESKTOP=sway XDGSESSIONDESKTOP=sway QTQPAPLATFORM=wayland flameshot gui flameshot: error: Unable to capture screen flameshot: error: Unable to capture screen Wayland does not support QWindow::requestActivate() flameshot: info: Screenshot aborted. Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThe flag upstream:\nIt turns out that this flag is not yet available in a release. To use it, I created the following package override: and now flameshot works! For home-manager I also the following:\nNot sure I'd call this a bug if there's no release with this code, though it seems like it will be some time before the next release:\nI can confirm that the overlay above works for me. There's a small caveat: should be available in the PATH, otherwise the setup will be a little more janky.\nWhether or not there's a release, it's still a bug. There were more attempts to fix this 2-3 years back, but as you can read in that linked issue, the authors are currently not working on updates. Since there's no official release, it might not make sense to issue an interim package update, but as long as I have my working flameshot, I'm happy. I just wanted to share this with others who run into the same problem\nI hadn't noticed that... I've just updated buildInputs (to add grim) and removed grim from my default home-manager environment... I think that should take care of it, but I'll test to be sure.\nAfter using for awhile, I can confirm. You need to add grim into your environment in order for this to work consistently.\nI can't seem to get that to work on GNOME see\nYes, grim is for wlroots-based compositors, not mutter.\nUnrelated to this issue then?"}
{"_id":"doc-en-nixpkgs-3164cfaabe5e44ad81baff9b171255e9cdabd3fefeba85cdc40d9b806936369d","title":"","text":"-Krey, make a new issue?\nSure, but I don't know if upstream even supports mutter; doesn't seem like it based on , , etc.\nFor context it's currently broken, but it worked with the fix in until recently, so thought it was relevant to this."}
{"_id":"doc-en-nixpkgs-b56cd6ada43ea3fab4f2384171710b32be0fb391286fc403b3796a2f20bec0ed","title":"","text":"crashes as is fails to find the path Steps to reproduce the behavior: shows some info 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. Maintainer information:"}
{"_id":"doc-en-nixpkgs-35f33454871e2285e127ca62d9a9cc5db60ad5ee52223c304d7c166fb075695a","title":"","text":"Describe the bug doesn't work, either on or . It works on and I have a bisect running at the moment (on some slow hardware, so the results might take some time). It fails with this log: To Reproduce Metadata Maintainer information:\nThe first bad commit could be any of: jfsutils: fix build with glibc=2.28 ppp: fix build with glibc=2.28 oathToolkit: fix build with glibc=2.28 postfix: fix build w/glibc 2.30 libffi: only run tests on musl targets stdenv: rebuild aarch64 bootstrap files with gcc8 expect: remove hack for aarch64 build expect: fix aarch64 build seasocks: fix build w/glibc-2.30 bzip2: fix aarch64 build xnbd: fix build w/glibc-2.30 glibc: remove outdated patches rr: 5.2.0 -5.3.0, fix build w/glibc-2.30 diod: fix build w/glibc-2.30 libunistring: disable tests distrho: fix build w/glibc-2.30 glibc: depend on libidn2 (and libunistring, transitively) stdenv bootstrap: disable dejagnu tests gcal: fix build w/glibc-2.30 sharutils: fix build with glibc=2.28 drbd: fix build w/glibc-2.30 gnum4: fix build with glibc=2.28 xen48: fix build w/glibc-2.30 gnulib: - mono: fix build w/glibc-2.30 glibc: 2.27 -2.30 foundationdb61: fix build w/glibc-2.30 spaceFM: fix build w/glibc-2.30 cpython: fetch darwin- to nixpkgs xen48-{light,"}
{"_id":"doc-en-nixpkgs-96eb99d3cd8a97ff181f4fcd38c4b86e222c155eb226b42d393950c2ee67b11d","title":"","text":"slim}: fix build bootstrap-files: bump WIP Merge branch 'staging' into glibc230 Ignoring 'fix build with glibc' commits libffi: only run tests on musl targets stdenv: rebuild aarch64 bootstrap files with gcc8 expect: remove hack for aarch64 build expect: fix aarch64 build bzip2: fix aarch64 build glibc: remove outdated patches libunistring: disable tests glibc: depend on libidn2 (and libunistring, transitively) stdenv bootstrap: disable dejagnu tests gnulib: - glibc: 2.27 -2.30 cpython: fetch darwin- to nixpkgs xen48-{light,slim}: fix build bootstrap-files: bump WIP Merge branch 'staging' into glibc230\nstdenv bootstrapping of 32-bit ARMs is (hopefully) being fixed right now:\nThanks for the hard work"}
{"_id":"doc-en-nixpkgs-090aa222ce4d45f922f725e2ff4ea9d52c8ef668ab8a1f48e975cddec8e43eef","title":"","text":"I don't use at all, but I'm getting this error when I'm trying to rebuild my flakes (same happens when I run ) and also I don't really use it or install it Steps to reproduce the behavior: or Expect or to work fine I ran before running <!-- 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.\nBy grepping through nixpkgs, depends on by default. (see ). However, abook is only lists linux as supported (Im not sure if this this is just nixpkgs or abook in general) Up until , lbdb has not depended on abook by default. Perhaps a mistake was made while refactoring. In the meantime, you can just override the package."}
{"_id":"doc-en-nixpkgs-0fb7cb5ecacba46717c330a0d6afdf3adee573cb0e63c80b566fa1b373af8218","title":"","text":"Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: - -"}
{"_id":"doc-en-nixpkgs-2b0d5c1ef8fb8f6f22c44dd9f94f9a20bdd30c0b1ca8118303172add0c9de475","title":"","text":"The Linux stdenv sets But that flag is specific to GNU strip, and LLVM's strip will fail if passed it. Conveniently, we silence all errors from stripping, so this has gone unnoticed until now: I noticed this while trying to fix . One of the reasons it doesn't work is that it has in , and strip should be removing that reference but isn't. What I'm not sure about here is the best way to fix this. There's nothing platform-specific about this option, so it shouldn't live in the Linux stdenv. (Other platforms like NetBSD use GNU binutils by default.) Ideally it would be a conditional in the strip setup hook, but we don't really have a bash equivalent to . So where (in Nix) should we check this and set the variable? cc\nWith what we have at the moment, I can only think of hacky workarounds like checking if ends in . However such an approach (and even checking ) is actually incorrect: and don't have to be matched, e. g. with as linker and GNU bintools is quite common actually. Looking at prior art in nixpkgs, I'm quite convinced that the cleanest solution for now would be to bite the bullet and extend to also wrap . In fact, we already seem to have a strip wrapper for darwin.\nHmm, I don't like the idea of globally adding a flag only to remove it again in a wrapper. Another idea I had was to do this in the definition of make- — the hardening flags are precedent for doing manipulation of environment variables for setup hooks in there. We could add an isGNU attribute to the possible values of , and use that? I don't much like this idea either, but I like it better than adding the flag globally and then wrapping to remove it. What do you think?\nSince this flag is unconditionally in general, I think we can just remove it from the linux hook and instead add it in the binutils-wrapper. This should also solve the issue of this being binutils-specific and not linux-specific AIUI.\nOh, you mean wrap GNU binutils' strip to add this flag? That sounds fine to me.\nIf I understand correctly this is now done:"}
{"_id":"doc-en-nixpkgs-e2fef385739d722238a77c1a108d717436126979fc210de7ce87ccdedbdd1fbf","title":"","text":"Describe the bug There are reasons to want a system, that has no user that can log in by SSH or with their password, for example in a declarative container To Reproduce Steps to reproduce the behavior: up a minimal declarative container asserts that I will be locked out from the system and refuses to build the configuration with Expected behavior nix generates me a container that I can log in with , or maybe I don't want to log into it at all (because it's a disposable VM or something of the like). I think there should be a check whether the generated system is a container and an additional \"I know what I'm doing\" override for other cases. I'll create a PR once we agreed on what's best. Maintainer information: Code causing the problem: mentioning since you the check.\nIs it an option to set a randomly-generated (the hash itself would be generated, not obtained by honestly hashing a password)? Recovering the password from such a hash is probably harder than a lot of other attack vectors. But an override «doLockOutEveryone» sounds fine.\nSetting a password would certainly be a possibility, but somewhat (for lack of a better word) really lame. Having slept a night over it, I propose , that disables all the assertions at the bottom. I can see scenarios where two users with the same uid could be wanted. I want my unixoid to always give me enough rope to shoot myself in the leg.\nWhat about not enabling ssh and disabling the getty? It should completely lock anyone out, unless I am missing something. Take a look at the profile.\nIn case of a nixos declaratively defined nixos container, you are not logged out because the root system(d) can generate a root shell without any authentication, which is why I consider this a bug. Having to \"fool\" the assertion to actually lock oneself out is another matter, I could live with that but I don't think it's nice behavior.\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this."}
{"_id":"doc-en-nixpkgs-16abd9ad4b672810f2e52e21b7fac30c74d401a0fe5af20dc4582ca4f1340671","title":"","text":"Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .\nThis is still an issue.\nI marked this as stale due to inactivity. &rarr;\nFixed via"}
{"_id":"doc-en-nixpkgs-bdc899bebec4988739f8fa591ca1b8f45bd4d58150da8239425612db6e450390","title":"","text":"Package name: gnuradio Latest released version: 3.10.8.0 <!-- Search your package here: --- Current version on the unstable channel: 3.10.7.0 Current version on the stable/release channel:3.10.7.0 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nTnx. Update is proposed at"}
{"_id":"doc-en-nixpkgs-e91de60cb14060d3e176a0f536c2ca8dc32648f7dba68a648c373ba95c481e6d","title":"","text":"Project description From the project page: A tool to sign PDF files with Linux support. Why There appears to be a lack of applications that run on Linux and allow for attaching free-hand signatures to PDF files in a good way. (Non-)alternatives include: Xournal and Xournal++: Allows free-hand annotations but not saving those for later use. Allows inserting images and .pdf files but will rasterize them rather than retain the vector graphics, resulting in lower quality. LibreOffice Draw: Allows inserting images and .pdf files but will rasterize them rather than retain the vector graphics, resulting in lower quality. Okular: Allows free-hand annotations but not saving those for later use. Allows inserting custom saved stamps, but these will not be visible in other PDF readers. Evince: Allows certain kinds of annotations, but nothing that can look like a free-hand signature. pdftk, Ghostscript, and other command-line tools: Allows superimposing .pdf files, but not interactively selecting where. Metadata homepage URL: source URL: license: MIT platforms: linux\nWorking on it"}
{"_id":"doc-en-nixpkgs-7357d3e515fdef81d2897559f84d2c80e1167c9bc9440555f228969513cd3e50","title":"","text":", (nixos-19.03) (nixos-19.03) (nixos-19.03) (nixos-19.03) (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives.\nSee also\nCan be fixed by bumping the debian patchseries we pull from -6 to -11. Already fixed by the -6 debian patchseries. Fixed, indirectly, by the patches for CVE-2014-9638 and CVE-2014-9639 (above). This CVE was a fulldisclosure publication, so it didn't get triaged and fixed... But it is fixed. Conclusion: we can close this bug by pulling in the new debian patch series from 1.4.0-11 (up from 1.4.0-6). Sending PRs."}
{"_id":"doc-en-nixpkgs-c0aa189c929dc8c4b6a207b978d212a94c8a4a6957f177769627280d870aa538","title":"","text":"Describe the bug I need to list the out paths of cross compiled packages beforehand which causes an eval error. To Reproduce Steps to reproduce the behavior: Expected behavior List all out paths like `. Additional context I need this feature for nixpkgs-review when cross compiling. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata system: host os: multi-user?: sandbox: version: channels(user): nixpkgs: Maintainer information:\nI think its because of the lack of splicing for perl-packages. Note however, that when that is fixed, other package sets will fail with the same issue. cc\nProbably multiple issues. Have seen that problem with building xwayland for aarch64 too. Removing makeWrapper helps but probably breaks it :(. But the deps don't cross-build anyway so never got that far for now. Was thinking about opening an issue but got caught up trying to find the issue -- to no avail. Not currently at my machine, might post it later.\nI marked this as stale due to inactivity. &rarr;\nstill important to me\nFix in"}
{"_id":"doc-en-nixpkgs-3429661dd1dfed205d7bd7f8901212bad8d792b3f98177c4efaac2598fbba5c6","title":"","text":"Steps to reproduce the behavior: for the pipewire package, e.g.: building it This can be fixed by either making sure that flag controls the Meson option in addtion to the , or by exposing a new option to control the directly. ping let me know which of the options above you guys prefer and I can open up a PR to fix as well. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nCan we just remove that option instead?\nSorry do you mean set the to always be false or completely remove the as an option? Because I prefer the abilitiy to turn as many unnecessary dependencies as practically possible on my system (better stability and security).\nRemove the option, yes, because we can't realistically maintain the exponential explosion of possible flag combinations.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI made two PRs: and Feel free to pick whichever PR looks better to you\narg removed in\nHow much maintenance burden does this actually cause? IMO the package options are one of Nixpkgs strengths (one of the things that attracted me, after I stopped working on Homebrew because package options started to be removed entirely), and they're critical for people working on systems where size matters.\nTo expand a bit, I don't think that package maintainers should generally be expected to support all combinations of options, but I also don't think they should block people who want to from doing so. Just having the flags there shouldn't cause any problems for package maintainers that don't want to maintain the flags, and it's fine IMO to respond to issues about flags not working by asking people to adopt the flag and send a patch.\nNo one's blocking people from overriding. It's just a bad idea to have some flags we haven't even looked at in months and pretend we support them by including them in the expression. Or in other words, keeping the flags is shipping broken code if people don't maintain them.\nThe enableSystemd flag had clearly been looked at recently, because there was a commit from me fixing it, and yet it was removed anyway."}
{"_id":"doc-en-nixpkgs-d91befef6cbf231552b04684585add3c68d75e5a7b522c3af1f34c58b5a34eeb","title":"","text":"Describe the bug throws an error when attempting to generate the musicbrainz disc id: Notify maintainers recently updated the package in listed as maintainer Maintainer information:"}
{"_id":"doc-en-nixpkgs-805425fbc76aeaac93cddece2054bef09457ec10516cd1724492f4ecd69bdc39","title":"","text":"Describe the bug My server uses an encrypted filesystem /data that I have to mount manually after reboot. Gitolite is configured to use /data/gitolite. I have configured gitolite-init to only run once /data is mounted. Mounting of /data always fails, as gitolite uses to generate directories and thus the mountpoint is not empty. Manual cleanup is required every time. Expected behavior Gitolite should create its directories in gitolite-init.service. Additional context systemd-tmpfiles-setup.service runs before the system is fully initialized, so I cannot delay that service. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nI'll try to address this in the next few days."}
{"_id":"doc-en-nixpkgs-df71e16778d8aeb56a84c848a3810cb231e577c3a90a803a9e50876dd8d3f07d","title":"","text":"<!-- 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: dt-schema <!-- 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.1 desired version: 2022.12 <!-- 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.\nA new version is out: Should I just update this and my PR to make use of this new version?"}
{"_id":"doc-en-nixpkgs-868fa31c6bb92517d56780f4332126348bf6af3b1cf9d3a86878fe0e6f65bf70","title":"","text":"Project description Tile World 2 Metadata homepage URL: source URL: license: gpl2+ platforms: linux"}
{"_id":"doc-en-nixpkgs-b8dfb9ac7de21a8ef78d5da32dbd0c0bc94f6df732f9262930ed7fc75efe37a6","title":"","text":"Hi, i need to use open-zwave as a dependency for a build, but the version built in the Nix package is a specific fork for supporting home-assistant, which does not work for my package build due to linking errors. I will happily contribute a new package, but I'm not sure how to proceed, with regards to how it would fit in with this package, or if indeed the best way would be to modify this package to use the upstream repo. Pinging people who have maintained the package, apologies for the noise!\nHello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as \"still important to me\". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .\nWe should replace the package with an official version and make use the fork."}
{"_id":"doc-en-nixpkgs-2223c069d01196d45e45bc91d3a0b37757785e79ff4a841935495d9017be8525","title":"","text":"Describe the bug Tensorflow binary builds don't work on mac os. (neither do the source build, but that's a separate issue) To Reproduce $ nix-build '<nixpkgs' --show-trace -A python37Packages.tensorflow-bin_2 this derivation will be built: /nix/store/cc5p6r864smaf5mm8bqb9dbp6d7jkb3x-python3.7-tensorflow- building '/nix/store/cc5p6r864smaf5mm8bqb9dbp6d7jkb3x-python3.7-tensorflow-'... Sourcing python-recompile-bytecode- Sourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts- Sourcing python-remove-bin-bytecode- Sourcing wheel setup hook Using wheelUnpackPhase Sourcing pip-install-hook Using pipInstallPhase Sourcing python-imports-check- Using pythonImportsCheckPhase Sourcing python-namespaces-hook unpacking sources Executing wheelUnpackPhase Finished executing wheelUnpackPhase patching sources configuring /private/tmp/nix-build-python3.7-tensorflow- /private/tmp/nix-build-python3.7-tensorflow- Unpacking to: unpacked/tensorflow-2.1.0...OK substitute(): ERROR: file '--replace' does not exist error: --- Error\n--------------------------------------------------------------------------- nix-build builder for '/nix/store/cc5p6r864smaf5mm8bqb9dbp6d7jkb3x-python3.7-tensorflow-' failed with exit code 1 host os: multi-user?: sandbox: version: channels(noah): nixpkgs: yaml attribute: module:"}
{"_id":"doc-en-nixpkgs-f3ba2f59bc67e27ac93ba79a5ac54008a1bf2fc731c0faf14dd91838a2f796bf","title":"","text":"Describe the bug tensorflow-bin_2 wants gast-3.2.0 due to but gast has been updated to 3.3.0 so tensorflow refuses to install: To Reproduce Notify maintainers Metadata Maintainer information:\nThere are also other dependencies that fail the version checks: scipy==1.4.1 and tensorflow-estimator<2.2.0,=2.1.0rc0.\nThis compiles i'll test it, any feedback appreciated\nGot some issues\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nRelated .\nIt looks like fixes this."}
{"_id":"doc-en-nixpkgs-d46a75d78cbf6cb0599409aeb1363fb3031c210777ffce56b5dd776eb2af2b0d","title":"","text":"Package name: bibata-cursors Latest released version: 2.0.4 <!-- Search your package here: --- Current version on the unstable channel: 2.0.3 Current version on the stable/release channel: 2.0.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-e8f9a3a23efc4958a1b5982d1b45b87be560e7b35815bf144f1aa16d4b91c5ac","title":"","text":"<!-- 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: zotero <!-- 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: 5.0.96.3 desired version: 6.0 <!-- 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."}
{"_id":"doc-en-nixpkgs-52a54a72c01be2910e6fd3031b1bca03728cd8dfbda5c573f8f83df53a0d19ef","title":"","text":"It would be nice if we are able to have , in the same way we have , and the other completion siblings. I know it's easy to just and store in , but doing that we have to allow the user in question to write to that location (I don't really know the repercussions of any) and really defeats the purpose, somehow, of Nix Packages.\nas the modules (at least for bash and zsh) are fairly advanced it shouldn't be too hard. I'll try to have a look at it tonight %)\nHi, I installed on Arch Linux , but whenever I go into any Gradle-based project it doesn't work – as it works in macOS when I install it using Brew. It just doesn't discover, nor auto-completes any of the (currently available) tasks. Maybe it's not getting sourced into the shell? I do have also installed, not sure if that's an impediment (or not):\nI actually confirmed that the package is doing its job, however it can be possible that I screwed something up (e.g. something in my system config made it work). I don't think that I'll have sufficient time to look at this tonight, by I'll definetely keep this in mind and have a deeper look at this as soon as I have time to.\nI rechecked with the following vm config (which is basically the same as the settings I posted in my commit message): It seems to work perfectly fine with , however the validation breaks with (didn't test this, mostly use as it's easier to type :sweat_smile:) It shouldn't be too hard to fix this, I'll ping you when it's done.\nFor me, even if I try to use alone, when I hit (auto-complete) on the shell (), it does auto-complete what I have in the directory, which is fine, but I guess at some point the script(s) should take over the \"normal\" shell auto-completion.\nI'm fairly confused, are you sure that it's not caused by something else? I tested it with a VM from master and inside and work perfectly fine: What I suspect now is that it could be caused by your user profile. I'm not sure if actually pulls completion scripts from . Would you mind checking this with a VM or by adding to in your ?\nHi I'm using Arch Linux and the Bash shell."}
{"_id":"doc-en-nixpkgs-2ac570f3dca1340d4f4203b365d4038327dec3032eb760206d9f886354907541","title":"","text":"I searched within my \"home\" directory for this file: and I couldn't find any. I did find a , but couldn't find on it. My Bash shell is the one that comes by default with Arch Linux. I did the same on a virtual machine with Ubuntu . Let me know if you want more info.\nAh good to know! I've been testing on NixOS, usually which defines the system's entire state. But I'm fairly certain that this is related to living in , please give me som etime to investigate, but this sounds like a bug in the bash packages themselves...\nIt might be a bug because right now that I'm on it, I should also have auto-completion for Git commands (due to the fact that I have ), and it doesn't work either. I even to , but still, nothing going on there: Thanks for the effort!\nI see... Unfortunately I don't use the user profile for this so I might lack the required knowledge. I'd recommend to look for related tickets (or open a new one) as I'm fairly certain now that this is related to the integration of into ."}
{"_id":"doc-en-nixpkgs-7156ab47d5835df817bba15c06c28cef42ad0f7083f838709c4c8578f22d094b","title":"","text":"The gitlab service does rotate its log files which has potential of filling up the partition. Steps to reproduce the behavior: something that causes a lot of logs to be written. the partition runs full. Rotation of the logs similar to <!-- 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. Maintainer information:"}
{"_id":"doc-en-nixpkgs-2df34c38f77646b66f28523705d86925c1cf632d44c0e96a314e5e3554243a05","title":"","text":"Describe the bug Upstream intel-vaapi-driver removed the --enable-drm ./configure option. It is now turned on by default. Happened in commit To Reproduce Steps to reproduce the behavior: the package and read through compile log Additional context This is a warning, package builds just fine despite this. Metadata Please run and paste the result. Maintainer information: (I don't know if I am dealing with attribute or module. I think attribute, but just to cover all bases.)\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on ."}
{"_id":"doc-en-nixpkgs-8f96c94404f79a3b045fa48de45f91fb4f52577812b710903ff43642de5bd9c5","title":"","text":"Proprietary HTML5 videos break the whole site Workaround is to disable . Steps to reproduce the behavior: Vivaldi package with the package in your Configuration (home-manager) YouTube YouTube should display and the video should play. !\nI hit this issue myself yesterday as well. I had reported it to Vivaldi before I realized it was indeed an outdated chromium-ffmpeg dependency. See . I wrote a PR at to fix this. For a quick fix, here's the code I have in my overlay to work around this straight away:\nI just saw it. Thanks a lot! I will close this issue now as you already created an issue for discussion."}
{"_id":"doc-en-nixpkgs-a76e432a7e42b5c6ff3a1a8ac13ee97225060c3957674934a43f149b7785110c","title":"","text":"Package name: aws-workspaces Latest released version: 4.5.0 <!-- Search your package here: --- Current version on the unstable channel: 4.1.0.1523 Current version on the stable/release channel: 4.1.0.1523 <!-- 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."}
{"_id":"doc-en-nixpkgs-d4e4db62dec1726fc9b3d4f7a7e7aeb3d754829e2bd0b96f38193dd5a70adde3","title":"","text":"Steps to reproduce the behavior: Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-93a5327b7aa0b30d329f8413b062b99f74d9317088746979d4e60b51a1576d02","title":"","text":"When starting a VM I get the following error:\nThanks; this is indeed same issue. I am closing this one."}
{"_id":"doc-en-nixpkgs-b48f175e0b2d737ebe3d2d904c38db99d924d0393e7582f4b88e90fcea6e0989","title":"","text":"fails with the vdirsyncer version from nixos-unstable. it works if I install vdirsyncer with pip. Output of :\nWhich do you get via ? Is it the old 0.16 branch or the new 0.17 one (which was mostly rewritten in rust)? We have the latest git version of 0.17 in nixpkgs. Unfortunately, so it might be some time before this bug is fixed.\noutputs this:\nSame problem here. Was there any reason to go for an alpha release except for the issue referenced in ? If not, a downgrade to 0.16.7 should be fine, since the original bug is still open and probably won't be fixed for a while without anyone maintaining vdirsyncer.\nThere are , so I'd rather not downgrade. I'd be happy with a package for the 0.16 branch though.\nThat'd be great! I haven't looked into packaging yet, so it would take some time if I tried. Would you mind helping out?\nI just opened a PR. It’s my first time contributing to , so I hope it’s up to snuff."}
{"_id":"doc-en-nixpkgs-5931d439f5def7c615cdbff522f8c0e56dca4d5cd334b2f05695c657e11595d2","title":"","text":"There is a hash mismatch for kstars in nixpkgs-unstable Steps to reproduce the behavior: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nLast updated by\nAs was spotted during the PR review , the ref is a branch not a tag.\nThe source of the problem is (also mentionned in a comment) a typo in the name of the latest version of kstars files (). There's now a 3.7.0 version out. So I'll suggest a new PR with this version, using the official source"}
{"_id":"doc-en-nixpkgs-d065b273e5b70fd9c37d6e3ee2c0244e52c250e0e26a8c01fc82d05a26124078","title":"","text":", CVSSv3=9.8 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives.\nmerged - closing"}
{"_id":"doc-en-nixpkgs-b664a8a399bdf6d2efa5d11500a4aa8324c3ad5a326975ccb7de632d988cc27d","title":"","text":"Steps to reproduce the behavior: ferium cc thanks! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-aca73233ad0471178259bb292c1dae2063a0ed29d6b5f41ee457e79d519e1a83","title":"","text":"Project description A scanner informing the technologies and headers a website uses. Metadata homepage URL: source URL: license: GPL-2.0 platforms: Agnostic (Darwin, Linux, Windows) See also:\nI was able to build it, check it here\nThanks!"}
{"_id":"doc-en-nixpkgs-4072b57fc969536527a6513501c8c11ee2077a7e8c32eeeaa26124cb4a386f66","title":"","text":"Project description Metadata homepage URL: source URL: license: BSD-3-Clause license platforms: linux The version compatible with NixOS 23.11 is 1.3.3. Below is the code for this Python package, which might be useful: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nplease test edit: i tried to add a quippy command to test this, but the new nix cli doesn't construct python environments like the old cli did, and the old cli can't trivially use github pull as input..."}
{"_id":"doc-en-nixpkgs-addf30e4a5ad2c32e262ba7c915803f7e1a5b0e68a134ffda87e63ff54954ea6","title":"","text":"Element v1.11.0 updated to Electron 19, so we need this packaged in Nixpkgs: <!-- 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: <!-- 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: 18.1.0 desired version: 19.0.7 <!-- 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.\nWhen I run the script tries to download which does not exist. Do you know where to get the electron headers?\nPR that brings electron19 but does not provide electron19 headers:\nI believe that states that they migrated storage. So, I think the new url would be\nGreat find, thanks! Updated PR to include this change and electron_19 now provides the headers.\nelectrum_19 to master via - feel free to update your package"}
{"_id":"doc-en-nixpkgs-ba9b7115b5c2a7be9e860d2e333a9e1e6f2041cdbf357868c24c540a5294dc8b","title":"","text":"Installing causes large dependencies such as and to be pulled in at run-time Steps to reproduce the behavior: that some of the large dependencies such as are pulled in. I'd expect and to be build-time dependencies, and as such shouldn't be needed at run-time The additional dependencies are being pulled in due to , which itself should be a build dependency. FWIW, declares as a make* dependency Please run and paste the result.\nnot the maintainer for -qt ( is), but I took a quick look at it nevertheless and it seems that gets to in the invocation for even if it is moved to . Unfortunately I don't know enough about the Qt ecosystem to tell why this is the case.\nI think that the issue lies in qttools itself, for some reason after , qttools depends on clang and llvm at runtime This doesn't seem to be the case on and\nqttools provides a qt plugin so wrapQtAppsHook will add to ‘QTPLUGINPATH’ automaticallyUnfortunately, the packaging of qttools is not subdivided, all output is almost in one packagethis leads to the addition of unnecessary runtime dependencies. ( Actually even may not be needed is required by and , lupdate seems to be just a optional feature dependency on clangbut is not feasiblewe have to recompile to disable this feature Splitting into multiple packages should be a better solutionqdoc/lupdate are often used to generate documentation/translations, almost no packages runtime depends on them This pr should solve the problem of qalculate-qt but this may cause some packages fail to find lupdate. it‘s not an elegant solution\nI think it's easier to add a flag to qttools, and only use that variant for building the docs.\nshould be , set can prevent qttools from being recognized as a runtime dependency the pull request to disable clang-based c++ parser by default\nIf that helps, maybe is no longer necessary?\nFor this issue, yes But not sure if there is a package need qttools (qt plugin ) as runtime dependency\nI checked all packages that depends on qttools, and found that most if not all of them have a runtime reference on qttools due to it being in . So this problem is actually widespread, we can have the workaround in for now."}
{"_id":"doc-en-nixpkgs-d7790ee2ed0194a2bf7f742382028587e22b796cdf9012dda59a48f046e4da60","title":"","text":"Currently we have two expressions that both build the kernel, whose only interface differences are in whether or not the .config is generated or provided. These builds should be merged with the two different interfaces simply being two ways to call the same underlying function, reducing code duplication and allowing the generic kernel builds to benefit from the IMO better structure of the newer manual kernel builds.\n+1 on getting rid of duplication What is the \"better structure\"?\nStructure may have been the wrong word, but the manual kernel build uses multiple outputs (suboptimally currently, which was part of the problem with the old PR) and uses the official kernel build system for building and installing, while the generic one (last I checked) had a manually maintained shell script to handle the install and parts of the build.\nFixed by"}
{"_id":"doc-en-nixpkgs-809deb472c373aaa7619d4794d80a4fa81b1ce7bdc73d6a695816d43adf0870e","title":"","text":"For example: If this is called with instead of , it will fail to produce a output. This causes an assertion of the form: Unfortunately, doesn't keep the build directory around, making the source of the problem difficult to debug.\nThis is more of an issue for Thanks for reporting though!\nWhoops! Is there an easy way to move it?\nNot that I know of, sorry.\nFixed, thanks!"}
{"_id":"doc-en-nixpkgs-64ab5d265792e8067b2e203a3e433d7fcb56fcd94016af96e922faf73714748d","title":"","text":"migrated from python branch issue tracker\nI'm closing this as it seems no longer relevant. From what I could find, python-virtinst is \"CLI tools for building virtual machines using libvirt\". But it is now merged with virtmanager: <-- contains one single file named MERGEDWITHVIRTMANAGER"}
{"_id":"doc-en-nixpkgs-cbfe8c4f8049e7d886f7f68c942cd0bfc7e0c449893801cf5eb0f7dc9879e4be","title":"","text":"Our can no longer link executables. For example: This issue is present in current versions of . Compiling and linking works fine with an older revision, say . It looks like this might be related to some change in binutils, maybe?\nThis is probably from\nYes, it is. came to the same conclusion.\nThis probably is GHC bug though. Things like gmp and libiconv get their paths hardcoded so this isn't a problem. I would expect the same treatment for elfutils. should provide a arg.\n/cc\nI guess now I know why there's a patch in branch.\nI'll reopen the PR fixing the linking issues.\nI opened while we wait on upstream fix.\nWhich one, from\nYes, although it doesn't help. See\nYes, it would have surprised me a bit if it helped against that symptom -- my patch fixes that DWARF-enabling is skipped completely.\nI'm surprised this worked for you back then and now there are linking errors."}
{"_id":"doc-en-nixpkgs-6ec0400229b8781c83238f3a4db3c8a815c3f38df07984d4daff86bbd33e4131","title":"","text":"Steps to reproduce the behavior:  nixos-unstable Noticed when setting and rebuilding &lt;!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nYou won't get a reply if you leave that empty.\nI'm having the same issue I didn't notice when it happened, but I also have sambaFull\nSame error whit the package .\nThis seems related to\nThat turned out not to be the issue. The actual error: In colour so that one can actually make sense of C++ error messages: ! One potential problem here: This is because of having: Switching to : Builds Removing entirely (which swiches to ): Fails on new related errors (see below) Removing and : Fails because Ceph requires lua = 5.3 and nixpkgs's default is still 5.2: CMake saysCould NOT find Lua (missing: LUAINCLUDEDIR) (Required is at least version \"5.3\")` Build failure with : <details</detailsI noticed Arch . But we can just use to fix the build.\nPR for the"}
{"_id":"doc-en-nixpkgs-60ebccc2099774e6fb4706a4d6f532716e1727595dafaa1ecca180c388c63e05","title":"","text":"If I install , then I get version , which causes problems with Tiller image pulls. Alternatively, if I try to pull a specific version like this: Then I get this build failure:"}
{"_id":"doc-en-nixpkgs-7f19e5c1ba64f99e6e5a8d6266095c5cd1833e943883bb2dc9b472f1285754de","title":"","text":"TEXMF defines the order in which files are read in The idea is that TEXMFSYSVAR and TEXMFCONFIG files take precedence over files distributed with TEXMFDIST, so there is a way for the user to override configuration files. Our lists: This seems all fine, except that our derivation also makes TEXMFLOCAL point to TEXMFDIST as well, and this destroys override-ability. My suggestion is to use a separate and empty $out/share/texmf-local for TEXMFLOCAL.\nCould you please provide an example of the override that doesn't work?\nI dropped my customization here: It boils down to adding a custom package (minionpro availble for my ) and running: in postBuild.\nI investigated your override. I see that you sneak the original , then add your font to it and regenerate the mappings which go to share/texmf-var. At the same time our texlive setup just reuses prebuilt maps provided by (for pdftex), individual font packages and others and those are installed into share/texmf which happens to be also pointed by TEXMFLOCAL. I also now discover that the line does nothing for us. Your change makes sense to me. Makes me wonder if we could do better. For example, not deleting should not hurt anything. I could not find any way to automatically scan for new entries for The Gentoo documentation mentions [1] concatenating it from /etc/texmf/updmap.d. [1]\nFirst of all thank you for taking such a careful look at my code snippet. I really appreciate it! First, yes, I sneak out and later sneak back in. I do think that there are no adverse side-effects from not deleting in texlive.combine. I will submit a PR to remove it. This will minimize my postBuild override to just: That looks much cleaner :) As there is no real \"hooks\" functionality in our texlive package derivation, it seems to be a good idea to optimistically merge (by concatenation) separate snippets. I will file a separate issue to discuss this.\nThank you!"}
{"_id":"doc-en-nixpkgs-b1a894fb378a83cf542e2872e966c1a06e05d2d99afd096521f0a620fbde40fc","title":"","text":"Project description Halloy is an open-source IRC client written in Rust, with the Iced GUI library. It aims to provide a simple and fast client for Mac, Windows, and Linux platforms. Metadata homepage URL: source URL: license: GPL-3.0 platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-2f5d30854b898ad41d0868b9c76cfdbaf075918edad88ef32da4fd047af464d9","title":"","text":"Project description An open source implementation of the Tailscale control server Metadata homepage URL: source URL: license: bsd platforms: linux"}
{"_id":"doc-en-nixpkgs-b76bb00d983d89b34e029fb04b87e1ac9af79ab5d9b82cd1718e2640b0b873af","title":"","text":"Describe the bug To Reproduce Steps to reproduce the behavior: ... ... ... Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Notify maintainers and edited it last Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nI really have no idea, contains it, even bumping gnunet-gtk to be the same release version still doesn't fix it.\nHave you tried applying"}
{"_id":"doc-en-nixpkgs-bc3dac8c703a6a52f1193307222bddb57b086033aad207767aa91cba19068772","title":"","text":"Describe the bug hides clang arguments in a \"response file\" by default if is true, but ccache does not support this and responds with \"no input files\" instead. Additional context The following workaround can be used to disable response files in a result , fixing the issue: Notify maintainers Maintainer information:\nI've run into this issue as well. Edit: my bad, that doesn't work; we need the env var to be set before the outer layer of stdenv wrapper machinery runs. By the time we're in the ccache wrapper it's too late. It's also not clear to me if this is a bug in or intended behavior (I was not able to find an issue for it upstream) but it's definitely reproducible:"}
{"_id":"doc-en-nixpkgs-1684b0f62f52d915876eedde126bdc7a4b44d7c5ab289fc2bfa388f87fbddce9","title":"","text":"I tried to build a package with debug symbols today and failed. NixOS wiki and nixpkgs repository comments say the following should work: Please run and paste the result.\nIt worked in Aug 2018: Bisected down to breakage at : Looks like it stems from the fact that does not expose anymore, only . /cc\nWoah. master and both work for me with nix stable.\nThat's surprising. Here is my attempt at current master checkout: I tried removing and seeing the same failure. I wonder why it works for you. Might be a different stdenv?\nDoes it mean and are the same object?\ni can reproduce\nI can also reproduce with stable Nix (2.3.14):\nHmm, the issue is that / slaps the on after is defined, closing over the old . In Smalltalk paralance, this would be an issue of insufficiently \"late binding\".\nStill reproducible on current master ()\nI ran into this.\nBump, ran into this while updating the Nixpkgs pin on a project of mine.\nThere should be a test for this :)\nGonna spend next hour or two trying to fix this.\nThings that are also missing:\nSo, this function is not executed on passed through stdenv. Not yet sure why.\nYeah, I've fixed it (thanks, for being there :heart:)\nPost-mortem: always read threads. Solution was kinda already provided in , but I delved right in without knowing that)\natleast you now know more about stdenv :slightlysmilingface:\nHow is the PR looking? I've been waiting on this for a couple of weeks to debug an intermittent crash I'm having with xfce4-sesion :)"}
{"_id":"doc-en-nixpkgs-7308361b42068ef85e67e83c7a924f74a084cbace2e7e1a8232bb1c3f1dc035a","title":"","text":"Steps to reproduce the behavior: Happens on intel darwin. Please run and paste the result.\nThe .so dependency should be fixed up:"}
{"_id":"doc-en-nixpkgs-852da244516b18a35be56fe913dc72b43ac55e5f83d6af8238e6d9ceca36c6e2","title":"","text":"Steps to reproduce the behavior: msbuild Trying to build msbuild on a mac fails. <!-- 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."}
{"_id":"doc-en-nixpkgs-e0b6bbe65e31a020ebc476d963c1ac6aa7c6f962d4a0da8c2756ca9c4dfa6432","title":"","text":"Describe the bug when a root-owned process dumps core (eg recent sshd, due to a known bug) and coredumps are enabled, systemd-coredump warns (but proceeds successfully). To Reproduce Steps to reproduce the behavior: systemd coredumps enabled a SIGABRT to any root-owned process (eg by running ) Expected behavior coredumps succeeds with proper privsep Screenshots Additional context Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nCan you reproduce this with a simple c binary you interactively run as root user?\nyes, as root does it. amended the original post addendum: if you want a minimal C example that causes it:\nstill happening regularly due to a bug in openssh (race conditions in process shutdown can cause seccomp filters to trigger)\nI am also observing this problem, both sshd dumping core and the systemd-coredump error when it happens. I can also reproduce it with as root.\nI can confirm I see the log messages: I looked at . It seems systemd-coredump wants to drop privileges to a user (but falls back to root if it can't find it). suggests we should create it (like we create one for ). I opened , which does that."}
{"_id":"doc-en-nixpkgs-2642b22a4137495ea893425f39dd637d01b4d0b04664b18c5fd598f00b9cc835","title":"","text":"When I ran , it failed to build my configuration because dependencies couldn't be built. Relevant sections from and : Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs:\na full log might be helpful\nSorry, forgot to attach the log. Here it is:\nIt seems needs to be cherry-picked there...\nI've created a pull request for this:\nFixed by"}
{"_id":"doc-en-nixpkgs-1727b1d54ba5ab9f9aa0f139fc5a7bee2273760c7c2c6690f7ee9e7bfedcb8cb","title":"","text":"(the .0 version has a bug that breaks ) <!-- 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 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: matrix-nio <!-- The current version can be found easily with the same process than 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: 0.18.0 desired version: 0.18.1 <!-- 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."}
{"_id":"doc-en-nixpkgs-9fcc13521ff19923202deac29d29af52b7619b3aaa1c7c940de6db7ca89358c6","title":"","text":"RTS/game with programming on simplified C Metadata version: 1.3 homepage URL: source URL: license: GPLv3 platforms: GNU/Linux, Windows, IOS"}
{"_id":"doc-en-nixpkgs-e38f884c284b3fed6a1bd0c74a4f1f97991e630981d54024a785b993ca8c0696","title":"","text":"Project description Python 3 bindings of the , library for managing BTRFS file systems. This binding is part of the project. Metadata homepage URL: source URL: license: lgpl2Only platforms: linux (I'm not sure if it works on BSD or Mac)\nI marked this as stale due to inactivity. &rarr;\nSee"}
{"_id":"doc-en-nixpkgs-0e5c47ee9a4f498a3325dbc646145e7dad9506711d2ea44081e6670266a47cf1","title":"","text":"Project description Gorm is Golang ORM for SQL databases. Gen Tool is a single binary without dependencies can be used to generate structs from database. Metadata homepage URL: source URL: license: mit platforms: all? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-70b841aac4c3772c5081aedd61898c24c19d96cf9db36723f9cd0812de442941","title":"","text":"When attempting to create a volume on a physical node pool parted is not found. Steps to reproduce the behavior: Create a physical disk node pool. Attempt to create a volume using that node pool. In this case I have created a node pool called and I am attempting to create a volume called Volume is created normally. If applicable, add screenshots to help explain your problem. I have tried to add parted manually using and overriding the package in the libvirtd module: but this did not fix the issue.\nThat won't work, it seems like we need to wrap to include in its . I'll take a look.\nYou most likely need to add it to in because libvirtd will probably call it."}
{"_id":"doc-en-nixpkgs-4f090997f40f0753761089fc3d6e7b421389fd4187461a09773f78d97a4d0cd5","title":"","text":"I sometimes create a qemu VM in libvirt in \"session mode\", meaning that the libvirt daemon is running as my non-root user, and the system-wide libvirtd does not need to be running (). This VM has a network bridge, which libvirt apparently creates by calling , which in turn uses . The problem is that doesn't get fully populated until the system libvirtd gets started. Previously, in nixpkgs (from February), this wasn't noticeable because libvirtd.service was WantedBy libvirt-guests.service (which is WantedBy multi-), so libvirtd would always be started on boot to populate that directory. Now, with , this is no longer the case, and libvirtd.service does not get started (presumably, if libvirt-guests.service actually needed to start a VM, then libvirtd.service would be socket-activated, but for me this is not the case). As a result, doesn't get populated and my session-mode libvirt can't find . python: The VM's XML file defines a network bridge, which is why gets involved. the following output: The libvirt user session should be usable without first starting the system-wide libvirtd. If you start (and optionally stop) the system libvirtd.service before following the steps to reproduce, everything works fine, because the directory gets populated. Probably, should be put somewhere else, where session-mode daemons can use it without needing to have previously started system-mode libvirtd. (The same may be true of other stuff in too.) libvirt maintainers: Okay, but I'm using flakes and that channel looks old. See relevant commit hashes above.\nOof, happy to find this, it would have taken me a long time to figure out I needed to run first. Can't the sudo wrapper point to the file in the nix store?"}
{"_id":"doc-en-nixpkgs-0147c5c64c74d3ceaadd7a5706655b173221afbbccd3d5708ec1a087437b62b5","title":"","text":"It is possible to use Plasma’s native file dialogues in Firefox 64 to open or save a file. Currently this feature is not working in NixOS, and it seems to me some small changes would need to be made to derivation in order to enable it. I propose we include this option together with as a Firefox option in NixOS (see also: ). I followed the explanation on how to enable this feature as it was published on : Firefox (64 is current stable) from a terminal emulator But it produces the following error: system: host os: multi-user?: sandbox: version: channels(root): channels(hook): nixpkgs:\nYou'll probably have to do something like this to expose the dbus service:\nWhere? In:\nIt needs to go into a nixos module or your ."}
{"_id":"doc-en-nixpkgs-86920eea86c816e795001e744fb6f7640d3bc525c4863d3a8bc693116931bb58","title":"","text":"Directory renaming is now out of scope This directory is also being used as the way to get access to the host machines gpu drivers. I think it's another source of confusion for many users to have to add so that they can get a vulkan game / cuda workload / opencl workload to work. I think we should deprecate this prior to the 21.11 release, and fully move it to something like or something more representative of the desired affect. This was done in cc EDIT: roadmap (2.5 years later... lol): addOpenGLRunpath -addDriverRunpath Init addDriverRunpath: Deprecate : -autoAddDriverRunpath Init autoAddDriverRunpath: Deprecate cudaPackages.autoAdd{OpenGLRunpathHook,DriverRunpath}: NixOS Module changes: TODO\nFor the transition period ( NixOS 21.11), I think keeping the old would help alleviate a lot of the pain, would just like to get the ball rolling away from using explicitly\nI agree. Also, on a related note, having to specify your graphics driver at the xserver level in the module system feels wrong to me. I'm still not exactly sure how it maps given names to driver packages either.\nI propose two changes: move -- make a symlink to for backwards compatibility of existing derivations -- add a\npotential future work as well: -- Until 21.11 EOL, have it add both and , to avoid system vs package invariance\nI'm also kind of wondering whether is just another fallacy in naming, and we should really be exposing something like, would be even more appropriate, as other hardware-accelerated devices such as tpus, fpga's, and others would also likely need to import \"libraries which are determined by the system, and need to be available at runtime\".\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nShould we, in addition, consider using a libc-versioned directory? Motivated by\nDecided to rename this issue since renaming the underlying path was deemed too risky for potential breakages.\nCould you provide some context as to why? My naive assumption was that we'd have a new path but: have both new and legacy path to rpath via the hook; new path preferred provide a legacy symlink pointing at the new path in NixOS which would be quite trivial."}
{"_id":"doc-en-nixpkgs-745ec59b774b6a01f7c4e4e3c9b0e7b7d04d932eed45b1a2c8dc29ddfe2f65b2","title":"","text":"TBH, I'm not sure how much value there is to migrating the filesystem path (unless we splay the paths further to increase granularity). I suspect what users see in practice is the nixos option path\nFor the NixOS module change, I came up with these terms: acceleration API = an API standard which intends to provide hardware-assisted compute acceleration such as OpenGL, Vulkan or CUDA driver = userspace library component which implements one or more hardware-based acceleration APIs The usage of the NixOS options API would then look a little like this: Individual drivers would also have a option which is a package selector for the specific package to use aswell as driver-specific settings. (More on the package selector data type when I have a more concrete implementation but it'd allow setting 64/32 bit using a single value.) Each acceleration API would have a option which is an attrset with driver names as keys and package selectors as values. These could then be overridden indivually. The intention behind this is to enable use-cases where e.g. different versions of the same driver are required for different APIs or a specific driver must be disabled for one API but enabled in all others. All enabling a driver would do would be to insert the driver's package into the options of all APIs that it implements. Additionally, accel APIs have a option if the API supports setting one and of course API-specific knobs. Here's an example of how a non-trivial driver config could look like: It's currently not possible to know which implements which driver and all drivers are thrown into the same directory but the NixOS API drafted above requires this information for fine-grained control, so we will have to define an interface here. I've been thinking of defining the output to contain all driver bits and subdivide it into driver subdirs like this vulkan/... cuda/... opengl/... Alternatively, I had thought of using multiple outputs; one for each driver. I kinda like that approach more as it generally strikes me as cleaner and has the potential to reduce closure size ( is ~200M) but am not sure about potential naming conflicts or other downsides of those. In light of this, I'd also like to propose to split the global lib dirs into accel API subdirs for clean separation. Though as said, the NixOS options are a lot more critical to UX and therefore the first steps."}
{"_id":"doc-en-nixpkgs-e0ca69c9f45063a2c9d86558c924187fa8b1e8ce1b1b636fd7f9c6c7199f187a","title":"","text":"Global path name and other changes are almost entirely tangential and could happen independantly but I'd appreciate if they came after the NixOS options changes such that we can let the knowledge we gained from the NixOS options influence their design. Anyhow, that's my current draft. Let me know what you think.\nMy naive assumption was that we'd have a new path but: That was my initial take as well, but there's community projects like nixGL and others who likely have hard coded the path. And there's a potential that we could never fully remove it without breaking someone\nForgive my ignorance, but wouldn't it be ok to make those kinda breaking changes by deprecating in one release and then removing one or two releases later? Surely nixos isn't promising to never change paths because someone might be using the old location? EDIT:I don't mean to imply we shouldn't consider non-breaking options where possible\nnixGL only sets the LDLIBRARYPATH? Although in all probability we must break someone's workflow... Fun fact: cudaPackages don't ship the driver (except for for jetsons). All the relevant stuff comes with nvidia_x11 or with the datacenter driver. Interesting. Would we somehow have to filter the glvnd/opencl loader/vulkan loader configs that come with the drivers to enforce that the declarative configuration be implemented?\nnixGL appears to be actively maintained. I don't think we need to worry about breaking it as they can simply adapt. Also, we could simply keep providing the old path in both NixOS and binaries with a preference for the new path and that should work out fine. Oh, okay. I'll leave it to you CUDA people to figure that out. I will only be lifting drivers to this interface on a best-effort basis and the rest will keep using their legacy interface with a minor implementation change. Though if you forsee possible issues you could have mapping your driver to this interface, let me know so that we can design the interface better from the start. That or simply write our own. Though I'll only be adding the option where it is feasible; currently, I only know that Vulkan has sane mechanisms for this. Some issues I still need to think about:How to handle drivers that only support 64 bit?"}
{"_id":"doc-en-nixpkgs-0624fd87929db0b6eb5da997829c01a9a71f31b0a2929a6b7657509bb4d6048d","title":"","text":"Will have to filter that somehow How to handle APIs that can only have a single exclusive driver? Only have a option on the API, rather than ? Have but only install the default driver?\nI think NixGL doesn't care about , it probably just exports an ?\nThe original protest against renaming the path: I feel more strongly about the NixOS options being intuitive than the implementation consistent.\nI think was more concerned with it being placed under rather than some other directory in because is very much NixOS-specific while the current is not.\nI believe I got all of the packages. Once merged, I should be able to deprecate\nThis thread is over my head, but I would like to check it , , and need the same? All three have GPU or CUDA support options.\nThis is more about deprecating usage of the term , as it's a bit of a misnomer. I don't see usage of the legacy OpenGL helpers in those packages.\nTalked to , we concluded that we can close this ticket and have a more \"NixOS options\" specific ticket to represent that work.\nGoing to do one last pass on documentation to ensure all references have been updated. I'll close this ticket after that sweep\nI wonder if needs an update. I'm not offering a PR because I'm out of context. Arrived here from a warning in nixos-rebuild. And I'm still wondering how this is being triggered [still investigating].\nArrived here from a warning in nixos-rebuild. And I'm still wondering how this is being triggered [still investigating]. It should come from the toplevel scope now, so it should never need to default to pulling them out of cudaPackages. I can update the nix expression though."}
{"_id":"doc-en-nixpkgs-bddcf3f5554a923368d314bf4cf3862d5979f893506d071d682561a9f04ed2fb","title":"","text":"Project description udev rules to make supported controllers available with user-grade permissions Metadata homepage URL: source URL: license: mit platforms: linux"}
{"_id":"doc-en-nixpkgs-a16c173a8ebe9ddd7ed3d9d2924c043eff7f69ecdf8d5b5d844b47fe0a6eb951","title":"","text":"Currently it's only possible to configure kanata by specifying specific parts one at a time. It's not possible to read a configuration from a file and use that instead of the specific parts. I use HomeManager to manage the kanata configuration file and because it's also used for Windows this is the most platform neutral way for me without duplicating parts of the configuration. As a workaround I did it like this for now: But clearly that is not ideal. What I would want is to just keep the 'readFile' and uncomment the 'defcfg' part from the configuration file ()\nI created to address this issue. Could you help test it?\nThanks a lot for the fast solution! I tested it with my config and it works without any issues."}
{"_id":"doc-en-nixpkgs-74483d13e38d234ec30379799b7bb9778dc75bdffa75aaeee5d033fa45ac8604","title":"","text":"Project description A lightweight cross-platform build utility based on Lua Metadata homepage URL: source URL: license: asl20 platforms: unix"}
{"_id":"doc-en-nixpkgs-65e982adfdd34d1b360ee68c33933b7da9a548cb9fa3b63cf6c6eb65b1015e45","title":"","text":"Package name: jextract (jextract-unstable) Current version on the unstable channel: 2023-11-27 Current version on the stable/release channel: n/a As of today the current release build is (see ) It would be nice for the nixpkgs version to be based on JDK 22 -- which contains the final non-preview release of Java Foreign Function & Memory API (aka \"Panama\") There are significant changes to that users will want before building/launching projects that use Panama. See: I am wiling to contribute but before we can do this we'll need to build with JDK 22 (see Issue )\nIt would be great if we could update to be based on JDK 22 :+1: , and we should also keep the current JDK 21 package as a new name (perhaps ?) at the same time, as some downstreams still depend on it and JDK 21 is a LTS version.\nSo should the first step be to rename the existing package? And leave as JDK 21-based (with a warning, maybe) and then do a separate PR to upgrade to JDK 21?\nUpdate: There is a PR for JDK 22:\nI can open a PR to update jextract after gets merged. Considering the significant API changes between JDK 21 and 22, and the fact that jextract itself produces very differnt code if you have to use JDK21 (see ) , is there really value in keeping a jextract version compatible with JDK21?\nAwesome! I'm going to test on macOS/aarch64 this weekend, so that will help get it merged. wrote: as some downstreams still depend on it and JDK 21 is a LTS version. JDK 21 is LTS, but Panama (Foreign Functions & Memory API) is a \"preview feature\" which makes it really hard to build anything real with it (i.e. publish JARs for use by other projects. I even had problems with a Gradle multi-module build). I migrated my project to 22 a few weeks ago and am not looking back (which meant I had to stop using Nix as a source for temporarily.) But, I don't see any harm in renaming the existing to and starting a new one. And we certainly don't want to unnecessarily break anyone's dependencies."}
{"_id":"doc-en-nixpkgs-81f462fe9ac1573bf053b4036350a3249290a89edd9a61b28359ad53e5c757f1","title":"","text":"And now that Panama/FF&M is final, I'm hoping it will be possible to use jextract 22 to build headers for JDK 23+. Newer versions of jextract might offer improvements, but headers generated for JDK 22 should work wth JDK 23+ (I don't know what guarantees the JDK makes for that, but this seems a reasonable conclusion given a stable API.)\nNice to hear that, and thanks for your work! IMO, I think it's worth. The point is that JDK 21 is a LTS version, some downstreams prefer to use a LTS version of JDK to develop their projects. For them, if we don't keep JDK 21's , this will be unavailable to them unless they give up on choosing LTS and do some extra effort - porting their project to a newer version of JDK.\nI agree. But I also strongly encourage new projects to start with JDK 22 and existing projects to migrate as quickly as possible. Having to make sure \"preview mode\" is set in the compiler and at runtime can cause various problems with tools and the output of the latest is significantly improved. In general, it's much better to be using a non-LTS JDK with a non-preview feature than and LTS JDK with a preview feature. I migrated my project recently and wish I had migrated to JDK 22 much earlier.\nPR has been merged. I gave it a quick test on macOS/aarch64 and it seems to be working. (I used it to build which uses JDK 22 and Panama via Gradle's Java toolchains)"}
{"_id":"doc-en-nixpkgs-87b74f3e4cad3721e39256a6077292acede47da1bb6389ddcfb80ee7315b1c1a","title":"","text":"Invoking is producing the following error message: is part of the package so it's just failing to locate it. I'm running on NixOS Unstable.\nI believe this issue has been fixed and can be closed:"}
{"_id":"doc-en-nixpkgs-ade1cc95f46d9cf36a6140b0a6c75880127fbebc7c192dd71c6885858f6fe0c3","title":"","text":"Travis has been giving build failures because of this: commit seems to be at fault here.. The reason I didn't just fix this this bug and push upstream is because there are two different ways to approach this and I'm not sure which the best course of action is. a) jfsrec removal was intentional, remove all references to jfsrec b) restore jfsrec Here is a listing of all current things pointing to jfsrec:\nThe jfsrec commit has already been reverted.\nthanks for the info"}
{"_id":"doc-en-nixpkgs-2d7f9eaa70940c572f7906af66d62dcb0810fd2ae7ff475248823382faefb249","title":"","text":"nixos/modules/services/x11/display- has code to load ~/.Xdefaults, but not ~/.Xresources, even though ~/.Xdefaults is the deprecated version of ~/.Xresources"}
{"_id":"doc-en-nixpkgs-e1fe2fa73c60e4baf2fd8994dc48caf2660fed8428d8299b2a0f1079b4d727bd","title":"","text":"In its builder, there's a command saying \"Need libgcc until the llvm compiler-rt library is complete\". It's from in 2011, so I'm inclined to think it's out of date and that the dependency on gcc is spurious. Is that true?\nFor context from #llvm on oftc:\ncovers , covers , the only thing I'm not sure about is the C runtime files (e.g. ), none of those packages seem to come with them (but maybe clang does it another way)\nActually some of the files come from glibc, but these ones come with gcc: crtprec32.o crtendS.o crtbeginS.o crtfastmath.o crtprec64.o crtbeginT.o crtprec80.o crtbegin.o crtend.o\nThis story is quite old, is this still true?\nClosing because no reaction."}
{"_id":"doc-en-nixpkgs-e2f02ed52585931c00d116a10076b8e9045aa3f3716dd42268cae74f0a5e0f41","title":"","text":"Package name: clickgen Latest released version: 2.1.9 <!-- Search your package here: --- Current version on the unstable channel: 2.1.3 Current version on the stable/release channel: 2.1.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-9dec6b20cdd112282bd63a6eede2e9a20f807b9621cf5c04fe72e2d2809da559","title":"","text":"There is a bug in the latest release of quickemu (present in nixpkgs), that sends invalid flags to qemu and thus doesn't work for MacOS (maybe others too). The fix I was planning to PR was to simply move the src to point to the most current revision. I wasn't 100% sure if that was something that I should do however, given it would set the precedent that we follow revisions for this package instead of the version tag, which may add maintenance burden. Just wanted opinions before I made a PR, would it be acceptable to bump the revision temporarily to avoid this issue? It's niche but its real and could affect users of this package. Steps to reproduce the behavior: Pops open a Qemu window with the appropriate screens. Fails with a strange \"macos-ventura/macos- file not found\", but it is related to the bugged release. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nDon't know of any official policy on this. My opinion: If it's a single commit that fixes the issue, you can add a patch. If it's spread out over multiple commits, use current unstable, but that may introduce other unknown regressions and breaking changes. And in any case we'd go back to the release tag on the next release.\nPatching sounds like a good idea, hopefully it is just one commit. Though honestly from personal testing the newest release worked perfectly fine (I tested via an override)."}
{"_id":"doc-en-nixpkgs-da3644f045a46e465af9525a14c3f1755f3bcff8480fa555c1eed00543282c02","title":"","text":"is non-deterministic if given both and . Here are a couple runs back-to-back: However, when I make this and :\nInterestingly, itself is deterministic, despite being non-deterministic (at least from the command line). This is pretty curious.\nPerhaps environment variables come into play? Does the shell script take care to clear the environment like a nix build does?\nSo, I tried diffing two of the outputs: That looks an awful lot like part of my git hooks that automatically generate tags. Sure enough: I'm of the opinion that we should override in the package, to prevent these kinds of problems. Thoughts?\nSeems like those scripts in general should almost completely clear out your environment\nYeah, I don't know how much to get rid of, considering that someone may want to get the hash of their private repos or something."}
{"_id":"doc-en-nixpkgs-7e63ee9cc709d735dcbc93762f2553bf8e73b293d95d08deccb22bd58c1d1655","title":"","text":"This issue is mainly a note to myself since the upgrade won't be trivial and will need a lot of testing. Protontricks is now using the Pressure Vessel runtime, so I have to refactor my patches with steam-run to account for this. <!-- 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 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: protontricks <!-- The current version can be found easily with the same process than 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: 1.4.4 desired version: 1.5.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: myself"}
{"_id":"doc-en-nixpkgs-cc6203f80e09cbf793be2db27e65f69af1a394e1ae65d2c8d8f4017e48303ca1","title":"","text":"<!-- 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 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: <!-- The current version can be found easily with the same process than 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: desired version: <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: are you already working on it? if not i can do it\nI have some exams to take tomorrow, so maybe I cannot open a PR in 17 hours. Feel free to open one if you have done the update.\nI just wanted to make sure you haven't started to work on it, so we don't do duplicate work. I wish you great success with the exams!\nJust also have a try on this, fails with . Actually I have no idea what happened so I just opened , downstream workaround should be something like , actually this seems to work, builds and launches. <img src=\"https://user-\" width=50%Also I noticed that we maybe need in , haven't tested yet.\ndownstream workaround should be something like , actually this seems to work, builds and launches. i don't understand what it does, but it works Also I noticed that we maybe need in , haven't tested yet. I noticed before that the indicators do not work. I'll try it."}
{"_id":"doc-en-nixpkgs-0e3687b61940648e3adf44f14b3537bfe1645297dc63985cc9ce4b21d46d89f7","title":"","text":"Isolates parallelEach doesn't work Steps to reproduce the behavior: run nix develop with then run: dyalog then in the dyalog repl type ⎕DL isolate.llEach (1 2 3) returning like its the case when using the .deb on lets say a debian host strace log reveals a lot of lines like which does not happen on a debian host when I install dyalog 19 via dpkg -i I have also tested this on a debian host that has nix installed and installed dyalog via nix instead of dpkg but I run into the same issue making me believe there is something wrong with the drv system: \"x86_64-linux\", multi-user?: yes, version: nix-env (Nix) 2.18.2, nixpkgs: /etc/channels/nixpkgs (I ran it against the current (1 hour ago) nixpkgs master/unstable branches) as in I pulled these 2 about 1 hour ago\nI'll see what I can do about this. In the meantime, could you change the issue title to start with ?\nsure\nPhew, finally found it! The issue was with the class, which auto-crashed when created. I redirected its output to a file, and it turns out that because I didn't patch to require it wasn't able to load it, thus erroring out.\nThis is awesome, thanks for the incredibly fast response/fix time. I suspected it was something like this I initially thought that maybe some of the libraries weren't copied over since the nix expression is a little pickier than just cp *.so $out/lib but upon fixing that nothing change really. Usually knowing when to apply patchelf is quite clear as software will let you know if a library is missing so throwing ldd against it generally gives some pretty good insight. Though if you'd like sharing this information, would you mind telling me how you found out? Was it just intuition or did you use some sort of tool to debug it to come to the conclusion that this may be the issue. As i couldn't really get hold of logs making any sense when I tried it. This would be quite interesting to me as I most likely will get to fix more dyalog stuff in the future."}
{"_id":"doc-en-nixpkgs-a8e229b65ffee80eae717c782ae84bba5ea0454d03cf93b920dd25fa720afb00","title":"","text":"First of all, I somehow got my hand on the file that lists where it crashed exactly, then looked through it, found the definitions in the namespace explorer. It looked like it was supposed to start some processes and then connect to them, however they exited immediately. I was able to verify this by printing in . is an array of new objects, so I looked up the docs, and it turns out you can specify an OutFile, which specifies where a process should dump its logs (its the 5th parameter of ), so I overrode that to point to some known location. That file contained the following: In was required by the binary, so took care of it. However in they probably changed it to load dynamically using which can't be auto-detected with . I had to use with the normal binary to make it work, but I didn't know what was so I didn't do anything with it. Note: in a new binary named appeared, however I don't know where it's used, so I don't know what I should do with it. Might have to ask around for it.\nthanks for taking the time to outline how you came to that conlcusion im sure that will help me in the future. Sorry for forgetting to close this its closed now\nWell, the fix isn't merged yet, so I think that this issue staying open was not a problem.\noh sorry I forgot as I used the branch locally and then after many weeks I saw its still opened and somehow was under the assumption that it was merged. Sorry I skipped that"}
{"_id":"doc-en-nixpkgs-935f8eb36a9b85ac42e9d47f23589af752ca7edba7b3a7cdd62a5a359fb7ec33","title":"","text":"(this is a qt specific test): Loc: [t-(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 1047ms This seems to affect master too, but for some reason it's been built successfully once. The aarch64 build started failing when updating qt5 from 5.11 to 5.12 making it the likely root cause: Edit: the cause was expired testing keys: cc maintainer cc as you've been active in keeping plasma/kde up to date lately. ping staging next:\nDid you found ? Sounds very similar and should be fixed...\nNo didn't find that, but yeah, that sure looks exactly like the same issue. I'm guessing the qt issue were never actually fixed: Blame on the test gives no change at least:\nAnd applying the suggested patch does fix the test: diff +++ gpgme-1.10.0/lang/qt/tests/t- -455,7 +455,7 private Q_SLOTS: QVERIFY(result.numSignatures() == 1); auto sig = result.signatures()[0]; QVERIFY(sig.validity() == Signature::Marginal); QVERIFY(sig.validity() == Signature::Marginal sig.validity() == Signature::Unknown); auto stats = ().userID(0).tofuInfo(); QVERIFY(!stats.isNull());\nSo, what are we want to do? Do you maybe want to comment on the upstream issue?\nHmm, strange, I'm getting the same failure on master (using ), forcing single core does not fix the problem though, so probably not a race condition. I've reported the failure as you suggested:\nThe cause is most likely qt 5.11 to 5.12 upgrade, as the aarch64 build started failing the test then:\nSo the keys used in this test expired on 2019-01-06, which explains why we suddenly saw this without any apparent reason. :\nThanks for fixing this and sorry for my late reply... (Edit: And of course also thanks"}
{"_id":"doc-en-nixpkgs-ee4ace808e52d98014ec2c32ad46d28bcf4f5300643309b641a0cbf3f7246afc","title":"","text":"name: didyoumean current version: 1.1.0 desired version: 1.1.3 maintainers: Version 1.1.3 comes with a man page as well as shell completions for a few shells (bash, zsh, fish, elvish). I'd like to have the script install these. I'm more than willing to do the actual update myself, but I'm very new to Nix, so I'll probably need some guidance, specifically on how to install these completions and the man page, and how to update the hash. Thanks!\nTo update the hashes, simply set and , and update them as suggested by . Having done it right, you'll haveTo install the man page and the shell completions, setYou may also need to set on some platforms (at least on ?). Before doing this, feel free to make a pull request.\nI'm running into some issues trying to test it to ensure it's doing what I want it to. I'm going to the directory with in it and running but I'm running into issues regarding being undefined: Any pointers? I wasn't able to find anything searching through the web\nneeds to be in the attrset at the top of the file for you to be able to use it.\nAs explained, we need to add at the top of the file."}
{"_id":"doc-en-nixpkgs-40950376e52e84f55c6dff685c79e9aa282185baa54825a1d18bb923b540ec69","title":"","text":"When installed through Nix, Bluemail does not create a desktop shortcut in $out/share/applications. The program can only be run through the terminal by default. The program also fails to load unless the --disable-gpu-sandbox option is used. Steps to reproduce the behavior: Bluemail by adding to , and rebuild. for Bluemail in the Application Launcher - not present in terminal - core dumps on gpu process not usable in terminal - bluemail opens with the default wayland icon What currently happens is detailed step-by-step above. What I'd expect to happen is that a desktop icon is created when I rebuild to install bluemail, and that clicking the application from the Application Launcher opens bluemail without a core dump. Installing from NixOS-Unstable Running on Intel UHD Graphics (10th Gen)"}
{"_id":"doc-en-nixpkgs-6fe9bc51ab3ee96b3708d55d048267c3bc83cd834af9e59be101d89671d66626","title":"","text":"Describe the bug SANE does not find the backend To Reproduce Steps to reproduce the behavior: backend to the error Expected behavior SANE loads the airscan backend. Screenshots Listing of symlinks to SANE-Backends: Additional context is missing the version suffix, so SANE does not use the library. The issue has been fixed on upstream master, but no new version has been released yet. Should we just update the package via commit-hash (it's still in early development anyhow), or wait for the next release for updating it? Using in my local nixpkgs fixes the problem. Notify maintainers Metadata Maintainer information:\nI will quickly get in touch with the maintainer of to see if he can cut another release for us. It feels important enough to cut a bugfix release ;) thanks for taking the time for writing such a detailed explanation!"}
{"_id":"doc-en-nixpkgs-0f242a92e0b0226b81870f91c595084bcd07dc9467712c67ab9d28ca9882d58e","title":"","text":"Building on Darwin fails. The problem seems very similar to which was solved by —however I do not know how to apply that solution here.\nWasn't this fixed by merging\nThis issue is fixed, but it broke again recently. Same issue as but we use\nProposed\nFixed by"}
{"_id":"doc-en-nixpkgs-dc9a3d7a8623a429032d060192a4a6ac5e356695f03e5ff883ee876beb282c78","title":"","text":"I had i3pystatus fail to build because of a pytest error with praw on unstable. I tried to bump praw from 6.0.0 to 6.3.1 but it requires a new dep websocket-client that doesn't look packaged thus I ended up ditching it from i3pystatus dependencies. Maybe we should do the same upstream and provide a leaner i3pystatus as it's not a core plugin anyway (and fails ). nix build -f channel:nixos-unstable system: host os: multi-user?: sandbox: version: channels(teto): channels(root): nixpkgs:\nCC ? what do you think of removing it from i3pystatus default ?\nAgree. A user can add manually by overriding of parameter.\nis this still relevant now? or can it be closed?\nI just removed praw it from i3pystatus default dependencies but itself still won't build. So it makes sense to keep the issue open even if I have no personal interest in praw.\nit was irritating me, so i updated it."}
{"_id":"doc-en-nixpkgs-b528f2190826eebb2aafe553ad4065f6411308d190a84d2d379e51cf28bf4441","title":"","text":"As a fallout of the migration to GHC 9.0.2 got marked as broken, as it failed to build with GHC 9.0.2 and the Stackage LTS 19 package set we now have. It would be necessary to investigate if survived this (i.e. if it still builds) and if not to get it to work again. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc\nshould compile again. The bootstrap is additionally built by Hydra, so only the GHC bundled libraries will need to be compiled (which is an improvement to before at least)."}
{"_id":"doc-en-nixpkgs-f7da54e340c3eacc9429e7c52c397f5545d56bd6bce4d0fa3900e82519c698ba","title":"","text":"Steps to reproduce the behavior: unstable defined, enable the ollama service with pkg overridden to point at unstable: without show-trace: with --show-trace: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nHi! Can you confirm your nixpkgs revision has this change incorporated and you're not overriding the package manually?"}
{"_id":"doc-en-nixpkgs-6e8fd2862547e767cd29c367fd1177769f1c399cd63d5f8f3d940352156f20bc","title":"","text":"Describe the bug and failed to build on current master (). (The former depends on the latter.) Build log: To Reproduce Steps to reproduce the behavior: nixpkgs master. (or ) the build error. Expected behavior It builds. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:"}
{"_id":"doc-en-nixpkgs-fbf7c15e70192d72fd7aa1013281dd1396cae6086eaf11578714fd7d4c2a1110","title":"","text":"Describe the bug If you open KDE Partition Manager using its file, it tells you that you aren't running it as root, and you won't be able to make any changes with it (rendering the program useless). The only workaround is running (which is probably unintuitive to people with less linux experience) or changing the file (a bad idea when you want Nix to manage your system) To Reproduce Steps to reproduce the behavior: by adding it to your the file (e.g. in KDE, click on the start menu in the bottom left, type in partition manager, and click on the program) Expected behavior Use when clicking the file for a seamless experience Screenshots ! Additional context The message mentions so I tried adding it to by hand, but that did not work. Metadata Maintainer information:\nLooks like the package is out of date. This dialogue does not appear to be part of the latest version:\nThis might work\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on ."}
{"_id":"doc-en-nixpkgs-f1b8b1a2e652726477dada066c66ea30c7f60a9b9a8643153134b12ebfad61c4","title":"","text":"= 2021.07 does not build successfully on Darwin. A bisect over commits shows this: 2021.10 - - does not work 2021.07 - - does not work 2021.06 - - works 2020.12 - - works Steps to reproduce the behavior: this repo: on Darwin. (I'm on MacOS Big Sur). line 4 from to . . Observe the build failure in the output: For the full log, see .\nCaused by Please use to show the files that a working rakudo contains on darwin\nTested on and it works. Thanks!"}
{"_id":"doc-en-nixpkgs-94a9aee2ec28de03d173583e8274c7bce78f196330b4c0cb40560faf1af9b919","title":"","text":"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):"}
{"_id":"doc-en-nixpkgs-cfbee760400f5ff7afecb1427c4a8f0e206f70419fd2f516d08ff22547888a50","title":"","text":"Describe the bug To Reproduce Expected behavior The derivation to build an executable called Additional context It fails with also but succeeds with but so 1.3 seems to be a recent addition even though julia is on 1.4 and about to move to 1.5. Notify maintainers Metadata Please run and paste the result.\nSame issue here: system: host os: multi-user?: sandbox: version: channels(root): channels(jfelice): nixpkgs: This prevents installing GNU octave on MacOS.\nFWIW I was able to work around this issue by creating a to disable the checks in arpack: I was able to build octave successfully with that. I had to hack around a runtime issue finding , will log that as a separate issue."}
{"_id":"doc-en-nixpkgs-b40213c8d49c4df5a9b3632dafb7b2e5cd9dc19eeef9339235c12577fcbd3b5a","title":"","text":"Describe the bug I'd like to build the python numpy package on an x86 machine for the armv7 architecture. numpy requires liblapack and blas, which require gfortran I already fixed one issue which is that liblapack couldn't find the gfortran compiler (see the overlay below) I'm trying to use the 20.03 release, latest commit. Here's what I'm running exactly: To Reproduce Steps to reproduce the behavior: -build here's the error I get Expected behavior The derivation builds Metadata Please run and paste the result. Maintainer information:\nMaybe related to: ?\nI'm not getting this in NixOS. It looks like a sandboxing issue. Can you try running this:\nThanks for responding! I launched this build on NixOs using an AMI on EC2 and I get the same result as in the issue report, here are the system details:\nA similar issue exists on unstable when building for x86. Currently on: system: host os: multi-user?: sandbox: version: channels(root): channels(swflint): nixpkgs:"}
{"_id":"doc-en-nixpkgs-5011544f88d81473d1c3bb60b7d8c5be5286c40a03a794c3b2b3c925508f6183","title":"","text":"Package name: repgrep Latest released version: 0.15.0 <!-- Search your package here: --- Current version on the unstable channel: 0.14.3 Current version on the stable/release channel: 0.14.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-0e1cd67f9a11bf961f04be517a354898c571fc0454369d7987cab96198d5ecf5","title":"","text":"option was changed to ddclient.domains, but instead of maintaining backwards compatibility the type was changed to a list of strings, which also was not in the release notes, which makes this a bug. I don't see why the type was not simply changed to an or of a string and a list of strings in order to maintain compatibility. Try to upgrade 18.03 with = \"\"; Any released 18.03 version.\nAs this breakage already happened, would there be a point in doing a patch for 18.09? (I could provide one, but I don't know, wether it will be merged into a stable branch.)\nIt would improve the experience for others (if you make it such that it works for both types). I cannot imagine any reason for it not being merged into a stable branch. I wouldn't mind merging it myself, but since I have no rights to do that you would have to wait longer.\nhmm it looks like the module is in a weird state anyway. The config file, which is produced at the moment, doesn't look very useful, as all options will be applied to all domains likewise. So only one protocol can be used in nixos at the moment. If I am not mistaken I will need to change that into a config per domain, with a global part.\nYour changes would introduce new features and go beyond what is in 18.09. 19.03 would be a good target. Due to the module system people could already use them in . Even then if would be nice if you could keep it backwards compatible. It's probably also relevant to consider whether there is an actual demand for what you are trying to do. For example, I would not be a potential user and most people would likely only use one protocol.\nNot a problem, so I will just make the minimal possible change.\nThis needs to be reopened, because of a failure to build:\nI'll take look. Which commit did you use?\nWhatever was newest 15 hours ago in the release channel.\nYes, the change wasn't backported to the release branch :(\n: Could you please reopen this and merge the change into release-18.09 ?"}
{"_id":"doc-en-nixpkgs-2ff518cee040b0e8cf355144e99a3a553e266d742ee776760ffa6f363c3bed82","title":"","text":"Project description swc is the \"speedy web compiler\" fast alternative to tsc, to compile typescript to javascript without type-checking swc is mentioned in a different context in adds 150 MByte to node_modules so it makes sense to factor-out swc to a global package example use: () on a 2x2GHz machine, swc is 10x faster than tsc = 2 minutes vs 20 minutes is a lightweight wrapper (1 MByte or so) but has as peer-dependency, so npm will install both Metadata homepage URL: source URL: license: apl2 platforms: all"}
{"_id":"doc-en-nixpkgs-ddaf4a97e8436cd21a189480ec2f4bfc747be6ae6f339389927e671747d83925","title":"","text":"The dbeaver package does not build on . Steps to reproduce the behavior: Dbeaver should build <details<summaryTruncated build log</summary<br</details"}
{"_id":"doc-en-nixpkgs-32f06a08797adbfbd22032a6c28cbe9f6f71ecc7211ee306de15c97b6e9cdb7f","title":"","text":"Upstream ibus-1.5.24 (in nixpkgs) supports gtk4. It will be good if we enable gtk4 support in nixpkgs. I fail to enable it with the following patch."}
{"_id":"doc-en-nixpkgs-47f51570c0301b68851f9e5dcbd98b283205edf5af84230553cbfc1b27c053ba","title":"","text":"K3s module example option () is causing a crash because kubelet verbosity can no longer be updated post-initialization k3s does not start with the option \"--kubelet-arg=v=4\" defined Suggest any other k3s option except this one <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-4f1dc74b96a4f0cb034d97ffddbd63da159420a63e1dd3c5285a6aca9c14715a","title":"","text":"Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: In the context of pip we previously deleted these files,"}
{"_id":"doc-en-nixpkgs-c91184c8ea0a0458dc74d81804a56eb6f555b9f46d024c002dd0a585d8121618","title":"","text":"Current version of rustracer 2.1.22 does not build with latest stable rust (see ). Please update rustracer to the newest version 2.1.27"}
{"_id":"doc-en-nixpkgs-cc4eb6be48c10d08b4cde3ac253e50d8da14616f30c6a8132a967c6f3dbd1d79","title":"","text":"should have only eliminated the s and removed some of the platform-based (adding new broken/non-buildable attrs), but instead has changed the actual logic. Since that commit, no longer resolves into but into (note the wrong cuda release), later leading to evaluation errors This currently breaks on Steps to reproduce the behavior: We should probably add some tests for the selection logic as well... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-fa7c861a7bd4d53f9b7ed195e75d6c7498d3c81e19c3400492cac34fb03e056a","title":"","text":"I have a Samsung M2022W (usb) that works on a raspberrypi using raspbian (2017-11-29-raspbian-stretch-). I had to pick the ML-2160 driver in CUPS 2.2.1 as recommended by On NixOS (cups-2.2.2): [nawal nix-info system: \"x8664-linux\", multi-user?: yes, version: nix-env (Nix) 1.11.16, channels(nawal): \"nixos-17.03-17.03.1082.\", channels(root): \"nixos-17.09.3149.\", nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs If I use services.printing = { enable = true; drivers = [ pkgs.samsungUnifiedLinuxDriver ]; extraConf = '' LogLevel debug ''; extraFilesConf = '' FileDevice yes ''; }; and pick the same driver, I get garbage printed out. I tried to track down the ppd on raspbian, but only found: pi $ grep 2160 /usr/share/cups/drv/splix- ModelName \"ML-2160\" PCFileName \"\" and (i.e. it generated the ppd when I installed the printer apparently)."}
{"_id":"doc-en-nixpkgs-c6a46d6619cb8238efe4ffca5005782d98b0f3826fd896b0e6f3411633c00b56","title":"","text":"On nixos: [nawal | grep 2160 /nix/store/6f2zx8dl4w0kzgw3wj8f466mvkcgc3dc-samsung-UnifiedLinuxDriver-4.00.39/opt/share/ppd/ML- /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- Having diffed them, I notice amongst a huge number of differences: [nawal diff /nix/store/nmp023llc8fix567f413a5rqbx4sw45g-cups-progs/share/cups/model/ML- | grep Version < FileVersion: \"2.0.0\" < PSVersion: \"(3010.000) 0\" < QPDL QPDLVersion: \"3\" < *cupsVersion: 2.2 so raspbian is using a version \"2.0.0\" and \"2.2\" of something or other, whereas nixos is using a version \"1.2\" and \"1.1\" of similar things. I managed to get my printer to work by copying the ppd across, but I don't understand enough of cups (nor now have the inclination to learn) to figure out what's going on or how to make nixos do the right thing (i.e. in a word, print). I thought this might be useful for someone else who wants to pick it up? Happy to hack around the raspbian if you need more info, or try out things if you need me to while the sd card contains raspbian.\nCan you find out what package on Raspbian provides the driver? Have you installed proprietary Samsung driver there? If not, can you try removing ? It seems we have latest version of but not the latest of the proprietary driver but you don't seem to use it.\nI'll have a look tomorrow evening - how do i use the new splix without upgrading everything to the same commit?\nFind out your current commit with (look at the suffix), then clone nixpkgs repository (), checkout current commit (), fetch my changes () and cherry-pick my patch atop your current commit (). Then you can rebuild nixpkgs with .\nI can confirm this works."}
{"_id":"doc-en-nixpkgs-bbb1d0b40fe3741a63586342ad0baa585ba72a3de513b2574903b2b7ef555a6f","title":"","text":"Thanks for the detailed instructions and for fixing it so quickly! NB: I had to do: (i.e. ) thanks"}
{"_id":"doc-en-nixpkgs-e05844a145e60829257f1ac4b99d42fd7f6e65c04c94014632bfa5115770315b","title":"","text":"The tsocks package creates a shell script () that can be used to run a command with set to the tsocks library. However, it is hard-coded to use . It should be changed to use .\nFixed by"}
{"_id":"doc-en-nixpkgs-e455069fc6f305b07f458c03d81b36056427a627ea3d500a859dca5c32e229c0","title":"","text":"The package can't be cross compiled to other architectures, tested: raspberry-pi and aarch-multiplatform Steps to reproduce the behavior: It should be compiled. This doesn't seem to a nix-only problem, but still influenced by nix. Doesn't compile on arm: AIX: Some missing support for aarch64: Doesn't compile via qemu for arm32v7 and arm64v8: The error I'm having doesn't seem to show up anywhere else though. And a few of those threads also post work arounds. There is no maintainer. $ nix-shell -p nix-info --run \"nix-info -m\" this path will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/xq77wmzk8d306anyk9rsvl4i4h7ihchw-bash-interactive-4.4-p23-dev copying path '/nix/store/xq77wmzk8d306anyk9rsvl4i4h7ihchw-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): channels(nix): nixpkgs: Maintainer information:\nIt seems to be that every package that declares in it's is failing to cross compile. If I put it in it fails with another error though: Should I open another, conglomerate, issue for all the other packages?"}
{"_id":"doc-en-nixpkgs-444a5a64b499ca4679db8862639c8627a574f0193026798e70421d646ce6c6d0","title":"","text":"The latest major version 5.9 of the Linux kernel . Apparently, zstd compressed things decompress much faster and can cut boot times substantially, hence it seems worthwhile for us to support this scheme. Currently we are using bzip2. Unfortunately, I probably won't find time to work on this myself, but thought to open this issue to track progress.\nI've [probably] been using it through a xanmod patch, not recently since the 5.9 release though. What I have in my files are and adding to of the kernel derivation\nFor the initrd image: For me (which might differ from the stock kernel NixOS provides): is already enabled, so set This enables ZSTD compression for initrd. However, which will need to as mentioned above.\nI was wondering if zstd should be made a part of stdenv. are all available in stdenv on linux and with slowly becoming more common by being available in the kernel and used by various distribution's packaging it should make sense to include it.\nCan this be closed? Did cover it all?\nYes, it did! Closing this issue. Thank you for pointing that out, didn't notice before."}
{"_id":"doc-en-nixpkgs-d603952271cf103562aeee7631c956b6fde6c48752b8740d539a86dc08a89a24","title":"","text":"Since PM stumpwm is now up to date but I have an issue in stumpwm module loading. SBCL will return the a package conflict error between packages \"CLOSER-COMMON-LISP\" and \"DYNAMIC-MXINS\" Steps to reproduce the behavior: to your stumpwm contrib modules in an appropriate directory a minimal file: reboot using stumpwm or refresh the stumpwm config using command (by default keystrokes are: ) Modules are loaded as expected Results of :\nHm, indeed. And maybe for debugging we should provide access to the «library» version of StumpWM…\nWe could try building using the Makefile instead of save-lisp-and-die. I did, but then there were problems with missing HOME. Then the problem was that the stumpwm build script seems to want to remember the value of HOME from compile-time on run-time (something like \"/build\") How did stumpwm work previously in nixpkgs?\nCan you try with this?"}
{"_id":"doc-en-nixpkgs-38aca37d5106f846f7193ffbaabd20c34d58c8564f490b38786ef3cf544bdc15","title":"","text":"I've to my . itself works fine: But the man pages are all missing: As far as I can tell, upstream provides them in DocBook format: and also provides a Makefile to build them: so this should hopefully be easily fixable. Steps to reproduce the behavior: . to read a man page for any of the binaries. Man pages should be provided. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThanks for reporting I have opened PR to fix it."}
{"_id":"doc-en-nixpkgs-7d83384c2124adb325012c90af3868a00b71f43d9543f5dab9b23b58d9c391d6","title":"","text":"Pretty much all commands just show the \"usage\" output, regardless if the input is correct or not. For example, outputs: Steps to reproduce the behavior: , , , and many other commands incorrect output I expect to see the correct output, for example should show the current status of all miners.\nHow did you determine the commands? The printed help page does not list any of those as supported.\nI got the commands from the Tracker documentation: You are right that they aren't listed in the help page. I do have manuals with usage for all those commands installed though.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-c829112a9b931418d9809581da116abc6946a133fc5c8abfdb1441b38202e883","title":"","text":"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"}
{"_id":"doc-en-nixpkgs-daf620083ff8fab62d432cc61ac98f0c50e8e7db92afebb2ba47677ef9fe2c05","title":"","text":"Describe the bug I cannot make a shell with pandas installed. To Reproduce Expected behavior A shell opens and works. Additional context <details<summaryI get this error message:</summary</detailsNotify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-f45360e8e919f85865fc813c75c05538cccbd084bc80d2aa68115c2cf67e2095","title":"","text":"Steps to reproduce the behavior: $ nix build --verbose The interesting thing is that I can build the flask-sqlalchemy package just fine: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-b0975512f5450702bf55dbdd481345760419b26002a4a18cff41e4908af786f9","title":"","text":"I became marked as a maintainer on the package many years ago, but since then I have changed careers and have slowly stopped using nixos as much. I don't currently have git installed (and I don't really remember how to use it) Please remove me from the maintainer list I am in the maintainer list as follows:"}
{"_id":"doc-en-nixpkgs-44d4e7686c0dec53e2c7807cf1309f8bb8f9ce347f0fd16c8602d9e135920cd6","title":"","text":"Emby uses ffmpeg for transcoding media and for generating thumbnails. Emby fails to find the FFmpeg binary during the setup wizard but can be specified manually if FFmpeg has been installed separately. Add to , browse to , and advance through the wizard. System: 17.03pre92039. (Gorilla) Nix version:nix-env (Nix) 1.11.4 Nixpkgs version: 17.03pre92039.\ncc\nFunny thing is that I was just watching a movie when I was mentioned on a system without any ffmpeg/ffprobe binary. My system was upgraded from an older version (config was already existing so no check was done by the wizard). I was able to reproduce the issue. Will take a more detailed look at it sometime tomorrow :)"}
{"_id":"doc-en-nixpkgs-24eb25fd37481859a548dfc65f1cb21d23fd3ac381aee9b11e8eb76afd9c0a7e","title":"","text":"Trying to run an action with azure-cli that requries authentication, az will fail to read the cached authentication token from the token cache: This is due to a version mismatch of . will update the package, I checked that the authentication works afterwards. That's me! Please run and paste the result. ` Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI also experience this issue with , as well as with . Thanks for adding the fix!"}
{"_id":"doc-en-nixpkgs-4605117d1f18a574d958f7704fb3e886242237e8c9a068e43b5a7ec470ab14c4","title":"","text":"Setting to while setting to any non-empty value will cause a build failure because and both attempt to create The correct result would be for the contents of to be written out at the end of , after the stanzas provided by pulseaudio. Somewhat relatedly, the in and in pulseaudio's generated config doesn't make a whole lot of sense. means \"override\", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the actually makes any difference.\nI am having this issue as well. Easily replicated by setting those two options.\nCan you make a pull request?\nShould be fixed with . If there still is a problem, please reopen this issue."}
{"_id":"doc-en-nixpkgs-892e83a5d39db04e896c872ef8119391dca727794dfd2103534eefe0563ebaa0","title":"","text":"Describe the bug When printing to Brother MFC-L2700DW printer (with created from a similar model in nixpkgs), CUPS often (but not always) complains about \"Impossible to connect to Name or service not known\" even though I followed the and enabled . To Reproduce Steps to reproduce the behavior: Brother MFC-L2700DW printer. NixOS as follows: (full configuration ) something to http://localhost:631/printers/BrotherMFC-L2700DWseries and see the \"Impossible to connect to Name or service not known\" message. Expected behavior The job is sent to the printer and printed. Additional context When the printer cannot be connected, running usually helps and the stuck job gets to the printer. After my investigation, I think that the cause is long delay in mDNS name resolution. By default NixOS uses NSS module, which tries to resolve both IPv4 and IPv6 addresses sequentially. It seems to start with IPv6, which does not resolve to a valid address so after 5s timeout the resolution continues with IPv4. So the address of the printer is returned after slightly more that 5 seconds (can be verified with ), which seems to be too long for CUPS so it gives up and tries again later and the same repeats, because nscd in NixOS does not cache the results. My current solution to the problem is to switch from NSS to with the following in my : I've also tried but it didn't help. The question is whether to make it easier for others. Possible things that come to my mind: Document this at Wiki Extend to provide e.g. option. Enable caching in nscd Something else? Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(wsh): nixpkgs: Maintainer information:\nConfirm, I have the same problem (with Xerox WorkCentre). And your workaround fixed it for me too. Thanks!\nI wanted to link this issue from the and found that there a comment suggesting that he might have the same problem. does the above workaround make your setup work without restarting cups after booting?"}
{"_id":"doc-en-nixpkgs-47734e5bcbeee2ec5ecc42ba28777a745581f918003fe4d2378e07588cc24a0b","title":"","text":"If yes, I'd update your comment, because it's not accurate. The is not needed, because it is pulled in by mentioned on the previous line.\nHi, I'm back and I'll test your workaround soon. About , I thought it should have been pulled, but it wasn't at the time. I vaguely remember triple checking and it wasn't there.\nSorry, I can't test it again. My printer is busted.\nOK, thanks for letting me know :-)\nOk, my printer has sudently revived and this solves the issue for me as well.\nI marked this as stale due to inactivity. &rarr;\nConfirming that the issue still exists with current nixos-unstable.\nOut of curiosity, is this workaround supposed to break or use outdated softwares? If not, would it make sense to directly apply your workaround by default?\nThis workaround makes mDNS working only for IPv4. If you are on a IPv6-only network, mDNS won't work for you. On mixed IPv4/IPv6 network, you might not see some devices. That's definitely not what some people want :-) Btw, may be relevant to this problem. I've not read all the comments there, but the keywords seem similar to what I remember when debugging this issue. I think the solution might be to increase or decrease some timeout somewhere, but I'm not sure where. More debugging/analysis is needed.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nSame happening here with a Canon MF643C. I found a workaround, but yours seems better. Mine was to manually add the expected on '/etc/hosts' file. This only works if your printer has a fixed ip (like 10.1.2.3). networking.extraHosts = '' 10.1.2.3 '';\nI also hit this issue. Given that (I assume) most people are running ipv4, can we not try the v4 exclusive module first, and still fallback to the one that also works with v6, so that it \"just works\" for this rather common use case? Given, that will slowdown v6 name resolution, but I guess we could also add a big warning in the option.\nLooks like this is closed by\nUnfortunately, that commit is not sufficient for me."}
{"_id":"doc-en-nixpkgs-6fa7a59bdb5af7cd4d15604deee00ef642b13052bb04366fbd8ad2a530e02215","title":"","text":"Current version of CUPS complains with: \"No destination host name supplied by cups-browsed for printer \"BrotherMFCL2700DWseriesmDNS\", is cups-browsed running?\" The referenced commit makes my contain the following line: hosts: mymachines mdns4minimal [NOTFOUND=return] files myhostname dns mdns With it, running returns an IPv6 address: fd76:76f3:2dcb:0:3205:5cff:fecb:4509 From the output of it seems that the command first asks for IPv6 address, so the is somehow ignored and the address is returned by at the end of the line. I can ping and connect that address via so I don't know why CUPS cannot print to it. Anyway, if I disable IPv6 in the printer, returns the IPv4 address, but only after the 5 second timeout, which is too long for CUPS. What I need is also at the end of line. I'll ask at and submit a PR to do that if people do not complain.\nPlease submit a PR.\nUses a direct printer install. Same sort of problems encountered."}
{"_id":"doc-en-nixpkgs-80e55d66bd4b6a2c557cc2d0c49ff32b50d89804064cd40d9e7aa2ff108bd774","title":"","text":"<!-- 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: pmbootstrap <!-- 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: 1.45.0 desired version: 1.49.0 <!-- 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."}
{"_id":"doc-en-nixpkgs-99f03776c9bd21ef1f2c4134ad91e66c42fda9589eb4d1ac0af5b62049774547","title":"","text":"Describe the bug In order to be able to invoke the command from teleport is using  call. There is a wrapper around to bring into PATH . That means is invoked from without wrapper and the browser page never opens (due to missing ). To Reproduce Steps to reproduce the behavior: Expected behavior The path to the wrapper must be persisted in the Screenshots If applicable, add screenshots to help explain your problem. Additional context Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information:"}
{"_id":"doc-en-nixpkgs-71b20f75e37a6c5576423c26c9660322afa75f6812d23292f3ce8e9ec63cce04","title":"","text":"Inkscape has support for openclipart but it doesn't work in the package provided by nixpkgs. inkscape to File -Import Clip Art... a search term and click the Search button. the in the GUI and in the terminal. NixOS 18.09 and nixpkgs master.\nI researched a bit and thought adding glib-networking would fix it. I wrote the following patch, but it doesn't seem to have any effect:\nI wonder whether it really is because TLS support is unavailable, or because uses an invalid security certificate?\nGood point. Hm, that's weird. I followed that URL () a day or two ago (when I first noticed this) and was redirected to https:// without problems. But now I see the certificate warning in firefox.\nI think it may be a packaging bug after all. Look at this grep: The message only appears in the glib tree, in the gdummytlsbackend.c file. No matches from glib-networking, which AFAIK, provides TLS support.\nI tried the patch and am getting Probably because the site is down.\nis not down for me.\nThank you!"}
{"_id":"doc-en-nixpkgs-2dcfa830de69213cd40a12af65533eac68f28ba7b34e64cb4499fdff7c90bb17","title":"","text":"Steps to reproduce the behavior: gmic in a nix shell using the unstable channel Add any other context about the problem here.\nWill be fixed by\nThanks! Note that it makes darktable fail to build.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-5614e72d22b4e5d070e77b7841bf007a47075e6ba2e9e2017d6abd153e9cdefe","title":"","text":"Describe the bug Building packages that use always try to use all cores, independent of ( argument to nix-build) To Reproduce Run , and observe that it spawns many rustc processes (depending on the amount of available processors). Expected behavior The function should pass as argument to cargo. Additional notes Fixing this will probably cause a rebuild of all rust packages, so should we batch this with other changes to the cargo builder? Notify maintainers\nhas been merged"}
{"_id":"doc-en-nixpkgs-e22af4b6671e13035e04e94a13dd742aeebf5a70fdb285df5f2a4a63eb7068b3","title":"","text":"For x8664-darwin, aarch64-darwin: build .#EBTKS x8664-darwin: aarch64-darwin:"}
{"_id":"doc-en-nixpkgs-2b5478bbd02cd69c5f1797a2516d9dbf281d9f62bab362825eb816e48535aeae","title":"","text":"Package name: ArchiSteamFarm Latest released version: 5.5.2.3 <!-- Search your package here: --- Current version on the unstable channel: 5.5.0.11 Current version on the stable/release channel: 5.4.12.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nIt helps if I also open the PR when doing the update"}
{"_id":"doc-en-nixpkgs-19621e4405c7b5b37193c395b6c986786a482142dce27a5253fe2fd4c3dbe0f4","title":"","text":"Project description A simple, high performance relay server written in rust. Metadata homepage URL: source URL: license: mit platforms: Linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-763573e34fdf0ee966be4a9daff807b0d341407c5512e31ef176eabc8feb76e4","title":"","text":"Describe the bug When calling somebody using Microsoft Teams, it seems that the softwares fallback on ALSA plugin, which makes the audio output butchered (hearing noises when someone's talking, but unable to understand what this person is saying). To Reproduce Steps to reproduce the behavior: teams (require an Office 365 accounts) somebody Expected behavior It should use the PulseAudio backend during calls. Additional context I'm using Sway as my window manager (thus, running on wayland). Notify maintainers Microsoft Teams package maintainer: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(ely): nixpkgs:\nHow can one tell it that it falls back to the ALSA plugin? Apart from the butchered sound that is?\nInside Pavucontrol, you see it uses an \"ALSA Plugin\" as a backend. It shows ALSA only during a call, on the rest of the software it shows as a standard pulseaudio program output."}
{"_id":"doc-en-nixpkgs-81c5a8203aee8981e9148221c13e63abb38b1ce8bb1b617c54fc9ae4d86259c2","title":"","text":"Package name: astro-language-server Latest released version: 2.14.2 <!-- Search your package here: --- Current version on the unstable channel: 2.10.0 Current version on the stable/release channel: None <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI'm on it ^^. I've got a working version. Gonna soon open a PR :+1:"}
{"_id":"doc-en-nixpkgs-9431e5e830ab0a1a48c56c93a28fe38f674f5a29f6f6eab0cf53cf73a4d95731","title":"","text":"Steps to reproduce the behavior: floorp Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nHi, Please elaborate - there does not seem to be any actual build failure here. What's the actual error? Are you sure your build machine has enough resources? A browser build is pretty demanding and can take even multiple hours on low-to-mid-end machines. Can you please also post the complete derivation log, as obtained using ?\nI have the same problem (with floorp and floorp-unwrapped). Here’s the error: ! That feature was removed in February, so either update the qcms crate to 0.3 or downgrade the rust compiler version (1.76 could work).\nis the log in the link not enough ?\nOh, I see, Github just truncated the file in the UI. That's what you get from hosting projects on crappy, proprietary software .. Pointing out the exact error too from the get-go would have been helpful in any case. Anyway - seems it broke with a recent rustc upgrade in nixpkgs. This is already fixed with 11.14.1, as it updates the firefox base source. See .\nOkay, I will host my opengist instance for the next time ;) Thanks for your prompt response, waiting for your pr to be merged.\nAny ETA on the PR merge?\nFloorp is now in version 11.14.1 on unstable."}
{"_id":"doc-en-nixpkgs-c849fd8cbe663973962a9b680f9144aab759202a97a7266bee78f372e8c50146","title":"","text":"When installing a PWA using the Floorp browser (experimental toggle in settings), the installed desktop file uses /usr/bin/floorp as the path for the browser to run said PWA. Steps to reproduce the behavior: Floorp experimental PWAs in settings a PWA, e.g. Github or Excalidraw the newly spawned PWA window to launch the same PWA from your DE's application launcher The PWA opens. ! , using flakes, installed via <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThanks for reporting! As well as the upstream report! I can look into it what we can do as I get time. But as I'm the only maintainer for Floorp and currently pretty much out of time due to university and $dayjob, I cannot promise any timeline unfortunately. But happy to review patches, of course, if you'd like to fix it yourself. Can you provide such a generated file for further investigation?\nsure, one such generated desktop file with the example of excalidraw can be found (github doesn't allow for drag and drop of .desktop files)\nHello! I don't have experience maintaining and modifying large packages like Firefox (floorp), and I currently don't have much free time. However, I've discovered how floorp generates the .desktop file for PWA applications: Maybe it will be helpful to you.\nThanks, that is indeed helpful! Should be relatively easy patchable by us then, from the looks of it.\nupstream has and now it will use the path it was in at the time of creating the PWA. It may not be too big of an issue if what they say about fixing it in the next version is true but now the patching will probably fail."}
{"_id":"doc-en-nixpkgs-c12201f553a288c09591b74b997b328b1e391196b993562c7e316de117b849a6","title":"","text":"Panel applets are being picked up from environment variable in and a completely hardcoded path in . First, we will need to patch the latter manager to use an environment variable as well. Second, we will need to do something similar to what . Or better, create  derivation. Originally posted by in\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .\nI'd like to tackle this, do you have any pointers? We need to get it to pick up at least right?"}
{"_id":"doc-en-nixpkgs-3bb7fb1d686ef070c04a22b97001b44580a3fd1138b404c694b73b820a4212cf","title":"","text":"broke with the new Darwin stdenv changes. See log file here: This is a bit odd because Homebrew doesn't appear to be doing anything special to compile it:\nI think we can use llvm 6 here to fix this. It is weird homebrew doesn’t hit this though. I wonder if the SDKs are still on libcxx 6?"}
{"_id":"doc-en-nixpkgs-57ec925ff8c9deca7dcc4d92dc6b37a3fbe36294185cd7f22ec3aeaf8f86105f","title":"","text":"blender to import a gltf model get a huge error, but no model and will be fixed with blender 3.5. But as that is probably still a few months away, I would actually quite like to continue using blender on nix until then. system: host os: multi-user?: sandbox: version: channels(root): channels(betalars): nixpkgs:"}
{"_id":"doc-en-nixpkgs-8c7b2f813f77330693707b6ecf3aa11556d5bc423ff4ebda9ce0b66eec2d7ab5","title":"","text":"Package name: kitty Latest released version: 0.29.2 <!-- Search your package here: --- Current version on the unstable channel: 0.29.2 Current version on the stable/release channel: 0.28.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-f721f3b82d4820cfb704b8b791b0158fe34d1b2b252c2b1c2da35f66500ac9db","title":"","text":"inadyn enabled via doesn't cache the discovered IP address. Therefore every time the service runs it forces an update with the DDNS provider. Enable inadyn service, e.g.: Review the service logs and observe that it forces an update with the DDNS provider every time it runs, even when the IP address is the same. Notice the cache directory is empty. With the above config there should be a file created after the first run with the IP address as contents. When the service runs again at the specified interval and the IP address is the same, it should not update the DDNS provider. N/A The relevant service definition is: According to the env var is the absolute path defined by , so it is not . Therefore the command line is setting inadyn's cache directory configuration to , which doesn't exist, and it silently ignores the missing directory. should then be: Manually overriding is working for me. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nthanks for the investigation, this sounds right to me! Would you mind opening a PR doing the proposed change, and link it from here? Happy to take a look :+1:\nThanks for the report. I won't be able to make a PR for a couple of days so it would be great if could. I think this should also be backported to 24.05."}
{"_id":"doc-en-nixpkgs-41260800955e432416584509b8f26558f638c4790f938d1c8ad85591aea8983a","title":"","text":"fails to run most basic commands when installed via nix, due to an error seemingly related to it's vendoring of some dependencies. On a NixOS machine or Darwin with Nix installed, run: <details<summaryPEXVERBOSE=9 nix shell -c pex</summary</detailsA pex-managed python repl should open, same behavior as in a venv. For comparision: <details<summarynix shell nixpkgs#python3 -c sh -c \"python -m venv ./venv; ./venv/bin/pip install pex; ./venv/bin/pex\"</summary</detailsthe site-packages path where pex lies is in the /nix/store, so read-only. however, the the vendored dependencies are included in the closure; exists and includes attrs, pip, etc. maybe could help us interpret the error and/or how to debug this efficiently? :) some simple commands such as do work. same commands run fine in a venv on the same machines using the same python intepreter. same symptoms on NixOS and when installed via nixpkgs unstable on darwin. the tempdir path mentioned in the error message is writeable, but non existent or cleaned up. the alternative script/entrypoint shows similar symptoms: <details<summaryPEX_VERBOSE=9 nix shell -c pex3 lock create requests</summary</detailsHope you don't mind the pings (maintainer) (done multiple recent updates) (pex developer)\nNixOS is pretty exotic in my world. Can you confirm that I can use a container to emulate this? I assume I can, but just to check. I'll be back at a keyboard August 3rd to repro, but I expect the workaround for now is to set PEX_ROOT somewhere writable. Pex does try to detect the default is unwritable and fall back to tmp, but perhaps all these measures are foiled in this environment.\nwow, that was fast! :) Should be able to emulate in a container or almost anywhere you can get a recent nix with flakes enabled running. Let me know if can assist you with that!"}
{"_id":"doc-en-nixpkgs-323c610776ee87202a1e3b9ec04e3e2379aaf92629bbbdcf3b81bfdc497888bc","title":"","text":"(contact info in profile) Many environment variables like and are different when run via nix (symlinks to /nix/store), but \"~/\" and other filesystems are not namespaced or sandboxed in any way here. is writable by my user. I've tried with PEXROOT set, but that didn't incfluence the output. Going to have another look tomorrow, but it's quite late already here in CEST.\nI don't think notifications are sent for linked issues; think I found a fix in Thanks to for pointing me into the right direction\nOk, this works perfectly fine in nixos (N.B.: I 1st used the vanilla image which is not sandboxed and everything worked fine; so I went through a bit of extra effort below to enable sandboxing in the image and prove it out to see if the sandboxing behavior was relevant to repro): So I'll try to repro using .\nOk, after following the multi-user install instructions for the command here: and enabling flakes, etc - I do repro: So, for someone with knowledge of nixos vs nix shell vs flakes, this would presumably mean something. I'll continue to dig in my shell to see what's up.\nAlright, Pex 2.1.141 should fix. Please let me know either way\nSandboxed builds do not work inside Docker as we can't create required namespaces from an unprivileged container.\nI've tested a build against your tag and that works just fine on NixOS (with sandboxing enabled).\nOk, great. I used in addition to mounting in that custom nix config."}
{"_id":"doc-en-nixpkgs-70243f87d588be9c63ee14313352508055fdfe2350233ad6a8957a98812eb2a2","title":"","text":"Steps to reproduce the behavior: -rebuild test on settings.datadir = \"/mnt/garage0\"; resolves fine Tested on nixos24.05 but code of the module is unchanged in nixos_unstable. I'm using flakes as well Please run and paste the result.\nLooks like doesn't apply, maybe should tinker a bit on my own\nIt looks like the option type was adjusted, but not the other code in the module that checks that value. Shouldn't be too hard to fix."}
{"_id":"doc-en-nixpkgs-7325a08d149b96764836228ef2eac34111065f825cc97a7a3e2d73fb903be061","title":"","text":"Ffmpeg 6.1 supports vulkan video, but it is not enabled in the default version of ffmpeg, it is only enabled in ffmpeg-full. The default version of ffmpeg should support vulkan video so that applications like mpv can use it. Arch enables vulkan by . Vulkan video already works with amd GPUs using ffmpeg-full with this command: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis seems reasonable. I'm in favor.\nEDIT: Error on my end, skip reading this. Hm, your command doesn't work for me on Mesa 23.3.3: Another aspect to consider is closure size.\nIf you haven't tried already, can you try with something in h264? Vulkan video currently only supports h264, h265 and av1(experminental), and only if you gpu supports them.\nIndeed it's h.265, let me try h.264. This looks like a generic VK issue though.\nAs suspected, this happens on h.264 too.\nDo you have multiple GPUs in your system except the amd one perhaps? This chooses the first one arbitrarily.\nSame error for all.\nThen I am not sure about what's causing it, that's the exact same error I receive when using ffmpeg 6.1 instead of ffmpeg-full 6.1.\nUhhh about that... So and that commit didn't seem to have been pulled into this brain thingy of mine... It works as expected with ffmpeg-full."}
{"_id":"doc-en-nixpkgs-144ea127ec4c5ac2a42ae455faf7790d85fb09f3c519b6da48f6b73a387bf51c","title":"","text":"Project description Formatter for typst. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...\nThere is no CLI:\nLooks like the author use .\nlooks like it is still a WIP in\nwhat do you mean wrong default branch? Hi there, I wasn't sure there was interest for a cli, I'll merge the cli in a few days, want a ping then?\nI merged my change, it should be good to package!\nhas renamed the project from typst-fmt to typstfmt in"}
{"_id":"doc-en-nixpkgs-9bf79057fbb81ff9ac5160af4c50edf8e7381d59509da567d7000295e63504b9","title":"","text":"The build attribute of the last state of the package contains a expression to substitute tool names with its Nix packages. The scrip substitutes with the git package, which includes and similar regex used in the script. Script : Packaged script in my nix store: Steps to reproduce the behavior: the package and inspect its output The regex keys aren't substituted by the git binaries store location. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-ab8de325788bd61cd088963f3bb72fe37daa61335186253def136cfce1621c30","title":"","text":"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:\nHm, 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 ... ?\nI 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?\nFor 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).\nYeah, I don't see any directive on the manpage for ."}
{"_id":"doc-en-nixpkgs-93fefeabc28435d4d54b22e9160228375522bff96525021b35ee453ec103f865","title":"","text":":-( 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 ...)\nIts 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?)\nThere is But then you need to write Perl, which might not be an improvement."}
{"_id":"doc-en-nixpkgs-39b045de1668fc2b87788cd68d21a9d0d135e54051536ddfd48e691c51e448d5","title":"","text":"This configuration: If you poke around in the configuration I linked, you should see that I disable NetworkManager and use a static configuration for my main NIC. I can't think of anything special in my config or with this machine that would affect my usage of Wireguard, but I'm also new to using Wireguard. I'm currently on nixpkgs with a few of my own commits on top of . Please run and paste the results.\nIt doesn't seem happy when already exists... I have done two things, both of which were necessary, to resolve this: the link manually () sure the path to the private key exists (if not, you get a different failure in the journal, with failing). (It's possible that fixing the private key path and rebooting would have been sufficient). I'm leaving this open for two reasons: user should receive a better error message in both cases. that we're in NixOS, we should assume full control of the interface and just re-configure it, instead of failing in the setup script.\nI ran into this issue after trying to debug my wireguard setup. My setup is essentialy identical and I get the same error message. Running the start script that is causing the error results in this output. The offending 2 lines are .\nI had to go one step further than deleting the interface. I needed to stop the via then redeploy configuration. But this solved it for me. Nixos should handle this much more gracefully.\nI had to remove the routes with etc.\nThe command is . You can build it in your conf as pre-setup command, but it has the nasty side effect that it possible interferes with other connections.\nI am still running into this issue."}
{"_id":"doc-en-nixpkgs-afb2cd7eb7b92c8d8070098667d1b3fe370c7c19e933ef71b60058f24b519701","title":"","text":"branch to nixos-unstable to your with\nBisect has identified (specifically ) as the source of this failure in nixpkgs, cc See also upstream issue\nIf you're using a flake, this is how I was able to mitigate this until it's fixed. I rolled back the changes from in a branch on my fork, and used it as an overlay for the affected packages like this: This is how you would add them to your overlay: Ofc, depending on how you do stuff, you'll have to fiddle with it a bit to get it to work. I found this helpful:\nThe fix is now on the nixos-unstable branch, but I still cannot build my system after updating, with the same build failure for opencolorio. Is this expected?\nProbably not, since and both build on Hydra.\nOh thank you, this is very bizarre. I will ask on the forum what's going on\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-9705a4f689b3e6cca7e7a8866020e48a68724a618e86e13c94a3ac676b74f1a5","title":"","text":"fails to build in because of a hash mismatch Here's a log showing it: I noticed this when built a PR for 20.09. It appears that the same package builds fine on . cc"}
{"_id":"doc-en-nixpkgs-767dccfdd02fca9fc90b586a8d1cea7fe54a9f3e031268dd60929e4dc52bbee7","title":"","text":"Describe the bug VIber package in nixpkgs repo is broken/outdated. Getting this errors when trying to install it: To Reproduce Steps to reproduce the behavior: to install viber via config file/nix-env. Expected behavior Successful viber installation. Metadata system: host os: multi-user?: sandbox: version: nixpkgs:\nhave the same issue\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on ."}
{"_id":"doc-en-nixpkgs-03687124444c9f3c5504c18c56a8c7050ff44e4f1f7c6fe416c8181626c841c0","title":"","text":"Describe the bug When installing viber, the download step won't complete because the package has an incorrect sha256. My nixos version is 19.03.. (Koi) To Reproduce Steps to reproduce the behavior: Ensure that you can install non-free packages: a) For you can set { = true; } in to override this. b) For , , or any other Nix command you can add { allowUnfree = true; } to then: Expected behavior Viber should install Screenshots Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .\nThis is still reproducible. Is there an archive of Viber versions anywhere so we can pin Viber versions or do we have to constantly play catch-up with them?\nI have the same issue, but in my case the SHA got is different:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-6fdcce550c0b2b1f53e6cb11493794dc77d00a53bb8ccb717c471f43f8346b9f","title":"","text":"Package name: pdm Latest released version: 2.19.1 <!-- Search your package here: --- Current version on the unstable channel: 2.18.2 Current version on the stable/release channel: 2.15.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-f16853e92df17050d4d5fef52c67ede405e2a5d00d661ecf8eb5e20bf8f5dc56","title":"","text":"On with , the tests fails with the following error: Steps to reproduce the behavior: -shell -p python3Packages.scikitimage The tests run without errors. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: channels(smaret): nixpkgs:"}
{"_id":"doc-en-nixpkgs-79828e8badaab68beec95501b9e1dbf68197f625653ba7f13caf9c97cfd2f7c0","title":"","text":"Project description Raze is a fork of Build engine games backed by GZDoom tech and combines Duke Nukem 3D, Blood, Redneck Rampage, Shadow Warrior and Exhumed/Powerslave in a single package. It is also capable of playing Nam and WW2 GI. Metadata homepage URL: source URL: wiki URL: license: non-build code: , build engine & tools: platforms: linux The build instructions should be the same as for gzdoom, so I want to notify the maintainer of gzdoom if he/she is interested in this. Also I want to notify the maintainer of eduke32 because this project could more or less replace eduke32(?)\nI can take a look, but my current schedule is pretty full. maybe at the end of the year? But if someone else is happy to do it, feel free and ping me on the PR\nMight take a look next week. EDuke32 replacement probably won't do, because iirc HRP runs only on it etc.\nThank both of you to possibly have a look into this. I think you're right. But I see that three projects: Enhanced Resource Pack Fixes for Duke Nukem 3D Duke!Zone II Fixed Release of the got raze support, already. Possibly HRP will follow sometime..."}
{"_id":"doc-en-nixpkgs-9cf4af4646156b7fe57c2b775ce9cf44c08bb0090a83ed9e7619c28f85519091","title":"","text":"We got theses reports of Kubo panicing on startup due to probably an empty field This is a bug in our software however I belive this is also a bug in: Because a Kubo daemon without an API listener is borderline useless, your choice to change to a unix socket () makes sense however I think some default got lost and now it is set to . Given I am not a Nix user myself I got help from to fill in the template, thx :heart:. Steps to reproduce the behavior: to notice it's failing with a panic. After installation Kubo daemon should start and the RPC should be usable by a permissioned user. Please run and paste the result.\n/cc (I forgot to fill it in the template and I don't belive GH pings peoples from edits)\nWeird that it works on my machine and in the NixOS tests. One of the NixOS tests only has and options set. does quite a lot but I didn't see anything obvious why this should affect the API settings. But maybe it does make a difference and maybe I specified some additional option on my machine makes it also work there. I'll try to reproduce it with just the enable option set in the next couple days. On one machine shows that the field is set to and yet Kubo starts without a problem and can be seen in the log. According to a comment at the top of, , \"Enabling this [socket file] will completely override any API listeners configured in your config.\". NixOS enables this socket file and overrides with (which is ) plus whatever the user has set in . What I don't know is how systemd communicates this information to Kubo but this seems to work. So in conclusion, I would think that setting the field to in the Kubo config doesn't matter because is enabled, which should override this and specify a socket for the API.\nThx I wasn't aware we even had this feature (or that you could use systemd to configure application sockets in the first place). We have a simple incorrect assumption which is panicking since kubo is configured without listeners. However this is fed by which tries to load as you linked. So if you have a but use something like it should work (AFAIT)."}
{"_id":"doc-en-nixpkgs-b02f0f77b12a9e7b5460f557933141bdd6474bcf7f5976cea43c6b96e2699f79","title":"","text":"I can't test experimentally that feeding the API through systemd works right now, I'll report later, but it seems to me that the like config is not applied somehow.\nI was able to reproduce the problem. Maybe I just need to order the unit after the two socket units. I'll take a closer look in the following days when I have some more time.\nThis happened to me too on first installation, the reason was that systemd couldn’t bind port 8080 because it is already in use by another service, then started Kubo anyways. So my theory is that Kubo checks if there was a socket made available by systemd and if there was none falls back to trying to read the listen address from the config (which is then null) and then panics in the observed way. For anyone else affected by this, run and check if both sockets were correctly bound when Kubo crashes in this way.\nI created , which should fix this."}
{"_id":"doc-en-nixpkgs-81954e06a840dbdb79f74a619bbe044c0689d8c14fa041258528ff23ebc60a55","title":"","text":"Bug description nixos-build switch produces a build error due to firebird-2.5.7.-0 while firebird is not explicitly mentioned anywhere in the file... To Reproduce -channel --update -build switch error message a few apps from file hoping that one of them would be asking for firebird to be installed behind the scene at no avail... Expected behavior A clean error free build. Screenshot ... making all in engines/ccgost... g++ -DREENTRANT -I. -I../common -I../common -I./unicode -I./.. -DREENTRANT -DHAVECONFIGH -DULAYOUTIMPLEMENTATION -O -c -DPIC -fPIC -o HebrewLigatureData.o make[2]: Entering directory '/build/openssl-1.0.2u/engines/ccgost' gcc -I../../include -fPIC -DOPENSSLPIC -DOPENSSLTHREADS -DREENTRANT -DDSODLFCN -DHAVEDLFCNH -m64 -DLENDIAN -O3 -Wall -DOPENSSLIA32SSE2 -DOPENSSLBNASMMONT -DOPENSSLBNASMMONT5 -DOPENSSLBNASMGF2m -DRC4ASM -DSHA1ASM -DSHA256ASM -DSHA512ASM -DMD5ASM -DAESASM -DVPAESASM -DBSAESASM -DWHIRLPOOLASM -DGHASHASM -DECPNISTZ256ASM -c -o egosterr.o egosterr.c g++ -DREENTRANT -I. -I../common -I../common -I./unicode -I./.. -DREENTRANT -DHAVECONFIGH -DULAYOUTIMPLEMENTATION -O -c -DPIC -fPIC -o HebrewShaping.o g++ -DREENTRANT -I. -I./common -I./common -I./unicode -I./. -DREENTRANT -DHAVECONFIGH -DULAYOUTIMPLEMENTATION -O -c -DPIC -fPIC -o IndicClassTables.o gcc -I./."}
{"_id":"doc-en-nixpkgs-cf6cdcc6cd78baafe7be233936234586e151ef1159dded45871c36303d827d18","title":"","text":"/include -fPIC -DOPENSSLPIC -DOPENSSLTHREADS -DREENTRANT -DDSODLFCN -DHAVEDLFCNH -m64 -DLENDIAN -O3 -Wall -DOPENSSLIA32SSE2 -DOPENSSLBNASMMONT -DOPENSSLBNASMMONT5 -DOPENSSLBNASMGF2m -DRC4ASM -DSHA1ASM -DSHA256ASM -DSHA512ASM -DMD5ASM -DAESASM -DVPAESASM -DBSAESASM -DWHIRLPOOLASM -DGHASHASM -DECPNISTZ256ASM -c -o gost2001keyx.o gost2001keyx.c error: narrowing conversion of '' from 'unsigned int' to 'icu30::IndicClassTable::ScriptFlags' {aka 'int'} [-Wnarrowing] 229 | static const IndicClassTable teluClassTable = {0x0C00, 0x0C6F, 3, TELUSCRIPTFLAGS, teluCharClasses, teluSplitTable}; | ^ error: narrowing conversion of '' from 'unsigned int' to 'icu30::IndicClassTable::ScriptFlags' {aka 'int'} [-Wnarrowing] 231 | static const IndicClassTable kndaClassTable = {0x0C80, 0x0CEF, 4, KNDASCRIPTFLAGS, kndaCharClasses, kndaSplitTable}; | ^ make[4]: [./config/mh-linux:43: IndicClassTables.o] Error 1 make[4]: Leaving directory '/build/Firebird-2.5.7.-0/extern/icu/source/layout' make[3]: [Makefile:98: all-recursive] Error 2 make[3]: Leaving directory '/build/Firebird-2.5.7.-0/extern/icu/source' make[2]: [ libicu] Error 2 make[2]: Leaving directory '/build/Firebird-2.5.7.-0/gen' make[1]: [Makefile:193: externallibraries] Error 2 make[1]: Leaving directory '/build/Firebird-2.5.7."}
{"_id":"doc-en-nixpkgs-c30904a24f27703d997b1ab33259832985511d3e3c9781cea710a1920d601852","title":"","text":"-0/gen' make: [Makefile:6: firebird] Error 2 builder for '/nix/store/589jgyzjbbn6zl870qswm80pi4xh8ffq-firebird-2.5.7.-0.drv' failed with exit code 2 building '/nix/store/f5v53hni9pnldx4l0v4svxv0ibl62ir3-tor-browser-linux64-9.0.9en-'. cannot build derivation '/nix/store/c1wpclz112ssp5ki6m546llszn144bq8-wt-': 1 dependencies couldn't be built cannot build derivation '/nix/store/8izfzp2k51zz3385cq14ffd31l2c8bwg-fileshelter-': 1 dependencies couldn't be built cannot build derivation '/nix/store/wi7fzbgmwj9rrzm48mlcsvw51lymmcz8-system-': 1 dependencies couldn't be built building '/nix/store/75r17sql3df7jq3azd76w9fjw6870wm6-'. building '/nix/store/0zq0cb92k0w72ri9jb2zd65gzpnhx6fv-udev-'. building '/nix/store/jqc775s8a0m6r6qhwcfssjdya326s6z0-unit-NetworkManager-'. building '/nix/store/bvg0a7ah4bd77s86f16rq7jsl7sh3nxy-unit-NetworkManager-wait-'. building '/nix/store/vbnnzk9kdx828c8vi3pqcjayrf1ja43n-unit-'. building '/nix/store/df1ffd22pbca5x7ya5mwa8prm40mg54p-unit-alsa-'."}
{"_id":"doc-en-nixpkgs-e7659c6412c8dd561a6111ac6fbeb59ef25556ac8fd186253e8160e88cf3644e","title":"","text":"cannot build derivation '/nix/store/4375h9w8pmppld22s4jb6ag05riw87vg-xsession-': 1 dependencies couldn't be built cannot build derivation '/nix/store/gi689m2ph1avv6n2svvlzr5d2v2xm4p1-nixos-system-bx26-': 1 dependencies couldn't be built error: build of '/nix/store/gi689m2ph1avv6n2svvlzr5d2v2xm4p1-nixos-system-bx26-' failed Notify Weber <marco-<!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata* system: host os: multi-user?: sandbox: version: channels(root): channels(k): nixpkgs:\nThis is pulled in as an indirect dependency of via .\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-3b156242622d74b6a7f7adadcd522ffa1e45665c6ff222b18014ce7d48071696","title":"","text":"Versioned QML import paths introduced in will lead to broken kde applications. Issues include visual glitches, disabled mouse scroll, and potentially other functional problems. A temporary workaround exists, but a proper fix is needed. Steps to reproduce the behavior: your nixpkgs to leatest version. a KDE application that uses Kirigami (e.g., KDE Systemsettings). broken behavior (visual glitches, scroll issues). with . (this partly undoes changes) expected behavior. KDE applications run normally without any visual or functional issues. Start application normally: ! ! Start application with : ! Qt related configuration of my system: Although Kvantum is installed, disable it won't fix this issue. Same problem also occurs under breeze theme. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nCan you post the values of and in the environment you're running it from? Also, does this still happen if running with those variables unset?\nHere is my environment. <details</detailsThis still occurs when running with .\nCan you run it with and post the log?\nAs requested, I've attached the relevant logs for analysis: ,captured with , captured with The initial attempt with didn't produce desired logging output. Therefore, I ran it again with the additional setting.\nDoes it work if you add and to ?\nIt works. QML components render normally now, under both Breeze and Kvantum themes .\nI also encountered this issue. Adding and to alone didn't fix it for me. I needed to set as well for it to work."}
{"_id":"doc-en-nixpkgs-fdba1749e6e83e396b734fb6fde63b046d3c47ac843f703498d9fdf170793818","title":"","text":"Steps to reproduce the behavior: librewolf from nixpkgs master Add any other context about the problem here. Please run and paste the result.\nI have the exact same issue but my machine is a little slower :|. Also this means (not just Git ) is now broken.\nI also reproduced this on master.\nI think it's related to . I'm guessing the crash reporter symbols aren't generated because we disable the crash reporter. Running some tests to confirm.\nis the first broken commit on master.\nI'm going to close this. The PR by fixes the problem."}
{"_id":"doc-en-nixpkgs-7fdb41f1146baf89fa81e6503682ca05ee2c155f57e8652eda01cebc7f18df6e","title":"","text":"Describe the bug fails to build on armv7. It compiles, but then fails one test, making the derivation fail. To Reproduce on armv7. Expected behavior The build completes successfully, passing all tests (except for tests known to be broken). Screenshots Additional context I'm currently trying this on , but with reverted because of . I'm using '<nixpkgs/nixos' since I have a few options set to minimize build times and I'd prefer not bootstrapping from gcc/binutils/etc just to see llvm fail later, but if you insist I can try building it with a clean config. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Note that that is showing the nixpkgs version for my currently running system. I'm trying to build it for a newer version of nixpkgs, listed above. llvm11 failing is currently blocking me from upgrading since I need borgbackup and it has a transitive dependency on llvm11 now (through the Python cryptography module and rust). Maintainer information:"}
{"_id":"doc-en-nixpkgs-4f0ac75aeb8d17ca007a8e0617ec6bc43b828c2611e18fce8d9639d57fcd3cbe","title":"","text":"Project description <!-- Describe the project a little: --Metadata homepage URL: source URL: license: platforms: darwin"}
{"_id":"doc-en-nixpkgs-d3ea649ffb24296d38351f3110d7ad3ccfe73aedc2876949803f9eb050927681","title":"","text":"Project description Volume control applet for Pipewire, written in Rust. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ..."}
{"_id":"doc-en-nixpkgs-346cd31fd1ee2eaf6db00b447eaab18988c2012b0a009c337c77138bce7d9ef7","title":"","text":"Darktable can make use of OpenCL, but the nix package apparently isn't set up properly to allow this. Run : system: host os: multi-user?: sandbox: version: channels(root): channels(lukas): nixpkgs: OpenCL is set up properly on my system: cc darktable maintainers:\nI'd been meaning to fix this for myself for awhile. Should be good now, pending review.\nThanks!\nSorry to revive this, but I am still having this problem in dartable 2.4.4 using intel OpenCL Neo driver. Should ti be already solved? Or the fix is still not present in 2.4.4? Thanks\nDisregard (at least partially) my last comment. I was using the snap version in Ubuntu 18.10. Using the deb, OpenCl works. Where should I submit the bug for the snap version?"}
{"_id":"doc-en-nixpkgs-e80f697eae3a40939db160eca577e80dfd6350857c465727836183ab9f7d5611","title":"","text":"Project description A very small, very simple, yet very secure encryption tool. Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux, darwin, windows"}
{"_id":"doc-en-nixpkgs-37f288610f4c004a41f48eac54e743060444e324f639baf08403b04625664262","title":"","text":"Steps to reproduce the behavior: diffutils-3.10-riscv64-linux i had suspended the system halfway through the build, and suspected that might have caused an issue, so i ran the build again and got the same result <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI can't reproduce this failure on RISC-V hardware. With , the following command runs just fine: Could this be an issue with the emulator you're using or a result of ?\nThe following command also builds for me. Relevant excerpt of the logs: Could you try running this in your build environment to see whether it's an issue with your emulator or build machine? If it builds, could you improve the reproducing instructions you've given?\nI ran that command on a seperate x86 machine and recieved the same build failure\nI have successfully reproduced the issue by emulating RISC-V on an x86 machine. So this could be caused by a QEMU bug. I suggest you update the title to make it clear that it only happens with binfmt emulation.\nOk i edited the title\ni'm curious why the gnugrep pr was merged, but not this one ? given that confirmed this build failure, but not the other one ?\nThe other one just got the attention of a committer a bit earlier"}
{"_id":"doc-en-nixpkgs-63312c0af0382607e30a8aa3b32e7cf2c9f106e5765206dfaa3707de91634089","title":"","text":"was recently updated to use LLVM 4.0, which is rather good news for my use cases. Can we update our version to use this? It also seems they now so perhaps we should switch to using that as well? (maintainer)--LMK your thoughts and if you want to tackle it or want me to (I'd probably get to it this weekend). Thanks!\nI'm pretty busy these days but if you're interested in updating it feel free :+1:\nSure thing! Although actually we'll need to actually add LLVM 4.0 first, forgot that wasn't in-tree yet :innocent:. Maybe I'll give that a go as well :+1: (cc )"}
{"_id":"doc-en-nixpkgs-de35d9aa7a91d883354c5348e0ee14c16b25bb458c50525659df4961a4b7c3e4","title":"","text":"Describe the bug is broken in latest master To Reproduce Steps to reproduce the behavior: -build -A lieer cc\nI reverted locally, and got it to build again - so it's definitely some incompatibility with the openssl we pass in.\nthat commit is from 4 years ago, I wonder why it's making an appearance now\nThis error seems to be present since (more specifically ), so is probably mostly unrelated to it."}
{"_id":"doc-en-nixpkgs-4b7fa26394ba26dd7fbff0969b48867db82010478eca93ae19d01793c6afc9d2","title":"","text":"Incus fails to find when launching a VM. (There is no problem launching a container.) It exits with the error message: Lines 1815-1824 of in the looks for it at or in the path. I think it means that there is a fixup that isn't being done. Steps to reproduce the behavior: (The specific image doesn't seem to matter.) while the VM is created... It exits with the error message above. that is installed at just not being found. Launching a VM should work as expected without the error message. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nWhile that path does appear to be hardcoded in Incus, I'm not able to recreate the error on my zfs storage pool. Can you provide more information about your storage setup, including the output of\nNever mind I see the problem. Will take some time to get this reviewed, backported, and available to 23.11"}
{"_id":"doc-en-nixpkgs-07d51a7b1b73b297c7ac5bc2ba5bb3221a14bea42cddd57f6c80f61630ed9402","title":"","text":"Steps to reproduce the behavior: xdg-desktop-portal-hyprland-1.3.3 This issue only recently occurred upon updating to the latest revision. My entire nix config is . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI suspect this is fixed by For some reason has a pkg-config that defines that it has a non-existent include directory, which cmake then later chokes on since it declares it has a dependency on as a package, not a tool.\nIndeed. I'm cooking up a PR for this."}
{"_id":"doc-en-nixpkgs-8655ad6095b9978398f038e1e5b1aa3d865c3d9f36318a0c3cc4d9ef5ebeb8e3","title":"","text":"It looks like Qt has broken support for SDK 10.10 in their latest release. Here is the log: Any ideas on how we can fix this?\nfixes this.\nWe should probably keep this open tho, we can't keep using"}
{"_id":"doc-en-nixpkgs-a7acce79e2717ffb5bd7923afbc3e55f0df7d061664430c7f1d193b7529a89f5","title":"","text":"When tries to create a volume of type=block, it cannot be created due to the occurrence of . This is because is not registered in . Steps to reproduce the behavior: Create block type volume. If you check nixpkgs for lxd 5.20, you can see other package dependencies that are not present in incus. For example with lvm, this is expected to severely impact the lvm backend. (Currently, it cannot be confirmed because there is no lvm drive.) Can we change it in the same way as lxd? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nOpened a PR to fix. Sorry about that. Not sure why I dropped these..."}
{"_id":"doc-en-nixpkgs-64268ecb6381603cce9c8d36b6f37d5ff43ed5d4c4ecce6f228a205f4ac9380f","title":"","text":"The original author of gitless has not committed any code to it since 2021, and the version currently in nixpkgs errors out when trying to do anything useful with it. has forked and continued to develop it though: Package name: gitless Latest released version: 0.9.17 Current version on the unstable channel: 0.8.8 Current version on the stable/release channel: 0.8.8 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.\nThanks for the tag! I'm glad that gitless can live on past the initial MIT research that was conducted. Although it's been a while since I've updated gitless, it has been very useful for my day to day work and I'm committed to fixing bugs in a timely manner.\nSure! I rediscovered gitless (and your fork) on the back of a recent Slack discussion with folks from about the best way to make version control as accessible as possible for newcomers in the research community."}
{"_id":"doc-en-nixpkgs-48770413132d0a3e4bad199e300b6cda85180951f5e38c36481936d90d5f5f68","title":"","text":"Version V1.3.0.4373 of mwprocapture (the Linux driver for the Magewell Pro Capture family) FTBFS when building against Linux 6.8 or newer. Steps to reproduce the behavior: Add to your Nix configuration. Add to your Nix configuration. Magewell has provided a revised driver update to address this issue. I am working on a pull request for nixpkgs. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-1905c8d45982c96a50eaffe421baf84241912a4700d2df9cfe9598b7a290186f","title":"","text":"Steps to reproduce the behavior: sysdig Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nCan't repro on master () and the error isn't in the log output, can you provide additional info?\nHey, thanks for the response - checking again - it only happens if for me if I enable the sysdig-option in my config not building the sysdig-package - maybe this helps to reproduce and depends on the used kernel-version? I've uploaded the full build log:\nThanks, seems this is the error:\nI guess this is already fixed upstream in the drivers () but needs to be to nixpkgs to fix 6.10-kernel builds.\nfixes it for me\n~Ah 0.38.1 - got released somehow oversaw it should check first if that includes the fix~ 38.1 does not include a driver-bump"}
{"_id":"doc-en-nixpkgs-8865a2a0a97e111f30b92c2ba6d281111cd174fa4f5da241d3ef0dbb9eb72328","title":"","text":"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:"}
{"_id":"doc-en-nixpkgs-c3dfba42f7103e261dd479c2ab4c59c6910abbe5dc7fc8df706ee25432a657de","title":"","text":"Describe the bug When adding to the NixOS configuration the udev rules do not get installed. To Reproduce Steps to reproduce the behavior: mixxx with a DJ controller plugged in. controller is not recognized by mixxx Expected behavior The udev rules are in the correct folder i.e. or and therefore the udev service does not recognizes them. Additional context The fix in worked for me after a little modification (the rules file got renamed). Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nOriginally, mixxx did the right thing = install udev files to - see Later they changed the behaviour and they install to - see Sigh."}
{"_id":"doc-en-nixpkgs-7a2d571b59864b077255c8f73170c68f6caef9b161982f9986a31fc282ff609c","title":"","text":"The package with that are automatically fetched carry no license. ` cc\nPoking upstream does not seem to yield anything. They did indicate they wouldn't support this use case, so what are you expecting from them?\nI talked to the authors of wp4nix and they are happy for new contributions. It would be nice if the wp4nix script would somehow handle license informations, for example by manually defining them. Not quite sure yet how to implement it\nIf we don't know the licenses to these packages we honestly cannot keep them around. For example, it is absolutely unclear, whether we have a license to even redistribute them. Of course upstream will take patches, but they're not exactly in the same boat we are. I think your attitude towards the whole licensing situation around wp4nix/nc4nix and its resulting packages is alarming.\nAs written : Fixing this for Wordpress packages and themes (wp4nix) and Nextcloud apps (nc4nix) in a foreseeable time exceeds my skills and competence. Therefore I would like to offer to add a flag to these package sets and remove them for the next release 23.11 if it's not resolved by then.\nCouldn't we mark them as unfree so they don't get cached on hydra but people can still use them if they want? Unfortunately it seems like the wordpress plugins repository doesn't seem to provide the license information in an easy manner. And I don't know whether it is stored somewhere else or can even be extracted from the derivation without import-from-derivation.\nActuallly we seem to be safe in theory. claims\nIn an ideal world, that would hold true, but it is up to the user and distributor to validate the final outcome. I therefore think this situation remains unresolved."}
{"_id":"doc-en-nixpkgs-38bb6930cd09e5488c2f92ebdca65fb55b1149ed2c103a87ef3f567d66c06cdc","title":"","text":"System: (macOS 10.11.6) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: 16.09pre-git\nmay fix this problem for you, though you may also wind up needing something like to get a functional set of go commands on darwin."}
{"_id":"doc-en-nixpkgs-39022281a5f7bd7e2c4a9b99b5aa7987cf02f044fe88ae6a4c36add6f3e6091c","title":"","text":"Project description cameractrls is a UI for v4l camera settings, like pan/tilt/... on fancy Logitech cameras. Metadata homepage URL: source URL: license: MIT platforms: Linux\nHere's a prototype:\nI'm using this successfully with the latest version,\nIs there any progress with this request?\nPlease test my PR I don't have the device.\nTbh, I would like to, but I don't know how to test a custom package...\nFor new CLI: Or\nI executed and then nothing happened... I can also not find cameractrls\nCheck your current directory, there's a symlink to store, and the executable is in\nI only tested the gui app and it seems to work fine!\nThanks! What about the others executables? Have you tested all the functionality of the app?\nI can only test the the GUI, because I don't know how to use the CLI program. But the GUI is working fine, afaict."}
{"_id":"doc-en-nixpkgs-25545a79235c9870f9c6a2d7fa34cbd52e95ead643827d337d993367951f9c4d","title":"","text":"When enabling freshrss and rebuilding, no freshrss systemd service is started. Steps to reproduce the behavior: (as well other requirements for minimal config) (with , for me) The only freshrss units are and . to in browser. Unable to connect. A service with (or something?) is created and runs automatically. The http server is accessible from a browser. I initially tried running in a container, but running on the host OS had the same result Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nFreshrss doesn't run as a systemd service. It runs under php-fpm. The associated systemd service is . This is then exposed via nginx. I believe the default nginx configuration will expose freshrss on port 80, so http://localhost may work for your current configuration. The used by nginx for freshrss is . My guess is you'll need to configure it. If you want to access freshrss via \"http://localhost:8080\" you could use a config like:\nSorry I never responded to this! This worked, thank you.\ni guess we can close this then? please report back if i am wrong.\nI do agree with qyriad that this could be explicitly documented better, but I don't have any further issue to specifically track\nany specific location where you want this documented? where would you look something like this up?\nI would probably put in the description of the option."}
{"_id":"doc-en-nixpkgs-482d2fe1e54bd7ebf4a85c97407a98658613e0dc61fc33b057c96b9f12aef1d7","title":"","text":"The NodeJS 12 release goes end-of-life on 2022-04-30, which needs handling before the next release. Worst case we update like in ."}
{"_id":"doc-en-nixpkgs-5ec8a1585bcd34afb90458ae98e0d7f354701cab4c3577fd7821b13d9e361d47","title":"","text":"Should there be an ability to specify UDP port forwarding in the nat module? It would necessitate an extra property in the forwarding list specification, like .\nHas done this!"}
{"_id":"doc-en-nixpkgs-15bc34de874989a461287283e008176cdc40a4547f6dec970d768d05e947bf1a","title":"","text":"Project description  Selectdefaultapplication is a very simple GUI application that lets you define default applications on Linux in a sane way. Basically it just loads all installed applications by reading their .desktop files, reads the MimeType fields to see what it supports, and updates with what the user wants. Not all desktop environments provide such a tool, prompting for an agnostic tool. Metadata homepage URL: source URL: license: gpl2 platforms: linux Additional info: AUR package:\nYou can try using this in an overlay, use .\nSeems to work!"}
{"_id":"doc-en-nixpkgs-7f09ef34450e54cf3576615ce23f8939eedbbf70739c9daf65850245b3598a53","title":"","text":"Linux Kernel 4.7.3 seems broken, as my laptops keyboard doesn't work. experienced by the arch community too: update, reboot - 4.6 and 4.7.2 work, 4.7.3 doesn't nixos-version: (Gorilla) nix-env --version: nix-env (Nix) 1.11.4 nix-instantiate --eval github/nixpkgs -A lib.nixpkgsVersion: \"\"\nSame issue with kernel 4.4.20 (lts). I can no longer enter my cryptsetup password. The reason is that i8042 is no longer integrated in initramfs, I suppose because of: Update: To fix this issue I had to add it to\nThanks, created a quick fix with your solution, which should fix it for everyone"}
{"_id":"doc-en-nixpkgs-6284fb83c62546234d076d5641c6f0b6f602cdd9bf3e39f0420b2e0b0272b47d","title":"","text":"Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . nix-build '<nixpkgs' -A --check --keep-failed You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: nix-store --read-log $(nix-instantiate '<nixpkgs' -A ) Tested on nixpkgs\nPR was merged and made it to nixos-unstable, so this should be fixed"}
{"_id":"doc-en-nixpkgs-eec3e0666fb680ed28d05b614655d4cb67dad9d02582805247fa16cc561b7a34","title":"","text":"Filing this issue to track related actions in nixpkgs. Feel free to send questions my way and/or contribute via comments in this issue! A buffer overflow in which allows a malicious actor to potentially get code execution in software that displays a specially crafted image file. This impacts pretty much all web browsers, as well as other software which might process or display untrusted images (image editing software, email clients, chat clients, social media clients, etc.). Chrome has rated this vulnerability as critical severity and has indicated that they have evidence some actors are already exploiting it in the wild. This vulnerability was very shortly referred to as CVE-2023-5129, but that second CVE for the same vulnerability has since been withdrawn. Firefox and Chromium are not vulnerable anymore as of 2023-09-16 in and . Direct dependents of the system are also not vulnerable anymore. Some applications bundle their own version of libwebp instead of using the system version (including some other web browsers in nixpkgs: Brave, Tor Browser, etc.). Each of these need to be updated separately by nixpkgs maintainers. See below for a list of all the known applications that need an update and their status. Review/merge any nixpkgs PR that you see pending in the task list below. Help figure out a course of action for . Report your findings and suggested course of action in a comment here, and I'll update the sheet and the task list below. If you have an idea of how to fix/address the vulnerability in any of the packages listed in the task list below, don't hesitate to post a comment here and send pull requests! Feel free to cc me on PRs so I can make sure they're tracked and they don't get lost.[x] libwebp is updated in staging-next (unstable: , 23.05: ) [x] This will make it to master via - said likely this weekend. [x] We need to merge staging-23.05 to release-23.05. That should also finish this week: [x] electron is also vulnerable. Upstream is making new releases on all their supported branches to include the patch. [x] electron 26 bumped in master (). [x] electron 25 bumped in master (). [x] electron 24 bumped in master ()."}
{"_id":"doc-en-nixpkgs-0faa5d9f9dc8d9adece39d35975b267e23a787e4eb7dafda21cc8b9d6f44881b","title":"","text":"[x] electron 22 bumped in master (). [x] electron 26 bumped in 23.05 (). [x] electron 25 bumped in 23.05 (). [x] electron 24 bumped in 23.05 (). [x] electron 22 bumped in 23.05 (). [ ] We should figure out what else might be vendoring libwebp. Not sure if there's tooling for this? List of derivations to investigate further and possibly patch: [x] High risk stuff (mail clients, IM clients, web browsers) [x] armcord [x] caprine-bin (, ) [x] discord (, ) [x] Darwin version: / [x] fluffychat () [x] gitter (, ) [x] mailspring [x] mattermost-desktop ( / ) [x] mautrix-whatsapp ( / 23.05 ) [x] microsoft-edge ( / ) [x] mullvad-browser ( / ) [x] palemoon-bin (, ) [x] rocketchat-desktop ( / ) [x] signal-desktop (, ) [x] signal-desktop-beta ( / ) [x] slack ( / ) [x] threema-desktop (embedded electron not used) [x] tor-browser-bundle-bin ( / ) [x] tutanota-desktop ( / ) [ ] Libs that other stuff might depend on [x] flutter [x] libcef ( / ) [x] opencv ( / ) [x] qt5.qtimageformats ( / ) [ ] qtwebengine (darwin only, maybe?) [x] smooth ( / ) [x] darktable () [x] golden-cheetah-bin: ships a vulnerable prebuilt libwebp (cc: [ ] koreader: ships a vulnerable prebuilt libwebp (cc: [x] libreoffice () [ ] localsend: ships a vulnerable prebuilt libwebp (cc: [ ] obs-studio () [ ] rigsofrods-bin (ships a vulnerable prebuilt libwebp (cc: [x] Anything Rust that depends (transitively or not) on libwebp-sys2 < v0.1.8 libwebp-sys2 might silently decide to build its vendored version, if it can't find system libwebp or if the crate feature is enabled."}
{"_id":"doc-en-nixpkgs-a2b1809b30392f28b5bbef70a8a3b9b7a3fc187169f043fe82848ede71afa992","title":"","text":"[x] () [x] catppuccin-catwalk () [x] Anything Rust that depends (transitively or not) on libwebp-sys < v0.9.3 Linking against system webp is intentionally not supported: [x] oculante [ ] .NET software that uses SkiaSharp. Upstream has yet to release a fixed version. () [ ] avalonia-ilspy [ ] BeatSaberModManager [ ] denaro [ ] galaxy-buds-client [ ] jellyfin [ ] mission-planner [ ] mqttmultimeter [ ] opentracker [ ] openutau [ ] ryujinx [ ] scarab [ ] wasabiwallet [ ] Go software linking with (, ) - broken down per vulnerable lib [ ] (unmaintained, likely never getting patched - action should be getting upstream to migrate away) [x] hydron ( / ) [x] mautrix-whatsapp () [ ] () [ ] hugo [ ] Godot related derivations: these should be unvendored (capability already exists in the build system). [ ] godot4 [ ] godot3 [ ] godot3-server [ ] godot3-headless [ ] godot3-export-templates Built using Godot [ ] lorien [ ] oh-my-git [ ] Electron apps where we ship upstream binaries instead of using nixpkgs electron Best course of action: upstream should update to electron = 26.2.1, = 25.8.1, = 24.8.3, or = 22.3.24 and tag a new release [ ] atom [ ] hakuneko [ ] hyper [ ] indigenous-desktop [ ] joplin-desktop [ ] keeweb (unmaintained, mark as insecure?) [ ] keybase-gui [ ] insomnia [ ] mullvad-vpn [ ] simplenoteFor derivations that vendor a vulnerable libwebp, priority list of preferred action to take: De-vendor libwebp and use the version from nixpkgs. (Difficult/impossible for binary provenance derivations.) Update to a new version from upstream that has a more recent libwebp patched for the vulnerability (TODO: how to check?) Mark as at some point if upstream can't be convinced to make a new release."}
{"_id":"doc-en-nixpkgs-a7eef09e05f223adf80a4d152b138bafee1b5ccb34a257132db63261d208f0e4","title":"","text":"List of all software in nixpkgs known to contain libwebp:\nis now out\ni think one way you could check for vendored webp is with nix-locate, searching for , for example darktable might be vulnerable : possibly also koreader the full output\nThanks, that's indeed useful! I think the most common case though would be bundling the code and linking statically with the lib, which wouldn't necessarily be found by this - but maybe I'm just too pessimistic :) EDIT: the ones you found to the tracking in the issue's first comment so we don't lose track of it.\ndarktable: links with libwebp, the is an internal plugin and is not a vendored version.\nkoreader: binary provenance, ships a vulnerable prebuilt libwebp (cc:\nlocalsend: binary provenance, ships a vulnerable prebuilt libwebp (cc:\ngolden-cheetah-bin: binary provenance, ships a vulnerable prebuilt libwebp (cc:\nlibreoffice sources file lists a libwebp- (or libwebp- for libreoffice-still)\n, vendor libwebp via the rust crate libwebp-sys2\nUgh, and good luck finding all the things that end up transitively depending on that crate I guess. I suggested they file a GHSA so dependabot can go and do its thing, but it might still take a while to trickle down through dependents. Anyway, libwebp-sys2 version 0.1.8 looks like it's fixed.\nThere's also and I can't seem to find the vendored code by grepping for strings in the binaries. Would need further checking, but I'm tempted to say libreoffice is fine?\nThe libwebp-sys2 crate also will link against the system libwebp if it is found. I'm currently compiling a list of rust packages that use libwebp-sys2.\nBut since it transparently falls back to the vendored source, I'm going to assume most Rust programs in nixpkgs haven't bothered declaring libwebp (and pkg-config?) as buildInputs... But at least that might give us a lever to patch without requiring an upstream cargo deps bump?"}
{"_id":"doc-en-nixpkgs-4f59a31577a872e04e0e062b6f0d4566a2d61e291b07f9a0ff9024a133501463","title":"","text":"the application has enabled the libwebp-sys2 'static' feature, then it will skip looking for the system one and build its own\nUnsure how to deal with the libwebp-sys2 things, which would still be vulnerable for cross-compiling and pkgsStatic. Opened an upstream issue:\nHi! Sorry for just popping in randomly, are there any publicly available workarounds for this issue currently? I'm on , but it seems like firefox nor others have gotten their version bump on that branch.\nNot really, and as noted in this issue's description relying on the browser's version number is misleading here (because nixpkgs doesn't use the vendored libwebp, so what matters is the version of the libwebp dependency). If someone wants to write instructions using I'll gladly add those to the issue description for future reference.\nOn the branch we're only missing a few thousand builds per platform right now, so I'd hope for to update tomorrow.\nFrom the : So looks like this one is fine. I'd remove the vendored download to prevent confusion, but looks like this is automatically generated...\nstaging-next was merged to master, so users on nixos-unstable should have their browsers patched on the next channel bump.\nFixes for Tor Browser & Mullvad Browser:\nHi! I use the branch specifically in my flake, any ETA on when that branch will get the update pushed?\nDepends on how fast stuff ends up rebuilding, I'd expect within 1-2 days at the latest. It's all in automation's hands at this point, unless there's somehow a breakage we didn't notice. You can switch to which already has it (but might require you to do more rebuilds from source), or follow for the status of the fix.\nI think I might channel-switch for a bit for this fix, thanks for the help!"}
{"_id":"doc-en-nixpkgs-1088b8ea5f03208e747bc35842e16c17b868c232c57f5bdd9a3147bff499b4bd","title":"","text":"Additional packages which have a vendored libwebp that I found on my system via the that posted in Matrix: slack obs-studio (via ) openutau (via embedded , also oops this package is mine )\nSame method as mentioned by Lily, found: android-studio discord idea-community vial (via ) joplin jetbrains-jdk-jcef (via ) qtimageformats (via )\nI looked more into .NET apps that depend on Avalonia and I've also confirmed these vendor libwebp (all via ). I've not confirmed that any of them use the vulnerable version directly, but it seems highly likely they do given a new SkiaSharp release has still not been made since the release of the CVE fix: BeatSaberModManager alttpr-opentracker avalonia-ilspy denaro galaxy-buds-client git-credential-manager jellyfin mission-planner mqttmultimeter ryujinx scarab space-station-14-launcher wasabiwallet\nsame method as hexa and liliy\ncurrently working on a betterbird update. Not sure about thunderbird and I don't really have the time to check it right now. edit\nAlso going to add onlyoffice-bin, libsForQt5.qt5.qtimageformats, libsForQt6.qt6.qtimageformats and remarkable{,2}-toolchain to the naughty vendoring list.\nIf it uses buildMozillaMach it uses our system package.\nGot a match for \"no memory during frame initialization.\" in : /nix/store/z613gjk28c3q0ypjsdch9vshdlydc9fm-vscodium-1.82.0./lib/vscode/codium\nI've ran a grep on ~200K Nix store paths from a full Hydra evaluation - here are the results: Let's start categorizing that a bit and translating it into trackable tasks :) I've already listed all the SkiaSharp dependents. A few other categories I see: CEF users Vendored Electron users Qt libs Flutter Go binaries (e.g. mautrix-whatsapp, but not sure what package the dep is coming from)\nFor reference, I believe that all supported channels (6) have updated past the patching (the non-vendored one). This weekend turned out to be a pessimistic estimate."}
{"_id":"doc-en-nixpkgs-ba737ca90cd686726257e776b5ccd674049ff31ab3072693ccaa4c4d1c57127b","title":"","text":"golden-cheetah-bin: PR to mark insecure: Also reported upstream:\nopencv seems like a relatively common package (with multiple versions). Maybe the maintainer could have a look?\nHigh priority things that I think are still to be updated: Chat apps / browsers / mail clients: fluffychat (uses vendored flutter < v3.13.4, cc upstream has a commit in master which updates flutter to 3.13.4, but I don't think that's released yet. gitter (cc upstream seems unmaintained anyway, should be removed?) mautrix-whatsapp (vendored via some Go dep, cc signal-desktop-beta (cc who took care of Signal, can you maybe have a look?) threema-desktop (lib/threema/threema-web - is this even used? since we use nixpkgs electron, cc tutanota-desktop (opt/tutanota-desktop/tutanota-desktop - similar to threema-desktop, also cc\nmattermost-desktop (share/mattermost-desktop/mattermost-desktop, cc\nrocketchat-desktop (cc I think just needs a bump to 3.9.7 for\nYeah removing gutter seems fine\ndo you recommend moving FluffyChat from stable -a git commit temporarily? By the way, flutter itself seems to have a bad vendored version. Need to push out 3.13.4.\nThere's a mautrix-whatsapp bump here: , not sure how I can check whether this is fixed by that PR? Edit: looked into the upstream source, definitely not fixed by that PR. From what I can see mautrix-whatsapp uses libwebp in a vulnerable way. I'll try to work with upstream to get this resolved.\nIf cherry-picking the patch is an option it's probably less invasive, if upstream is planning a release in the next 2-3 days I think I wouldn't mind waiting too. If neither of these options apply (or if you don't mind bumping twice in rapid succession if upstream pushes a new release) going to an unstable version SGTM.\nwas updated and merged recently (). Would that count?\nLooks like that new version contains which is a proper fix. Thanks for the pointer! Just needs backport to 23.05 now.\nIt was mentioned in the changelog, please read them when updating a package."}
{"_id":"doc-en-nixpkgs-eaba471ab2faff6c214eacc72ad255daa502238b58f0b906ad22953d3720c32a","title":"","text":"It will count once the backport to release-23.05 has happened.\nI had already reported the issue to mautrix-whatsapp in private to lessen the chance of exploitation (they use the webp dependency to decode webp images and are thus vulnerable). I've had no response yet though.\nHeh, I don't think there's much value in reporting this in private (and making coordination/tracking harder) given that it's a publicly disclosed vulnerability already. I noticed you said you'd talk to upstream but couldn't find any trace of that, so I went ahead and filed that bug... Sorry for stepping on your toes - it's hard for me to know exactly how actively maintainers are going to handle the remediation by themselves, so I've been proactive in making sure upstream issues are filed when I don't see one\nGodot (godot3, godot_4, godot3-headless, godot3-server, godot3-export-templates): upstream has merged which I think is getting backported to the 3.x branch. But it also appears that, at least for 4.x, libwebp can be unvendored: I think that's what we should be doing while waiting for new releases, and this is likely true of many other dependencies that can be unvendored via the same mechanism. cc maintainers: (please cc me on any fix PR and make sure to backport to 23.05).\nFix for mautrix-whatsapp here: (backport here: )\nWorth noting is vulnerable, upstream fix was in PR Kong/insomnia, though it hasn't gotten a release yet.\nis a fix for signal-desktop-beta, thanks\n:heart: to all who have contributed to this.\nExplicitly pinging the maintainers for the remaining high-risk use cases: armcord still uses vulnerable Electron 26.1.0. Please get upstream to fix their security vulnerabilities. caprine-bin is presumably built by upstream from Electron 24.1.3 from 151 days ago. Please get upstream to fix their security vulnerabilities. (Additionnally, why is this a binary build instead of something we build from source?) - mailspring uses Electron 17, which is hopelessly out of date, EOL, and insecure. Please get upstream to fix their security vulnerabilities."}
{"_id":"doc-en-nixpkgs-72b6dfc5a05af070315fa3022912ae01f19e37f824acb162976907792bf1d84d","title":"","text":"mattermost-desktop is out of date in nixpkgs. Their latest release is based on Electron 26.1.0, which is also insecure. Please get upstream to fix their security vulnerabilities. rocketchat-desktop also needs a bump in release-23.05. I've started the backport process via the master PR, please test it and let me know when it's ready to be merged. - Everything in this list that hasn't been updated by Friday 2023-09-29 00:00 UTC will be marked as insecure next weekend.\nAlso mentioned this on Matrix, but for posterity: SideQuest is also affected (and frequently loads untrusted content). It appears to use a bundled Electron 13, which has not received and will not receive a patch. I've e-mailed the upstream in the hopes that they can update to a newer Electron ASAP.\nUsing and then checking the output of by opening DevTools (Ctrl+Shift+I) : <- patched according to GH security advisory : <- patched according to GH security advisory : <- vulnerable? Tested on\nGreat, thanks for looking into it! Hopefully they'll roll out that update to the stable branch soon... I guess it's difficult for a small indie developer like them, it's only been 2 weeks since the fix was made available! :-)\njust got updated in master so it's not in nixos-unstable yet. thanks for checking it out, I couldn't figure out a way to check the electron ver.\nThanks! I checked 0.0.30 (which is on master and 23.05 as of yesterday) and it seems to be on Electron 22.3.24. Marking as fixed\nThanks for pinning me. Just created an issue there: Because the source build failed the time I tried to package Caprine (some years ago). It's a pain to an build Electron app from source in Nixpkgs.\nRegarding Mailspring there is , I will ask about their plans to move forwards\nThere should be a pre-release with electron 27 for armcord, will dig in tomorrow.\nCurrently we are not building koreader from source (see for some efforts)."}
{"_id":"doc-en-nixpkgs-0447b404b05a517bc61f6b594a2f70271dac2b48d2122f4aacbf9e8d65fd0b1d","title":"","text":"Since the released upstream deb package has not fixed CVE-2023-4863 ( fixed it, but it is not released yet), we have to wait a while for a new koreader release.\nTo make it better, I reported them this like 2 weeks ago! They're still working on running the npm command on the stable branch, give them some time!\nfluffychat and flutter updates have been backported now:\nI made a draft PR that contains the caprine-bin update (), but the updated app turns out to be unusable (sindresorhus/caprine).\nThe above issue is resolved in Caprine 2.58.3. Please take a look at .\nit was brought to my attention that the Darwin version for Discord was not bumped in 6 months, and is thus still vulnerable to this libwebp vuln. If nobody maintains this software can it be removed and/or marked as knownVulnerable? Thanks!\nI'd say that after a bit of wait you mark packages as vulnerable and that is the main way of finding out whether someone is really willing to keep it alive.\nI have bumped them in . The main issue is that r-ryantm isn't helping us out here, as there is no for the darwin packaging. Not sure if any of the other Discord maintainers are using Darwin, but I certainly don't and would need some assistance testing these.\nis affected. I created mifi/lossless-cut to remind the LosslessCut upstream to make a new patch release, so that me can update .\nis affected, fix:\nAll the packages I evaluated as being high-risk have now been taken care of (and most of them did actually get updates, woo! only marked 2 or 3 as insecure). Right now I don't think anyone has the bandwidth to try and track the rest. I'm going to close this bug - if someone does want to take over the remediation for the rest of the impacted packages, feel free to reopen and assign yourself. (Note however that there is a large overlap between vulnerable to this libwebp vuln and vulnerable to the recent libvpx vuln... so maybe just go help over there instead of reusing this bug.)\nUnpinning due to closing\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-25ed9e8d5fb6adb3141fdbca5b360d19a1bbaff6be69540ccf5cb397a6804586","title":"","text":"Package name: kitty Latest released version: 0.34.1 <!-- Search your package here: --- Current version on the unstable channel: 0.34.0 Current version on the stable/release channel: 0.31.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-96e3ea347c0cf73b0a2ad52eaee67ebd3b5613a2e4bedcea998ae1b4d25444c3","title":"","text":"Project description Virter is a command line tool for simple creation and cloning of virtual machines based on libvirt Metadata homepage URL: source URL: Blogs: , license: Apache v2 platforms: Linux only written in: go Thanks a ton!"}
{"_id":"doc-en-nixpkgs-5fcc445a4c409838c30e58ef3fb7d9ce03abe9a4a92afaa61434bff592be502d","title":"","text":"prints The message seems misleading as everything works as expected, even as a regular user. = { enable = true; locate = pkgs.mlocate; }; System: (NixOS: ) Nix version: () Nixpkgs version: ()\nThis still happens, although its a correct warning\nThat's surprising since it works for me without root. I only experienced issues when the wrong binary is used. If I recall correctly has higher priority and causes this. Can you check the output of or paste whatever error you get?\nSorry hit the wrong button by accident.\nThe warning is correct, but the wording is misleading. What it’s trying to warn you is not that will only run as , but rather that will run as . You can prevent the warning from being shown (with no other effect) by explicitly requesting that run as with .\nThis is warning is still confusing to me. If I'm building an index of files, I'd expect that if I run it as a non privileged user many files will not be reachable and therefore these won't end up in the locate database/index. Given the way works, I'd also expect to have one database per system, not one per user. So from this my expectation is that can only successfully index everything if run as . In other words, I'm still not sure what is the purpose or goal of the message. Is it just that the command needs to run as ? is this bad in any way? why is this special given the purpose of the tool? Is it that the fact that it runs as is in some way a security concern? Is this to clarify that despite the existence of an group (and user?) these are not actually used for indexing, or is the point something else entirely. Do other tools work in such a different way that justifies the existence of this warning for ?\nmlocate’s doesn’t have a option like findutils’ does. Therefore, the NixOS module ignores when using mlocate (). It prints a warning to indicate that your expectation has been violated. The group is there so that the mlocate binary can be setgid rather than setuid . Given that mlocate is designed with an that indexes everything and a that only shows you your own files, there doesn’t seem to be much point in running mlocate’s as another user."}
{"_id":"doc-en-nixpkgs-b62b950883453f459e5c83325bfd393fae19cd35e4f38c9784c51a56b6c12510","title":"","text":"If you want that, why not switch back to findutils?\nI see, in this context, the above makes sense. I actually want the full system indexing. To me has always been a synonym of , except several times faster. Thanks for the clarification!\nHello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as \"still important to me\". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .\nCould you include your commit in a pull request? I think that's a good solution and we can close this issue.\nIt’s been in this whole time.\nMy bad, I read only the latest updates and the pull request was higher up. Did a bit of noise on the pull request. It's a harmless change so I was surprised to see it sitting there for this long.\nTo avoid , this is needed: it's needed because it creates the group. That error happens when using: with or without: and then doing something like . But if not using the (so only using the alone) then there's no error, because the service itself uses a different package's by default, it's from package. The source: EDIT: I made some mistakes initially, you can see post history for that."}
{"_id":"doc-en-nixpkgs-d109b709baccabfabfae33e26af29b03af7b1b278580d27659240bd57020f704","title":"","text":"The pijul fetcher throws a certificate error when used, for example with the following command: Related: Steps to reproduce the behavior: fetchpijul (for example like in the command above) fails with above error Repository gets fetched successfully Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nOh my, thanks for notifying, I'll make a PR to fix that ASAP!"}
{"_id":"doc-en-nixpkgs-a132cb53a491f15abbade8cb851f73e41a2109e323f73f62ea6e00cb4bbd4ff3","title":"","text":"Project description Railway lets you look up travel information for many different railways, all without needing to navigate through different websites. Metadata homepage URL: source URL: license: gpl3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-a56b468a42312ff95c533a7f257b02d97cb988de6d8f84373957da9af58d4a42","title":"","text":"Describe the bug xscreensaver-demo is both a way to preview individual screensavers and the frontend for configuring xscreensaver. It should be installed alongside all the other xscreensaver binaries; however, it isn't, although its man page is. To Reproduce Steps to reproduce the behavior: Expected behavior is available in . Notify maintainers (raskin) Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-60a69067484323b15484d9a16cd667f1577bb836d9f250b1a5e4251fca0a3e99","title":"","text":"firejail bash . Error: cannot establish communication with the parent, exiting. . [milan ~]$ firejail --debug bash ~ Autoselecting /nix/store/fibk8jc2iwswn1q1d7aw98pcw2l3lzjf-bash-4.4-p12/bin/bash as shell Command name #bash# Attempting to find default.profile. Found default profile in /nix/store/y4ai4pgjizcanjahcfcd785i7n0h6r4q-firejail-0.9.44.8/etc/firejail directory Reading profile /nix/store/y4ai4pgjizcanjahcfcd785i7n0h6r4q-firejail-0.9.44.8/etc/firejail/default.profile Reading profile /nix/store/y4ai4pgjizcanjahcfcd785i7n0h6r4q-firejail-0.9.44.8/etc/firejail/disable- Reading profile /nix/store/y4ai4pgjizcanjahcfcd785i7n0h6r4q-firejail-0.9.44.8/etc/firejail/disable- Reading profile /nix/store/y4ai4pgjizcanjahcfcd785i7n0h6r4q-firejail-0.9.44.8/etc/firejail/disable- Note: you can use --noprofile to disable default.profile DISPLAY :0, 0 Using the local network stack Parent pid , child pid Initializing child process Host network configured PID namespace installed Mounting tmpfs on /run/firejail/mnt directory Mounting read-only /bin, /sbin, /lib, /lib32, /lib64, /usr, /etc, /var Mounting tmpfs on /var/lock Mounting tmpfs on /var/tmp Mounting tmpfs on /var/log Create the new utmp file Mount the new utmp file Cleaning /home directory Sanitizing /etc/passwd, UIDMIN 1000 Sanitizing /etc/group,"}
{"_id":"doc-en-nixpkgs-45c3fd10dc04ebb6c750c146431fc7f2aaa15a2df3ad263ba6062f3abd552c27","title":"","text":"GIDMIN 1000 Disable /run/firejail/network Disable /run/firejail/bandwidth Disable /run/firejail/name Disable /run/firejail/x11 Remounting /proc and /proc/sys filesystems Remounting /sys directory Disable /sys/firmware Disable /sys/hypervisor Disable /sys/module Disable /sys/power Disable /sys/kernel/debug Disable /sys/kernel/vmcoreinfo Disable /proc/sys/fs/binfmtmisc Disable /proc/sys/kernel/corepattern Disable /proc/sys/kernel/modprobe Disable /proc/sysrq-trigger Disable /proc/sys/vm/paniconoom Disable /proc/irq Disable /proc/bus Disable Disable /proc/timerlist Disable /proc/timerstats Disable /proc/kcore Disable /proc/kallsyms Disable /boot Disable /dev/port Disable /dev/kmsg Disable /proc/kmsg Disable /home/milan/.gnuplothistory Disable /home/milan/.zshhistory Disable /home/milan/.bashhistory Mounting read-only Disable Error: cannot establish communication with the parent, exiting. [milan ~]$ System: (NixOS: , Ubuntu/Fedora: , .) (Hummingbird) Nix version: (run ) nix-env (Nix) 1.11.8 Nixpkgs version: (run ) \"\"\nMay be caused by . Does the same occur with , and not with ?\nI'm having the same issue on Nixos 17.03. There at least it is exactly as you have described it, hence almost certainly the referenced issue.\nFailure: [milan nixpkgs]$ firejail --noprofile -- firefox /etc/nixos/nixpkgs Parent pid , child pid Error: invalid whitelist path Error: cannot establish communication with the parent, exiting... Success: [milan nixpkgs]$ firejail --noprofile firefox /etc/nixos/nixpkgs Parent pid , child pid Child process initialized\nYep, that does look like it's that issue."}
{"_id":"doc-en-nixpkgs-8839f31a07c662fb3d62cacfbcdbf05079bfa866ba325ecf94de8d6142a30872","title":"","text":"refuses to work since it requires the directories containing the scripts to have mode 755, but the nixos module creates them with mode 750. Steps to reproduce the behavior: (re)-configure an interface (for example by unplugging and replugging a network cable) something like in the journal and that does not exist, i.e. the hook was never run. networkd-dispatcher works. <!-- 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.\nThank you for the report! I'm thinking about adding a rules option to the networkd-dispatcher module so this might solve your issue"}
{"_id":"doc-en-nixpkgs-62916288d4a8c23b00820935d093b50004785eb9ca3805982341809067c3f2ea","title":"","text":"Project description fre:ac is a free audio converter and CD extractor for Microsoft Windows, Linux, macOS and FreeBSD, distributed under the GNU General Public License.[1] Besides extracting audio from compact discs (with various features including hidden track detection), fre:ac can also convert audio files from one format to another or to the same format but a lower bitrate. fre:ac is compatible with many audio formats such as Ogg Vorbis, FLAC, MP3, MP4/M4A, AAC, WAV, WMA and more.[2][3] fre:ac uses the CDex library to convert from CDs and uses freedb to retrieve artist/song information from the internet which is written to the files as various types of ID3 tags; this library supports cdparanoia which aims to improve audio quality.[4] The user interface is multilingual with 43 languages and is able to be a portable install on a USB drive. Metadata homepage URL: source URL: license: GNU General Public License v2.0 platforms: Windows, macOS, Linux, FreeBSD, HaikuOS\nfreac is already available on my nur repo If you want to avoid building it, it should be on my cachix https://scott- (for nixos-20.9, nixpkgs-unstable and nixos-unstable)"}
{"_id":"doc-en-nixpkgs-491084485d63eac944e29788cee1136c1c4d044642e6ab7aedd8b40bc709a4c2","title":"","text":"I'm using , and I'm trying to perform an update: The update works. (information found from )\nWhat does have to do with ? Can you reproduce the problem with just & ?\nBeginner here. I think that is using under the hood. I don't know how. Should I report this issue to instead?\nSounds like breaks vscodium darwin build :upsidedownface: I will do a PR"}
{"_id":"doc-en-nixpkgs-03391c100dddfbbf7629910288e846528643972f977069fbd929f1323928f78e","title":"","text":"defines a package option, but does not use it in the service definition. Steps to reproduce the behavior: an alternative package to use system is ignored As there is an option to set an alternative package, this setting should be honored. The current version of pkgs.pgmanage is broken, which was the motivation to actually use the package option."}
{"_id":"doc-en-nixpkgs-46a4ff97c3fc43e1dea4e6fca82c2f07fc8fa788a0966bf157cd656b6d0d6e1c","title":"","text":", CVSSv3=5.5 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.9 (nixos-21.11, nixos-unstable) CVSSv3=4.3 (nixos-21.11, nixos-unstable) Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Compiling). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Federated). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Stored Procedure). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior."}
{"_id":"doc-en-nixpkgs-5245e38332bf2b0eb2407c2e91ae4db23de8384c2b1ab27135047bf725bce903","title":"","text":"Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Parser). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H). Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 5.7.36 and prior and 8.0.27 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 4.3 (Integrity impacts)."}
{"_id":"doc-en-nixpkgs-0e3aaaa5c3bb6ba7a548770c25cea2398ebd364287654b609c75a220725910bf","title":"","text":"CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). Scanned versions: nixos-21.11: ; nixos-unstable: .\nSee also: , , , , , ,\nFixed: nixos-21.11: mysql-5.7.37, mysql-8.0.28 nixos-unstable: mysql-5.7.39, mysql-8.0.30"}
{"_id":"doc-en-nixpkgs-99661b6d06932d39c55ae576906316c3456f619b6a59b7f57ab46812aa567021","title":"","text":"Project description Universal Scene Description (USD) is an efficient, scalable system for authoring, reading, and streaming time-sampled scene description for interchange between graphics applications. OpenUSD is AFAIK the library to work with the USD format. Metadata homepage URL: source URL: license: Modified Apache 2.0 License platforms: unix, linux, darwin\nI've got a working derivation, but I'm not sure if this is already in a state that is good enough for a PR. In particular, packaging the pyside tools properly didn't seem straightforward to me. AFAICT, it just copies some binaries from other QT parts and wraps them with extra arguments, so that's what I'm doing here. While the python package seems to be working properly, I ran into an issue before when trying to include the headers into a C++ project, and I believe it failed to find some python headers? Maybe that needs some extra buildInput? I haven't investigated more. Locally, I've just been using a version compiled with for that. The binaries, such as , are working by my testing, besides requiring on wayland. I'd be happy to make a PR for this if this is a good-enough state."}
{"_id":"doc-en-nixpkgs-6a12f285928a5a1f2d26839763d02e6e3fd67322b60cd3de5fbc6a37a24f45cd","title":"","text":"CLion 2021.3.3 derivation fails to build. Steps to reproduce the behavior: to system/user packages The system rebuilds. Seems the folder has been renamed to just : Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(zane): channels(root): nixpkgs:\nSame issues here, waiting for fix : (\ncc"}
{"_id":"doc-en-nixpkgs-20ae3d2f401de1bf323d11751cc443d0166cf64024c9c1ca7a81487d2794b102","title":"","text":", CVSSv3=7.5 (nixos-20.03, nixos-unstable) CVSSv3=7.5 (nixos-20.03, nixos-unstable) CVSSv3=5.9 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc Cc\nA security update 1.6.24 addressing the vulnerabilities exists. I'd suggest marking openafs-1.6 as broken, now, to enforce migration to openafs-1.8. I am unaware of plans to further maintain openafs-1.6 beyond 1.6.24. Edit: Maybe, we should do both, update to 1.6.24 and mark it broken. So, users have a secure version as of now and still get the hint to take action.\nAlternative idea: Go with only openafs 1.8 on master and upgrade to openafs 1.6.24 on NixOS 20.03. This way, user must migrate to 1.8 when upgrading to NixOS 20.09 which is the only sensible action security wise.\nThis is fixed with the move to 1.6.24 for 20.09. Closed."}
{"_id":"doc-en-nixpkgs-e787eb33384c2434433943421bbe8a511a84113e77ac059a874265a75131e7ef","title":"","text":"Steps to reproduce the behavior: cryptowatch-desktop download url redirects to a blog Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nAs of September the 30th 2023, Cryptowatch was sunset and users were advised to use their parent companies offering Kraken Pro. I'll create a pull request to remove cryptowatch from nixpkgs as there aren't any archives available that contain it that are reliable"}
{"_id":"doc-en-nixpkgs-3e64177ee63037563bb76649cd2857f730a30427e9f48ee0a57a93463d6d8b0a","title":"","text":"Package name: Ollama Latest released version: 0.2.1 <!-- Search your package here: --- Current version on the unstable channel: 0.1.48 Current version on the stable/release channel: 0.1.38 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-f62d3b1fa23ca8382131ca29c2dfafea75706bd30962f26a66d246069c352e97","title":"","text":"Using on macOS requires using . Steps to reproduce the behavior: a new nix file: it with error The derivation and the built docker image work fine, and should build correctly even without . I believe this might be due to , while it's true docker cannot run macOS binaries, nix can be used to build Linux binaries on macOS, either by downloading them from a binary cache or by cross compiling, and those binaries can be put in docker images. cc\nThe fix is as simple as you suggest. I don't expect any problems with . Some users already do what you're doing but with ."}
{"_id":"doc-en-nixpkgs-bc862c2e5ef66c1bf2c9e93170997b9ca6cbef91067cde9fddda8eda9a154183","title":"","text":"Describe the bug The desktop file packaged with VSCodium specifies the wrong StartupWMClass To Reproduce VSCodium on the started application Expected behavior Step 4 prints . Therefore step 5 should print one of those strings. But instead, the file contains . Additional context Those must match or else the application won't be linked to the .desktop file when started. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels: nixpkgs: Maintainer information:\nI'm surprised says that the is . After all, for it seems to be , as , and as I also just tested on my system: After all, the executable for vscode is and for vscodium it's . Nevertheless, I can reproduce your output. Since I don't know whether that could be changed, it's probably easier to simply change the file. Will push a PR in a moment.\nI wish I could assign myself to this issue.\nI had a quick look at the history of the and they had it this way since the beginning. So I think it's safe to assume this won't change anytime soon."}
{"_id":"doc-en-nixpkgs-2a167e9714f2f45bd331e942cdd0b7f0220eab90f17823564c0b2f2a8d33ba29","title":"","text":"Project description Keeweb webapp is a browser and desktop password manager compatible with KeePass databases. It features an Electron-based desktop application. Metadata homepage URL: source URL: license: mit platforms: Electron (unix, linux, darwin, windows) and Web\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .\nstill important to me\nWhile PR to nixpkgs is still open, I've keeweb to NUR repo () as well."}
{"_id":"doc-en-nixpkgs-bfe694ad2b05a5627eb7b054b8f27b479100efb3ac856ae9a2e0f1edffc869f7","title":"","text":"Gives this error: , yet installing doesn't fix the problem. Steps to reproduce the behavior: Meteo That the Maps section works. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI have this exact issue. Hoping for some clarity.\nshould be here:"}
{"_id":"doc-en-nixpkgs-661bfdd5f097008cf54b42aac9cf6f5d33c1eeeb0a6311e48fd4b0a743076491","title":"","text":"Package name: Latest released version: 3.5 <!-- Search your package here: --- Current version on the unstable channel: 3.2 Current version on the stable/release channel: 3.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-d90a06ad50198db0c4976e4b75b3dced72f8999e584b9d301253e1173a1af221","title":"","text":"This might just be darwin; haven't tried on Linux. $ nix-shell -p these derivations will be built: /nix/store/dpcwgrlydrrlbdrnf0mi9hmr0kjvia89-python3.7-fire- building '/nix/store/dpcwgrlydrrlbdrnf0mi9hmr0kjvia89-python3.7-fire-'... unpacking sources unpacking source archive /nix/store/20rzw7yi3yvjb7w2ixzj6aqa5fim6p1q-source source root is source setting SOURCEDATEEPOCH to timestamp of file patching sources configuring building running bdistwheel The [wheel] section is deprecated. Use [bdistwheel] instead. running build running buildpy creating build creating build/lib creating build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire copying -build/lib/fire installing to running install running installlib creating creating creating copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - copying - running installegginfo running egginfo creating writing writing dependencylinks to writing requirements to writing top-level names to writing manifest file '' reading manifest file '' reading manifest template '' writing manifest file '' Copying to running installscripts creating creating 'dist/fire-0.1.3-py2."}
{"_id":"doc-en-nixpkgs-27619e1bcccb3b1a2026f1e483f5512d36b3ab24bbdb7259fdef838292fcde3b","title":"","text":"py3-none-' and adding '' to it adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding '' adding 'fire-' adding 'fire-' adding 'fire-' adding 'fire-' adding 'fire-' removing installing /private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire- /private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire- Processing ./fire-0.1.3-py2.py3-none- Requirement already satisfied: six in /nix/store/qayyh24znx8kixy7wqz6i5416nyljzxk-python3.7-six-1.12.0/lib/python3.7/site-packages (from fire==0.1.3) (1.12.0) Installing collected packages: fire Successfully installed fire-0.1.3 /private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire- post-installation fixup strip is /nix/store/3ibh116gnggzgsvrq8vvalmqyipk8cy9-cctools-binutils-darwin/bin/strip stripping (with command strip and flags -S) in /nix/store/b96a60g0apqx015sscpv8jywnjd8svcq-python3.7-fire-0.1.3/lib patching script interpreter paths in /nix/store/b96a60g0apqx015sscpv8jywnjd8svcq-python3.7-fire-0.1.3 running install tests ============================= test session starts ============================== platform darwin -- Python 3.7.2, pytest-4.2.1, py-1.7.0, pluggy-0.8."}
{"_id":"doc-en-nixpkgs-a55f5496cbb21c3902eb6cf66a6c37023a26669d7d33ef1db5a86ce8843c59ae","title":"","text":"1 hypothesis profile 'default' -database=DirectoryBasedExampleDatabase('/private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire-') rootdir: /private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire-, inifile: plugins: hypothesis-4.7.3 collected 160 items . [ 0%] ...... [ 4%] ... [ 6%] .. [ 7%] .............. [ 16%] ............. [ 24%] ........... [ 31%] ... [ 33%] ...............F........F..................... [ 61%] .F........ [ 68%] .F....... [ 73%] .. [ 75%] .................... [ 87%] .. [ 88%] ... [ 90%] ............... [100%] =================================== FAILURES =================================== _ FireTest.testFireKeywordArgs _ self = <fire.firetest.FireTest testMethod=testFireKeywordArgsdef testFireKeywordArgs(self): self.assertEqual( fire.Fire( tc.Kwargs, command=['props', '--name', 'David', '--age', '24']), {'name': 'David', 'age': 24}) # Run this test both with a list command and a string command."}
{"_id":"doc-en-nixpkgs-89c09656844c2d12101e0e68dbaff17e7f875df53986563b7a0f1888bda93c07","title":"","text":"self.assertEqual( fire.Fire( tc.Kwargs, command=['props', '--message', '\"This is a message it has -- in it\"']), # Quotes stripped {'message': 'This is a message it has -- in it'}) self.assertEqual( fire.Fire( tc.Kwargs, command=['props', '--message', 'This is a message it has -- in it']), {'message': 'This is a message it has -- in it'}) self.assertEqual( fire.Fire( tc.Kwargs, command='props --message \"This is a message it has -- in it\"'), {'message': 'This is a message it has -- in it'}) self.assertEqual( fire.Fire(tc.Kwargs, command=['upper', '--alpha', 'A', '--beta', 'B']), 'ALPHA BETA') self.assertEqual( fire.Fire( tc.Kwargs, 'alpha beta') component = <class 'fire.testcomponents.Kwargs'command = ['upper', '--alpha', 'A', '--beta', 'B', '-', ...], name = '' def Fire(component=None, command=None, name=None): \"\"\"This function, Fire, is the main entrypoint for Python Fire. Executes a command either from the argument or from by recursively traversing the target object 's members consuming arguments, evaluating functions, and instantiating classes as it goes. When building a CLI with Fire, your main method should call this function. Args: component: The initial target component. command: Optional. If supplied, this is the command executed. If not supplied, then the command is taken from instead. This can be a string or a list of strings; a list of strings is preferred. name: Optional. The name of the command as entered at the command line. Used in interactive mode and for generating the completion script. Returns: The result of executing the Fire command. Execution begins with the initial target component. The component is updated by using the command arguments to either access a member of the current component, call the current component (if it's a function), or instantiate the current component (if it's a class). When all arguments are consumed and there's no function left to call or class left to instantiate, the resulting current component is the final result. Raises: ValueError: If the command argument is supplied, but not a string or a sequence of arguments."}
{"_id":"doc-en-nixpkgs-7ed6d7956c724ec4d52e801d58e20099ff6e2902b04123ba3838dd080c48bc72","title":"","text":"FireExit: When Fire encounters a FireError, Fire will raise a FireExit with code 2. When used with the help or trace flags, Fire will raise a FireExit with code 0 if successful. \"\"\" name = name or ([0]) # Get args as a list. if isinstance(command, six.stringtypes): args = (command) elif isinstance(command, (list, tuple)): args = command elif command is None: # Use the command line args by default if no command is specified. args = [1:] else: raise ValueError('The command argument must be a string or a sequence of ' 'arguments.') # Determine the calling context."}
{"_id":"doc-en-nixpkgs-9196ddead4a612d77342fc7ba89a52fc0b7cc35096a67427733815abf9af56a7","title":"","text":"caller = ()[1] callerframe = caller[0] callerglobals = callerframe.fglobals callerlocals = callerframe.flocals context = {} (callerglobals) (callerlocals) componenttrace = Fire(component, args, context, name) if componenttrace.HasError(): for helpflag in ['-h', '--help']: if helpflag in componenttrace.elements[-1].args: command = '{cmd} -- --help'.format(cmd=componenttrace.GetCommand()) print(('WARNING: The proper way to show help is {cmd}.n' 'Showing help anyway.n').format((command)), ) print('Fire trace:n{trace}n'.format(trace=componenttrace), ) result = componenttrace.GetResult() print( helputils.HelpString(result, componenttrace, componenttrace.verbose), ) E 2 FireExit ----------------------------- Captured stdout call ----------------------------- name: David age: 24 message: This is a message it has -- in it message: This is a message it has -- in it message: This is a message it has -- in it ALPHA BETA ----------------------------- Captured stderr call ----------------------------- Fire trace: Initial component Instantiated class \"Kwargs\" (/private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire-) Accessed property \"upper\" (/private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire-) Called routine \"upper\" (/private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire-) Accessed property \"lower\" ('The function received no value for the required argument:', 'self') Type: builtinfunctionormethod String form: <built-in method lower of str object at 0x1116ffef0Docstring: Return a copy of the string converted to lowercase."}
{"_id":"doc-en-nixpkgs-dd70131bf0c29d8aaf0c5143df0ea3bd5e25a2f8d2fefb230969ddf37262141c","title":"","text":"Usage: upper --alpha A --beta B - lower SELF upper --alpha A --beta B - lower --self SELF _ FireTest.testFireObjectWithDict _ self = <fire.firetest.FireTest testMethod=testFireObjectWithDictdef testFireObjectWithDict(self): self.assertEqual( fire.Fire(tc.TypedProperties, command=['delta', 'echo']), 'E') self.assertEqual( component = <class 'fire.testcomponents.TypedProperties'command = ['delta', 'echo', 'lower'], name = '' def Fire(component=None, command=None, name=None): \"\"\"This function, Fire, is the main entrypoint for Python Fire. Executes a command either from the argument or from by recursively traversing the target object 's members consuming arguments, evaluating functions, and instantiating classes as it goes. When building a CLI with Fire, your main method should call this function. Args: component: The initial target component. command: Optional. If supplied, this is the command executed. If not supplied, then the command is taken from instead. This can be a string or a list of strings; a list of strings is preferred. name: Optional. The name of the command as entered at the command line. Used in interactive mode and for generating the completion script. Returns: The result of executing the Fire command. Execution begins with the initial target component. The component is updated by using the command arguments to either access a member of the current component, call the current component (if it's a function), or instantiate the current component (if it's a class). When all arguments are consumed and there's no function left to call or class left to instantiate, the resulting current component is the final result. Raises: ValueError: If the command argument is supplied, but not a string or a sequence of arguments. FireExit: When Fire encounters a FireError, Fire will raise a FireExit with code 2. When used with the help or trace flags, Fire will raise a FireExit with code 0 if successful. \"\"\" name = name or ([0]) # Get args as a list. if isinstance(command, six.stringtypes): args = (command) elif isinstance(command, (list, tuple)): args = command elif command is None: # Use the command line args by default if no command is specified."}
{"_id":"doc-en-nixpkgs-e6844850dcec93aa30edfbd69891dd9309d4125bee813550b84ba26d7133bfb0","title":"","text":"args = [1:] else: raise ValueError('The command argument must be a string or a sequence of ' 'arguments.') # Determine the calling context. caller = ()[1] callerframe = caller[0] callerglobals = callerframe.fglobals callerlocals = callerframe.flocals context = {} (callerglobals) (callerlocals) componenttrace = Fire(component, args, context, name) if componenttrace.HasError(): for helpflag in ['-h', '--help']: if helpflag in componenttrace.elements[-1].args: command = '{cmd} -- --help'.format(cmd=componenttrace.GetCommand()) print(('WARNING: The proper way to show help is {cmd}.n' 'Showing help anyway.n').format((command)), ) print('Fire trace:n{trace}n'.format(trace=componenttrace), ) result = componenttrace.GetResult() print( helputils.HelpString(result, componenttrace, componenttrace.verbose), ) E 2 FireExit ----------------------------- Captured stdout call ----------------------------- E ----------------------------- Captured stderr call ----------------------------- Fire trace: Initial component Instantiated class \"TypedProperties\" (/private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire-) Accessed property \"delta\" Accessed property \"echo\" Accessed property \"lower\" ('The function received no value for the required argument:', 'self') Type: builtinfunctionormethod String form: <built-in method lower of str object at 0x1100c7340Docstring: Return a copy of the string converted to lowercase."}
{"_id":"doc-en-nixpkgs-665276dca58a1dbc5994591bc5e00e7271986f578e8f6d1fbefba3712b3e8342","title":"","text":"Usage: delta echo lower SELF delta echo lower --self SELF __ HelpUtilsTest.testHelpStringBuiltin _ self = <fire.helputilstest.HelpUtilsTest testMethod=testHelpStringBuiltindef testHelpStringBuiltin(self): helpstring = helputils.HelpString('test'.upper) self.assertIn('Type: builtinfunctionormethod', helpstring) self.assertIn('String form: <built-in method upper of', helpstring) E AssertionError: 'Usage: [VARS ...] [--KWARGS ...]' not found in 'Type: builtinfunctionormethodnString form: <built-in method upper of str object at 0x11028d458nDocstring: Return a copy of the string converted to uppercase.nnUsage: SELFn --self SELF' AssertionError _ InspectUtilsTest.testGetFullArgSpecFromBuiltin _ self = <fire.inspectutilstest.InspectUtilsTest testMethod=testGetFullArgSpecFromBuiltindef testGetFullArgSpecFromBuiltin(self): spec = inspectutils.GetFullArgSpec('test'.upper) E AssertionError: Lists differ: ['self'] != [] E E First list contains 1 additional elements."}
{"_id":"doc-en-nixpkgs-16d011d8d63653f557664cfc7c39b0a397ed60e3c8f6590452790ccc62354d2a","title":"","text":"E First extra element 0: E 'self' E E - ['self'] E + [] AssertionError =============================== warnings summary =============================== /private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire- DeprecationWarning: 'U' mode is deprecated self.fromlines = open(fromfile, 'U').readlines() /private/var/folders/8g/qgvf93s1b40dd8nhsvqkm0000gn/T/nix-build-python3.7-fire- DeprecationWarning: 'U' mode is deprecated self.tolines = open(tofile, 'U').readlines() -- Docs: ============== 4 failed, 156 passed, 12 warnings in 1.80 seconds =============== builder for '/nix/store/dpcwgrlydrrlbdrnf0mi9hmr0kjvia89-python3.7-fire-' failed with exit code 1 error: build of '/nix/store/dpcwgrlydrrlbdrnf0mi9hmr0kjvia89-python3.7-fire-' failed nix-shell -p nix-info --run \"nix-info -m\" system: host os: multi-user?: sandbox: version: channels(abathur): nixpkgs: FWIW, I'm also running bash 5 () as my default shell atm, but I see the same error when I manually run launch a bash 4 () shell to run this in. I haven't updated channel in a bit but I don't see any open/recent issue or PR."}
{"_id":"doc-en-nixpkgs-f424a3f56593c54ee809a9f0470bdd9e2f10ab34a2409c079e246608d8505f04","title":"","text":"Relevant snippet while building it fails with I copied over the for debugging, this is the full output: Steps to reproduce the behavior: snippet as flake default output Build should succeed and images should be loadable via Patching the as follows: fixes the problem, but would probably hide other cp errors. Maybe the behavior of coreutils/cp changed in the recent versions. At least the current manual states it will fail silently. I'm using a linux-builder on my machine.\nThank you for reporting this. I’ll try to replicate this locally. The lines do not look like errors to me. It looks like is informing that those files already exist in the output and thus are skipped (--no-clobber). However, if the build is failing there’s something going wrong.\nThank you for linking the manual. It looks like will exit with a non-zero status code in case of files that are already present now. The coreutils changelog states that now reproduces the behavior had at the time I wrote the mergeImages script. I was able to build by changing to . I don't know how to best go about obtaining the behavior everywhere, should the flag be dependent on the version of somehow? Maybe we can just assume that in will be a new version from now so that we can use everywhere? Given that all files that are present in both docker images apart from the and repositories files should be content addressed the only issue with removing is that time is spent unnecessarily writing content that's already present, so removing the flag altogether might make sense.\nThanks for investigating! I'm not familiar with the backward compatibility policy of the nix ecosystem, but I would assume that the most recent version of can assume most recent coreutils. Might happen that someone is overlaying old coreutils but then you might just need to overlay the old too, if you can pinpoint it down to coreutils cp.\nTrue, but then apparently they have a legacy software problem, in which case they should use overrides only where it is necessary, instead of a blanket override in an overlay. It is not realistic to expect all of Nixpkgs to work with arbitrary changes. The cost of such compat logic isn't worth it; certainly not in this case, until proven otherwise. If they contribute a full time maintainer it is worth it, and if they have a legacy software problem they probably can."}
{"_id":"doc-en-nixpkgs-9f2264431e3c40bb9ef4a6f4e2776817beb743764fa592ed9f4d530cdb730a6a","title":"","text":"Optipng crashes with a segmentation fault on current as of . points to the library used to throw/catch exceptions. relevant source: Automatic points to being the first bad revision. However, I don't have enough knowledge of this piece of nix to understand why it causes optipng to fail in the . System: nixos-master Nix version: 1.11.11 Nixpkgs version: Sandboxing enabled: yes CC\nReading into the causing commit's comments made me try which seems to work around the issue. However, I'm hesitant to commit this as a fix without understanding the issue here.\nSo some packages use the C compiler instead of linker directly to link. Nixpkgs's cc-wrapper is aware of this, for example, with separate and environment variables. Classic make builtin rules however only have , , , and , so then either in a configure script or make itself they seem to default to , but manually specifying breaks this. Manually specifying , however, avoids that pitfall, and, unlike , will also work for cross compilation.\nHere's a blurb from optipng's script: If I understand your comment, it looks like optipng's build system is doing precisely what you describe: So when isn't set, it defaults to configuring the such that it uses as the linker, and I suppose the theory is that they depend on behavior available when invoking through e.g. (though I don't know precisely what that may be). It would seem reasonable take the (on a per package basis) approach as a solution. I think this can safely be considered a bug in the upstream packages' build systems.\nProbably the use of to pass actual ld flags, e.g. .\nI implemented the workaround in . Feel free to reopen this if you don't think the fix to be adequate."}
{"_id":"doc-en-nixpkgs-7ce8589c711d1269ddb5190541e78bb03666d549e4541ef005a9de062136a94a","title":"","text":"gcc5 and the dependant gfortran5 packages are failing as of 31 July Failures: ] ] Building either package using or fails. System: (MacOS 10.11.6 and MacOS 10.12.6, both nix-multiuser install) Nix version: (1.11.13) Nixpkgs version: (17.09pre-git) Sandboxing enabled: (relaxed)\nhas been looking into this but it seems pretty mysterious so far\ngit-bisect is pretty neat\ncc\nThis is also needed to fix things that depend on gcc"}
{"_id":"doc-en-nixpkgs-c4082bc039b9a317a77e5be9f0d4abeb0e6e5d738ec8c7e1f0761233e984a219","title":"","text":"Package name: edgedb Latest released version: 3.2.0 Current version on the unstable channel: 2.3.1 Current version on the stable/release channel: 2.3.1 Notify maintainers Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-8c226cdf14328097affdddf62e31df605d3b972e29a8cf089b96914ea49816b3","title":"","text":"Steps to reproduce the behavior: FWIW: my fix is here, - but it is using a fork of . If somebody has the time to create a minimal patch on top of the current source, please feel free to. Please run and paste the result.\nLooks like you are on a good path. Unfortunately I have no access to Apple hardware at all, but would be happy to merge a PR.\nYes, is working on it. There is a more active fork of luabind here: - how about we switch to using it? It'll obviate a bunch of patches as well.\nI agree, sounds sensible."}
{"_id":"doc-en-nixpkgs-7b11395bac5f506c4f06c950b95176a1daa7f409efbcb696556c5fd8ff4bceaf","title":"","text":"I get the error: It seems that this problem is related to There is no problem for System: 17.03pre94121. (Gorilla) and on master Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: 17.03pre94121.\nit seems the tests depend on a package like"}
{"_id":"doc-en-nixpkgs-11f04ac68f392a4e654a74737d7272aebe9fd01d8e3ad51add3c50e5fb7e1666","title":"","text":"XOrg crashes when certain applications are launched. More details here: Steps to reproduce the behavior: any of the IntelliJ IDEs. You may have to set anti aliasing to greyscale. Xorg will crash. Xorg doesn't crash. This is the bug: It looks like a security fix caused this regression. Ubuntu has already applied patches that fix this for Xorg and Xwayland: see this message from the above Ubuntu thread: NixOS should use the same patches until this is fixed upstream in XOrg. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSounds like this will be addressed by this update:\nxwayland too: looks like updating xorg and xwayland to their latest versions will do the trick then\nxwayland was bumped to the latest version in PR"}
{"_id":"doc-en-nixpkgs-d91cd50d7ffff5f4415b14ccf0050d29ccb79fbf76616b3141ee9b85180aff7d","title":"","text":"Installing results in a broken application that exits on startup with the message \"GEGL operation missing! Glimpse requires the GEGL operation \"gegl:introspect\". This operation cannot be found. Check your GEGL install and ensure it has been compiled with any dependencies required for Glimpse.\" Steps to reproduce the behavior: to Glimpse Glimpse should work! works fine for me. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:\nThanks for the report, Unfortunately I cannot reproduce your issue. Neither on as you reported nor on current . Could you elaborate on your setup a bit? Which window manager/desktop environment are you using? Is it possible that you modified glimpse in an overlay? I'm running Sway (Wayland) and deleted and before testing to make sure I didn't have any leftover state in my home directory.\nI'm using i3wm (with no separate desktop manager); I installed Glimpse by adding it to environment.systemPackages in , I don't think there's any chance I did anything special with overlays there. I can't think of anything else I've done that might have affected this – I only installed NixOS a few days ago. I do have Home Manager installed, so I guess is it possible that something I've installed via that is causing a problem? (I don't have that much stuff installed, though, I don't think.) on my system is a tmpfs, so if something put a file outside of /nix or /home on install and is expecting it to still be there then it'll be unhappy, but I think I tried running Glimpse immediately after installing it with and it didn't work even then, so it shouldn't be anything related to that. Deleting changes the icon in the popup, which is weird, it looks like this if that directory isn't present at statup: ! and like this if I leave the directory there: ! but nothing else seems to change. (I noticed there's a directory in and , but removing it doesn't seem to do anything.)\naha, I found the problem: works just fine, and adding graphviz to environment.systemPackages fixes it permanently. see e.g."}
{"_id":"doc-en-nixpkgs-b9320ed5944f57cb6d86264b171c8777f0d14df0b3d2a6c1c5459bcce6cfdb61","title":"","text":"Ooh nice, didn't think about using a pure nix-shell to circumvent already installed packages clouding the issue. Now I'm able to reproduce the issue. Will add graphviz as runtime dependency then.\nLooks like Gimp is not affected, as they got it . Glimpse didn't receive that fix, and it won't in the foreseeable future as the project ."}
{"_id":"doc-en-nixpkgs-8bac55323962f27e74f8e35e9b9490705b3357d6e5124a72edfb1c7ab0f4008a","title":"","text":"Steps to reproduce the behavior: (warning: veeery long) Seems caused by Also previously reported (if I'm reading the many thousands of lines of output right) to be another instance of Breaks: .\nThis appears to have been fixed somewhere between and\nI have no idea how you tested, but after a (pulling branch), I fail to build this same package. Now with the newer hash: I vote for this issue to be marked as \"prematurely-closed\", and thus re-opened.\ndebugpy was blocking my nixos rebuilds through . Updating to resolved it for me. That's about all the testing I did at the time, and figured it was good. Sorry about that.\nYep! Looks like this is related to flaky process test timeouts (which are more likely to fail on less powerful / overworked devices). should fix this!\nYou can checkout to see when the fix will be applied to the channel you're using."}
{"_id":"doc-en-nixpkgs-41b5f2fdb04297b0cc8af1214da8b06683d55b551f8625bc942f2c672f89d525","title":"","text":"Project description Flawfinder is a simple program that scans C/C++ source code and reports potential security flaws. It can be a useful tool for examining software for vulnerabilities, and it can also serve as a simple introduction to static source code analysis tools more generally. It is designed to be easy to install and use. Flawfinder supports the Common Weakness Enumeration (CWE) and is officially CWE-Compatible. Metadata homepage URL: source URL: license: gpl2 platforms: unix, linux, darwin\ncould you please test Thanks\nWorks for me on NixOS. I wrote a simple c program that it found the vuln in: where it gave:"}
{"_id":"doc-en-nixpkgs-0af86241f29b7a4801588018a0812989b5676dcd9c78c6c55224d1b2adaf6e1f","title":"","text":"<!-- 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 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: <!-- The current version can be found easily with the same process than 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: 4.6.3 desired version: 4.11.2 <!-- 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."}
{"_id":"doc-en-nixpkgs-9b7bc3db0617b835a57320ae7bd0b694e39c06807fa7d0e99ea5c2cc5386b7cf","title":"","text":"Not all the executables of the /contrib directory are patched, so some functionalities of the theorem prover fail. For instance, running the Sledgehammer tool (subwindow in the bottom bar of Isabelle starting window) always fail with: The directory: The sub directories marked with a star contain the x64 executables I tried to execute manually and I got: \"Not such file or directory\" Run Isabelle and try to use Sledgehammer. Then try to execute the executables in the marked directories, and you will obtain \"Not such file or directory\". System: 16.03.1171. (Emu) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: \"16.03.1171.\" I am definitely new to NixOS, but with my nonexistent experience I think at least two solutions are available: 1) I can substitute the broken software with the packaged one, as it is done with Java and Polyml in the Isabelle2016 derivation; 2) I can patch the executables with patchelf (hopefully). I did not have time to try these so far, but I was wondering how difficult would be the 2nd: I think that using (1) can potentially break Isabelle since we would use different versions of the software in /contrib. You guys are amazing! Thanks a lot for NixOS!!! It is the most elegant OS I ever tried!\nHello, after some experimenting, I found a hack to make Isabelle work in Nixos Emu x64: this derivation substitutes the broken provers and rebuilds the exec-process executable. What I do not like of this solution: the provers are not the same (versions) of the Isabelle distribution, and this works only for x64 -- if you use a 32 bit you have just to change (take away the_64 bit from the target directory name) the derivation after the comment in the postPatch phase. However it works. Hopefully someone more expert than me can propose a better solution! Thanks again!!"}
{"_id":"doc-en-nixpkgs-9dff3c872933d75ba5392a8d2f440532bbeefa56cdb1a06de8dd9236f1a355f4","title":"","text":"<!-- 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: <!-- 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.1.1 desired version: 2.1.3 <!-- 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. It seems that this version has a few changed dependencies ( instead of )"}
{"_id":"doc-en-nixpkgs-d46f41222db91cd0b6568933c467c043cfc980f4f933c47467f509f6d2955cc1","title":"","text":"The is failing to build Steps to reproduce the behavior: Package should build\nrelated to\nThis is unrelated, GNOME 43 is not yet released. Most likely this was caused by gobject-introspection changes.\ngobject-introspection should be in nativeBuildInputs instead of buildInputs"}
{"_id":"doc-en-nixpkgs-295c95b84f8a70e1053607b78a625a20875fd22045a7532b4fea1c299addf4b3","title":"","text":"fails when building the wheel for pip. (Building the wheel for wheel succeeds.) Steps to reproduce the behavior: Build succeeds as it does for regular Python: (there are no maintainers given)\nWhich branch is this on?\n~Can't reproduce this on master nor on nixos-22.05.~ pypy version succeeds, pypy3 version fails. master and nixos-22.05\nProbably also on 21.11. -No, 21.11 is fine. -\nEncountered on Nixpkgs 21.11 system: host os: multi-user?: sandbox: version: nixpkgs:\nBisected to the 7.3.7 update. Newer pypy3 versions exhibit the same problem. Our pypy3 package set is clearly unmaintained. cc\nFixed in ."}
{"_id":"doc-en-nixpkgs-683f2f198c5aea79e1bcc2b4383f1c4b428a18338368d83820b20c6636202f94","title":"","text":"The package hard-codes various X11 libraries as dependencies while making many other features optional, including GUIs. It would be nice to have an option to disable the X11 feature and the related . The use case I have in mind is installing a custom Vim on a remote server. Pulling X libraries, even without enabling a GUI, adds a few dozen megabytes for something essentially useless. An approach is doing something like this: but it doesn't feel very clean... Any thoughts from or ?\nI agree. It would have been nice if these X dependencies would have been to only if is or .\n/me whispers neovim~~~\nI'm all for testing new things and neovim is on my list. But according to , the neovim package pulls 428MiB of dependencies, half of which for Ruby, the other half for both Python 3 and Python 2 (seriously?). Is there a way, by any chance, to configure neovim to avoid this bloat ?\nadmittedly I've never tried to configure a mininmal version but one can unselect these ecosystems:\nSee ."}
{"_id":"doc-en-nixpkgs-3ce5fc31c98e9ece16f0ed9831900ba85a32fd640b9c2976ad3ee28120e1f3ff","title":"","text":"is empty. As a result plugin is not loaded and there is no socket. Relevant part of build log: There must be python instead of : before ./format- ^^^"}
{"_id":"doc-en-nixpkgs-2c09e816266609e0ab582391acf2d3c5aa53aa295f27743913810ca9a0a36478","title":"","text":"Package name: sqlx-cli Latest released version: 0.7.3 <!-- Search your package here: --- Current version on the unstable channel: 0.7.1 Current version on the stable/release channel: 0.7.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI'll take a look at this tomorrow. Thanks for the ping."}
{"_id":"doc-en-nixpkgs-acb1279b4cee9833c213a167499702550e05e43386ff19f5e592fab861225771","title":"","text":"Project description This allows applications like Discord that use xwayland to capture Wayland windows. Metadata homepage URL: source URL: license: GPL2+ platforms: Linux\nI wanted to test this and packaged it my config repo. I'm not interested in being a maintainer, but I can submit a PR or someone else can feel free to use mine as a base. The project is definitely beta though cause it segfaulted when resizing Dolphin and crashed Plasma entirely.\nIf this is the wrong place to post, please let me know. I can see the package here under However I'm getting the following error after adding to systemPackages when switching:\nI guess you jsut want to \"cherry-pick\" xwaylandvideobridge from unstable, but the rest of your system follows e.g. stable by default? First you add unstable channel if not already done and refresh the package definitions: Import it in your And then you add it to your systemPackages via ."}
{"_id":"doc-en-nixpkgs-271de1d030518bd6d25f0bd3e39ec9a1557135c22c8c66d286322429b0c219a5","title":"","text":"Describe the bug getting when trying to scan over network (scanning from the , scanner device connected to via usb) To Reproduce Steps to reproduce the behavior: server config: client config: on the : choose the network scanner : stops scanning immediately, server logs have an entry: from Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Guessing here, looking at the commit log for the service definition, apologies for pinging a lot of people: Metadata Please run and paste the result. server (managed via nixpkgs): client: Maintainer information:\nI marked this as stale due to inactivity. &rarr;\nPlease test\nnice ! will do in few days as I'm moving house :)\nHi just tested it now and it works very well !\napprove the pr"}
{"_id":"doc-en-nixpkgs-7eef30cebaaa96e00d3e80bb3f2ff26ac4dc8d0fe124f10ab9d4b0a2ab593b9b","title":"","text":"Describe the bug The recent Haskell generic-builder changes for Darwin (in particular according to bisect) have broken . To Reproduce from a nixpkgs at or later on Darwin. This fails with . Additional context is a pure Haskell package, that depends on , which is what actually uses the C dynamic library. So the problem seems to be that fails to include the C library in its closure. Interestingly, this C library has filename not , even though it looks exactly like a dylib as far as I can tell (I'm not expert in macOS linking): So I can see why would fail to be included into by . However, I don't see why broke it. Nothing to do with the C or Haskell packages involved has changed for months. Updating the generic-builder to include as well as files does fix the problem for me, and seems benign, so I'll submit a PR for that. But I don't feel I understand everything going on here, so I'm opening the issue in case more qualified folks can identify a better root cause fix. Metadata system: host os: multi-user?: sandbox: version: channels(simon): nixpkgs: Maintainer information: Ping from the original changes - thanks for all your efforts!\nJust noting here that there is some useful discussion ."}
{"_id":"doc-en-nixpkgs-58889e398d9cca351d0d9fb05c27c94c3e7e69d5aa212f004a34b5e66c93e657","title":"","text":"Not sure if this is known, but I'm seeing the following error when trying to do . System: Fedora 23 Nix version: 1.11.2 Nixpkgs version: 16.09pre81657."}
{"_id":"doc-en-nixpkgs-f5aa09c278e45e363a7e030c2d375ae27375ce7cd999cacd5fb6e505b766f449","title":"","text":"I currently cannot execute any 32 bit Linux binaries on my 64 bit system and this breaks updates, since I have 32 bit support enabled in the nix options: I remember that this worked about a week ago, so something has changed. I am new to NixOS, so its possible that I have done something wrong. I used ArchLinux for about 9 years before that and now NixOS for just 3 months and its concepts are still foreign for me. As a long term linux user (about 15 years) I do feel a bit out of place in NixOS. So I am not sure how to fix that myself. Not sure. I have wine installed and support for 32 bit games enabled. Then I normally do just 'nixos-rebuild switch --upgrade' to upgrade, and sometimes 'nix-channel --update'. I also regularly do 'nix-collect-garbage -d'. No idea if that is reproducible or not.\nThis might be from Could you see if it works without that commit? Also verify that /nix/store/4qj9vzggfzsc34ci79ckaim5cjrwc6ns-bash-4.4-p23/bin/bash executes. I can run it on my system. You can run this to verify that your store is not corrupted:\nI solved it now for me. Instead of using the 'linuxPackagestestinghardened' 4.20 linux kernel I switched back to 'linuxPackages419' 4.19.2 kernel and now executing 32 binaries work again. So I guess the hardened kernel does not support executing 32 bit binaries. Does it make sense to have some kind of visible warning here? I normally would not have used the hardened kernel, if that wouldn't have been the only 4.20 version is I get. Its not clear to me when and how those changes in master appear in my nixpkgs/nixos channel (I am on unstable). I would like to use the master branch directly, but I haven't figured out how to best do that yet.\nThe same here, hardened kernel 4.18.17 and build failed."}
{"_id":"doc-en-nixpkgs-438fdf44847d4143cf60f14288a7ffd98e0a7d7a282027de46cb766976bea0b8","title":"","text":"building '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxcdxtn-'... while setting up the build environment: executing '/nix/store/xgf4vra77qrww0n228hd80jsdccdp54w-bash-4.4-p23/bin/bash': Exec format error builder for '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxcdxtn-' failed with exit code 1 building '/nix/store/cfwj5yjby2xvagyj69zd1yx8hdhi27ay-'... cannot build derivation '/nix/store/maynq4fxxjc217figygdrgg5q9xnw6yy-mesa-drivers+txc-': 1 dependencies couldn't be built cannot build derivation '/nix/store/wv9b4ayvgnpkvwz81zkk0lm9w4v5pd1y-opengl-drivers-': 1 dependencies couldn't be built cannot build derivation '/nix/store/q61vc27rdbcsrhxifiw89w1qdjax1amh-nixos-system-brix-': 1 dependencies couldn't be built error: build of '/nix/store/q61vc27rdbcsrhxifiw89w1qdjax1amh-nixos-system-brix-' failed Thanks\nMaybe the hardened kernel shouldn't set when NixOS' is an ?\nIt should be 64 bit for the x86_64-linux stdenv. But some packages use the i686 stdenv.\nI am not too familiar with stdenv. Is this expected behaviour that a 64-bit system uses 32-bit binaries? This issue is reproducible building as well.\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity."}
{"_id":"doc-en-nixpkgs-9ded393087ff070a9a48c29a7c92f759cf78f68c04905f287b2e2460a9e5ab95","title":"","text":"Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .\nThis should be resolved by - please reopen if there's still a problem."}
{"_id":"doc-en-nixpkgs-51d245dbd6bc119eb68f30fb419af589f321780888e879900bda0928bfd1cffb","title":"","text":"<!-- 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: rtl-sdr <!-- 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: 0.6.0 desired version: 0.8.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: This package is currenty using but it should probably switch to Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-10b508ff32ad59767ceed9c92e86ec6bc90afe0fc1abab6bc30bae53b7ac862a","title":"","text":"Describe the bug Gitlint fails to build due to a dependency on click v7.1.2 To Reproduce Steps to reproduce the behavior: Expected behavior Successful build of gitlint Screenshots ! Additional context Looks like click got separated into two packages, one where it updated to 8.0.1 and is present in and one where it was kept back for . Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(david): nixpkgs: Maintainer information:\nYeah this is interesting. As far as I know, things shouldn't just break like this. I assume this is a regression, as it used to build, it seems a LOT of stuff has started breaking.\ndoesn't work with later releases. We have 8.0.1 and is pinning all releases (affects also , I guess). It would requires that is overriding the releases.\ncould you please give a try?\nLooks to be good on my system. Runs as intended with"}
{"_id":"doc-en-nixpkgs-d5054cf1390cbd8063bf634f0bab0a007b41d30c0f62eef7a3a8067646e6a4f1","title":"","text":"Project description The elevator pitch: But it's mostly used to install and run AI applications pretty easily, the creator made this video: Which is the same as on the homepage. Metadata homepage URL: https://pinokio.computer/ source URL: license: MIT platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI created a PR based on this packaging request."}
{"_id":"doc-en-nixpkgs-9f19776daa410fa52c463100f1f8f878c2373a918c55660614ae5c5d51a02770","title":"","text":"On a fresh install, lightdm is writing several files to / These should probably be either in /root or in some other runtime .cache and .gtkrc-2.0 Steps to reproduce the behavior: NixOS with X enabled, using the default lightdm display manager. soon as the display manager starts, files are written to / That my / will stay clean. If I stop display-manager.service, delete the files, then restart it, the files return. Looking in my /etc/passwd, shows that lightdm does have a home directory set at /var/lib/lightdm. But for some reason these files are not being written there as they should be. Please run and paste the result.\nI just realized after I posted this that I used an old iso from 21.11 to install. So I reinstalled with 22.05, and this still happens\nAre you using KDE Plasma? Can you reproduce the issue with SDDM?\nI am using KDE. The issue also happens with SDDM. I went ahead and tested GDM as well (while still using plasma,) and it does not happen.\nI can reproduce. For my case, in I saw one single file with prefix, after some search it is likely cache for kbuildsycoca5 (). I have no idea what that package does so far though.\nAll the files in my / are exactly the files being generated in\nI can reproduce this with Plasma 5/SDDM on nixpkgs-unstable.\nI also observed these files, tracked down the problem and prepared a pull-request that -- hopefully -- fixes the issue: . I came to the conclusion that it is best to entirely remove the code that creates those file. However, I feel a bit unconfident about my solution, so it would be good to have it tested by more users. If you can spare the time, please have a look at my draft pull request, maybe try my solution, and feel free to report back or even drop a review. Thanks a lot!"}
{"_id":"doc-en-nixpkgs-25df34e3989706204b2fc42dce8d7cbd01d89db07bf93b933c022a1b7c4e67e4","title":"","text":"crashes instantly and won't start with the new Darwin stdenv. My is bundled with quite a few Emacs packages, so this may be a bit hard to isolate, but hopefully it's reproducible anyway. Build with recent . This is with . Partial Problem Report included below. I've elided most of it for privacy reasons; let me know if you need more info:\nCan reproduce on current \"master\". \"open \" won't start anything, but I don't get a crash report, nothing appears in ~/Library/Logs/DiagnosticReports/. edit: got my crash report a bit later, it's the same stacktrace as reported\nThe regular works.\nLooks like libdispatch is too old. Working on it now\nI've opened up a draft that I think might fix it: I'm building it now, but if you have a beefy machine it might help to try to build it as well\nI'm afraid that doesn't fix the issue. Here's a gist with the new crash, which looks more or less identical to the one I posted above: I built this with my fork here: I'm trying to confirm that this has been built with the updated . I'm having trouble tracking it down. Can you tell me how to figure it out?\nHere's a simpler repro case. This happens when I try to build using and the melpa Emacs pacakge:\nSo the short term fix is just to use llvm6. At some point, I'll try to dig into what is actually happening, but I suspect something has changed in how llvm handles threads.\nThank you! I’m happy to use a work-around and didn’t expect you to address this complex issue so quickly! I was resigned to using the vanilla emacs for the foreseeable future, so this is a very welcome development.\nI can confirm that this appears to be fixed in my Hydra builds, as well."}
{"_id":"doc-en-nixpkgs-5ee9f21fe7dbe771cd035e28fa6ef74b36a374b34d62a4038def398804ee95af","title":"","text":"Gitlint CLI tool and pre-commit hook plugin to lint commit messages with presets Metadata homepage URL: source URL: license: MIT platforms: linux, unix, darwin (python3)\nThis isn't my library, I simply requested for this package. should i still be included as maintainer?\nAlso, do I make a PR with the code above? Or is there already a PR\nThere is no PR yet. New packages need a maintainer and I don't want to maintain this.\nI'll do it. I'll send in a PR now."}
{"_id":"doc-en-nixpkgs-3d1b6bc44785eb1a6a321a72f32eaf91236b71a7601756754a3bfee6c6a3970b","title":"","text":"chia farmer fails to register with a pool over https. Relevant log contains: Steps to reproduce the behavior: a new-style chia plot with a pool up a farming node Chia should successfully run. If applicable, add screenshots to help explain your problem. Based on , the missing file is . Upstream normally but this appears to fail here. (This is in an LXC container so it's a bit weird) system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-3c417b688c2837dd8b7937f91f728ff570966153df33f5587abb20f4e572d13a","title":"","text":"Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: python311Packages.astropy maintainers cc: Other cc: n/a nixpkgs at commit Contents of : This issue was automatically generated by . that created this issue. Internal tags: -\nLooks like may be the problematic line. Looks like a flaky test, we should prob disable it.\nseems to fix this. If anyone wants to review it you are welcome. I will merge it otherwise myself because CI is green there."}
{"_id":"doc-en-nixpkgs-db60b5f1381b2e325323bc6a3d4ca55763d728fcd9a9150bb22fdd09ac50f15c","title":"","text":"Project description Metadata homepage URL: source URL: license: idk, its not obvious and im not a lawyer platforms: unix/linux?"}
{"_id":"doc-en-nixpkgs-abc4c6d3e134def64323539232fd547ab2227a69c4741ecbe599169d58a87f5e","title":"","text":"Rofi doesn't seem to find the application for VSCode even though the .desktop file seems to be there. It shows the command when running but when running it doesn't seem it show."}
{"_id":"doc-en-nixpkgs-13546cfbd93d56a115ec350e96afd9d0c84db9b847e6b890ec584a3d59a2c881","title":"","text":"Thunderbird fails to compile with \" error: undefined symbol: wlproxymarshal_flags\" when rebuilding system configuration. Steps to reproduce the behavior: updated my system configuration flake inputs () run system rebuild () Thunderbird compiles successfully. Relevant lines from the build log: So it looks like the error has something to do with Wayland support. nixpkgs lock: nix-info:\nPlease, search before opening issues:"}
{"_id":"doc-en-nixpkgs-9ea241eb7629bfb306aee5de3e3ab34f13005986faeaed4bdf961937aeeb8546","title":"","text":"I believe that this prevents the use of other display managers -Don't force it?\nif you enable a another dm you wouldn't get this error i submitted a pr so that this error does not happen when lightdm is disabled but a another dm isn't enabled"}
{"_id":"doc-en-nixpkgs-c47dc1cbcd3e0d0ad436f531478f1236d7dc49a8bdf8c0051d9ba11eab367b34","title":"","text":"A frontend in GTK 4 and Libadwaita for Apx. GUI for tool for (both are already packaged in nixpkgs) Metadata homepage URL: source URL: license: GPL-3.0 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-d778056d9f1efe08da649a8b84637edc29331e5375fe80ebffa692aae58a6207","title":"","text":"Using the NixOS option to specify the configuration, I noticed that if an ampersand () is present, the password field of isn't generated correctly. the option along with the option. The environment file should contain . the field \"password= the content of . The password is decrypted to . The password shuld be decrypted to . The global variable's name shouldn't show. Here are some nix code that is tested to trigger this issue instead. The environment file: Generated in the aforementioned path, note how the field is erroneous. A hack to get around this is to split your password in two halves, and put the & in plain text. . Of course I would still like to see this get fixed :p Thank you for maintaining this module and reading this issue ! Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nIt looks like a missed a metacharacter: I don't know if escaping it as works, or it interacts somehow with other systemd/shell/nix metacharacters. I lost counts of how many level of escaping we are in. I hope to get rid of all of this nonsense with , but next release of wpasupplicant is taking forever.\nDone in The fix should be in NixOS 24.05."}
{"_id":"doc-en-nixpkgs-6243d49522b4f5c2644cc846aaa30f17f3f5464cb1e4cb3b2f6fc4ae1d60b61f","title":"","text":"Currently we build with support for . Sonnet typically looks in for dictionaries That means it won't be able to find any dictionaries and thus spellchecking won't work.\nIs this still a problem? It seems that hunspell paths are not hardcoded in hunspelldict.h anymore: But they are still hardcoded in\nYes, this is still a problem. It seems like we should disable hunspell and use aspell, which is configured correctly in NixOS.\nI marked this as stale due to inactivity. &rarr;\nI marked this with \"good first bug\" because I think we need only to change to depend on , and do some testing.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-a681b572d12515be29815322e1d7e4e730fa01f20309250bf4fd87999970bcfe","title":"","text":"package lists and as dependencies but upstream uses instead. Steps to reproduce the behavior: dependencies of package it to the dependencies listed by upstream and should not be in the dependencies list, but should n/a <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThat's a bot.\nThank you for the quick turnaround!"}
{"_id":"doc-en-nixpkgs-f2a411bca897e2ed4ad24f6257dd5672f1f4ed477e6f5f8d0c4bd38a7ec6d838","title":"","text":"Using AtLauncher to launch Minecraft 1.20.6 crashes immediately: <details<summarylog</summary[13/06/2024 11:48:21 AM] Checking for updated files! [13/06/2024 11:48:24 AM] Preparing for launch! [13/06/2024 11:48:24 AM] Launching pack Minecraft 1.20.6 (Vanilla) for Minecraft 1.20.6 [13/06/2024 11:48:24 AM] Logging into Minecraft! [13/06/2024 11:48:24 AM] Using Java runtime java-runtime-delta (Java 21.0.3) at path USERSDIR/runtimes/minecraft/java-runtime-delta/linux/java-runtime-delta [13/06/2024 11:48:24 AM] Launching Minecraft with the following arguments (user related stuff has been removed): [gamemoderun, USERSDIR/runtimes/minecraft/java-runtime-delta/linux/java-runtime-delta/bin/java, -Xmx4096M, -XX:MetaspaceSize=256M, -Duser.language=en, -Duser.country=US, -, -Dlog4j.configurationFile=USERSDIR/assets/logconfigs/client-, -XX:+UnlockExperimentalVMOptions, -XX:+UseG1GC, -XX:G1NewSizePercent=20, -XX:G1ReservePercent=20, -XX:MaxGCPauseMillis=50, -XX:G1HeapRegionSize=32M, -Xss1M, -, -, -, -, -, -Dminecraft.launcher.version=3.4.36.4, -cp, USERSDIR/libraries/com/github/oshi/oshi-core/6.4.10/oshi-core-, , --username, REDACTED, --version, 1.20.6, --gameDir, USERSDIR/instances/Minecraft1206, --assetsDir, USERSDIR/assets, --assetIndex, 16, --uuid, REDACTED, --accessToken, REDACTED, --userType, msa, --versionType, release, --width=854,"}
{"_id":"doc-en-nixpkgs-7195c3cb919c98f37cdc28f04f7c3d93f0d8c199e714ef6c93a3848e969944cf","title":"","text":"--height=480] [13/06/2024 11:48:27 AM] [Datafixer Bootstrap/INFO] 222 Datafixer optimizations took 173 milliseconds [13/06/2024 11:48:29 AM] [Render thread/INFO] Environment: Environment[, , name=PROD] [13/06/2024 11:48:29 AM] [Render thread/INFO] Setting user: MINECRAFTUSERNAME [13/06/2024 11:48:29 AM] [Render thread/INFO] Backend library: LWJGL version 3.3.3+5 [13/06/2024 11:48:29 AM] ---- Minecraft Crash Report ---- [13/06/2024 11:48:29 AM] // Don't be sad, have a hug! <3 [13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] Time: 2024-06-13 11:48:29 [13/06/2024 11:48:29 AM] Description: Initializing game [13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] Failed to initialize GLFW, errors: GLFW error during init: [0x1000E]Failed to detect any supported platform [13/06/2024 11:48:29 AM] at (SourceFile:78) [13/06/2024 11:48:29 AM] at (SourceFile:846) [13/06/2024 11:48:29 AM] at ffh.<init(SourceFile:509) [13/06/2024 11:48:29 AM] at (SourceFile:223) [13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] A detailed walkthrough of the error,"}
{"_id":"doc-en-nixpkgs-e36d1abeb5fa2b09079ab898a8f2327f19cce290b2039ede1a8620d087af02d5","title":"","text":"its code path and all known details is as follows: [13/06/2024 11:48:29 AM]\n[13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] -- Head -- [13/06/2024 11:48:29 AM] Thread: Render thread [13/06/2024 11:48:29 AM] Stacktrace: [13/06/2024 11:48:29 AM] at (SourceFile:78) [13/06/2024 11:48:29 AM] at (SourceFile:846) [13/06/2024 11:48:29 AM] at ffh.<init(SourceFile:509) [13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] -- Initialization -- [13/06/2024 11:48:29 AM] Details: [13/06/2024 11:48:29 AM] Modules: [13/06/2024 11:48:29 AM] Stacktrace: [13/06/2024 11:48:29 AM] at (SourceFile:223) [13/06/2024 11:48:29 AM] [13/06/2024 11:48:29 AM] -- System Details -- [13/06/2024 11:48:29 AM] Details: [13/06/2024 11:48:29 AM] Minecraft Version: 1.20.6 [13/06/2024 11:48:29 AM] Minecraft Version ID: 1.20.6 [13/06/2024 11:48:29 AM] Operating System: Linux (amd64) version 6.1.92 [13/06/2024 11:48:29 AM] Java Version: 21.0.3, Microsoft [13/06/2024 11:48:29 AM] Java VM Version: OpenJDK 64-Bit Server VM (mixed mode),"}
{"_id":"doc-en-nixpkgs-9097592522930a6109debb6cd5f53677c016f242bf945286983cdc82e113a16b","title":"","text":"Microsoft [13/06/2024 11:48:29 AM] Memory: bytes (468 MiB) / bytes (704 MiB) up to bytes (4096 MiB) [13/06/2024 11:48:29 AM] CPUs: 16 [13/06/2024 11:48:29 AM] Processor Vendor: AuthenticAMD [13/06/2024 11:48:29 AM] Processor Name: AMD Ryzen 7 5800H with Radeon Graphics [13/06/2024 11:48:29 AM] Identifier: AuthenticAMD Family 25 Model 80 Stepping 0 [13/06/2024 11:48:29 AM] Microarchitecture: Zen 3 [13/06/2024 11:48:29 AM] Frequency (GHz): 4.46 [13/06/2024 11:48:29 AM] Number of physical packages: 1 [13/06/2024 11:48:29 AM] Number of physical CPUs: 8 [13/06/2024 11:48:29 AM] Number of logical CPUs: 16 [13/06/2024 11:48:29 AM] Graphics card name: unknown [13/06/2024 11:48:29 AM] Graphics card vendor: unknown [13/06/2024 11:48:29 AM] Graphics card VRAM (MB): 0.00 [13/06/2024 11:48:29 AM] Graphics card deviceId: unknown [13/06/2024 11:48:29 AM] Graphics card versionInfo: version: a1 [13/06/2024 11:48:29 AM] Graphics card name: amdgpudrmfb [13/06/2024 11:48:29 AM] Graphics card vendor: unknown [13/06/2024 11:48:29 AM] Graphics card VRAM (MB): 0.00 [13/06/2024 11:48:29 AM] Graphics card deviceId: unknown [13/06/2024 11:48:29 AM] Graphics card versionInfo: version: c5 [13/06/2024 11:48:29 AM] Virtual memory max (MB): ."}
{"_id":"doc-en-nixpkgs-0e732217ab3f9dbe82eafc8e6e3f21fcce87c3049c218a20ca45935e64258df2","title":"","text":"45 [13/06/2024 11:48:29 AM] Virtual memory used (MB): 9594.43 [13/06/2024 11:48:29 AM] Swap memory total (MB): .00 [13/06/2024 11:48:29 AM] Swap memory used (MB): 0.00 [13/06/2024 11:48:29 AM] JVM Flags: 9 total; -Xmx4096M -XX:MetaspaceSize=256M -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M -Xss1M [13/06/2024 11:48:29 AM] Launched Version: 1.20.6 [13/06/2024 11:48:29 AM] Launcher name: ATLauncher [13/06/2024 11:48:29 AM] Backend library: LWJGL version 3.3.3+5 [13/06/2024 11:48:29 AM] Backend API: Unknown [13/06/2024 11:48:29 AM] Window size: <not initialized[13/06/2024 11:48:29 AM] GL Caps: Using framebuffer using OpenGL 3.2 [13/06/2024 11:48:29 AM] GL debug messages: <disabled[13/06/2024 11:48:29 AM] Using VBOs: Yes [13/06/2024 11:48:29 AM] Is Modded: Probably not. Client jar signature and brand is untouched [13/06/2024 11:48:29 AM] Universe: 404 [13/06/2024 11:48:29 AM] Type: Client () [13/06/2024 11:48:29 AM] Locale: enUS [13/06/2024 11:48:29 AM] CPU: <unknown[13/06/2024 11:48:29 AM] # Game crashed!"}
{"_id":"doc-en-nixpkgs-8418b1de9251316d52758d1fb5f2cd1004ef44a5d80d6259ef309ae89a6ec60b","title":"","text":"Crash report saved to: # USERSDIR/instances/Minecraft1206/crash-reports/crash-2024-06-1311.48.29- [13/06/2024 11:48:29 AM] Oh no. Minecraft crashed. Please check the logs for any errors and provide these logs when asking for support. </detailsSteps to reproduce the behavior: (from nixos-24.05 channel) by adding it to user packages in and then nixos-rebuild. AtLauncher. In \"Create Pack\", select 1.20.6 in the version list, and click \"Create Instance\". it successfully created the instance, in \"Instances\", click \"Play\" under the instance just created. crushes without showing any game interface. The log above appears. Launches the game as expected. Using proprietary NVIDIA driver on X11. OpenGL is enabled in <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThat's weird. I'm not able to reproduce this issue with the same configuration you've mentioned: ATLauncher version Minecraft version Proprietary NVIDIA drivers on X11 As an initial debug attempt, could you run and see if that fixes your issue? If it does, then there's some missing library and I can try to find what that is.\nYes, it runs fine with steam-run.\nGreat, at least we have a temporary solution until I can fix this issue. Thanks for reporting this! I'll get to it as soon as I can.\nI suspect that the latest upstream version may fix this issue. Could you please confirm this by trying out that version?\nNot fixed. Neither 3.4.36.6 nor 3.4.36.8 fixes the issue. I also tried 3.4.36.9, but it's not good either. Launching with is still fine.\nAll right, so it's definitely something missing in the Nix expression. Will look into it."}
{"_id":"doc-en-nixpkgs-b043360c5b45a162c39229135f320666854c7f1d95ff44b3418d25838fb7b679","title":"","text":"I narrowed down the issue to the lib not being able to dynamically load. I it to while having nix-ld enabled as a workaround for myself. Additionally my mouse is always visible in front of the crosshair unless I also add . I have no idea if this issue exists under wayland.\nThanks for helping debug this, The package for ATLauncher has a function parameter called , could you try putting the libraries you mentioned within that? The syntax would look something like: I would try this myself but I can't reproduce the error. ATLauncher wouldn't run under Wayland at all (without ) as with all GUI apps built with Java.\nYep, that works perfectly.\ncould you please confirm that the above fix works for you as well? Meanwhile, I'll open a PR to fix this in the package itself.\nIt works."}
{"_id":"doc-en-nixpkgs-658d6b4c700f79a2ec340115ea9b6f78df44e1c48fb09c6b94613f2c43c87d25","title":"","text":"This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.\nHi Already opened a PR for that ()."}
{"_id":"doc-en-nixpkgs-bff4c00e3ff69cd84990c8d5ad2e3c6efb7d5a7ddf8c2bbe6bd3da6a36dbf7a0","title":"","text":"To prevent issues like , meson setup hook should define install directories just like stdenv and cmake do Unfortunately, simple patch like the following will not work Meson does not like it very much when the directories are not descendants of prefix See also"}
{"_id":"doc-en-nixpkgs-57311ec7a364924ce7d39811f70d477e241f53261408fc924edf94c95561eae2","title":"","text":"Project description Alternate Discord and Fosscord client made to be private, secure, customizable, and Linux friendly. Metadata homepage URL: source URL: license: MIT platforms: x86_64 and aarch64 on linux, darwin, windows\nI had a shot at trying to package this from source, but it seems that for whatever reason, the nixpkgs' Electron crashes with SIGTRAP when trying to run with source. I haven't had much luck using on Electron to find a root cause either. Haven't tried using the AppImage yet, though.\nI don't think the appimage will have much difference, but I've also gotten the same error. There is now a that uses dream2nix to package it properly\nI made a derivation that doesn't use dream2nix, and it's available at if it's of any use. The SIGTRAP issue was just a bad Electron version, from what I could tell. I haven't submitted this to nixpkgs yet purely because I want merged first.\nAh it would make sense for the SIGTRAP to be an electron version issue, I've had it on a few other electron apps too. Your derivation looks pretty good, might try it out. Wonder how long it will take the pr you mentioned to be finished tho\nThe PR has been marked as a blocker for 22.11, so at the very latest, end of November. May be an excessive amount of time to wait, though.\nNow that is mostly done and merged, I've used it to make a nice and simple derivation for it:\nLooks great. Not sure if you're planning on submitting this to nixpkgs, but if you are it might be worth adding arm64 support as well.\nYeah it would be nice to get this to work on aarch64 and/or darwin too, but I don’t have any devices to test it on. Can you help with this? The package might already even work on arm since we're just wrapping nixpkgs electron. I’m also down to put this on nixpkgs, might wanna do a bit more testing and tweaking; if you can see any places for improvement that'd be great!\nis there anything that would stop this package from running on i686?"}
{"_id":"doc-en-nixpkgs-3c73c3d687e5e8b7e8786f9c61ee5ecbfd6cde4afd19085a36338eff657f3b2d","title":"","text":"Steps to reproduce the behavior: also yields the \"got\" hash. The hash was last changed in nixpkgs @\nwe just hit the same issue in Alpine - it looks like the upstream uses format specifiers for that change depending on the state of the repo: (found by [here][1]) in your case it might help to do instead ( provided that doesn't just do on the remote URL, but fetches the repo in some other way ): [1]:\nthanks for the new upstream issue and the infos!"}
{"_id":"doc-en-nixpkgs-bbd0a67a25f0272b3f194b1b0a24f977223aff96f2f7fc62893b92a57fce96ee","title":"","text":"Steps to reproduce the behavior: pyside6 Please run and paste the result. :sweat_smile: I guess it says not found because i have no channels (i use flakes)\nThis same failure is causing syncplay to fail to install on my system.\nyeah thats how i knew lol\nTo confirm, I can reproduce this issue.\nI'm trying to package something which relies on pyside6. Package builds fine on nixos-stable but fails under nixos-unstable due to pyside6 not building."}
{"_id":"doc-en-nixpkgs-e782fa2c5fe2c1c4b9bc043ea34653d6500cbb89965b00e2699ae0c0bb734fb5","title":"","text":"Package name: picom-next Latest released version: regrettably, v10.2 (released December 2022) is still the latest upstream release <!-- Search your package here: --- Current version on the unstable channel: unstable-2023-01-29 Current version on the stable/release channel: unstable-2023-01-29 <!-- 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! --- There's at least one bugfix since the start of the year that would be nice to have: 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.\nCan you help reviewing it?\nApologies for not testing this for you, I couldn't immediately work out how to do so. I've now opened to hopefully make it a little easier next time."}
{"_id":"doc-en-nixpkgs-c17373f09683279a03304fbe15b25ae366d41fdd3f7765eb6526b29215ac0510","title":"","text":"Octoprint can't build on unstable due to a conflict of the required version for . octoprint , while the dependency requires (due to ) . Octoprint builds successfully I ran a between and (known good) , the first bad commit was I suspect that it's necessary to pin the additional dependencies (and maybe some more), too, but I'm not that experienced with packaging python packages. made the first bad commit Octoprint maintainers: system: host os: multi-user?: sandbox: version: channels(root): channels(richard): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-238f47a2c9268e034f0fa450629b2d4f9507689d3420a46db7693b971405a84d","title":"","text":"Geary and are . I suppose updating might remove its dependency on the insecure . (I think i remember having seen somewhere in an issue tracker that this dependency was removed in Geary source code, but i cannot find now where i saw it.)\nBy the way, I do not really understand these GTK and WebKitGTK issues and versions, but, just for reference, there is an open issue about previous versions of Geary using GTK2 instead of GTK3: .\nIn Geary 0.12 there are some fresh bugs (for example, ). It looks like version 0.12.1 is in the beginning of November.\nRunning shows gtk2 as a transitive dependency from webkitgtk (which depends on both GTK 2 and GTK 3) and gnome-themes-standard. I do not think the latter is necessary for GTK 3 applications since Adwaita is built into GTK 3."}
{"_id":"doc-en-nixpkgs-423a22242b1698b03ffce3dd8898d380abf8b24308fb9282200471619e2ed463","title":"","text":"cliphist wayland clipboard manager Metadata homepage URL: source URL: license: gplv3+ platforms: linux"}
{"_id":"doc-en-nixpkgs-4aeed9179222b372673755d35a25b3e27a19fcb59f06048305f8850fa6a86a74","title":"","text":"Describe the bug fails to compile with Additional context See for a possible cause. Notify maintainers cc (sorry for notifying you here and in the PR!)\nGonna try to just switch it to . We should probably update gnome docs for Rust+Gnome packages\nYeah, I think that would be best. The idea of the hooks is that is not necessary anymore in mixed projects. I will also do a PR for cargoBuildHook, since it should not be used when is set explicitly."}
{"_id":"doc-en-nixpkgs-edcd0f50c03ab3337ffbc029daa7e11cc68bd7fcbd1d59d3396f9c4c0023e7de","title":"","text":"Describe the bug neovim fails to build with missing , similar to , on . To Reproduce Steps to reproduce the behavior: to from master () Expected behavior The package should successfully build. Metadata On master () Maintainer information:\nvia in\nso you could do until a proper fix.\nReverting the luarocks bump doesn't work for me. That fix is also very surprising to me, since neovim broke (for me) after the latest nixos-unstable channel update.\nInteresting. It worked fine for me. Running the above revert command and then (inside my local nixpkgs with it reverted) let me build neovim properly. I don't think it's particularly surprising if updating a channel that happens to include the luarocks bump causes it to break, unless I'm misunderstanding you.\nI updated from a channel where the luarocks bump had already happened, and neovim worked on that channel. In fact, I reverted to the previous hydra evaluation to make my system evaluate again.\nThis was actually before and it was working without problems and then suddenly the problem appeared again. I can also report that I cam getting this in the same way described (updated latest nixos-unstable channel and then neovim stopped building again).\nI confirm this fixed by on master (channels may take a while). For now I'll assume that charvp's failure to resolve the issue with that revert was some kind of mistake; we can re-open otherwise, perhaps separately if it's a different kind of error.\nDoes anyone know why updating the luarocks dependency is so brittle? Is it possible to at least add a test so we don't regress again in the future?\nthe tool exists (nixpkgs-review) but it takes CPU and disk space to run plus some reviewer time (and was not run in this case). Also for this specific case, the luarocks update broke in subtle ways the build so I wouldn't call it . It is called unstable for a reason. The good thing about nixpkgs is you can pin neovim to an older version while keeping your system on unstable.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nAre we sure this is fixed on Darwin? still shows failing with logs of: Or is this a different issue?"}
{"_id":"doc-en-nixpkgs-e09767df0580761637b592fb601d32b1e74bbbe6be5426b230a286e2e7d01bcf","title":"","text":"I think the root problem here is that luarocks has a poor implementation of \"move\". Combined with the build's behavior being affected by filesystem ordering the result is essentially random. The [implementation of move][] calls out to the operating system commands [][] and [][]. Building with will contain a sequence of , and . I've extracted the [relevant part of the log][]. The critical aspect here is that by default, unix will dereference symlinks and copy their contents. [implementation of move]: []: []: [relevant part of the log]: My theory: luarocks scans the directory for external libraries in filesystem order and attempts to move all shared libraries from to . At which point one of 3! things will happen, but the two main ones are: is copied and deleted and , now broken symlinks, fail to copy and are copied by dereferencing, and deleted is copied and deleted Either way is wrong to some degree, but one of them happens to work well enough for downstream packages to build. If I build locally, the filesystem order I get seems to work, so we can inspect the two results: I've been focusing on this for darwin since the failure case happens to be cached, but I believe it applies equally to linux.\nis that sthg you have already witnessed ?\nWhat LuaRocks version is this happening with? I have pushed fixes related to the file deployment stage in 3.3.1.\nI've tested 3.2.1 (current nixpkgs master) and 3.3.1 (hasty upgrade locally), they both have similar results, except on 3.3.1 the errors now propagate correctly. I've uploaded a [log of a failed build][] with 3.3.1. [log of a failed build]:\nI was hoping to find time to write a proper issue report and a test lua package for this, but haven't yet. My test case would have a directory structure made with , that looks like: In order to succeed the deployment stage would have to produce both the file and its symlink."}
{"_id":"doc-en-nixpkgs-1e4fcf1fb0aeb4c16221f034e0c294114b7fe3907c35f8218554cbb7771d9345","title":"","text":"Describe the bug I have neovim in my systemPackages, I did and today and it stuck at building luajit: To Reproduce Steps to reproduce the behavior: to Expected behavior The system should upgrade properly. Additional context Output: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kj): nixpkgs: Maintainer information:\nPossible fix is in . There was already an open issue about it () but from an unclear reason people have reached the conclusion it was fixed on latest master.\nOh I meant , not .\nWell, I agree with that conclusion. For me, on the build is broken with the error above and on current master it isn't. EDIT: note that the channels lag behind, usually less than a couple days, but sometimes we get a week or two due to some harder regression.\nYea right. For me on NixOS I tried with the nixpkgs-unstable channel and could install successfully. The nixos-unstable still fails though."}
{"_id":"doc-en-nixpkgs-7d244a5b086d551a2dd912c355617c1536b0726d4be696b02774154d0857beb6","title":"","text":"When using to create and activate a swapfile on btrfs, it fails with messages like this: The kernel says: I am not very familiar with Nix, but after reading the corresponding and , it seems that creating a swapfile on btrfs requires disabling copy-on-write for that file (via ) as well. However, doesn't do it currently. BTW, manually creating the swapfile and letting NixOS activating it works fine for me. to ( is supposed to be mounted as btrfs). . Swapfile is created and activated without any issue. There is a workaround on NixOS Discourse: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nI have the same issue. I already tried disabling copy-on-write for the partition but it still fails: I also still get the warning like even though I the attribute to my mount options (afterwards). My current swap configuration can be found .\nMounting with attribute won't work because: [^1]:\nI came up with this yesterday, which seems to work (or at least you can follow the general pattern): I have as a separate subvolume, nothing else on it. Once you've run this to create the swapfile, it seems to mount and function properly from there on out. But yes, it would be nice if this were taken care of automatically. EDIT: Fix link\nbrilliant, that helped me solve my issue. While your script didn't work out for me, I was able to adjust it so it did. I noticed the following warning when running your script: So, I searched for this and found the following note on ArchWiki: — Replacing with made the warning disappear for me but running still failed with . Then I compared the script to what I've used in and noticed that I used instead of to create the empty swapfile. The full script I ended up with:\nThanks for the update. I originally used , but switched after reading that should be much faster (and have to admit I can't remember if I tested that change yet -- thank you for the feedback). I've switched it back to ."}
{"_id":"doc-en-nixpkgs-4358b0559f17b8c7d7c8b3c6aec9ea97b48ed026c45cde0df4bc7b037c9c52bf","title":"","text":"Steps to reproduce the behavior: Checking waybar's , it appears that fixing this would just be a case of passing in . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nIt appears that a similar issue also arises with ."}
{"_id":"doc-en-nixpkgs-dfe044077b19d0d86b1b6b49a167f48d869c604e784643d95cba8eb3a6b0ba3c","title":"","text":"After installing the hack font it can not be found. Probably because it's installed in the wrong folder. Steps to reproduce the behavior: font-hack up Gnome Font application for the font hack and see it's not there and see it's in a separate directory next to Font should show up in Gnome Font and other applications Running nixos 23.05 beta\nFor me it seems to work when adding:\nYeah, rearranges font files anyway. But it seems like a good idea to unify the output directory with other fonts, thanks for catching this!"}
{"_id":"doc-en-nixpkgs-420f7ff22085cd5f3d2835cacfdd9aa6c6ffda67c99e2795ccb6ecc3c921e9d6","title":"","text":"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."}
{"_id":"doc-en-nixpkgs-a3c2232c6f9456ff4750772457c63e12cab2cc03cf9ec86a8b132fb1c90371b0","title":"","text":"<!-- 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 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: roon-server <!-- The current version can be found easily with the same process than 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: 1.8-850 desired version: 1.8-880 <!-- 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."}
{"_id":"doc-en-nixpkgs-1b9a61ba0b5bf4a461a082a41a25b60e5fab5d2ace02e714a46f51ab225c4e99","title":"","text":"When trying to load a multi-binary, a GLib error occurs on the terminal, and liberation-circuit crashes. In fact, this appears when interacting with anything using files: Saving a code, loading a code, and saving a multi-binary. This causes the player to have no way to program his processes. Steps to reproduce the behavior: multi-binary A window should appear to select a file This is the error appearing in the terminal : Please run and paste the result."}
{"_id":"doc-en-nixpkgs-f8be2163cc5cf38b9a84c87484339374029fc81dedb2129c655bba264d0f03e6","title":"","text":"Steps to reproduce the behavior: -shell -p redisinsight Multiple of these errors Full log - Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-582f97b476ad8947a85ba29e365b88ab6e6ff8187ba137872d62552ae77f4e37","title":"","text":"Project description cchat-gtk appears to be a generic chat frontend cchat-discord appears to be a discord-capable backend gtkcord3 was the predecessor and was quite nice, I'm excited to get this packaged. Metadata homepage URL: source URL: license: gpl3 platforms: linux\nupdated OP to reflect that we should package cchat-gtk/cchat-discord now instead of gtkcord3.\nI marked this as stale due to inactivity. &rarr;\nstill important to me\nI have this packaged in my own config:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-81602087967891733df8c30103d558ea0c7d13ac563494c96161099ed737cc7d","title":"","text":"and other operations fail with See upstream bug report Steps to reproduce the behavior: arion on a basic , e.g. Arion is operations complete succesfully - you seem to think this is a docker compose issue, should those maintainers be pinged? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nweird, the fix to seemed not to fix this one for me yet"}
{"_id":"doc-en-nixpkgs-70de878a69963fd650a7b36ad4e5d078d04724de99af3553252b8a3a6b3217f6","title":"","text":"introduced a deprecation warning for the option. Upon following the warning and moving all options out of the option and removing it, the build fails with the following error: Steps to reproduce the behavior: the service without using the option the configuration Build succeeds. As a temporary workaround, I tried setting to an empty set but then borgmatic fails to parse the config file. <!-- 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."}
{"_id":"doc-en-nixpkgs-a731bdf1a4b4274f9506768062134595e763d6d64a3e8fee5a1a14e41d653e73","title":"","text":"Describe the bug To Reproduce Steps to reproduce the behavior: ~/nixpkgs -build -A tilix <details<summarylog</summary</detailsExpected behavior Screenshots Additional context Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nbuild tilix\nI guess that only works for PR. Sorry.\nThis looks like an issue with the package.\nThis probably needs patching\nMy mistake, the same error occurs in multiple tests, so fixing a single test won't do.\ngrepping for points to the DMD linker: It looks like the DMD linker invokes gcc with to do the actual work. Considering that the package hasn't been updated since April, perhaps some change in the gcc toolchain caused this build failure?\nPinging maintainers\noutput of <details\nThanks everyone"}
{"_id":"doc-en-nixpkgs-a0820a529549a8533a5ea93e225be93095337a3baa76db2bc5f61201f5feedd2","title":"","text":"Describe the bug I have a ZFS pool with approximately the following layout: The datasets under are those that the local system is installed on and the datasets under are backups from a different machine received via . All datasets are using native ZFS encryption, however, datasets under are encrypted with a different key (that of the machine that sent the backups) than the rest of the pool. When I boot, the initrd will query me for the key for and but this key is not available and I also don't want to make it available for obvious reasons. The culprit lies in this statement in the : This forces loading of all keys, which is a good default, but cannot easily be overridden. My current workaround for this is to turn this off and only load the key for manually. To this end I would like to propose the following patch by which it should be possible to load the key only for the specified datasets. To Reproduce Steps to reproduce the behavior: NixOS with an encrypted ZFS pool a dataset with a different encryption key and set you lost the key for this new dataset errors when mounting due to the lack of keys Expected behavior It should be possible to restrict for which pools and datasets to query encryption credentials. Screenshots N/A Additional context N/A Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:\nI think you can open a PR with your patch for this one."}
{"_id":"doc-en-nixpkgs-783ea8a796fb0bc1a6261d06cb56934a08ce6d8afc2ffe41e49009084ca41021","title":"","text":"Steps to reproduce the behavior: The regression is directly caused by , and the root cause is the library is not properly linked, upstream issue: <!-- 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."}
{"_id":"doc-en-nixpkgs-85b5fa89ed5b28bcc92c1eee54156df3d4847310ce701e009ecace8b24d57472","title":"","text":"Describe the bug Most of my programs is unable resolve DNS after I updated my system to (from the last time nixos-ustables was updated which is approximately 14 days ago). This includes curl, chrome, resolvectl and nix which basically makes my system unusable. One really weird exception is the tool which is actually able to query both a remote server (such as 8.8.8.8) and the local systemd-resolved server to resolve DNS (which indicates that this is probably not the fault of systemd). There's also a error message in systemd-resolved's that said \"Failed to escape hostname: Invalid argument\". I also tried to edit my file to change the nameserver to 8.8.8.8 and that didn't change anything. here are some examples of the errors returned by those programs: To Reproduce I don't really know how to reproduct this issue Expected behavior DNS should be working properley on all programs Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. Maintainer information:\nPrograms which are broken are using the libc calls to resolve the hostname, looks like the nss module from systemd-resolved can't resolve the hostname either. This looks to be some kind of failure within systemd-resolved, since systemd-resolve on the CLI fails with . We should also open an upstream bug unless we find some evidence that this is caused by NixOS.\nThis bug affects me too. Same error and same logs.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nSame bug on my end.\nI think I figured out what's the problem here. I opened an upstream issue: Can you try if the following patch works around the issue?\nthat worked! (though I have to manually edit the service file since automatic GC kicked in and I cannot rebuild my system:facepalm:) Also, I feel like there should be a basic network connectivity test to prevent bugs like this from being merged into the unstable channel.\nAnd thanks for the quick action ! I agree, but I thought we actually have them for unstable?"}
{"_id":"doc-en-nixpkgs-b677dc70d0839b3ff23c411d8c801e1b18099707d4310a54fae8423a3250712a","title":"","text":"I've the following to my : and I can confirm systemd-resolved works again. Now, how do you get to rebuild your system if like you don't have a working system to rollback to? I did (as root): to force using that file in order to be able to run .\naw man I did not know that if you stop systemd-resolved it will resolve normally. I removed the symlink and created a new directory there, copied everything from to there, manually edited systemd-resolved.service, and ran and after that restarted systemd-resolved. method is definitely more superior.\nSo... for now we push this workaround to nixpkgs master?\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI'd say yes. Especially if there's no quick upstream fix in perspective. Hopefully this problem only affects users following unstable.\nStable doesn't get systemd updates, so it shouldn't be affected (based on flokli's analysis).\nPR at"}
{"_id":"doc-en-nixpkgs-2b2e1be73da8feaa3e85f4c78ac84d1f09932c4749a5e1be208c47fee34a80cc","title":"","text":"On Darwin the wrapper adds a number of unused arguments that are passed along to . displays a warning for each of these arguments: This makes the build log of some packages extremely large, and in turn it can cause because of the log size limit is exceeded. /cc system: host os: multi-user?: sandbox: version: channels(smaret): nixpkgs:\nI think that fortran on darwin is a rather under-maintained combination in nixpkgs ATM.\nfor packages that use and on Darwin: Could this be implemented in the wrapper itself rather than in each package that uses the wrapper?\nThis needs to be propagated to everything that uses gfortran? I think using for gfortran packages might be a better in that case, it's less likely to cause other problems.\nI think auto-passing such an option is slightly risky over the long term, as it may hide other errors, e.g. user typos. (No strong opinion.) I wonder if using gfortran with clang is actually a \"supported\" combination upstream; I guess might be better, as you write."}
{"_id":"doc-en-nixpkgs-cfb7c298c846490320c53f6645ba9033c410a8f86184c6f69625da55cb48ac93","title":"","text":"Project description Native Linux desktop client for accessing your Proton Pass vault. Metadata homepage URL: source URL: license: n/a platforms: Linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI see repos for iOS, Android and Web builds, but not for the Windows/macOS/Linux ones. Are you sure these are actually open-source? Building from the provided .deb is an option but is discouraged if building from source is viable\nthe source code for the Proton Pass linux client is here:\nActually the have a global lockfile for the entire monorepo\nUnfortunately, building from source doesn't seem like a viable option right now — the Yarn infrastructure in Nixpkgs currently is very shoddy and frankly, nobody knows Yarn well enough to make it work reliably. Upstream uses both a monorepo structure and v2 lockfiles, neither of which are really natively supported in Nixpkgs right now (see ). Unpacking the upstream .deb file seems like the only way forward EDIT: Unpacking the .deb was just... so much easier. Making a PR now"}
{"_id":"doc-en-nixpkgs-ec834c874c64c9410baac82b957d97398717ee0026133b0cdfd52b5a1a3f137a","title":"","text":"Build of failed on x86_64-linux as of . This is currently breaking . python3Packages.pytorch maintainers cc: python310Packages.tensorboard maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: -\nRelated:"}
{"_id":"doc-en-nixpkgs-ab0951e8cbc51f3685e46b30824e4652a7d73fa04cf39c3a24e695c8ef7281fe","title":"","text":"Unable to use Podman's quadlets feature for a user, since the service unit files are not generated by systemd. Steps to reproduce the behavior: a quadlet file in (say, ) . Systemd says that no unit files were found. Caddy service should have been generated and its status displayed. This issue is caused by not symlinking the provided by the package to . Does not occur at the system level, since is already symlinked to Fix: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nConfirmed the quadlet systemd user generator is not found in /etc/systemd. I'm gonna take this one and try to come up with a fix in NixOS module."}
{"_id":"doc-en-nixpkgs-29bcd12634a6f4b63574cfd389e304a1525b29403d582f581a092ceb9a155ddf","title":"","text":"Describe the bug Tribler does not have any desktop icons, and does not show up in any menus. There is a desktop file in But it's not being included by the desktop environment. Maintainer information:"}
{"_id":"doc-en-nixpkgs-9749fce4e3cd607af09373e6de71562f80341e9d3ef07d5d9d6e081d468f13a7","title":"","text":"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."}
{"_id":"doc-en-nixpkgs-91efa0360c80bea4eb431561456771ab77480a4ea75f62dc44a4f2d807e752ac","title":"","text":"Steps to reproduce the behavior: to build (required by ) fail Full trace (libxml2): Doesn't happen on , before I have no idea if this happens on any other platforms, needs triage. I also have no idea why python for linux needs something darwin?!? This also breaks the evaluation of , but not Python team <!-- You know a bunch about splicing --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8d38e2fd0acd1cef6d146a58d05016fb1d58493c924e1f72821afd80051e4970","title":"","text":"I don't know much more than this: and but I don't know how to fix this.\nI was bit by this as well. It fails on other key for me -- looks like it would fail on any.\nHow did you solve this issue?\nCan someone tell me where this \"keydir\" should be located? I cannot find it in my !\nThe keydir should be in your gitolite datadir, which is /var/lib/gitolite in the default settings.\nOkay. My shows:\noh it should be in \"/var/lib/gitolite/.gitolite/keydir\", my bad.\nOkay, everything is there. How to check why it fails?\nIt failed for me for every key on v3.6.2. So, besides upgrading gitolite to v3.6.3, there is not really much you can do.\nUpdate solved the issue."}
{"_id":"doc-en-nixpkgs-9857396b27856000ce36d10cfafe61e5c6fe2bf9bbfd96b34dd6e3b10b2c7018","title":"","text":"Update certbot Current packaged version is 0.39.0, upstream version is 1.2.0.\nFix in"}
{"_id":"doc-en-nixpkgs-ff56b294a4f9e759c8c75e3caf7bd2b2827189a317fbf6779049228048ff592a","title":"","text":"Package name: git-open Latest released version: 3.0.0 <!-- Search your package here: --- Current version on the unstable channel: 2.1.0 Current version on the stable/release channel: 2.1.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package.-- Note for maintainers: Please tag this issue in your PR.\nThe latest version of listed on the project's is (Dec 3, 2018), however was released on the project's (Jul 18, 2022)."}
{"_id":"doc-en-nixpkgs-93fb3fb51b0d59bf5896b5450edcec65c55e4ce651a3053dd582f8daea58c911","title":"","text":"Project description A cross-platform TUI database management tool written in Rust Metadata homepage URL: source URL: license: mit platforms: unix"}
{"_id":"doc-en-nixpkgs-44f7f38a585567b1b208256d34e867937d34ed0a4f72414cf07cf89e337982cd","title":"","text":"Several windows of nemo closing together when sending killactive (note that this is not real kill) and a coredump can be found in systemd journal. Steps to reproduce the behavior: several instances of nemo from a wlroots based compositor e.g. sway or hyprland. hotkeys attached to killactive on one window. systemd-coredump message from journal (I use gnome-logs for convenience). The nemo window should exits one per time, not closing together, and not coredump as well. windows do share one process id, but this seems to be not the case as . (however, this may be misleading as someone mentioned that steam also exits its background process when using killactive) issue didn't exist on Arch Linux. Just to mention that there may be something we should patch. is the content of coredump: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nReported from Fedora with nemo 5.6.2, also hyprland, works fine.\nMore related behavior (I'll call nemo windows in time order as nemo1 nemo2 etc): I launch nemo1 and nemo2 in a short interval, they won't close together when I close one. I launch nemo1 and wait for about 10 seconds, then launch nemo2, then close nemo1, they are possible to crash. However, closing nemo2 immediately won't, if wait for another 10 seconds, both crashes when closing nemo1 or nemo2. I launch nemo1, nemo2 and nemo3 in a short interval, then close nemo1, they all will crash. Again, nemo windows share one pid. So the crash will close all windows. This was , but I'm afraid they can't reproduce the bug anymore. Also since other distros can't reproduce this bug, I'd rather believe it's specific to nixos, and maybe because of the wrapper."}
{"_id":"doc-en-nixpkgs-d93d611e1a9ff3ee387e3a19f502055592997bc689e80940efeaf96e1904f2fc","title":"","text":"I was not able to properly test this right now (sorry :bowingwoman:), but here are some random things you can try: See if you can reproduce this with nautilus, thunar, also some old version of nemo, some old nixpkgs checkouts, ... If you find it previously working, a bisect point will be appreciated. Install debug symbols and reproduce the crash, not tested but should be something like: Then get list of crashes with , run and enter . Based on the above step, try to patch away (remove) some of the lines in  according to your stack trace and try reproduce the issue, you can also e.g. try swapping the order they distroy widgets to see if it matters. Sorry I have no idea how killactive \"closes\" a window, is that the only way to trigger the crash? Did you spot the crash when closing nemo normally, i.e. clicking (File) - (Close All Windows) and/or (File) - (Close)?\nSorry I haven't got time to debug it, but I've tested with \"close all windows\" or \"close\" several times, they didn't crash and \"close\" works correctly. Thunar don't (since it doesn't share the same pid across windows?), and nautilus refuses to open a second window when one exists.\nOkay here is the coredump:\nWeird, did you trigger the crash after rebuilding nemo? :thinking:\nYes, by the same killactive sended by hyprland\nin my nixos configuration, and installed with home manager (home manager as a module of nixos). This rebuilds nemo (I saw it) when applying config.\nCan you try adding to () instead?\nOkay it seem to work, and now I get this:\nPretty fun though, it happens even without triggering the 'search window'. I just open and close the nemo, and do nothing else.\nMake sense to me! If I hit the search button to trigger the search widget, then close it, it won't crash (tested 10 times). So the problem is trying to destroy a widget that doesn't exist."}
{"_id":"doc-en-nixpkgs-f057f1877c5c446f03b4bd8060288ea2fac8629b5cc583471c1dfe6c5eb40cb0","title":"","text":"However, there is another question: fedora and archlinux with the exact nemo 5.6.3, hyprland latest, xdg-desktop-portal-hyprland, doesn't, and the code makes sense. So what is happening to nixos?\nUnsure of memory leaks, but anyway it works. This seems like a upstream bug and caused by gtk or glib version compatibility. Will close it for now.\nHmmm, please consider reporting this to linuxmint. I checked nautilus and they after so we are on our own. I actually wonder whether a check is needed But it is unclear to me why the null check is not enough :upsidedown_face:\nTested, this is not enough however.\nDid this ever get fixed? I seem to be having this same issue still with version 6.0.2\nI totally forgot that. I'm using my patches for more than one year. This is also useful for Would be better to report it upstream, though.\nThanks for the info. This does in fact fix it. It's worth noting for anyone who might travel this path in the future - the patch has to be applied to , even if using . Totally didn't spend 45 minutes trying to figure out why it wasn't working just to figure that out\nPlease try .\nseems to work?"}
{"_id":"doc-en-nixpkgs-43062a6871d4493419803a94e60ef2174c65a1dbcd5024a75714082a44bed4b8","title":"","text":"Project description ClickUp is a project management solution, similar to Trello Metadata homepage URL: source URL: N/A license: unfree platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSeems like it's needs to be archived with (currently it's down). Download URL is:\nI also found this PR, but it has been a year\nYeah I did give packaging it a shot but I could not find a reliable way to get it downloaded because there doesn't seem to be an exposed way to get a specific version?\nYeah, I also checked PR URL, and it doesn't seem to give reliable version package. Even AUR has some problems. That's why I suggested"}
{"_id":"doc-en-nixpkgs-6ade04beaa4b0d9b084d60474f49455924d77fc3c8f7d6a966a597a1ced917ea","title":"","text":"When you try to connect to the Tor network using the Tor browser you get the error message ! When you try to visit a website after being shown the big red error message your get the error message ! This problem appeared between one and two weeks ago. ; can't find an existing Nixpkgs issue. Steps to reproduce the behavior: the Tor browser from Nixpkgs the Tor browser on error message to go to a website When clicking on the browser should connect to the Tor network and be able to browse. The . browsers says that it can detect my internet connection. ! Tor logs doesn't seem to indicate any problems (from what I can interpret) I live in Sweden and this issue has appeared both when I've connected to the internet using my home connection (Sunet) and when I've connected over a VPN. I.e. no fuckery by an oppressive government. The timeline match up-ish with when would have become available in the binary caches. Unsure if the error appeared before or after updating around that time. After checking the original PR I see that this problem was noticed, but a workaround was applied. Doesn't seem to work for me :-/ The value is for me. I'm using root on tmpfs, and nothing under is persistently saved between boots. ! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- and because you seem to have actually researched the problem. The system is fully up-to-date as of 2023-03-05 22:15 CEST.\nThe red error message indicates that Tor cannot find the tor socket. Everything else is bound to not work unless it goes over the normal internet. Please see and for the underlying problem and please check if the firefox setting points to the right socket file.\nI tested to set to , but that didn't help.\nSetting to also doesn't work.\nJust to avoid ambiguities, did you set to (with file name part)? TBB is still working fine for me with the workaround. Likewise for me, is a tmpfs. Have you modified (and forgotten about it) your torrc, e.g. to use a different control port/mechanism? What is your XDGSESSIONTYPE?"}
{"_id":"doc-en-nixpkgs-2e15c347ff7eea00debe4fb34d1dc4107dff5d48fe9b416d45375b96cf9617d1","title":"","text":"The person on uses wayland (with sway). I currently still use x11 (with i3) and haven't tested it with wayland.\nThat did it! I missed that you should specify the file in the path. I'm using AwesomeWM.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nThe person on had the same problem and the same solution :-)\nWhy did you close this issue You can't seriously think that this temporary workaround is an acceptable permanent solution to this problem? While we still don't have a permanent solution, it should be as easy as possible for users to find information about this workaround. By closing this issue we signal to people that this problem has been solved. And people currently experiencing this problem on a fully up-to-date system will probably not think about looking into closed issues, because the issue is still there.\nI am also experiencing this issue. The fix worked for me.\nConfirmed. The issue is still present. Default installed value of is 127.0.0.1. Changing it to resolves the problem.\nThis issue only started happening on my machine after deleting today.\nStill an issue. I'm using TBB with firejail and I have to apply the workaround at every restart. TBB creates the folder but not a profile inside (this wouldn't be a problem for me if connection works out of the box). about:config - = tor-browser-bundle-bin 12.0.5 firejail-0.9.72 nixos-unstable\nBy default, the service runs on port 9050 and the control port on 9051. This is configured in the torrc file: Your firewall may be blocking some of these ports bound by default to localhost which normally point to 127.0.0.1\nThe PR for Tor Browser 13 removes the current workaround again, because it seems the issue was fixed upstream: I would be grateful if some of you could give this a try and report if it's still working (or working again)."}
{"_id":"doc-en-nixpkgs-59c17214a78261982dd66ba7e013c66486bf2b71bc6bc9afbb98a4c9dd52a4f4","title":"","text":"<!-- 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: <!-- 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: 1.3.0 desired version: 1.3.3 <!-- 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."}
{"_id":"doc-en-nixpkgs-f3dc10cc9a789ea592fad75889f0b375b5153fee9af30318746b7fe0ca669e39","title":"","text":"Describe the bug Using commit . See build output . Gimp builds fine.\nI knew I was forgetting something. This is likely fallout from I was partially fixing it in : but a more proper fix is necessary."}
{"_id":"doc-en-nixpkgs-9de472daeb6f0878d581fcfb980d70eb2dd6c51ac64d54e2d93d05ee50bca77d","title":"","text":"Project description is a library that provides strong cryptographic hashes for password hashing, such as bcrypt and yescrypt, as well as a number of legacy ones for backward compatibility (e.g. sha256). It is API- and ABI-compatible with provided by glibc. glibc intends to drop the library eventually: This is a first step towards transitioning whole nixpkgs from libcrypt bundled in glibc, as described here: Metadata homepage URL: source URL: license: lgpl2.1+ platforms: unix"}
{"_id":"doc-en-nixpkgs-09f14b90f461826d56cab258dce734c8e609e9db9a8c1913ec696a7cc53d0d40","title":"","text":"Describe the bug Since upgrading v8 to 8.4 () it no longer builds on darwin (at least on my 11.2.3 machine) To Reproduce Steps to reproduce the behavior: Expected behavior A successful v8 build Additional context By default it fails when trying to find the macos sdk, which I patched around with: This then gets as far as , which is avoidable with: which then produces ... and I had to admit defeat. Notify maintainers Metadata Maintainer information:\nHi! Thanks for reporting this! I've opened which I hope fixes this - at least it builds fine for me on 10.15. Please give it a try on your machine too.\nYep, looks good!"}
{"_id":"doc-en-nixpkgs-02a961e7d214689e3ed57b2a06b3f911eafb8e9f783e3f0b7460a20a237d61ae","title":"","text":"QEMU VMs using the profile that have a in their hostname were broken by A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result."}
{"_id":"doc-en-nixpkgs-6efbac3fd0923e08da6ac9ee93db879b76a819034a44be5869b98c9992f5485d","title":"","text":"Describe the bug wendy, one of the big-parallel build hosts used by , cannot successfully build This blocks advancing nixos-unstable. To Reproduce Steps to reproduce the behavior: wendy to build Observe :( or, more realistically: the attached CMOV16rm-, and run (a reduced commandline that produces the same assertion failure is ) Expected behavior A clear and concise description of what you expected to happen. Additional context The assertion that's tripped by this YAML file is: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:\nis the CMOV16rm- (can't upload it here because it's not a supported GitHub filetype, apparently). To be more precise, the test that is failing is this one:\nThis has primarily become apparent because the configuration was changed in NixOS/nixos-org-configurations to make wendy only build big-parallel jobs. Since llvm is big-parallel, this means that wendy will now usually get selected for building llvm, since the load is otherwise pretty low. Previous successful builds of have been using one of the packet builders instead, which are using a newer CPU for which LLVM has a scheduling machine model.\nFWIW, this probably affects other LLVM versions as well, but they have current versions in the cache. If wendy rebuilds the other packages (e.g. stdenv bump or something), they'll likely start failing as well.\nIf you spin up a VM using the CPU profile that at least virt-manager calls \"OpteronG1\", then you can reproduce this using the LLVM tests. That's not quite the same as the CPU reported on wendy (OpteronG1: k8-sse3; wendy: amdfam10), but it exhibits the same problem.\nI don't know why, but wendy as disabled now.\nit's probably late for you (I hope I didn't confuse names), but you this issue some time ago.\nuh, same full name but this GitHub name is in .\nFiled upstream for this."}
{"_id":"doc-en-nixpkgs-f746fd38e388c865a78f38a4405e1101f94cc9e3a5ef05f425c9b3564c68f88d","title":"","text":"Regenerating the package set takes several hours so let's be quick when merging those to avoid rebasing. having a label autoassigned for the node updates would be nice."}
{"_id":"doc-en-nixpkgs-5b01d54988b3a4e4268b86a3f69463a6d9fb4a391535f5d9139342e2cbffcf45","title":"","text":"Describe the bug Roundcube just responds with the following message: Same thing in the systemd logs: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Maintainer information:\nwas just updated to in . That might be the issue. Override the package with maybe?\nThat was the problem, thank you! PR here:"}
{"_id":"doc-en-nixpkgs-a60b5b0eb6578de2ed9add4e839b8cda3b596595fa9fc4b2968d47c1aa02cbb4","title":"","text":"Steps to reproduce the behavior: I updated nixpkgs and now nixops does not work anymore. I don't even use gce, so I'm baffled why it's failing. was still working. In both cases I used the same nixops version 1.7. My config did not change and can be found at <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nIn the future, please ping the maintainers as instructed in the template. cc\nThanks for doing that, I didn't know who to ping\nloaOf was removed in after many years of being deprecated nixops at 1.7 still had loaOf being used as it was released(2019) before the type was deprecated also cc\nI've switched to morph in the meantime. I keep this issue open for if someone wants to fix it.\nNot everyone may be able to switch away easily. Simple nixops deployment without cloud resources and static hosts may be easy, but that's not all deployments. Reverting in"}
{"_id":"doc-en-nixpkgs-b40a7d0ae210dcb7b994becff8eb7704c06ec92f7787e560a119a3c5f5d6489e","title":"","text":"Emacs mozc looks to only package the file, but it requires other binaries to work. Specifically 'mozcemacshelper' is required for it to run, as well as the mozcserver. I suppose the server can be installed with ibus-mozc, or fcitx-mozc, etc, but either way I did not find 'mozcemacs_helper'. Steps to reproduce the behavior: emacs to require it - and run mozc Japanese input via the Mozc IME should be functional <!-- 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.\nI made a patch Could you try it?\nI have a feeling this will not work for you now due to Apparently just changed paths (it's in now under the ibus-mozc store path). So I think it should continue to work as long as the emacs variable is updated. (I'm using fcitx5 so it didn't hit me, but I came across this by chance and thought I should let you know)"}
{"_id":"doc-en-nixpkgs-455a07b8a545d406c1cbab20ca38156bfc94f8db632076c0a06d1dcc8875b16f","title":"","text":"Package name: Latest released version: Current version on the unstable channel: Current version on the stable/release channel: Notify maintainers I attempted to update the version myself, but encountered an issue: Unfortunately, I don't have the time to investigate further at the moment. Therefore, I would appreciate it if someone else could take it from here. Note for maintainers: Please tag this issue in your PR.\nI've updated the issue to reflect that the same error persists even with version ."}
{"_id":"doc-en-nixpkgs-8a82419281165c91816ec3583ad2bc967a30c8f45ff1bec11af347f7bd47aad4","title":"","text":"Any expression on darwin which sets fails to build claiming that the C compiler cannot create executables. This is the same issue as , but it more serious than I thought, so I'm raising it as a separate issue. To reproduce just change anything to use on darwin, like the build.\nI'm beginning to suspect executables built on 10.9 which don't use clangStdenv, but rather use the gcc 4.8.2 which Nix builds. I'm seeing frequent and consistent general protection faults (EXCI386GPFLT) from several different executables built in my Nix store. It's still possible these frequent GPT faults could be due to a faulty processor, so I'm waiting on delivery of a new desktop machine to do some comparison testing.\nFor future note: Those GPT faults were from a bad memory module in my machine. After fixing that module, I was able to rebuild all of my Nix packages using , and it succeeded as expected."}
{"_id":"doc-en-nixpkgs-9f8f216c8ac72021e5cbbc767a3a91aae8ec9b8441931c1e3b6ea640d2883033","title":"","text":"name: All packages in current version: 1.2.189.1 desired version: 1.2.200 maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-79097b8d77aa0f689a795b30659f8ae72d64a31fd162810bd6e1cd3b17235b3e","title":"","text":"Steps to reproduce the behavior: cemu Adding and to buildInputs might fix it <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-dd817681221ef2cce5ac0f715460887c0c11441842dcb2021e2cafe8a4d6f467","title":"","text":"Trying to update a system to the latest \"release\" () results in the following error: I don't know how to easily reproduce this. At least for me, it seems to happen because the needs to adjusted. So: Try to update a system that (at least) uses ZFS I guess ... No build failure. N/A It looks like this was caused by . I'm not sure if the ZFS module is the only place that needs to be adjusted after this PR has landed. (authored the PR mentioned above) (approved the PR mentioned above) (ZFS maintainers) Please run and paste the result.\nFor now, I'm not sure, I can reproduce on 23.11pre504982.. It seems like the fix is obvious though.\nWhile I understand how to adjust the two lines in , I don't know how to deal with the other occurrences of in that file.\nUsually you can replace \"PATH lookup handle where this binary actually is.\nI have a potentially fix in\nSomeone should prove that before the fix, this was broken with a NixOS test ideally and with this fix, this is unbroken.\nI suspect it's related to and that that's not covered by any of the existing nixos tests.\nAnd that in turn can't trivially be tested end-to-end because nixos-generate-config doesn't actually support non-legacy zfs mounts... I've written a test and a little prose about the issue:\nMaybe we should consider adding them. Using new mounts is rather convenient when the disk needs to be mounted in a live iso.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nRan into the same exact issue over here. Also running on ZFS root. (The discourse link above is mine.) EDIT: Fixed by updating to master. I think I'll be converting to flakes soon, thanks to this\nFix reverted because it broke basically the entire nixos test suite:\nI get this with NixOS 23.05.\nare you sure it's exactly that? The util-linux split isn't even on 23.05 so that would be very weird.\nYes\nThat sounds like you're somehow using unstable util-linux for the stable initramfs generation, and it's not surprising that that would break."}
{"_id":"doc-en-nixpkgs-a1c49f18fdab055debfb9125953e4c185c73e37408b8059175c511a0176050f7","title":"","text":"You can try confirming this by temporarily setting both nixpkgs to point to the same (doesn't even matter if it's unstable or stable).\nI have unstable for Alacrity which is an application, I don't see how that would affect initramfs generation.\nAnd I don't see how you'd get a split util-linux from 23.05, since wasn't backported there.\nIndeed: And in fact: Which is a different util-linux version number than we see in your error message. Finally, your nix flake metadata says your using , and: So something fishy is going on here. You've got an overlay or override or something that's pulling in a different util-linux from unstable. Either that or there's some other build that's occurring as an unexpected transitive dependency that's building a nixos system using an unstable nixpkgs that doesn't contain the fix. Either way, I feel fairly confident in saying this is some obscure and subtle user error."}
{"_id":"doc-en-nixpkgs-7178e30bd3567a8ab4af8687945aca9af423cca2be6f79934f6c73afda50904c","title":"","text":"should hide the cursor but does not on X11. I have not tested this on Wayland or Cocoa. Steps to reproduce the behavior: GLFW 3.3.x (to match unstable, which is currently 3.3.4) GLFW's dependencies ( on X11), build the library's examples. The default CMake build should do the job: using or equivalent. Verify that left clicking the window hides the cursor since is set. NixOS's , build the example manually with . Execute it and now clicking moves the cursor to the center of the window but does not hide it. NixOS build should behave the same as the hand-built one. GLFWCURSOR_HIDDEN is also affected. and\nCould you send a strace of you running the example?\nYes I could. It seems that it's not due to how GLFW is built by nix but how dynamic libraries are looked up at runtime. Since the handmade executable only works with I made the wrong assumption: the one linked against nixpkgs' GLFW also work correctly. For the ease of reproducibility this is the program for producing the straces: I'm not sure if this is the cause but something is definitely wrong:"}
{"_id":"doc-en-nixpkgs-b2358a87186704b770911fbc04a428db75b4e0df2293d1a6fce2aef670a9b8c0","title":"","text":"Describe the bug Themes are not listed anymore in the Appearance Preferences for the Mate desktop environment. Some screenshots of a VM running Mate to demonstrate the issue: ! ! Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nIs the value of clobbered in the session? In an unwrapped program like , what is its value?\nIn in a VM with almost only Mate installed:\nWith the following patch find the themes.\nIt seems that the function to locate the system themes. This function is returning something like , which is not suitable for NixOS, I suppose. If this is really true, than is not being used. How it used to work before, I do not know.\n uses the environment variable , if it is defined. Does it used to be defined in some NixOS module, and has that changed?\nWe patch gtk2 like so that function works there without having to set which isn't good. By all means mate shouldn't use this totally deprecated function at all, especially in gtk3.\nI may patch it to use and submit upstream."}
{"_id":"doc-en-nixpkgs-86fc1fa8fafa0f9d1237ae1a8fbc09661307a7b6d2bf945353011e60ad78bb18","title":"","text":"Describe the bug When using krb5 together with samba & winbind for login in an AD, login works everywhere except . So or for example work just fine. However, when is used (either through the binary in the shell or through a tty or display manager), I get: Up on further inspection, I noticed a difference in the respective pam service files. Most of these files have with one notable difference: has If I change the in by , I can login to AD accounts without problem even using or . To Reproduce Steps to reproduce the behavior: (It's not realistically possible to reproduce the full setup) an AD with krb5, samba (+winbind) and a custom pam winbind service ` Expected behavior Login works for AD users with , and all the same. Additional Notes I'm by no means an expert in the domain of domains. What I however wonder is, how others solved this issue when integrating NixOS machines in an AD. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nUpdate: This seems to be related to the section following in the pam module. Namely, if any of , , , , , or is true, is , breaking any remote auth (like LDAP/AD/...). Why is this the case? Do these things (like kwallet or gnome-keyring) only work when called after ?\nI marked this as stale due to inactivity. &rarr;\nThis is not stale.\nAt least for sssd, it looks like gnome keyring would be propagated correctly (). So probably the comment pamunix is marked as 'sufficient' on NixOS which means nothing will run after it succeeds. Certain modules need to run after pamunix prompts the user for password so we run it once with 'required' at an earlier point and it will run again with 'sufficient' further down. We use tryfirst_pass the second time to avoid prompting password twice from is likely not true anymore for sssd\nFixed by ."}
{"_id":"doc-en-nixpkgs-6d1d897cf6d46f6f7d95f41f92abeceb8cb3bacd7e679d9ae2540841f3444b24","title":"","text":"When building nixos top level, will be too long to consume. I don't have a minimal config to generate the drv but here is an example: No Error Related code: Not entirely sure which version is causing the failure --- used to be able to built on but seems to be failing afterwards. Will update once find the exact hash. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThe module list grows over time, so it would make sense to hit the limit at some point. I suppose you could write the expression to a file and pass to fix the problem. I don't get why this derivation is called \"lazy\" though."}
{"_id":"doc-en-nixpkgs-8eafcd7d432d35c763e9bed6b773b609e673e30fae0cb394682eb700b8d0f604","title":"","text":"I want to use the TTS Mimic on a Debian 11. After installation, I Tried reading a text. Cli usage give me an \"alsa lib error\". Steps to reproduce the behavior: -env -iA -t \"hello world\" A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result. Maintainer information:\nworks perfectly on NixOS 21.05. Can you elaborate more about your sound setup? While geared toward NixOS, this thread might give useful information to debug further: Also try running ALSA tools or CLI audio applications natively from Debian and via to observe any differences in behaviour.\nThe above works for me too on NixOS, at least. I'm not familiar with how ALSA and PulseAudio in nixpkgs integrate with non-NixOS systems; perhaps a thread on Discourse might be of more help.\nI was able to reproduce your issue on Ubuntu 20.04. It seems this is . A few workarounds are mentioned in the linked issue.\nIt seems mimic just needs a proper wrapper: should give you some output.\nOk, I found a solution with inspiration. alsa-lib-1.2.4 doesn't containt but if i installed alsaPlugin (nix-build -A alsaPlugins '<nixpkgs'), this works for me : However, not really user friendly."}
{"_id":"doc-en-nixpkgs-c8d2a22c59447d367d98b88b478dbc297ee34d0cf62b0782e11b732ea8e6685a","title":"","text":"Describe the bug Because snappy does not install a pkgconfig file, you can't take snappy as a buildInput, packages will never find it. To Reproduce Expected behavior Metadata system: host os: multi-user?: sandbox: version: channels(seb): nixpkgs: Maintainer information: cc\nI have opened a PR on the snappy codebase: It is waiting for review and then nixpkgs will need to be updated. Note how the PR has to handle the absolute path being configured in cmake by nix\nhas decided not to take the patch upstream, so I will work on adding the pkg-config file as part of the nix installation\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on ."}
{"_id":"doc-en-nixpkgs-df124a2644229762d7c4c0b7b5bd8f5ca53b72f535130aa9f8426cb896c6dedd","title":"","text":"Describe the bug librealsense cannot be built on/for aarch64-linux. I see that the derivation says it is not supported on aarch64-linux but I also know it is possible to compile the library normally on that platform as I have done it before. So I think its just a problem with the derivation for now. I am willing to help in the work to fix the recipe, and test the fixes, but I am relatively new to the nix language and build system. I have attached the error message I get, could someone point me in the direction I should be looking to fix it? To Reproduce Steps to reproduce the behavior: Screenshots Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Maintainer information:\nHello! I tried it and got similar errors building graphite, though I can get it to build when I use the versions of the libraries so maybe that's a good place to start? I'm not sure what the issue is unfortunately.\nI fixed the build of on aarch64-darwin and aarch64-linux in PR will not work on aarch64 unless somebody fixes the build of package on aarch64 theoretically should work, but in reality the build of which is a dependency fails on aarch64 Will you please open two new issues for and not available for aarch64? The build failures you see have nothing to do with librealsense."}
{"_id":"doc-en-nixpkgs-bf93bee584c302a717bc81f9efd5650c71aee4cb57a0d01cb56676001a226f14","title":"","text":"Package name: paperless-ngx Latest released version: 2.12.1 <!-- Search your package here: --- Current version on the unstable channel: 2.11.6 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --"}
{"_id":"doc-en-nixpkgs-827c17d681460e80b42a8ed932a827383e34d26720c57599782e1f069c63686d","title":"","text":"I have transmission running inside a Nixos container which has been working without issue until I recently updated the system. It now fails to start inside the container, I have tried deleting the container and all its data but the same issue exists when creating a new one. I have also tried creating the path \"\" on both the host and container but it doesn't seem to care. Steps to reproduce the behavior: Run transmission inside of a container Transmission service starts and runs without issue Service status Here's where I have the container and transmission defined in my config. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nSame here, not sure if it's an upstream or nixpkgs issue\nFor the time being and since it's inside a container anyway I'm overriding the root dir of the systemd unit:\nThanks your fix is working for me!\nThe problem is that is listed in : Which got introduced in to The original problem was that was not in the chroot. I'd say mounting all of as read-only is going too far, so a better fix would be to just mount and only if is true. It also seems weird to have this logic be part of Transmission, but whatever. So a workaround is: (And I'm not sure why this wasn't a problem for 3 years)\nI've stumbled upon this issue as well, and wondering if there is anything we can do about it regarding the Transmission service. I had to disable the following is well, before it played nicely in my setup.\nindeed, adding only was one the alternatives suggested in , so we can try your suggestion. IMHO disabling or should not be the default, we could make them use though, would that be enough for you?\nThis is actually still an issue and it isn't limited to containers. Adding the params that posted, unfortunately, does not work for me ;/"}
{"_id":"doc-en-nixpkgs-abab2609755e7e3b885c4e94ae5137627387d35be0bc794776c7c719bac71004","title":"","text":"Project description A simple and easy to use mod manager for several Unity games using Thunderstore. Support for Risk of Rain 2, Dyson Sphere Program, Valheim, GTFO, Outward, TaleSpire, H3VR, ROUNDS, Mechanica, Muck, BONEWORKS, Lethal League Blaze, and Timberborn. Metadata homepage URL: source URL: license: mit platforms: linux\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-fbfa66ebfbbe7f644a911dfa1cbd0397d303597f6728ee82877d6c9b56715291","title":"","text":"During Hackage downtime, nix builds are needlessly broken. There are mirrors available; we should use them. See: Mirrors include: http://objects-us-east- I'm a third party reporting errors I've heard of, so I don't have precise repro steps. Do certain Haskell-related build stuff during Hackage downtime, I guess?\nMirror list is available at E. g. https://objects-us-east-"}
{"_id":"doc-en-nixpkgs-972bf251b42cc4f9b006a58570595af2de22aab8ef8aa759f3e8598630675a45","title":"","text":"The ffuu tool analyses iptable rules and dumps them. I thought it would be pretty cool to try it out on NixOS.\nLooks like has done this:"}
{"_id":"doc-en-nixpkgs-6b6f912dc2e086a07b38f641253bcc1f4ef6967e6862e38563d828909f9c6166","title":"","text":"Describe the bug The Thunar bulk-rename dialog doesn't support regular expressions. To Reproduce Steps to reproduce the behavior: multiple files. -Click → Rename. \"Search & Replace\" Expected behavior The \"Regular Expression\" option can be checked. Screenshots ! Additional context This appears to be because it is not using PCRE or PCRE doesn't support UTF-8. I support it isn't being built with PCRE at all. Notify maintainers No maintainers, touched it last. Metadata system: host os: multi-user?: sandbox: version: channels(kevincox): channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-c0c11b92e729531686cce62a1e81450c9201ea8f397de59752ae1f86f4a2a4b2","title":"","text":"cannot access my devices. Here's an example log: I'm almost certain, that the issue is an empty , as the service runs fine without it, but I'd like a second opinion before sending a PR. Steps to reproduce the behavior: and set [Optional] Override DeviceAllow list: The service will work now. should run without errors. Adding has the same issue, overriding fixes it aswell. Possible offending code: Not sure why the override is not working, though: <!-- 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.\nWhat does your resulting systemd unit look like? Also default priority is 1000, so overriding it with priority 100 should work.\nI agree, it should work, here is the before and after (created with systemctl cat) Stock nixpkgs: With my changes: Evaluating results in for me.\nYup, that looks like the problem. That would mean they share the same priority, so we should likely try going down to 50 with the override.\nI'm not sure if [the wiki][1] is up to date, but 100 seems to be the default, 1000 is the default for defaults. It might be more future-proof to change to , but it's probably more disruptive for the other modules. Overriding with 50 seems to be the smarter option. [1]: I could assemble a PR, seems like a very small fix\nFeel free!\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-5a621837f2060c050f771bbc79aba79967a4d25562d788a0a0058456bf301c4b","title":"","text":"Stressful Application Test (or stressapptest, its unix name) is a memory interface test. It tries to maximize randomized traffic to memory from processor and I/O, with the intent of creating a realistic high load situation in order to test the existing hardware devices in a computer. It has been used at Google for some time [...] In my experience it's an absolute monster in finding random memory errors that don't show up over weeks of real world usage. Until ECC is commonplace, running this software is necessary. Metadata source URL: license: Apache 2.0 platforms: linux\ncould you please give a try?\nworked no problem, thanks a lot!"}
{"_id":"doc-en-nixpkgs-e7718299cbc1b844776f9a4f1988294f1ab3e8cec5833fd10c5453b896345b26","title":"","text":"Package name: poop Latest released version: 0.5.0 <!-- Search your package here: --- Current version on the unstable channel: 0.4.0 Current version on the stable/release channel: 0.4.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-86976b64b3cfaa95b7f1404f9eb096a07c0ced0e062acc51ea73718092c1d8a8","title":"","text":"I have installed, and as of 24-05-2021 it fails with the following output: To Reproduce on stable channel 21.05 Notes and findings I do not use pipewire. This bug seems to happen regardless. This bug seems fresh. See on the Manjaro forums. As far as I can tell, is not available in nixpkgs. This may be fixed in the new Steam runtime. Notify maintainers Thank you! Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(matt): nixpkgs: Maintainer information:\nbtw is in nixpkgs, i use this tool to find what package a file is in\nFYI, this seems to only happen on the steam beta, workaround (for now) would be to switch back to steam stable.\nThe workaround of deleting works! Having a flag file is great, since it allows you to switch to stable without launching the beleaguered application. Thank you! I use the same tool, but I must have an out of date index. I think it's time to add reindexing to a cron job.\nAfter reindexing, I see the Nix reference: Users who want to use the beta could presumably use the following override, though I have not tested it on my machine:\nDeleting worked for me too, thanks for the help.\nWhen using the new module, packages are automatically picked up from :\nLooks like this beta release just made mainline. Vanilla Steam install is broken.\nfixes it\nso... could you create a pull request to fix it for everyone? that would be great :)\ni can make a pr for it\nrelated:\nFor people that are \"stuck\", and just want to play games\nGoing to pin this until we have another unstable / stable release\nJust updated on unstable after 2 weeks to find this and... Steam just segfaults with this. Think that's my cue to go back to stable.\nworks for me, can you give more info about your environment? this will be backported to 20.09 and 21.05\nIt still is segfaulting on my 2 week old configuration that worked yesterday, so idk if even going to stable is going to fix it. Guess I'll be without games for a bit."}
{"_id":"doc-en-nixpkgs-e193f39279758916c5c8682eb9828ee0244415613da22ff49472fcc664ae6d0c","title":"","text":"yields CPU: Intel i7 4790k GPU: AMD RX 5500 XT Configuration is\nUpdating completely (completely as in like 30m ago) resulted in broken vscode as well. Full reboots after each update. No dice.\nLogs:\nNevermind. Apparently something broke my steam profile. fixed the issue. Time to copy all my games over...\nmove the games its faster also steam automatically detects the games so you dont have to go through and install them all again for it detect them\nYea, I think valve just oof'ed on this one\nif anyone is still stuck with the command that I had above, you might be able to use: which will add pipewire, and make the steam check happy\nSo it just corrupts the profile every time I close and re-open Steam. So much for it being fixed.\ndid you try the one I just posted?\nYes :(\nInteresting, your channels are quite old, if you don't use flakes, it might be worth while to\nI use flakes :) Nothing is really installed from those channels.\nthat's what I assumed when your installation said something significantly newer\nSame issue right?\nLooks like it. Good catch!\nUnfortunately, the linked issue doesn't seem to actually have a fix that works, but I think it's still out of scope for this issue, so it can probably stay closed. I'll just have to use the flatpak until Valve fixes whatever they broke. Update: broken in flatpak too :/\nThe patch seems insufficient for my system\nDitto previous comment. Running 20.09 steam still not happy.\nThat also doesn't work for me: Full log: EDIT: Sorry wrong ping! x.x\nIt's not that the issue is not fixed, but the system API (seem to be X11 here or libc) is not compatible with the package. Try this for 20.09 until it's available in the channel ():\nI still think we should move forward with as it's current needed for the beta runtime, and will eventually be needed when the runtime gets bumped\nworks for me. But I've done 2 channel updates and nixos rebuilds and my vanilla steam install is still broken. shows it was last built 08/06 with commit ."}
{"_id":"doc-en-nixpkgs-63f99c240b8baa75ef2e1a5c7a8604043dd696711766cd52a1d00b9551ca02fe","title":"","text":"That commit is exactly the commit for this issue: Forgive my ignorance, but shouldn't a channel update + nixos-rebuild pull this in and 'just work' ?\nRun nix-channel with sudo Or rebuild with --upgrade which does it for you\nDo games run with Proton anymore for you? I can get Yooka-Laylee to work using the nix-shell command, but not Foxhole, which requires Proton. I'm on unstable, if that changes anything.\nFor those who are like me and install user software with , this workaround works, at /home/[username]\nYour snippet helped me get steam running in my flakes based setup. Thank you! Properly learning nix averted for yet another day. Hooray!\nMy crasher was solved by adding to . It's a different, unrelated bug, so I will create a separate issue tonight probably.\nI did a and steam started working for me again. Thanks for fixing this!\n... Ironically, all channels have updated with fixes except unstable...\nLatest unstable now has this fix and my steam is working again. Thanks folks.\ncc (Apologies for the ping, please let me know if it's inappropriate) I've encountered some strange behavior trying to get this to work. Steam will notably fail with the following error despite running to bump the and channels: I've also tried using and attempted to add the override to both channels, like: Unfortunately, none of these approaches worked. In a surprising twist, the following does work, although I can't figure out how it's different :thinking::\nDo you have a stale installed under your user account, or otherwise have a stale in your path somewhere? Try a to see where is coming from.\nI don't think so, unless I've done so accidentally.\nThat is installed in your user account via . only upgrades \"declarative-style\" packages referenced by your . It will not update packages installed via . Do one of the following: If you want to manage steam declaratively, enable in your , for example, by setting and then run to uninstall older versions installed via If you want to manage via , remember to periodically to upgrade those packages. I recommend picking one strategy or the other exclusively for managing your packages.\ngreat eye, thank you for the advice and thorough explanation! After running , I can see it now uses the updated path and loads correctly."}
{"_id":"doc-en-nixpkgs-b5d401b2f7df1860db058b75af0fdb1aabbf77e1d3e343f5cd374b35d681afba","title":"","text":"honk-initdb.service attempts tu run even though already exists, causing it to fail and prevent honk.service from starting. I think honk-initdb.service is supposed to be skipped since already exists? Please run and paste the result.\nHi, Thanks for the bug report. That's weird, because that service shouldn't run since the file already exists. I will try to investigate during the week.\nDo you know if there is any way I can make honk.service believe its dependencies are met, as a workaround?\nWhat I did precisely in I have no clue why this is not working yet.\nI pushed a PR here: Could you try it and let me know if this is fixing the issue ?\nDear is your issue fixed now ?\nPing ^^\nThe condition seems to work but the issue remains?"}
{"_id":"doc-en-nixpkgs-4bc3d899d3de3197429424d51c5f6f2c3855a64d8b2c1ffecfc924c3428e7b43","title":"","text":"Steps to reproduce the behavior: bitwarden Please run and paste the result.\nWill be fixed by"}
{"_id":"doc-en-nixpkgs-49266b3d42d5fe1839a71c39091ff3fb66b79afc9e445fe5fe46fc5ed4a2e2ba","title":"","text":"Describe the bug repology reports some issues with the package name and version. It should end with the version, not \"staging\". So we could just call the package . But we should be consistent here! All the wine versions and attribute names are messed up. wine-4.0.2 | wine wine-4.0.2 | wine-4.14 | winePackages.unstable wine-4.14-staging | wine-staging wine-4.14-staging | winePackages.staging Why is \"staging\" in the package name but \"unstable\" not? Is there even a difference? So i would remove \"staging\" from \"wine-4.14-staging\". Metadata master Maintainer information:\nAdding to this: I locally built and without issues with the current packages but I'm not sure what's actually required for a PR here. Seems odd that it was so easy and nobody else already PRed it.\nMind doing the PR then? :)\nI'm not sure what's actually required for a PR here. I also don't know what the wine maintainers want. My motivation is to get the repology error fixed. So i would remove \"staging\" from \"wine-4.14-staging\". Seems odd that it was so easy and nobody else already PRed it. There is a lot that can be improved in nixpkgs that is quiet easy! For example i'm currently fixing package versions that produce errors in repology. There are 586 known problems left to fix: There are 4997 outdated packages in nixpkgs unstable: Most of them probably quiet easy to update, but someone has to invest the time. Maybe there is already a PR that is not merged yet. A review can help to speed it up! But we are already the best distro when it comes to up-to-date packages! And we might supersede AUR in the future with total number of packages. But at the same time, many common packages are not in nixpkgs...\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\"."}
{"_id":"doc-en-nixpkgs-a100435b840235a2f8176c829fee3cdd632b97576a5d74c5c397b071165d000a","title":"","text":"This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .\nissue still exists cc maintainers\nThere is a difference between unstable and staging. Staging is the staging patches on top of unstable.\nThat makes sense. Can we add it to Long description? Repology seem to recognise the version now: !\nAdded to description, but if you think longDescription is better, or think the wording is not clear — please comment or PR."}
{"_id":"doc-en-nixpkgs-66dffd12d4da0608835df21130726191e7fafd0fa2a49f730574eee8bef5d3b1","title":"","text":"Describe the bug It should be the path to ca- To Reproduce Expected behavior No error happens. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(mnacamura): nixpkgs:"}
{"_id":"doc-en-nixpkgs-6bdc0f1b71e4c1133cfd802d8bb6b8f8a583ea2296f3a4212b1867b98391418c","title":"","text":"Package name: linuxKernel.kernels.linux_zen Latest released version: 6.7.6-zen1 <!-- Search your package here: --- Current version on the unstable channel: 6.7.5 Current version on the stable/release channel: 6.6.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nOh, forgot to do it. Currently not at home. Will see how late it is when I get back. PR will be up tomorrow at the very latest.\nPR is up. When it get's merged, I'll close this one."}
{"_id":"doc-en-nixpkgs-09dc705c3c093c96ab435eab8089b5ff6150f6527240bb92106f4ad80b0a828d","title":"","text":"Package name: wayland-protocols Latest released version: 1.32 <!-- Search your package here: --- Current version on the unstable channel: 1.31 Current version on the stable/release channel: 1.31 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR.\nfixed in"}
{"_id":"doc-en-nixpkgs-4dae91ad785dd8be230756c6bcc3dfdfdaa5ce6c72295e36bb4899dc23e79e17","title":"","text":"doesn't build with GHCJS as of due to an issue on and/or as suggested in It looks like this is related to\nI'm trying to build again with at the moment, I'll report afterwards if it was successful.\nYep. Updating 's dependency on did the trick. Everything built just fine. See pull-request"}
{"_id":"doc-en-nixpkgs-09e0cbae37ee434e3d3e5353ca0444fc3470eaec50eb28fd7a7f8ab12331bb5a","title":"","text":"The file does not exist so ODBC connections fail. The offending line is which should reference . In add: to nixpkgs Create/Edit and add the following: [MyNewDSN] Driver = MariaDB Server = localhost Port = 3306 Database = MyDatabase User = MyUser Password = MyPassword Run Then run: and you get the error: [][unixODBC][Driver Manager]Can't open lib '/nix/store/4cnh6dg7mwhsw0yy7c5ajxhw29l6hwa8-mariadb-connector-odbc-2.0.10/lib/libmyodbc3-' : file not found [ISQL]ERROR: Could not SQLConnect system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nFixed in"}
{"_id":"doc-en-nixpkgs-ee0989cb8533e0ddce2e35f6d7bbdae64e560fac740ed0fe42b8ce1a7e6817f0","title":"","text":"Project description An OSC UI replacement for MPV with icons from the bomi video player. Also contains thumbnail preview and a picture-in-picture button. (MPV Userscript) Metadata homepage URL: source URL: license: unlicensed platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-e50c049021c9eeaa426de070d9b5ec6a1bf165a0bf2adafc0abb0d9f192e24f2","title":"","text":"Describe the bug When trying to use this package, I'm getting: To Reproduce Additional context I'm currently disabling gst-rtsp-server's split outputs in order to actually use it. Notify maintainers Maintainer information:\nWe should probably apply\nThat patch won't apply. But I managed to apply a different fix based on a common fix to other gst plugins, at ."}
{"_id":"doc-en-nixpkgs-0dc45d1f6afac4362035b76ee83c575f349414e49a4cc072faacc18169d6c509","title":"","text":", CVSSv3=4.3 (nixos-unstable) phoronix-test-suite is vulnerable to Cross-Site Request Forgery (CSRF) Scanned versions: nixos-unstable: . Cc"}
{"_id":"doc-en-nixpkgs-a5beda798f8350f28c839ca247ee53b72a95bcc0e784973e1ea7781c1d3d8d86","title":"","text":"Project description There is a great wine package currently in NixOS but it lacks mingw support for the DLLs. This is needed for a few games including World of Warcraft it seems. Basically we need to build WINE with \"--with-mingw\" compile flag. The problem I have here is - I have no idea how to actually include the mingw compiler as a dependency to WINE. Any help here would be appreciated. Metadata homepage URL: | source URL: n/a license: n/a platforms: linux\ncc\nI think something like this should work: You should see something like this in your build output: I've had to do something similar when trying build Guy1524's Easy Anti-Cheat fork:\nMaybe it would make sense to add a parameter to handle this?\nI am not sure what it actually does, but maybe\nThanks a lot for that - I also another problem which your linked code sorted - the \"compiler cannot create executables\" error - strictDeps looks to have solved it though. :+1: I can tell you - it uses the mingw compiler to compile \"PE DLLs\" (I believe this is in reference to Windows PE DLLs but could be wrong.) It then uses these in place of the normal fake builtin DLLs it uses. This enables a much more convincing Windows environment which some apps / games appear to need.\nAhhh makes perfect sense. Do I understand correctly that build closure grows quite a bit? Any impact on runtime closure? I will merge a PR adding an off-by-default MinGW option, absent some well-grounded onjections, but maybe it should indeed be off-by-default. I guess if runtime closure change is small and build closure change is within 20% or so, we could enable by default…\nI'm not too sure what closure means in this context D: What I will say, however, is that this is OFF by default in most distros so I think it should be as an option and not enabled by default - just as you suggested. Your changes got me a lot further in to the build but I believe I am missing one critical change - the build runs correctly and starts building DLLs via mingw but then fails out with: Actual overlay pkg (including the fix for exactly this error from your code linked above.) I wonder if mingw is ignoring the hardeningDisable flag or is using defaults somewhere?"}
{"_id":"doc-en-nixpkgs-234673dc836b1b466e59827f8c1e377d34d5ccbf7e0410798df574702f02d3c7","title":"","text":"We're so close to fixing this I can feel it! :+1: :\nI think Arch builds wine with mingw: () In official wine repos for fedora () there are lines: and for Ubuntu (), there is mingw-w64 in . So, if it doesn't increase closure size by too much, I'd say it's a good idea to enable it by default.\nTransitive closure: deps, deps-of-deps, deps-of-deps-of-deps-of-deps… This can go over runtime or build-time dependencies, of course But yes, no need to look too deeply into impact if the default is off.\nHmm, it worked for me when specifying . Maybe there is a problem with using ? The Nixpkgs manual strongly recommends using instead of . I think it's very likely that's the cause: I'll gather information about the closure sizes for each configuration (wine32, wine64, wineWow) and I'll also look into creating a PR that adds a new support flag.\nI hadn't noticed that little difference - changed it to overrideAttrs and it's now building properly from the looks of things. Thanks again for all of your help on this - that's super helpful! :+1: It looks like it was disabled by default in Gentoo (in: ) due to the following bug: ^ This may not be all that relevant to NixOS - just wanted to bring it to your attention.\nHm, interesting. We'll see. if it is default-off, feel free to skip the closure-measuring step for anything you are not going to use anyway. No need to build something just for that.\nI noticed that runtime closures were dramatically increased with this option: wine32 (minimal): 829.3M -2.6G wine64 (minimal): 912.5M -2.6G wineWow (minimal): 1.5G -4.9G It looks like development header files from are being referenced in all DLLS under . For example, these paths are referenced in the wine32 build: Right now I'm looking into why they're being and if they can be removed / reduced.\nIf mingw is disabled by default, perhaps it could be as a new attribute so that it's cached?"}
{"_id":"doc-en-nixpkgs-1ea78ea94b4089afe32ca884f7a48085725b594a0d23217248c01f4ffd38cc27","title":"","text":"Considering it's enabled by default in (at least) Arch and official wine repos, some users may expect it to be enabled by default in NixOS too. Having to override wine for e.g. lutris and also build wine (which takes a pretty long time) is a lot of friction for an unexperienced NixOS user (or someone with not so powerful hardware).\nPreferably we would enable it by default. Once, binutils 2.34 is which contains the we can re-enable stripping to avoid the closure increase caused by the header references.\nConsidering the OP mentioned specifically games, I'll just mention that lutris now ships (via its \"runners\" machinery) wine 5.21 with mingw.\nNow that has been merged you can just use: This isn't currently enabled by default or cached, but does this solve your issue? Hopefully we can enable this on the base build once is merged, and after stripping is enabled.\nI don't seem to be able to overwrite to enable . It does work for though. It complains about a missing hexdump dependency and a patch that it is unable to apply.\nDid you eventually get WoW 9.0.2 running? Starting ends in an Access Violation popup for me. This is on wine 5.22:\nJust a heads up, I noticed a regression running Cities: Skylines (specifically the Paradox Launcher) with : It looks like this is a problem upstream (I have the exact same problem with Lutris wine), but for now I'm just forcing it to launch with a wine built with .\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-1e375004a7ad1fb1437d6fdc19436e713218e4415a0cc8be24412621fa710e41","title":"","text":"Describe the bug The last several Hydra trunk-combined runs have been blocked by (among other problems) a , which was recently back(?) to release-combined in (). When I run the test locally it sometimes succeeds and sometimes hangs forever. To Reproduce Steps to reproduce the behavior: it succeeded, clear the result with (is there a better way to do that?) and try again. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(anders): nixpkgs: Maintainer information:\nWe have a lot of channel blockers currently, so I recommend to also purpose revert this one. Though it sounds like it's only with issues, so perhaps comment it linking to this issue. We can always re-add it."}
{"_id":"doc-en-nixpkgs-fd862fae58dcb1e52a2425484b2f111756bd202332c154c9daf26462abe25495","title":"","text":"On 17.03: This is potentially problematic as consul may use the version number of peers to make decisions. Why is this?"}
{"_id":"doc-en-nixpkgs-7cbd7fe22e374ce05248d060666275df3b4028cca9708f44bdd8c2ff83f9ebaa","title":"","text":"Package name: trenchbroom Latest released version: 2024.1 <!-- Search your package here: --- Current version on the unstable channel: 2023.1 Current version on the stable/release channel: 2023.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-33d2f9bdb2a82e973dbef6e823c7a6610faa72a29014b5c198d7ef88239c64d0","title":"","text":"Steps to reproduce the behavior: builds fine on NixOS, not on darwin. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\ndoes work for you? maybe something like will work while the PR is waiting to merge.\nYep! Thank you"}
{"_id":"doc-en-nixpkgs-d2efb5f7b796b60aa3117b90a86036fb42fff2ed0beb58783033f901dd0cfb6f","title":"","text":"Project description A tool to print Wayland toplevels status and info. Metadata homepage URL: source URL: license: bsd platforms: linux"}
{"_id":"doc-en-nixpkgs-62769c01d6d4e2e5694e586b5ee76327f3ee65e543bfc52b85440d979fd9beed","title":"","text":"Steps to reproduce the behavior: Upscayl failed to build due to hash mismatch during (I'm nix beginner, I hope to that I write this bug report in right place.) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nStrange! I wonder why I did not get that hash mismatch when I reviewed the PR. Upcoming PR!"}
{"_id":"doc-en-nixpkgs-f442146e42d0a0989cc35734e689eab44c645162e5a1e45182455be71fd07bf6","title":"","text":"Attempt to build on Sample This is on an M2 chip, and it seems the issue is with node-canvas not being able to install due to missing giflib. Building with: Fixes this. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8ab7dbf7d28a49d01a68100fcb36c0d3b4358ffea12fb756eab8d4d852ac9385","title":"","text":"I have installed the TeXLive package on my system, but its binary script fails to run because: its directory is not found in it does not have an explicitly dependency on it does not have an explicitly dependency on the module for Python 2 cannot be found. Please fix this issues so that the script can be run. (Maybe can take a look at this.)\ncc\nWell, the first two bullets would be fixed very simply by but I don't yet have framework to add external python dependencies to the scripts.\nNothing new here? A similar problem happens with :\ncc Maybe while a good solution is not engineered, a package for without the TeX stuff can be to . It would contain the binary with support for the needed Python dependencies. What do you think?\nThere aren't any true binaries, are there? It's just python scripts IIRC. But still, what you propose is probably the easiest way to resolve this somehow.\nIt is just a Python script that depends on the module.\nMy attempt at it:\nSo pygmentex works as expected now?\nIt works! It can be tested by downloading the example document from the distribution on , unzipping the downloaded files, removing the Python script and the LaTeX style class, and than compiling : The result is , with many examples of code listings typeset by Pygments.\nOK, then I think we can close this.\nSorry for necromancing this (should I have opened a new issue instead?), but it doesn't \"just work\" – or needs further documentation on how to use it: The created by building the pygmentex texlive package can not find the module. gives us such an environment, just try running the command from there -The package though provides a executable which works just fine and finds the needed pygments python module. So how to combine these both packages? In particular I ran into this when trying to use the texlive package, as that seems to directly invoke the executable during build. Issue appears on release-18.09\nI encountered the same issue, the latex package seems to be working fine tough (and can be used as a replacement)\nI have in both with (which provides the style file and a non-functional Python script, because of missing Python dependencies) and (which provides the script). This setup works for me.\nI still do not know a way of allowing Python module dependencies for Python scripts installed through .\nThis is to be fixed in"}
{"_id":"doc-en-nixpkgs-56cc62ff26c95bce9a96252d04b51e8a10ac626e4aabc72d6b0ee9481258c6b4","title":"","text":"Package name: gnubg Latest released version: 1.07.001 <!-- Search your package here: --- Current version on the unstable channel: 1.06.002 Current version on the stable/release channel: 1.06.002 <!-- 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.\nI packaged this in 2015 and I have no idea why."}
{"_id":"doc-en-nixpkgs-65f3088b9bbbf1d02f89358884318a914d04cc0e0ae3906738587b52d788e82f","title":"","text":"I'm trying to use the mwprocapture nixos module (which uses the mwprocapture kernel package) on 20.09 (linuxPackageslatest), and I get the following: Is this known and/or already fixed somewhere? (Also, is it safe to use it anyways?) I'd love to try and fix it further myself, but I don't know how to splice in a local/development nix file into my for development purposes :sweatsmile: (also CC\nLooks like upgrading the package version resolved things. Will create a PR soon.\nThanks for the heads up."}
{"_id":"doc-en-nixpkgs-7878269a2a9c76e4731585fd39fd1205274af45e7b8845c3858cbd3ab33e2fd7","title":"","text":"According to documentation of the app: there's a dozen dependencies we don't explicitly have a dependency on, so there's multitude of bugs that might appear depending on what's on $PATH.\nDo we need a new maintainer of to move this issue forward?\nWe should pull the package from NixOS core...absolutely no reason to have such a bloated less ship by default."}
{"_id":"doc-en-nixpkgs-ad04fdf4e05e638a26c1ba74488d536cc5c6de804e8ee55e5396e66ecf8967b6","title":"","text":"I'm trying out NixOS 19.09 and notice that Enlightenment is still being built under X. Enlightenment 23.0 have some highlight. One of them being \"Massive improvements to Wayland support\".\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as \"still important to me\". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .\nIt would be nice to hear about the recent progress."}
{"_id":"doc-en-nixpkgs-93019e774792df5492445f549f8ff3a401fe56bd46084458829c61455fdf90d3","title":"","text":"I've set up a borgmatic backup script using the borgmatic service. I can run the backup manually by running as root, but fails with the following error: Here is the service definition I used: I then tried to pass an absolute path to cat, by replacing with and got the following similar error: Steps to reproduce the behavior: one of the service definitions above and observe that running it manually works. the output in No errors, as both and are present on the system, and I can run I also noticed that borgmatics default value for , , causes an error when the borgmatic service is run. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nAs I know, NixOS package doesn't use your settings, which mean what you can use in your shell environment doesn't mean the package can use. User can use and whatever command they like in , I can't put everything in . So my suggestion is to use the format when using a command provided by other packages. As for your pgdump command not found, I suggest change it into Good caught, I will file a PR to change the default value.\nThis works, but I'm curious why it's not the default? As is, the service doesn't work for postgres dumps?\nIf we make this default, I think it will add those packages (pkgs.{mysql,postgresql,mariadb}) to nix store even the user doesn't need it. And I prefer to keep the package in minimal. Personally, I use the following code to use mysqldump\nThat's fair. Thanks for the feedback :-) Do we leave this issue open until has been merged?\nYou can keep it open, it will auto close once merged."}
{"_id":"doc-en-nixpkgs-59810d0a40e96f50f4a86d30ef1b6ed8eff812f4126ff717c70551f46056c70c","title":"","text":"As it stands, the NixOS MPD module runs MPD as a systemd system service. As such it expects that the MPD user account (mpd by default) has control over the audio device. This conflicts with PulseAudio when it's used as a systemd user service (the default configuration). The intent of this change is to extend the MPD module so that it can be configured to run as a systemd user service. The changes remain backwards-compatible so users can continue with a system-wide configuration or go with a per-user config. I have a proof-of-concept of the modified module which I'm currently experimenting with. It can be used in as follows: The result is MPD running within a user slice: [ ] Ability to use a different per user; Probably by providing a option which overrides the other options and simply points to a file in the users home directory (ex. ). [ ] See if it's possible to get realtime scheduling to work. [x] Add NixOS tests. Currently there aren't any. The different options make for numerous potential combinations; I'm to lazy to test all of them manually.\ndid you ever add support for running mpd as a user service? It looks like just tests in preparation for running it as a user service.\nWow, I forgot all about this. Perhaps because I soon after stopped using MDP. The implementation is still on Github:\nAn alternative could be to let it talk to pulseaudio over the network. In the past I have used a config in mpd like audio_output { type \"pulse\" name \"pulseaudio\" server \"127.0.0.1\" } and then some config in to allow this access."}
{"_id":"doc-en-nixpkgs-929a1d5a8db7e815a4ebc75f8db23965bb0840363769eadc24aad7f543fe48d7","title":"","text":"When launching the extension through Inkscape, the application freezes. Steps to reproduce the behavior: Inkscape the extension under Extensions Text Launch TexText Maybe linked to <!-- not actually involved, sorry --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nhmm, it opens pretty much instantly for me on current nixos-unstable (). Do you see any error messages in the terminal where you opened Inkscape?\nNo error message is reported on the terminal. Is there a flag I should add to the command for verbosity? I had someone else test this and they reported the same behavior. Something else I noticed is that Inkscape returns to normal if I let it hang for 1 or 2 minutes, but no sign of the extension's window.\nI don't know if its related, but I tried the builtin formula extension, and I get this error when clicking on apply: <details</detailsDo you see anything suspicious?\nsorry for the ping again, but I just noticed that trying to launch TexText results in a file with this content:\nNo worries about the ping! Unfortunately the errors you found in don't seem to be related to TexText. The errors from the builtin formula extension don't immediately give me anything to go on either.\nI was able to identify two problems that are (most likely) causing the issue. The first is the python bindings for gobject-introspection that were missing. I submitted a PR for this one and now at least the extension window opens when I click on it. The second is related to Inkscape throwing a segmentation fault when trying to use the extension. I opened an issue here I don't know what's causing it though. Hopefully we can figure this out. EDIT: Please ignore the first issue. For the second one, there seem to be a fix on the way. I will close this issue if it resolves it.\nGreat that you were able to figure it out!\nSorry to revive this thread, it doesn't work for me. the script errors out i believe because it doesn't contain the path to package.\nI'm afraid we'd need a bit more information. I just tested on latest nixos-unstable () using the above and it worked for me."}
{"_id":"doc-en-nixpkgs-7799799dd87236b98cb91bbcafb1154c197e7d12bfddb7ac6679f5d50550e04a","title":"","text":"Are you using inkscape on NixOS or on a different platform? Are you using the from above or some other way to create the inkscape? Exactly when do you get an error, and what does the error look like?"}
{"_id":"doc-en-nixpkgs-2d1a657681a8b0af6177aea43e1fec631919bed304fb5df354c9cd51e15d836c","title":"","text":"name: current version: desired version: (filling out this template is tedious. especially since there's no syntax highlighting to see through the dense comments) maintainers: cc: cc: who reviewed/merged the libxkbcommon last time. draft PR is incoming. Please tag this issue in your PR.\nLooks like this can be closed now? Correct me if I’m wrong!"}
{"_id":"doc-en-nixpkgs-b069200bc9adf44e745defb2ff93527faa5113933f67afa7d11e718790133287","title":"","text":"Describe the bug Since made it into nixpkgs-unstable I can't install neovim on an M1 laptop anymore, error is: To Reproduce Steps to reproduce the behavior: an M1 macbook run Expected behavior neovim to successfully install Screenshots N/A Additional context Notify maintainers Metadata Maintainer information:\nIs it possible for you to check if reverting fixes the issue?\nYeah, that did the trick. It is weird as I can install luajit with no issue so maybe this is just an issue with the build setup rather than with the lua interpreter?\nRefs I will test this on my M1 as well tonight\nSorry, tonight came later than I expected - I encountered the same issue on M1 and filed , which fixes it. Seems that luajit version is not the issue here ( did not work), as was suggested in Guess we should do a bit more digging"}
{"_id":"doc-en-nixpkgs-49909aaa57e93b6c549606a87b1edc17dc045600e856d9f23afd3c1ca426446d","title":"","text":"Project description It's a pinentry app, using rofi. I , but failed with (pls ignore metadata on that derivation, was testing): Metadata homepage URL: source URL: license: gpl-3+ platforms: linux\nI just gave it try and quickly hacked together the following (based on ): Please feel free to use this as a base for a pr."}
{"_id":"doc-en-nixpkgs-7423453195a00835c08b9ae7a7d9eac4ffc0179929588b1a67d8d379af9cf441","title":"","text":"After upgrading to the current version of nixpgs (nixos-unstable) anki starts up to a blank main window. According to the documentation () that is because of the system glibc having changed to a version not compatible with anki. Their suggested fix is that users move to using the beta package instead. Steps to reproduce the behavior: -shell -p Anki working as usual Add any other context about the problem here. Please run and paste the result. Excerpt from\nCan confirm the behaviour."}
{"_id":"doc-en-nixpkgs-60f9e220610798ace0fc17f6d024d717cf77dc0cb30abb483ee5256631c97dd4","title":"","text":"The package won't install on macOS. It triggers an assertion in : . macOS run system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nAwesome, thanks!"}
{"_id":"doc-en-nixpkgs-b5877da8c04649430d63261a213fbd04662ec8cd97a783daceb434a7a71faec7","title":"","text":"OAuth2 Proxy's Nginx plugin used to forward and headers to downstream programs. This stopped working after I updated on unstable channel, which is potentially related to or . Steps to reproduce the behavior: up OAuth2 Proxy + Nginx up of header name . does not recognize the session More simply: up OAuth2 Proxy + Nginx or something similar the headers — and used to be present, but not anymore and are passed to downstream servers under Nginx. I have I went on upgrade of nixpkgs unstable from sometime late January to a few hours ago, which is what led me to the two PRs mentioned above. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nare you able to play around a bit and confirm if the changes mentioned introduced this regression?\nyes. I can't really pin-point to what exactly since there were a lot of changes. Instead, I just have a local fork from (prior to the changes mentioned in the PRs above).\nI have a pretty good idea what it could be.\nCan you give a try? I didn't test it yet, so it could completely break everything and be completely insecure, just as warning.\nfantastic work please let us know how it goes ‍\nSorry for the late reply, I haven't been able to have time to test it out. Now that I do, it seems like has been converted to . This won't be an easy find-and-replace for me to try in my setup, so I will have to find some time to do proper cleanup."}
{"_id":"doc-en-nixpkgs-849e9056777800f653cf56f1e2756be73b0fb29e9e04ef6cda906dd505767096","title":"","text":"I am encountering the following error after launching Pinta 2.0.2. I thought initially that it was a problem in the Adwaita theme itself, but whatever the GTK theme I use, I always have the problem. I tried on two different machines and had the same problem with both. NixOS with unstable channel Ubuntu + Nix 2.5.1 with unstable channel I did not have this problem in the last packaged version of Pinta. Maybe it is there since the 2.0.2 upgrade? Pinta should launch without this error. ! Please run and paste the result.\nThis looks like exactly the same problem discussed on Except that it should be fixed. Not sure what is happening here, and I don't have access to a Linux machine right now to debug. Maybe can help?\nI also have this issue. It also causes the toolbar on the left to not appear.\nCan someone show me the contents of the directory inside the package? It should have a directory/file somewhere, inside the icons directory (I don't remember the exact path). If this is missing, this is probably the issue.\nIt is missing:\nHuh... I think I can blindly patch this issue, however someone will need to test on the PR.\nWait, I was wrong, it is there, but not in :\nIt shouldn't be in , it should be in . This is the issue. This can be probably fixed later correctly by setting some setting on , but since I don't have access to a Linux system for now I will just duplicate the assets for now. Later on I can do a proper fix.\nCan someone test this PR please:\nWaouh that was fast. Thanks a lot, both of you for your reactivity!"}
{"_id":"doc-en-nixpkgs-7710c51805dbbfed412747fb51b6452f24f86bcceb32d8bb5b75d8e03855f8ef","title":"","text":"Project description Skanpage is a simple no-frills scanner KDE application that is a bit more comprehensive than skanlite. Most importantly, it has multi page support, that skanlite is painfully lacking. cc Metadata homepage URL: source URL: license: gpl2+ platforms: KDE"}
{"_id":"doc-en-nixpkgs-15251b66996a227d44f60e1d4c822c6592aa14e5e751f5fbdd353ed462c3eda1","title":"","text":"Octave needs library to process audio (e.g. ). System: NixOS: Nix version: Nixpkgs version:\nSee\nClosing in favor of"}
{"_id":"doc-en-nixpkgs-49c5e97176c16f384344f01d36eae3669d5be8e557b9a91ff984517ffa41cd69","title":"","text":"In 's tray menu the options \"Floating Window Exceptions\" & \"Active Hint Color\" don't work. Steps to reproduce the behavior: & enable pop-shell in GNOME (Wayland). pop-shell's tray menu and try clicking the mentioned options. Further dialogs should open for the respective features.\nI found the problem: the compiled (g)js are not executible in filesystem. I do not know a solution yet. Most beautiful solution, fix chmod in pop-shell (but how ...). Or after compiling with an workaround in nix. Other solutions are set path to gjs during patching. Till fixing, you can run this features in your in, with calling it per gjs ..."}
{"_id":"doc-en-nixpkgs-ef7c54865dc3ecc91d74106204ecd299e433a59a2a9f2a109ac92dfd1bd956c0","title":"","text":"Project description OpenTofu is a fork of Terraform, which is no longer under a free license (and should be marked as unfree for releases = 1.6.0). This fork is from the free sources before the license change to a source-available BSL license. Metadata homepage URL: source URL: license: mpl platforms: unix\ncc some active maintainers of terraform:\nRelated issue:\nI think it would be a good idea to wait for it to be actually named, see OpenTF is a placeholder name, and at this point OpenTF didn't release an alpha.\nWill to take this on later today if nobody else grabs it.\nPull request has been opened, if the current Terraform maintainers are okay with it I can add them to the maintainers section of the new package. Otherwise more than happy to take responsibility for it."}
{"_id":"doc-en-nixpkgs-f132d9e3cfc0898ab3350446733feb1997e10a6c81985e97e389e55761828c99","title":"","text":"Since won't build () From the above logs: Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nCan reproduce on my ZFS system, not on my ext4 system though.\nI can't reproduce by running on any system.\nI was able to build from that commit nix store is zfs backed\nIt's more relevant whether is.\nThe renameat2 syscall used isn't (fully?) supported by ZFS: I'm not sure how that relates to this issue only occurring with , I guess it's related to the sandbox.\n/tmp is tmpfs for me\nThanks for filing the upstream issue!"}
{"_id":"doc-en-nixpkgs-bf6324256752d407120d4555ef16bb5437e3f9b9e95de0aac3df18cb9f61dce3","title":"","text":"Failure happens locally as well when trying to build spotdl on the nixos-23.05 branch. this the tail of the log: The last line is apparently unrelated: (maintainer) (recent bumps)\nThis test doesn't fail if spotdl is built using version from this nixpkgs commit , I'm not sure if this is an upstream issue with spotdl while using newer yt-dlp versions (newer than )."}
{"_id":"doc-en-nixpkgs-9dd6913039d70bc588abd5fd890874ef14de2ca3e9794bdf6e0c7f80d59d4ff4","title":"","text":"Package name: bun Latest released version: 1.0.9Current version on the unstable channel: 1.0.7 Current version on the stable/release channel: 0.6.2 Notify maintainers People who've also recently updated the package: Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-c0f4f54a4ab3d005ecabdb7af5c96d5115be970a9c20daeef0021ef6ac32af37","title":"","text":"Starting with it is not possible to build the android sdk with ndk included. I tried varous ndk versions which have different failure messges: fails with fails with Steps to reproduce the behavior: the following with : Dropped into a nix-shell with androidsdk in <!-- 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."}
{"_id":"doc-en-nixpkgs-afa232dbffcaea127ebbe76d98c6cf264cfa70187a8708f9f9cf5be571fabeec","title":"","text":"universal-ctags is not built with jansson, which means that universal-ctags does not have support for outputting JSON files. Steps to reproduce the behavior: universal-ctags with error: Expected: Tags file created with json format. Additional context I think this can be resolved by simply adding to the , but I've never written a nix package before so I'm not certain. I did this locally and it seemed to work, but I don't know if there's a better way to do it. Metadata Maintainer information:\ncc I took a whack at fixing this locally. If this looks good to you, let me know and I can create a PR. I'm really new to Nix so it's likely I did something wrong.\nWelcome and thanks a lot for the wonderful bug description Open the PR of course! You can update the package to the last version or add yourself to maintainers too if you are agree Don't hesitate to ask if your find any troubles"}
{"_id":"doc-en-nixpkgs-6053c7291862b60bb4f43ec0095199c435f9443d5083462fd3de9ff4d5f9f996","title":"","text":"When started, ClipGrab always want to download youtube-dl. When after that, ClipGrab never finds the video and stays stuck on «please wait while ClipGrab downloads video info» (translated from french). Steps to reproduce the behavior: ... or ... Start ClipGrab ... youtube-dl dependency should be accessible, and video info should be fetched ! !"}
{"_id":"doc-en-nixpkgs-3f32de43c608df624b0011105aec4cbb764adbba05faa850bff7e76e06b67cd4","title":"","text":"Describe the bug In the AVX512 support was turned back on in openblas, allowing for the use of dynamic, AVX512 optimized compute kernels. started to discover problems with AVX512 while working on the and I can confirm that this problem affects multiple packages that are built against openblas. The problem already manifest itself in that packages fail their unit tests, when build on an AVX512 enabled machine (see for a detailed list). The tests either fail due to a wrong result or time out. I could indentify 5 different packages which are affected by this bug, leading to the conclusions this very likely affects many more packages. Affected versions of openblas, which I have tested, are 0.3.13 (master/release-21.05) and 0.3.15 (in staging at the moment). The problem disappears when: is complied with in is injected into the test phase or just set at runtime. Note that any core type that does not use AVX512 works fine here (tested: , or , but , which uses AVX512 fails). is turned off at openblas build time and is set to a non-AVX512 target (see point 2). you seem to be making use AVX512 optimizations. Did you notice any problems? I suggest to revert and thus re-introduce the makeFlag in openblas. To Reproduce an affected program which is linked against openblas on an Intel CPU that supports AVX512 instructions (e.g. Xeon Scalable) and check the results. In nixpkgs it is at least that is affected (delivers wrong results). , for example, on an Intel CPU with AVX512: the self tests/unit tests never finish in this case. external packages fail to run their tests on and AVX512 enabled machine: Notify maintainers CC Metadata This should affect since (~January 2021) and . The tests I have carried out were run with versions from the ~last week.\nSorry to hear that :(. Then we should indeed revert that change again.\nCan this be closed?\nThe PR has been merged into staging. Should we wait to close the issue until the fix reaches master?"}
{"_id":"doc-en-nixpkgs-de9259ad6b82afb4a9e745baadc931c255a96aa505bad162c89b16006cb18492","title":"","text":"Running reports: To Reproduce on NixOS 19.09. . Metadata I ran but got .\nHello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as \"still important to me\". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .\nI had this same problem today.\nI marked this as stale due to inactivity. &rarr;\nNot stale; this is still a problem on a flakes based NixOS system using"}
{"_id":"doc-en-nixpkgs-dae38a1bfad999a926212f0af2b7f53ec5aadd3fa55ed2477d5db1958689d2fd","title":"","text":"Describe the bug The package that there was a directory in go's tools repo. Unfortunately, this directory was removed on commit  Not sure when the binary stopped being shipped in nixpkgs. To Reproduce Steps to reproduce the behavior: latest version of the the directory of the output from the derivation and assert the command is no longer there /a Expected behavior The gopls command should be available, it's a crucial binary, as it is used for lsp support Notify maintainers Metadata Please run and paste the result. Maintainer information:\nis now available in package. This was changed in\nUhm, silly me, didn't check there was an independent package now. Would you say it is a good idea to update the referenced comment in this ticket? I can volunteer to update the comment.\nYes, I think so. Let's add a reference to this issue as well.\nCreated the PR: Apologies for the delay"}
{"_id":"doc-en-nixpkgs-a8a62c094da346d4b5198d359fd60a04a1ee8b673fed2a6330af46e19d0c9be7","title":"","text":"Project description Epson Scan 2 is a scanning utility for epson printers and scanners. Metadata homepage URL: source URL: license: platforms: linux\nI spent some time on this, but probably packaging epsonscan2 isn't worth the effort. My findings: build is quite tricky, as the sources contain some amount of tweaks (overrides) to standard cmake variables for build/install paths, and some install commands don't use , non-free software plugin is required for network scanning: sources of epsonscan2 are hard-coded to search the plugin in same path as is the installation path of epsonscan2, which doesn't play nice the immutability, the scanner might be supported already by My all-in-one printer is EcoTank L3160, which isn't listed in , but is similar to EcoTank L3150. And, all that was need is the following config: Terminal output:\nI've managed to get this working on PR . As you said, building is a complete pain and required a fair bit of patching. It would be great if other Epson scanner owners could test this!\nWorks for me with Epson L3150 with wifi connection and non free plugins."}
{"_id":"doc-en-nixpkgs-854814d1e21de5f37dcb55062c5dbb717782c045ada28517e1da8ff0f7f6257a","title":"","text":"ssh-dss was deprecated in 2015. Server support was removed in 17.03. It might be time to remove them client-side, and also from examples.\ncc me as openssh maintainer to look at this later\nProbably fixed by update\nThis is still being set through the NixOS option default."}
{"_id":"doc-en-nixpkgs-faaa21654d92c9a55083fa0a55f8d72bb7e5a15bb633762ea99921225a9af000","title":"","text":"Project description amdgputop is tool that display AMD GPU utilization, like or . The tool displays information gathered from performance counters (GRBM, GRBM2, CPSTAT), sensors, fdinfo, and AMDGPU driver. Presumably it wouldn't depend on as does, and it's written in that one language. :lobster: Metadata homepage URL: source URL: license: mit platforms: linux"}
{"_id":"doc-en-nixpkgs-b602d5a9ee3226f0480b0929cbc4899eae268d60dcbd69d2a153c29729e001c3","title":"","text":"fails to find libcdparanoia and flac at runtime. This is a regression from , and appears to be more or less the same issue, except for Plasma 6. Steps to reproduce the behavior: to rip a CD with K3b It works, and lists Flac as a supported format. If applicable, add screenshots to help explain your problem. The fix from should still apply in some form? Manually adding flac to and libcdparanoia to works around the problem. also (maintainer for Plasma 5 K3b) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nPlease test"}
{"_id":"doc-en-nixpkgs-d500b4b10b9a755ede3b693065d413b7f50ff7a1f8b2157a0511d15a534acfe4","title":"","text":"In the dotnet section of the nixpkgs manual, However, the behavior is actually the same if is unset or : all executables are installed. The behavior is expected if is a non-empty list. First, package a dotnet module like this: <details</summary</detailsThen, build the package, and look at the dir : As can be seen, some executables (actually, all of them) are installed despite that . If change to , the result is expected: According to the manual, the expected behavior when is that is empty or nonexist. In the definition of , the phase has something like this: Seems that an empty list is falsy here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nCan reproduce\nThe code is actually which means , then this results in the string and the alternative code path is executed. What I don't see is why would be either in this case...\nAfter debugging it appears that this is being caused by these lines The if condition for does not succeed, as it is empty, so it goes onto the block. Now is iterating over each path given by and spitting out any executable seen in , then it gets wrapped by\nIt is expected that every executable is wrapped in the block (the behavior when is unset). Something should be modified so that it enters the block instead of the block when is an empty list. Oh yes, I guess I need a pair of glasses (maybe just copy and paste next time). If is unset or null in the shell script when it is an empty list in the nix, I guess the actual problem may be in the definition of ? An empty list becomes null somehow when did the substitution, it seems. I have not debugged it, though."}
{"_id":"doc-en-nixpkgs-c13b5d767039d22c8c9e93f80989db055642762c065ad560f8001aaa87e8d55a","title":"","text":"Errors with: This error has already been fixed in by (See also MultiMC/MultiMC5.) MultiMC successfully builds if you set the version to develop: Attempt to build MultiMC. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nWould also be fixed by (Edit: only the CMake errors, include patches are probably still necessary)\nProbably best to just patch the release. I'll see if I can do anything about this. I need to fix the desktop file anyway.\nPatching doesn't work, and calling the commit directly results in this. Not sure what to do. If someone does fix this, please include in to fix the desktop file.\nI managed to fix it by using the unstable version, but I'm not sure if that's the right approach. I can make a pull request with that if you'd like.\nIt should be fine, just note that it's a temporary workaround until MultiMC increments a release, since IIRC stable packages aren't generally supposed to be using non-stable repos."}
{"_id":"doc-en-nixpkgs-1a3663c27d0ba2fff8450f2937e178182d6c44c4ddfea6695a46bfc89fdaca7b","title":"","text":"in secret management was redone for bookstack. Now I can't place a mail password as secret. It's also appended with : Please run and paste the result.\nOh, sorry about that. I can't see any obvious culprit in the code and I really don't know where came from. Can you paste the service script as it's been rendered? Can you paste a configuration that reproduces this?\nOh, I suppose this could happen if the mail password file path is a superset of the app key file path. Is that the case?\nI've submitted a fix for you to test: . I hope it solves this issue."}
{"_id":"doc-en-nixpkgs-e5c923abd9f7a1e914a3cc496cec0a530030e15630b0b06ead1bbeb5f1789d40","title":"","text":"Describe the bug executing terminates with an error. This didn't happen with idris2 Version 0.3. To Reproduce See above and below. Expected behavior The REPL should successfully start and present its own prompt Additional context Notify maintainers Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:\nCould you try setting ? In particular, they should be set here:\nThe library paths mismatch.\nHey, your seems to be empty. :O This is what my recent install () looks like:\nhuh, why does it seems empty, it clearly contains stuff?\nAh sorry, I misread the columns then.\nCan you compile and run execs?\nsuggestion:\nwhen I manually adjust the library paths to include the version, it works:\nRun with\nWill apply, though I am now concerned about the different behavior in NixOS, so maybe I am getting the libs from somewhere else DX"}
{"_id":"doc-en-nixpkgs-bab8916f2b888ed4f2e50911696e54549d2e03591fdfd16c93490027312ec267","title":"","text":"Rebooting a NixOS instance on ec2 does not resize the root volume even though Created one of the amazon ec2 instances: nixos-17.03.885.-x86_64-hvm-ebs Resize the ebs volume associated with the instance using the aws console. Reboot the instance. View to see that nothing has changed view Find this in the error logs: System: (Hummingbird) Nix version: nix-env (Nix) 1.11.11 Nixpkgs version: \"17.03.885.\" Sandboxing enabled: build-use-sandbox = false"}
{"_id":"doc-en-nixpkgs-3a49cbd6e31b24a90e1488deb65444327f4b8c98de37b5020a366740349c4b7e","title":"","text":"this commit makes my NVIDIA GeForce RTX 3090 no longer visible to ollama: needs to be revisited, or add optional flag to disable hardening (which i don't really need since I dont expose ollama over internet). when running through systemd: when running :\nCan you check , and try adding these strings, prefixed with to ? For me on NixOS 24.05 they show and the module currently allows the following device types:\nJust upgraded to the unstable module and package and things are still looking fine. The only nvidia related config I have is\n, will try later when I get back home. Not sure if related but I'm on nvidia as the newer versions are broken in one way or another (wayland/performance regressions/pytorch issues).\nYou can also try nuking the DevicePolicy altogether if the suggestions above do not work: = { DeviceAllow = lib.mkForce [ ]; DevicePolicy = lib.mkForce \"auto\"; };\nwas the missing piece: +\n--------+ |-----------------------------------------+----------------------+----------------------+ +-----------------------------------------+----------------------+----------------------+\nthanks for your support!\nFeel free to send a PR to add it to the module. Thanks for looking into this!\nsome additional findings, nvidia device group names are definitely driver version dependent, this is what I get on 555 ( is gone):"}
{"_id":"doc-en-nixpkgs-5396b953eca10e76a7524c412430d26968e74eefda5cfeb9c0ffec8978197aeb","title":"","text":"Electron is a security-critical component for several desktop applications and we shouldn't be keeping EOL versions around. Please remove all versions older than 18 if possible. The latest version is 21. via cc\nThere are at least 14 packages that require Electron < 18, should we drop them as well? Isn't it better to just mark Electron < 18 packages as insecure via ?\nThat is a start, ideally we could move those packages off older Electron versions, but I don't know how feasible that is."}
{"_id":"doc-en-nixpkgs-a599fb65bfdd0e72c4ea9134d18098afe43a5a14a3379ceeff89eeb4c3975372","title":"","text":"After the recent update of nixos-23.05 from to (which included , updating Firefox from 119.0.1 to 120.0) Firefox started crashing, apparently when WebGL gets used. Steps to reproduce the behavior: 120.0 with a clean profile. a crash. Some crash reports: https://crash- https://crash- These crash reports point to , which shows a matching backtrace: The underlying problem might be somewhat different though, because the offending option is not present in any Hydra build logs ( is present though). system: host os: multi-user?: sandbox: version: nixpkgs:\nYou can disable WebGL temporarily while the bug is being fixed. about:config webgl.disabled set to true\nalso works without crashing even with WebGL enabled.\nHydra build log: This is the same root cause as described in (originally for Ubuntu Firefox Beta PPA for 18.04 LTS). This is caused by building in such a way that and (and ) embed and export their own version of the code from libstdc++ (in particular ) instead of using dynamic linking to call into the code that is exported by . It is unsafe to do that because of the flag that is used to compile these binaries, and starting with Firefox 120 that results in a WebGL crash. For the Ubuntu Firefox Beta PPA this was caused by compiling with but we do not understand why this situation occurs for the NixOS 23.05 build at the moment. But it does occur (see screenshot below). <img width=\"399\" alt=\"Commands showing that indeed firefox, and all export std::locale::Sinitialize with this build\" src=\"\"If someone knows how to ensure that and (and ) do not embed and export code for , that should fix the crash (we should not see a for when using on these binaries, in fact we should not see it at all because this function is internal to the implementation).\nAlso apparently the problem is specific to the branch:\nComparing the “good” build log () with the “bad” one () shows the difference in clang versions (and the extra option for the build, which uses clang-15): And the difference is indeed in the compiler behavior."}
{"_id":"doc-en-nixpkgs-7e342c0ddb6e14e09e556b17ec3c8483d0c4f56ee9f7b5c47ded749df99c18e7","title":"","text":"Using the test file from the Mozilla bug report: With the new compiler from : With the old compiler from : Apparently the important difference here is that the compiler from passes the option to , and the directory contains , therefore the linker uses the definitions from the shared library as intended. However, the compiler from passes the option, which refers to a nonexistent directory ( actually exists, and there is the symlink, but these directories are not mentioned in the parameters), therefore the linker does not see and uses only from , so the resulting shared library contains copies of all libstdc++ functions, which breaks things when is also specified. So apparently the real problem is that in the branch uses wrong library paths for the GCC libraries.\nI'm currently building with the following patch, thanks to trofi. This approach fails, as it overrwrites all previously accumulated flags. This was apparently fixed on master in\nThis will most likely be resolved through , but I'm still testing a solution that would be more localized to firefox and thus arrive quicker.\nThe workaround is part of the latest release-23.05 evaluation. You can follow its progress here:"}
{"_id":"doc-en-nixpkgs-2e6971d0083b09c096aa32dc9e54777743a9b1f9a68972064269bff531ec05e7","title":"","text":", CVSSv3=9.8 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives.\nmerged\nNeed to keep open for 20.09\nMerged to 20.09 too. Closing."}
{"_id":"doc-en-nixpkgs-d40186c38e4d7385647d282493e750befac8452b805caa50c39133ec2d6e1622","title":"","text":"Describe the bug /dev/fuse isn't user read/writable To Reproduce Expected behavior Additional context I've been testing with and : Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nAfter further testing, I found that reverting fixes the issue. I'm guessing that this new file needs to be installed somewhere. CCing maintainers of systemd:\nThere are even more tmpfiles configs that we're not using. I'll check what applies to us and prepare a PR.\nIt would be cool if there was a test for the permissions.\nI have the same issue with /dev/fuse for can't mount remote sshfs as user only as root la /dev/fuse 10.6s crw------- 1 root root 10, 229 Sep 23 14:36 /dev/fuse ~sshfs user ~/sshfs/ fuse: failed to open /dev/fuse: Permission denied Any fix we can expect soon?\nSeems permissions is associated with systemd /etc/static/systemd/system/kmod-static-nodes.service\napparently that broke permissions for me, which are needed for\nStrangely, on my 19.09 system does have 666 permission, despite containing a line .\nI think the permission is automatically set to 666 by udev rules when the fuse module is loaded.\nIn my system on 19.09pre channel I have this issue manifesting in kbfsmount failing with a permission error. crw------- 1 root root 10, 229 Sep 23 21:48 /dev/fuse"}
{"_id":"doc-en-nixpkgs-9094011f0db5c3c7fa214d5fd52c142e265fa1a795639f29e6ebc3e29b7e4ee2","title":"","text":"is currently using this command creates the temporary directory inside the current working directory instead of in . This can cause the generated directory to be included in the final package, as I'm assuming accidentally picked it up. I encountered this while working on and The temporary directory is not included in the output use use (output is of the format ) note: this isn't really used across nixpkgs use something else <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8e1deabc04a41b7429a65a8e8a0eaca30ea7954c9f0cfe39ea04c2264c58bdcb","title":"","text":"Steps to reproduce the behavior: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nHydra can reproduce:\nI tracked down the potential source of this failure, and am working on a fix. These builds take 30 minutes for me though, so it's slow going.\nPlease see for a fix. Testing appreciated.\nThanks for the quick patch. EDIT: My way of installing to profile didn't pull the fix, I'll see if I can figure out a way to do it properly using the pr review package\nBuilds and runs... seg faults as soon as I load a model, but that's an AMD driver thing (whole WM crashes)... Ship it :laughing:\nI did see some segfaults, but was able to restart and get it to load on my 6700xt. “Glad” to know it’s known and common.\nNice! Thanks for this - excited to see it roll into unstable soon. Ollama seems to always have some issue - is there a \"working group\" that has some focus on this program and nix? Anyway, thanks again!\nThe problems with crashing aren't nix problems, they're crappy amd driver issues. It doesn't crash if you don't load models close to the max vram available... obviously it shouldn't crash if you do, but amd... so yeah"}
{"_id":"doc-en-nixpkgs-ea44bad297dc46b26528015d1242b18aabf802bcdebe5fa7c370f5c2442f48f7","title":"","text":"Steps to reproduce the behavior: cmus on current (). Full logs: I haven't updated in a while, so I'm not sure where this failure starts. Nothing has changed in the cmus package; it must be a change in dependencies. system: host os: multi-user?: sandbox: version: channels(root): channels(jamesw): nixpkgs:\ncmus started failing somewhere between (good) and (bad). I don't have the hundreds of gigabytes of RAM that would allow me to do a bisection between those, so I'll leave that to someone else.\nManually going through it suggests as a possible culprit. I have no idea what that commit does, though, yet.\nthe issue is bump of ffmpeg to 6, i am about to push a fix"}
{"_id":"doc-en-nixpkgs-1732262b95f67479134acad5f8ec4963bd7e57ee329f398ede69671136cb243b","title":"","text":"Project description DevSpace is an open-source developer tool for Kubernetes that lets you develop and deploy cloud-native software faster. Metadata homepage URL: source URL: license: apache2 platforms: linux, darwin"}
{"_id":"doc-en-nixpkgs-12a321d4150119c3fc21835b7dddf7c14ab01af03bc6b146a1937f519c675f9e","title":"","text":"Steps to reproduce the behavior: nixpkgs electrum was recently updated 4.3.1 -4.3.2: previously built fine on nixpkgs 2022-09-28 () <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --<!-- attempting ti bisect, but on a slow machine, and it looks like there's miscellaneous failures over this duration so not sure it'll bisect cleanly: --\nbisected to: good: bad: that's the staging-next merge though, so a lot of surface area. however, we appear to address a very similar build failure over in pkgs/development/python- by doing: i'm not sure how to test this same patch on electrum since it doesn't have any file.\noh just kidding, Electrum just places its in a different location. the patch below fixes the build when applied to master, and the application starts but i didn't test any functionality that i know touches protobuf. not sure how concerned i should be about overriding a pinned dep (i'm not a python dev):\nFix in"}
{"_id":"doc-en-nixpkgs-98b2863848dbd29922d8ea03cac475162a1261f7758ec810b4964672214de5c3","title":"","text":"A clear and concise description of what the bug is. Steps to reproduce the behavior: build github:nixos/nixpkgs/nixos-unstable#legacyPackages.x86_64- Nix builds the derivation. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Maintainer information:"}
{"_id":"doc-en-nixpkgs-d37f704de91e5bdc47017959e67b3c43f96b51345e18545d34f070843c8e5f7a","title":"","text":"Possibly a regression after CC <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nLog The clue is in this log line Odd that we'd be copying something to a derivation ending in , right? Let's investigate further. is one of the CUDA redistributables, so I know it's built by the manifest builder. Looking it over, we can see the relevant portion of the : Well, that looks about right, but what is it actually rendered as when building? Uh oh. Yeah, that's right -- we're missing a newline character! Turns out using the multiline string literal doesn't mean we get a leading newline character (which makes sense given that we concatenate them everywhere and we're not drowning in empty lines). With just a small patch Our is what we would expect: And the resulting build contains our binaries! More generally, the problem likely caused the last, non-, output to disappear.\nWill be\nI suppose it wouldn't be unfair to say that this is an instance of the \"we've stringified our data and failed to parse it again\" issue?\nI think that’s fair to say. As I view it, the actual build is always done by a bash script. We can either write it entirely in bash, or template it (like we do currently). Both come with tradeoffs. In my opinion, the boost we get in expressivity from lifting some parts of the build up into Nix expressions (so we can use attribute sets and functions in the library) outweigh the cost of making sure we’re producing well-formed bash. Although, that does fall apart sometimes (like here, where we were missing a new line). I’ve not tried to rewrite the install phase as a static bash script which leverages structured attributes, but I do wonder if it would have been as easy to debug? At least with the approach of using Nix as a templating language for bash we can use nix eval on the install phase to see the result. thoughts?\nYea we can also use to peek at the attributes that would go into the JSON, and then maybe there's less bash to read"}
{"_id":"doc-en-nixpkgs-d2c98ee2983654da39ba834eb04a89eb24c030a12542aef87e8fd8310551360b","title":"","text":"Package name: libjson-rpc-cpp Latest released version: 1.3.0 <!-- Search your package here: --- Current version on the unstable channel: 1.3.0 Current version on the stable/release channel: 1.3.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers no maintainers :< <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-5b6446c3ff21465dfc7ee0cdb992ef905bf56c7d5a1d902c78f7e366d2776557","title":"","text":"Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tag:\nLooks like another gcc11 issue. would you mind taking a look?"}
{"_id":"doc-en-nixpkgs-6c61cf361f813d54f9afccb8a30f893b0c1176d47f31f3509d3e0c2b0e97ad20","title":"","text":"First release in three years. <!-- 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: <!-- 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: 1.6.4 desired version: 1.8.0 <!-- 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.\ncc who might be able to help with building the extension from source"}
{"_id":"doc-en-nixpkgs-9932a2175ff4c2f98fd49eff883ad1848737c343cce0e643df1ed56402cea930","title":"","text":"Describe the bug It seems you can't disable GDM's auto suspend behaviour. Disable has no effect. To Reproduce laptop will auto suspend after timeout Expected behavior Suppress auto suspend. Additional context Follow up from Notify maintainers Metadata\nI'm on Wayland if that matters.\nI believe it only touches the dconf profile in gdm, and sets these settings You probably still have those set in your actual session. See the OP of for more details.\nThough I could be misremembering things\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nNot sure if it will work yet, but I ran these commands to make my settings match the autosuspend = false settings:\nAfter making these changes, it still suspended. Then I killed , and since it has restarted it has not auto suspended. I'm not sure if this is the simplest thing, but what worked for me was: set , rebuild NixOS Kill so it restarts\nreturns nothing for me on unstable. I have set to false and it still suspends. (I not 100% sure this is caused by gdm).\nWell, it started auto-suspending for me again, even with the above settings.\nI'm trying this now:\nSeems to be working!\nIn my case it was xorg, not gdm at all. I disabled screensaver and autosuspend with:\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nWow, it's 2023, and this still appears to be the solution To clarify I actually did the suggestion in here, which has an additional line\nI vote to reopen this. The fix is easy to configure, but difficult to understand.\nIt seems like \"don't suspend my system, i'm running this as a server\" should just be a single config option"}
{"_id":"doc-en-nixpkgs-7b21ebae16aa4ca48c794aa328740289eae3a7f2400abd88d9c48ab7ebeedc8e","title":"","text":"Describe the bug The unifi controller has dropped a present in my : Seeing as Unifi support has asked me about \"temp\", the \"device tab\", and my network topology, I'm not holding out on getting a good answer as to what it's doing. Short of that, I'd like to prevent it from having any access anywhere except a single temp, non-executable location managed by systemd.\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-a40813bf91b8c1f62e4e8eff1d615a0a0864c99625c705cf9ee7fe56b99cb09b","title":"","text":"When the service starts, the following message is printed to the logs: sshguard[]: sshg-fw-ipset: Could not initialize firewall Blocking does not actually work. Blocked hosts can still initialize ssh connections. Default sshguard config. system: host os: multi-user?: sandbox: version: channels(root): channels(XXXX): nixpkgs:\nIt seems like that is due to ipsets being created of different types than intended. I'm not sure where it's getting created with that though: # ipset -L Name: sshguard4 Type: hash:ip Revision: 4 Header: family inet hashsize 1024 maxelem Size in memory: 88 References: 1 Number of entries: 0 Members: Name: sshguard6 Type: hash:ip Revision: 4 Header: family inet6 hashsize 1024 maxelem Size in memory: 104 References: 2 Number of entries: 0 Members: Whereas the script intends to create types which is why it returns with an error. I do not see where in the sshguard is type of ipset getting created. I came across though."}
{"_id":"doc-en-nixpkgs-ab03ee43beb66e9fb5a846787cd2ca28c4c41eaae8c63b8e2fd216eeea6b412f","title":"","text":"firefox package is missing its icon in the KDE4 menu whatever its called today.\nAny update on this issue? Is it a license problem?\nTry firefoxWrapper."}
{"_id":"doc-en-nixpkgs-13992677115d29aa99dff79006759715e99c2dbb61095e2283c06b21afe870a6","title":"","text":"Nixos build error when using a MQTT sensor, following . being the channel. The corresponding line seems to have been removed in : which is the commit for the update to . Maybe the code has changed and the python script no longer recognises sensors correctly ? system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nThe configuration you listed above does not yield an evaluation error. I have verified that by building it myself. You must have specified somewhere else.\nI don't have any other mention of in my config, although I have also configured an external mqtt brocker with which might change the evaluation. I can confirm that when I remove the sensor config, the evaluation error goes away, which is why I didn't think I needed to include the brocker config. Those are the only mention of in my config I promise! Still it's strange that the line was removed from no ?\nI've just noticed now that I have forgotten in my config... Here is the actual pieces of relevant config:\nThat's the default. No need to include it. After all, I was able to reproduce your error by building NixOS from the stable channel. My bad. It's caused by the following line: which will use the from the stable package. However, if I set I get which I still have to investigate.\nI really have no idea what's going on. The way I test this is by having a file with the following content: and a checkout of the branch with the following diff at : When building the configuration I get What's strange is that there is no error when points to the branch with the diff applied. Maybe or have a clue.\nI am happy you could reproduce this! Still, I don't see any line for in the (but I see it in the ), which I think it will lead to problems when it will be merged, no ? What I still find strange, is that the referred file in my original error is from ... Is this making any sense ?\nYes, this makes sense: The module is taking the list of from the stable channel and passing those used in your config to the package from the unstable channel, which obviously can't find the component since it's no longer in .\nOk, thank you for your explanations, I understand where the error comes from now !"}
{"_id":"doc-en-nixpkgs-f5f3d0566204e6872e831605dd430d587077925911ab2f5cc5e43a3ff59536e6","title":"","text":"I did some digging around to know why the line has disappeared from the with the update. This is what I found out: on the home-assistant repository, the code for the mqtt sensor was moved from the to between and this means that the is now in the When I define a mqtt sensor in my nixos config, will the nixos module be able to do the conversion from to (I don't fully understand the code in the nixos module, especially the code) ?\nNot yet. I will implement that once I was able to solve the stack overflow issue.\nThe problem should be solved once you upgrade your system since is now in the channel. Can you please try again?\nI can confirm that I don't have the build error anymore, thank you ! However, the home-assistant environment is missing component dependencies. Same as stated previously, home-assistant code has been refactored, but config is the same, which means that dependencies are not found. For example, I have declared in config, but dependencies are at the key.\nAdjusting the code for is on my TODO list. For now, please override the package's .\nOk, at the moment, I am using manual config because I am testing home-assistant, using and the automation editor, so I have manually set the . Do you think we could add a package (something like ) which would have all possible dependencies (the idea being that I would also be built by hydra) - a little like the docker/distro image that distributes ?\nSure, no problem. However, I suscpect that will often not build due to some Python packages not building. Do you want to make a PR or should I do it?\nI can surely try, but I am not sure how I should proceed : I define a new option for package that populates to all packages referenced in should I call the package with all packages referenced in (in a new file next to ), and call it in a new in . Which option do you think is best ?\nI guess the first option comes close to the best one. However, please don't use for that but directly add the packages to . Maybe we could also add a few lines to to add a list of all packages to so that we don't go through all components to generate that list."}
{"_id":"doc-en-nixpkgs-69568eadcc8d60dc3f808812eb03d0e5b5e72b07cfae76935f7a5d3f41780599","title":"","text":"NixOS's wrappers for gcc also apply for gcj, which is a Java compiler. The wrappers add the flag to gcj's command line, however the Java language does not have a preprocessor, and means a different thing for gcj. This means that gcj cannot compile anything. Another issue is that gcj links to zlib by default, but does not pull zlib into the environment. This means that, even if the former issue is silenced with , compilation still wouldn't work.\nA similar problem for gfortran:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-e47cc6740662ed2d91a1e4b4a195e29476303394f8bd94c58050df5e5750794e","title":"","text":", CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc\nCVE-2020- doesn't seem to have a patch yet. The rest (for all mentioned branches) is going to be addressed in ."}
{"_id":"doc-en-nixpkgs-ae3f04bb4cb14c1a82327198737842dd37c8465a326ccd9bf16174e91bcd4920","title":"","text":"Package name: matrix-synapse Latest released version: v1.113.0 <!-- Search your package here: --- Current version on the unstable channel: 1.112.0 Current version on the stable/release channel: 1.112.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-635c3c247502f50bd7e1ebde54e2e682ff5c72948654f1a86fef996ba69c4193","title":"","text":"Minor cosmetic issue: when using kpcli, the prompt shown to the user says \".kpcli-wrapped:/\" instead of the usual \"kpcli:/\". system: host os: multi-user?: sandbox: version: channels(delroth): channels(root): nixpkgs:\nUsually this can be fixed with the --argv0 flag:\nkpcli uses wrapProgram which already sets --argv0 correctly AFAICT. Looks like this is a kpcli specific problem:\nOK, I understand the reason why --argv0 did not work now. Since this is an interpreted script, we are indeed setting Perl's argv[0] to the right value, but within Perl 0) - Sent to just wrap the script manually and thus control the basename of the wrapped script.\nFixed in"}
{"_id":"doc-en-nixpkgs-d5c67d51b640f1d448c36ff8a256749572000fafab2cd1d86f25646c6748818e","title":"","text":"Describe the bug clones each submodule in sequence instead of in parallel, which is unnecessarily slow for repos that have a lot of submodules (such as which has 64 direct submodules). At first I thought this was because git's setting defaults to , but it turns out doesn't even use that, it instead recursively clones the submodules by hand. it looks like you this 10 years ago; is there any reason we can't just use today? I don't know why it doesn't just use git's built-in submodule handling, doing so would make fixing this trivial. Parallelizing the manual clone loop seems a lot more complicated (especially because of the problem of mixed output). To Reproduce Steps to reproduce the behavior: from scratch. (Edit: was recently updated to not use submodules anymore. This can be reproduced using an older version) Expected behavior It should clone the repo in a reasonable amount of time. Notify maintainers Last few changes to were and Metadata system: host os: multi-user?: sandbox: version: channels(lily): nixpkgs: Maintainer information:\nI marked this as stale due to inactivity. &rarr;\nSee\nSimplified in"}
{"_id":"doc-en-nixpkgs-93db852914e88c8db82feb5bd13dfb25b8c89cfd349e5bf99f32f53eba81163e","title":"","text":"Steps to reproduce the behavior: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nRelevant issue on the upstream repository:"}
{"_id":"doc-en-nixpkgs-969f85afd78ca0fa0455a0cc5c6b18825b95597ab6d2d7ff8872c4f323c9e7c8","title":"","text":"Project description A system for automatically configuring mutt and isync with a simple interface and safe passwords Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-7e8233d1ddec0f15df2717cfb3a33fe73ce2a2a733dc18f66ccf6e35e6819338","title":"","text":"Project description Journalist is an RSS aggregator that can sync subscriptions and read/unread items across multiple clients without requiring a special client-side integration. Clients can use Journalist by simply subscribing to its personalized RSS feed. Metadata homepage URL: source URL: license: gpl3 platforms: linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nplease test"}
{"_id":"doc-en-nixpkgs-89fece91aca33e358c9f28f57e31ee7c968369234dcf3761f46fba5e5d0d8f89","title":"","text":"Creating fixes this. Remove and restart . system: host os: multi-user?: sandbox: version: channels(michael): channels(root): nixpkgs:\nMaybe we need to add something to the systemd service to ensure this is created?\nSee"}
{"_id":"doc-en-nixpkgs-558cd5cb2fecb24e67d4a530b7db2b2dc1041d0cfc25536a90132233e93a8c9e","title":"","text":"See also Steps to reproduce the behavior: This is such as basic cross-compilation that I wonder whether something is wrong in my setup. However, the errors are surprising, because I thought most packages were cross-compilation aware enough to not run host binaries on the build platform. Please run and paste the result.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nwas mentioned as a possible fix.\nI can confirm that fixes this issue."}
{"_id":"doc-en-nixpkgs-a9e15db1dded80f4e29764455c3dc16523b452baa397d68ce8d5ec0ba4aefd1a","title":"","text":", (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.\nNo upstream release so far. Applying will probably be OK, but I don't feel confident enough to do that \"backport\".\nI do :-)"}
{"_id":"doc-en-nixpkgs-a5cb55979aaad6ca1c5ef6039daf1748d3b94d98a6cb7f5a6056687327cea9e7","title":"","text":"I used Genymotion for a long time on macOS but with Virtualbox. I switch to Linux/nixOS about 5 months ago and was pleasantly surprised to read Genymotion now supported the QEMU engine. Alas, myself and a few other of my friends were never able to get Genymotion to work using QEMU, which is the preferred Hypervisor. I've tried to source some help at but to no avail. Steps to reproduce the behavior: a running working QEMU installation. Presumably with at least 1 functional VM too Genymotion Genymotion, ensure QEMU is selected as the Hypervisor a random Android device, add it and run it. 'll first get a 'can't start virtual device' error trying to start the Android device again gives a 'Another QEMU process appears to be using the same resources' error I'd expect Genymotion to start the Android device using QEMU, naturally If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: ! !\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\n! !\nDuplicate of . Does the workaround in work for you?\nI'm not really sure this is a duplicate but that's up to you. I'm not a coder so had no idea what to do with that old 'work-around' either. I had a colleague who kindly looked at it, spent some time, and turned it in to a flake which can be found at And now the broken Genymotion functions great with QEMU. Perhaps the flake code can help in fixing the package. Thanks for the pointer to the old work-around"}
{"_id":"doc-en-nixpkgs-ad7e0fd3f1e33008640f0a19fe9a478cdf82e391b12df252f4cf4516d23daead","title":"","text":"Steps to reproduce the behavior: ... ... ... A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.\nHey have you ever made Genymotion work under Wayland ? For instance, on any other distribution ? I'm not sure the support for Wayland has dropped quite officially for Genymotion or I might be wrong, maybe there is no need since it's a QT based graphic interface and platform plugins do exist for Wayland nowadays. EDIT: To add more information, on ArchLinux, here is what I'm getting as an error you might want to share your exact genymotion logs I'm running Sway and I have the following env variables set : QTQPAPLATFORMTHEME=\"qt5ct\" QTQPAPLATFORM=wayland #QTWAYLANDFORCEDPI=physical #QTWAYLANDDISABLEWINDOWDECORATION=1 XDGSESSIONTYPE=wayland XDGSESSIONDESKTOP=sway XDGCURRENTDESKTOP=sway\nOkay so I made it work on my end but I'm not under NixOS/not using Genymotion installed from Nix, try\nI have run with , but still get error. and this is the QT relate envs and this is XDG relate envs\nCould you give a try and use every single platform listed here :\nAlso please share your genymotion logs, there might be more to the error in there And finally, please let us know your exact Desktop Environnement, Wayland is being used, I suppose.\nOne more thing, could you retry using xcb as a platform after having installed in the environnement ? EDIT : Also set So to sum up run :\nI am using wayland + plasma, so I think the dependencies is ok and this is\nThis may not fix your issue, but try it with this : ! EDIT: Also are you running with an Nvidia GPU or not Wayland ? If yes, you should try everything related as well."}
{"_id":"doc-en-nixpkgs-adcef89bb3076e9a3f54ee31d9892306ef472bd028ad4440a15a90c13bb80771","title":"","text":"EDIT2: I've found this so I believe it should work, but something may be wrong, I may need to look at the Nix definition of the package and compare with the way it is packaged for ArchLinux and see if there is anything that could explain what's going on. ! There could be also issues regarding Wayland + Plasma : If you could try another desktop environment, maybe Sway if possible, if you cannot, I will give this a try in a VM under the latest NixOS when I have some time.\nSee this commit too this maybe a fix, that you don't have yet, maybe you have it already because it's been backported.\nCould you please the run of the command ? And uploads the logs to a GitHub Gist. If you can't or are busy, let me know, I'll try to reproduce inside a VM and investigate.\nThis is the log\nI know what causes this problem, because I have different qt version, so I have to add to , and it works for me, thanks for your patience and help\nShould I make a PR?\nHm I'm not familiar with the process but I believe you should make a PR if you can or maybe let's tag the maintainer of Genymotion here ? I believe it is\nLet's wait a week or 2, if he answers back and can make the PR then you can wait to close this issue once the PR gets merged.\nStill relevant. Genymotion tries to load some Qt plugins from nixpkgs and fails for whatever reason. I was able to workaround it by doing . used to work before too but is failing now (and it's unclear why, since its effects are similar to , I guess genymotion still picks something from env vars besides plugins)\nHi! I'm there is seems no this issue on unstable, but I've found another one - Can't start virtual device: qemu libpixmin not found. Here is log: Should I create another issue?\nThat's weird, I believe you should open a new issue yes however I'm not sure if including as a dependency in the derivation of might fix your issue : Running outputs :\nas the maintainer of genymotion's package in Nixpkgs any advice/idea, what's going wrong ?\nSeems like you were trying to launch genymotion with qemu instead of virtualbox."}
{"_id":"doc-en-nixpkgs-c774cd1b27eef7a34b5f620f8e2127370d295eb2932ffafbb65e53c9f21b9234","title":"","text":"A while ago I managed to make qemu version working (at least on my machine) by adding some bloaty dependencies: I didn't test it on latest unstable, but you could give it a shot. It also workarounds that Qt issue via in wrapper."}
{"_id":"doc-en-nixpkgs-5e4e068b90548fecefbeb2f14bbb3fc5b74c2e00d6693d1b1a0d83e2f3255101","title":"","text":"Describe the bug The static build of is broken. To Reproduce Steps to reproduce the behavior: Expected behavior It builds. Screenshots See log output. Additional context In the version was bumped but the patch was not adjusted. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (+ author of ?) Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-64f477d94eaff6d41ca22b86a5ce4e64f70b8160415379725713fdb5d0d44431","title":"","text":"Project description Tana is an outliner, a note-taking application that sits between Roam Research and Notion. It's a great up and coming productivity platform, with a unique feature called Supertags. Supertags are basically templates you can graft on to tags. They currently have a deb and a RPM, but as it's a closed source application, the source is not available. Metadata homepage URL: source URL: license: Proprietary platforms: Linux (Deb and RPM), windows, mac Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI have it working locally, need to clean up some stuff and then will create the PR! I still have to figure out the license they're using (for the metadata)\nThat's amazing! I'm so happy thank you so much!"}
{"_id":"doc-en-nixpkgs-ddfb1ce6a6a1be561cf8868e18b77a22c28133e7f8f4faf1c6e491725d6393b2","title":"","text":"icoutils' extresso missing perl dependencies. install pkgs.icoutils and execute \"extresso\" in shell. This works(): NixOS 16.03"}
{"_id":"doc-en-nixpkgs-300cbb98e17004bc6d5d09fa49a9f7faf5d78b65aebb6ef136b765505986e328","title":"","text":"Steps to reproduce the behavior: oh-my-posh package as part of a system flake on nixos-unstable branch broke today, however most recent working commit I have found is: which is obviously confusing package author says not their issue, but also says the package is out of date as they are on 19.5.2 and the package is on 18.26.1 My system config is: Dont judge im kinda new I havent worked on secrets yet so I just dont have any secrets in it\nLooks like an update PR is in progress that'll probably fix it:"}
{"_id":"doc-en-nixpkgs-920c6f2bff6e5eb39702ef31ea5a0b0478a3e1e0ebc276a4512dbc75096dc972","title":"","text":"In latest version of Adw-gtk3, window title bar on Electron-based app be weird transparent Steps to reproduce the behavior: Adw-gtk3 to latest version (from Nixpkgs) it as usual Electron based app title bar be weird transparent It looks as usual I show screenshots from my installed Electron-based apps, VS Code & YouTube Music by th-ch ! ! I haven't idea sources of this bugs <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nBased on upstream issue, it needs GTK 4.16 for v5.4 version. I wish it can solved soon as possible\nThis for Gnome 47 needs to merge first.\n!\nMaybe we could just revert and update it again once GNOME 47 is merged?\nI override it on my configurations and it works properly"}
{"_id":"doc-en-nixpkgs-3a917d45b3b73bb74736cbbd17e4d463dbd9444403f29ad3c0012679e825b1c4","title":"","text":"Apparmour service doesn't reload correctly after a system switch. Steps to reproduce the behavior: anything in config with apparmor enabled nixos-rebuild switch error of apparmor service failing to restart No error, apparmor starting as it should Here my service log: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI'm encountering the exact same error here.\nSame issue here\nSame for the issues after . However do a after that just fine.\nSomeone once told me that the state of AA in NixOS wasn't great. But I don't know first hand. Could be wrong. I lack any knowledge at all to even figure out the root cause of the issue. :/\nAA seems to work fine in general. Just the service restart after a nixos-rebuild doesn't work.\nTested just now on nixos-23.11. AppArmor service restarts without any issues after nixos-rebuild. I think this issue is resolved.\nReopening this issue as unresolved. Currently on 24.05.. and this issue seems to be persisting after a nixos-rebuild: reloading the following units: apparmor.service, dbus.service Job for apparmor.service failed. See \"systemctl status apparmor.service\" and \"journalctl -xeu apparmor.service\" for details.\nI did some more investigation on this. I have one system with a custom apparmor profile and another system with no profiles. On the system I have with a custom apparmor profile, nixos-rebuild works fine. On the other system without any apparmor profiles, nixos-rebuild fails with the message in this bug report. After nixos-rebuild, journalctl reports: In I tried running \"sudo aa-remove-unknown\" from zsh: The error message matches what is in the system log. I think this may be related to the aa-remove-unknown step.\nAs a workaround, adding this to appears to work: After this, the first nixos-rebuild switch will still cause the issue (because the profile is not installed yet). But on the second and subsequent nixos-rebuilds, there is no error message on my system."}
{"_id":"doc-en-nixpkgs-fde57707d03e52a3fefb2624c8d327571366018a3902ecb2ebae265d3178c260","title":"","text":"Can someone else try it and see if it works on their system too? If so, it may help to figure out the proper solution.\nI tried it and it actually rebuilds without error the first time too. Hopefully that helps you or someone else figure out a permanent fix! Many thanks.\nFrom my side the issue seems to be be fixed with the merged fixes. So I will close the issue.\nIf anyone wants to track the merger of the fix :"}
{"_id":"doc-en-nixpkgs-12c94151fb8242195ee0b584fc4faafe8f5252df561d762b046af60807811a43","title":"","text":"the following configuration: guests are started to confirm VM should have automatically started guests marked to start on boot start Guests marked to boot on startup should start doesn't seem to do what it says\nNot stale\nThe problem is that libvirtd is socket-activated on NixOS which it isn't out of the box."}
{"_id":"doc-en-nixpkgs-0b4f66b2958b8b4cc17af835f5c4363c316a9a467aae05aa914ceb448520b11e","title":"","text":"RStudio is missing most of the text from its UI (see screenshots), the text one being displayed is in the top menu bar. Icons are displayed correctly though. or to the environment (for example ) The main interface starts in a new window with version information in the left pane, environment information in the top-right pane, and filesystem overview (with file and folder names and not only a logo to represent them) What I observe: ! Expected (here taken from archlinux's rstudio package) : !\nConfirmed, fixed on my side, thank you!\nI also have this issue and the PR does not solve it... Please let me know what information I can provide to help you in debugging.\nPlease just forget about it : my pinned version was not building the new version that you packaged. Thank you for your help !"}
{"_id":"doc-en-nixpkgs-35e3a95ae05980479eaba39193774cb7b64ebbf3b35c8d4d5575878c56bcce4d","title":"","text":"Describe the bug The current downloads 2 patches, both of them 404. I realized this when I tried to build my system from scratch without substitors. To Reproduce a system that somehow depends on mercurial (not exactly sure if this is reproducible with just or similar, this was also on a content addressed machine, and reproducing the issue in a more isolated way would require another toolchain bootstrap which takes several days) the system from scratch using see errors like this: Expected behavior mercurial builds without errors Screenshots See log output from reproduction. Also ing the URLs as in the derivation linked in the description result in 404. Additional context The exact commit the system was build from is nixos/nixpkgs/, though as the same path URLs are used in nixos/nixpkgs/master, this is probably only partially relevant. Notify maintainers cc Metadata nix shell nixpkgs#nix-info --option trusted-substituters -c nix-info -m system: host os: multi-user?: sandbox: version: channels(nmelzer): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-f3cb88883b03065be3b326c627d084959a2bd8ae6854a81298f2357669bcac20","title":"","text":"When I set in , the rebuild fails as is no longer a valid option. Steps to reproduce the behavior: thrown: The option definition /nix/store/bfg7xzgvbhxhs7vnl7lynaxmjhmvc4j0-' no longer has any effect; please remove it. See the 16.09 release notes for more information. should not fail. - - Please run and paste the result.\nHaving had a look at that module (), IMO it should just be removed. ? really?\nThe module in general looks outdated and incomplete. I share the opinion of either dropping it or actually correcting and finishing it.\nOther question is when you look at the history they removed lsh 7 years ago because it was unmaintained, but then the commit got reverted later?\nThis module doesn't make sense at all. GNU stuff and non-GNU ones usually can't fully replace each other, and it's up to the users to decide which one to use."}
{"_id":"doc-en-nixpkgs-ea98ffda5e048ca9f25674eac8f0d5b1a7795efa91a907519a5bc8e6b4f9dd92","title":"","text":"Please add rust-gdbgui to in the post install script of rustup. rust-gdbgui was recently to the list of proxied tools in rustup. However, the change that's now present in latest master of rustup is not yet part of a tagged release. I'm assuming that updates to a package are only done to tagged releases? I'm also not sure how disruptive updating the is. So, I think this issue cannot be resolved until the next release of rustup. name: rustup current version: 1.24.2 desired version: 1.24.3 (not yet released) maintainers: Please tag this issue in your PR.\nCan you make a pull request? We should wait for a release so.\nSure. I'll make a PR on the next rustup release.\nI marked this as stale due to inactivity. &rarr;\nSee pr"}
{"_id":"doc-en-nixpkgs-32603ce11a58683305f5877ed04b62734c1da3819483f3df2c0a34eca7fc3c64","title":"","text":"Project description Dr. Robotnik's Ring Racers is a kart racing video game originally based on the 3D Sonic the Hedgehog fangame , itself based on a modified version of . Metadata homepage URL: source URL: or license: gpl2+ platforms: linux cc (this is kart v2) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nDone. Test it out and let me know if you encounter any issues :+1:"}
{"_id":"doc-en-nixpkgs-77c035deefe5d1a6090f0d7c5f81991b6761dd0896a048c2e582a644f9fd1aa1","title":"","text":"and fail in this fashion: This seems to have started to happen in December of last year (see ). This effectively means that using the avr toolchain in nixpkgs means re-compiling gcc on every channel update. Not sure what is causing the log size, unfortunately there's no special hydra meta attr to change the log limit. cc Maintainer information:\nFrom doing local rebuilds of this package and noting how much output it gives, the long logs are from echoing back the compiler commands from make when compiling all of the soft float routines for each different AVR chip. It started dumping all this output when we moved from GCC 9 to GCC 10. Looking at the logs prior to that version bump, make must have been quiet because I see no compiler commands getting echoed back. Is it possible to add something like here?\nmay be worth a try:"}
{"_id":"doc-en-nixpkgs-9932846b4493de53c06b7dd13115d49ee4432a8732f3fbd00e5759fb3c2da68f","title":"","text":"Project description Oculante's vision is to be a fast, unobtrusive, portable image viewer with wide image format support, offering image analysis and basic editing tools. Metadata homepage URL: source URL: license: MIT platforms: cross"}
{"_id":"doc-en-nixpkgs-555ed3c35a275fe5145c8e4df08a7838915d92b403c5c7e9d6488221a33c14a6","title":"","text":"When is installed with , works fine. When is installed with , then prints an error message. When installing with , I get this log: So, it might be that git-with-svn-2.6.3 is fine but not . System: NixOS: = () Nix: = Nixpkgs version: () /cc\nI think you have nixpkgs and nixos channel. One might be coming from root. So on one channel it works, on the other it doesn't.\nThis is a bug in the Perl bindings generated as a part of our Subversion build. The library depends on , but it has no RPATH set that allows it to find library. Curiously enough, is the only dependency with that problem: other library like are found properly using a full path into the Nix store. Cc: and\nand it was working fine in :\nAs I said, this as nothing to do with Git. It's that provides broken Perl bindings.\nRan into same problem. git bisect log of checking ldd /nix/store/-subversion-1.9.3/lib/perl5/siteperl//x8664-linux-thread- follows. there's some big binutils related changes in the middle yet."}
{"_id":"doc-en-nixpkgs-4010ec81f9480db79dfcdeeea414e3133ba4a105210f0bc8ae92590c54668cce","title":"","text":"On NixOS 21.05, when setting , I could see the result of this settings by running: Since NixOS 21.11 however, altought the masquerade works, I cannot see anything with iptables commands: As discussed on the Discourse topic , I suspect this is linked to the following change in NixOS 21.11 (PR ): Steps to reproduce the behavior: an interface with on a system running NixOS 21.11 the lack of information about the IP masquerade The IP masquerade should be visible like in NixOS 21.05:\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nActually, this is due to systemd since v248 preferring to use nftables if available, see Systemd does not use the iptables binaries and but a separate library that creates iptables rules directly without translation to nft by iptables-nft. So even without using the legacy iptables tools, these rules in nftables by networkd would not be visible. Other services that need to add firewall rules like libvirtd, docker or podman are likely getting proper nftables support soon and users still using iptables will run into the same issues. Since we are not the only distribution dealing with this, this should either be solved in systemd (can rules be generated that are compatible to and can be parsed by iptables-nft?) or in iptables-nft by displaying a warning that other nftables rules are active. The only related problem remaining in NixOS is that since our module is heavily based around iptables, our users assume NixOS is using iptables when in fact it is using nftables with iptables compatibility. cc\nThis particular issue is also giving me issues running docker on NixOS 21.11 in WSL2 on Windows 10. It requires iptables and the docker service fails to start due to docker trying to issue iptables a command and the nftables reply throws docker as an error. Same configuration using systemd v247 via 21.05 works fine\nWhat you're seeing is directly caused by and has nothing to with this issue since the problem described here is that not all active rules are visible. Are we even supporting WSL officially?"}
{"_id":"doc-en-nixpkgs-dc6f4547535101dac912717ba39c17a7fe271baacc8d399f93a657866de2df11","title":"","text":"You might want to open a separate issue for this if you're interested in seeing support or getting this fixed. We would need to detect if nftables support is available and use the correct iptables package everywhere. Not sure if it's worth it, though.\nthis seems to also cause problems when upgrading systems from before the nftables bump. In my case, these were fixed after a reboot, but it's still a pretty annoying thing, for which we probably should at least make sure there's a release note entry. cc\nHmmh, I'm also a bit baffled about how to interpret defaulting to false. ~It seems and are mutually exclusive, but since we now configure nftables in other places, the firewall module is just broken?~\nIt seems only supports defining all rules exclusively, which doesn't play very nicely together with other things invoking iptables, or managing rules by themselves (like networkd , libvirt and other programs invoking iptables). Maybe that module needs a bit of a re-vamp - with merged we might want to configure most of what the module was doing, except managing the ruleset by default. However, that's a bit offtopic from the original issue.\nyou should see nftable tables when invoking , which is where systemd keeps its nft rules. iptables rules configured with the command are in . I think this is mostly a matter of updating the release notes, and raising awareness, that nftables is used, the command is only managing some tables in the nft system, and that there's more rules than what you can see with . I'll try to come up with a PR updating the release notes in that regard. It might not be possible to translate some nftable rules to a iptables syntax - I'm not sure if logging a warning breaks backwards compat with some tools relying on iptables output…\nI improved the docs in , PTAL. Fixing the nftables module, and using less iptables in the firewall module should probably be left to another PR.\nI opened to track the nftables NixOS module improvements."}
{"_id":"doc-en-nixpkgs-d4ea00f57c0734f771209b7aa82fed685fcd6f7a4aa79b32479e2632362d2f6e","title":"","text":"git package includes which defines functions for shell prompt customization like . Even though the file is included it's not sourced by default and doesn't make the functions available. Steps to reproduce the behavior: package system-wide. one of the functions provided: the file manually: function becomes available: shell function being available out of the box when package installed. Making the prompt functions available when bash completions are enabled seem to have been the original intention of . However one might also argue that the functions should not be sourced by default if someone doesn't use git prompt customisations provided. It could be placed behind an option but I'm not sure it's worth the hassle. cc\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI'm not a maintainer or expert, but I read your linked Discourse thread and your ticket because it sounded interesting. Great analysis and writeup. My interpretation is that was never intended to be sourced automatically when completions are enabled, for two reasons. First, inside of : which is an instruction to source it explicitly. Second, the for says: which leads me to believe that was created so that it can be used independently from bash completion. Prior to its creation, it might have been available automatically as a consequence of completion scripts being loaded eagerly, but that was accidental.\nThanks for digging deeper into this, Theodore! I agree with your conclusion: it does look like the prompt script wasn't intended to be sourced automatically. I think the best way to approach this in NixOS would be to have a option that would enable sourcing of the file.\nI think something like this sounds reasonable. I'm sorry I can't help with it right now, because I haven't set up NixOS yet. (I'm just using nix on my Mac right now.)\nNo worries, thanks for your help so far :) I might eventually give it a shot myself."}
{"_id":"doc-en-nixpkgs-45c97117b609ede32b806ce95e3e99092f69706fce66648c9ad354222496f3a0","title":"","text":"The package fails to build because of missing test dependencies: system: host os: multi-user?: sandbox: version: channels(z0028sn): nixpkgs:\nI jailbroke it and the the tests fail anyway. So it should be set to . succeeds.\nThe problem is that the release tarball on Hackage is incomplete, i.e. the required file appears to be missing. This should be reported upstream () so that they can release a fixed version. Ping:\nThis should be fixed in 0.6.1, which I just uploaded to Hackage. Please tell me (probably on a pure-zlib ticket?) if you have any further problems."}
{"_id":"doc-en-nixpkgs-d32a946575b60ff9b84d1515f755329b20b8706822ea23e2d9016dab2855aea1","title":"","text":"Describe the bug While Nixpkgs provides version 2018-12-14, there are some fixes landed since then. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\ncan please check using with a local chekout of nixpkgs?\nYes, I will. Thank you for your prompt response!\nI did and tried some commands. It seems to work fine and the store size does not grow significantly. Is there anything else to test?"}
{"_id":"doc-en-nixpkgs-c654bed2676bb916e6f3c1f28c8df156f91296e346bfd1f8d4096e00c861739b","title":"","text":"Describe the bug AppImages assume that the gmp library is present on the system, but appimage-run does not include gmp. To Reproduce Steps to reproduce the behavior: +x the appimage Expected behavior The app should run. Additional context I believe it is because of this commit: I fixed it on my end with: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nI marked this as stale due to inactivity. &rarr;\nnot stale\nAlso affected:\nas pointed out by t-paul, appimage specifically assumes GMP is provided by the system"}
{"_id":"doc-en-nixpkgs-fbbb23af0e3dcaeda5bd98674525f007916cb06bc6d4c8e4dbcafd57e1cde2c7","title":"","text":"Describe the bug Building fails with the following messages: Note that points to which updates . To Reproduce Steps to reproduce the behavior: Expected behavior The package is built successfully. Notify maintainers (gfan, cddlib), (cddlib) Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(omasanori): nixpkgs: Maintainer information:\ncddlib put its .h file in <hash-cddlib-0.94l/include/cddlib/ rather than the old version of the library placing it .h headers in the root. <hash-cddlib-0.94j/include/ So options are get upstream to #include \"cddlib/setoper.h\" (and the rest of the directly pathed includes) Patch it in the derivation Take a look at the library is being why it differs from 0.94j to 0.94l ...... and see if can be symlinked (botched). not sure why it's subpathing these .h file now?\nv0.94k header files are now installed to PREFIX/include/cddlib to avoid clashes with other libraries. configuration file for pkg-config : assuming cddlib installed in <prefixknown to pkg-config, \"pkg-config --cflags cddlib\" etc will work. (Otherwise, one would need PKGCONFIGPATH=<prefix/lib/pkgconfig). this is the source of the breakage. this probably breaks everything that uses this library.... lovely! So, options are fix it gfan upstream, or patch it in nix?????? has a 41 length thread, where the developers are trying to workout how not to break any application that uses this library and which distro's they want to break.\nThank you for your survey, The long-term solution would be fixing gfan upstream, given that this is not Nix-specific. The current Makefile assumes that, if cddlib headers are prefixed, the prefix is instead of . A variable to change the prefix will help every package maintainer IMHO. However, adding a patch to gfan just altering with into nixpkg may be fine for now. I will try to address it next week but feel free to make a PR if it is urgent for anyone."}
{"_id":"doc-en-nixpkgs-301228c0b45dcc27122b1b338f6b683701a391df76ad722941d627e925c9d3b4","title":"","text":"Cannot run the git tests because is broken. Steps to reproduce the behavior: The build should work, the git tests should run and pass Please run and paste the result."}
{"_id":"doc-en-nixpkgs-8982b9473e513a1ab33ffd8d8b8d6063a3da275a6b4c40468141ba3c2bd1603e","title":"","text":"Try building\nJust 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:\nExcerpt from : which seems to be the change that breaks , so we probably need to file an upstream issue.\nAs a workaround, something like this should work:\nNote that the downgrade would undo some security fixes; see PR ... which is also why we backported this problem to 22.05.\nI see...I'll wait to re-enable qtile then\nDepending 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.\nHow would you modify the package with a general overlay? Something like this didn't work for me:\nThis 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.\nI 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...\nSomehow, 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."}
{"_id":"doc-en-nixpkgs-a923e82c05e1f4690455a17795733765d23420793e12f31a5c818f385f5fd63a","title":"","text":"Steps to reproduce the behavior: on fails (see ) Happened within CI when building () Will do. Please run and paste the result. Don't know how to run this on the failing CI machine. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-95146365bc24d295ca534e4ca5e7b67a845282633a6eec15dd80167394f1461c","title":"","text":"Whenever is used with vivaldi to set it's binary path into a session variable for example, it produces a big warning stating that the attribute is missing and it will default to package name. a library function that needs the attribute like lib.getExe the vivaldi package as below: rebuild the config: the build process a big warning will appear stating the following: , Do the hint stated in the warning and use it like:"}
{"_id":"doc-en-nixpkgs-a2b2068c3cd2ff758a0b1a91748dadd7f8661da53975bee6732ff8b7b3c8566a","title":"","text":"Awesome Spectral JSON/YAML linter with OpenAPI/AsyncAPI support Spectral is a flexible object linter with out of the box support for OpenAPI v2 and v3, JSON Schema, and AsyncAPI. MIT\nShould be trivial to package using ."}
{"_id":"doc-en-nixpkgs-049f5518a8b3ff5b1480bf558f124ff5cdf1f5eeaf205e7017f56df9333e3ca7","title":"","text":"Describe the bug There is no AWS AMI for NixOS 20.03 To Reproduce Steps to reproduce the behavior: Check or Try find it in AWS AMI console Expected behavior 03 is created and uploaded to AWS\nCC I think knows how to do this part.\nYep, I have no idea how to do this for NixOS, so I'd need someone in the know with AWS AMI for 20.03. This actually was one of my concerns for 20.03.\nI know how to build the release AMI and put it on a personal AWS S3 bucket (I'm using one now for my NixOps AWS cluster), but do not have the permissions to upload it on the official account. about 2 months ago I followed this process, which you can use if you're looking to unblock yourself: then follow these instructions to upload using : Then on NixOps you set to your custom AMI. You can also use this to bake in pkgs to the AMI so there's less startup time if you know you'll be downloading specific things on provisioning startup otherwise."}
{"_id":"doc-en-nixpkgs-c5dd4f443ff21110b6bdab4ac55d9771d60231102848fc17a8743b7b0319cede","title":"","text":"Describe the bug rspamd for aarch64 can't find luajit and fails to build. To Reproduce At the moment of writing, the latest unstable seems to be . Expected behavior Build succeeds Screenshots n/a Additional context Hydra build log: Notify maintainers Metadata Maintainer information:\nI managed to pinpoint the issue to the commit , where rspamd was updated from 2.5 to 2.6. Build log: It looks like rspamd is trying to find LuaJIT, but it's only available in builds. Probable fix would be disabling LuaJIT support in CMake flags.\nSorry, looks like I broke it in PR . I didn't notice the failure, probably because it showed as a grey dot instead of a red cross :x:: I'm not sure why that is, perhaps because it has both a build failure in the output (same one as you see), AND an evaluation failure"}
{"_id":"doc-en-nixpkgs-37f05c5dd7386471f7a0091ac2da7e1c8bce8df73f63eedac8a4ca28bf1c05f5","title":"","text":"<!-- 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: sumneko-lua-language-server <!-- 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.2.3 desired version: 3.4.1 <!-- 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."}
{"_id":"doc-en-nixpkgs-d9b93440d057fda70db6040c46fcd47b63653329e22dc9328af0aa90b695d533","title":"","text":"Steps to reproduce the behavior: textadept (10.8) The error is in building Scintilla <!-- 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."}
{"_id":"doc-en-nixpkgs-ec630da48a9ce0d986a06d4151ae456bf7d0e205b32257a3696187bfb76d72dd","title":"","text":"Hi. So I'm running KDE and whenever I try to launch the AnyDesk application, I get the notification: Launching AnyDesk (Failed) Could not find the program '/nix/store/a1cic900s29g1hfwv731cm3bsgni7p9i-AnyDesk.desktop/bin/anydesk' I have to run from the terminal to open AnyDesk. Please run and paste the result. Content of /run/current-system/sw/share/applications/AnyDesk.desktop: However, that Nix store path only has the desktop file and no binaries. The AnyDesk binary is in ."}
{"_id":"doc-en-nixpkgs-1fe8dfea5da1027c1c228207cabdae9f38d5316ba2f01a1247882b6d69316ddd","title":"","text":"Steps to reproduce the behavior: on darwin aarch64 see Since neomutt is broken on darwin-aarch64. See the CI output: Tangent: is it normal that a failing CI build wasn't marked as a failed check, but rather just ignored? <!-- 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.\nBroken on Darwin x86-64 as well.\nseems to work — I can't tell whether they are running the tests, though, or not. Here are the failing tests.\nLooking at the latest comment on the already closed issue here: This issue could use some love. Neomutt is broken on MacOS and it looks like it's the derivation, not upstream.\nI can't install neomutt on MacOS with home-manager too\nThe failing tests were disabled upstream in . I tried simply upgrading to HEAD with the following patch, and the succeeded (darwin-aarch64):\n( That's a different bug which you should probably raise separately.)\nUnfortunately, the latest fix didn't work for my Intel Mac, some tests are failing for me. I tested using because I didn't know how to do overrides from the CLI\nYes, the failure on should be a separate bug (and could probably be fixed by putting into )."}
{"_id":"doc-en-nixpkgs-2eebf1d8a8cae0ba27ca6e423ae9d3c99632ddf6585f0d366eb97ab3cfaf3a82","title":"","text":"Project description describe the project a little is a highly configurable dashboard for Neovim. It's an alternative to Metadata homepage URL: source URL: license: MIT platforms: Anything that can run Neovim, I would assume"}
{"_id":"doc-en-nixpkgs-e5c5f909cb3c0b7fa4b232b654e7ce8cdb859c97b83f4d2832cf59abb1343bda","title":"","text":"When I click on any program in latte-dock, nothing happens. If I run in a terminal, I get these warnings:\nI figured out the issue is that latte-dock code fails to detect the version of plasma desktop. For that they parse the output of . I made a dirty test with hardcoded value in and which works around the issue. What is the correct solution to have latte-dock detect the version of plasma? Does it not have access to plasmashell path? Also I noticed that the command results in a segfault. Is that an issue?\nSee for more discussion. Would you mind describing how to trigger the issue for a person (such as me) who doesn't use plasma shell nor latte dock and so is unaware of (a) how the thing is supposed to work (b) how to set it up?\nSure. the latte-dock package latte-dock. There will be a in the nix store path/share/applications that should appear in your application launcher. For more verbosity, run will see the default layout for latte-dock appear at the bottom of the screen ! By default it has in my case Firefox, Dolphin, and a clock widget. I don't know if it will show your default browser and file manager instead. will auto-hide if a windows covers its area. app that you open should also appear there (eg. a terminal emulator) on an icon of an app that is not already open should open a new instance on an icon of an app that is already open should show that windows if there is only one. If there are more than one, it should show an option to chose the window. At point 6 or 7 in NixOS currently nothing happens and we get in the log which is due to in latte-dock (see )\nCurious. I can't reproduce this. Could you try cleaning latte-dock qml cache () and trying again? [aroun plasmashell -v plasmashell 5.26.4 Segmentation fault (core dumped) Can't reproduce this either with Plasma 5.27.\nWhen running , the issue is still happening for me. The segfault also happens for me in plasma 5.27 on NixOS unstable (inside a VM). !"}
{"_id":"doc-en-nixpkgs-6a9218040f20d6eaddedb930929ee3f543dc0f7c8b58585c90847e2430c685b2","title":"","text":"Which DE are you using? Maybe this happens only in KDE plasma?\nNixOS Unstable () with KDE and Radeon graphics. Ok, this seems like a plasma bug, though very weird. Can you provide a stack trace? Here's the short instruction: Install gdb in your system cp . chmod u+w ./plasmashell open plasmashell in your text editor, scroll to the last line, add gdb into it so that it looks like this: (the hash might be different) run You'll be presented with the gdb repl. Run commands and . If you get a segfault, run . Copy the stack trace and paste it here. Also, having your VM would help.\nThank you for the instructions.\nOh sorry.. i forgot to ask you to run in gdb if you get a segfault. That was actually supposed to give you the stack trace. Updated the instruction above. But from the looks of it, there's something wrong with d-bus in your system and this is a plasma bug, not a latte-dock or nix bug. The best course of action for you would be to create an issue in KDE bug tracker and attack system info, stack trace, and other relevant data.\nHere is the bt Ok I will try to create an issue in the KDE bug tracker. Are you saying that latte-dock works perfectly well on NixOS on your side, in the current state? Can you share your nix config? EDIT: How do I install debug symbols on NixOS?\nAre you saying that latte-dock works perfectly well on NixOS on your side, in the current state? Can you share your nix config? It's pretty generic. I have latte-dock in and KDE installed as per wiki: This has worked with Radeon, Nvidia, and Intel graphics. EDIT: How do I install debug symbols on NixOS? This might be tricky. Here are a couple of relevant links. I haven't tried this myself, mind you. P.S. I use X11 only. Scrolled through this thread and didn't find any mentions of whether you test this with Xorg or Wayland."}
{"_id":"doc-en-nixpkgs-8ba2fe5cb51c83fd23aa86b1323c7cbf2ef648e33cf5e22913fcea3fd5f21abc","title":"","text":"My config is pretty generic too, especially in the VM, I installed NixOS with KDE Plasma, latte-dock in system packages and not much more. I actually switched channel to unstable to try with plasma 5.27, but apart from that I'm basically on default nix config. I did slightly more configuration on my main NixOS install, 22.11, but get same behavior in both cases. Debug symbols seems painful on NixOS. Unsure if I will do that now. Thank you for the help. I use X11 too.\nOk, so after reading the suggested , I enabled and followed the instructions of the option I have and The part for plasma-workspace seems to work fine, but the one for qt5 givers this:\nTo reproduce the bug described in this issue, a simple way is this: the official NixOS virtualbox ova from (22.11.2939. at the date of writing this) it in VirtualBox the vm konsole will segfault will run latte-dock and you will see that clicking on items in the dock does nothing\nI also tried to update the vm to unstable still segfaults, only that the version shown is 5.27.2 still nothing happens when clicking on items in the dock\nAgain, this seems like a Plasma bug, possibly due to VirtualBox video drivers or something."}
{"_id":"doc-en-nixpkgs-97ca71e4a02591c14c2922d635a4eaeeb3bddbab7a3b2985d61b9a6b09ff4a30","title":"","text":"Package name: Latest released version: 0.1.39 <!-- Search your package here: --- Current version on the unstable channel: 0.1.38 Current version on the stable/release channel: 0.1.28 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers (sorry!) Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-9997c54473c62b577ea68a1ffba3eb522378a21818677f95bd8e41518a0bc778","title":"","text":"Describe the bug Size of aarch64 sd_image has suddenly blown up a lot. whereas on commit it was To Reproduce Hydra: - - This blocks the channel ATM.\nIt seems this is caused by my PR here: We switched to , but does not erase the original file, while does. I created PR which hopefully fixes this by passing to ."}
{"_id":"doc-en-nixpkgs-ee58432c3c90ae36be3fbcdf3b7dee3b1d0673e65202927e5483bd6a8a911dfe","title":"","text":"Steps to reproduce the behavior: the package Offending line Seems to me like the darwin framework is missing Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nPosted a PR to fix this:"}
{"_id":"doc-en-nixpkgs-3e51f9970b359b90b3a79c4a7325403fba1678ee80757c5a0a17ad2365a027f6","title":"","text":"The beta derivation depends on a pre-built deb package that no longer exists.\nCC: (I don't have the ability to assign this)\nHey I just needed the fix for myself and therefore figured I could as well push it. Hope you don't mind.\nI don't mind at all! Thank you for doing that."}
{"_id":"doc-en-nixpkgs-0c79d6b46d27fa9fd9c27d03c6723838f9f416aaabb18f693829132618c689d4","title":"","text":"When trying to install Ocenaudio, the installation fails due to a sha256 hash mismatch. Steps to reproduce the behavior: ocenaudio to my NixOS config I expected the program to be installed. <!-- 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. Maintainer information:\nlooks like aur has the same problem this should be reported upstream."}
{"_id":"doc-en-nixpkgs-2f517fa7b7e85f7c3165fa5c7072997ca06ae3fb24339039de8887ac9a048b67","title":"","text":"Package name: lightningcss Latest released version: 1.24.1 <!-- Search your package here: --- Current version on the unstable channel: 1.22.0 Current version on the stable/release channel: 1.24.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers myself, <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Despite being a minor version bump, an entire dependency chain was for NAPI which I think has something to do with WASM which fails the test in Nix. See lightningcss’s open bug on their Microsoft GitHub proprietary issue tracker @ As a non-Rust developer, I have no idea what this error is supposed to mean with its Cargo package management. Hopefully their maintainer will eventually have a look. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [^1] or offering a non-proprietary, non-US-corporate-controlled mirror for this free software project. I wish to delete this Microsoft account in the future, but I need more projects like this to support alternative methods to send patches & contribute.\nBuild error when updating:\nPersonally I’ve stuck with version 1.23.0 since 1.24.0 had a regression for system colors. The upstream maintainer seems to be too busy with other stuff to look into issues.\nshould fix it for further releases. For this particular 1.24.1 release, I a patch to automatically patch the source, see\ngreat work!"}
{"_id":"doc-en-nixpkgs-03f08b10d621f371c44a8d6eabbd9761a37659f59ab031a93777bb05404a95e1","title":"","text":"Describe the bug See https://nix- The particular cases that fail are I believe rust was updated recently (was that in the release?). It doesn't appear upstream has made a release recently, so perhaps if this report is forwarded to them they can direct us to which patches could fix the test failures etc. cc\nAccording to and bug reports, this seems like a ulimit issue. An interesting workaround for hydra could be using , as suggested in but it's certainly isn't necessary on my machine because I've tested the build and it passed it.\nsounds like it would make an already long checkPhase longer :rofl: How about we try ?\nWe can try this indeed. The question is, what are the default limits of a build user on hydra? Are we sure this might make a difference?\nI noticed you've marked sequoia as broken in . Even if a package fails to build on hydra butt doesn't fail locally, does it mean we mark it as broken in its ? Doesn't sound right to me..\nThat's was the motivation for the issue being opened. If we bump in preCheck and unmark it as broken I think we should be good. ofborg can serve as testing perhaps similar to hydra.\nThe point is, that we haven't even tried playing with these settings. I would have tried doing it my self but since I know nothing nor I have any effect on Hydra's deployment etc., I wouldn't even know how to test it. What bothers me is the fact it was marked as broken without any attempts by someone with more influence then me to debug it's failure to build only on hydra. Are we even sure this wasn't a failure that happened only once?\nShould we close this issue with the PR?\nNo, it's still failing , at least for hydra, it runs out of file handles\nA bit off-topic maybe but I generated a Nix expression for sequoia using , as build times for sequoia where around hours for me. It works now like a charm, as every crate got its own derivation. It can be found here, as a flake: Maybe repackaging with could be an option?\nThis may be an option, but unpleasant as the generated deps file usually is 1-10k+ of generated noise."}
{"_id":"doc-en-nixpkgs-f8ef5ab2593eaa8a69ce021d3417687c6b5a2d87889ccf5601a9609d8b2ddfd7","title":"","text":"(for local building, this works great)\nYeah, that noise is a bummer. Sometimes I dream of having all of packaged the way we do it with , but I guess that would blow up Nixpkgs indefinitely. But maybe someday when Nix flakes are ready? …\nI'm not sure I have enough time to have a good view on this. What's most important about specifically, is the fact we use upstream's to install many other files that should be part of the package's output - files such as libraries, ZSH/Bash completion files and headers. So I'm not sure how will this go together with the approach.\nIf anyone is interested in a sequoia flake which is built incrementally (vs. everything built in a single derivation), I try to maintain one here:\nsequoia , but it hasn't tried 0.16.0 yet - .\nYep, we need to fix it for python 38 though"}
{"_id":"doc-en-nixpkgs-4db9b6232b39c0e2f9ab1f43e90bdb8300fb1884636e157ffaa2cc9cee7e3843","title":"","text":"The 'select file' dialog works fine, but I cant actually open or edit anything. Steps to reproduce the behavior: Either: via the GUI, then a design or a design via the command line: A edit window with a preview should appear. Please run and paste the result.\nJudging by the error message, this might be as simple as compiling with wayland in the deps like ?\nOmg it worked! Can I leave it with the maintainers or do you want me to file a PR?\nIf you submit the PR yourself then you automatically get ownership/credit for your work :-)"}
{"_id":"doc-en-nixpkgs-500b02a31b515df561228e7ddb2a8a87542db0065935397cdea251d6fc33642b","title":"","text":"Project description Continuation (rebranding) of Hanazono font (nixpkg: hanazono). Supports a lot more Unicode glyphs (141,457 glyphs, mostly CJK). English README: Metadata homepage URL: source URL: license: CC0 platforms: N/A (TTF binary) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-a5856cb7d2d6faacc803720f0e3895cf45fb7ca4c91389d2c15d65101e25a969","title":"","text":"When adding to and running , emacs 25 builds and fails with 4 unexpected TRAMP mode test errors: The full output contains null bytes and weird control characters that don't let me paste this into a gist easily. Is that part of the test or indicative of the problem? cc\nok... i think this will contain the build output? again if i open it in emacs there are lots of control characters. had to zip so github wouldn't complain.\nI disabled for emacs25pre, for now, on my system. I hope this will be resolved upstream before next release ...\nIt's quite possible that tramp-related tests fail because there is no proper networking support in the build chroot, i.e. it's not possible to resolve host names or service names. Another source of trouble could be the lack of an UTF-8 capable locale in our default build environment. Anyhow, it would be really good to report those errors upstream to make sure that the next Emacs release has them fixed in one way or another.\nI've been working with the Tramp author for the past several days about these failures, and we've identified that the problem is somewhere in the environment that the tests are presented with, but we don't yet know what exactly. I'm still digging into it."}
{"_id":"doc-en-nixpkgs-77a09dafae5c1535ce256479a9a15cccdc219a4ef0e7d75630f00f19a3129bfb","title":"","text":"This is the content of on my system: It has set to , which does not exist. This path should point to the include directory of vulkan-headers package. Also, the package contain headers that include headers from vulkan-headers package. Should the pc file for glfw3 add vulkan-headers to the include path? Metadata system: host os: multi-user?: sandbox: version: channels(saga): nixpkgs:\nPing (Vulkan maintainer), I'm seeing when building anything depending on vulkan-loader using pkgconfig.\nThanks for the ping! Drafted Please confirm that this solves the problem."}
{"_id":"doc-en-nixpkgs-43095e4a104704969589be732f727273198f4a7fc365c083106f68948dfd26ed","title":"","text":"Reported via email by a Nix user without a GitHub account. Build fines. In the attempt to build GNU octave for aarch64 darwin. Maintainer information:\nI would suggest opening an issue but I guess that's not an option.\nPerhaps, but it seems peculiar that the user \"is not able to compile a simple test program\" - as if there's a bug in our compiler . Related issues: Perhaps the user should try this edit to Nixpkgs: So even on Darwin the compiler that will be used will be gcc, to play nicely with gfortran.\nThe suggestion to use is good; I think couldn't possibly work otherwise. Beyond that, I have no idea.\nBut doesn't it work on x86_64 Darwin?\nperhaps you could help us - does arpack and/or octave build currently on x8664 Darwin?\nAny news here? This also affects other derivations (e.g. openspecfun). arpack does build on x86_64-darwin.\nThis issue should be renamed \"gfortran broken on aarch64-darwin\", as it is not specific to arpack:\nSee – but we should really fix this in gfortran, rather than requiring every derivation to copy/paste the line.\ncc To summarize, we should set: In stdenv somehow.. Perhaps this should go here:\nWe probably don't want to globally disable stack protector support, though; this only affects gfortran. Seems like we'd want to have the cc-wrapper for gfortran (on aarch64-darwin) to never inject the options, either through a option, or in the cc- script itself. Actually fixing whatever goes wrong in the toolchain would be preferable, of course.\nHere's a proposal:"}
{"_id":"doc-en-nixpkgs-ea7f39db6b21485e74b83739e7749852fa583f9faaa58fbe1750ce3305a7909d","title":"","text":"Project description \"Linux/macOS media player based on GStreamer and GTK\" gstreamer rust Metadata homepage URL: source URL: license: MIT platforms: linux\nI tried to package glide and it's building successfully but the timestamps and the progress bar at the bottom aren't working. My progress is at if someone else is willing to look into it but I'm not sure how to debug this.\nNice, thanks Sadly, I think you made it further than me: heh\nI couldn't really find anything about\nI pulled your branch but it doesn't launch for me. Just the .\nStuck here I think maybe updating the registry would help, but I'd better waiting for the next release if possible..."}
{"_id":"doc-en-nixpkgs-6da65d5c4c1914660da0eb269e15486708dac7f9833d7e117a078eb8c51d013c","title":"","text":"Project description So basically it is a simple ssh config manager. Metadata homepage URL: source URL: license: Apache-2.0 platforms:"}
{"_id":"doc-en-nixpkgs-8e7624cd66432a4913e872891df8636f2097974e8e231e68815cab1bde281cfd","title":"","text":"pivy fails to build due to being unable to find some files Steps to reproduce the behavior: try to build pivy from nixpkgs HEAD"}
{"_id":"doc-en-nixpkgs-0ec1a9160f27f17ce64a7243d2c85e2845e433698b4c78117144d76372675f9a","title":"","text":"Describe the bug Since the recent commit ( ledger fails to build on Darwin. To Reproduce or similar. Additional context Add any other context about the problem here. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(steve): channels(root): nixpkgs: Maintainer information:\nif you don't need python. do you mind trying to build it with it off?\nthe error you're seeing is that a header from package isn't able to be found. I don't have a darwin machine to see why these two are different\nThanks. I don't need to work around it particularly, more interested in identifying a fix. I think the issue is that it's somehow picking up the system python: so probably some of the handling is broken, and indeed there are a few suspicious portions in the output I pasted, e.g. and subsequently:\nI got the same cmake warnings, upstream needs to update some of their files. I'm not familiar enough with nix-darwin to have it NOT pull in system python"}
{"_id":"doc-en-nixpkgs-be1dfc843eec01a09fa9b483d920f907317e286bf0f42506a8c8f53bafc01e6b","title":"","text":"Steps to reproduce the behavior: package 'grapejuice' Fixed by adding to propagatedBuildInputs Please run and paste the result."}
{"_id":"doc-en-nixpkgs-b4fe243ce0686505f4b6df04586261d2a75b64ba551055e3adb36103aee5fbc4","title":"","text":"Describe the bug A clear and concise description of what the bug is. mitmproxy tests broken on unstable. To Reproduce Steps to reproduce the behavior: nix-env -iA nixos-unstable.mitmproxy Additional context Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nthank you for submitting this, ill get it fixed"}
{"_id":"doc-en-nixpkgs-54dc46d8a328c1010c9261d6b22417859632fdc7bec7ec0cc2e66d819c3f13b2","title":"","text":"The version of AWSCLI in master is 1.32.58. This version requires botocore==1.34.58, however the version of botocore in master is 1.34.87 AWSCli botocore pin: This started happening after changing my to Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis should be fixed by , which syncs botocore, awscli, and boto3."}
{"_id":"doc-en-nixpkgs-b5e92a93bbedad6a6f48a147b94113c1a471bebaa0126ac123aef9949df5a8b5","title":"","text":"Using with and any packages depending on results in the following error: However, packages not depending on work fine, as does running on packages depending on and entering the manually. Steps to reproduce the behavior: the following flake: and that fails while succeeds. To be dropped in a with packages depending on . <!-- 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.\nWhile I could reproduce your case with nixos-22.05, on master, in both cases, I get dropped to a python shell, not a hy shell. Here is a version of your flake that overrides the so that you land in a hy repl. But I think it would be better to put this into eventually.\nI'd done that with , but hadn't thought to do it with ; it works! Thanks! Should one of us submit a pull request?\nOr perhaps would want to?\nNot really, if you want to open a PR I can review/merge.\nSorry, the instructions for contributing are a little confusing to me; could someone give me a summary of steps I need to take?\nAlso, I just realized I don't know how to merge this with ...\nAnd my own problem was fixed after changing the way the flake apps were made; thanks for all the help!"}
{"_id":"doc-en-nixpkgs-c849fbf0ac5347579926a1e2607b294f0c60a082bc60f11f48cbfe6c15ae5d9a","title":"","text":"On the , quite a few jobs are failing because libomxil-bellagio fails to build (, for an example). cc (as the package maintainer)\nCopy-paste from IRC (for the record)"}
{"_id":"doc-en-nixpkgs-d08998b9a9cdb502177a566c30ca85e07c39726819bfec251a4d9d538fa82b8a","title":"","text":"I'm not really sure why this would happen or how to go about dealing with this. Any tips?\n(triage) still a problem?\nUnsure, I don't use nix on my mac anymore.\nThis was a coreutil, right? If so, it’s probably fixed by now.\nProbably safe to assume so.\nI'm actually hitting the same thing right now."}
{"_id":"doc-en-nixpkgs-319df7c92f185cf1f02019f5814fd6f77ed78d38cd99729450ff6f54d1a34930","title":"","text":"Describe the bug Trying to run mutagen results in an error: The mutagen- which is supposed to have binaries for different platforms is missing. To Reproduce mutagen a mutagen session Metadata system: host os: multi-user?: sandbox: version: channels(alex): channels(root): nixpkgs: Maintainer information:\nHey, author of Mutagen here, super excited to see a Nix package for it! I just thought I'd mention that the bundle currently needs to be placed in the same directory as the executable itself. This is something I've been meaning to improve for a while now (by allowing it to be put in a directory), but I haven't had a chance to implement it yet, mostly because it's a little tricky to get right with package managers like Homebrew that symlink binaries into a different target location. I'm not very familiar with Nix, but I'm sure that it would prefer to avoid having this tarball in the directory. So I'm happy to push ahead on trying to support the -based layout if that's helpful here (or perhaps something more general if NixOS prefers a different layout).\ncc\nA quick update: Mutagen v0.11.2 and later support looking for the bundle in a directory (assuming a Filesystem Hierarchy Standard layout), so a layout of the form: should now work (in addition to the option of installing the bundle directly alongside the executable). This also works in a -style setup where the binary is symlinked into a larger directory.\nThanks! Is the available for direct download?\nThe bundle ships as part of the official releases (e.g. in the ). It needs to be kept in sync with the version of the binary being installed, but it should work just fine with a binary built locally, so long as the versions are the same (to the patch level). The bundle can also be built locally, but doing so requires running a custom script inside the Mutagen source tree that performs the necessary cross-compilation (this bundle is a collection of cross-compiled binaries that get injected to remote systems to facilitate file synchronization and network forwarding). I'm not sure the best way of handling that in the context of the NixOS packaging system. Perhaps there are some custom hooks available?"}
{"_id":"doc-en-nixpkgs-328847c28f89a681f18662c0ec3ec9c396ea7839498369dc4761e40a6b86d0ae","title":"","text":"At the moment, this script doesn't have a flag for building just this bundle (it will only be built as part of a full set of release bundles for all platforms), though I suppose such a flag could be . One of the downsides of doing the cross-compilation locally on Linux (or any non-macOS system) is that the C FFI bindings needed for efficient filesystem watching on macOS won't be available, so file synchronization between NixOS systems and macOS systems will suffer. That might not be a huge loss, though. This is why the Homebrew packages just use the official pre-built release bundles as their \"source code.\" It's a bit non-idiomatic, but it saves on local build times and allows for cross-compiled binaries with C FFI support. Of course, I totally understand if that doesn't work with the NixOS package philosophy, in which case just building the bundle locally is probably the best bet.\nAs a reference point, here's what the Mutagen Homebrew formula looks like:\nI agree, setting up the cross-compilation would not be trivial so the nix derivation must download the prebuilt agents binaries from somewhere while still being able to build the agent on the platform it is running on. I see three possibilities: (No changes on the mutagen side). Nix derivation downloads the full mutagen release and extracts . the version number to the and add it to the downloads. The nix derivation would just download it. the individual downloads for the agents similarly to for all the platforms and have the nix derivation create the itself. That way it would be very easy to even parametrize it to only download the agents the user wants and the nix derivation would supply the binary for the platform it is running on.\nAll three options are reasonable ideas, though I would prefer to avoid (3) since it would significantly increase the number of assets attached to each GitHub release (which is probably already too high). The individual agent binaries for linux/amd64 that you mentioned are sort of a special case for some experimental container integration features, so I'd prefer to avoid expanding them to every platform."}
{"_id":"doc-en-nixpkgs-a87cde7e326a96a7d9dadc58ab859015089fd27226445de21aeb32213d7df961","title":"","text":"I also don't know if many users want to go through the trouble of filtering the remote platform support that they want, though if that's something users are interested in then I'm certainly willing to try to support that.<sup1</supOption (2) is possible without too much effort, though I don't think it adds much value over option (1). Additionally, if option (1) is already going to be used to download the release bundle, it might as well just pull the binary out of the release bundle as well and save the complexity of a local build. In any case, the current package should have the build of removed since it won't really be of any use. Let me know if option (1) will work and if there's anything I can do to help. <sup1</supI think a better long-term solution is to provide two download variants: a \"full\" agent bundle that includes all platforms and a \"slim\" agent bundle that just includes commonly used platforms. P.S. Thanks for helping to support this!\nGiven the usual problems with pre-compiled binaries, reading the discussion above I thought we might have another problem : nixos needing its own agent in mutagen- But to my surprise, the amd64 binaries work on nixos without the need to patch the ELF interpreter or anything else, it seems that everything is self-contained with no external dependencies. So why not make a binary installation directly?\nI can open a brand new issue about this, but wanted to get a quick check from you about a problem I'm having with this. I'm getting the following when extracting an agent: The libexec path appears to be appended to the directory for some reason. I don't know if this is an issue w/ nixpkgs or mutagen but would be happy to help track it down and (maybe) fix it. So, it looks like the file is there, but the search path is treating the absolute path for as if it was relative to the path. I suspect it has to do with the liberal usage of symlinks in nix tripping something up. I'm just too new to golang and nix to have any idea how to fix this.\nHey I believe this is fixed in Mutagen (thanks to who reported it in mutagen-io/mutagen and fixed it in mutagen-io/mutagen)."}
{"_id":"doc-en-nixpkgs-611d50e8210f619ce78539ff6014b1ab8514d14a50e79853ec0c5b1523ce7b48","title":"","text":"It looks like the corresponding NixOS package needs to be updated — we're currently at Mutagen v0.16.4. If you want to open a NixOS/nixpkgs PR for that, that's probably the way to go. Feel free to @ mention me in that PR, otherwise I'll see if I can find some time to open it during this week.\nThanks for the information. :) I spent some time yesterday trying to get my local system running on Mutagen 0.16.4. I got it working in terms of correctly locating the agents, but I noted in the PR that it isn't working for docker containers because Mutagen running as root does not seem to be able to find Docker installed via nix. I'm happy to move any additional discussion to ."}
{"_id":"doc-en-nixpkgs-65e3286ab4adde8d6fdba1a4a3b5577dc21b72126f2b743e00c906d04feea9b6","title":"","text":"I never really noticed this until today, but apparently the discord task bar icon (if you have one, I am on KDE) is supposed to have a notification badge, I have included a screenshot. The discord task bar icon should include a badge for the number of unread notifications ! Today I was setting up a system for someone else who was new to Linux, I installed Discord via flatpak, and then they asked me about the badge (since it is present on Windows but not on the ). From a little searching, it seems that Discord needs to ba available in the system, so on Kubuntu this was fixed by doing . Since is already in , it might just be a matter of adding it to the ?\nHuh. I don't think I ever knew one was supposed to be there either. I see an unread indicator (red circle in the top corner, no number), so that works fine, but I don't think I've ever seen a number. Assuming that would be all it would take, sounds like a pretty simple PR that would be a good addition.\nI have made a clone of and it does seem that all that was need was to add the library to . I found it to be a bit ugly myself since I had over 1000 unread notifications, and it seems disabling it is only possible outside the application. On for example, you have to go to and tick off \"Show notification badges\". Running the current from afterwords does not remove the badges, it only freezes them in place, as in marking notifications as read will not update the number, so this is also cached somewhere outside , meaning this couldn't be a toggleable functionality via an ."}
{"_id":"doc-en-nixpkgs-ff93313c40e8241a976049652c1983ae4edac80f5ea043ac946c9d0545b1c5fc","title":"","text":"Recently variety stops working on NixOS. Pictures are downloaded well but the wallpaper can't be changed and can only be set in system setting. That's because of the hardcoded shebang which is taken from on the first installation. So when the bash is updated the script can't find it. It should be set as something like . Not sure if this is a nixos bug. Steps to reproduce the behavior: variety bash It works after the bash update. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nIIRC now we use . I am patching it now."}
{"_id":"doc-en-nixpkgs-41c3bf3e1df6632726d12a9af093b782f927b7790ebfe52308b1bda89b9965f2","title":"","text":"When attempting to add a Vim plugin, fails. It updates without error. I believe previous developers have this feature enabled in their system/user Nix configuration."}
{"_id":"doc-en-nixpkgs-0913763c01ed27c68780cc17d63b5c93e105371c4870f656caa3823e938fe95a","title":"","text":"We should mention in nixos manual Chapter 6 that options can be dicovered with and It will help newbs learn how to discover packages more easily. As a new user, I was sticking everything I wanted inside of the array, and I didn't not realize that is a better route to take because it configures many things automatically. For example, results in also being installed as well as features enabled, while writing does not. This will be helpful to new users.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-84a4bf76a0695e576ed44dc2bc383835e1c4b6792699c1f1790f8a3185c72af0","title":"","text":"Deluge 1.3.12 is incompatible with current libtorrent-rasterbar 1.1 introduced in . There are a few exceptions thrown in the log and several core features do not work as expected, e.g. seeding torrents get queued, although queues are disabled. The Deluge team does not plan to fix this, but it looks like libtorrent might in version 1.1.1. References: System: 16.09pre87431. Nix version: 1.11.2 Nixpkgs version: 16.09pre87431.\nShould we include an older version of libtorrent-rasterbar in the repos alongside current? We can point deluge to use it instead.\nYes, that would probably best in the meantime. 1.0.9 should work as expected.\nLooks like the PR that fixes this has been merged."}
{"_id":"doc-en-nixpkgs-ddc4f01b288eab34bb6acbdc8fcc95d3508ba90cfe02c087d13fa55036d5abec","title":"","text":"In this blog post [1], Google states that after March 15, 2021, they will be limiting access to various Google APIs that they are now describing as \"private\" and \"only intended for Google's use\". The most notable of this apparently includes \"Chrome sync\" which allows syncing bookmarks / browser history / etc. across multiple browsers logged-in to a given Google account. Additionally, emails [2] have been sent out to chromium maintainers from other Linux distros stating that users of their chromium-based browser will no longer be able to sign in to their Google accounts. They recommend these chromium-based browsers remove and from the build configuration, or alternatively, set at startup. Did we get a similar email as the one shown in [2]? [1] [2] CC\nFurther discussion With actual \"answer\" edit looks like this was cross-posted across two lists... I was confused by the interface... the content was already in the previous link. Basically, unless Google backtracks, the API key will become unusable for a distro-level deployment. We could continue providing the derivation, with bring-your-own API keys. This would be expensive to build for end-users. I wonder if the keys are trivially replaceable in the resulting binary though. If they are, we could produce prebuilt unusable binaries, and let users \"finish\" the build with their own keys. edit: The archlinux devs state that . Pinging and as we probably will have to apply the same resolution to 20.09.\nSome will poo-poo the thought because \"not FLOSS\" and similar ideologies, let's think about end-users first here. We're smaller than those distros, but if there's a common front to talk with Google about it, we should participate or approve of such a This will end-up hurting a part of our end-users.\nPersonally, I don't use chrome. Google does, what google wants. I don't think we have much of a choice, and will just provide what we can. I'm sure users will be aware that the limitation exists regardless of platform.\nYes, we should be able to pass these API keys from the environment instead of baking them in."}
{"_id":"doc-en-nixpkgs-394cd14a59502a985393a1b43c52229dced4d34767e676e8f8a6f446d973cb19","title":"","text":"From (This of course doesn't change anything about our API keys becoming unusable after March 15, 2021)\nQuoting a couple lines here from the email thread, since it was initially unclear to me exactly which keys we needed to remove: and So, we'll just need to remove and , but not from our builds.\nI drafted a PR: . Feedback is welcome (I lost track of this for a bit). Thanks for this issue btw :)"}
{"_id":"doc-en-nixpkgs-6a01be632c01a1607134d995eadd157e305e96642d5000d9745532a05a162b67","title":"","text":"Package name: tutanota-desktop Latest released version: 3.110.0 <!-- Search your package here: --- Current version on the unstable channel: 3.108.12 Current version on the stable/release channel: 3.98.20 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-7f1b50cbac881a6b33320ad1a8897900a113e04cccb62b31dfc3b59bbdb6e508","title":"","text":"Package name: Latest released version: 0.0.22.post7 <!-- Search your package here: --- Current version on the unstable channel: (This version never existed but whatever!) Current version on the stable/release channel: None <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nlet me know if you have time to test"}
{"_id":"doc-en-nixpkgs-7ed6b34dba9afa0ab46485e05c66a1040de6cb02de3059d1a6591cb6eab0b9f5","title":"","text":"Project description hwatch - A modern alternative to the command, records the differences in execution results (Rust, currently distributed via [Homebrew], [MacPorts], [Arch Linux AUR], and [Rust]) At the moment hwatch is only available for on nixpkgs Metadata source URL: license: MIT platforms: All\nIt has been available since 22.11:\nThat's weird, it didn't work for me when I tried it last time so I switched it to homebrew via nix-darwin. Let me retry\nI see the issue, it's Linux only\nupdated, thank you!\ncould you take a look at ?\nApproved, thank you for being awesome"}
{"_id":"doc-en-nixpkgs-b2c2864b34e8d4411236921d6d49806be229f71c0cfa66397a08aa4d5c16872d","title":"","text":"<details<summary<codenix log /nix/store/xglq4zgrfjp92jrjn1d740wgssrzbqpy-python3.10-tpm2-pytss-</code</summary</detailsSeems to be the same error as , but the current (as of ) has the supposed fix (). Maybe one of the other patches since then ( ) re-introduced the build failure? Please run and paste the result.\nI can confirm this failure\nI am also hitting this issue. Both of the above mentioned commits build for me.\nBuild failure was introduced with\nFrom the commits from that merge, narrowed it down to\nFollowed merges back up to , though both parents have the failure there... :(\nI have this issue too. This is my error message: This is the full log:\nI have the problem, too\nI don't have a patch for it yet, but adding -DFORTIFYSOURCE=0 to this list gets it to build.\nUnless I'm mistaken, that was the fix applied by &mdash; first patch in the list here:\nIt only add on L207, not on L187\n[deleted]\nYeah, the overlay I build isn't working for me either. Not sure where I was that made it work...\nfind out it and u will be the hero hhh\nOk, found the exact PR causing the issue:\nThe issue is that nixpkgs now forces the fortify setting, ignoring whats set in project's files. So old method of disabling fortify for just one invocation is not enough I've been trying to use and then setting fortify settings in the environment, but that is not working. With , the package builds, but with that set, it seems that trying to enable fortification in the environment has no effect. So not sure how to enable fortify for the built object files.\nThe overlay I'm using until there is a better fix is:\nSorry for the lag, I'm out in holidays with family without much internet. I posted a fix in but I'm not sure I'll be able to follow up on it."}
{"_id":"doc-en-nixpkgs-e29e7462b49ce617477a87951b85d9bc311c7aaca87ab15653657abe806f2bd7","title":"","text":"The doesn't start 'cause probably the wlroots it's causing a compatibility issue. Everytime that i try start river, it doesn't open. I searched on official repository and i found this issue: The current river's version on nixpkgs repository use wlroots 0.13.0, however the available on repository it's 0.14.1. Maintainers:\nI'm not maintainer for months so I don't really care.\nI'll get to updating it in about ~2 hours."}
{"_id":"doc-en-nixpkgs-04d41aeadcb8ef326cbc96af38272d478014a5d896487d4cf7d99ff7b259a611","title":"","text":"Steps to reproduce the behavior: <!-- 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.\nThis is due to the upgrade to Rust 1.65 in I'm sorry for the inconvenience and will take care of fixing this. The caveat is that I need to fix my system first, which I broke somehow trying to install the new version of nix\nThank you very much!"}
{"_id":"doc-en-nixpkgs-4b566e7df2bef081c48f77c1262d4bc9fb4d33be66cfc6b62a087376fc80221c","title":"","text":"I just tried upgrading to 23.11, and my ssh config no longer works. I specify and during a rebuild I get: , seem to have been in here last. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --I have a PR incoming as soon as git finishes pushing my branch to GitHub.\nThere's the PR,"}
{"_id":"doc-en-nixpkgs-074d58f797da308f388fa23df7c143164769dbb2e0fc849e7bba50c818043ca3","title":"","text":"<!-- 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 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: remmina <!-- The current version can be found easily with the same process than 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: 1.4.13 desired version: 1.4.20 <!-- 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."}
{"_id":"doc-en-nixpkgs-e12990bbaa997dac9684e665c8001f7f1151efa6e689ae1462f1c65b6c15c1fd","title":"","text":"Project description LDtk is an open source level editor that's used to make video games such as Dead Cells. It's just reached a big milestone and recently hit 1.0.0 release (now on 1.1.1). I apologise to the people of nixpkgs for requesting for so many new packages today! Metadata homepage URL: source URL: license: mit platforms: linux, mac, windows"}
{"_id":"doc-en-nixpkgs-83a368073141821af3e4951b454b62e54cbbf6b298315d690d1b33e543f56879","title":"","text":"Brave browser keeps reporting a failed autoupdate. ! It should be possible to avoid it just adding a CLI option in the entry: install the package open \"Brave Web Browser\" from the Gnome applications menu click the menu button (it is displaying an alert even before clicking) Please run and paste the result.\nBtw, this is much less relevant, but all icons are missing from the package.\nThe icons are there. They are symlinks to the directory.\nIndeed, I realized right after writing it, but then forgot to update: I thought I was two directories upper in the hierarchy (I could have realized, simply noticing it was missing ...). My bad.\nI was checking out the above PR, but I cant seem to recreate the issue. right now I've got brave 1.62.162, and the latest version available online is 1.62.165. It doesn't seem to be checking for updates. Is there a trick to getting it to check, or is it just sorta auto-updating for you?\nExploring Brave issues, like the one linked above, apparently the auto-update is a Chromium feature, even not so easy to mask for the Brave crew. However, within Nix, Brave is prevented to auto-update, so that's not an issue on its own. But it's attempting to, and just reporting the failure. So, no trick. I will soon check the version and report, but in case it helps, I'm using through a flake: and installing through NixOS:\nYeah, that's what I mean, it doesn't even appear to be trying to update when I try it.\nSince I provided the whole flake (and I'm also not doing anything other than requesting the package), I'm not sure what else can I do to improve reproducibility. In case, I could provide further screenshots. But the one above is essentially the issue on its own.\nRecreated with the flake :+1:\nDo you understand why is it showing up with the flake and not without?\nDidn't bother figuring it out. Figuring it's probably just that my version wasn't out-of-date enough."}
{"_id":"doc-en-nixpkgs-d1617b105472423cdf9866b3ab79779c55c200a1ea392a8a728b9e2dd2616c19","title":"","text":"Package name: uutils-coreutils Latest released version: 0.0.27 <!-- Search your package here: --- Current version on the unstable channel: 0.0.25 Current version on the stable/release channel: 0.0.25 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-f24fd1ae34051b6710ab6193879a06746600fca230fa3844e7b8526616a31132","title":"","text":"Steps to reproduce the behavior: I came up with the idea of building julia19 for that platform as a possible resort as the binary artifact does not work as is on my hardware, causing a , see also . <!-- 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.\nThe failure is also reproducible on hydra: , looks like the flaky tests that have been plaguing us for a long time."}
{"_id":"doc-en-nixpkgs-68b9e969555cd2a16fd6d8ccb63fc1c39151365dbc9c27ad83c61d968622da86","title":"","text":"Submenus (rendered as popups) in some qt apps (happens a lot in telegram-desktop) can make the app crash if one clicks outside while they are shown. It's a bug in qt6.6 that is foxed by this patch: Other distros (Arch at least) include the patch already."}
{"_id":"doc-en-nixpkgs-72782e31732f2b8d3bd00956abc2a2d178efe98b79fb9d5c07a4b08ceef6055e","title":"","text":"Describe the bug When renaming a submodule, the makes the child options reappear in the docs at the old location. This did not happen before (ping I've encountered the problem in the arion docs when its tooling to nixpkgs 20.03. The move is -. The regression makes the docs start with a mountain of legacy options comprising just under half of all options. Reverting fixes the problem. To Reproduce Steps to reproduce the behavior: an option to is in the docs, despite Expected behavior The option docs should have at most one entry per renamed option. Any suboptions should be omitted. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:"}
{"_id":"doc-en-nixpkgs-0aa454cbc0b0ca67637cc38e85baec79236843f98c76b31bd013169bac153e4d","title":"","text":"Describe the bug It is not able to build 3.4.2 with To Reproduce Steps to reproduce the behavior: Expected behavior Successfully build Additional context It looks like there is a build issue with 3.4.2 (, , ). It would be better to update to version 3.5.1 from Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(jjc93): nixpkgs: Maintainer information:\nI tried to update it locally, and failed. It still gives me ."}
{"_id":"doc-en-nixpkgs-6efb3442f5a57f53498d246f0f73207c820cda4911dfb9c39d3e42717ccde753","title":"","text":"Steps to reproduce the behavior: X Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result."}
{"_id":"doc-en-nixpkgs-785c2fe35c1cc5ae236a2b93c72bc73a4aa8804dcf4bc238d7060c2f83776921","title":"","text":"currently fails It requires 3.12. I believe this in pinned to 3.10 somewhere in NixPkgs, but do not know where. Add any other context about the problem here. No maintainers Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nplease add \"Haskell\" label\nfixed here"}
{"_id":"doc-en-nixpkgs-450c2a42f0a30d790e3218a9eeb918a138445b1e338ca86f18a3e70f1db97893","title":"","text":"Beginning around commit , postgres < 14 will not build with musl: Postgresql successfully builds Here is the full output: The patches introduced in the above commit appear to be specific to Postgresql 14.x <!-- 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."}
{"_id":"doc-en-nixpkgs-5293069c61a534e23aa0d9cd57856f389da79fa2b26f1aee892837580da6706d","title":"","text":"Request for a new nix package for openmesh : library for polygonal meshes Thank you. OpenMesh is a generic and efficient data structure for representing and manipulating polygonal meshes. OpenMesh is developed at the Computer Graphics Group, RWTH Aachen. It was funded by the German Ministry for Research and Education ( BMBF). It was designed with the following goals in mind: Flexibility : provide a basis for many different algorithms without the need for adaptation. Efficiency : maximize time efficiency while keeping memory usage as low as possible. Ease of use : wrap complex internal structure in an easy-to-use interface.\nI think it would help if you described why you need the library packaged. Do you plan to include any software that uses the library into the distribution?\nYes it will be feasible later. At the moment I would like to develop and launch continuous integration with Nix. I have 7/8 libraries and I need this last one under Nix to start. Note that this library is very stable, recognized in the domain of meshes, simpler than CGAL, small, without dependency... It is also on Mac with HomeBrew for example.\nI don't want to maintain it, but this derivation will get you up off the ground:\nThanks a lot, I will look that maybe after summer and maybe I will propose to be the maintainer of this package, we will see ! Thanks\nI marked this as stale due to inactivity. &rarr;\nHave you tried to package this?\nNo time for the moment. But I will look that when I can... or or\nModified from version to fit the URL for versions 10.0: Hi I saw your comment about the PR. If you have time now, that would be great. If not, I'd be happy to help and create the PR.\nHi No time sorry, so you can do that. Thanks !"}
{"_id":"doc-en-nixpkgs-7521c45b7a26116b8b75b99df9d6b3a53a88029ef83661285062e6960ca7a9a6","title":"","text":"Steps to reproduce the behavior: nixpkgs master (currently ) This seems to be directly caused by introduced in No update of is availble upstream. (author of the PR) ( maintainer) Please run and paste the result."}
{"_id":"doc-en-nixpkgs-d6f651d2f4fb060e28ea2b597e300699f9462877efe7f1057585b67659f4f0fa","title":"","text":"Cc (PowerShell maintainer) Describe the bug Powershell uses telemetry unless explicitly told not to do it. In addition to its own environment variable (already set in the wrapper), it should require another one to disable telemetry from the underlying .NET platform, i.e. should be set to To Reproduce Steps to reproduce the behavior: powershell with (assumes you have the unstable channel installed) it with and verify that it's not set (i.e. no output) Expected behavior should be set to : Additional context Example of PowerShell's own CI config that disables telemetry on Linux: This should be fairly easy to change here: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-7eae7bd6501915d4e50192bba3268ce59b4052976e08d422371ed1a660696a53","title":"","text":"Describe the bug I'm trying to get Steam big picture to work with , xbox wireless adapter and a couple of xbox controllers. But if Steam is already running and I turn on my controllers, they successfully connect to the dongle, but steam doesn't detect them. If i first turn on the controllers, and then i start Steam, it recognizes them and they work fine. xow: I couldn't use the service file provided by the package because it would never start. I read somewhere that systemd is picky with symlinks, so i defined it myself, now it's starting fine. I also had to blacklist else xow would crash. Steam: To Reproduce Steps to reproduce the behavior: sure xow is running fine Steam on steam controllers to see if they work (they dont) Additional context I think xow is working fine. I tried the latest version (0.5) and the last commit, importing udev rules from the package and adding them to I also tried adding my user to the group. It doesn't matter if steam is running in big picture or not, i also tried steam native, still not working. Metadata Edit: Steam won't detect controllers even when using the wire. And also i tested the controllers with and and they work as expected. So i'm pretty sure the issue must be with steam.\nThis might be an upstream problem with , have you tried using it on a non NixOS system? I also maintain (a kernel driver for Xbox controllers) and I don't have this problem with Steam. Maybe try to test if there's still a problem on your system with xpadneo?\nYou might also want to try enabling xow using the NixOS module instead of writing a custom service:\nYes, i have another system with Arch and it's working fine there. Steam detects controller connections even when it's already running. That's what i tried at first, but xow wouldn't start, the service was hanging in an state. And I think it might be because when importing the service from the package, nix is creating a symlink to the service and it might cause some issues."}
{"_id":"doc-en-nixpkgs-5996a4180ee79b0cb1d56cc4e8ae105210abbccbe35fe0b839096feab5dfe391","title":"","text":"Also I did some more tests with xow and controllers are working fine, , , this website https://gamepad- everywhere it works as expected, even Stardew Valley is able to detect them, but not Steam (well unless i restart it with controllers connected, then they are detected and working). It's really weird, I am able to pair them, xpadneo detects them, but they are totally unresponsive, everywhere. I uninstalled xow, and removed the wireless dongle when i tested this. Since xow it's working fine in browser with https://gamepad- and with some games, then udev rules should be fine , right? I would say it's an upstream issue with Steam, but it's working fine on Arch, so there might be some issues with some libs?\nThe xow NixOS module is fixed now. The problem was that NixOS specifically bypasses the Install section of service files and the module wasn't setting WantedBy for the service explicitly.\nI am wih something similar here, I am using the gamepad via USB , before the config all software detected the control, and I was able to play without problems except for steam, which prevented me from using the big picture, after enabling this option I have the same behavior as steam for all applications, if I plug in the control it does not work until the next reboot. Any suggestions on where to debug to understand why this behavior? Dmesg and lsusb look ok.\nHaving a similar issue, since I'm not using xow or anything but kernel drivers: Steam isn't able to detect a hotplugged Xbox one wired controller. It works perfectly fine if I plug it in before starting Steam. I can also confirm this behavior works on Arch.\nthat's my situation too\nI guess no news on this? :(\ni'll take a look, probably something to do with udev rules. i dont have a xbox controller though, only a steam controller\nThis problem sufficiently annoys me at this point that if there are any instructions I can follow to provide information I'm happy to do so. Thanks for offering to look. I am currently in possession of 2 xbox controllers, several controllers that show up as xbox controllers, and some controllers that don't show up as xbox controllers. I have this issue with all these controllers to the best of my recollection."}
{"_id":"doc-en-nixpkgs-1a9e26e5a93cdd6ec41079208dbd200b18bc5a6adb2fac15922ccac88dce5bb6","title":"","text":"the steam udev rules are almost the same as on other distros, though arch does i'll try borrowing a xbox controller. does this happen with only the xbox one or does it happen with 360 too\nsadly i can't find a xbox one controller. the udev rules provided by the steam package are the same as on other distros, maybe it has something to do with our other udev rules. may also have something to do with bubblewrap\nIt seems to be related to linux usernamespaces which to my understanding remaps the id of the sender of udev events (from 0 to a big number) leading udev to ignore these messages if it's not zero. Running directly on my system and under (running as root and as a normal user) led me to believe this (). This issue may need to be fixed with bubblewrap, I don't think something can be done here. Unfortunately I don't have a solution :sweatsmile: PS : I don't know if fixing this issue will make everything work, .\nthese look related\nI merged someone who has this issue please look into using the patched systemd with the steam fhsenv\nI've just tested on latest NixOS unstable. A hotplugged Xbox One controller was successfully detected by Steam Big Picture. Thank you!\ni haven't done anything that would have fixed this\nWell that is exceptionally weird! Because it's definitely working for me, looks like an unrelated PR fixed it? This is straight out of my terminal, after starting Steam with no controller, disconnecting and connecting again:\nThis must be a change to how steam recognizes controllers. The program from still does not show events when started within There is still something odd: My joystick Logitech X52 HOTAS is recognized as a gamepad, while when I run steam packages on flatpak, it works properly. I don't know what they do differently in the flatpak version to get it working. Maybe using libgudev or a flatpak specific version of udev in the runtime packages? I have tested adding patched systemd to the fhs of steam, but this did not change anything (maybe some other udev library version was shadowing it)\nI marked this as stale due to inactivity."}
{"_id":"doc-en-nixpkgs-500221d572d6d0af96a88ede3b2e959cbc096c9e6faa0ded27b916c46da78006","title":"","text":"&rarr;\nI still have this issue, with both an xbox 360 controller with the wireless adapter as well with an 8Bitdo SN30+ in both wired and wireless mode. Starting steam with any of these already connected works, but if one gets connected after starting steam (or worse - shortly disconnects while playing) it will not be reconnected until a Steam restart. However, with a Steam Controller hotplugging works just fine! This happens with Steam Big Picture mode (and also in games, but I guess Big Picture mode is more readily reproducable). I assume I am doing something wrong as others have it fixed, is this really no longer an issue for others? Happy for any pointers and to assist in debugging. (my config is at in case it is needed, i am currently on )\nI assume I am doing something wrong as others have it fixed, is this really no longer an issue for others? I have the same issue, with PS5 DualSense controllers. I debugged a bit during the christmas holiday, based on some info in either this issue or some other... By applying a patch (linked from the issue) I was able to see udev starting to detect hotplugging the controller in the Steam FHS env (it didn't detect these events by default), but still Steam wouldn't pick up the hotplugged controller.\nI found my experimental config snippet from back then: AFAIR, I was worried that steam itself didn't use the patched libudev, but I'm pretty sure I looked up the process map and found it had (only) loaded the patched libudev, so I'm not sure what's going on. Didn't look at it since.\nIf anyone just wants to throw money at this problem I highly suggest the to solve it. The real win with this gamepad is that it always shows up as connected to your PC, even when it is powered off. It achieves this by coming with a usb dongle that shows up effectively as a wired joystick regardless if the gamepad is being used or not. Perfect solution for this problem... I have 3."}
{"_id":"doc-en-nixpkgs-6814377abefe4dab907c16e71e7fc8d1d00629e6f59a6c2c5852bb8359990c50","title":"","text":"I'll mention a potential con, though: Make sure you have good line of sight between the usb dongle and the gamepad (don't worry, it comes with a ~1m usb extension cable to allow good line of sight) and aren't too far away (3-4 m I would guess) or else the signal is really spotty. In my last setup I used this through the wall and it absolutely wouldn't work for any serious gaming, but now I have the pc in the same room as the gamepads with direct line of sight and it is perfect. But yeah... a real solution would be better and still appreciated by me. Just thought I'd post this in case anyone could benefit from it. :man_shrugging:\nAnother alternative is to use : in the config: then install and run it: I didn't have any issues since doing it since flatpak was updated to = 1.12\nI still have this issue on Nix's version of steam using nixos-unstable. Enabling xpadneo did not fix it either.\nmay have fixed this\nSeems like didn't fix it. I see that it is in nixos-unstable and it seems like Steam still displays the same issue with my DualSense controller. I need to restart Steam before it detects it\nI am having this issue on every controller I have: Steam Controller Nintendo Switch Pro Controller PS3 Controller Gulikit King Kong Pro 2 Controller in all 4 modes (Switch, XInput, DInput, Android/iOS) USB adapters for NES, SNES, and Gamecube controllers It occurs when using both Bluetooth and USB, so I am 90% certain it has nothing to do with which controller you are using. The behavior is the same for all of them; when I connect any USB/Bluetooth controller it is not recognized or noticed by Steam if it is already running, but only when Steam is starting up while the controller is currently plugged in. Here's some information on what happens when I use the Gulikit controller (XInput mode via bluetooth): Controller connected and Steam is not started At this point, and are now created Now I start Steam And reports: And now and are created (???)"}
{"_id":"doc-en-nixpkgs-e83f0efb955e092cb8ec8c8ddc99d4903be3dbc3e9f5041de4c4deefaf5ae6ae","title":"","text":"Disconnected the controller with Steam running Nothing new in I reconnect the controller with Steam running* And and is back TL;DR - So it looks like Steam will normally start up and find the controller and then it will create the virtual input devices and . However, it won't create these devices when they are connected after Steam is already running. The question I have is why this happens and what can be done to fix it. It looks to be a NixOS specific issue as the problem doesn't appear to be on other Linux distributions like Arch (just reading off of what's in this thread, I haven't tried myself). If anyone wants me to try anything and test it on a fair variety of USB/Bluetooth controllers please let me know. I think something might be wrong with how the FHS wrapper () seems to be binding the devices that prevents new devices from being seen. EDIT: I just confirmed the and device files are appearing and disappearing in the environment that Steam runs in, so the FHS is actually properly creating those devices. The only difference I can see is that they are owned by in the FHS environment (versus in the normal environment). I can still properly access both. I did see : However, that would imply this is not NixOS specific and instead is default Steam behavior. No indication of how to change that default behavior though, so I can't find a way to confirm it.\nThis seems related:\nJust as an datapoint: The Steam Controller is actually one that does not exhibit this issue for me, at least not when wirelessly connected with the Dongle that came with it. If I connect it via cable then it is the same as usual, only recognized when restarting steam. Also if connected via dongle and I replug the dongle, the controller only gets recognized when restarting steam. But if the dongle stays put and I shutdown the controller (by holding the Steam button for a few seconds) and start it again it works just fine with steam running. I guess it might be similar to the controller described in\nI was surprised as well, and a little bit of digging reveals that SDL2 being inside flatpak and disables the unreliable udev-based discovery. And disabling it manually ! I opened to fix this.\nCan confirm that it fixed the issue for me. Good job in discovering this\nThis is resolved for me now as well."}
{"_id":"doc-en-nixpkgs-e705b308d1650b64e9739c8de298aa94ef31564cac89ad2c4ae07c72d5d67d46","title":"","text":"This link is invalid: It is used to download the build Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-43f00b1aade255ae6000e83f90fa545b52e309e82042f0b4db22316c1fa6794e","title":"","text":"Steps to reproduce the behavior: , build v2ray-geoip Probably we can pin to buildGo120Module?"}
{"_id":"doc-en-nixpkgs-69c5c493715e75afc3e0a7d6e9a36e9fe4724477fe2d75afb5473e1a8396601c","title":"","text":"NixOS's gzip 1.11 contained , but gzip 1.12 does not. This was probably caused by Please run and paste the result."}
{"_id":"doc-en-nixpkgs-5d31f4969bd624667d5fae402711388b0f0a61d146d299a768d2d072fc8bb78e","title":"","text":"I cannot install on my Apple M1 PowerBook any more (potentially due to ?) I'm tracking (commit ) Steps to reproduce the behavior: Here's the output of\nI'm afraid I don't have a Mac around to test with, but from glancing at the build log it appears the problem may go away if you remove from in the jsonnet derivation, or make it conditional on stdenv.hostPlatform.isStatic as suggested in .\nI can confirm this issue. We worked around this in our own overlay by reverting to the last known (to us) NixPkgs version for the Jsonnet package only (i.e. we overlayed the derivation with one that is basically . No idea what exactly causes the problem, though.\ndidn't fix this, I still can't build jsonnet on Darwin.\nThis is fixed in , PTAL."}
{"_id":"doc-en-nixpkgs-5257102a2d301ada9d39dca6e08180dd62abb54c0844af89d6d242c54add4309","title":"","text":"Project description Microsoft Azure Command-Line Tools Storage-preview Extension Metadata homepage URL: source URL: license: mit platforms: unix, linux, windows This package is distinct from the package that is already in 24.05 and unstable. It enables azcopy utility in the azure-cli, which is useful for interacting with large storage accounts in Azure.\nCode for extension\nplease give a try and leave some feedback. :)"}
{"_id":"doc-en-nixpkgs-d36b6468cb9eed52a0373130a63e018997290051a94cddf20ca62111a2746191","title":"","text":"Describe the bug A lot of kde widgets and functions broke after recent updates on the unstable channel (nixos-unstable). Opening the bluetooth widget shows this error message: Other broken widgets/functions includes bluetooth widget, printer widget and desktop (the desktop disappeared resulting in a black background) xsession log: To Reproduce Steps to reproduce the behavior: plasma plasma Expected behavior Plasma widgets should work normally Screenshots A broken widget: ! Additional context Add any other context about the problem here. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\ncc I believe Qt was updated on unstable.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nThat was just me asking if it was broken. In my case, The activities and taskbar went down. I am also having the black screen as background. The errors messages I've noticed are: Ocorreu um erro ao carregar o arquivo QML: file:///nix/store/aril5n1mllyyfdgjp23va4wh8d8mbl13-plasma-desktop- module \"\" is not installed system: host os: multi-user?: sandbox: version: channels(wjjunyor): channels(root): nixpkgs:\nThe likely culprit (though I'm not super familiar with QML) is that these lines: Are not present in the 5.14 version of the patch:\nThat sounds about correct to me. All the patches had to be redone for 5.14 so I guess that hunk got dropped\n30 minutes into rebuild with it readded, will report if it works :)\nJust a recommendation, not sure if it will be helpful to you specifically, but the time to rebuild should be relatively short, and it could be even shorter if you test via running the nixos test interactively\nYeah, that's exactly the command I've been waiting for... it seems to rebuild all dependencies of qt; I'm currently on qtwebengine, which hydra says takes 5 hours :/\nIt works :)\nWhat do I do now?\nthe fix was merged into master, so wait for the next update of nixos-unstable (or switch your system to master :)"}
{"_id":"doc-en-nixpkgs-14faabc686787f0bbf6ae0adda721d6d33280e1acca948941da7317c648af17f","title":"","text":", (nixos-19.03) Scanned versions: nixos-19.03: . May contain false positives."}
{"_id":"doc-en-nixpkgs-b4614fbfe8566b268c08b5cb8960f3b77ef29375bd873c256e172a9b90c95939","title":"","text":"Package name: cardinal Latest released version: 23.10 Current version on the unstable channel: 23.09 Current version on the stable/release channel: 22.12 Notify maintainers Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-307c7b1e3bdcd7fad6770b20d86298c0061775eb015605205deda1a886416a19","title":"","text":"Package name: csvkit Latest released version: 1.1.1 <!-- Search your package here: --- Current version on the unstable channel: 1.0.5 Current version on the stable/release channel: 1.0.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --attn upstream at upstream docs at Note for maintainers: Please tag this issue in your PR.\ncontains the update."}
{"_id":"doc-en-nixpkgs-00860d6c35e78810a36c716f3dfcb92a4a278c89725a0fd78f843a9acd0b04da","title":"","text":"Describe the bug The following warning logs are produced in my server. To Reproduce Steps to reproduce the behavior: a NixOS server Expected behavior No warning should be logged. Additional context It should be noted the interfaces of my server are named and and not and as referred to in the warning logs. Notify maintainers Metadata Please run and paste the result. Maintainer information:\n(exact) duplicate of .\nIt may seem related but it is not a duplicate. First the concerning logs are warning (PRIORITY=4) which makes me less inclined to whitelist it in journalwatch. Also, there are no interfaces named and . It seems is not respected.\nSorry, I didn't notice the interface names. That message is surely coming from the IPv6 privacy udev rules. To see their content: The interfaces are not set from NixOS but are coming from the kernel. I'm not sure why you're seeing and . Maybe the traditional scheme is used first and later the interfaces are converted to the new scheme so the udev rules are fired twice.\nThe message seems indeed to come from the udev rules:\nindicates (emphasis is mine): as well as: So it seems the kernel does not respect . you worked on the following code, do you know what is happening?\nThe interfaces are renamed according to the logs: - I do not know much about udev, maybe the udev is triggered as soon as the network interface is detected and by the time the command is executed, the kernel has already renamed the interface.\nI marked this as stale due to inactivity. &rarr;\nThe same thing is happening here on NixOS unstable:"}
{"_id":"doc-en-nixpkgs-8560503de2cf27aab2f08bfcd6b0378451003eab31300ce98e1816a921814e6e","title":"","text":"is missing a dependency, hence the build fails. Steps to reproduce the behavior: to : end up with this error: should build without any issues - -\nIf doesn't work, that is a bug but kind:bug and not kind:build-failure so another issue not to mix stuff…"}
{"_id":"doc-en-nixpkgs-6f521fe55baa1c8d6c7fd8cf0413332195bc45b223ada41d1dbcc4f0ed6515e5","title":"","text":"after suspend the network-manager applet in plasma5/kde disappears suspend resume search for nm applet log out log in its back\nDoes this still happen on ? I cannot reproduce it.\ni am no longer using nixos"}
{"_id":"doc-en-nixpkgs-f4e9cba1d672c9158ab703c0198966c2602098862e6d647f341c49c5bf6dc97e","title":"","text":"Project description Prometheus exporter for Free Range Routing Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-55efd96de5f9b1cd4795fbad2a9eae8b6e421e5e5ede9152d3dbb745637dbecc","title":"","text":"When trying to run , I am with the following Qt error: I'm fairly new to nix in general, and definitely not familiar enough with the Qt wrapping mechanism. I would expect the derivation to somehow set the \"Qt plugin path\" (?) properly so that is found upon startup of the application. I've found the section in the NixOS Qt documentation page which recommends using the in your derivation, but as far as I can tell, the derivation ? A dirty workaround I've found is to manually specify as follows, after which the application can be successfully launched: I've looked for a way to patch this properly into 's derivation, but I'm not comfortable enough with nix to figure out how to do this. I've found that other packages such as QGIS do : but it seemed to have no effect in , maybe because the derivation uses , and not ? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nPlease test\nI merged the above PR. please give it a try once it hits the channel you follow:\nIt works like a charm, many thanks for your fix :heart:"}
{"_id":"doc-en-nixpkgs-208ceddf43ae72a27ed3f5eb66254c2382f2ef8852d5a230b817b601b2a5b169","title":"","text":"consider the following which is running inside of a container: and the corresponding system profile: the original produces a store path of now let's modify to add a simple file to : instead of immediately ing to this new configuration, let's set it to activate on : looking at the system profile it looks like everything is in order here... the symlink has been switched appropriately: the new produces a store path of let's , the new profile, and look at the file we to : :thinking: what happened? what does our system profile say? :explodinghead: somehow an additional system generation, the old system generation, was created, symlinked, and activated! additionally worth noting is that + works absolutely fine at this point i'm completely lost :manshrugging: any help? :bowing_man: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --... maybe has run into this before and has some insight because he seems to know what he is doing with running on ? or at least he can confirm whether he has this issue as well? :heart: Please run and paste the result.\nI can confirm I'm seeing the same thing. I followed basically the steps you laid out for testing this. Before running , I am on . My profiles look like this: I then run , and I'm now on . I then run , and my profiles look like: I then run and restart the LXC container. After logging back in, I can confirm a new profile has been created and it is pointing to the previous profile for some reason: Although, at this point, if I jump into and look at the nixos version, it does appear to be pointing to the latest NixOS version (which is system-16-link in my example). So this at least looks correct?? I'm not sure I understand exactly the semantics of vs , or how exactly the works. It is not clear to me what is the \"correct\" thing to happen at each of these steps. edit: Oh, I did a little more digging and I think I know why gives the seemingly correct nixpkgs version."}
{"_id":"doc-en-nixpkgs-51027216735f3ad1da4b724d97105d1114ab53592012d52e36390d19700cf7d1","title":"","text":"After I've rebooted, still has the correct channel setup: So 's channel does seem like it is setup correctly, it is just the system that is not: Here, you can see that both and are pointed at the previous version (as you would expect from the state of the directory, as shown above).\nI should add the following two things: I can also confirm that doing followed by , and then booting the machine back up does get the correct profile setup, as reported.I'm not able to confirm that was ever working for me in my LXC container. Looking at some of my previous system profiles, I see the same Nixpkgs commit hash being reused over and over again (corresponding to the bug you'd expect). It is possible that has never worked in an LXC container. I don't have any ideas here, except that maybe the module is doing something bad?\nThanks for looking and confirming I'm not sure the answer lies in the script... but it is somewhere down that path so I'll ping our expert in case they can take a look and provide any useful insight. I'm also not exactly sure who else to ping specifically about this... so I'll just ping some random people who know a fair bit about the lower levels of NixOS in case they can provide any insight ping\nCould you comment the switch-to-configration output as well?\nI don't know a lot about lxc, but these unconditional commands look rather suspicious:\nThanks for the comments everyone! I spent a few minutes poking around and found a few things. By commenting out this line the new generation is not created, though + still doesn't activate the new generation. More on that below... The doesn't do much when called via - it . The script, which calls , looks to be as it should. Our module includes which will use to boot the new system... but since we are running this replacement of never happens, which is the cause of the problem here! I confirmed that if I manually replace and reboot everything regarding works as expected. I don't think will execute any code from the module system directly (ie. activation scripts). So how do we teach to run ? I appreciate any and all thoughts on this topic :bowing_man:\nI found some time to dig into the depths of how NixOS builds systems and now have the understanding I was missing to solve this problem."}
{"_id":"doc-en-nixpkgs-067295c9a380f65a093f8992b6063be11654f437a3edae963e87d1163c8f5c45","title":"","text":"Steps to reproduce the behavior: Notable part: @ lines 43..48: Looks like a cmake incompatibility?? possibly connected to ? <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): channels(anna): nixpkgs:\nCan you try building it manually against the latest nixpkgs-unstable revision using ?\nThis is really weird. Looks like something went and replace the first occurrence of in the source files with in . This is how it's supposed to look:\nThis was already built against the latest at the time, around an hour ago. My system flake registry pins to it. I get the same result with .\nthis looks completely normal. what is going on?\nI have done a bisection and it appears that the first bad commit was\nAfter bisecting Meson, this bug was introduced by and is still present in master.\nYes, I am writing a fix right now\nhas been merged, but do you think you could make a PR to master to have prismlauncher use its own overriden meson and another PR to staging to undo that change, so that way prismlauncher is at least fixed in the master branch sooner than a few weeks from now and when staging hits master, it won't have that temp fix anymore? Thank you again!\nNote that the package that's actually broken here is . But yes using a fixed version of Meson for this sounds like a good idea."}
{"_id":"doc-en-nixpkgs-5dc9df62f3ac0af10defaebb42dea37413dd8bff582f6e1771306768e32faf22","title":"","text":"Mention key types that people actually use and don’t mention ones that have been removed. <!-- make sure this issue is not redundant or obsolete --- [x] checked [latest Nixpkgs manual] ([source][nixpkgs-source]) and [latest NixOS manual] ([source][nixos-source]) [x] checked [open documentation issues] for possible duplicates [x] checked [open documentation pull requests] for possible solutions [latest Nixpkgs manual]: [latest NixOS manual]: [nixpkgs-source]: [nixos-source]: [open documentation issues]: [open documentation pull requests]: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-81b0d160139003ec4acd4821a65e4cb9d380297ebf5cc5bcb7d01f7016be6c4a","title":"","text":"Let me start off by saying that I'm completely new to nixos (this is my first install that I did today) so there might be something obvious that I don't see yet. I'm installing nixos in vmware fusion on macos and I'm trying to enable vmware guest additions in nixos. I enabled: and got an error say that it's unavailable on the hostPlatform \"aarch64-unknown-linux-gnu\". Steps to reproduce the behavior: nixos 23.05 (minimal) in vmware fusion on macos to enable vmware guest additions. error It should configure nixos for vmware. ! I found which makes me think this should be supported. I noticed that aarch64 isn't listed under There don't seem to be any maintainers for xf86-input-vmmouse Please run and paste the result.\nif you enable headless mode ( ie = true ) this should work, with the caveat is that this will install the headless version of open-vm-tools. AFAICT xf86-input-vmmouse is not supported on aarch64 (there is no other distro that ships a aarch64 package and the for it does not reference aarch64). Ill see about sending a PR to fix this case, just need to set an env where i can test this. (where you want xserver installed and you enable virtualization tools).\ncomments out some stuff that's actually not problematic at all on Aarch64, since only the ps2 mouse thing is, and ps2 is not even useful these days: I'm thinking just this part should be conditioned by !Aarch64 (or maybe x86_64):"}