{"_id":"doc-en-nixpkgs-9a3fed3e5cfa4fe9faec71122ca8a2269be410e0b0f3d90e00be2f58a68836db","title":"","text":"lists a listener option called that can be used to listen for incoming network connections only on the specified interface. Unfortunately does not accept this option. Steps to reproduce the behavior: This should evaluate cleanly. Incidentally, that assertion message drops the component in the attribute path, it might be nice to fix that."}
{"_id":"doc-en-nixpkgs-37c8cf8a361af109b648bdf4ce64fdf071659bbb47ff303d0a8ffd6100aa6124","title":"","text":"I started grafana-agent in flow mode, and tried to access the http API at http://localhost:. Unfortunately, instead of providing a web interface to debug the current list of components, I get a \"404 page not found\". Steps to reproduce the behavior: grafana-agent in flow mode. port via HTTP I'd expect grafana-agent to ship with the web interface. Please run and paste the result.\nIt looks like is what's building the frontend. Unfortunately, the web interface seems managed by yarn (and has a ), so we'd need to first provide a . I tried to have resolve the dependency, but it seems it's not able to:\nI manually patched things in to bump to a more recent version, compatible with the react version that's mentioned in , but ugh, I'm not really sure why it's that way. I'll ask upstream.\nyeah, sorry, I don't use flow mode (yet?) and the nixos module does not support it either, as far as I am aware. I can try looking into it as well, first, before you raise an issue upstream. While the nixos module might lack support for it (for now?), I believe we should try fix it nonetheless :)\nYeah, we should probably have a second NixOS module for flow mode, it's very different and the existing config structure doesn't make much sense - for now I just did ship my own custom systemd unit for it: But yeah, without the web ui it's quite annoying to debug, so we should probably get that sorted out first, before providing a module and getting more people to use it.\nfyi\nI tried to move it over, but still seems to be terribly slow when trying to resolve deps and not being able to, so I guess we should stay with yarn.\nWe should prefer yarn simply due to upstream having an instead of a :) ^"}
{"_id":"doc-en-nixpkgs-010a2a3693a15d2bd177cbeee943f5b4d9e4c44588ef75b26a641ccc3bbfff94","title":"","text":"The packages and are outdated () and have been replaced by the package (). To update a derivation just replace those two packages by as a build input. The following packages depend on and/or : [x] openmpi (fixed in ) [x] (does not find librdmacm in the configure phase when compiled against rdma-core) [x] (infiniband support seems to be defunct. configure does not check for IB libs and it is not linked against any of the required libs, libibverbs or librdmacm) [x] (RDMA support was removed from )"}
{"_id":"doc-en-nixpkgs-8b1f60a4da22f0634f69abae37f027ea0ecae0b0dd101ce64e0ff435d82d6aae","title":"","text":"Steps to reproduce the behavior: localstack (from unstable) (version 3.2.0) localstack 2.3.0 works and so does (tagged because you bumped the version) (the channel is slightly messed up. I am using 23.11 but with flakes) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThe new version requires too many dependencies to package up in a reasonable time frame and even includes circular ones. contains a revert to 3.0.0 which builds for me and shows the usage. Can you take a look if that works for you?\nSorry for the delay! Yes, the revert works well for me! Thank you!"}
{"_id":"doc-en-nixpkgs-71474bd610073a818f548a085cdcaaf38531270b5bd7b1f574e912255a4f51d6","title":"","text":"ember-cli nodePackage The command line utility. If someone could give us some pointers we might actually have a crack at it ourselves ... Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-9b2ae468a0bb9c7ebe7d386ca9502d1a5cef2d03cd4f2b363afac4dcc6a5bf25","title":"","text":"Package name: mongodb-compass Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 1.43.0 Current version on the stable/release channel: 1.43.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-b0a53253d36a420b93a020a8434f628c169c37515fc496086657aa3735807eba","title":"","text":"Describe the bug For some reason neither of nix-env, nix-build or nix-shell compile Lean standard library, i.e. there are no .olean files. This results in abysmal performance even on trivial code, because every time it needs to recompile entire library in memory. Also, there is no leanstatic.a installed. To Reproduce Steps to reproduce the behavior: Expected behavior There should be compiled .olean files. Additional context Building Lean manually using compiles standard_library by default without issues. Also, there was no such issue on older NixOS. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nTurned out that compiling standard_lib was included in tests. Adding should fix the issue.\nExcept that 39 tests have failed :disappointed:\nThis patch fixes all remaining issues, which proves that in NixOS 20.09 expression for Lean is broken:"}
{"_id":"doc-en-nixpkgs-b272f9ed8becbb4c110392ecddfe718f87189c5bb71bdc4e08d836a303659c01","title":"","text":"Describe the bug I'm unsure what the error is, but it seems to relate to ulauncher being unable to find the project path, whatever that may be. To Reproduce Steps to reproduce the behavior: Expected behavior For Ulauncher to start normally Additional context This is the error message I get: 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(miyuki): nixpkgs: Maintainer information:\nSee the PR linked above. The issue is that the ulauncher package must be installed via , , , or something similar. Using does not work (for reasons explained in the patch). The PR both updates ulauncher and adds a note to explain what's going on to Nix users trying out the package. I think it would be a good idea to create a NixOS module for Ulauncher. I might be able to do this after I finish exams in a couple weeks.\nAlright guys, the real solution here is to just use rofi. With a little work you can make it look pretty good and with a little extra work one could easily make it look similar to ulauncher. Here is my config I tried to fix this issue up but it seemed to work for maintainers thus it was the end of that story\nHello ulauncher package maintainer here. This definitely shouldn't be the end of the story. I do want to get these issues fixed. The problem is that ulauncher wants to store paths to its assets in a config file within . Typically we'd just let it use paths for everything, but that would cause ulauncher to break if we update the derivation then garbage-collect the old paths in . I also use Rofi right now, and it works. But I really want the plugin ecosystem of Ulauncher, so I'm motivated to fix this situation. Perhaps we could modify the current package to allow decoratively specifying the file contents (like ), which would allow the package to be used without messing with system state? Maybe we could even create something like and a NixOS module?\nPerhaps this is a good fit for a home-manager module?"}
{"_id":"doc-en-nixpkgs-f16059bf2f4eb83fd48faa0f7060c43bd86ee9755105fd41a8bb918c33fae14c","title":"","text":"In any case, this issue can probably be closed once is merged. Maybe a new issue should be opened to track the addition of an unlauncher module?\nI marked this as stale due to inactivity. &rarr;\nbad bot\nI installed (rev ) through . Unfortunately, I get this error message on launch anyway.\nsame issue here"}
{"_id":"doc-en-nixpkgs-09525a8853c2fb75b12c5348aef5253e0705d0956c84c9129bd0c54760a0bce2","title":"","text":"Describe the bug Doesn't build. To Reproduce Steps to reproduce the behavior: Expected 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 system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-581d60c131c0f1440cd8a069f8b5437a452670b129831a0ae49f74bfa6ed4458","title":"","text":"Describe the bug qtwebengine fails just after successfully configuring with error message To Reproduce ` Expected behavior should compile Notify maintainers Metadata\nPull request works on my machine. Thx."}
{"_id":"doc-en-nixpkgs-ba59712a1c3baef6d8528e4fef0a13a683420f6eb8941fd6ba7dd70ed5e02646","title":"","text":"Project description Enables common unix utlities like cut, awk, wc, head to work correctly with csv data containing delimiters and newlines Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-94f6172f3d1f0f2ce94806480d9eadf95659c97bc303e10b981f0da71a2b0324","title":"","text":"Buck as installed via nix reports with an older release version than the one listed in its nixpkgs My guess is that is probably the correct version. The issue here is that IIRC buck Expected behavior 's output should match the version rerefenced in the build file. Notify maintainers\nI did try to investigate by bumping buck to its latest release that should be Python3 compatible but didn't get very far as I am unfamiliar with the build system. But maybe the patch helps With this I encountered a failure at the end of the build\nbuck now generates a hash for build outputs"}
{"_id":"doc-en-nixpkgs-c4713581c810fca693c398c0e426cb9f6c6026edd1c96b53571bceaeeb8c959e","title":"","text":"Package name: pulsar Latest released version: 1.117.0 Current version on the unstable channel: 1.114.0 Current version on the stable/release channel: 1.117.0 Notify maintainers"}
{"_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-bfb4e8b9db14d10f329721576c2eb8d6ebb4147bb69b55501afc4c9f82bc23fc","title":"","text":"This tracks the conversion of from DocBook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue."}
{"_id":"doc-en-nixpkgs-2a28a6160df27b3c04eb80056b1a7daa9b1784c9b2d0fb9875f7299786c71650","title":"","text":"This tracks the conversion of from Docbook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.\nI opened a PR for and : PTAL, thanks in advance for reviewing :-)"}
{"_id":"doc-en-nixpkgs-5d48828c4107043be82104395b86e2327476b09958ad079aaae58dad34206ff5","title":"","text":"Project description Ente's 2FA app. An end-to-end encrypted, cross platform and free app for storing your 2FA codes with cloud backups. Works offline. You can even use it without signing up for an account if you don't want the cloud backups or multi-device sync. Metadata homepage URL: source URL: license: AGPL-3.0 license platforms: linux, windows, android, ios, apple silicon macOS, web Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-546ecdbe4ca6741d939dac7f381e42dfa2ba3f46b32a2979d756b488ba50762d","title":"","text":"Describe the bug has , preventing it from being used on other platforms, particularly Darwin in my case. To Reproduce nix-shell to get this error: error: Package ‘postgis-2.5.2’ in is not supported on ‘x8664-darwin’, refusing to evaluate. Expected behavior Produce a postgresql-and-plugins package with postgis available. Additional context Simply allowing doesn't work immediately because PostGIS' build system is quirky. There was some relevant-looking discussion on . Metadata system: host os: multi-user?: sandbox: version: channels(lukeworth): nixpkgs:"}
{"_id":"doc-en-nixpkgs-8f9e2da9f58a29e72ef4d394f307be0154b903949d3e0443aa2485e1f46eaec7","title":"","text":"Describe the bug Mailman module in NixOS requires postfix enabled and has no way to configure Mailman to work with other MTAs supported by both NixOS and mailman upstream. To Reproduce Steps to reproduce the behavior: postfix mailman the evaluation with an assertion Expected behavior The Mailman module allows to select an MTA of choice (or even adapts to the currently enabled MTA) Screenshots n/a Additional context Notify maintainers cc Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(vika): nixpkgs: Maintainer information:\nIt looks like exim's configuration should be RFC42-ised first if we want to inject Mailman-related settings into Exim config, which is a requirement (Mailman requires a custom Exim router and transport).\nYes, the module is currently quite opinionated. If you're willing to contribute exim support that's great.\nI see how I could make it work, but the first version of it will require manual editing of Exim's config files (because RFC42-ising Exim will be a pain, even though I have some drafts on how to translate Nix into the syntax that's required), and I'm not sure if it will be merge-worthy enough :3\nExim config is complicated enough as is, I'm not sure adding an intermediate layer from nix will help that much. I also don't really see this integrating well with existing or other exim config. I'm honestly kind of surprised this works for postfix."}
{"_id":"doc-en-nixpkgs-4a7a5e3e606c4c2af5087ea2579ad5d539afa299a11f45be25e306f1b61ca000","title":"","text":"Project description As discussed in is now EOL and the dev's have moved their effort to . As per the in order for it to work specific need to be set up. We can probably do something similar to what we do for the expression: Metadata homepage URL: source URL: license: GPL3 platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nFor people who subscribed to this issue: I opened to add streamcontroller"}
{"_id":"doc-en-nixpkgs-3b98f871c023d91a37889c463903eaf3897333ddc6902c22919df70912b7749a","title":"","text":"Yes. We have a package which is what I tried, but since it’s a thin wrapper around it’s possible that it’s still not built with the right options. Also I’ve noticed these messages from : does not show the extension, and GLX applications fail to start. Originally posted by in I probably merged , too early. I'm not totally sure this is working properly.\nThis is pretty much a help wanted because I lack the depth of knowledge and hardware to help anymore with Nvidia things. My goal with finishing was that it could be possible and improved upon. i.e packages are built with the capability etc.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nThe last few evenings, I have tinkered around a bit. I was not successful so far. Here are my findings: I have set the following options: This page says that there is no acceleration support for xwayland and nvidia yet but glxgears fails to start, so I think this is another issue There are multiple versions of : One from the egl-wayland package, the other from nvidia-x11 package. As the one in is loaded, I tried to replace it with the one from egl-wayland. Though, the result is the same with both. When starting an application, which would use acceleration, I can observe this line in the kernel log: Using , I can see that is accessed, though one of the calls fails: one more thing: looking at , gnome-shell is listed. Maybe it has working acceleration? Edit: Got a bit further: Found a reference to an additional directory, which is used to look up libraries: Creating a file in there: with the file in /run/opengl-driver/lib/libnvidia-egl- being replaced by the one from egl-wayland package. Now the error in xwayland is just a warning: I can run a wayland native terminal, but still fails If you have any suggestions, what to try next, I would be glad to give it a try.\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."}
{"_id":"doc-en-nixpkgs-1b2c4fabd380e4d2d549094e15b3adba92e0ac86bf631b3edba3cc0fc9da2dc6","title":"","text":"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'm trying to get this working as well. However I can't even get the session chooser in GDM in 20.09. Is it only working in unstable? Any tips? Here's my config\nWith this overlay and the 470.42.01 driver, nvidia is usable with xwayland. :tada: , unigene-valley and so far every game I started on Steam. Only issues I have so far are that chrome does not start properly Workaround is to start it with some options: and in CSGO there is noticeable input delay.\nI've updated to the latest nixos-unstable () which includes updated & , but I'm still facing issues. While it's generally working I have problems with some apps. : : : Additionally in my system logs I can see: & are both working. My relevant config: I also tried using an overlay to apply the new meson flags from overlay: Is there anything else I need to set up?\nalso fails with\nI have a very similar setup as and am experiencing precisely the same errors. I'm not sure whether it's an issue with gnome, my particular config, or what. Things work fine when running in an X session.\n:thinking: I don't see anything missing with your config . I have updated my config to and removed the overlay. and are producing the same errors, and chrome won't function properly unless started with and are working for me, as well as and and . Note: Seam is installed via but this should only be relevant for running games inside steam, not steam itself."}
{"_id":"doc-en-nixpkgs-88f4183a0e0931d860f4061479982e8b10374969e71d8c5899f6ca1823af1bdf","title":"","text":"I came here because I'm experiencing the same as and Can't launch Steam or Kitty under Wayland: nvidia: 470.42.01 xwayland: 21.1.2 Config is virtually identical to\nI found this issue because I had the same problem as After reading , I tried to create a different file (listed in the end). And that solved my problem. With this file, I can open steam. However, alacritty still has an error. Maybe that relates to another . The cause of this problem is that even though both and packages provide , cannot be found without a json file. The says: So, maybe we should add a json file /usr/share/egl/eglexternalplatform.d /xxx.jsonnvidia-x11egl-waylandlibnvidia-egl-wayland.solibnvidia-egl-, gnome setting says my video card is \"Unknown\". In the end, I will post my related config:\nI filed this issue to see if we can patch to look in the right place: If we can't get it to look in then we should probably just add the etc symlink in the nixos module so that this works correctly for end users out of the box. I'll send an initial PR shortly and will update it in that egl-wayland issue gets a useful answer (or if there's another way to patch a closed source SO that I'm not thinking of).\nBTW, I can confirm the different results. When I override nvidia's with our \"upstream\" one, I get more info in , but I'm not sure if there are other functional differences. Not sure what I would've expected, but it nags me that there's a difference.\nPR:\nInteresting, there IS a way to override the egl_externaplatform search path(s):\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nwould this still be an issue after ?\nI think it needs and\nI am taking over as I've been using that setup as a daily driver and have a rough working understanding of the pieces fitting together. And to confirm, the general problem here, that is addressed in , is EGLStreams working in Wayland environment with the NVIDIA driver (aka, it doesn't now because we don't \"wire up\" NVIDIA's egl driver per egl-wayland's expectations)."}
{"_id":"doc-en-nixpkgs-81ffb849edb4d41eec15cf04e164714ef9722a6f53509b340d6203b4425c1d76","title":"","text":"That is pretty tangential to NVIDIA having a driver that supports GBM allocation and \"wiring it up\" (an extra piece included in ), and it being discoverable (whatever I send to replace ). Hope that helps.\nAlso, to reiterate, is good to merge independently on it's own and will resolve this issue. Separately, a replacement for will be necessary for the ideal Sway scenario without users having to set an extra env var.\nI thought the point of the new Nvidia driver was to finally move away from EGLStreams? Is EGLStreams used by the new stable driver at all?\nI don't know? It doesn't really matter, we should still fix it? Like, the fundamental issue is that we're simply not installing the Nvidia driver correctly for NixOS when it comes to these important configuration JSON files. Plus, it's not like everything is going to immediately switch to GBM, drop EGL, know about the env var, on and on. That, and the wiring for GBM is in that PR and I'm not splitting them apart at the current merge rate."}
{"_id":"doc-en-nixpkgs-f9e92c0c9d5c73a4ecaea0839a8297283ab86a45df389dfde856e12c81abe24e","title":"","text":", CVSSv3=6.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc\nI couldn't get the vulnerability to compile and run, so I don't know for sure whether this version bump is actually a fix. Nonetheless, here's a PR."}
{"_id":"doc-en-nixpkgs-91620aab9c7889b98418c0353af14ece83171076467dfeaa2dee48fb58b9eacd","title":"","text":"Describe the bug Build fails when trying to install . I get: To Reproduce Expected behavior The package should install without error. Metadata Maintainer information:\ncc\nRelated to\nTried the following: It doesn't even bother about the C-core Version 6 that I asked: What am I doing wrong ?\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 .\nRefreshed. My PR will fix this issue. Thanks for your patience."}
{"_id":"doc-en-nixpkgs-03150474e642c19f599ad623573b49db818115a1d92547d0ee2b41d63e0f8641","title":"","text":"Describe the bug is currently in nixpkgs master. It was released in July 2018. was released in October 2019. It contains a few improvements and may also contains fix for some vulnerabilities: Is there a reason to keep the old version in nixpkgs, other than a lack of manpower? I'd be happy to do this work, but I just want to be sure that I was not starting a long, difficult and redundant work. I already tried a \"naive\" bump of the and but it does not work, mostly because most of the patchs are not valid anymore.\nThis was solved by cc.\nThank you for continuing this work!"}
{"_id":"doc-en-nixpkgs-9f1d4fc6da948eb14a91f50c9b03ce0858f6e91b393998688e5f7a9fc52fd48b","title":"","text":"Project description ET: Legacy is an open source project based on the code of Wolfenstein: Enemy Territory which was released in 2010 under the terms of the GPLv3 license. Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux, darwin\nI got a derivation to work: This is for the 32-bit build, client only. Run and use the binary. Planning to properly package it and contribute to nixpkgs, but since it's my first package it'll require some more time. Also planning to get the server and omnibot working.\nI marked this as stale due to inactivity. &rarr;\nStill interested.\nMy version of derivation gist doesn't seem to work now that I've upgraded to NixOS 22.05. Haven't had time to investigate too much yet. Whether I try to join an online game server or host a game, I get the below error:\nThis adaptation of gist is working for me. It's currently for the 32-bit Linux version only, so produces a package . There is an option to use the mod libs built by the ET Legacy project (CI pipeline) or compile them locally.\nHi guys Based on gist I did compiled using NixOS VM Machine it runs fine but there a small quirks there Date is not set correctly it is set to beginning of the time :D Also does ignores manually set env variables ?\nAdded those 2 in etlegacy*.nix files ` Those 2 should fix issue with correct compile date and naming scheme to build non package But it does not Am I doing something wrong ? :D\nPackage created and pull request created. Just waiting on PR to be approved so the package can be to nixpkgs.\nIs it normal I cannot find the package in the unstable channel?\nI think there may be some delay as it migrates to the unstable channel, and then into 23.05.\nit seems to be in unstable now."}
{"_id":"doc-en-nixpkgs-3bc960712609c6cb235449a1f475947d5de6db07dbd43c898ee8b6fb2370a693","title":"","text":"fails to install on . It worked before the recent update. It fails early on in the check phase. I'm guessing the fact that I have to build it from source at all is because it also fails everywhere else, so there's no cached build to download. Try to install on system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nHmm, the tests worked just fine for me on\nDo they work for you now? What's kinda weird is that I never get an error message or anything. You see in the output I posted above, there's just loads of dots. It kind of sits there printing dots for a while and then it looks like it just times out or something.\nFor what it's worth if I put in the derivation, the resulting player is perfectly functional at least for my purposes. Haven't tested every feature or anything though.\nI think it crashes during the test. I will try bisecting.\nBisecting was inconclusive because I ran out of resources when building webkitgtk.\nWhat commands did you run? I have a server with plenty of resources that's just sitting idle at the moment, I could try run it on that.\nbut I guess it might make more sense to skip the builds where dependencies failed by running something like:\nCool, I've been running this for a while, for what it's worth it's currently narrowed it down to between and .\nI'll let you know in the morning when it's finished.\nThe original bisect command I ran didn't take into account the case where dependencies failed to build, so I had to run it again with a script like the one you suggested. Here's the output of :\nFWIW I managed to build it by setting in an overlay. Works for me, but I wouldn't suggest that this is done in the Hydra build of course!\nYeah, we should probably add in the expression if this still occurs.\nI get quite a bit further, attempting to build rather than . The entire test suite finishes, then reports three test failures related to icons and GTK / GDK.\nSeems like the tests are failing again\nI marked this as stale due to inactivity. &rarr;\nEDIT: Kindly ignore this comment, didn't notice that I was using the deprecated repository. Hi, I'm encountering the same errors as reported previously. In case anyone else is experiencing the same, I was able to fix them using:"}
{"_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-7c4a032f50555756fe5ca48ed7f1a8ad5ba03b46b2f72bd70041526d9381a74c","title":"","text":"segfaults on launch Game runs Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI noticed this as well yesterday running nixos-unstable"}
{"_id":"doc-en-nixpkgs-c21b394ebf31b86e5786cce424b48c9cdfc687cffa7b4dbfff0f24ee7318c03c","title":"","text":"I would like to use to encrypt my home directory. is already packaged (as , for some reason) What's missing is the PAM setup (). Given that exists for EcryptFS, I would like to request support for via the option, or something similar. I am aware that EcryptFS is available, to achieve the same goals, however it seems to be considered deprecated by other distributions (, ) and has some which I am not comfortable with.\nThis is just to say hi and to share that I too am interested in this feature\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-12a01423512b043ab073d14404728750ed2f734df054328f396c91f2b142f47b","title":"","text":"Buck build system is packaged with the wrong JDK it seems PR introduced a bump in JDK version, see (). Metadata Please run and paste the result. Maintainer information:\nI guess the most recent version should support java 11:\nUntil they make a stable release with those changes included, we will just use jdk8"}
{"_id":"doc-en-nixpkgs-d48e9c4789c3fdac810c1dea25f173f41b051d7a0c2ff16bd686fab4ff00924c","title":"","text":"A clear and concise description of what the bug is. Steps to reproduce the behavior: to or -build switch to install android-studio android-studio and open one project the right-top button to sign to Google will open a dialog show nothing happened android-studio can open the default browser and success to sign in google. ! 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.\nThis is the same problem as , which I'm experiencing. Clicking documentation links from within Android Studio does nothing other than showing a jumping icon of Firefox besides the cursor for a few seconds (on KDE Plasma, X11), while it's expected to open the page in Firefox."}
{"_id":"doc-en-nixpkgs-4639429f1ec11d83cd05f454edab1c0096d4ee81604e41452b5a7c8503f1ba3a","title":"","text":"Project description WebUI service for Large Language Models Video demonstration by : .. basically self-hostable ChatGPT-like service Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin Additional info Follow-up on for open-webui nixos module. There seems to be an ongoing work on the subject by and on Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nRelevant Merge Request:\nJust for reference / workaround here's another nix package:\nThanks for that reference. That pdm tool workaround looks a lot more maintainable for the Python backend. Maybe i'll have time to try another PR in the next weeks. In the meantime and as a much simpler UI i packaged as part of PR It would be great if someone could review it.\nI would like to mention that in the latest release switched to , I am not sure of any straightforward way to do this while packaging it for .\nI just tested your flake, it's impressive, especially the nice UI at the end showing all the processes ! Regarding open-webui, it would be so nice to have that in !!!\nThank you, planning to have more UIs and devShell integration (for CLI tools that interact with ollama). I would love that too! Although there are a few challenges (like the one I pointed above regarding ), I am willing to contribute here. Also, maintainers are quick to respond, in case we need any upstream contributions to make it happen."}
{"_id":"doc-en-nixpkgs-146da02b6d8147b961d73ae2270ce223ba659c6a1f1953ea75b2a08db1020be2","title":"","text":"The recent changes seem to make sage crash when it tries to run some code using openblas (I think). I installed the sage derivation from the latest github repository. In the sage interpreter, run the following sage crashes with the following message: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(okideal): channels(root): nixpkgs:\nProcedural: as it is , please specify the CPU model. Looks like the Sage build system had the idea to use somewhere… I.e. the local build could work. I wonder how feasible it is to find where Sage does it — the Sage derivation is allowed to rebuild a lot of dependencies because it is just too much pain to make it use the system versions.\nHere is the output of lscpu\nFrom the traceback it presumably crashes here: which is which indeed is an AMD-only instruction (MMX? thought that would be long obsolete by now...)\nYou were right. A local build works fine. Thanks for the help.\nThanks for your report. do we set to and give up?\nThis should be fixed by exporting (see ). I'm not quite ready to give up (even though it would probably be the healthier choice :grin:). I'm actually currently experimenting with doing it the \"right way\" and replacing the sage buildsytem with nix (with a mix of sage and system dependencies).\ncan you confirm that the latest binary works?\nSorry for the late answer. The binaries from the master branch seem to work. The initial crashes are gone and running gives only unrelated failures. Installing from still gives me the old, faulty binaries though.\nAre you sure you updated the channel? What do you mean by \"binaries from master\"?\nI meant that installing from the master branch of the git repository works. I was not aware that there is a difference between nixos-unstable and nixpkgs-unstable. The latter does not seem to include the fix yet. Installing from nixos-unstable works well. Thanks for your help.\nOkay, I guess hydra is a bit overwhelmed by all the fixes for the upcoming release. Thanks for reporting."}
{"_id":"doc-en-nixpkgs-8b01fb728282f18b4a39a8c93e86c8a55a69a266c8dbf55955f9ab1f18ecf31e","title":"","text":"Project description Unofficial source port for Blake Stone series (Aliens Of Gold and Planet Strike). Metadata homepage URL: source URL: license: mit platforms: linux"}
{"_id":"doc-en-nixpkgs-9872372b693ccb87bd79375bf723544c54de4801ae08eedcc476d77ab411f39a","title":"","text":"error while building using unstable channel trying to build a system using weston pkg building successfully I assume its an easy name swap changing \"libseat\" on 4th line to \"seatd\""}
{"_id":"doc-en-nixpkgs-def4076a762f795e229191d588d8527e60ce2a936b083188a5651f53d32efb21","title":"","text":"Describe the bug The uses the following source definition to build (in ): This source is no longer available, returning an HTP 302 redirect to a new homepage: Navigating the new home, this seems to be an alternative download location: However it seems to be a different file (warning, very slow download, file is ~ 140M in size): To Reproduce Steps to reproduce the behavior: -shell -p cups-kyodialog3 Expected behavior Packabe builds properly. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(marc): nixpkgs: Maintainer information:\nI was slightly wrong because I don't understand how is supposed to work; it is the same file. The following works for me: I had to add the URL fragment to get to extract the file though.\ndoes kyodialog3 works this way? Could you create a merge request?"}
{"_id":"doc-en-nixpkgs-4410cac6d59c32e82b10437c10320ba209ca9c679157da30abe7192487f06b88","title":"","text":"Describe the bug From IRC: ; Looks like we currently just use their appimage: and our appimage tooling uses buildUserFHSEnv: It seems like we can either: using (build from source, maybe?) similar to how iohk patches Daedalus.\nI tried packaging it with yarn2nix, but stumbled upon , unfortunately.\nI don't know much about the appimage architecture. Why exactly can we not run appimages natively without FhsUserEnv? Is it just because binaries linking against fhs paths? In this case we probably could run autoPatchelfHook on the contents of the appimage and produce a new image that links against nix libs. EDIT: I just tried this. Extracted the appimage contents, patched all binaries, but then when executing ledger-live-desktop, I'm getting: Currently I'm running ledger live via qemu + usb device passthru via . That works fine.\nhow difficult would it be to lift Daedalus's patch and use it for the libudev inside the fhs? I've never worked with FHS before, but also don't want to build ledger live from source...\nI tried to build ledger live from source and it didn't work because of the issue that mentioned. Patching libudev worked though.\ncan you link to the patch? It would be great to be able to use my more-trusted nixos machines for these types of activities.\nI already created a PR for it and it's referenced above. This one:\nFeel free to comment in the PR whether it actually works for you :)\nThe patch had to be re-done in Should this problem probably be communicated to upstream, so we can think about how to fix this long-term in a more sustainable fashion?"}
{"_id":"doc-en-nixpkgs-ced4e1a7fe6a3ecdb00ede28a2dff5e6a9f4040c25dbd3110adcca7cd6c31a69","title":"","text":"Describe the bug When booting with ZFS legacy mountpoints like this: the boot fails as described in this post: To Reproduce I guess this is difficult if not anyone is having this issue with legacy mountpoints, but it seems that in the linked discourse post, I'm not the only one with this issue. But I've tested it just on this commit: where it fails, and on this (just one commit before): And there everything works. Expected behavior Mounting of legacy ZFS mountpoints succeeds while booting. Notify maintainers <!-- Metadata Please run and paste the result. Maintainer information: --\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nCan you check if this is fixed by ?\nI tried with this overlay: Not sure if that's the way to do it, but it didn't work.\nit should probably be\nThanks I tried that, and it didn't work. Not sure how to confirm the patch got applied properly though.\nif you have the log output, you will have something like:\nGuys, just to report, I'm in the latest zen with ZFS 2.0.1-1 with encryption, unstable channel and I'm not having any problems.\nI've just found time to test this, thanks for the research. The patch did indeed fix the issue for me! (I've checked the log output for the application of the patch). For the sake of completeness the overlay I've applied (needed a slightly different sha256 sum for me):\nCould you make a PR adding the patch to zfs?"}
{"_id":"doc-en-nixpkgs-82210125eb24cda451b756c29cb8a898b946a37b0b94e19d73e5acc1ba8e286b","title":"","text":"A clear and concise description of what the bug is. The package doesn't include a folder. I am looking for a version of which includes the executable. Are we building the package incorrectly such that it doesn't include a binary? Any and all help/advice is much appreciated :bow: Steps to reproduce the behavior: output - notice there is no folder A clear and concise description of what you expected to happen. I want the executable. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- might know something about this? :man_shrugging:\nwas the binary there before On a quick note: I have never used , so I am not familiar with the package. It seems that the package also needs an update:\nIt appears that the binary requires AMPL, a commercial package, which is not packaged in nixpkgs. See: https://coin-\nah, I understand. Thank you."}
{"_id":"doc-en-nixpkgs-08aa466a727de72a66e9122a9279f01f4e917643298641199c547b24c20b576a","title":"","text":"We've had issues with building atom-beautify since This happens now in both Atom and Atom Beta channels. Error for Atom: Error for Atom Beta: Travis CI for your fork Travis CI or a Docker image for nix and checkout master from atom and atom-beta Last successful beta/stable build: https://travis- Last successful stable build: https://travis- Both failed: https://travis-\nhere is a new issue.\nSeems to be related to\nFor stable maybe, beta is slightly different error."}
{"_id":"doc-en-nixpkgs-1c87a9fdc97e77fbe252c63249e7741e98e444845c1efd3826d704f3423ca77f","title":"","text":"The default boost version has been bumped from 1.69 (or 1.75) to 1.77. This is a notice for maintainers that the following packages are now failing to build: - - - - - - - - - - [x] cryfs A typical fix would involve pinning the package to a specific version (e.g. see )\nMy fix in is not the same as . Is there a very good reason to prefer one over the other ?\nWell, I like trying to keep it away from the huge top-level file. (which is e.g. harder to use in git)\nRe. pivx, I think we should mark it broken. Our current version is very old (and therefore useless), and the new version includes a rust build. I don't have the capacity to fix this ATM.\nIn my case, what broke it was the update from boost175 to boost177. Fix is in .\nIt's in the branch now, so please target any further fixes there as well (unless they're a mass rebuild, etc.)\ncolobot fixed with\nFYI, ledger has some broken behavior with the new boost version, although it curiously doesn't cause a test failure: ledger/ledger.\nOur expression does not attempt to run tests.\nAh, that would be why, thanks. Nevertheless, the binary exhibits the same problem described in that issue in interactive use."}
{"_id":"doc-en-nixpkgs-b49fc10ecb92dcefb6932360638ef5f8b54d4599524a843214d8797f0523e3e6","title":"","text":"Project description A cross-platform Discord Rich Presence integration for mpv with no external dependencies. (MPV Userscript) Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, windows\nI've already but haven't PR'ed this to nixpkgs yet. Will probably do this when I get home from vacation next week."}
{"_id":"doc-en-nixpkgs-d7f5a69f073c94108ac4fefffe5d8aeb3934c608210071b1e24c43352f0378a3","title":"","text":"Steps to reproduce the behavior: shotwell from latest nixos-unstable I simply install shotwell with . Noticed that often updates this derivation, last time it was changed by but I don't think his change would cause this. Otherwise - meta.maintainers is empty. Please run and paste the result."}
{"_id":"doc-en-nixpkgs-e6d29004b9ae4ef54fe6c9471a2ed00e858f19c4fd1e60ac3075386a3d20c3cc","title":"","text":"Enabling services.hardware. (as a systemd service) breaks. Steps to reproduce the behavior: error about and several other errors like \"has not been declared\", \"does not name a type\", etc. To rebuild xow and everything else without any issues. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nThe git not found problem is not fatal and the derivation overrides the version info anyway. Looks like another victim of our stdenv compiler upgrade. Looks like upstream master has a fix for that. Upstream is also orphaned so upgrading the derivation to an unstable revision is going to be needed in the short term and in the long term a replacement should probably be found. I don't have a working controller to test xow with any more so if someone wants to adopt the package, feel free to."}
{"_id":"doc-en-nixpkgs-bcfb9c3fd3b0292725947d57a76c9f76feccda2d71b26491b38ce25cd954ac35","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]:"}
{"_id":"doc-en-nixpkgs-fd392d4314403089c8bb330219e13d636f77fa72013d8355a04c862612c5eb17","title":"","text":"Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-000b5e0422e8df6969c79251d9cde1d90b2f0d3151ad0c02602dfaaccfb6e58a","title":"","text":"rendered in : ! bumping osl to did not work. Applying did not work <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- system: host os: multi-user?: sandbox: version: nixpkgs:\nI have verified that the problem exists with the current derivation even with version , which was updated away from in . I guess somehow the ZLIB_VERSION is replaced improperly , but I've got no idea what could be causing it, and I'm really confused why it's only become a problem recently, as it doesn't look like osl has been touched in either.\nI've tracked it down to , and reverting it seems to fix it. I also believe it's a cmake issue. Consider this file Output: Maybe because the header changed to (? But if I'm reading the correctly, I think it should just set the version to an empty string? Either way, this patch seems to fix it I don't think it's worth raising with zlib because with the next patch version they're going to fix it anyway. It might be worth warning them in advance of 1.4. It's probably worth raising with cmake, because they will want to support all version, and then zlib won't have to care anymore either. I can open a PR for this tomorrow or when I have time, but don't wait for me if anybody wants to do it before.\nNice catch! One minor note: you are looking at 's master branch. It seems to be already fixed there as: We'll need that backport to . UPDATE: or wait for to reach master. With now is in ."}
{"_id":"doc-en-nixpkgs-22f64b3bd50829df020efc6ddfbd69ace6610410a34c8d9c10b3d23b9ff393a7","title":"","text":"Project description Converts Linux images and kernels into UEFI images. Metadata homepage URL: source URL: license: GPL3 platforms: Linux"}
{"_id":"doc-en-nixpkgs-2a5126e6f9562e43052264a7fa66b701ec05c980453d6db5fe756e177f14fa26","title":"","text":"In , I introduced support in libvirtd for UEFI VM creation. rightfully remarked that this brings closure-size up too much. Looking into OVMF shows that only 1MB out of the 114MB install size is needed to enable said UEFI VM creation. I think that we should look into splitting out OVMF_(CODE|VARS) from the rest package."}
{"_id":"doc-en-nixpkgs-e70f43ef7398225088613a3b14199ef5663d6d4da811d62d922eb8c4a037ab5a","title":"","text":"Describe the bug failed to build on master. To Reproduce Steps to reproduce the behavior: nixpkgs master 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. system: host os: multi-user?: sandbox: version: channels(root): channels(oxa): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-39a63796733715311f147619af592756a43a3aea82f511469a2a87770698ad8e","title":"","text":"Possible, because X11/xkb/rules/*.lst [0] are somewhere 'hidden' in the /nix/store. [0]\nFixed, just let me do some updating on E19 libraries and I will make a pull request."}
{"_id":"doc-en-nixpkgs-9f5bc20cabfb384816ae19590c2f8bd63ed99172db57b185c1d1a1ba968d240c","title":"","text":"When trying to install , the build fails with: To reproduce, use the following and run it with : I think this happens because of the symlink of the , which seems to be resolved while running the build and in that case the symlink target does not exist. /cc btw: could you please also add support for the latest beta / dev / stable releases?\nHey it's fixed in the latest commit. Can you try it ?\nWorks fine, thank you very much for the fast fix!"}
{"_id":"doc-en-nixpkgs-dd749394ca6f9ef8dec044c1f97ed1031c2283da667ca4fc89f0ac2387af4dc8","title":"","text":"Easyeffects crashes when Echo Canceller is used (at least when applied on input). I've been told that it works fine on arch linux. Though it might be my hardware that somehow makes it crash. Steps to reproduce the behavior: Echo Canceller module to the Input Easy Effects to one of recording apps It doesn't crash It doesn't write anything useful in the logs, just exits with code 137. Please run and paste the result.\nI can reproduce it but it is not a regular crash – there is not core dump. It appears to be killed. Weirdly when I run it with: The termination is not caught.\nFor me it reproduced with gdb: Maybe it's terminated when child process is crashed?\nhmm, it seems to be something wrong with speex when configured to use the fftw library... not sure what, but this doesn't crash:\nThe same also happens in Speech Processor effect now:\nUnfortunately this didn't seem to do the trick for me, it still crashes with the Echo Canceller.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI have the same problem. The thing is, used to work OK on my system. Then I tried the module, after which this issue appeared. However, now it's persisting. I undid the change, even tried booting into old generation, but is still getting killed with the echo canceller on. For reference, this is what I used to try to enable the echo cancel module (not sure if it ever worked):"}
{"_id":"doc-en-nixpkgs-f372e129959372975f314d0d2a4149c963fcbea2a6b81a8bea8154c2aa05a241","title":"","text":"Describe the bug Neo4j does not start because it cannot locate a Java Runtime. To Reproduce On my system, I installed with: Then, running shows: \"The operation couldn’t be completed. Unable to locate a Java Runtime.\" Expected behavior Neo4j should start. Additional context Note that shows Note the line that sets to . 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-486e3920f9d1ab2186439cac7edc25b1091e16e58e06e7b558349de302b5cf92","title":"","text":"I just found out about wrapGAppsHook by examining a gnome package, but there really should be documentation about this in the Nixpkgs User Guide (a section about Gnome would be nice, which would show the right way to package GTK3 / GTK2 glib based apps). Also, perhaps there are other things I missed that one should know when packaging Gnome Applications or GTK3/2 apps? /cc Gnome maintainers\nI'd like to know as well. Currently receiving this error: On one of the packages I'm trying to put into nixpkgs. Apparently sometimes you need for buildInputs. So apparently all you need to do to use this is:\nThe error occurs when you do not have any directory containing in variable. One of the things does is (which usually contains the aforementioned file) of dependencies to . (Actually this happens in cooperation with via variable.) Icon themes work in the same vein, only is used and it is populated by which is propagated to (). (XDG fallback theme) should be probably to any GTK application that uses icons (I think that is every GTK applicaton nowadays due to CSD) but some applications require Adwaita because they use icons not in hicolor. Not sure if this functions correctly though, at least it should not according to my mental model of how icon theme selection works; I will need to read the relevant XDG spec before I can finish the documentation.\nJust thought I'd leave this comment here for future reference: if you get an error like for python gtk applications, try adding to propogatedBuildInputs!\nIt should go to , though. But be wary of"}
{"_id":"doc-en-nixpkgs-1cc1186132a030931019ec0b93a6c2f1715ddf193a6f4c5ccb3deb43d1900000","title":"","text":"Many Emacs packages, for instance mu4e, move their -files into a subdirectory of . Nixpkgs currently only adds all files located in to the load-path but does not add the files in its subdirectories. This currently makes mu4e from Nixpkgs unusable (by default). We have to fix this snippet of code: E.g. will not make mu4e available within GNU Emacs.\nI'll give it a try in a few minutes\nWhy can't somebody just fix mu4e instead of making emacs startup slower? Like make a wrapper for it like has for Agda or just put files into a correct place like package does? I see wanted to do this, but then changed its mind :(\nThis actually seems to be the default behavior for Emacs - at least for packages it ships with. See for an example or run to check the default value of (it includes subdirectories)\nI see. Okay then. Still, personally I would prefer packages to separate their emacs things into a separate package or at least a separate output.\nThis broke the package which have subdirectories that include \"non-public\" files, which gets required as the wrong package for , etc. See Perhaps this should be revisited? I am not sure if this potentially breaks some other packages.\nI have reverted this locally (or at least I think so, could be that the change was not propagated somehow), but still seems like paths are , I see a lot of projects test directories being to the e.t.c.\nHere is an example of bad load-path and this is just a subset of them all, nix-shell to reproduce:"}
{"_id":"doc-en-nixpkgs-a4df8bd7a3b26553227e58572ea86506f566d6d640cdaea47e177240fdf64804","title":"","text":"The derivation of creates a different .desktop file from the \"official\" one that has a different name. This is probably done in order to differentiate the two versions of in case someone installs both of them, but the problem is that while it creates a new one, it doesn't delete the \"official\" one. Also, the new .desktop file should also set , otherwise games don't launch in Wayland. (Though maybe it should be a wrapper instead) (And, unrelated, but why and not ?) The same also applies to PATH: there are both and (which is a link made by the derivation to in the folder). For consistency, there should be made a , otherwise if both dolphins are installed, one overwrites the other in PATH. Steps to reproduce the behavior: dolphinEmuMaster; an app launcher; are both the original \"Dolphin Emulator\" and the new \"Dolphin Emulator (master)\" that open the same app (the master one doesn't set `QTQPAPLATFORM=xcb). PATH there are both and (which is a link). There should only be the \"Dolphin Emulator (master)\" desktop file, and in PATH there should be only (and instead of ). <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --"}
{"_id":"doc-en-nixpkgs-1686e76734eced6537d75d03118e3c339e524148893b114b448178f1015704ea","title":"","text":"Darling is a compatibility layer for running macOS apps on Linux (think Wine for macOS). I think it would be interesting to work on with macOS support. They have reverse engineered some headers that Apple doesn't release publicly so having them in \"libdarling\" could be useful.\nWe already have this part:\nJust heard of Darling. I would be delighted if it could be used for running builds on NixOS!\nIt seem to be packaged by but only for macOS. If i understand the project correctly, that makes no sense. We want it on linux, to run macOS apps. Also, the package has no version. That's probably because they havn't tagged a version yet. So this is pre-alpha state software. could you update the package to the commit the \"stable\" AUR package uses and add a version as described here: ? Then we can close this issue.\nIt looks like the project has started using tagged versions:\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 .\nI'd still be very interested in seeing this , especially with the hope of future cross-compilation support\nThis would even make it possible to package Mac binaries for Linux!\nI'm interested in this so that I can test cross compiled binaries when running tests.\nI marked this as stale due to inactivity. &rarr;\nNot stale!!\ndarling-dmg is just part of . To be exact, it is included as a submodule in the source tree of darling. The darling build will come with kernel modules. It would need someone with kernel-packaging experience to pack it into Nixpkgs. Build instructions in the Darling Docs:\nI marked this as stale due to inactivity."}
{"_id":"doc-en-nixpkgs-749c8cbf56c60551b97231439afa3cf61a1fb97dcfb75a7a6dde8afed40ae66b","title":"","text":"&rarr;\nI'd still like to see this, though largely for much the same reason Andrew mentions at this point -- I've started working with zig and being able to test cross-compiled macos binaries would be brilliant.\nI have got most of a Darling build file running, but I have found an interesting issue. Wever I build I get the following error: From this cmake file: As far as I can tell, the command is a special MacOS thing, and I unfortunately do not understand CMake well enough to fix it...\nWell, turns out the issue is that Darling relies on git-submodules, and it looks like this must be built against the Git repo directly, not against the released tarball...\nWhat would therefore be a derivation?\nWhat do you mean It's just a with .\nI tried to re-package the prebuilt deb from darling GitHub releases. Here is the nix code darling- Save these 2 snippets as and darling-, then run . With 2 problems: needs setuid/setgid perms, while nix-build would fail if dpkg-deb -x executed directly. I use fakeroot to ignore this problem. always fails. I am not a darling expert, have no idea.\nAh, fantastic, thanks! Looking forward to having this in nixpkgs anyway, but let's see how we go there.\nIt could be named when entering Nixpkgs.\nGood suggestion. I've edited those two scripts.\nI got as far as finding out that darlingserver doesn't start with that script because it expects /usr/bin, so updating my to a version, the next issue was that darlingserver was trying to mount overlayfs on \"lowerdir=/usr/libexec/darling,up\" (may be incomplete, this is strace output) which did not exist.\nAfter a bit of tinkering I got Darling to build from source. I opened with more info. Please give it a try!\nIt seems that they now use instead of the kernel module. This would make packaging easier.\nWhat's the purpose of ? If it is only the sandbox part of Darling, a new name like would bring less confusion. Update: Opened PR to do the renaming."}
{"_id":"doc-en-nixpkgs-4b00adeb42101b412386966602b908aa36452c4b936db7237bdff4d9708cc7da","title":"","text":"Describe the bug Starting slack doesn't show the window in 8 out of 10 runs To Reproduce Steps to reproduce the behavior: Expected behavior Slack window should open Screenshots If applicable, add screenshots to help explain your problem. 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 system: host os: multi-user?: sandbox: version: channels(ymatsiuk): channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-386befad45a82fa0c7c36cc0d88b3a289cde006ba27de7b98e06b6b23546dcc0","title":"","text":"Project description CoreCtrl is a Free and Open Source GNU/Linux application that allows you to control with ease your computer hardware using application profiles. It aims to be flexible, comfortable and accessible to regular users. Metadata homepage URL: source URL: license: gpl3 platforms: unix, linux\nIt looks very complicated. I will look at AUR.\nsorry for the late reply thank you very much for looking into it :relaxed:\nWell, I will do what I can do. I am not a huge user and packager of such graphical things, but it looks an interesting project to take on. I will do some research."}
{"_id":"doc-en-nixpkgs-35f009bc9d4c9aedb02e0d2e5742627f7fe59429940355385553e2cd50d3ba61","title":"","text":"Project description qpsolvers is python library for solving quadratic programming problems. It contains wrappers for multiple solvers like osqp, cvxopt, quadprog and much more. Metadata homepage URL: source URL: license: LGPLv3 platforms: platform independent (python3.10)\nThis package wants new version of and new package - . I will try add PR today, but now you can use my NUR repo if you want:"}
{"_id":"doc-en-nixpkgs-710f58d16cb2010768a796cc9aeb6fcc9d664e50de6a6f37b0d22bbdb7fccc33","title":"","text":"In the latest stable release, the package fcitx5-openbangla-keyboard does not work. OpenBangla Keyboard package is installed but it does not integrate with fcitx5. fcitx5 crashes every time after logging in.\nHere are some screenshots. ! ! !\nThanks for reporting, will take a look.\n... Here is my !\nAny update? Thanks.\nfcitx5 crash log:\nI have forked the OpenBangla Keyboard from the develop branch. After the recent commit. it built successfully in NixOS. I am now using OpenBangla Keyboard with an overlay from OpenBangla Keyboard's develop branch. !\nI think change of these two lines according to this image will solve the problem. ( I don't know the correct hash = sha256, I just gave this and the correct hash was shown in the build error!) !\nThanks for looking into this. I've pulled the relevant commit and also tested at runtime this time, it does not appear to crash and outputs text properly."}
{"_id":"doc-en-nixpkgs-2ce1191a389387887d708517292e8d507aace598995442dc71ba60b9eac25a76","title":"","text":"openbangla keyboard installed from the unstable channel does not integrate with fcitx5. It installs just fine but does not integrate with fcitx5. Fcitx5 does not autostart too. OS: NixOS Stable DE: KDE Plasma !\nOpenbangla keyboard from unstable channel does not work in the unstable nix os installation too. Openbangla keyboard crashes fcitx5 and even if it is restarted switching keyboard layout says openbangla keyboard not available."}
{"_id":"doc-en-nixpkgs-a73a4367a99b8b1e57f334255c0c315709aed102f4694b84c01d34e252ebed32","title":"","text":"When you set , although it sets the CMAKE flag correctly the resulting package isn't actually built correctly as cmake can't find cuda so it unsets the flag. This is due to the incorrect usage of instead of when building the cuda related packages. The correct usage can be seen in the package. It also tries to build with CUDA by default which is wrong. Dlib hasn't supported fftw since however there are leftover references to it in cmake which might lead people to think it does support fftw. fftw should be removed. As mentioned in this it makes more sense to have as an input into rather that so that people can override it with other BLAS implementations e.g more easily if they want to. The package was also missing lapack which should be . Steps to reproduce the behavior: Build the package, it tries to build with CUDA by default. I made an example with a fairly simple nix flake that let's you switch between my patch and the original package. I have created a which fixes these issues. For it to build with CUDA. How CMAKE fails ! For this simple c switching from my fix to the original bugged package on 23.11 before openblas was . ! Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: Thanks!"}
{"_id":"doc-en-nixpkgs-d2699b4a2b715ec5ba8ea068301108f3a7b0bf075bba5d97316b57ecf9b8f7ba","title":"","text":"Project description Metadata proposed package name: homepage source URL: license: platforms: probably portable to all platforms which Nix supports. requires python3, exiftool, gobject introspection"}
{"_id":"doc-en-nixpkgs-d0830ad68267cfa1b9a600c038aad34db1e45b01d9c71a60d4c1552ab31ac437","title":"","text":"Reproducing is pretty simple: . The error is: system: host os: multi-user?: sandbox: version: channels(philipp): channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-e2c8ee84a213c18923e2d9aef55fd9e118160725d549506a7446a052ac7ba782","title":"","text":"to newer version to different directory as under postgresql user Output I get:\nThe NixOS service module for PostgreSQL, for some unfathomable reason, initializes new databases using a non-standard superuser role name ( instead of ). This makes it a nightmare to get to work right, so forget that. Instead: back to your old version of postgresql root, dump your entire database to a file somewhere: to the new version of postgresql root, read in the database dump: (you'll likely see an error go by about the role already existing, you can ignore this) For good measure I went and tested this upgrading a 9.2 database to 9.4 under NixOS, worked fine, the applications using it continued on as normal after the import. That said, the real issue here is: why are we initializing databases using a non-standard install / superuser role name?\ncc\nSee regarding the superuser role name.\nShouldn't we switch the default user to \"postgres\" on new databases and keep the \"root\" account around for existing-ones ? See\nI strongly agree we should switch the default superuser to . Currently, it seems impossible to use to upgrade postgresql databases due to NixOS using the superuser: simply refuses to run as root.\nThe approach given by above doesn't work for me:\nI can submit the change as a PR but don't use postgresql and it needs testing. Feel free to steal it and do the upgrade process with it.\npgdumpall tends to e pretty useless if you database isn't tiny_ :(\nthat would be a good start :)\nthere you go :)\nFYI: I've just tested migrating 9.2 to 9.6 using and it works flawlessly.\nOk, I think I found out why wasn't working for me, like I mentioned in It seems to be due to this line in the Hydra module: If I change the mapping to then the command works fine. But I'm not exactly sure what are the implications of doing this, or why was mapped to in the first place...\nIn case someone runs into the same issue as me, I am documenting the procedure I used to upgrade a PostgreSQL database that was being used (only) for Hydra."}
{"_id":"doc-en-nixpkgs-b9dc4ebf514fb65f87e5ffe43b99c1cff4c2a6713c5bf4a56d3c890aac684425","title":"","text":"I tried to follow procedure above, but as I mentioned before, to use as suggested I needed to change the PostgreSQL user mapping in the Hydra module as specified in my comment just above this one, otherwise I would get a message. However, to read the database dump back into the new PostgreSQL installation I had to change the user mapping as follows: ... and then, after activating the configuration, I needed to run the command in the following way (as root): After doing this, the upgrade from PostgreSQL 9.4 to 9.6 seems to have completed successfully.\nRelated\nIf anyone else stumbles on this, pgupgrade seems to work now. I realized after upgrade that my db got reinitialized, so steps for me were much more brutish than that post, but in a nutshell: with new postgresql running, clear whatever got reinitialized (pgupgrade won't run if there are data around, but won't tell you what to remove... lists databases, don't know how to list users, I guessed) drop database whatever; drop user whatever; stop postgresql.service figure path for old binaries, e.g. and copy it somewhere. run the actual pgupgrade as user: restart the postgresql service if all went well after some testing pgupgrade suggests removing the old db with (disclaimer: Don't blame me if that eats your data)"}
{"_id":"doc-en-nixpkgs-519c4e91a9b5dbd968fa5be8b65f8ceabf6f7c68a90fc1e3027974a94fccb7a8","title":"","text":"I get errors like: This shared object is provided by derivation, not i.e:\nJust some additional info: using the wrapper script provided by doesn't solve it either.\nI would like to hear from someone more experienced, but maybe an aggregate package (like for texLive) could solve this.\nYou are right. I was talking about the PulseAudio plugin simply because I believe that it is the only plugin used by almost everyone. Other plugins are kind of “special”, or “professional” and can be dealt with on per-expression basis, but the PulseAudio plugin should work out of the box without any extra configuration from the user or the expression maintainer.\nBTW I just found this topic from 2009 with a relevant discussion: An aggregate package seems to be a viable solution. The problem with this (which seems to be the one concerning in the ML) is that adding plugins won’t be possible without rebuilds.\nIt's really tricky because ALSAPLUGINDIRS is a compiletime constant in alsa-lib. (so the env-var approach won't work) I tried to add a dir for plugins like for the graphics drivers to /run/alsa-plugins. The problem with this is that alsa-lib builds smixer into ALSAPLUGINDIRS so it has to be inside the derivation. You can pass the configure flag --disable-mixer an then alsa-lib will build, but then gstreamer won't build anymore (i guess it tries to link against the smixer in alsa-lib). I haven't tried the aggregate package yet because I'm not sure how to make everything use the aggregate derivation instead of the alsa-lib.\nBy the way, looks like should be removed. Looks like there used to be a in Nixpkgs that made respect this environment variable, but now it is .\nShouldn’t the commit that removed the “unused” variable be reverted? I mean, we need a beautiful solution, but at least it worked before that.\nAll the plugin so-files are relatively small in comparison to libasound (<300 kB together vs. ~1.4 MB), so we might consider having the default attribute contain the plugins needed for pulseaudio playback. Our attribute no longer needs to build, so we should be able to reverse the dependency and make depend on . /cc should know more about pulseaudio packaging. Perhaps it's a similar situation in there."}
{"_id":"doc-en-nixpkgs-18a978a88d3a4826f2a1d50bea87d4c4b0817e000b5a9acdc38f419c607a5f20","title":"","text":"I was thinking about integrating the alsaPlugins into the alsaLib derivation altogether. (I need the jack plugin as well) It may not be an elegant solution but it's not that big an overhead (maybe some dependencies will need adjustments) And build all the plugins that are buildable. Also I think the workaround was removed in official alsa project. See Dynamic Loader helpers section here:\nI'm using this workaround right now:\nAlso see , which maybe adds more complexity to this issue because of a 32-bit library / 64-bit plugin mismatch.\n(triage) status?\nI think I'm seeing an effect of this in attempting to update the Factorio derivation, but master nixpkgs has a more up to date version of alsaLib, but it appears to be trying to load the plugins from the system installed version of alsaPlugins.\nI also got hit by this issue while trying to run Nix-installed Audacity 2.2.2 (from nixpkgs master) on Ubuntu 14.04. Audacity playback doesn't make any sound because, it seems, hardcodes its plugin search directory.\nI worked around this by creating a directory containing a symbolic link to and adding that directory to .\nI've found a workaround in Guix manual alsaPlugins the following lines to ~/.asoundrc or\nWow. Thanks for the tip gnidorah <:\nStill relevant in 19.09 :/ Does anyone know the syntax for importing rate conversion plugins (\"speexrate\", \"samplerate\", etc.) directly inside \"\", or if there's a method without hackery by now? Btw, seems to be affected by this, I'm using your workaround from here right now, together with .\nMeanwhile it is even ALSAPLUGINDIR instead of ALSAPLUGINDIRS (notice the missing plural 'S')\nwe could patch like so. But beware, this is actually only for the the second time that i am patching c code. I tried it with and the converter and it's working so far. <details<summaryenvironment-plugin-</summary</details\nOr we could just bring back the original patch."}
{"_id":"doc-en-nixpkgs-1e8505900df2b907f79409ee29ad0a8cbc41abf334d79cacd2583e3de09dd3af","title":"","text":"i guess it is still here (somehow :)) but it is doing nothing for loading rate converters since they are neither loaded through patched from nor through from but through from But yes, now that i reread your comment, that way of telling alsa where to find libs is gone.\nSince I opened this issue I'm not sure what to do with it, but since learning more about alsa config this is no longer an issue for me. I'll post my config hoping it helps people: I have in my And my config looks like this: This finds the jack plugin just fine due to the If I want to run something (for example steam) that won't be able to run with jack then I just fallback to my mixing PCM with stopping jack exporting\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 .\nThis still needs to be addressed (either by the wrapper or by patching the package, maybe both). I've been using the same trick as and it works well enough, but it'd have been great to have the package itself or the wrapper handle users' additional plugin paths out of the box.\nWith the release of v1.2.4 on 19 Oct, alsa-lib gained official support for an runtime environment variable. It was in , following with some Guix folks. Note that this environment variable only supports a single directory, unlike the (effectively unused?) alsa-plugin-conf- which provided a plural environment variable."}
{"_id":"doc-en-nixpkgs-4d395059ce1906654c05aa846fa68bccd3fa1ca80d5683d6b94b015958c368e3","title":"","text":"One nice effect is that we don't have to patch alsa-libs any more. Thoughts on how to best take advantage of the new feature?\nWithout writing an updated patch for multiple plugin directory support, the upstream's can probably be put to use immediately by pointing to symlink farm of plugins. Haven't tried this, but I suspect it (or something similar) would do the trick. The linked GUIX thread included review of a patch for multiple plugin directory support. It looked promising but its growing stale with outstanding feedback. They've not responded to news of upstream ; I do wonder if they'd consider contributing their multi-directory patch or not - especially given that there's now some kind of upstream support.\nGuix's property will automatically create a create a symlink union of the relevant plugins for single-entry search paths. It's how Chromium extensions and plugins are discovered, for example. It's just because we haven't gotten around to update alsa-lib yet, as it missed the latest 'staging' cycle.\nHi, I'm the author of that patch from Guix, although it grew out my reading of the old unused nixpkgs patch. I ran out of energy for keeping track of all the \"C issues\" one has to think about... if alsa-lib's new ALSAPLUGINDIR meets our needs then I'll be glad to leave the patch behind. Feel free to use the patch in any way you like — it does work fine and, as a part of Guix, the license is GPL3+. Or, as a part of alsa-lib, maybe it's LGPL2.1+? Anyways, feel free...\nI marked this as stale due to inactivity. &rarr;\nI implemented the aggregate package approach () and appreciate your thoughts on it."}
{"_id":"doc-en-nixpkgs-80f5c46561f7ab28752633fd9af584ffb0ecf02cc73993239caef92f717e712c","title":"","text":"Package name: Latest released version: 1.1.0 <!-- Search your package here: --- Current version on the unstable channel: 1.0.0 Current version on the stable/release channel: 1.0.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-4e03ee9b83873012a491713bebc10928e80c74f870c8b7967b6b3670edef7d1a","title":"","text":"Restart cinnamon from the panel freezes the desktop, from the journal you will find cinnamon crashes. click the panel trouble shooting cinnamon No crash.\nOkay, I guess I need upstream help for this, going to forward this to upstream..."}
{"_id":"doc-en-nixpkgs-09815e4986410dc27a75843ff5acd3054955002917fe1b9d11636a7cb69677e1","title":"","text":"Packaged VLC does not seem to support wayland. Steps to reproduce the behavior: vlc with on e.g. sway opens as a XWayland window VLC opens as a Wayland native window Not applicable Possibly related to VLC not depending on qtwayland. Please run and paste the result. EDIT: Typo\nIt is strange. I built it and verified, it is not linked with QT libraries even if they are put as inputs.\nIs also pulled in as an input?\nNope. Working on it now. First encounter: Wayland is considered experimental and disabled by default.\nCan you test the patch?\nWorks like a charm, thanks a lot! :)\nI'm on NixOS 23.05 and discovered that vlc prefers to use XWayland if var is set. If I unset then vlc starts in Wayland mode. Does anyone know how to make it to start on Wayland by default?\nFor now I hacked it with: Special thanks to\nWell, if this is hardcoded on VLC, there is nothing to do (besides maybe searching some hidden commandline flag).\nThe \"use QTQPAPLATFORM be damned\" behavior is apparently just what QT does, and is not specific to VLC\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nHere is the updated wrap that also addresses the desktop file"}
{"_id":"doc-en-nixpkgs-8c96c5974e0e0df814e0e73eb56f82a7910c35d5ed7401414c0653742f42ca79","title":"","text":"After setting up faster-whisper for my Home Assistant instance, I learned that my CPU (i5-6500) isn't quite as fast as I'd like for this, so I am now trying to test a GPU (NVIDIA Quadro M2000). My configuration for it is the following: I expected it to then run on my GPU using CUDA, but unless my GPU and CPU are continually equally performant, it is not working. (Also, no processes are shown in ) Steps to reproduce the behavior: NVIDIA GPU, and then configure it accordingly in , add , , , and to faster-whisper in configuration, configure it to work with device = \"cuda\" for STT to be faster, instead same speed I'm not totally sure what to expect because this is my first time using this, but I expected a Python3 process to appear in and for my STT to be quicker. My config is the following: The following (seemingly) NVIDIA related items are at /dev/ ! ! works, but I am not totally sure that my CUDA is configured correctly, for all I know possibly CUDA isn't configured properly, but I think I have everything correct.\nI eyeballed CUDA support, but have no hardware to test or reproduce. I appreciate help in fixing the module to make it work with CUDA.\nI am not overly proficient in Nix or anything like this, but I would be willing to help if you have ideas.\nWell, for one we're not passing in . Can you try setting ?\nOk, I that and now when looking at the logs, I get this: It then exits.\nThat looks actionable. We did indeed not build ctranslate2 with CUDA support. I can try to set that up, but it won't be the default, because that would make the package unfree. We possibly need multiple ctranslate2 attributes.\nIs it possible to have the package be free unless an option is passed that enables CUDA and then makes it unfree, or would two different packages be needed. There could be a package, I think that could work.\nYeah, that would also work.\nIf you want to try and build it with CUDA support, I can test it out and report back.\nfixes the module, so it passes as expected. It also adds CUDA support to ."}
{"_id":"doc-en-nixpkgs-deea290ab90432a1bc50f8d87148fde0ffbb51a83ad9ef7b1740311c01aae2ea","title":"","text":"Check the description of the PR on how to opt into CUDA support in nixpkgs.\nHi Just to clarify, you only need in your (or in your 's ) if you're setting up a development environment to write cuda programs. If you only want to use packages with cuda support enabled, you just use them directly (e.g. ), no need to add anywhere manually. If you want to enable cuda in every package that supports it, you can set in your (nb: this triggers a massive rebuild). Instead of adding , you want to use (this way if you switch e.g. -, you'd be still using for the correct kernel), but also instead of you can take (keeps working if you switch e.g. -) Sorry we didn't get this documented yet\nWow, thank you! I assume I still need in my , right? About enabling , I've already enabled that and let it go through that whole process, so I think I'll just leave it enabled. About changing the , how is that to be done exactly? Do I just swap for in the exact same spot?\nAlso, is there an easy way for me to test out this updated package before it gets merged?\nDepends on how you deploy your machine and what nixos version you are on.\nI'm on Unstable and use Flakes.\nYou could replace your nixpkgs input with a fork of nixos-unstable and pick the commits from that PR on top. I'm sure there is a better solution, but I'm not well versed in flakes.\nNo, is the old version of , and you don't need it in Yes, except it's just , without at the end. This refers to \"whatever graphics driver is in use\". But also you can just remove this if you use and (both options are badly named, they're not really specific to neither of opengl or x11)\nI have , but I don't have xserver enabled because this is a headless server. Do I even need nvidia_x11 if it's headless with no DE?\nis where comes from; I don't recall now if it's ok to use on a headless machine, but if you like to just be explicit, you can keep P.S."}
{"_id":"doc-en-nixpkgs-94249543496d415209061fb1f4fa043d11dbaaf86df4c6f58d8d3bdbccce06a1","title":"","text":"Discourse and NixOS matrix channels provide venues for Q&A discussions\nWith the changes made to ctranslate2, and the fixes to th , I fully expect this could work. If not, please get back to me with some error messages, e.g. the hardening of the systemd unit might cause problems.\nNo problem. I attempted to use just the new packages, but it became a little difficult because my old nixpkgs didn't think that ctranslate2 could have CUDA enabled, so I'll just wait for master to get pushed to NixOS-Unstable (Hopefully soon!)\nThe package now fails with . My system may not be correctly configured for CUDA support, or the SystemD Service is not passing through the NVIDIA device correctly. Just a reminder, the following devices are available at : (I'm not sure if is an NVIDIA thing, but it exists if that's of importance.)\nThen we're at least missing . What's the content of ? nix DeviceAllow = if [ \"cuda\" \"auto\" ] then [ # \"/dev/nvidia1\" \"/dev/nvidia2\" \"/dev/nvidia3\" \"/dev/nvidia4\" \"/dev/nvidia-caps/nvidia-cap1\" \"/dev/nvidia-caps/nvidia-cap2\" \"/dev/nvidiactl\" \"/dev/nvidia-modeset\" \"/dev/nvidia-uvm\" \"/dev/nvidia-uvm-tools\" ] else \"\";\nI modified the SystemD service to include , and it didn't help at all. The contents of are . Also, I just discovered something new. When running I get So possibly updating this system now broke NVIDIA support and it just so happened to be at the same time I tried to get Whisper working.\nDid you also check which is in ? There are two things you need to maintain: 1) your driver should be newer than the cuda libraries used to build your program, 2) your should come from the same (version of) package as the kernel modules (in other words, currently you have to reboot if you update your nixos and get a newer - the new kernel module is only loaded on the next boot)\nshows the following for Also, I just rebooted and is working.\nfrom what I listed is accessible from , should my system have functional CUDA support? I tried using some testing parts from , but it seems to be out of date."}
{"_id":"doc-en-nixpkgs-bde4ace680e2d5fe41f9bee1b4802f790a02d98a2c460d04f0ac19706332d871","title":"","text":"PS: Should this conversation be continued somewhere else, or is it fine to continue it here because it is somewhat pertinent to the issue?\nYes please, e.g. in or , or on You can just post the final update here once you get things to work, for discoverability purposes. Thanks!"}
{"_id":"doc-en-nixpkgs-2e264a69f87eca7bab0371a27fd036c818b3f1d370c074f3e81b241ef7f47157","title":"","text":"Can't build xorriso due to source archive hash mismatch. Steps to reproduce the behavior: the substituter -shell -p xorriso nixpkgs 23.11.5408.\nProbably it comes from a moving target... Let's go!\nHow exactly it happened? Here is the url: Is web archive failing?? P.S.: since Xorriso is just another name for libisoburn, I will remove xorriso and link-alias it to libisoburn."}
{"_id":"doc-en-nixpkgs-71d85c0190495b2ae1c0f9f151cb8a674aecb121639411f42e01a3121ee6d9ec","title":"","text":"Project description vcpkg is a package manager for C++ and many large and very small libraries are packaged there. Many of my projects use it for CMake configuration and for its toolchain file that automatically download and build libraries. I want to setup dev environment with nix and this is one of the packages I'm looking for that I've been building manually (since the brew packaged vcpkg is not well configured for manifest files support) Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin, windows\nI'll try something now.\nReading the , it looks like a case for a module, not merely a package.\nI'm not sure what's the difference between a package and a module... but if it allows me to download a prebuilt binary of vcpkg that I can simply install, that's fine for me. Know that this package manager is made (partly) in C++ and need compiling. The build script is the you see there.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nMaybe I am over-engineering here. Reading the AUR script, vcpkg uses systemd scripts/services. Therefore I think it requires more integration with the operating system. Modules are, roughly speaking, designed to \"patch\" and configure NixOS (the operating system).\nWould be nice to have!\nWork is ongoing here:"}
{"_id":"doc-en-nixpkgs-75d15a86d41224c05ab438c76d7a6a379480237e44b7ba6afff4b5074f09becb","title":"","text":"Python module, corresponding to the package and exposing its functionality in Python programs, fails to import, despite being included in . module is imported successfully. n/a <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --- (as maintainer) (as the one who exposed the Python bindings) Please run and paste the result.\nNote: it seems like the module doesn't work even on commits that introduced it properly... To verify, run in a Nixpkgs checkout:\nYeah, I screwed up testing this. btrfs-progs doesn't propagate python, so I was using my system (non-NixOS) Python installation without noticing. should fix it."}
{"_id":"doc-en-nixpkgs-198a39e3bd1614677d62051a7e1f79cf3e95ec61f01d0aa80f662a143c5dabaa","title":"","text":"I have a system without Command Line Tools or XCode and nix'es cmake can't find headers and tries to pick up system frameworks. Try to build this: On my system I get: System: Darwin Nix version: nix-env (Nix) 1.11.9 Nixpkgs version: 17.09pre-git () Sandboxing enabled: no\nRelated to"}
{"_id":"doc-en-nixpkgs-0c8f5976efa2adf115a9b6c5623cd1c71ad892072a3785fc4110062a5ef0adf9","title":"","text":"The gitlab  script depends on , which was removed by in . Steps to reproduce the behavior: The update scripts succeeds. (myself) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nAlso looks like nix-update could be used here.\nOk. looks like switching to nix-update would require some other major refactoring because the writes out some json file out. But here is a simpler approach:"}
{"_id":"doc-en-nixpkgs-0e6c22a36e23f1b2cda19170877a73435ca7b585fdc6770b6757017664915ab8","title":"","text":"Describe the bug to the find call. This prevents things in the that are symlinks from being wrapped. Noticed this during office-hours when wasn't wrapped anymore. We should add some code like there is in or revert the . To Reproduce Steps to reproduce the behavior: a binary into or the thing and notice the binary isn't wrapped."}
{"_id":"doc-en-nixpkgs-db05278674bd6328671072c1a3bd8bba68531a117280217f108ab80c5381f731","title":"","text":"Package name: nexus Latest released version: 3.69.0 <!-- Search your package here: --- Current version on the unstable channel: 3.68.1-02 Current version on the stable/release channel: 3.68.1-02 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8647570b6161614f3304f8cdc85cfb063f2c5a84685720d56b7c73e29c3ddf9b","title":"","text":"Package name: gpt4all Latest released version: 3.2.1 <!-- Search your package here: --- Current version on the unstable channel: 2.8.0 Current version on the stable/release channel: 2.7.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]:\nHi, I don't maintain GPT4All any longer, I switched to some other technologies (Open-WebUI).\nhaha, maybe i'll give that one a try then :) ty for all your hard work"}
{"_id":"doc-en-nixpkgs-d5b1400c87e3ce5106a341ccff576fa6f978186d23f666fde6a54ccd3c73b9a5","title":"","text":"It would be great to have option to fetch nnn plugins with nxpkgs or with additional package instead of manually fetching it like developer advise. And second is it possible to implement some option to include icons support from nerdfont to nnn binary file instead of recompiling it? Thanks.\nI think this issue was closed preemptively by the line in the PR, there doesn't seem to be any way to include plugins as of now\nnnn seems to expect plugins in . This might work better as a home-manager module, maybe with the plugins themselves as an output of nixpkgs. I might take a look at this next week.\nI marked this as stale due to inactivity. &rarr;\nI've recompiled nnn with icons, by using unstable branch and overriding nnn-package:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-8b72561b535ed031fc0a7c52e258635fc8a8ae420de455c549e57920619bf9db","title":"","text":"is failing with: Steps to reproduce the behavior: Result: It should work. N/A I need to use netplan locally to test generated configs, I don't actually need to apply them locally. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-1c6b5cda96e7fd2651731f6f2d9c74a881af17f8ad0530e38f6a84c0c23fa0c0","title":"","text":"Project description Glue is a python project to link visualizations of scientific datasets across many files. Click on the image for a quick demo: ! Metadata homepage URL: source URL: license: BSD Linux, BSD"}
{"_id":"doc-en-nixpkgs-81059555bcfa1996c48627555ec9e7d1c61c8d0c2774ffe7e4457744f248e765","title":"","text":"Since Sage is huge and complicated, I figured I would make this issue to collaboratively track progress and share branches. One big issue is that Sage 7 , instead they use some with scant documentation . has the correct SHA256 for Sage 7.6 and updates a patch file. It currently fails when Sage tries to build . Some nice things to do for the future: ) cc:\nthanks for picking this up\nMe myself being a miserable loser who has failed to update Sage in the past, I hope you succeed… My attempt hit the following wall. It is unbearably slow to let Sage build everything, but when I had convinced it to use the system versions of majority of dependencies it began to complain cryptically about their interaction in some case.\nCan you elaborate? Do you have a branch that has that work? Also, to be clear: I probably don't have the skills or time to upgrade Sage by myself, I was hoping that if we shared our knowledge and de-duplicated efforts we might be able to get closer together\nI think it was 6-dot-something; it required a metric ton of adding options to the packages in NixPkgs (I have pushed that all to master long ago), and the Sage tricks are most likely too version-specific. It was long enough ago that I have since abandoned and lost the changes.\nIn case anybody in here is still waiting for this: I got sage to compile and run. I'm currently trying to minimize the dependencies and check that everything is working correctly (there is one doctest failure, but it was mentioned multiple times in the mailing list and apperas to be harmles -- just a timeout). I'll probably make a PR in the next couple of days."}
{"_id":"doc-en-nixpkgs-6a59b808d07963af847c2e1fab5f8d14c099155832af09487ad2d2db6454d025","title":"","text":"Sage needs texlive-core-2014, which is deprecated. Run with modern nixpkgs (i.e. from git) System: NixOS: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version:"}
{"_id":"doc-en-nixpkgs-d952e9c39b4f577ab9fcb900722a85c5e9a76c34b465d44923dd95760c87434f","title":"","text":"Chromium coredumps on wayland/sway when trying to share a screen. Steps to reproduce the behavior: sway/wayland \"\" on \"share screen\" anywhere -Dump A selector for the screen to share should appear According chromium setting: According nixos configuration: Console output when the error occurs: Also this works fine with firefox-wayland and used to work with chromium. <!-- 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.\nCould be related to as it also states\nDid screen sharing work before / is that crash (segmentation fault) new? And do you know since which version it stopped working? So far screen sharing did never work reliably and there have been frequent regressions: (I've fixed it twice on my test setup but I've given up since then). We might want to close this issue in favor of to keep the discussion in one place.\nFor me, screenshare works on Chromium v99, and stopped working after update to v100\nFor me it also worked in the past without issues. This is new and this is chrome core-dumping. This is a different issue. If screen sharing did not work in the past, it just did not work. It did not cause an out of bounds read or crash of the browser. Please don't close this issue.\nSure, we can leave it open. We should mention it in the other issue though (I just did that) for better visibility. Now we need someone with time and motivation to handle this issue (analyzing the issue, searching for upstream issues, etc. and eventually someone needs to submit a fix).\nSince this is NixOS and we have the boon of input-reproducibility and a binary cache, could you post: the nixpkgs commit you are on the nix store path of your chromium binary This will make it even easier for others to reproduce. You may also be able to get the stack trace with GDB using , use , make the segfault happen, and use in GDB."}
{"_id":"doc-en-nixpkgs-6973e71473a4f895441b6f403f07f7923c55c8d7ca6e1d08741ac6fb608cd613","title":"","text":"nixpkgs: /nix/store/07346c7jv5wnwg30r5dvmlgqbk52hinz-chromium-100.0.4896.60/bin/chromium\nRegarding gdb: ` How do I get gdb on the actual executable but keep the env vars of the shell script wrapper?\nNow edit , replacing like this: Then terminate all chromium instances (to avoid joining existing instances), and run .\nThank you for the detailed instructions!\nLooks like it should be fixed in m101\nI tried to build chromiumDev(102) or chrimiumBeta (101) - but both failed with errors related to:\nThis patch may be useful: https://webrtc-\nI'm a week old to nix, but trying to figure out a way to patch it. It seems it needs a special flag due to it's location:\nbuilding chrome is an undertaking not to be embarked on lightly. you can install the chrome dev or beta channel package. On my up-to-date, flakes-enabled nixos-unstable: The issue seems fixed there. There are builds of chromium upstream here: (under other), but I'm not sure if there is a nix derivation for them.\nI've opened for a quick and dirty fix - the code isn't pretty but should do the job (I wish would support Base64 patches or even better: Gerrit and gitiles would support fetching patches using a sane format like basically any other web VCS frontend does...). Anyway, I'll check if the VM test passes (although that patch is so trivial that it should be unnecessary) and can merge the fix tomorrow.\nI love the name and thanks a lot for your time & effort!"}
{"_id":"doc-en-nixpkgs-a1e2f7882d05903f7652cdf4d7d261ed26aa9fa2035b2cde7a63811b69f3c3a5","title":"","text":"Describe the bug is when building for MinGW, however an equivalent GCC 10 patch file doesn't exist. I tried looking for a GCC 10 patch on the master branch of , but the folder that contained the patches no longer exists. GCC9 is still currently the default on master, but this will break everything under MinGW the next time staging-next is merged to master. See Support for was originally in To Reproduce Steps to reproduce the behavior: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(kira): nixpkgs: Maintainer information:\nIt has been moved to to upstream migration. Neither of these repos is stable; their master branches are constantly rebased on upstream and force-pushed."}
{"_id":"doc-en-nixpkgs-cd5f83c46ee17f89f649a6c0dd644e59b4f67de474fb7ff9a7f4e0bf9042309b","title":"","text":"Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nstates that this only fixed the swift build but all downstream packages are still broken. re-opening.\nActually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.\nI noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?\nThe above open PR seems to run into the same issue…"}
{"_id":"doc-en-nixpkgs-861874befbdc4c82ebffce62acbd78a485a8ea9d6fbf2f45089f9a81d42d8ef7","title":"","text":"uses two actions and do get necessary authorization via . but these actions are not properly registed, leading to error: (It can be verified that these actions don't exist by using ) This breaks and . I tried both pcsclite 1.9.5 and 2.0.1 ending up with the same error. Steps to reproduce the behavior: and in , configure your smartcard (yubikey) to use yubikey error There actions are registered correctly and usable. Please run and paste the result. I'm using flakes (no channels). Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\ncorrect description of your effect, i am not able to use my yubikey with gpg.\nThis can be solved by\nthis works, thanks! but this is really unintuitive, given that is already adding the package to : I am leaving this open as I believe a proper fix should be provided in the module itself.\nSame issue here. It was working approx. last Dec. I don't have a specific commit hash. Adding to works for me.\nLooks like a regression in () - is implying to me that polkit actions get included in the output, however: isn't included, which explains why adding to fixes the issue. Solution ideas: Add to . Not sure about this one? seems to also contain some libraries that probably don't need to be installed. Install polkit actions to instead of . IMO this one makes the most sense, especially as it seems to have been the previous behaviour before this change.\nI was bitten by this when attempting to update over the weekend as well. In my case it prevented login because I use smartcards for user login which made debugging difficult due to the number of reboots required. I tend to agree with that going back to having the polkit actions file in the output instead of makes the most sense. That will mean that of the pcsc module will again result in the polkit action file being to the system configuration.\nCc: ()\nI also think the location should be fine, the files are also there.\nI ran into this issue when I couldn't access my yubikey anymore via pcsc for commits. The above solution worked for me."}
{"_id":"doc-en-nixpkgs-1dc19b411349a77f8de94073121e5bb443f03602435e03488bac0e62b039780c","title":"","text":"I'm going to add some comments for SEO so this is easier to find\nI think you have found the right culprit that caused the issue, but I suppose the issue has more to do with the itself, where it only includes if . This has been rectified in from what it seems. For now the proper solution seems to enabling polkit with .\nI think that makes more sense based on the existing file structure but maybe we just switch bin to out, so it is the default and move the libs to lib instead of being in out.\nI've created to make the outputs a lot more expected by moving the udev file and the systemd service to the out output and the libraries to the lib output: I didn't test it yet, so it is still in draft. If someone could verify that it doesn't break security keys again, that would be great and then please undraft it, otherwise I do it in the evening.\nI do not think I can fully test this due to the amount of rebuilds, so please chime in for reviews and find the one mistake I might have done (which I hope I didn't)\nTried to build but it fails on my machine:\nI've xdist to dulwich here . Let me see if we can just disable some tests as a speed up from 66s to 9s is quite good.\nThis should be a lot better with . I did a lot of rebuilds locally on a low and high core machine and didn't encounter any failures anymore.\nThis was fixed in , works fine for me."}
{"_id":"doc-en-nixpkgs-4565d3d3c61667aaff2c7b2cc97b925b15546401ce4eb2bbe2ed329bf9a9345c","title":"","text":"When executing switch-to-configuration in a pure environment it fails: I am calling switch-to-configuration via systemd-run to active a new profile using the Hail update tool. The actual executed script is as follows: Actual output: <preactivating the configuration... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = \"enUS.UTF-8\" are supported and installed on your system. perl: warning: Falling back to the standard locale (\"C\"). setting up /etc... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = \"enUS.UTF-8\" are supported and installed on your system. perl: warning: Falling back to the standard locale (\"C\"). setting up tmpfiles Too few arguments. sh: systemctl: command not found </preThe script works if I pass on the PATH and LOCALE_ARCHIVE environment variables: System: (NixOS: 17.09pre-git (Hummingbird)) Nix version: nix-env (Nix) 1.11.13 Nixpkgs version: nixos-unstable (Commit ) Sandboxing enabled: no (Related Hail issue: )"}
{"_id":"doc-en-nixpkgs-8505e2e169ccd0e84b48bf63a7b77cea258ec857c37c2b69ad64f6000616288c","title":"","text":"Steps to reproduce the behavior: dvc actually it is hash problem. error from my nixos: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis happens not for the first time and probably not for the last time :cry:"}
{"_id":"doc-en-nixpkgs-908d93f4599026c258c5c41a3bf1b189e13f1eb86856f1a41403d4fefe3d6101","title":"","text":"Project description Emmet support based on LSP. Metadata source URL: license: mit platforms: all"}
{"_id":"doc-en-nixpkgs-7e8a0c97dcb7dbcd2b71d65756906fa735408dd7fbd49ef7d3e91745d57faf58","title":"","text":"Steps to reproduce the behavior: on old thinkpad Device: Thinkpad X220 <!-- 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.\ngreetings ! are you able to test ? an other workaround is to stick to < 6.4 kernel\nfor now I can't test your commit since I'm newbie and asking you to teach me would take a lot of your time Gonna stick to < 6.4 kernel and try to test commit in free time\nappreciate your concerns! from looking at your setup you seem to know fair bit already, and I dont mind spending some time for as long we all learn something useful you should be able to test that PR by changing in your flake to edit: also no rush to test this\nWell that was actually easy to test! PR works! I thought I need to use overlays to test it and I have zero experience with them for now."}
{"_id":"doc-en-nixpkgs-d8d369c92c79ab6926e9a6161bde4bad33a0c734941e02313e155077e2fe27d1","title":"","text":"Steps to reproduce the behavior: onionshare <!-- 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]:\nThe package distutils was remove in Python 3.12. Depends on upsteam. I raised a PR for the fix:"}
{"_id":"doc-en-nixpkgs-c872235c4c92ce8c8731931557d6e424ab6083ac3f22a18864b07549f0819e6f","title":"","text":"The component of the derivation fails to compile on MacOS. But in two ways, and I can't tell what causes one or the other to trigger. On command: On command: the channel compilation failure Compiles.\nIt has been broken for a while now for different reasons. Maintaining it for darwin is a lot of work and nobody has stepped up to do that. Also, this is a duplicate of\nBy the way, what is your use case for ?\nWe're building a desktop version of mobile application and we need for our in-app browser with Ethereum support."}
{"_id":"doc-en-nixpkgs-037777ed3857890e0bd45e3c72591f30dc4091dd196fdbdf59077de31f8b3dda","title":"","text":"Full log: Error message: That's the result I get from my macOS remote builder. When I run the build on my desktop Mac, it builds fine and uses the impure SDK from my Catalina install (10.15.1): However, the local build displays this warning repeatedly: I assume this is related to the macOS patches and hopefully gives some clue as to why it's broken.\nqtbase builds fine on hydra: qtwebengine fails:\nThose links point to the same thing. Anyway, strictly speaking I'm trying to build , but it's failing in .\nCan you explain what do you mean? How are you using ?\nIt's a dependency of . edit: sorry, I see what you mean now. is a dependency of . I was confused by the message from the build saying that QT would be installed in .\nSure, depends on . Realistically, your best bet for now is to just use anki from an old version of nixpkgs. You see, doesn't have a darwin maintainer. I think, I was the last person to fix it around last January. The problem is that it's hard to keep up with all the updates. Every \"minor\" Qt version bump brings serious breaking changes for on darwin (like they might not even support our version of SDK anymore...). To make things worse we port all those bumps to the stable branch, so it quickly breaks there too.\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, many qt apps are broken on darwin due to this one."}
{"_id":"doc-en-nixpkgs-b31892eae18ac7cc8b8561132600b5c0d37fbd3ad716b580bef456d9605b6e75","title":"","text":"Mangohud no longer appears on gnome/wayland when opening a game. \"rev\": \"\", (works) \"rev\": \"\", (doesn't) Steps to reproduce the behavior: a game on gnome/wayland doesn't appear even when enabled (worked in previous revision of nixpkgs above) ... Mangohud shows system stats Please run and paste the result.\nI have the same problem too. I'm using Hyprland btw.\nOh weird. I'll try looking into this. The only thing that really sticks out to me in the diff is possibly ? - but it seems unlikely. I'll do a git bisect to try to narrow it down better.\nIf it helps you narrow down, here's my repo with the exact commit where mangohud stopped working. If I revert back to previous commit mangohud starts working again:\nI bisected it, it's cc\nmangohud uses its own internal copy of vulkan-headers: So it's probably the loader? If it is though, it might be tricky to bisect...\nSo, what are we going to do? Especially w.r.t. 23.05 being around the door. I don't think we should ship a broken mangohud in 23.05. Honestly, I think should have probably not made it to master before branch-off. (Eventhough it was technically merged a few dasy before breaking changes were restricted.)\nI'll try to reproduce locally and see if I can bisect vulkan-loader.\ncc because of\nWe could also try updating the headers externally; Mangohud's are really quite old. They use this weird meson wrap thingy rather than letting the distro provide it and it too is very out of date. Also, this is the error we're getting: (This is on 64-bit-only Mangohud.)\nIt breaks when built with newer headers.\nOh sorry, forgot to get back to this! Maybe we need to switch back to using the system headers?\nI'm actually pretty sure it's which we probably don't want to revert, but we may need to look into layer ordering?\noh no - yeah i think you're right, i think the duplicate behaviour was specifically to support multi-arch layers (from what I remember)."}
{"_id":"doc-en-nixpkgs-24a19da83989cda5abcb72eb02c234a2e7e1a38a07aba7dbb77be76269ea3072","title":"","text":"If it's just an issue of duplicate layers, perhaps we could add 32 and 64 suffixes to the layer names. obs-vkcapture does that too.\nI gave up o pursuing this, as seen in It works, but for this case here, it's probably better to bring attention upstream. Cc\nHaving only the 64-bit mangohud json in the implicit layer dir works! Going to try giving the 32-bit layer a different name now.\nThis is also going to affect vkbasalt too then - I haven't tried yet though - I'll take a look at fixing that too!\nSpeaking of, any reason you gave up on that? I personally really liked the good idea.\nDifferent suffixes work! PR incoming.\nIt needed a proper rebase+bump to v1.3.250, and I couldn't figure out how to really take a good benefit from it.\nHm, I'll definitely try to pick it up after branch-off then.\nPeculiarly, obs-vkcapture seem to do this for some time already: from gamescope might need this fix too."}
{"_id":"doc-en-nixpkgs-577676d6229de14404463683fc90a1af7001aaf74fe99fff9d8ee8748797ced4","title":"","text":"Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-edc2ea564177a34579d90296e8dc2e13106792a1e46457b88839f08a6d2dbd1c","title":"","text":"singularity cannot use nvidia gpu because it does not access 'nvidia-container-cli' Steps to reproduce the behavior: return result of ! This is because the path is not listed in , as also in a. It is caused by neither the option nor . I tried to handle it with override, but since it was called in , I think it is impossible to handle. Also, I created a conf file in as shown in the singularity docs, but it was not read. <!-- 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 reporting and sorry for the trouble. I'll look at the SingularityCE documentation again. (Those configuration options has been deprecated by Apptainer.) Also, I created a conf file in /usr/local/etc/singularity/ as shown in the singularity docs, but it was not read.  shold be what you are looking for. The overriden package can be assigned to . (If you would like to bypass all the overriding done by the module and directly specify the package to install for some special reason, you can assign it to .)\nThanks for the reply. I followed your advice and tried the override and was able to use the GPU. Here is the code This is simply adding a process to append the nvidia-docker path to the I mentioned earlier that when conf was entered in , it was not reflected, and the same is true for '/etc/singularity'. I referred to .\nAt least we have confirmed that in works and the path is replaced by , but the product does not seem to be recognizable.\nDoes setting the to make ldconfig search in help? This is modified from the configuration proposed by (). There's also (probably) related to this topic.\nAdding the path of to works well. This once removed from consideration. Next we have a patched version of ldconfig. This does not append the path of to the config. The result was an error that could not be found, and it could not be started.\nOh, I already forgot about this issue. Absolutely coincidentally, but maybe efforts such as might open up a way to implement this hack more reliably."}
{"_id":"doc-en-nixpkgs-fec39dc3883d65fce70d2b6cb3b6ca5c1362ab49a45d2d5af4255cad24f627be","title":"","text":"Meanwhile, in my config I'm still abusing You probably already have guessed, but singularity in nixpkgs is configured to read this config from the package-specific directory, rather than from the global . You could in principle override this behaviour, but there maybe isn't much value in supporting that\nI tried to enable the use of external sysconfdir (), but have encountered issue trying to specify a directory under with the NixOS module ().\nHave you tried to apply both at the same time?\nThe SingularityCE Admin Guide says If the value of nvidia-container-cli path is empty, SingularityCE will look for the binary on $PATH at runtime. It should work as long as is found in the run-time , even when is not set. As nvidia-container-cli is alredy included in the PATH-prefixing wrapper, we shouldn't have to set the .\nUpdate: I found a bug in the prefixed PATH of the wrapper introduced in . The prefixing should be specified as (in Bash) I forgot to add , causing the trailing to be missing.\nThe statement in the SingularityCE Admin Guide turns out to be wrong / irrelevant. The source code clearly states that nvidia-container-cli will only be read from the configuration.\n(we need to patch nvidia-container-cli, for many reasons )\nEh, actually, closed semi-automatically. Apptainer with is fixed (on NixOS), but not with . The fix doesn't concern singularity-ce either, unfortunately. Shouldn't be hard to make this work with singularity too, but I'm out of bandwidth\nHi folks, I've been trying to get apptainer to run this (which I've done previously successfully with a slight ldconfig hack -- that doesn't work anymore -- on NixOS 22.11), that will make use of the machine's Tesla V100 to do some simulation stuff. The machine is running NixOS 23.11. Using the workaround from 9th of May post further up, I was able to get past the ldconfig issue, but now I'm getting an error saying the driver and CUDA are not in sync."}
{"_id":"doc-en-nixpkgs-3bc913b48518f98f234bf001456f37a1ddcfd0a3b6f8b118900f346cfae78dea","title":"","text":"Before I start posting any details (I don't want to re-open this issue, but I'm also not sure if I'm just doing something wrong) I was wondering if the current implementation of singularity/apptainer on NixOS is expected to work, and I'm just being an idiot, or if there are known breaking issues? I've seen the other issues about singularity/apptainer here, but I'm not knowledgeable enough to make a judgement call if they are responsible for my problem or not. Thanks very much in advance!\n(If I understood the message correctly) That usually means you need a reboot, and you should experience the same issue outside the container\nNo, the reboot didn't help either. For some reason, though, after upgrading to 24.05, everything \"just works[tm]\" again. So, whatever the issue was, thanks for fixing it (probably)! :)\nThanks to Nixpkgs 24.05 includes GPU-related changes/fixes to the package and the module.\nWell more like thanks to ShamrockLee"}
{"_id":"doc-en-nixpkgs-dd3d6b5b1c9bc5760ad06e5425708664e505380a845314d6d57997260bff0eb4","title":"","text":"The derivation is missing the directory to work properly. Steps to reproduce the behavior: A clear and concise description of what you expected to happen. is output without error. This can be fixed by creating the directory manually (). I guess this could be to the derivation. <!-- 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.\nNixOS module provides those top-level directories. discussed with one of the main Apptainer developer in . He think it should be easy to specify a directory that will always exist at build time. Regalding this, I'm considering the possibility to put those dilectories under the derivation store path. Not sure if there would be potential problem using a store path as a mount point, but it seems to work without problem.\nCould you help me take a look at ?\nIf you have time, please help me test the PR . It should fundamentally solve this issue. If applied, you no longer need the NixOS module or just to run images. It specifies the LOCALSTATEDIR as , making both Apptainer and Sylabs SingularityCE works without . (The image running still depends on and to run images, which might be the final obstacle to build images as a package without invoking a virtual machine. Other than that, it should not be an issue for most users, as are available on most of the UNIX/UNIX-like systems.)\nI removed (the temporary fix for this issue) and ran the following and it seems to work fine: Thank you for this fix!\nGlad to hear that! Would you mind ? I've heard that committers tend to merge PRs getting two approvals.\nDone!"}
{"_id":"doc-en-nixpkgs-89d7d63dbf352f46ddf329dd8a15eec4e2fc45ac51128d999bcaa5b3ba4de069","title":"","text":"It got a huge closure size. Jump happened here: 91.1.0: 0.5 G 91.1.1: 3+ G On a quick glance, it's mainly due to dragging lots of toolchain packages, rustc in particular: /cc other likely interested people:\nand don't suffer from this, by the way.\nThis may be relating to ()."}
{"_id":"doc-en-nixpkgs-31fe604789e114328eda23659df47a12c68321d5a98e507368d76d4948e8416c","title":"","text":"Steps to reproduce the behavior: afl <!-- 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]:\nIf you are planing to open a PR, you don't need to create an issue first.\nI wasn't sure, thanks for clarification"}
{"_id":"doc-en-nixpkgs-262cb658dd5b2753cd4ccd84dcf190fcb4a732c4b771691d0a2ce76157d3a594","title":"","text":"Mesa 21.3.2 present in is causing , and they point to , not yet fixed as of now. Reverting to nixos-unstable to Mesa 21.2.6 updates fixes the issue. Steps to reproduce the behavior: sure you're using Intel GPU nixos channel to No flickering should happen on the application screen. Mesa bug report has a video demonstrating the issue. If applicable, add screenshots to help explain your problem. cc: Please run and paste the result.\nAccording to the bug report this seems to affect at least Blender as well. Anyway, we can leave this issue open for a while (in case it helps users to figure this out) but I don't think there's anything actionable for Nixpkgs (it's an upstream bug and we simply have to wait until a fix is released via a new version). It looks like the patch from should be submitted formally via a PR so that it might get included in Mesa 21.3.4.\nThis is also happening on qutebrowser for me, but only on the wayland backend. I have a temporary fix to just launch with , but this obviously disables the hardware. Works fine though so far for just browsing and work stuff, at least until a proper fix is merged.\nIt's unlikely that the patch will be applied for 21.3.4 (as no one filed a MR for it so far), should we apply it downstream?\nI'm seeing this in qutebrowser as well (non-wayland)\nI'd prefer to avoid applying a patch that hasn't been reviewed upstream.\n+1 for what said. Luckily a developer from Intel started looking into this so let's see how things will develop: Ideally a patch will be ready for 21.3.4 but the release might happen in two days (unless it gets delayed) so it'll indeed be close (but we'll of course re-evaluate our options once the release is out).\nUnfortunately it was indeed too close for the patch to land in Mesa 21.3.4. However, now there's at least an alternative patch from Paulo Zanoni (the Intel developer) and Giuseppe Ghibò (author of the other patch) and others confirmed that it's working: I've included that patch in Does someone have time to test it () and report if it indeed fixes the issues?"}
{"_id":"doc-en-nixpkgs-835bfc2f47079558e8e767b5e91fbd30314b04d1f49606ad29714462659b2ef5","title":"","text":"Thanks a lot for putting together a fix! I'm happy to test. Could you confirm I understood the instructions correctly? 1) integrate the code from the above PR into my nixpkgs tree. 2) put the following into my nixos config: 3) replace with the path to my nixpkgs tree. 4) run Did I get that right?\nIt's the easiest if you use a separate/dedicated Nixpkgs tree for Mesa ( in the example). That way you don't have to rebuild a lot of other packages (which would most likely still take way too long). You can also cherry-pick the commit to (I'd recommend doing that) which saves additional rebuilds (I only tested it that way so no idea how many many builds are currently cached for staging-next). The rest looks fine. And thanks in advance :)\nIt works like a charm. Thanks\nSeems like this wasn't closed automatically once landed in master. Should be fixed now. And upstream merged the required patches in the meantime (s. note in ). And thanks for testing the fix and :)"}
{"_id":"doc-en-nixpkgs-8b654653324b57945be0670be0eb74bd1bed31037123175a5dfd54e30bfc84f9","title":"","text":"Describe the bug If I change and enable when the cert/key in question already exists the group access will not be granted after rebuilding and restarting the . This is because a condition in the post start script does so only when the key is newer than the existing one. To Reproduce Steps to reproduce the behavior: without group/allowKeysForGroup and start the service to reques the certificate group and allowKeysForGroup again and restart the service, the ownership/ode will not be updated Expected behavior The group and chmod setting should be set on existing certificates as well as new ones. Metadata Please run and paste the result. Maintainer information:\nAdditionally, shouldn't chmod 0640 suffice on the files?\ncc as potentially interested individuals"}
{"_id":"doc-en-nixpkgs-340944532c7d195c7da550b50c1ae77473332bd6adda86f22db49dcce9874ec0","title":"","text":"Package name: ollama Latest released version: 0.1.20 <!-- Search your package here: --- Current version on the unstable channel: 0.1.17 Current version on the stable/release channel: 0.1.7 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\n20 was released.[^1] :tada: Had a quick look into the source changes. Seems that patching is required because of the integration of ROCm. [^1]:\nI modified the title :-)\n21 is going to be released very soon.\nI opened\nupdate: 0.1.22 is the latest version.\nSeems update can be problematic. I've tried manually download and executing new ollama and encountered a lot of issues connected with ROCM libraries. After adding I've got it to state where it crushes: But before adding it seems also miss new version of because it was asking for but current unstable version have CPU works fine without mentioned ROCM packages.\nThis appears to have been resolved by . Reopen if it's not."}
{"_id":"doc-en-nixpkgs-0fbec96de8ec47014e2a31bae96871224488166ed21aa0f8b7e2ad0ede23ec53","title":"","text":"I'm experiencing the issue for a long time now, and it was really hard to spot and debug this issue. I'm talking about this line: It's kind of hard to give instructions how to reproduce the issue. In my case, whenever the dash script runs, every folder I already have configured, fails to update. The whole configuration thus fails to be uploaded to the server. I can inspect the and the by editing that dash script, and I can see that I get folders twice in the json arrays. Hence I'm not surprised I see the following error in syncthing's web interface: ! I expect the merge script to not a JSON array with no duplicate folders IDs. Transition most of the logic from jq to bash, for easier maintenance, and use and API, and use when . I'm working on a solution at the moment but I'd like to here your comments first. cc who wrote the original dash script, other people have touched that line ever since, was the latest."}
{"_id":"doc-en-nixpkgs-ff8f2cc9b59a445f99fae48c3e0da966f14344e373a9a00ac8b59caec99fab2c","title":"","text":"To make sure that we are on the same page: Kernel: System: Nix version: Nixpkgs version: broke legacy packages (only tested with the -set). Multiple options to solve this: revert the commit (an update will eventually have to be done) make sure no-one depends on sqlalchemy legacy versions (this would be the best choice, but can require a big amount of work) re-introduce an outdated version only used by legacy version (I’ll prepare a PR shortly that follows this path) cc\nTo be complete, the build problem is a test failure: I also checked, we cannot downgrade sqlite only for few pythonPackages, the entire python (and package set) have to be changed. Any preferred way to go?\n(We should check if we still need this version, have it removed locally for virtmanager, virtinst as it isn't used, but haven't had the time to push that)\nYes, this is the preferred way to go. I began that but did not finish it yet, and it impacts some important parts (it causes xen to fail) I would prefer not to break because of unsufficient testing from me. This is in progress but could require some time to complete.\nFYI xen already fails on\nFYI: I switched away from sqlalchemy7 in yesterday.\nApart from virtinst, acd_cli, beaker, coilmq, and geeknote are the only revdeps of sqlalchemy7, as far as I can tell.\nI openned to do some cleanup on sqlalchemy7. There still is that explicitly require . The same work will have to be done for and .\nThis should have remained open.\nUsing an older version of sqlite requires overriding the derivations of the interpreters.\nSee"}
{"_id":"doc-en-nixpkgs-995558cf18e491320129dce4bf7037ef835175b233c5e39c5f19900eaea690db","title":"","text":"First failing build (4.9.76, but not always): Latest (4.9.77): Looking through the changes for any obvious culprits...\nbisected to (as the first \"bad commit\"). cc\nReverting the commit on master fixes the build, but need to replace with to at least fix evaluation on cross. Since doesn't seem to build on cross (at least not on any architectures I've tried) I can't tell if this \"works\", but would be good to fix this on non-cross regardless.\nSee corresponding PR, this has been handled. Thanks!"}
{"_id":"doc-en-nixpkgs-1d62006edc5884bcbc2f6a5530af983a140dff616ff399e7af6a39553e7ef211","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: 25.0.1 desired version: 25.0.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-f1282c38361b97e8a8845a90de8893ac68cd159b9df2290aae384aafe2bec774","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.7.3 desired version: 2.0.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.\nwaiting for 0.50.0 release of\nI fixed echidna.\nLovely. Thanks you so much for you effort."}
{"_id":"doc-en-nixpkgs-2037af2d1e293156477cc2f2aa4fff3d15b39ca943ae9ba73b413dc9d4cd3eaa","title":"","text":"The mpccli package is missing bashcompletion, even though a bash completion file is in the upstream repo under contrib/mpc- . Steps to reproduce the behavior: the package a terminal and type It tries only to complete with the contents of the current directory mpc should be completed with the mpc subcomands like , , etc. On a regular system, the file would have to be installed under /etc/bashcompletion.d/ . I don't know whats the nix(os) equivalent to this.\nFirst, I am not the maintainer of this package. Nonetheless I will review this. Second, in Nixpkgs we do \"almost\" the same: we use a special hook that installs those extra files at the . Now I need to sleep; please wait a bit more."}
{"_id":"doc-en-nixpkgs-a82f4ce609cd875f970d50e519a45ad2bada82790ba8f3a07be20b24123754d1","title":"","text":"Package name: neovide Latest released version: 0.13.0 <!-- Search your package here: --- Current version on the unstable channel: 0.12.2 Current version on the stable/release channel: 0.11.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. As an additional note, I am currently working on updating Neovide myself. Part of my plans this summer are to begin giving at least two contributions to Nix/NixOS/Nixpkgs each week. I intend to begin maintaining Neovide as part of this goal. Gotta figure out how to A.) apply as a maintainer and B.) figure out if I'm even eligible. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nFor future issues/prs/etc. where should I add an additional summary/context if I have any? I've sandwiched it between the Note for maintainers... and Add a reaction... sections in this issue."}
{"_id":"doc-en-nixpkgs-9f8261fbdde52064a26ef453e404e8945d6c7d37dacc0598fad064d59e428400","title":"","text":"Evaluation failure when setting and . Moreover setting any will \"remove\" the default values for and your system with these options: the failure: System builds, firewall is opened for the default 4533 port. This bug happens because the rather than for each individual setting. <!-- 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]:\nthe Issue here is the option being null, you can use these options together if is supplied. if you encountered a different eval failure to this please attach it. Yes this is because those options values are supplied as apart of one default of as a whole, I am not aware of a nice way to give them a default independent of the rest of the settings being set or not. would giving this port value a catch for being null be an alright solution? e.g.. if is not set, then use the upstream default ( of 4533 I believe ) I don't really want to separate out these values from the . option so this wont address the removal of default values when setting them yourself to something different, I think this is expected enough* behavior. I think fixing this eval failure condition with simply supplying the default port where isn't supplied is reasonable enough, as anyone who wasnt going to set that in the first place is unlikely to care if its the same value in function either way. In fact i may just remove the default entirely and simply handle the case of no supplied value by assuming the default port (of 4533 ) in the openFirewall rule. I'll PR these changes once I get the time"}
{"_id":"doc-en-nixpkgs-793705aec2024e9f515fdeaf5764a25ef01905be7b67abc3e0de07a5c390abf4","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.\nI will also work on this"}
{"_id":"doc-en-nixpkgs-802678535b350eed08ea10df73bc81bf92557d6188be3f51029b757f94e872a7","title":"","text":"Working with large repositories on low-memory systems (such as aarch64-linux SBCs) can lead to out-of-storage scenarios with the github-runner service because the working directory is set to by default , which is sized to 25% of the system memory by default . Ideally there can be an option to use storage instead of memory for the working directory. I'm opening an issue first because I am not sure if there is a way to work around this already; can the argument in the service be overridden, or is there another way to change for this service with a systemd setting? If there isn't a straightforward solution I can open a PR to add this as an option. Maintainers:\nI also experienced issues with no space left on . So far, however, increasing its size did the job. Nevertheless, I'd also appreciate the option to use another filesystem for the runtime directory. We won't be able to use systemd for that as it demands a -like filesystem for the runtime directory.\nI guess standard installs avoid this by using the directory. Maybe we should just document how increase size instead of adding another option?\nYou may pass an arbitrary path to the options of the configuration script. Our module currently always uses the runtime directory systemd assigns to the service.\nYeah, in our case using the runtime directory that provides makes the most sense for dynamic user, again, with documentation on how to increase the size of the runtime directory. Currently our module doesn't support static users so isn't very useful... though I'm guessing our lack of support for static users is an oversight - see details here:"}
{"_id":"doc-en-nixpkgs-127de076f67d7265d2c6daadb3b3b597c96b739ca8d0313ac35cb9e6942ad423","title":"","text":"dockerTools.buildImage fails with: System: 17.03pre95306. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: \"17.03pre95306.\""}
{"_id":"doc-en-nixpkgs-f5badd077946e4e6f40c069b18eae4778cc7f4cbaaf3a16b8bf41bd37aaceb44","title":"","text":"Project description mouse macro Actiona is a task automation tool. It allows you to create and execute action lists. You don't need to know any programming language to use it: its intuitive interface allows you to create action lists (scripts) using drag & drop. Advanced users can use JavaScript (EcmaScript) to extend its functionality. Actiona is free software and runs under Windows and GNU/Linux. Binaries are available for Windows and Ubuntu for both 32 and 64 bits. The program is developed in C++ and uses the Qt framework. Metadata homepage URL: source URL: license: gpl3 platforms: cross-platform\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-275496e9534ca117f6fefe3c384eb5fa655763e0f3a7174f8ea10a55dae2469b","title":"","text":"After upgrading to eww 0.6.0 from unstable I've got problems showing some strings in some of my widgets, one that shows the hour and another the minutes using two digits each one, i.e. : \"09 : 10\". When using eww 0.6.0 the string shown is like this: \"... : ...\" In eww's github repo I can see that there is a commit after version 0.6.0: And cloning eww repo with that commit, compiling it and using a local eww executable the problem explained before disappears for me. There's also another problem, asking eww-0.6.0 for version number shows it's 0.5.0: unstable eww 0.6.0 some string truncation (I think this is the problem) see \"...\" where a two char string with the hour should appear. eww should work as expected. Cloning eww repo with latest commit after v0.6.0 was published solves the problem for me.\n~The current package for eww is . How did you install 0.6.0 from nixpkgs?~ ~As for the outdated 0.5.0 version in nixpkgs, there are three maintainers for eww in nixpkgs so it probably will be updated shortly, perhaps fetching a commit with the solution to the string truncation problem you describe.~ EDIT: i was wrong, see comment below.\nI got it installed today from unstable when upgrading my system: But, as you say, if I look for it into unstable () it shows version 0.5.0...I can't understand very well this...I'm relatively new to nixos. Ok, I'll wait then. Thanks for your interest in this.\nOh sorry, you're right! There is eww 0.6.0 in master, although it didn't make it into unstable yet. I built the package and, indeed, truncation is broken the version is incorrectly reported So the truncation was fixed, as you mention, after the release, and the reported version . That . If you can't wait, for it, i'd recommend you use the package output from the eww flake."}
{"_id":"doc-en-nixpkgs-02014dd8fbe92d71b2d592c5aaccbaf15f67a8c419924839f922b7758363182b","title":"","text":"I personally have been using it for a while and it works correctly (let me know if you need help, i'm on the matrix server with the same username). For now, I guess this issue can be closed because both are upstream bugs and the fixes will make it into a future release.\nI think I we can backport the changes using patches. I'll send a PR.\nStill I don't know how this 0.6.0 version was pulled from unstable into my system...I'm in my way learning nixos. Flakes! my never ending story :). I'll try to use it and if I have problems I'll try to ping you on the matrix server. Thx!\nSince 0.6.0 reached unstable, of course, and you updated your channels/inputs. BTW the search can be out-of-date, so don't expect 100% accuracy from it.\nYep, that makes sense to me and seems to be the missing piece that confused me: how could it be possible that in the search appeared version 0.5 and I had installed v 0.6. thanks for clarifying it for me and for your work in Nixos."}
{"_id":"doc-en-nixpkgs-e72ed13735ba03a0be4aa7b4271cacb3b9a3ee51a031a54268a1fdfd6c1f6dd2","title":"","text":"cc\nBisected to\nThis is an error when calling . We should fix git wrapper."}
{"_id":"doc-en-nixpkgs-b30f42e8043eaa3a28d9e7a4dccce080dbcb33da5585485f3984a35d6e633021","title":"","text":"Describe the bug dmd keeps references to boostrap compiler. To Reproduce Steps to reproduce the behavior: Expected behavior dmd has no references to boostrap compiler Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(symphorien): nixpkgs: Maintainer information: Note: to prevent future regressions, it would be nice to add to the derivation ()\nI marked this as stale due to inactivity. &rarr;\nStill an issue\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-eb17c19de12b3a54b024abbdcee0e28a1298dbfbeb430b0360084ae0bcec8ccd","title":"","text":"The final merged version of isn't building. Just build with the initial configuration that would give on a UEFI machine, along with: Build successfully and boot into Dom0 on next reboot. <img width=\"1201\" alt=\"image\" src=\"\"During the progress of , the issue isn't happening as of . Might be a regression happened in the last few commits before it's merged. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nWhoops. That's my bad. Will make a PR in a few."}
{"_id":"doc-en-nixpkgs-f9dec70328f8ef26b28907d16fe12adecfd33949c19fa9ec0c91303562fc87a8","title":"","text":"Steps to reproduce the behavior: azure-cli 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.\nFor now, changing python used to seems to fix the build:\nMade a PR that fixes the failure.\nWill investigate this failure and try to fix it (by using Python 3.11), but the build was working before (We may temporarily fix it using as a workaround), some dependencies must have been changed, from before, not sure which one is causing this failure, I'd need to bisect commits on master branch, I guess...\nThe failure is because of python3.11, the tests didn't work properly on 3.11. Upstream fixed those tests for a future release. For now we can either rollback the python used to 3.10, or back port the tests fixed. From what I tested, nothing is broken on 3.11 except for those tests.\nThanks a lot for those clarifications and appreciating a lot your help in fixing all this However, we can't really make sure that those tests won't break again, unless we pin a patch on those ? And this is what you've done in your fix PR. I'll be trying the latest release 2.53.1 with the dependencies cleanup."}
{"_id":"doc-en-nixpkgs-5859223ae2b8940c21745a02a88c555bd77b71e3a3a6d53d0d6527d07231a384","title":"","text":"Describe the bug The is failing. I bisected this problem to “linux: Init 5.8”. The error message matches , which points to both a workaround of recompiling systemd against Linux 5.8 headers, and an upstream systemd patch (systemd/systemd) that’s in systemd 246 () and was backported in 245.7 as systemd/systemd-stable To Reproduce Steps to reproduce the behavior: Notify maintainers Cc Metadata Please run and paste the result. Maintainer information:\nMy PR wasn't merged, Linux 5.8 ended up being by someone else.\nLinking for visibility: that PR was\nThe PR bumping systemd to 245.7 is at\nIs it really helpful to send systemd 245.7 to given that will be unable to advance without it? Or are you thinking we also want to revert the bump in for now?\nMaybe we should revert in master, and re-revert it in staging again. I let and decide about this, they've been doing the staging rounds.\nHey all, question: How do you spot which tests block the channels? I always track and every few days I notice nixos-unstable doesn't progress. When it don't I see an issue with the \"channel blocker\" label and I always wonder..\nClick on the “Hydra job for tests” link and go to the “Constituents” tab."}
{"_id":"doc-en-nixpkgs-b85f99a5ae9fc896cccac42a4f59880fe9b444ddaafcfaacc8c0ccc0a4ced755","title":"","text":"The postStart script of elasticsearch fails when a special values like or ( ) is used for services.elasticsearch.listenAddress as the script expects an IP or a hostname. Using an ip as listenAddress ist not always a viable option especially when generating NixOS images upfront for a dynamic deployment (e.g. on Azure or EC2) I am not sure how to address this issue. Perhaps one shall check netstat output to find out which ip was bound to? /cc\nYes i agree, we should implement another option for es url, I'm fine even with removing postStart. You can create pull request if you need fix asoap, I will put it on to-do."}
{"_id":"doc-en-nixpkgs-7b2a0daede1097f56e111ecddf673a419f58aaa539d9082a08d627fa3c93fd01","title":"","text":"Project description The MongoDB Shell Metadata homepage URL: source URL: license: APACHE LICENSE, VERSION 2.0 platforms: linux, darwin\nI will like to have it on too but fyi there is a NUR package.\nThanks, I haven't searched in NUR"}
{"_id":"doc-en-nixpkgs-34de8508e3f587cb46c2e45a31789c31a26a7aa06aa8584dd2e9fa2139a6cd02","title":"","text":"Package name: hyprland Latest released version: 0.36.0 <!-- Search your package here: --- Current version on the unstable channel: 0.35.0 Current version on the stable/release channel: 0.32.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]: The 035.0 has a bug that makes my system crash very often (nullptr when monitor is disconnected) the issue is supposed to be fixed in 0.36.0."}
{"_id":"doc-en-nixpkgs-a79e8e67eae5635ffe06ae13dee0b296613ad719d741b6e28374791f9621a27a","title":"","text":"After reboot, while systemd units are still loading, if user clicks on Systemd-Manger extension the entire DE will crash and Gnome will force a log out of that user. Moreover, Systemd-Manager is at v14 when v15 is out from the developer. Steps to reproduce the behavior: Computer DE loads and user is logged in on Systemd-Manager (while the systemd units [custom systemd units by the user into the extension] are still loading for example \"bitcoind\") crashes and forces log out No crashing of DE and you should be able to see in Systemd-Manager the units that have not started without it crashing Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nAny news on this? Thanks so much!\nAny news on this Thanks so much!\nUpdate should be contained in\nsweet!!! Thanks, I will keep an eye on it. Thanks again!\nI checked and plus the superseding still contain version 14. The author notes on the that they will no longer be publishing to that site, and indeed the latest version available for download there is still 14. So the metadata for that extension may need to be manually overridden in nixpkgs since it is not going to get the latest from via the automated update process.\nThis works as a standalone package, for inclusion in you'd probably be fine not declaring ,,. Would be happy to make a PR for it, though it's not something I'd actively mantain/use myself. Just updating the metadata itself wont do, as it would still be pulling from for nonexistent files.\nLooks good! That updated package does fix the crash for me.\ndid you just install the package from nixos?\nyes, it seems then having its own package would be the best no?\nAh no, it would need a PR to even get into nixpkgs. I just it to my local config using an overlay.\nokay, well I will look into how to overly in a nix file. Also, it is hard to maintain a package? As, maybe I could learn how to maintain this extension if will be unable to maintain it?"}
{"_id":"doc-en-nixpkgs-662dae9ad92f260d7c227e9a3e9fc95185c4d8d82032088ad4ba50ef4610ee17","title":"","text":"Maintaining an extension like this should be as simple as increasing the version number when a new release exists, given it's lack of external dependencies or nixos-specific quirks that need to be patched (there may be some out there). What I meant by not mantaining it is that I do not actively use it within my setup. And I assume these manually packaged ones would need at least a \"reference\" mantainer to keep it in check and direct issues to.\nThanks for the good info ! Well, I can be the maintainer, but I might need help from time to time. I will use your code if that is okay? So, next steps to put in the PR and then add me as the maintainer. Also, would you want to be on this as well?\npiegamesde was only the maintainer of the original extension package because they're the . Manually packaged extensions go in and generally have a maintainer attribute set.\nCircling back to this... I would like to be the maintainer of this plugin. However, I have never maintained a piece of software on github and I only have minimal skills with shell and nix configuration files. I have never made or packaged a nix module before. Should this task be reserved for someone else with more skills or is there someone who could mentor me in how to be a maintainer? Thank you all for the help in this.\nAdded this to extension creator's github :\nOkay, I figured out how to add 's code into my existing setup. For all the noobs out there this is what I did it: I did NOT use the \"overlay\" process in NixOS as describe here: I used the process as described here: This is an excellent write up BTW! Save this link for future use. With these resources in mind, this is what I did. I used 's code and named the file . This naming is arbitrary. It can be anything you want as long it has at the end. Then, move that file into directory. Do this via terminal and you must be the user. Then in my NixOS (not nix) configuration file () I simply into the Then, like always, as root This is all explained in the link above. Limitations: hack does not put the new is in the official repository."}
{"_id":"doc-en-nixpkgs-3bc098d4fe9136916a8e39445cc12babfba79d941428cc61d3a32e6445df3792","title":"","text":"This needs to be done by someone and they will become the maintainer. you use this hack you will have to update the for NixOS whenever the developers of release a new update.\nUpstream devs released version 16. Whoo hooo! Here is the .nix to make it work on your local machine. Again, this is not in the main nixpkgs repo. You will have to use this code and follow my \"hack\"above to get it to run in your local nix install. Thanks again to for the original code."}
{"_id":"doc-en-nixpkgs-017826ce4a4e49dc58adf01e2126d1ea8318ff7715f3f87cc1e81c931492a7dd","title":"","text":", CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc Cc\nBackporting update that resolves these ().\nFixed in 20.03 and master."}
{"_id":"doc-en-nixpkgs-90c64f30339f2405e4ae636b08838dda82f84da84fbe6dc18cc01a076da969e0","title":"","text":"Package name: gummy Latest released version: 0.6.0 <!-- Search your package here: --- Current version on the unstable channel: 0.3 Current version on the stable/release channel: 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! --- There is an open pull request () by from October 2023, but it has not been merged and later versions of the program have been released since then. I think it is also worth noting that the source code repository of the is no longer available on GitHub. as the repository has moved to Codeberg (see ). Notify maintainers (last updated the package) <!-- 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 updated my linked PR to the latest version.\nThank you for updating it so quickly! Is there a time frame in which we can expect the pull request to be merged by someone?"}
{"_id":"doc-en-nixpkgs-ba09e3ca2c19017f66a38c00caf8f5d7e653f3d96413647df65a784fdeab04d0","title":"","text":"Package name: gummy Latest released version: 0.5.4 <!-- Search your package here: --- Current version on the unstable channel: 0.3 Current version on the stable/release channel: 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 I've tried to bump the version to 0.5.4. <details<summaryThe build fails when downloading json-poputlate</summary</details<!-- If the result shows no maintainers, tag the person that last updated the package. --"}
{"_id":"doc-en-nixpkgs-9a56b65af9674fe7258c069ca8148e8a8c0eb51a2807b97599f90ddb3c49f1d5","title":"","text":"Package name: itch Latest released version: 26.1.3 Current version on the unstable channel: 26.1.3 Current version on the stable/release channel: 26.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! --- The current version is broken since butler is marked broken 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 latest version on seems to be 26.1.3 which is used in the package.\nThere is 26.1.5 as a source code , but current package uses binaryBytecode"}
{"_id":"doc-en-nixpkgs-55b543d20e58ec795558543e32e8570cddc5578fc8806f776fd87bd883680440","title":"","text":"libgtop is not reproducible, since it embed the output of into one of its binaries. See or build on 2 machines with different kernel versions. Report attached since r13y will not keep it, I think: libgtop build should be reproducible. This patch works from a nixpkgs perspective: However, it should ideally be reported and fixed upstream. N/A Maintainer information:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-f12ff9e3a78fb8d462f4b5ee2f8839a0df5aee6a6506786c080f898eba93f427","title":"","text":"Description Attempting to install conan with nix-env on Mac OS X errors out with the following message: To Reproduce Steps to reproduce the behavior: Expected behavior As Mac OS X is a supported platform for conan, it's expected that it would install. Additional context This appears to be due to conan's dependency on the python3-distro package, which only compiles on Linux architectures. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(tclemons): channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-ea80e970525c40bd26fe067aef98528248ede31b3a61b12eee8b094b329e5b7a","title":"","text":"There is about the use of imagemagick in NextCloud due to . Admins may want to disable it unless they are certain that users won't upload untrusted files (which can easily happen by accident if folder sync is active). NextCloud is only passing certain file types to imagemagick but it is doing so based on the file extension. Therefore, an attacker can pass any file type to imagemagick. I have tested this with a PNM image (not supported by NextCloud) that I have renamed to . doesn't get a preview image but does, i.e. NextCloud thinks it is HEIF and passes it to ImageMagick, which processes it as PNM. There are several ways to disable imagick: in the NextCloud config. This will not only disable imagick but also previews for PNG and JPEG (which do not use imagick). in the NextCloud config. This may need manual adjustment after a NextCloud update. the extension for PHP. This also disables it for NextCloud plugins. Option 1 and 2 can already be used by an admin if the drawbacks are acceptable. However, I think 3 is the best option in most cases. has options that disable the other PHP extensions that used to be by default. I think we should do the same for imagick. If imagick is disabled, NextCloud will automatically disable the preview generators that need it. It will also show a warning about that (which is subject to debate in the issue linked above) and there may be some implications for the themes app (which I don't use). Therefore, I think we should keep imagick enabled by default and leave the decision to the admin. We could also add a suitable policy for ImageMagick and thereby disable any file formats or features that are considered insecure. I don't think I could write such a policy and be sure that it is secure (or even \"secure enough\"). In addition, we will have to keep it up-to-date with newer versions and CVEs. That is why I recommend that we only add a simple off switch. The above information is based on NextCloud 20. I will wait until and NextCloud 21 have landed in nixos-unstable (and on my server) and then test again and create a PR if there is any interest in having this upstream."}
{"_id":"doc-en-nixpkgs-2b435ee5fa699c7e0e49ff7e3f54df7dc4a573c1c7db5090b8a005b608720857","title":"","text":"Ouch, decisions based purely on a file ext is a behavior that sounds pretty broken to me :/ Optiobally disabling imagemagick and adjusting the config accordingly sounds reasonable to me, so feel free to file a PR. You can ping me for a review or if you need assistance with modifying the module :)\nIt's ok for what they do with it. It won't do double duty as a mitigation but I guess that was never intended. Thanks. Any suggestions on a name for the new option? Simply ? Should I add any tests for that? The existing tests only test three different configurations so adding one just for imagick seems like overkill. It should be quite easy though. If we want to test that previews actually aren't generated... Well, that's a different story. We would have to automate the web interface, for that. I think the existing tests are only testing the service, CLI and WebDAV.\nAs imagemagick enabled will remain the default, I'd suggest . Yes, adding a fourth VM test just for imagemagick is indeed an overkill IMHO since those tend to be fairly expensive. I'd suggest to write a testcase in , other integrations such as are also tested there. Right that could be a non-trivial thing to solve. Maybe check if there's a REST API or a way to implement this with the CLI of . But I don't think it'd be worth spending too much time on this if there's no reasonable way to test :)\nI think we still want to test the default option in so we will need a second configuration that disables imagick. We don't have to start that VM if we only want to check whether imagick is in its closure. As there isn't any test helper for that, we probably don't want to do that though ;-) see Unfortunately, qemu on ARM is too unreliable for the automatic tests because qemu crashes when started on one of the little cores (i.e. 4 out of 6 times). I have done some interactive testing of the above commit but not an automated run. I will have to find some system that is not ARM, not high-security, not already virtualized...\nQemu/KVM does work if a kernel build or stress-ng is hogging the big cores :) is ready for review."}
{"_id":"doc-en-nixpkgs-80aa134ef177ee067ceeab68067850db33842fcc735d95d63da92ef85924397f","title":"","text":"I to and I return I got:\ncc (I had to look through essentially old SVN history to find a reference -- this service is untouched for a long time).\nI don't use this service anymore. BTW I've fixed its evaluation in the PR .\nLet's not close this unless fix hits master.\ncan you please test the fix and see if there are any more problems with the service?"}
{"_id":"doc-en-nixpkgs-117cecda982ab182689d603430f7be97377d02d3239ce1197edc04b551e114cd","title":"","text":"Imhex on unstable and nixos-24.05 crashes. Output from the above command: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nsame as pending to merge\nAh, sorry, I only searched in opened issues."}
{"_id":"doc-en-nixpkgs-1ce38f7564593687c071469cce4ff5d95e28f69c0a59d5b0e40845fea899d2a7","title":"","text":"Imhex failed to start. Steps to reproduce the behavior: -shell -p imhex --run imhex Shows the following errors: Imhex start up normally. Adding -v, --verbose doesn't give more information. I don't know how to either.\nMaintainer ping:\nCan repro on master, but can't repro if I checkout and build from it, it should be possible to bisect and find out at what point this broke.\nFirst bad commit: <details<summarygit bisect log</summary</details\nSeems there's a bunch of upstream reports of breakage with glfw 3.4\nThis might be fixed with The PR was merged into 1.90.6, but 1.33.2 contains a vendored 1.90.4, which doesn't contain the fix. My guess is that updating from the current 1.33.2 in nixpkgs to the latest version upstream (1.35.3 as of today) should fix the issue, as the latter contains a vendored updated to version 1.90.8, which should contain the fix.\nLooks like the PR was closed, are you talking about instead?\nYes, sorry. I got the PR reference from: ... which also references the commit you mentioned.\nStill crashes on imhex 1.35.3, which I more or less expected.\nAfter applying both PRs and , finally works on my system with the current . Note: both PRs were needed, either one alone didn't fix all the issues for me.\nSolved, marking as closed."}
{"_id":"doc-en-nixpkgs-a7989aab39de4ba137fd3b37dfc72ae76969f78ecb545be330164d5321138b6c","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: gvm-libs <!-- 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: 21.4.2 desired version: 21.4.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-e0c8989b3d2a000cf72201f2634d07160728b139c8fa930c30e18f6fd442e166","title":"","text":"Describe the bug NetworkManager is a particularly important component and we don't have any tests for it that could block a channel advance. In particular, a change can happen on nixos-unstable leaving users without functioning networking, and while rollbacks are possible it isn't an excuse to allow that to reach production systems. NixOS doesn't produce either. Manual testing is also cumbersome if we want to make a new stable release. Upstream NetworkManager does have some integration testing but obviously not useful to us. I think to start, if we at least had a test that verifies the services start without issues would be great.\nAgreed. While developing tests for the multipath TCP module I was surprised to see no networkmanager module. I had some difficulties with the nixos test infrastructure at first because the test infra will by default install a slirp interface () and it messed up the interface naming. Like I would clear but interfaces would still be named starting from instead of . Just thought I would mention it in case the brave soul writing the test is interested in multihoming. (but that's more a concern I have with the test infra).\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 .\nBleh.\nI marked this as stale due to inactivity. &rarr;\nconsequences of our inactions"}
{"_id":"doc-en-nixpkgs-2de6621d34a29cb7f9b5e0bf770038a4a8aa241d576a376039ce45f4814a10d2","title":"","text":"() is an old unmaintained software from 2006. Currently fails to build on due to typing changes: And also on that will need an fix: WDYT of removing instead of patching it? Is it still useful? CC Maintainer information:\nThank you for reporting!"}
{"_id":"doc-en-nixpkgs-71e148119726fe1b3e9cacfc4ab41dfc83ba4399c9638d16f798789fe78ee329","title":"","text":"Project description A Wayland-native logout script written in Gtk3 Metadata homepage URL: source URL: license: mit platforms: unix, linux\nIt's already packaged in nixpkgs-wayland IIRC"}
{"_id":"doc-en-nixpkgs-ee1c17a85eb06883f09de05d1e994f2f0711f4a54062c7bfbd88b27908ae9909","title":"","text":"Since it's not possible to use PHPINISCANDIR variable to pass additional php configuration. That breaks tools also. To Reproduce Steps to reproduce the behavior: 1 . Install php74 Expected behavior Notify maintainers Metadata\nEnv variable concatenation should fix it\nThis was intentional to avoid impure state, IIRC. The expressions we have now are very flexible. You can create a executable to include any configuration desired on the fly like so: nix-shell -p 'php.buildEnv { extraConfig = \"memorylimit = -1\"; }'. Also keep in mind you can pass configuration via to any instance.\nBy the way... are you familiar with ? Combine with and you have a really powerful combo that accomplishes what you want and more.\nsure, I'm working on this kind of setup for my long running projects and I love it. Just migrated from 20.03 where we haven't soo much options. However, for some short term scenarions (like clone, patch, test, remove) creating nix config is not an option. Most of projects maintain their own and symfony tool use them both for cli and web/fpm without any additional setup and cost. I'm ok to use php -d / php -c , but still ignores custom ini files on 20.09\nI didn't know that HPINISCANDIR can have multiple directories, but if that's the case, prefixing it in is fine. I mean, we also do that for many other env vars such as , etc.\nYeah I think that should be fine. I would like and to give a thumbs up first, just to make sure the idea is congruent in their minds. You're still happy if we don't automatically import though, right?\nThis claim seems interesting to me, I have, probably never seen a project provide a And I've been working professionally with PHP for about 10 years. And from what I can recall I haven't ever seen this before. Even working with symfony components along that way. So maybe some does, but I wouldn't say that \"most projects does\". I wasn't aware of this either, but from reading the documentation again: It's kinda clear that it allows the variable to be separated as any other like variable. I'm fine with introducing the possibility for such impurity just for flexibility for usages such as\nthere is backported version also can we merge it too?"}
{"_id":"doc-en-nixpkgs-d089c6358e7b00e932740b59d6b7e61f73d6df07585a62739454deb0a8f32d8b","title":"","text":"Describe the bug Bazel is currently broken on the latest master, tested at . Bazel was built fine back at . I'm currently bisecting trying to find the offending commit. To Reproduce Steps to reproduce the behavior: -build . -A bazel Expected behavior Bazel builds correctly on Darwin. Additional context <details<summaryError log</summary</detailsNotify 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:\nI suppose this might be related:\nIt's possible. I reverted , , and but I could not verify that it works because gcc failed to build. <details<summarygcc error</summary</details\nperhaps or can provide some guidance here. I'm not familiar with how it's all wired up together in nixpkgs.\nWhat’s the content of that fails?\nI'm trying to compare the environment of the working build against the one not working. As far as Nix environment variables go, there are no differences except for these that are missing: However, exporting them does not seem to make a difference.\nI've tried several different iterations, I'm unsure how to fix this. Anyone else would like to take a stab at this? Things I've tried: Adding clang to the buildInputs, nativeBuildInputs and propagatedBuildInputs. This was a long shot but gave it a try anyway. Exported the and . Added to the and of the bazelrc construction at line 421. Added various files in to NIXLDFLAGS and NIXCFLAGSCOMPILE I also compared the NIXLDFLAGS and NIXCFLAGS_COMPILE between the working version and HEAD, I did not find anything different.\nI am not quite sure what the actual error message produced by bazel. However to debug this, you can do to see what flags are passed to the actual gcc.\nThis is not set if c++ usage is not detected. See also this bit: If you want to include those manually you need to put them in instead. This can affect C programs however.\nproposed to check whether it’s a similar issue than what was solved in (He’s not available the next few days though.)\ndid fix this?\nThis should be fixed in"}
{"_id":"doc-en-nixpkgs-bdf88d1d0316435a36561f5fe0cba691a23464f4265ac55ccf5a58ec43799e5a","title":"","text":"Steps to reproduce the behavior: dosbox-staging on darwin Complaining that alsa-lib not available on darwin I suggest referencing the derivation of in which use to opt-in dependencies P.S. wonder why the maintenance of this package is separated from and Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI don't have a Darwin machine. Nice. A full log would be nicer of course, but nice nonetheless. Wonder why they should be maintained by the same people."}
{"_id":"doc-en-nixpkgs-c9b18e78ee7d522425ce7dde7b7aa4e9a313f157befda623c002410271ae14e4","title":"","text":"Project description Turn swipes into words -- \"plugin\" for wvkbd to enable swipe-typing under wayland SXMO. Metadata homepage URL: source URL: license: agpl3 platforms: at least"}
{"_id":"doc-en-nixpkgs-331c2212d24d1463141d547a7802b08d4928af4ced6bdf128453a318841f72e3","title":"","text":"Project description Various vim plugins iamcco/coc-tailwindcss coc-extensions/coc-svelte evanleck/vim-svelte"}
{"_id":"doc-en-nixpkgs-4f9c2ede5c02dc50f65537577be8cc2ced50b993928435719fd62b890923f651","title":"","text":"Vulkan/dxvk doesnt work on bottles. Vulkan is working correctly on my laptop as vkcube, vulkaninfo and the game im trying to run on bottles (that i ran thru wineWowPackages.staging + dxvk install from the official archive file) run perfectly. Steps to reproduce the behavior: bottles a bottle for gaming a game. the \"directx error\" pop up. Also, the dxvk log files say that the \"VKKHRsurface\" extension failed to load. DXVK/Vulkan should work on bottles. ! Please run and paste the result.\nHaving the exact same Issue on 22.11pre393800. (Raccoon)\nIf fails then there is a driver issue. Vulkan wont be able to draw anything to screen without it. When it occurs in proton issues it's usually a missing 32bit Vulkan library. Tho there can ofc probably be other causes\nupdate: using the system wine doesn't fix dxvk either. only running thru the command line does. As i said, running it thru wine on the terminal does work, so something in the bottles thing is not working right.\nI found the cause: these hardcoded paths right there: With this extra lines in , Vulkan will work on Bottles: I'm not sure if this is the best way to solve it, though. Tested only on a 64-bit bottle (I don't know if 32-bit bottles need to also link ). .\n!!! nice find!"}
{"_id":"doc-en-nixpkgs-9ffcce4757eed45c449b89c24f8973564742f1e635e31fa390e3ea396bf0a727","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: bottles <!-- 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.5.28-trento-3 desired version: 2022.7.14-brescia-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.\nWhile automatic update using was removed by in you need to wait while we will \"get auto updates from r-rynatm\"\nThat not true. I removed the over complicated updater in which wasn't necessary at all. Since r-ryantm also uses nix-update there was also no need to replace it. That's wrong. You can always create an update PR yourself by running ` or by manually update the package and create a PR with that. r-ryantm goes through all packages so it can sometimes take a few days until the update PR is created. Also nix-update is very lightweight with minimal dependencies, so there is not really a reason to not use it. It also does not require any kind of token or authentication.\nBottles the version released after the one currently present in nixpkgs, was released on June 13. Over one month has passed, so something about the auto-updater isn't working.\nThe latest r-ryantm log is here . Not sure why that is not working like it should.\nI guess a update script is needed for this case :disappointed: Since the package is using , it HAS a fallback update script , so nixpkgs-update is no longer trying to figure out the latest version itself but just run the script."}
{"_id":"doc-en-nixpkgs-b4a2a5ddada1d87ab6a10b09c7cacbb08b26c4dff5ad7654b229a1f653af7eef","title":"","text":"However seems like cannot handle the version , so it will fail at You may just try Repology gets software latest version from various Linux distributions that ships this app, so since AUR and OpenMandriva have 2022.6.14 (no suffix) the latest version is 2022.6.14. Looks like there is also an related report in Note that nixpkgs-update does not really tries to bump package in this way because it has an fallback update script."}
{"_id":"doc-en-nixpkgs-436620f4647731cb7d2b4f548e70357453966b9345947c28a5c6e5b9ca9ded37","title":"","text":"Steps to reproduce the behavior: See Broke 3 days ago, (also broken for python-3.10 and x86_64-darwin, probably here )\nSame issue when trying to run ."}
{"_id":"doc-en-nixpkgs-9d3f267099c4f5ce209c9636a7a8341aae3a9866f5ae997f58d8179881366095","title":"","text":"Describe the bug fails to build when attempting to cross-compile to aarch64 on : To Reproduce Expected behavior builds without error. Metadata nixpkgs Maintainer information:\nI marked this as stale due to inactivity. &rarr;\nNot stale - this issue still reproduces on current nixos-unstable ()"}
{"_id":"doc-en-nixpkgs-9261f5a6afc44cfd0ef742214a726068160bcbcf4345559476d0eefb53314a22","title":"","text":"This is . Trying to build bcachefs-tools` for an aarch64-linux from x86_64-linux produces: I think comes from binutils. Adding binutils to nativeBuildInputs wasn't enough to fix it.\nIt's using a non-prefixed version of , it should instead be using\nAnd after that we need to pass something like to cargo (or maybe directly to rustc?) somewhere. And we're spoiled for choice here: from in the Makefile to and env variables to maybe even .\nI was able to fix this partially with this diff: That fixed the issue but seems like our libraries are incompatible? <details</details\nSomething has to be substituted in the source because ar is hardcoded\nApplying that patch and adding The build now fails at\ncommand encounters an error? Weird.\nThe built file is in instead of"}
{"_id":"doc-en-nixpkgs-508095479daa9857836a3c772a82b6411deeb5260d6b7ff8fecdc1cc79310853","title":"","text":"is not included in the version of xivlauncher in nixpkgs, meaning that xivlauncher is currently broken. The update will need a backport to 22.05. <!-- 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: xivlauncher <!-- 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: xlcore 1.0.0.9 (upstream release 6.2.33, which I think is probably a more useful version number to use, since xlcore remains at 1.0.0.9 in the most recent release) desired version: 6.2.44 <!-- 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-46383e668b553273996cc00c36c2fe91a2c9b842021f9b58b47fd931c03574b5","title":"","text":"When adding a local directory to spotify client, it always fails due to missing gsettings schema(s) and spotify crashes. This issue is the same as the one from 2021 Works as expected on arch based distros indicating that this an issue with nixpkgs Steps to reproduce the behavior: spotify Settings on Show Local Files ADD A SOURCE button Open a file chooser to select which directory to be . <!-- 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 actually reproduce the issue, but I do see some inherent packaging issues that I attempted to address. Can you test the linked PR?\nI also cannot reproduce the issue. However, I have never actually had local files appear after I have their directories (without crashing).\nYes your PR solves the issue!!! Thanks a lot for the fast reply :) I would really like to learn more about packaging programs for nixpkgs so I can contribute more myself. Do you have any recommendations on how to learn the different options for mkDerivation, the different phases, wrapping programs and libraries, etc.? I feel like the documentation is basically non-existend. If anything comes to mind (including workshops, etc.) feel free to just send me an email (this issue is probably the wrong place to discuss this)"}
{"_id":"doc-en-nixpkgs-8210dc951eb29cf6f30223217ecbb939cd55b3948325ccb19fb6f8aad9c30109","title":"","text":"Project description To interact with Google Drive via the command line, there are and , both no longer maintained and now in my experience unable to authenticate with Google. still works, but it only targets public files and folders. There is a spiritual successor / fork of gdrive (2): gdrive 3 Metadata homepage URL: source URL: license: mit platforms: unix"}
{"_id":"doc-en-nixpkgs-15f566b0b7ee84d326bc8c6fcefa95f1ebfb4b1e043a4b6adfd6c1b127c22093","title":"","text":"Project description <!-- Describe the project a little: --An UI for search and replace on neovim It has replaced for me 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-8f15b204a1717e45f0a4c2cdf2c7ebdbf7accddf08df9bc1362e32b315c347e8","title":"","text":"fails build as Should we force package to , or maybe remove it? No maintainer. Maintainer information:\nAnd stating the obvious it broke with commit"}
{"_id":"doc-en-nixpkgs-895bb39b9ac4b058813852ead6630b893e8e98051c195ddd8b0fd380e8b6bd1b","title":"","text":"Project description mgmt: next generation config management! Metadata homepage URL: source URL: license: GNU3 platforms: unix, linux, darwin\nAfter fixing up the mgmt make scripts , from !/bin/bash to !/usr/bin/env bash trying to build from 'nix-shell -p go git' git clone cd mgmt make path make deps make Building: mgmt, os/arch: linux-amd64, version: 0.0.21-90-g5c6a66e-dirty. go build runtime/cgo: copying /run/user/1000/go-build892927552/b057/pkg.a: open /nix/store/y2nrzzz2yz7k36xvwr7bbfx76cb8jg16-go-1.14.8/share/go/pkg/linuxamd64/runtime/cgo.a: read-only file system make: * [Makefile:175: build/mgmt-linux-amd64] Error 1 go env GO111MODULE=\"\" GOARCH=\"amd64\" GOBIN=\"/home/demo/gopath/bin/\" GOCACHE=\"\" GOENV=\"\" GOEXE=\"\" GOFLAGS=\"\" GOHOSTARCH=\"amd64\" GOHOSTOS=\"linux\" GOINSECURE=\"\" GONOPROXY=\"\" GONOSUMDB=\"\" GOOS=\"linux\" GOPATH=\"/home/demo/gopath/\" GOPRIVATE=\"\" GOPROXY=\",direct\" GOROOT=\"/nix/store/y2nrzzz2yz7k36xvwr7bbfx76cb8jg16-go-1.14.8/share/go\" GOSUMDB=\"\" GOTMPDIR=\"\" GOTOOLDIR=\"/nix/store/y2nrzzz2yz7k36xvwr7bbfx76cb8jg16-go-1.14."}
{"_id":"doc-en-nixpkgs-58c3d4edc61f1e1c7509fab8a3e9bbc3c1a68bf14e377bea2a987ded6663b9a0","title":"","text":"8/share/go/pkg/tool/linuxamd64\" GCCGO=\"gccgo\" AR=\"ar\" CC=\"gcc\" CXX=\"g++\" CGOENABLED=\"1\" GOMOD=\"\" CGOCFLAGS=\"-g -O2\" CGOCPPFLAGS=\"\" CGOCXXFLAGS=\"-g -O2\" CGOFFLAGS=\"-g -O2\" CGOLDFLAGS=\"-g -O2\" PKG_CONFIG=\"pkg-config\" GOGCCFLAGS=\"-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/run/user/1000/go-build275716735=/tmp/go-build -gno-record-gcc-switches\"\nmgmt now compiles under a I'm going to need a little bit of help to turn this into a nix package, as i'm not too sure how to handle it , as there are buildgopackage, buildgomodule , vgo2nix etc etc . Any pointers welcomed. to avoid I had to remove the -i from the go build this seems to be related to this NixOS/nixpkgs golang/go to run\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-29f739ce5f3e490b92773bf1061b3a9ea1f234622217cba331a6268cab1ca3bb","title":"","text":"Project description <!-- Describe the project a little: --Tools to manipulate pdf files. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI'll see what I can do, should be good practice working with Gradle apps\nThank you Tom, much appreciated, best of luck.\nBy the way, I have pretty much succeeded in packaging it, and it seemed to run fine. Just forgot about it a little. The only issue with the package currently is that jar files are created non-deterministically by default (timestamps are not set to a fixed time). After using the fixup hook made for this situation (unzip and rezip the jar file) springboot doesn't recognise its files anymore, which is really weird. So it stayed non-deterministic. So I have two options: A) use the non-deterministic package or B) use the prebuilt jar from GitHub. The latter one is much less complex to work with.\nSee if this helps you.. or this discussion from the top (concerning java apps)...\nThanks for the pointers, though the second thing linked is my own post :) I finally managed to figure out how to fix the jar timestamps, so I'll open a PR adding the package\nThank you for your help . Much appreciated.. sorry for the delay. had a rough week last and it spilled into this one. Looking forward to using stirling-pdf on nixos."}
{"_id":"doc-en-nixpkgs-42941bac95bbbd5f086ba2606f8f773a32aeb6559d0d47911d43a361b39656a5","title":"","text":"When trying to install firefox with , I get the following error: It seems is already gone on : Considering it doesn't work on 18.03 anyway, could we cherry-pick the commit to 18.03 to disable the VLC functionality? system: host os: multi-user?: sandbox: version: channels(sepp): channels(root): nixpkgs:\nFor whatever reason, on master I seem to be getting this error even without this (or other firefox configurations). So the issue could be broader than this. I suppose for you it worked after removing this option then?\nThis is now caused by another source on ; it should be fixed by (in branch, half of binaries built ATM).\nThe other issue is also fixed on master since ."}
{"_id":"doc-en-nixpkgs-ac788cf18509c34e70e02f5282ab3b91c374863ea58c491b61d31f3fefe8ba94","title":"","text":"Wanted to install and start sweethomed.application. the build worked without problems but when i started it, it didnt started. Steps to reproduce the behavior: sweethome3d.application via configuration file to start it Starting the Application stucks at the start screen ! Add any other context about the problem here. At the moment its installed in my user context. When i try to start it as my user over the terminal i get no errors. When i start it with \"sudo sweethome3d\" I get the following error, and it also dont start, also start at starting screen and vanishing from the task bar: I think these happens because its not installed as user, but propably it helps to find the issue.\nStarting random applications as root seems like an unwise idea.\nApologies, I misread the error, this appears to be a separate issue\nJust to confirm, which GPU do you use?\nI've got the same issue, and none of the solutions given in appear to work. On my side says my GPU is . EDIT: I should mention SH3D 7.02 works fine on my setup Mmh, I just tried with , and things work just fine (even though I'm on NixOS + tells me OpenGL is happy)...\nSame problem here, on NIXOS unstable. Stuck on the starting blue window. Had to install it with flatpak in the mean time... Any idea?\nsorry for delay i dont get informations from messages in last time from github... really annoying... I have an Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics]\nSame here, also on Intel hardware.\nBased on the NixGL idea, applying the following patch works to update to the latest version and fix the driver issue on Intel. But this does not seem like the best way to go about it; I can't find a single other package messing with , and it seems more like a debugging tool than something that should be in a package.\nI forgot to mention, to avoid getting terrible performance (< 1 fps), I also had to set Not sure if it's needed for others. Maybe related to my using Wayland/Sway. I also have to use to get the window displayed properly, but that's a common issue for most Java apps and tiling windowing managers.\nI also ran into this issue with a Nvidia card."}
{"_id":"doc-en-nixpkgs-66e879ce26a928030a124a95fcd82cd667b1b1be01fc2ada7cdcf6d399a72391","title":"","text":"For me, was needed (with patch). I also needed . and didn't seem needed (or give noticable changes)."}
{"_id":"doc-en-nixpkgs-2b51a8b69a4ad13d621a97f984d0b0d0640f6ecf7f69183dbbef20af9d34112f","title":"","text":"plasmatube can't play the video (black screen). probably need to add a dependency or similar. Steps to reproduce the behavior: plasmatube can play videos from youtube. ! system: host os: multi-user?: sandbox: version: channels(hervyqa): channels(root): nixpkgs:\nsolved, need install . !"}
{"_id":"doc-en-nixpkgs-cb9bc2693413fa068476c6322b2de3165f2485cdb7263eeff7ac3bfaffb74efa","title":"","text":"Describe the bug When the filesystem scrubbing service configured via is running, the system cannot shutdown until the scrubbing is completed. To Reproduce Steps to reproduce the behavior: the autoscrub server on some Btrfs file system, e.g. by the resulting service, e.g. the system: that the system only shuts down once the scrub has finished Expected behavior The scrub should be aborted properly when the system needs to shut down. Potential solution By default, running services are stopped by a SIGTERM, but apparently the btrfs scrubbing doesn't react to that. We need to introduce a custom into the service definition. This approach still needs to tested properly though. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: Maintainer information:\nThis will also need a fires of a iirc, and then exit immediately, so there is nothing to as the oneshot exists immediately and then gets removed from systemd memory. So to get this to work we need:\nIs really needed with ? Also cancel does not accept .\nOh my manpage-in-my-head read as block device .. not as blocking.... Scrub what I said! should be enough here I think. Also I think this is a great thing to add a NixOS VM test for\nWhile I'd love to have some tests for this, these may not be so easy: We need a filesystem large enough that the scrubbing doesn't immediately finish before the shutdown is initiated.\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."}
{"_id":"doc-en-nixpkgs-27d06b57089e2d2a5a6bab3ef000119b96a236121b6f159a1e7d31d441d13856","title":"","text":"You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .\nFixed by"}
{"_id":"doc-en-nixpkgs-f957d09249e3b2201ab5d57ccdcd356617bc963cbc8330d7e74c6a727a8988ea","title":"","text":"This weekend I tried these games, all deadlocked in the menu or character selection. Nyheim Oh...Sir! The Insult Simulator Reigns Unturned (free to play) You don't have to be worried to waste money in case you want to test a game. I have had no problem when requesting refunds, just go to I have played these games and found no issues with them: Dota 2 Counter-Strike TIS-100 World of goo Faster Than Light You Must Build a Boat Risk of Rain System: (NixOS: , Ubuntu/Fedora: , ...) 03pre99759. (Gorilla) Nix version: (run ) nix-env (Nix) 1.11.6 Nixpkgs version: (run ) \"17.03pre99759.\" Integrated graphics card, 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)\nThis is normal with steam on nixos unfortunately. There are many steam games that don't work for various reasons, unfortunately many linux steam game developers only make sure their games run on ubuntu and don't really care about relying only on dependencies from the steam runtime. Some games don't play nice with certain graphics cards or drivers as well. If you want to get a particular game working (I can list 150 games that work under nixos with nvidia card and drivers at least) then you'll need to do some work, or at least post any relevant logs from the game/steam so people can actually help you solve the problem. That is assuming that they own the game. :)\nThere's a slowly-growing list of extra dependencies in the Steam package. If you can figure out what's missing, you can add it there; e.g. as in\nI don't have enough motivation to actually buy games for the sole purpose of fixing them and then refunding, sorry. Nevertheless, I'm happy to help if you can post logs and/or s -- those two are the most helpful for determining FHS-related problems."}
{"_id":"doc-en-nixpkgs-8a73ae8e2f43a86585d4d41eeebe53589fe915aa58b69cbdb69f21cec7d16cb7","title":"","text":"hooks with work by . This fails because is a plain binary that doesn’t have in its environment. Steps to reproduce the behavior:\nA workaround is to use the binary from instead.\nIt seems the above fix is insufficient. While works correctly, the hook installed into doesn't have the Python environment with the pygrep package. tested on:\nStill same problem...\nIf you pull in the above mentioned into your environment, it should work. For best results, I recommend putting it into your (& use direnv) or systemPackages.\nPotential fix which doesn't require changing the python provided in the nix shell:"}
{"_id":"doc-en-nixpkgs-393e63083e82291ae47040b07b96f1264540de4ca9e80d08b7834fb0c639046d","title":"","text":"Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: tdmupdater tdm Expected behavior tdm starts. Actual behaviour tdm starts with a black error and has stderr errors such as: Additional context It looks like the problem might be that and the assets downloaded via tdmupdater are different versions: Workaround (Steam isn't actually used for this. This is just a lazy way to run FHS programs.) Notify maintainers Metadata** Maintainer information:\nThere's a version update in master. I don't know when it'll land in unstable (maybe it already did?) or stable.\nIs it possible to have NixOS stable not break when upstream changes? Either: (a) NixOS stable should include the TDM assets (in which case tdm_update is not needed) (b) becomes solely a shim to grab assets from the TDM assets, so it doesn't matter which version of is used.\nrequire patching the path to ELF interpreter, along with worrying about lib dependencies. complicated: TDM players are accustomed to dowloading extra missions, which requires a writable directory to hold the data. Do you have a proposal how to do this securely? Hardlinking the default install to /home would break if /home is on a different FS. Suid wrappers smell. World-writable bits in /nix smell too.\nSurely the engine supports multiple asset directories, so we can load the assets from the nix store in addition to whatever was installed manually into a local directory.\nThe comments on suggest The Dark Mod stores save games in its installation directory. tracks this issue.\nI have another issue that seem to be related. Running tdm via the ` work however. The relevent line are: When it doesn't work and with the second option\nI poked around - and I don't have any ideas why OpenAL might not be finding hardware. Right now, it seems that the best course of action is to remove TDM from repos (to avoid creating false expectations), and run it with steam-run. and do you agree?"}
{"_id":"doc-en-nixpkgs-18c8891dc808b69dc00bd7b1077d04c096210ccb8e6d1bdd546ac22c625a14ca","title":"","text":"Project description Scalene is a high-performance CPU, GPU and memory profiler for Python that does a number of things that other Python profilers do not and cannot do. It runs orders of magnitude faster than many other profilers while delivering far more detailed information. It is also incorporates AI-powered optimization suggestions. Metadata homepage URL: source URL: license: Apache 2 platforms: unix, linux, darwin, windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-d7410a67ef5035224da5e0190d75c201d07c42ca73df763ba87672cda9ea92f7","title":"","text":"The build is failing on master; it has been reproduced at . An example of the failure is below: There is a new release () which also doesn't pass, so I didn't send the PR as it'd fail on CI. Steps to reproduce the behavior:\nThose aren't the failing tests (BROKEN means they are known to fail). These are the real failures: Looks like a broken test directory setup in the build environment.\nfixed in the next point release I think\nprior work"}
{"_id":"doc-en-nixpkgs-2cde3e6ebf9918c7dc0e21da7f8f4169971cc42a299dade9635aaa0b3cdf9c1d","title":"","text":"Project description Wavefront is VMWare product and, per their website, is an \"Enterprise-grade cloud monitoring and analytics at over 4 million data points per second.\" The service can be provisioned via Terraform -- there's an OS Terraform provider available here: It should be included amongst the set of existing Terraform providers that already contains. Metadata homepage URL: source URL: license: apl2 platforms: linux"}
{"_id":"doc-en-nixpkgs-8498e9b5eef60b2a87c634eae13a7a6214fe617f51c3b8540b725a24336f75b9","title":"","text":"Tailscale package is not using the unless is set. Steps to reproduce the behavior: tailscale and set a flag ==no flags are used Flags are used If applicable, add screenshots to help explain your problem. Code reference: extraUpFlags is only used inside the if of auth key not being null check. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThis caught me out too - could just be as simple as a warning/error when setting without ?\nI don’t think that is adequate as you can run tail scale as server just fine without argument. An is only valid for up to 90 days.\nSure, but it would be a good start to alert users to the current behavior.\nI was managing personal nixpkgs only because of this issue... (simply patching package doesn't seem to work for modules) Created PR for this. Hope someone can review this."}
{"_id":"doc-en-nixpkgs-d3d29d090fc8750cc7384eed5d044bad7bf9d56e5da6f0c97d020a09f8888449","title":"","text":"Steps to reproduce the behavior: status: status: status: This was discovered via pr <!-- 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 seems like some tests have began to fail. When testing, the traceback shows the following tests fail because they don't initialize the module correctly (with ). - These tests don't undermine the functionality of when building from source, so I'm inclined to believe that the culprit is itself. Looking further, throws various deprecation warnings when the tests run. I fear that the more NixOS receives updates to , the more the tests will become more deprecated. It's unclear how NixOS feels about packages and their tests (particularly whether it's necessary for a maintainer to maintain package tests), but the current workaround is to disable these tests. Adding the tests to the field produces the result package, and continues to work as normal. I'd like some input on how to approach as this does feel pretty hacky.\nWe could override pytest back to a previous working version. I looked to the upstream package and it hasn't been updated in a year, to which was just a readme update.\nWouldn't this affect newer packages (assuming they use as a unit test framework) who utilize newer features of ? Though hacky, the solution I've suggested gets the job done. As mention previously, the failure of the tests don't influence 's functionality.\nDisabling problematic tests is done a lot across nixpkgs. Since we know its still working when they are disabled it should be fine."}
{"_id":"doc-en-nixpkgs-d1c8c173e848c324a8f3e9c6d3859768ca816ff5b139a6a78e0fec8a1a6f4acb","title":"","text":"Project description A CLI program that will let you save and apply your Linux customizations with just one command! It officially supports KDE Plasma but it can be used on all other desktop environments too! Metadata homepage URL: source URL: license: gpl3 platforms: linux"}
{"_id":"doc-en-nixpkgs-47ea3a63e945f3c556c59be14cb4d9ba13b394d4324db5fa66eb8fdfa7b92b0b","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.7.3 desired version: <!-- 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.\nI started preparing the update in . Cc:"}
{"_id":"doc-en-nixpkgs-473c5d2fef0a556879a529591218999340542741c576b2e10b3959100fe24669","title":"","text":"There is a license violation in the package. The package contains the code for under the old MAME license which is non-commercial and incompatible with the GPL code in the rest of the program. I tried to notify upstream, but that didn't seem to go well...\nHello! It seems that upstream actually an option to disable in version of . , from my testing, gives me an error when I try to run it. You can find more info in this . So, i think merging the pull request linked to this issue is the best option right now."}
{"_id":"doc-en-nixpkgs-a4d8261d47ec110fad60d754710166ce86f3c2d9579a8d63a8a740f54a88cd3b","title":"","text":"Xed Text Editor from Linux Mint Text editor from the Linux Mint distribution xed text editor homepage URL: source URL: license: gpl2 platforms: linux\nneeds an update of a dependency to package newest version 2.8.4"}
{"_id":"doc-en-nixpkgs-333eeea437d579ccccc2985a5e03cdcaa7b1e4b0e5fb94f937832c7f2c98ed68","title":"","text":"The package 18 on master failed to build. Steps to reproduce the behavior: build github:nixos/nixpkgs#clevis ! Full build log:"}
{"_id":"doc-en-nixpkgs-c9e0af6925bfe574950706141b2e5250ae55daf28e2cfbc4699c8c21c345c9d4","title":"","text":"The repo URL is missing for: To fix it, you can fork (I forked it for preservation but neither of us made changes: ) then change the GitHub username in the nix file to yours. I don't have NixOS or have any way to test this. I ran into your nix file while trying to find the maintainer: I asked whether the repo has moved because it is deleted from GitHub. I contacted him via 's contact form and I'm awaiting a response (I didn't try an e-mail address found here yet: ).\nRecently I have read somewhere that the author was absent from some social media, and that for personal reasons he has removed his account on github, and that this software is still available on launchpad. Github was just a second home for it. But I am not finding this info anymore.\nOk, the author responded to me via e-mail that the launchpad URL is correct, but that he isn't maintaining it. He says he's more likely to rewrite it in Rust rather than update it. The nix file can be corrected to use launchpad, but in light of that information, using one of the GitHub forks or forking one of them yourself and turning on the \"Issues\" feature is probably the best route to a future for it, even to a minimal extent of getting bugfixes.\nI am changing the upstream source to the launchpad repository, as it is the most correct. I am also watching the two forks on github, so that I will be notified of new actions on them."}
{"_id":"doc-en-nixpkgs-1ebad7700f34c9968ffb1029b0d5be63d9bd8363f449cb18b9aee1227d4c2eaf","title":"","text":"Package name: Apx Latest released version: 1.8.2 <!-- Search your package here: --- Current version on the unstable channel: 0-1 Current version on the stable/release channel: N/A <!-- 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-b4687572bc3e6be0eb740c0b6f9733fd9899441513edcbdba94fa26614222b3b","title":"","text":"I just filed a to update our version of CEF to fix a . The previous version was released on 2019-07-27— that's almost 2 years! For a piece of software that's functionally a web browser, we certainly shouldn't be using an out-of-date version: web browsers have a massive attack surface and it's very important to keep them updated at all times. I don't have the time to work on this right at the moment, but it shouldn't be too difficult. There's a containing metadata for every CEF release. All that should be necessary is to grab the latest stable version for the right platform. While we're at it, we could also consider building for i686 and AArch64. Tagging the maintainer\nIDK how it works, but it sounds like a job for the bot ()."}
{"_id":"doc-en-nixpkgs-d01c2a7d23f97cb7135b1e8de707fd8bfda8d3a47a0c97df97324d914441abdb","title":"","text":"HTTP Toolkit is an open-source tool for debugging, testing and building with HTTP(S) on Windows, Linux & Mac. Metadata homepage URL: source URL: license: AGPL v3.0 platforms: linux, darwin\nSorry, wasn't able to get it working. The httptoolkit-server is the difficult part. I tried building from source, however one of the dependencies tries to npm install more stuff in prebuild, so it wasn't building properly. I tried packaging the prebuilt binary but it's trying to do some auto updating and also package node with itself. I could have patched this when building from source, however the prebuilt one is minified & obfuscated so I couldn't do that.\nHave you a branch to continue the work ?\n+1\nI've started a small bounty of 20$ on this: It's not much but it would be great to have this tool on nix!\nI made another attempt at packaging this and I'm pretty close to getting httptoolkit-server to compile from source. This should help with patching out stuff, since we can do it before it gets obfuscated.\nif anyone needs to run this on nix the appimage provided by HttpToolkit works pretty well on nix with no extra dependencies. See and then Would still be great to have this as a nix package though.\nHey thanks for adding this! You can claim the gitpay bounty here: (I've tried to find your email to invite you but didn't have much luck) or email me at\nSent you an email,"}
{"_id":"doc-en-nixpkgs-53bf72741da8f718ce5bfb94c687d54ef9430a866067cd5e4ad3b68dd0271a49","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: mednafen <!-- 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.26.1 (dated November 10, 2020) desired version: 1.29.0 (dated January 19, 2022) <!-- 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-28544d1fcc73ea3214b0b3580e9196c6749defd673224a39ad4b77291ed55054","title":"","text":"Steps to reproduce the behavior: dvc with aws integration I am running nixos on the unstable branch. Please run and paste the result. Probably fsspec needs an update to 2022.8.2\nWill be fixed with .\nOh sorry for the noise, did not search the PRs."}
{"_id":"doc-en-nixpkgs-d9ffaeef3a55537037896e616b43bedef62fd209075434a4c0dde11878315cf2","title":"","text":"Steps to reproduce the behaviour: PyInstaller on Darwin It fails to build at gcc as gcc is not avlible on macOS CC <!-- 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]:\nIs it possible that you can make gcc only in linux but clang if pyinstaller uses clang for darwin to use that?\nI got it working I am willing to contribute a fix to this.\nI will need to some how package since requires it for macos systems.\nBut first of all since gcc is required on linux is there a possible if linux include gcc instead of clang.\nBased on , it seems like and the stuff is only required on linux. Maybe we could just throw in a here? Do you know if more needed to be done to fix the darwin build? Feel free to open a PR if you'd like.\nYou need which I am looking to make a package for and I think I still have to test if you need . I am looking to make a pr in a couple of days to fix both pyinstaller and package\nI think gcc can be replace with clang which is compatible with both linux and darwin.\nMacholib is now in a pr:\nNow I am looking to fix pyinstaller for darwin."}
{"_id":"doc-en-nixpkgs-30faaca2638b8db72a49a984262a1ae7b1d40390854da1c1ac4b3e8efd1a2129","title":"","text":"Project description A highly automated and intuitive digital audio workstation. Metadata homepage URL: source URL: license: AGPLv3+ platforms: linux\nThis is a stub of a derivative for ZRythm:\nDid you see It's for an older version, and I haven't compared it to your gist, but maybe you would like to do that?\nI marked this as stale due to inactivity. &rarr;\nStill relevant."}
{"_id":"doc-en-nixpkgs-3eb67e85b32edb5988a4eaf8d7795321c46aed896c8ab29ae1ba655d10d0686a","title":"","text":"The [monado] package doesn't install the udev rules generated by the [xr-hardware util] from the Monado project. Install the package and check the lack of udev rules in It was expected for the udev rules to be installted with the package. The udev rules are needed as some hmd's have some strange and specific permissions. Maybe instead of adding this to the package, monado could turn into an option like . <!-- 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]: [monado]: [xr-hardware util]:\nTrying packaging the udev rules similar to how . [brscan4]:\nI was working on a Monado NixOS module. Perhaps I can deal with udev rules there. See"}
{"_id":"doc-en-nixpkgs-bae14fa5f830a029fe7ce39b529cf8809e98f73c43d4cb83bf50c26a59138f98","title":"","text":"Describe the bug cmake-gui doesn't launch it shows an error like:- 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-56fe156d4613c90c2263f76b39829a77e7a7d186ad3c5025fbd87dcff1e42339","title":"","text":"Package name: digikam Latest released version: 8.2.0 Current version on the unstable channel: 8.1.0 Current version on the stable/release channel: 8.1.0 Notify maintainers 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-0bfa5270dc36b7d3ce66b0dd18047b1c4b1c1600dfdb6a1546c1311f95f37899","title":"","text":"Not valid cryptography in python3 ... Steps to reproduce the behavior: switch \"Screenshot\" Install yubikey-manager ;) 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. -- as cryptography maintainer Please run and paste the result."}
{"_id":"doc-en-nixpkgs-9f1c9b63864fedbfdbaa0b35232a5bad9392f66fe79c1fe90b3769963191041d","title":"","text":"I set up a brand new NixOS system with nothing but . After switching to the new configuration, I ran and was surprised to find in there in a and state. I poked around and it turns out that our module refers to in its section: It sort of makes sense, because presumably you want your webserver to spin up after your database, but it feels kinda icky to give completely unrelated (in principle) services dependencies on one another, especially when some of them might not even be on your system. I suppose we could make that entry conditional on , but I'm not sure what the pros and cons of that are.\nYes, I'd think it would better be conditional. Units should get reloaded on system switch IIRC, before starting new services, so I see no danger in that.\nI think, this link should be broken unconditionally. In my scenario apache-httpd is used solely for SVN web interface, and while I have running Postgresql instance, they are orthogonal (postgresql is acompanied by tomcat container/nginx pair)\nPerhaps, yeah. It also appears to depend on , which I think is a nixops-ism."}
{"_id":"doc-en-nixpkgs-70222b8350914ffaae99091fd719ee715c3a5ced213af7254da5c688429cd3c0","title":"","text":"Describe the bug Building neovim doesn't work anymore. To Reproduce Checkout master branch, commit (latest as of now), then build: Expected behavior Building neovim should succeed.\nThe failing code is (...-stdenv-linux/setup: line 320):\nHaving the same issue when updating my system.\nPing I think this has something to do with the recent stdenv changes. Do you know how to fix it?\nThis is from which breaks this manual sourcing of setup hooks I say this is a good thing! We should make those proper dependencies. I will fix shortly.\nI have a similar issue in stdenv-linux/setup /nix/store/fiaj00zrmb7dynd2q9xmcrh5rn0mjwj0-stdenv-linux/setup: line 97: $'r': command not found builder for '/nix/store/frqmqjyg649bkqivqhzq041fxbfvsikw-cockpit-' failed with exit code 127\nThanks!"}
{"_id":"doc-en-nixpkgs-fa4a32f6e49815a7601992cd1d0d98a5748d4203709fca24c13a41e46b5d05b5","title":"","text":"cannot process svg files despite the documentation advertising it can. Steps to reproduce the behavior: SVG should be supported Introduced in Build logs: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-b88f2aa36bc4470afb4342249b10a96ec75c052ad5c7d3b87bbb00157b5ab420","title":"","text":"This is especially important for Home Assistant, which and fails to build without it. Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR.\nCan you tell me what nixpkgs version you are using? On master home-assistant builds just fine, with bcrypt at 4.0.0, because we do in fact relax its constraints a bit. Added variables. nix-replhome- «derivation /nix/store/044cr7v736265qjiq2b3vc7r7hxbaqfd-python3.10-bcrypt-»\nI'm on . More build logs:\nUpon further inspection, the file does appear to be patched correctly, but there are still in and . Maybe those have something to do with it?\nMy bad, I just realised I was overriding without including the original\nThat explains it."}
{"_id":"doc-en-nixpkgs-fc7af294ae92797743c832a4bd070673650fa5e986c6f83d3c9ed4e24f01707e","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."}
{"_id":"doc-en-nixpkgs-48d6df343288765639073b6c2560bcab44bba033afd46fe03f5e7adeb01b63b3","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.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI opened a PR here: Thanks in advance for reviewing :-)"}
{"_id":"doc-en-nixpkgs-aaaefae16fb09364f07532c9b727f4f1e111587200229c39d2e4b31365e6368e","title":"","text":"The  package (which I and maintain) has a that is rendering wrong at It seems that I used the wrong markup language. I'd like to ask: what is the markup language that we're supposed to use in s? I've been unable to find an answer to this in the documentation, and unable to find a working example in some package's file, even though IIRC I've come across some description in search results that correctly rendered some quoted code with extra styling. When I first wrote my package's description, it was 4 months ago with NixOS 21.05, and I'd somehow thought that DocBook was the correct language to use. Looking at other packages' descriptions, I see some other attempts to use markup (or Markdown), which is maybe what influenced me, but now I see that these are also rendering wrong. My longer more-structured description looks especially bad, so it should be fixed.\nAs far as is just plain text."}
{"_id":"doc-en-nixpkgs-9d97813314902e3d9a94758d31f0f20a44969db08e938ce1fcaff118d6b16966","title":"","text":"A config file is read-only, which causes the program to fail entirely. The leo text editor should run when invoked. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nNot fixed:\nthis has been fixed on the master branch however has not been backported. I'll create a PR to backport this, in the meantime if using flakes you can update nixpkgs to follow master or nixpkgs-unstable otherwise you can update your channel to follow unstable. works fine for me. EDIT:\nAre you sure? Are you sure?\n!\nworks on my machine, which makes it extra strange that installing it locally with a flake that is pinned to does not."}
{"_id":"doc-en-nixpkgs-60b0b846f827b4db311361b6bd547deaa8a9a8b5182ec85d125eb718ef67ad18","title":"","text":"Steps to reproduce the behavior: ouch on x86_64 darwin Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-c0296c37730fb6d3cecd6a4108cf3f2f0a7ede0993eec6fe06c9f95f1caefe66","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: mpv <!-- 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.33.1 desired version: 0.34.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-564c651c57e944a0e0958d90987d5de831a00b074fc43c4a39287d2063d5c780","title":"","text":"They're trying to be smart: We should probably patch that check out, but maybe people with actual Java experience will have better ideas.\nWe need to patch that. Neither do we want to provide cygpath nor can we wslpath because that would most likely try to escape the sandbox.\nThe thing here is that they see WSL and automatically assume we're cross-compiling to a Windows target, which we're not. We can patch this out, or maybe we can force it to not cross-compile somehow, or maybe we can make lie.\nI would recommend to just patch that out."}
{"_id":"doc-en-nixpkgs-94e12579780a3af659c79c968e58c4661e21d30f444bf3506e2c48079bafcc5e","title":"","text":"I'm trying to use it on aarch64 and this is failing: [6/257] Building CXX object FAILED: /nix/store/fsn9mccnjinl212ypa3rx8b8647s9klh-gcc-wrapper-12.2.0/bin/g++ -DCEFUSESANDBOX -DNDEBUG -DWRAPPINGCEFSHARED -DFILEOFFSETBITS=64 -DSTDCCONSTANTMACROS -DSTDCFORMATMACROS -I/build/source/thirdparty/cef/cefbinary104.4.26+g4180781+chromium-104.0.5112.102linux64minimal -O3 -DNDEBUG -fno-strict-aliasing -fPIC -fstack-protector -funwind-tables -fvisibility=hidden --param=ssp-buffer-size=4 -pipe -pthread -Wall -Werror -Wno-missing-field-initializers -Wno-unused-parameter -Wno-error=comment -Wno-comment -Wno-deprecated-declarations -m64 -march=x86-64 -fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -std=c++14 -Wsign-compare -Wno-undefined-var-template -Wno-literal-suffix -Wno-narrowing -Wno-attributes -O2 -fdata-sections -ffunction-sections -fno-ident -UFORTIFYSOURCE -DFORTIFYSOURCE=2 -MD -MT -MF -o -c /build/source/thirdparty/cef/cefbinary104.4.26+g4180781+chromium- g++: error: unrecognized command-line option '-m64' ninja: build stopped: subcommand failed. error: builder for '/nix/store/a7r53z6050vvhlmwnxac6c6kp41gcz2g-jcef-jetbrains-' failed with exit code 1; last 10 log lines: For full logs, run 'nix log /nix/store/a7r53z6050vvhlmwnxac6c6kp41gcz2g-jcef-jetbrains-'."}
{"_id":"doc-en-nixpkgs-d5a82ae8f19fba879a24ecf4b71bafe2e4c3e4e6780c70c0f8244847a2577f69","title":"","text":"error: 1 dependencies of derivation '/nix/store/9mds0h6675lnh8hgam63xycvv8lrb01v-jetbrains-jdk-jcef-17.0.6-' failed to build\nWSL2 on aarch64? Also, this error is for Chromium.\nSorry, never mind. I'm having an issue with , that has a dependency on CEF. I posted in an incorrect place. I opened a separate ticket. Please ignore."}
{"_id":"doc-en-nixpkgs-61994e74a2d7239015845caf051a36096bc5ff84c6cb09017e94c5b6b7b9dabf","title":"","text":"Project description A command line editor for HCL Metadata homepage URL: source URL: license: mit platforms: darwinarm64, linuxarm64, windows_arm64 Release page: Copied install info from readme: If you are macOS user: Download the latest compiled binaries and put it anywhere in your executable path. If you have Go 1.20+ development environment:"}
{"_id":"doc-en-nixpkgs-20893d406585a002426fc5d51e22a14b6ce7af9990d709c7706806fb17c7b4bc","title":"","text":"The package is failing to build Steps to reproduce the behavior: The package to build successfully without errors\nI'm sorry, I haven't used in years - but also nothing with that package has changed in some while. I'd assume an upstream problem?\nI don't use but took a look out of curiosity. It was an upstream problem that is fixed by a few commits after the latest 2.4.0 release. There hasn't been a new release since then. Is the best thing to do here pull down that commit as an isolated patch or to bump the revision that's pulled down to that (untagged) revision?\nCan we use in the meantime?"}
{"_id":"doc-en-nixpkgs-2a26cb0e81874b2c32dd9b1e833a44c692fe633e9276c6da43883fc6f1d8ee94","title":"","text":"Steps to reproduce the behavior: python3Packages.rapidfuzz Introduced in . Please run and paste the result.\nIt appears that cmake selects an incorrect linker. I am currently unsure what's the reason for this. Following I think I might need to set: I have zero experience with nix os + no access to a mac. Is there any way to patch in the build system here to check whether this solves the issue?"}
{"_id":"doc-en-nixpkgs-ddd3dadc387fa3d416ac0db6c8c5f1a7476a092654bcc0f0a00b07e7fd67a6e6","title":"","text":"I get this error when the packages i build contain any musl one. Blocking me from reviewing PRs. Full error: Issue for a more helpful error message: Steps to reproduce the behavior: No error. I think the solution would be to disable musl libc on i686-linux until it actually works. So Nix or nixpkgs-review don't even try to build it. <!-- 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:\nCollecting information: this looks fine maybe here needs to be a check for 64-bit"}
{"_id":"doc-en-nixpkgs-fea7dacdfcfe354c937297bc7d6b9ef7630f2244d594f353fbda0b7a4397f38f","title":"","text":"When I try to open the warp-terminal on wayland it crashes without opening any window and get the following logs: Steps to reproduce the behavior: to open warp-terminal happens It should open the warp-terminal window and prompt. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nMight be helpful:\nFixed in , I tried running () on KDE Wayland and everything works as expected\nA warp-terminal dev has stated that wayland support is explicitly still experimental and off by default for this reason. Please do not open issues concerning configurations that are explicitly unsupported by upstream.\nSorry, I didn't know it was explicitly unsupported by the upstream since it was working before just fine on Wayland. Thanks a lot anyway!"}
{"_id":"doc-en-nixpkgs-0e86a7c0f13ac35d790baea024ead42fb524ac22bc9f6e87baf104eaf1b11912","title":"","text":"Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.\nYou don't need to open an issue if you're going to make a PR right after.\nApologies, my bad. I was not aware :(. I am only 1 day & 1 PR old here."}
{"_id":"doc-en-nixpkgs-2804bb8c9f1d546440b76d6665fd93982e6b5113793a17f212c364edb3b99833","title":"","text":"A clear and concise description of what the bug is. Steps to reproduce the behavior: created with expected behavior from This might be due to vhs being outdated in nixpkgs. Please run and paste the result.\nNixpkgs has since been updated to the latest version (v0.2.0), and the error still occurs on the latest Nixpkgs commit ()\nAny suggestions on a fix?\nI believe the fix might be to include as a dependency and ensure that looks for the binary in the same place nix installs it (i.e. it is located in the as chromium):\nThe PR for this breaks vhs on darwin, since chromium isn't supported on that platform\nThanks for filing a new issue"}
{"_id":"doc-en-nixpkgs-c15d5200452a4212c33395ab628ba9351ed78ead36e0d22e74b63026cbd9aa25","title":"","text":"It would be nice if the package included shell completions for bash, zsh, fish. Steps to reproduce the behavior: (In fish): pipx-specific shell completions should show. One problem specific to is that the instructions you get with do not work unless you know to install the binary first (e.g. ). I hope that mimicking would work (though I'd also like completions to be included). I might be able to try that myself at some point, but I'm not very familiar with testing that a patch to works. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-1e617540d621073aef89c6328c1bcb655eb5fd64b0319eee023d4776a635129b","title":"","text":"the strict commit history guidelines require frequent use of , a command which may be unfamiliar to those that are used to projects with more lenient commit guidelines. find or write a high-quality guide to and make it available in <!-- 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-2173b17f9835e3fac524fa0f91291503e0589e81a2702e2ebead5c3276a29db4","title":"","text":"So I today I spawned a machine with and satisfyingly the directory was generated with all of the certificates etc that taskwarrior needs, including the clients' certificates. I noticed that the users' keys located at are owned by root with read only permissions for the root user alone. No matter what are and . I'd like to enable the group read those client keys, as well as the file so that I can configure a client easily. Thankfully the group can read the file, but not the client keys. The manual indeed explains that the command: Could be used to get those keys, but I'd like to use syncthing for that to automate the process even further. I got a bit lost while reading the . Specifically, I'm not sure why does always works in the following umask: I mean, ~why not~ - a solution is suggested in . A word of comment will be appreciated. cc ."}
{"_id":"doc-en-nixpkgs-8d9990a80cf372d63fc0fd8f3d16e9315bcf45e4f4e7cca1c2589e90f6ffb22b","title":"","text":"hangs when given a derivation because of infinite recursion either error or treat it as a string, which all other generators seem to do <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:\nis there a context where a derivation would even be a valid input for this function? If not perhaps a simple fix would be to test for a derivation as input and simply throw a warning instead of continuing computation.\nit shouldn't be possible to use derivation as a attrset for this function, but store paths could be useful which is similar to 's behavior\nSo this worked without error: I was able to reproduce the issue by just passing your example input above though, and in looks like nesting the derivation deeper also still causes the error. I guess we could map over the input at the start of the function and convert any unconverted derivations to strings before moving on. That should allow us to declare store paths and avoid this issue. Side note: you shouldn't have to restart your system to recover from the error condition; worked for me\nI forgot SIGKILL existed. I removed the warning in the description\nI have run into a very strange issue. I thought that the following patch should be all that is required to fix this: however even though I confirmed in repl that the conditional evaluates to false when passed `\"${hello}\", the codepath guarded by the conditional still seems to run anyway and fails with the following error: to add to the confusion, if I push the value one level deeper then it works fine:\ni don't think ini support values at top level, or maybe its just the ini generator?\nah okay, then I guess my change is completely ineffective. I'll keep iterating :laughing:"}
{"_id":"doc-en-nixpkgs-81ed35f0052ff44f43d718f46a949ba5bc2986c49c7db6c456eccfb2ddce2349","title":"","text":"Helm defaults to a kubeVersion 1.20.0, which is 3 years old. Steps to reproduce the behavior: Would expect that helm defaults to a kubeVersion that is apart of the supported Kubernetes compatibility. helm 3.12 should support something similar to kubeVersion 1.25 accorsing to their version skew, The last version of helm to officially support 1.20 was 5 minor version ago Unclear where this default version is being defined. Downloading the corresponding binary directly from (example: ) does not encounter this 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nGreat timing! I just ran into this issue not to long ago but I'm unsure how to resolve it. (On mobile so I'm going from memory) there is a hard coded version in the helm or something like that, that can be overridden at build time. Presumably the helm team does override it. We can of course override it as well but I'm unsure how we can keep it up to date. It would be a 1 line patch to fix it for now but my question is, is there an automated way to keep it at the same version as whatever the helm team uses\nnormally helm takes the k8s version from the go k8s client lib and increments the first part by 1 to arrive at the k8s version. On my current dev system the output is as following (debian sid) In go you can directly set via as the Makefile does, but it's not always clear that those things can just be overridden that easily. i'd prepare a patch but i've no idea on how to add some script execution into to fetch the variables :/\nI am not sure how to add in script execution either. As a low tech eventual solution, opened a pull request to resolve the issue upstream."}
{"_id":"doc-en-nixpkgs-6d59f95a80cad9fc90f6821f50484304ce945fdd9f7ae45846679bfad520a193","title":"","text":"Project description A pure rust implemented turn server. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: gpl-3.0 platforms: linux, windows Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-a736a29de40c2879944dcf99983844a0e068ff5da940d05f81283b776fef7c29","title":"","text":"fetch-bower produces truncated nix-store entry when run under nix-build: Looking into the retrieved jquery in the nix store you can see jquery is actually missing: It works fine when trying to manually run it as a regular user: bower- generated by : run nix-build System: (16.09beta172. (Flounder)) Nix version: (nix-env (Nix) 1.11.4) Nixpkgs version: (16.09beta172.)\nping\nSorry for the delay I will test and merge today.\nHello thanks for your detailed report. I am getting slightly different results to you, so more investigation will be necessary. In my environment (NixOS 16.09 channel), there was no hash mismatch. Possibly something caused git to fail to download the jquery package. If it silently fails producing an incorrect result, then that is a bug in bower2nix which could be reported at\nI am not sure this due to bower2nix. Fetch-bower is calling git and should handle the error's accordingly, no?\nIt consistently fails for me both on the latest unstable and 16.09 channels. Can you try updating your channels? My suspect was commit but I wasn't able to revert it cleanly to try it out.\nBy , I also mean . I have rolled the two programs into one repo. You are definitely right, is calling (indirectly, through the API), and should handle the error. I'm an avid subscriber to 16.09 and especially nixos-unstable, so have tested on those. Obviously it would be easier to fix the error handling if I can make fail myself. Do you have any further info about your setup which might be relevant? E.g. any proxy settings required for git to work. Can I also confirm that you are running before retrying ?\nI don't have any proxy settings. Is it possible GitHub is rate limiting requests from bower? I found this thread interesting And yes I am running nix-store --delete before trying nix-build.\nHi are there any additional details I can provide? I am not that familiar with typescript or javascript, but I could try to narrow the issue down with some help.\nHow to reproduce: Expected output: bower package info json."}
{"_id":"doc-en-nixpkgs-77ecf19fefa55a64531d56ac4748b69ac6d529be081c870966f652edeb099c02","title":"","text":"Actual output: nothing, not even an error message.\nThis problem is back. I can reproduce it by following the steps outlined in the top message. (latest nixpkgs-unstable) It did work for me a while ago though, so it looks like a regression. Did some digging around but I cannot figure it out. cc\nGood catch, I think I've seen the same issue as well, but didn't bother (lack of time). Could be a different cause, but we have to start somewhere :)\nRunning produces correct result while -ing the following produces an output without jquery (just meta data)\nFigured it out. Git doesn't see SSL certificates. I made it run with this expression I'll try to open a PR to fix this in nixpkgs. I'll also try to open a PR to bower2nix because there is a bug in it - missing SSL cert should not result in exit code 0."}
{"_id":"doc-en-nixpkgs-166bb0ed0ba00d7a2765f2b0ae25700b87219a6d432c0b65fa991dba8fc17df7","title":"","text":"Project description <!-- Describe the project a little: --This is a electron-based app client for Pritunl server Metadata homepage URL: source URL: license: Non-Commercial platforms: linux\nPending review in"}
{"_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-255d8ccc91d454c8765422bd7ebd88546ee975d15f20501d006cda4d0e5082b8","title":"","text":"Package name: upterm Latest released version: 0.12.0 <!-- Search your package here: --- Current version on the unstable channel: 0.10.0 Current version on the stable/release channel: 0.10.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. -- tried\nBumping to 0.12\nSeems this need the vendor path now."}
{"_id":"doc-en-nixpkgs-c94e6ef8ffbecc2fd36f73b4cc75b41941b83324329edfac506721856c1b4128","title":"","text":"On nixos-unstable libglvnd (I think) has been failing to build since about a week ago. Build log: Update to the latest nixos-unstable channel Run with nvidia in\nRelated?\nActually it looks like this PR fixes this issue. Though nix channel is not yet updated.\nConfirmed. Adding the following override fixed it for me:"}
{"_id":"doc-en-nixpkgs-afa9d1459b23566e2c86f4c71a729ecfb27274219d7993e8363a99c9d0784b04","title":"","text":"Every new firefox update/rebuild generates its own (new) profile. This is annoying, as we rebuild firefox whenever any of its dependencies changes. See: Start with the profile manager or with a custom profile\nShould not it be just one profile per branch – one for stable, one for beta, one for nightly? Updating should not change the branch.\nI thought that too, but at least for me it created 4 profiles already - could be, that the FF beta is not smart enough (yet). Anyway, now it's documented, so people hopefully won't get as confused as I've been when/if they reproduce this.\nCan repro as well. Unfortunate!\nNot explicit above, but the workaround is: you see \"this firefox uses a fresh profile\"... quit firefox profile manager with an older profile and \"use as default profile\" as normal until the next update\nRelated issue: and workaround:\nFirefox 67 is now the stable release, when I upgraded unstable this morning I got hit with this issue, I'd guess a lot of other folks will shortly as well. Could the SNAP_NAME workaround be incorporated into the derivation until there is a fix from Mozilla? If there is a better fix out there then maybe that.\nJust got made aware of the issues as well. I'd sway te SNAP_NAME workaround is okayish for now. I will try to get a patch made so that we do not need that in the future and have a proper kill-switch for that... Sorry for the troubles. I missed that during testing the latest release :'(\nI opened a PR to add the workaround Will do the backport as soon as someone else can confirm that it works as expected.\nLooks like the more general solution has been merged into Firefox and will be deployed with 68+. From The dedicated profiles feature is off when MOZLEGACY_PROFILES is set to 1 at environment level, while the downgrade protection is still enabled. Probably should coordinate a change to that environment variable name with the release of 68, though it looks like the SNAP version would work for a while after as well.\nCan we set in the latest firefox now?\nWe could do that but that wouldn't work with former ESR / tor browser and probably a few other things. In the long run that probably makes sense."}
{"_id":"doc-en-nixpkgs-0c3b557dae16ec2de1278990b64ea7cc5c6941606bd15750759a786171dd9a15","title":"","text":"I am not sure it is worth the extra code to use the newer (equivalent) option for newer versions and the old one for older versions. There are constantly users that want older firefox versions because of plugins, java, … so we shouldn't just remove them?!\nthis hasn't popped up in my daily usage for a while now - please comment/reopen if it's still an issue."}
{"_id":"doc-en-nixpkgs-4b95f4a017015cc8f23f25bdfd93cd48ee7e45f361315acc73f7d86d627d70ee","title":"","text":"I tried to install Roundcube with an non-local PostgreSQL. The DB user password should be stored in a password file. I ran into problems with this setup: the password file is used in two locations: the Roundcube the systemd that initializes the roundcube database Unfortunately the neccessary file content differs for these two services: the roundcube the passwordfile should only contain the PASSWORD (even without a trailing newline) expects an entry like \"hostname:port:database:username:password\" () So one of these two services will fail. Setup Roundcube with remote PostgreSQL server and password file for DB user password. My solution for now would be, to add a line to the roundcube Please run and paste the result. Cheers, Andreas\nYour solution sounds reasonable to me, if you replace with something that takes into account escaped . Would you mind opening a PR? Tag me on it, I'll review it. As you can see the remote db feature of the module has probably never been used except by you; if you want this use case to be better maintained consider contributing a nixos test exercising it.\nFixed by"}
{"_id":"doc-en-nixpkgs-e1779595121343e66c44df1782fdc5c7be2053ed46139b687c7c05db9a28c9f2","title":"","text":"Describe the bug Failed to build . To Reproduce in -rebuild switch Expected behavior Build successful. Screenshots  Additional context Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nNew warnings/error are introduced with new GCC releases.\ncould you please give a try?\nYes, it works."}
{"_id":"doc-en-nixpkgs-bfb06549a6eeb75e1157ddcf9626e4f038deedfd515a40f29bd32b288649fad6","title":"","text":"When typing something here: <img src=\"https://user-\" width=50%The desktop crashes and you have to re-login (well it's Chinese in the screenshot but I hope you get the idea) <img src=\"https://user-\" width=50%Steps to reproduce the behavior: budgie menu something crash No crash. See above. I don't see this issue before the GNOME 44 update. Probably another issue but I haven't go deep yet. I am on right now, it's nixos-unstable with pull request picked.\nBacktrace points to <details</detailsLooks like there are changes on that touches after 10.7.1, I am testing that right now.\nI gave the latest HEAD (i.e. ) a try and cannot reproduce the issue so probably some of the commits fixes the issue. I wonder if this can be reproduce by others and if some fixes can be backported before 23.05\nOhhh goooooood and now I am reading , let me make some noise there Edit:\nAnd now I am on , which has glib 2.74 ( has 2.76). This is going to be weird because with G_SLICE=always-malloc I also cannot reproduce the crash (budgie-desktop 10.7.1), so probably not related to the slice allocator. Edit: and it's vala 0.56.4 on (no crash) and 0.56.6 on (crash)\nOkay I guess I can basically confirm it's caused by vala update because I am now on and cannnot reproduce the crash, wow it's first time I know valac can really cause issues :seenoevil: Bisect is too painful for my slow laptop :upsidedownface:\nCould you try compiling and running this Vala code on the broken version to see if it also crashes? It should do the same thing as the crashing Budgie code, just without crashing your desktop. If this ends up being a Vala issue, we need a minimal reproduction program to send."}
{"_id":"doc-en-nixpkgs-bb02419366d3a3c79f23b329bca087400efbaaa32939f2c207f98178ac20eaec","title":"","text":"Build and run with (assuming you put it in a file called ):\nI am now on and my desktop crashes, so the current range is :upsidedownface: I am away from keyboard for the next few hours because it's midnight here but feel free to drop questions :upsidedownface: I built the program with vala 0.56.5, it exits normally with\nWell, crap. I was hoping that would crash. Maybe this version when you get back? It's closer to the code in Budgie: Of those commits, the only one that really looks suspicious to me is at a glance.\nI am still here (for now) :laughing: but this runs normally for me as well (hmmm can we really guarantee \"if I can trigger the desktop crash, then using same vala same laptop same setup we can trigger a crash with some different program\"?)"}
{"_id":"doc-en-nixpkgs-45757e3f47c1dc5d222d45bb67988db837fb629a78736d1f60d22e715d49b60a","title":"","text":"Even when vulkan is installed and working, opening chromium and going to chrome://gpu shows vulkan is disabled. Also chromium logs the following warning: Warning: Couldn't open Info: Couldn't load Vulkan at LoadVulkan () at Initialize () Running confirms that vulkan is installed properly and working. vulkan is installed and working with running chromium and go to chrome://gpu check if vulkan is enabled or disabled. vulakn is enabled in chrome://gpu Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(robert): channels(root): nixpkgs: Maintainer information:\nHey I think you meant to ping the chromium maintainers:\nyes thank you!\nNot sure if this is actionable, AFAIK Chromium's Vulkan support is still pretty experimental (depending on the platform). Did it even ever work before? Also: X11 or Wayland, which flags are you using for Chromium, and could you provide the full output? might be actionable but apparently it's only a warning so idk... You could use to figure out the complete path where Chromium expects . Relevant parts from the source code: ;l=43;drc= ;l=173;drc=;bpv=0;bpt=1 But since Dawn () is Google's WebGPU implementation this shouldn't even be relevant (yet). Anyway, I'm afraid you're on your own here as I don't have enough time to give it a proper look. (Potentially) also interesting/relevant: ,RAMandSwap,ChromiumWillEatItAll PS: I also finally submitted but that should only be relevant when using SwiftShader.\nThis issue affects also google-chrome.\nseems to be relevant as it's ANGLE's Vulkan wrapper rather than the real libvulkan from the system. I only had a quick look through the source-code but it seems like we should definitely install it (but other Linux distributions don't seem to do it yet). Anyway, could you re-test this once is built by Hydra (maybe I can also give it a go during the weekend)? we already install for Google Chrome so it seems like there are some other issues as well. If you have time to debug/investigate that would be great (my older test system for Google Chrome lacks Vulkan support :o).\ngreat thanks for looking into it!"}
{"_id":"doc-en-nixpkgs-deba79bbb1d0e61f193f3c238646f2e366748a164dfe2a58c974e5f751c55210","title":"","text":"will definitely try to test it over the weekend\nunfortunately it does not seem to fix the problem. I still get the same warning that could not be load\nConfirming this is also an issue on google-chrome-beta: (Excuse the unrelated dbus things) I'm not experienced at debugging this kind of thing but happy to give it a shot if there are any hints for where to get started. :) Edit: I did confirm that exists and paths seem valid.\nIf you have time it would be nice if you or someone else could use strace (or similar tools) to figure out where Chrome/Chromium is looking for . Something like (see - e.g. can be useful as well). It's a bit advanced though. I'm hoping that I can also give it a go soon (currently working on a few other Chromium TODOs).\nBelow is the strace output if it's any help. Pretty sure just the first ~2 lines are relevant. The first line happens when the browser opens, second line onwards happens after opening and the browser prints: (This is with stable, same thing happens with beta too). <details<summary<codestrace-fe file --timestamps google-chrome-stable OCLOEXEC) = 37 : 17:09:44 openat(ATFDCWD, \"/nix/store/abmblk7xs49q0xhgkrp9izhab64jqri6-google-chrome-\", ORDONLYOCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/kxs3h7ffg2s061y9s8m00m5c6nbggg6f-libXScrnSaver-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/lbignzjfjydc4zb1d6qal3sjq7km3pqf-libXcomposite-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/6cy62r6hnzq5yqjj347p6dwv9pw21ixy-libxcb-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD,"}
{"_id":"doc-en-nixpkgs-84b6038cbc89824af143f64f16611b5b940c17c748abd214d672545a552f13b3","title":"","text":"\"/nix/store/1pj4gnng9ibcbd3cy4002lnyjwv2sjv3-alsa-lib-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/l9s8gcnh687p4cpkj0ic4ym180lpy9an-libXdamage-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/shjhw9gp0k78abd8mpd6jlgvbk17k2zv-libXtst-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/nfgwb2xk9jhidd4dh2l5j90kiyq17faa-libXrandr-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/pb2i4d6q7fai3kiqrw9za8svisyrngh5-libxshmfence-\", ORDONLYOCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/6hwhq9szpm65zhcvhfw42gzdlyi7b2rz-gdk-pixbuf-\", ORDONLYOCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/aqwqh3drn9bf6qrs70wiyrxaawh1wcnz-systemd-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/iy5g2611yc6y6jzcmpm55bjbskhcydkm-libexif-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/g7y8adgr5fac89kzfx8ddm66253a3idn-pciutils-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD,"}
{"_id":"doc-en-nixpkgs-605d04ce3854c7295561289394a4d4b8a80f5759b310a41c8ac12e15af805497","title":"","text":"\"/nix/store/19x7vr6vqvqcq1fqpdlk01c2gzb5igdm-curl-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/2jd06jm9lfis3knm615wm3idw86wjr3i-util-linux-2.37.2-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/qlxl487zbn873xqmp7gb3if3g250kdx7-flac-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/019a19l65k3qs88wr6fyznk7dj86a6vg-harfbuzz-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/jvbyjnjh4w8qg7izfq4x5d2wy9lv9461-icu4c-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/f76ccq4s20agzdz3m5fdmrs23r249fzr-libpng-apng-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/ani3r9bxx7il7zn54miylbxdn4lb2si5-libopus-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/ap050qq8w9xnpaijzhh4njhqarilam9c-snappy-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/86dp2ryfg8akpa9r3ylqd3fpdhqhzmxa-speech-dispatcher-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD,"}
{"_id":"doc-en-nixpkgs-2167d68f4895963ff1c13daadc5f8282afefa458353985f0bf78bdeb781bb7b4","title":"","text":"\"/nix/store/ckqhvpa7mg8181pfhd4gb1k834npjm89-bzip2-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/90v7y17p3s4mqlx8hmd75y5acsq3x9pl-libcap-2.49-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/qk4xw57jvy68ca2aikj1gzbpxg9rigi1-at-spi2-atk-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/b8s1yzzi7s1wpy5j5jqhhv5cw2vhdjxh-at-spi2-core-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/mypff9f5vvf41wrjz76dialpsj2k3wq6-libkrb5-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/4xgbyn6sv265gv86rmjgfypmlhh2rvj8-libdrm-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/csxbwm4sr4swzk7qidp0x3lhlsqg6vw6-mesa-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/wwcpra73jl6hgqxl908k1b0810pd6wv4-libxkbcommon-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/njzhva8b2idhdfzaqr09kq4wfdlddxki-pipewire-0.3.40-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD,"}
{"_id":"doc-en-nixpkgs-48c61969925a0922192bef6f9fd7a9fcf922dad78dde804379244d6bd6bb56a4","title":"","text":"\"/nix/store/7h5p0sd7acqvsw4jj4jygncmsq6sdcsq-wayland-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/a1b3p02cm1gsy16jwlgg00x9k3kp182r-libpulseaudio-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/pcs9vp9pcc2vqzvpjddqf7ifv951j323-libva-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/9a417mnzmkz7nbdq3kqpa5520qlggxga-vulkan-loader-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/5fpv8x3f6yzw0aqrslv3q126xx48lbn7-gtk+3-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/pwl7ygmix3skcz8xqz4pcm620vpr8bd5-nss-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/2nkjrh3za68vrw6kf8lxn6nq1dval05v-gcc-10.3.0-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/xnqj2w9szfw5mfwylhlavgxkiv9rslmg-sane-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/ldibnigsg44q3wp6v8ikn8kq08lf675c-glib-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD,"}
{"_id":"doc-en-nixpkgs-eb41cffb4b3de649ae7addb9a47c3d78ddc2a30ca97389fa5d204fb2c5b962b2","title":"","text":"\"/nix/store/bn7b7cidb9qgs8m8y83nf247j8j3xjsf-pango-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/q42c9s1cbyg5inf8ranys485akhaxh3v-cairo-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/w259jz35i221vil0jg2dpdw3zda55ai4-libX11-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/zbrzcprzpcby9107v8xkph2wks3mk93r-atk-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/pwl7ygmix3skcz8xqz4pcm620vpr8bd5-nss-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/5md0fgrd9jir7wdnxla46dfcb15vdsm2-nspr-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/cfv850gaqmzrs60fpxxkv088zcj74hi3-libXext-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/fgdh05bisfqs9llxvsg4c66ag9l78b58-libXfixes-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/lbignzjfjydc4zb1d6qal3sjq7km3pqf-libXcomposite-\", ORDONLYOCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/l9s8gcnh687p4cpkj0ic4ym180lpy9an-libXdamage-\","}
{"_id":"doc-en-nixpkgs-7b921e0ca589a220fa8e8bdfa64bcbe8e7749a7cf6665eaf218b00850626662b","title":"","text":"ORDONLYOCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/cgg7sv3aa40mksfrm44rfifcgprgd25v-expat-\", ORDONLY|OCLOEXEC) = 257 : 17:09:44 openat(ATFDCWD, \"/nix/store/zdmma38hz9jjks3dsm8qsmr006lnl0dp-cups-2.3.3op2-\", ORDONLYO_CLOEXEC <unfinished .</pre</details\nTemporary solution: or or, on flakes,\nBTW, same problem with the . Vulkan backend only worked with the trick above\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nUnfortunately this is still broken for me\nThis is still broken\nOh, seems like part of the issue is Vulkan is not supported on wayland yet\nIt's an upstream issue at this point, due to there being no Vulkan support on Wayland/Ozone:"}
{"_id":"doc-en-nixpkgs-80f7e1779a8b85e11e4b9d6922ba190f654b1ebec7e68ee5b6f553293cdf86b0","title":"","text":"Project description A simple one-file way to run various GGML and GGUF models with KoboldAI's UI. Metadata homepage URL: source URL: license: GNU Affero General Public License v3.0 platforms: darwin, linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nshould be similar to llama-cpp since it is a fork but idk enough about both projects to do it myself\nI'm currently working on this, although for to be packaged will need to be merged."}
{"_id":"doc-en-nixpkgs-cbbc06e0529ebe849bb8d5f696ebfafec37114a26492392982c261ec4483d323","title":"","text":"On or cross-compiled from , breaks: From : You can either run this on another architecture using . or should not crash: This was responsible for failing to replicate datasets to my ARM NAS. The issue does not_ occur for natively compiled builds. It appears to be a cross-compilation issue only.\nIt is a bug in / derivations. In non-cross cases it gets copied from used to bid into output: But in cross-case used to build does not yet provide as it needs bits of for it (and the library path is slightly incorrect). One of possible workarounds is to try to add to to get it pulled via from expected location.\nWe don't do the copying to glibc anymore, but this error still occurs as described on current nixpkgs master.\nYup. cross-compilation never propagated to in any form (and does not today).\nCould you please try this PR? It should fix the problem.\nWith that PR, I'm seeing this on both (a Raspberry Pi CM4) and with QEMU on : Log from aarch64 machine: Log from machine with QEMU:\nWell it's finding now, so there's clearly some other problem with addition to that. When I run it with I even get line numbers from inside : That line () is the last line in the following snippet of code: ... so is deliberately ing here due to . Grepping through the docs turns up: This is happening because uses . Once you do that, glibc needs to unwind the stack frame of any thread that calls . And unwinders are a giant headache. I'm afraid that's all I've got here. I've removed the closed-by from since it was only part of the problem here.\nAh, I think I know what it is. We can compile a without , but it won't have an unwinder. We need to pass the glibc headers to the build in order to get one of those.\nwould you please try ? I believe it fixes one of the two problems which caused this issue, and it includes which fixes the other one. It works for me: BTW, this issue (cross-compile , then run it under qemu) is a really valuable test case. We really ought to add it to so Hydra will catch any regressions automatically."}
{"_id":"doc-en-nixpkgs-4afc5513c2b5a5f91579f59d6c1b040753f5bb1c197835c24a79cc42186c48bf","title":"","text":"Especially since the failure mode gives the user no error message to help them troubleshoot the problem! is a great candidate for this since it's one of those very rare non-C++ programs that uses advanced stack-unwinding features from pthreads.\nConfirming fixes the issue. Tested with both and on real hardware and with QEMU on x86_64.\n~I think this is fixed, and more cleanly,~ by Edit: it is not. :frowning_face: I will keep trying. Test is in Currently building.\nAdded this to , but commented out since it is not fixed yet."}
{"_id":"doc-en-nixpkgs-1332fb6956bd210ca0dd316f8c0963da41f803a1ec1fe9071fbe2ed7e241929d","title":"","text":"JupyterHub seems to be broken. Launch JupyterHub and sign in from the browser."}
{"_id":"doc-en-nixpkgs-44ec56737771711ff1e4ec564c40cd67d438392697e2abe20084a95ec2b0e753","title":"","text":"Project description <!-- Describe the project a little: --Configuration profiles manager and scheduler for restic backup Metadata homepage URL: source URL: license: GPL3 platforms: linux, darwin Previous discussion that could be a starting point:"}
{"_id":"doc-en-nixpkgs-027e695569bab838d2203c78d98a7c56f113b1f3708ad2ca8b52f86a881d666d","title":"","text":"Running the package after installation does not work. It results in an error instead of starting the app. Steps to reproduce the behavior: The application should start up and work. as per Please run and paste the result. Maintainer information:"}
{"_id":"doc-en-nixpkgs-cd09c59631688483949246eb03f08163ad167ada63d20dc0bb54b1668a7605c4","title":"","text":"Please update Goland to a current version. The Current Version is now 2020.1 Thx and Greetz"}
{"_id":"doc-en-nixpkgs-882925499c853093224377a0097d0b606093e515325e385a879032bf85144d60","title":"","text":"Describe the bug building the package fails. To Reproduce Steps to reproduce the behavior: and wait Expected behavior Successfully building python37Packages.pwntools to be used. Notify maintainers Maintainer: Metadata Error\nWill be fixed via\nlol, I didn't see this issue, I started fixing it today because I recently noticed it was broken as well :D"}
{"_id":"doc-en-nixpkgs-df7df621198a3139ae37dfb2d781a2ee0485dba66b3ecccb0b50f9253dae9873","title":"","text":", (nixos-19.09) Scanned versions: nixos-19.09: . May contain false positives.\nThis is now fixed for 1.43 on master and 19.09:\nThanks :heart:"}
{"_id":"doc-en-nixpkgs-04c4d9ffe187b5c55bae48268d029cce6d5f1f39647e419f11645d2a7130b279","title":"","text":"The option is declared as \"list of packages\". To me, it seems too restrictive, since it prevents useful configurations where web applications are copied from some mutable location in the filesystem, like this: . (Note that for tomcat's virtualHosts, the similar configurations are accepted and work fine just fine! I'm going to use them on my server.) Moreover, the current type was possibly chosen without much thought: it was a part of the long commit which mass- type specifications. My proposal is to change the type of from to . Right now, this kind of configuration produces an error: system: host os: multi-user?: sandbox: version: channels(paul): channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-2ab0600659b9531685e40949f1696f97aa1383ba13629dadf3aa65a48b0078e6","title":"","text":"3 is out! I'm not sure what's changed but it's at least 200% more better, and has a plugin for making you toast :stuckouttongue: . The release notes are here: and are as follows: Anyway I imagine someone'll be excited about the new version :grin: so thought I'd share.\nHaha, a proper changelog is here: my bad :innocent:."}
{"_id":"doc-en-nixpkgs-92ca7defefdf3a92b6d995c31381163c38254f11899860df5d5f0eb644777795","title":"","text":"Project description Pantheon Tweaks is a Switchboard plug allowing users to somewhat tweak Pantheon (elementary OS's DE) settings of the more hidden kind, not normally available from Switchboard. As NixOS has Pantheon packaged, it might be of use in Nixpkgs. Metadata homepage URL: source URL: license: platforms: same as Pantheon Depending on Pantheon version currently in Nixpkgs, the predecessor elementary-tweaks, also GPLv3, might be of more use:\nAs I maintain Pantheon in NixOS, I approve of this being packaged in the future, but not , because it's archived and IIRC I denied that .\nThen we should probably do it once Pantheon in NixOS advances to whatever version elementary OS 6 Odin will have - this'll probably happen once elementary OS 6 will get released.\nAh yes, the repo says \"Pantheon Tweaks is currently only supported on elementary OS Odin\" :+1:\nDid some initial work for this (), would you like to try that? Will need Pantheon 6 () and following line in your NixOS configuration file: Update: I will move this out from the pantheon namespace when creating the PR due to reasons below.\nDid some initial work for this great! would you like to try that? of course works great. only the force darkmode did not work in minder program. haven't tested more... ! ! maybe it could be enabled by an option like ? So it's consistent with other options like .\nTested 1.13.1 on both elementary OS (installed via appcenter) and NixOS (btw minder in Nixpkgs seems out-of-date, just opened a PR: ), I guess this should be an issue to minder, as minder is trying to read information from of granite (, ), so it should respect settings from switchboard-plug-pantheon-shell, while what pantheon-tweaks does is (I guess) setting under you gtk config file and I am not sure how handle this. You can check this with: ! I am not sure as this is not an official part of Pantheon. I guess it should be okay to do this.\nI am not sure as this is not an official part of Pantheon."}
{"_id":"doc-en-nixpkgs-627b666afe33f0a943043a49c3d8ce2e1b1c3b4297186dc412180e220df22689","title":"","text":"yes, that is a concern, but we can make that clear in the description do you think it is acceptable to enable a third-party component (e.g. pantheon-tweaks) with an option like if we clarify that it is third-party in the description, which is for example displayed at the or in the documentation?\nI would not recommend packaging this tweaks app. It regularly breaks since it references gsettings that aren't considered API. That's just my personal opinion though I'm not familiar with NixOS options or what that means so I can't really offer an opinion there\nthanks for your opinion! the program exists and people want to use it and we at nixos want to empower users to do what they want, even if the choices could be considered bad, like installing proprietary software. that's why it's considered for advanced users. you are responsible for the choices you make and you can end up with a broken system, but it's easy to roll back to a working state. experimenting is encouraged So i think it's fine for us to offer the package, but we can clarify that \"it's not recommended by elementary because it regularly breaks\". I'm not familiar with NixOS options or what that means so I can't really offer an opinion there i try to explain quickly: on nixos the whole system is configured by one (or multiple) config. file. as a consequence is read-only if you want to use pantheon, you add this line to the config: that sets up pantheon with default settings. there are options to change those default, like to remove default apps you don't need... so the question here is, all current options with in the name relate to official pantheon software, but would relate to third party software, which is not visible from the name. so it might not be 100% clear all the time so my suggestion is to clarify it at least in the description of the option that it is third-party and not recommended the concern is that it could devaluate you branding like the name \"pantheon\"\nah okay yeah. If possible then it would great if that was not namespaced with actual parts of pantheon and instead namespaced the way you would hand extensions or apps if there's no special convention for extensions. Thanks!\ni suggest then"}
{"_id":"doc-en-nixpkgs-9a89aad9ddf445b88fc570bea7543b2d6398d1aeb5c41ff02509e947847d5166","title":"","text":"Commit introduced type specification for (which was absent before), but this specification is wrong. From within release-18.03, import the tomcat module from the master branch, and create a minimal Tomcat configuration that uses : And see it fails: When using the native module from release-18.03, everything works. system: host os: multi-user?: sandbox: version: channels(paul): channels(root): nixpkgs:\nIt's only semi-related, but why on earth is the type of a list of packages, and not just a list of paths or strings?? It severely limits the configuration options for no apparent gain.\nFor the record, was an issue about overly restrictive type of ."}
{"_id":"doc-en-nixpkgs-423010d7b844042868eadffa830300933e9b1edbe93d582be594af2a8336b530","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-437c4ed8db1222ae032b0f7811855e9a10512106285c56c502976f814799f7e2","title":"","text":"use instead of pulling the windows zip from github releases\nI can review if you want to PR this\nupstream has said that they'd rather us use the github mirror that they're going to set up\nthe github mirror has been created\nSorry, I have to delete the github mirror, due to bandwidth limits. Please use\nthe \"SRB22.2\" branch and/or \"SRB2release_2.2.13\" tag\nGetting 500 errors when trying to access\ndoes this work for you?\nThe link works however the download buttons don't. PRs welcome if anyone can get it working, but wait for to be merged first to avoid merge conflicts.\ni have had another look, and have found that it might be better to pull directly from branch\nThanks, was able to get it to work with :+1:"}
{"_id":"doc-en-nixpkgs-b2319ac6480bb914d71409084fcc84b3d14f8f0e247ffcfe4a5038dfbf766408","title":"","text":"Kdenlive build fails because CMake can't find QtConcurrent. Error: It appears to have been broken by some changes made to qtbase but I am not familiar enough with it to know what specifically. Changes between success and first failure: Latest Hydra failure: cc Attempt to install Kdenlive System: NixOS: 17.09pre107928. (Hummingbird) Nix version: nix-env (Nix) 1.11.9 Nixpkgs version: \"17.09pre107928.\" Sandboxing enabled: build-use-sandbox = true\nYou need to modify the to We should send a patch upstream. This must be a required change since QT5.8.\nFixed by:"}
{"_id":"doc-en-nixpkgs-be945e7ae566f497955dd2d1a94cd2404e78598c0ff3a96f22dd8f305c5c1e03","title":"","text":"Setting nixos option to null, which is legal according to typechecks results in an invalid disk size value passed to Launching the script, aka system build attribute , will throw an error at the disk creation stage mentioning an invalid argument for the size parameter. Steps to reproduce the behavior: new flake output attribute with value of basic nixosSystem option attribute ./result Launching ./result will create a qcow disk and launch qemu with the machine configuration. I found this bug through changes in nixos-generators. I've created an issue in their repo first, but their changes might be technically correct. REF; No maintainers list within that nixos module file. Pinging as last change author on the type of virtualisation.disksize. <!-- 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 don't remember why I've set this option to . From the commit that it () it's clear that null is not handled, so it's probably a mistake.\nJust stumbled upon this issue and agree with the analysis here. PR at"}
{"_id":"doc-en-nixpkgs-b82278382e653e1a00e694263b73b1b02b51f6b77e4c905cfe2c128dd18287c7","title":"","text":"Project description Hashlink is a virtual machine used in Haxe/Heaps game projects. This is the same stack that shiro games and motion twin uses to make things like Dead Cells and Northgard. The full steps for installing heaps (which goes through dependencies) can be found , and one of the steps is to download hashlink and put it on the path. Metadata homepage URL: source URL: license: mit platforms: linux, mac, windows\nI am on it, will try to compose a first draft. :-)\nThat was fast! I really appreciate it! I put in a few haxe-related package requests today, I'm so surprised no one else has requested them before! But once they're in we'll be happy! Not really looking to nix-ify my haxe projects yet since I imagine it'll be involved, but getting hashlink on the path in a package is a step in the right direction right? :) Really appreciate this, thank you!\nI'm not really familiar with the Haxe ecosystem, but the Arch build for Hashlink suggested that this packaging task seemed simple enough (no complex build system, just a Makefile, no dependencies on other parts of the Haxe ecosystem) so that I could do it. Glad that I could be of help. :-) Thank you for your issue contributions! While the pull request is not yet merged, you can use hashlink as follows: (Be wary that commands like this can cause the execution of arbitrary code, so in principle one should use these only with trusted repositories.)\nThanks for your hard work!\nhow are things going with the PR? I think someone has asked a question on it, I don't know if that means that it's stalled from going in? Thanks again!\nThere are in fact issues with hashlink on NixOS I think - I think there's some libraries that are build with hashlink that are unhandled - there's an issue for this already as hinted in your PR:"}
{"_id":"doc-en-nixpkgs-8cffe84af642e1e82571f6f3fef9efface847335809d3fa916de214f7319b5b1","title":"","text":"When running OmniSharp, the program is unable to find a dotnet runtime to use at all. When I remove the part from the part of the script, it starts to work. Presumably because moving the command to /dev/null just isn't helping at all? ! !\nOh this is an issue with buildDotnetModule. I was looking at nixos-23.05 when I am on nixos-unstable.\nSo I am not the only one having this issue I talked about this in the PR that introduced the bug (). I have made a proof of concept for a fix: I will open a PR for this, now that I know that I am not the only one experiencing this.\nYour fix worked because, because the original code is checking whether you have dotnet installed by checking whether has an exit code of 0 (which it does, if it is installed). But if you change it to , it will always have exit code that is not 0 (because running is not correct by itself), thus making it think you don't have it installed, which means it will use the hardcoded dotnet 6 version instead.\nYeah, I just stumbled upon it while copy pasting the script manually, I didn't take the time to understand what was happening, still new to shell-scripts. Thanks for hopefully finding a solution!"}
{"_id":"doc-en-nixpkgs-613b3fc03205fddc0cab698fb5b703d54048c7c668c2d8bf97bc8c4e4df96b4b","title":"","text":"efibootmgr is not a dependency, despite being needed Steps to reproduce the behavior: refind refind-install the error message: ! efibootmgr is a dependency of refind I already had refind installed (from another distro) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-da80197d21139924e57021df01721212c8d42f04bae06a3c157a33805f5998bb","title":"","text":"Project description homepage URL: https://xd- source URL: license: mit platforms: linux\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-334a36a4107841ea78362ac9cf1ba5b5f8aa6bb6115f30860cb82b2c9669628e","title":"","text":"shogun fails to build since the eigen 3.4.0 bump: The package is a likely candidate for removal. Upstream is unresponsive and development has halted. Removed from debian: Removed from fedora: Blocking vcpkg update: Please run and paste the result. Maintainer information:\nI think you were the last one to modify this package, so please speak up if you need it. Also pinging Last call - if no one responds within the next week, I'll open a PR to remove this package.\nYes, I was working on making it build on Darwin and adding it as a Python 3 module. Well, I did, but I didn't feel motivated to create a PR. As you comment, upstream has been inactive for almost a year, the latest release is several years old, and it becomes harder and harder to make it work, and the patches would start to accumulate. To make it work on Darwin we need two upstream patches that fix the build with newer compiler versions. In the current derivation, the Python interface is not built because the CMake flag is not the right one. When enabled, Swig 3 is used to generate the Python interface, but Swig 3 doesn't support Python 3.8+ (and with Swig 4 just fails). It can be fixed with a patch, that feels more like a hack, intercepting the Makefile build, so I am not happy with it: Another small patch is needed to fix the deprecated . Also, I wasn't happy that adding it as a Python module will recompile the entire library again, which takes too much time IMO. I haven't checked if it is possible to build with Eigen 3.4 because it takes forever to compile. It could probably work on the development version. Note that the development version doesn't support Eigen 3.4 because of this, but it may work: But there is no such limitation on the 6.1.4 release, which probably means it would require another patch to fix the code, if somebody figures out. So, I'd argue that the package is too old now, and the derivation has too many issues, and it's too much of a hassle to maintain it, so it's probably better to just remove it.\nI decided to sit and take a look at the error, and I actually fixed it."}
{"_id":"doc-en-nixpkgs-67241ca3003f91ee7feebffb5f0b84b1593fd60f4d164186dab305fdffcb4fec","title":"","text":"I don't really use Eigen but the patch makes sense. So, I can send a PR to keep this package on the repo for another cycle at least. I mean, I already did all of the work and it builds. Other distros end up removing it because nobody cares to maintain it.\nNice! Thanks for looking into it. Like you said, if you've already done the work to get it working I don't see why not. If it's too much work to keep it working in the future we can always revisit this and drop it."}
{"_id":"doc-en-nixpkgs-a3ea7ad11a758e0ba3d0f14fc12c014489ea90b26051ed76b35102c63d26fd0c","title":"","text":"In NixOS VM tests, service sometimes fails to start. This breaks e.g. GlusterFS tests. Steps to reproduce the behavior: Building — GlusterFS service fails due to dependency on RPC Bind service. See also Some result related to GlusterFS. Have not yet had time to bisect and determine what's going on.\nHey, I started down this path looking for an updated Glusterfs package, then found the paused PR, which linked here. Fortunately, I think I know the root cause. As you noted, the failure is due to a dependency failure on - the error message in journald is: This was sort of confusing, but I found that led me to . The NixOS config includes: L /var/run - - - - ../run So my suspicion is that starts before and can't check for the lockfile. Since there's no unit, which was my first guess, I've instead been adding and tied to , which makes the tests pass. The diff that makes this work is: Obviously we should probably make this fix in NixOS proper, but I want to double-check with you that such a wider-impact change is safe to make. The proposed global_ fix for NixOS would be: thoughts/feedback? I can PR the fix if this all sounds right.\nThe real problem is that I am competent about neither rpcbind nor systemd-tmpfiles (otherwise I would try to write a more sensible complaint). Maybe PR the change (if it indeed fixes rpcbind judging from logs + fixes GlusterFS tests + doesn't break any NixOS tests that passed right before) and see if more competent people show up? It does feel to me that ideally tmpfiles should not depend on rpcbind and if they do (dunno, because we have /tmp on GlusterFS???) we are doomed anyway…\nYou and I are in the same boat, friend :joy: I'm only rpcbind-aware as it applies to GlusterFS, so I don't count myself as an expert, either. The only reason I feel confident enough to PR a fix is that all the pieces line up here and the passing tests make me think that this does indeed strike at the root cause."}
{"_id":"doc-en-nixpkgs-bfc07550bb5255d09b6bf220afd81c5eb96b184bdc9d403dfff08049307121b8","title":"","text":"If NixOS is shipping with that tmpfiles configuration to bootstrap , then I think it makes sense for the downstream NixOS module to accomodate how NixOS is handling . So my initial instinct of patching upstream probably doesn't apply since distros are probably handling differently. I'll PR the change and we can see about additional feedback for us.\nI'm feeling pretty confident that fixed the rpcbind problem - are there any nixosTests that should be re-enabled now that rpcbind reliably runs? I looked around for disabled tests but am not sure where those might live, if any are still disabled. Otherwise, I think we can close this :crossed_fingers:\n(looked at the tests, doesn't look like there is a ton of disabled ones)"}
{"_id":"doc-en-nixpkgs-500cd872cbcdb9db7d5072ba080ed19a5f2ec42eff855a96c2688ef8b3537cc0","title":"","text":"Describe the bug Epiphany crashes on startup with a bind mount error. To Reproduce Steps to reproduce the behavior: epiphany Expected behavior The browser should startup Additional context Error: exists and opengl is enabled I bet is relevant 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:\nI can't reproduce this on my machine. Can you try running it with ?\nThanks for responding. I think this is the relevant part from :\nAh, this only shows that emits the error message. To trace what it actually does, could you try adding the flag?\nI just piped it all into here:\nThe output got cut off there, unfortunately. Maybe you could just attach the text file directly to your reply?\nSorry about that, here is the file:\nThanks for the log! I think I've found the culprit. I've opened which seems to fix it - please try it out."}
{"_id":"doc-en-nixpkgs-5e1aeaff6a38e8428d47a64fd620867b91805e3ffd34c71f9d06ab387bf5859b","title":"","text":"Package name: tailscale Latest released version: 1.72.0 <!-- Search your package here: --- Current version on the unstable channel: 1.70.0 Current version on the stable/release channel: 1.66.4 <!-- 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-e6a08080112a1be7878951ddaa1736a4ac1997659a9c50d18eb87a31e1c3e4bc","title":"","text":"Grocy does not properly save manuals for equipment The issue appears to be introduced by in a patch applied by nixpkgs. Changing that hunk to: Fixes the issue. I'm not currently setup for making a PR, I'm a bit busy, but I wanted an issue for other people to find if they run into the problem. grocy in nixos configuration (admin/admin is default) a new piece of equipment and attach a PDF manual to it to download manual; it will fail system: host os: multi-user?: sandbox: version: channels(aidenn): channels(root): nixpkgs:\nappears to be the maintainer.\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-b2f1918dceb727772866f929f4444ea5f08c6cf73d970d4306939e7d3eb80749","title":"","text":"Would be a very useful package to have for ML Enthusiasts Project description Machine Learning Catboost Library Metadata CatBoost is a high-performance open source library for gradient boosting on decision trees homepage URL: source URL: license: Apache License 2.0 platforms: Linux installation instructions: Please let me know if I should stop tagging you in random issues and it bothers you (sorry, i'll stop), but I thought this might be of interest to you since you are very involved in tensorflow.\ntaggining maintainers of xgboost and lightgbm. Wondering if you could look into compiling catboost too?\nI use tensorflow at work, which is why I care :). But I'm not a data-scientist\nunderstood, thank you. GPU support for catboost would also be very welcome.\nLooks like they have a non standard install script. But definitely doable. Sadly I don't think I have time in the near future but would be happy to point you in the right direction to get stared with a PR\nboth eyes wide open - i'll try to start this w/e, any pointers very welcome, thank you.\nCurrently failing to build on nix, although the file clearly exists.\n- maybe it's easier if you create a work-in-progress pull request so other people can check? Two things that stand out are: looks like something is being downloaded during the build process. This won't work with sandboxing because there won't be a working network. builds should be isolated, i.e. access to should be rewritten to the local build directory, not (probably hardcoded somewhere in the build scripts). Packaging for nix can be quite fiddly - I think might be a good example for fetching complex dependencies + build script patches.\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-be21f8c2daf32b1778ebf3d9fb46565b8fe9051ae7db6f8d012910dcbe581112","title":"","text":"Clang's wrapper does not set as an include path. Compiling files with since <cxxabi.hrequires is present in the aforementioned path I created the environment using this minimal mkShell expression Adding to\nProposed solution seems reasonable to me. See also started by\nPlease can you also include the nixpkgs commit hash in the repro (sorry if it's there and I missed it).\nOh thank you, that makes so much sense, I was also looking at how the monorepo handles things as well as their tests on finding the system include headers and what you said is probably the correct reason. Ah, it was the nixpkgs-unstable revision updated just then. Sorry I do not have that, but you can reproduce it with the current master as well."}
{"_id":"doc-en-nixpkgs-bc335a9772de89c8efb16157fe30d394629c74d0b71ded95e3f320266397be74","title":"","text":"Package name: tracker-miners Latest released version: 3.7.3 <!-- Search your package here: --- Current version on the unstable channel: 3.7.2 Current version on the stable/release channel: 3.6.2 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Tracker was updated in , however tracker-miners wasn't. It currently suffers from this bug: (and generates a lot of failures on a running gnome system). It was fixed in 3.7.3. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nPRs are welcomed."}
{"_id":"doc-en-nixpkgs-f3d30e1de3defca4e59b2b211bb67e6c2c579ff898a203a4b72eed0246329676","title":"","text":"Which version does it attempt to build? See for explanation.\n9\nHmm, are you sure procps(-ng) can work on darwin? I found just\nThe only reason I wanted it was for the utility, which does work on Darwin. Homebrew has a separate installation target for , so maybe we can do that too.\nI see, I noticed that. I'll leave it open then.\nSince there is now a specific watch expression, this is no longer a bug."}
{"_id":"doc-en-nixpkgs-cd195c44e05f2eb5a1835c89f628a68ace4699ccbce6ea204cafd9fb34c23a2a","title":"","text":"Package name: atuin Latest released version: 18.0.1 Current version on the unstable channel: 18.0.1 Current version on the stable/release channel: 17.0.1 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]:\nIf you are planning to open a PR anyway, you don't need to open an issue.\nCool, thanks. I was unsure of the policy around that"}
{"_id":"doc-en-nixpkgs-1459c488becda9882d001beb1460d82893761fcfd98bc9c64295ba0346e41d93","title":"","text":"Project description httm prints the size, date and corresponding locations of available unique versions (deduplicated by modify time and size) of files residing on ZFS snapshots, but can also be used interactively to view and restore such files. httm might change the way you use ZFS snapshots (because ZFS isn't designed for finding for unique file versions) or the Time Machine concept (because httm is very fast!). Metadata homepage URL: source URL: license: Mozilla Public License 2.0 platforms: unix, linux, darwin\nOh great thanks! Searched first but missed this."}
{"_id":"doc-en-nixpkgs-7c6043df90781722dc85ec59d2fcf9d81dbc5052bf13022e8a9aacb5f31696b7","title":"","text":"Package name: ko Latest released version: 0.15.3 <!-- Search your package here: --- Current version on the unstable channel: 0.15.2 Current version on the stable/release channel: 0.15.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-ae20a6888f51c10698ac9ade71000307e9fdfea5e66d3fe4fd1b949f3912a950","title":"","text":"As noted by scipy uses the wrong tests. Instead of running its own test-suite, it runs that of numpy. This is because accidentally pkgName was set to in\nMost errors are which are harmless according to\nThe 12 errors that are encountered are in fact 11 deprecation warnings, and one syntax error in a test when setting PYTHONPATH."}
{"_id":"doc-en-nixpkgs-af5047b366ca3740e95a504ed9604a2a9ee9f1632188d74d0d2b9f6d7bc5f254","title":"","text":"Describe the bug To contribute to the nixpkgs documentation I followed the instructions in the nixpkgs manual \"Chapter 21. Contributing to this documentation\" and I followed the code snippet Firstly I was greeted with some warnings: But moving on to I saw a large number of errors. It looks like is set up inside the nix-shell but it's not picked up by ? Running the command does work. To Reproduce Expected behavior No warnings, no errors. Metadata Please run and paste the result. Maintainer information:\nnix-shell has a specific setup to allow running stdenv phases such as\nThat also gives me a bunch of errors as well, but different ones: For a bunch of files. I managed to write some updates to the docs and validated them just using the command, but it's a bit unfortunate that just following the instructions literally doesn't work.\nSorry about that. should fix it.\nThanks, that fixes it for me (tested by setting the env variable manually). Great to see these steps towards making it easier to contribute to the docs."}
{"_id":"doc-en-nixpkgs-6b27e99607c9b09248b1e172673e899c8a590a0c0624774177a302b77cb91910","title":"","text":"On my M1 Mac, with homebrew-installed libvirt / qemu-system-aarch64, I'm able to run the VM defined in the config below without issue. However with libvirt / qemu installed via nix, I get: Some possibly related discussion . Looking at the , they're explicitly setting ; adding this seems to resolve the issue: I'm not sure whether disabling those failing tests is a reasonable thing to do. Steps to reproduce the behavior: to in A clear and concise description of what you expected to happen. Should run without , like it does with homebrew. Please run and paste the result.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nFWIW, I also encountered this issue, and have to use the following workaround: And -ing the efi firmware & vars manually. Fixing this bug can lead to great user experience: virt-manager can work out of box.\nWhere did you get ?"}
{"_id":"doc-en-nixpkgs-468c859d5a9704e239027a9ede6c33c20edb19490972e69a9654598a26f47be5","title":"","text":"Package name: river Latest released version: 0.3.3 <!-- Search your package here: --- Current version on the unstable channel: 0.3.2 Current version on the stable/release channel: 0.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]:\n3 is only a zig 0.13 compatibility release. It’s blocked by\nhas been merged, this is not blocked anymore."}
{"_id":"doc-en-nixpkgs-087bb5bb2c54a2ad330beb990fdb8a9e240d0e958e409b797ca051e469da2f60","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: lapce <!-- 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.0.10 desired version: 0.0.12 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Maybe it will fix the crash:\ncan you create a pull request?\nI am using changes in local build. it is working fine"}
{"_id":"doc-en-nixpkgs-92ab09d59079e845321cb7574a0aac614d211c81cd6293b42840735546c1cb0a","title":"","text":"DBeaver has support to show spatial data on a map when the database is capable (e.g. postgres + postgis) but opening \"spatial\" tab gives this error: Steps to reproduce the behavior: dbeaver to a table that has a geometry, show data \"Spatial\" on the left A map should be shown This happens on master and 21.05-release, didn't test on 21.11 but I suppose it's the same Maintainer information:\nI was able to reproduce the error and have fixed it. This is how the map now looks with a sample polygon taken from !\nWow that was quick! Thank you a lot!"}
{"_id":"doc-en-nixpkgs-5f3175c5808a0bc8f5175146b715eab1b59f9f0f218f93611d732dc0ec80914f","title":"","text":"Describe the bug When adding a local directory to spotify client, it always fails due to missing gtk schema(s) To Reproduce Steps to reproduce the behavior: on button Expected behavior Open a file chooser to select which directory to be . Screenshots If applicable, add screenshots to help explain your problem. Additional context Running spotify with flag from console gives me 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:\nI think that this issue is not NixOS specific:\nStill seems to be an issue. I'm using flakes so above is not applicable I'm on.\nTail end of strace.\nYep I can confirm that. However, as IvanMalison commented above, the bug might be not by nixos but by upstream.\nI'm getting the same issue as OP when clicking the button I also tried this on EndeavourOS with the same version of spotify and there it works flawlessly. So I think this is actually a nixpkgs problem and not something upstream related. Maybe the issue can be reopened?"}
{"_id":"doc-en-nixpkgs-09fbabe278b84afb0b08d2ad7d879e497766c6f0a9d08e8416d349320bdbfcb8","title":"","text":"Using Shogun as a for another CMake-based project fails because the dependent project cannot properly find the shogun library (via its installed cmake files). Steps to reproduce the behavior: to build a derivation based on shogun files are wrong Everything builds correctly I am trying to build the following derivation However I get an error at the build generation step: This indicates that shogun CMake files are not in the right place and/or are pointing towards the wrong paths.\nI fixed the issue with shogun. When installing the configuration files, CMake calculates the prefix to the installed library based on the output directory, instead of the default , and I missed it when I split the derivation into multiple outputs. I wonder why it's not a more widespread issue, only a few derivations patch it. But that derivation still doesn't build: This is in macOS, though. Maybe it works on Linux.\nThanks, is the fix committed yet? The other error is unrelated and I can fix it.\nI'm working on the PR."}
{"_id":"doc-en-nixpkgs-ddef63bab25eb34c5c3caabf9db8e167d88456ac316ae035023c3afeea97cdff","title":"","text":"Since is provided by the non-free on aarch64, I'm not able to install asciidoc-full or any software that requires it to create e.g. the man pages. Can we make an option different from ? /cc\nMaking new granular options is fine, but I think enableStandardFeatures should still include java. (Or else the option is dishonest.) Alternatively, can we switch to openjdk (assuming that works on aarch64)?\nIt was just recently changed to in I'm fine with granular options, even though it will be quite some work to make packages not use anymore.\nOh, so this problem is due to licensing, not wanting to use non-free software? I didn't pick up on that earlier. How about adding a disableJava option, that has priority over enableStandardFeatures? Hm, this feels like a local solution to a global problem.\nis a good idea! What do you think should be the default?\nIf enableStandardFeatures is true, you should get java. Setting disableJava then enables standard features except those requiring java. I'm not sure if doing this (per package) is a good idea though. Isn't this the start of a new whack-a-mole game?\nYes, it's certainly not a perfect solution, but I can then use an overlay which sets for . Alternatively, we could enable Java for x86 only by default.\nPerhaps it would be less confusing to have so the additive condition is positive."}
{"_id":"doc-en-nixpkgs-e03cf0f35b7bd7b9b46fbbc2abe5d1751f771d9ae9c3e7c668bbc979304cf377","title":"","text":"Discord's package has a script which disables breaking updates, by looking and modifying the file. This script breaks if said exists but is empty (fails to load the JSON object) For some reason all values in this file cleared to me and I encountered this issue. (tested on NixOS 22.11 but the script hasn't changed in master) Steps to reproduce the behavior: discord discord should not launch at all (silently, unless launched from a terminal) should handle the exception which arises from this issue. N/A Some logs of when this happens: <!-- 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.\nHmm, interesting that Discord doesn't launch at all. This is a pretty simple fix though, Or something like that (Now that I think about it, if the doesn't exist yet, the script could create it)\nTangentally related: I installed discord on a new machine, and the disable breaking updates script didn't appear to have any effect until I created an empty containing just . There were other files in , but not . Creating that would be nice. Also, the only real indication that it was missing is that when I ran from a terminal, the first line of the output was . This is quite easy to miss because it's at the top of the output, so maybe it would be good to show these errors in a dialog or something similar.\nI'm surprised this is even in tree - I don't think we should be changing program behavior - especially when you're calling it . I doubt the majority of the users even knew this was happening outside of those involved in PRs for nixpkgs. This is a matter of convenience like stated in the script that has a trade off causing a degradation in the security of the application - causing users to not update - relying on maintainers to do it. Please create a separate package for this at the same time when fixing this - call it whatever - just not . Or enclose it in an arg that is disabled by default.\nI hit this same issue and adding an with contents got it running for me as well.\nThanks for opening an issue and describing the fix. This broke for me too and it took me a while to figure out why ...\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-c81045feae140d7dd3cf792d8795333d46d868d48127f57d5bf5000d45e42afc","title":"","text":"Package name: sunvox Latest released version: v2.1.1c Notify maintainers\nThe current version in nixpkgs is not available so building fails. The hash of the new version is"}
{"_id":"doc-en-nixpkgs-452bd78a4899c34fffc31492009f74883d0e646e5308bc808f1bc0d1777987f3","title":"","text":"Project description forwards dns over https queries to normal dns servers and vice versa. Metadata homepage URL: source URL: license: apache 2.0 platforms: unix, linux, darwin, ... ubuntu package url:\nUpstream has system services. Is there a need to include these modules (services) within this package? I would prefer not to include them if there is no need, because is not actively developed and has not released a single stable version yet.\nI personally don't need them, because I prefer creating systemd services via nix configuration anyways."}
{"_id":"doc-en-nixpkgs-6ba11de2f7cd11d817090978976c2d0529e89e89c3bf463054fb5eff7e1b36f9","title":"","text":"Project description Catamaran sans is a font for tamil language Metadata homepage URL: source URL: license: OFL platforms: ? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-f4e27869b7c2604ea60e26961efcb371b6497837977c9aadd6f0d42eb2312b13","title":"","text":"Project description A window switcher, application launcher and dmenu replacement (Wayland fork) Metadata homepage URL: license: mit platforms: linux"}
{"_id":"doc-en-nixpkgs-640d9ae1365e0df306ee0ebb54337191b252e0bc185c2afc9c785d6588b2e05a","title":"","text":"Blender 2.93.5 Hallo When I start Blender now and set under “Render Properties” → “Cycles” Blender crashes completely. Also when I go to “Edit” → “Preferences” → “System” Blender crashes immediately with this Error: What does that tell me now? My GPU configuration in the clinfo: nix run -c nix-info -m:\nI think this might be the same issue as described in"}
{"_id":"doc-en-nixpkgs-bbc65f5e8a1677698dabeecb53179682a0217eb44ad7d14c46fbc6efb5596436","title":"","text":"Describe the bug Blender segfaults when an OpenCL render is attempted. To Reproduce Steps to reproduce the behavior: Properties (right panel) Select Cycles, change device to GPU Compute Expected behavior It should render. Additional context May be related to and 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: Blender gdb backtrace: I'm using a Radeon VII with: gives me:\ncc\nThis seems like an upstream issue. The question is which upstream? Does the crash also occur with e.g. the Intel OpenCL runtime?\nFWIW, I also see the segfault on an rx580 following the repro instructions. It does like others have Blender working with ROCm OpenCL, so the crash may well be due to our packaging. did such a nice job cleaning up our LLVM derivations that there's much less room for funny business now than with previous releases. I see that we have a option we could give LLVM which might reveal a bit more information?\nI can also reproduce the problem on a RX580. Here somebody has the same issue, with a plausible explanation: The conclusion there is that it occurs when two different LLVM versions are used in a process. Which would be the case here, since Blender uses OpenGL. Currently our Mesa is still on LLVM 9, whereas ROCm uses LLVM 11.\nYep, this is probably the issue. If I compile the derivation with a built against , I don't get the segfault. I am not sure yet what the solution is, since we cannot always update the LLVM version that Mesa uses to that of ROCm. I wonder how this is dealt with with ROCm on other distributions. Do they override the system Mesa?\nI guess I should have turned up that link first given my prior involvement! Could we substitute a at runtime instead? Perhaps via ICD, or , or even ?\nThere is , which we could use to override system package. I guess if it works, we could add a module along the lines of the support, which would use as the OpenGL package and could even add the ICD definition to ."}
{"_id":"doc-en-nixpkgs-ae2e0896f48a2fbeb092be2e71670eaed9218aa0359a6cf578a147c0065c8a66","title":"","text":"But we should probably first test how well building mesa against the LLVM fork works. At least it builds ;). I might have some time to look at this after work.\nIf you have a chance, could you elaborate on how you did this in nixos?: I understand that it's not the permanent fix, but I'm quite curious to try it.\nI modified nixpkgs in-place, but you could do something like: And then: A more proper solution would be to switch to a -built Mesa for . I do have a branch for this: or the two commits: But I ran into another issue in Blender, and I didn't have time to investigate. The system (including GNOME, etc.) worked fine with Mesa built with llvmPackages_rocm.\nSorry. I misremember. I may have rebuilt my system with Which should be equivalent to having an overlay But I am a bit nervous about switching Mesa to a vendor-forked (IIRC prerelease) of LLVM. We should just document this incompatibility for 20.09 and then perhaps land something like the proposed branch/module in master/21.03. But that definitely requires more testing.\ni tried your amdgpu-rocm thing but now blender crashes with this error when opening user preferences: is this the error you mentioned you didn't have time to debug?\nThat's the one. I am afraid though that I can't help with any further debugging. I had to replace the RX580 in the machine I was testing on by an NVIDIA card, because there were too many issues with training machine learning models on the RX580 :confused: .\nthis seems very similar to and replies there would seem to indicate that it's still some LLVM incompatibility, but i'm not sure what is incompatible here... is it blender itself?\nI think the core problem is that both OpenGL and OpenCL (through winding paths) each load their own instances of LLVM into the process, and those instances of LLVM somehow end up sharing some global data, with usually disastrous results.\nIt seems that upstream now explicitly states that ROCm is only for headless deployments: Given the risks of compiling Mesa against a vendor fork (we get to fix any bugs), I think that we should just document this in the AMD -OpenCL section of the manual and leave it at that. Do you agree ?"}
{"_id":"doc-en-nixpkgs-5c687af355a4280e4f07e318ef22b31f04e0708c302fe68d873cc6134e19bb50","title":"","text":"Given this and the lack of RDNA support, I guess the future of OpenCL for GUI apps is with Mesa's Clover.\nI do agree, yes. An AMD employee has been trying to walk things back, but who knows. It doesn’t make sense that they just switched their consumer driver to use ROCm for OpenCL if they don’t have a vision of getting in sync with Mesa, but that’s clearly their row to hoe.\nI'm amazed AMD has any foot left to shoot at.\nI marked this as stale due to inactivity. &rarr;\nStill important, though only in general (OpenCL in GUI apps with AMD GPUs), because .\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nI think I finally figured out a workaround! Disabling for seems to work. I did it with the following patch to nixpkgs, but it should be possible to do it with an overlay too: After a lot of building, Blender seems happy again :) !\nIf this works, it is incredible. How would I do it as an overlay?\nI think this should do it. It's ugly and there might be a better way but it should at least make it easy to test if it works for you. I'm still trying to figure out if there's a simpler fix (for example, overriding just ), but haven't been able to figure it out yet.\nIt works for me. I suggest you make a PR with this change to Nixpkgs. It may seem a bit ad-hoc, but otherwise it is not possible for a process to have both OpenGL and ROCm OpenCL loaded simultaneously, which seems like a pretty common use case.\nNow that I know it works for other people I'll try to make a PR in the next day or two, yeah :)"}
{"_id":"doc-en-nixpkgs-721c475cefbb369338f7ad9c89fddcf09bbf5b61ba58aef295f7329dc939fdd6","title":"","text":"Steps to reproduce the behavior: kicad (tested on ) The relevant part of the build log is: Complete build log is here: Setting the flag in the cmake build flags, solves the issue. Please run and paste the result.\nthanks for filing an issue i'm not sure what changed to cause this issue, or why that change didn't notify me of the breakage... i'll try to get your fix or something similar in a PR today"}
{"_id":"doc-en-nixpkgs-4d372444ab3aae580e594b06e5842db1a0668710ae2051008273b0944298ea87","title":"","text":"Steps to reproduce the behavior: working program Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-717e4b429f050e103d51e7d159e7272daefe8d81080a16b79d806c206f2dd855","title":"","text":"On NixOS 22.05, getting financial quotes in gnucash no longer works because the helper scripts are now binary wrappers, but gnucash calls so this fails. Commit suggests that should avoid this, but for some reason the scripts still get wrapped with binaries. NixOS 22.05..\nI can reproduce this on my machine from nixpkgs/master, so it's not a 22.05 problem. Interestingly, when I backport GnuCash's derivation from nixpkgs/master back to a known-good commit (), things appear ok. I'll continue digging.\n... I see you yourself as a maintainer. Any interest in taking a stab at this? Per I think we're being broken by a change somewhere related to .\n... I see you yourself as a maintainer. Any interest in taking a stab at this? still getting my head together after a bad bout of covid, not sure I'll be able to work on anything serious any time soon\nI worked around this on my nixos config by adding a patch () to execute the helpers directly without calling out to perl. It seems to work for me. Will this break anything? If desired, I can submit a PR with this patch. Also, the perl helpers seem to be getting wrapped explicitly () is this not the reason the perl helpers are getting wrapped with binary executables?"}
{"_id":"doc-en-nixpkgs-36d549183ed1f32b0ce0569cedf0472507b0632a8eb4a5b7ae11ca857dc75d21","title":"","text":"Package name: fragments Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 2.0.2 Current version on the stable/release channel: 2.0.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."}
{"_id":"doc-en-nixpkgs-79de6ed1ad75532d11612c7af90a4e33cff89ea4e3c593cb330d38f4a80145f4","title":"","text":"should provide a QT client to freeciv, which is probably named if I had to guess. Steps to reproduce the behavior: only gtk client installed (see below) A executable. If applicable, add screenshots to help explain your problem. ! -( does not exist) ! The installed is indeed a gtk client. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (You were the last person to commit, so I choose you :) ) (I don't believe the listed maintainer exists). Please run and paste the result. Maintainer information:"}
{"_id":"doc-en-nixpkgs-9234fa52b98a74998dc05d4256cd45d05133c5a1cac8ccdb5eebc3d30cd92cf6","title":"","text":"Steps to reproduce the behavior: cutter 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]:\nAny news on this?"}
{"_id":"doc-en-nixpkgs-a2fa9d3880f3b8bfaa2c0941f7a79ae1d15fca240d518e19d64767e23912e5f9","title":"","text":"It's not possible to lock screen in xfce unless \"xlockmore\" is installed. in in XFCE and try to lock without success and then retry to lock System: NixOS Emu Nix version: 1.11.2 Nixpkgs version: \"16.03.973.\"\nI think that's because there is no blessed lock screen for XFCE. tries XScreenSaver, GNOME Screensaver, XLock and SLock -- in that order.\nHas a situation like this (multiple optional but at least one required dependency on an executable) already been handled in NixOS?\nI think this is generally resolved by some kind of switch, but we have to add one. Something like of ...\nI kept as-is: see\nI think the issue may be resolved. At least with (as of 2023-09-17) lock screen is possible without having installed."}
{"_id":"doc-en-nixpkgs-b5b52486d38eb54c1eb9cc0a710275830a3cf86ba58c0f75a327d7f329611c90","title":"","text":"Project description linux-wallpaperengine aims to reproduce the background functionality of Wallpaper Engine on Linux systems. There already is a wallpaper-engine implementation packaged, but it only works on KDE, while this project should work with most Wayland-compositors and window-managers. Metadata homepage URL: source URL: license: gpl3 platforms: linux I tried to package it myself, but the \"just compare with other packages\" approach of the nixpkgs documentation was very confusing to me. If someone can point me to other documentation or anything helpful I'd be happy to try it again.\nSort of, it still runs under X fyi My rough process: check the repo of whatever you're packaging to see what language and tooling it uses read the nixpkgs manual for the language and tooling that you're building with find examples of other expressions in nixpkgs that use the same tooling to get an idea of the structure use something like to generate the boilerplate for the expression , get an error, use to find the required dependency (repeat this step until there are no more build errors) submit PR"}
{"_id":"doc-en-nixpkgs-f67c2a0ae5c8aba7b34d4875cbc84c1a80c2ad0725b8c60cf633fd5a5191c863","title":"","text":"Steps to reproduce the behavior: to NixOS config Successfully start. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8571a793b3fffc56298e670d9ef77049a92fcd3de22793fb38116ce6e4e01aa1","title":"","text":"Project description <!-- Describe the project a little: --Syntax Tree Surfer is a plugin for Neovim that helps you surf through your document and move elements around using the nvim-treesitter API. 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-9e61d2fa00938940458c36c7bf1b9406d073ffce222f7b922825d1c38190e0d8","title":"","text":"Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important].\nPR:"}
{"_id":"doc-en-nixpkgs-d808ce6c3d971d7469e147716cf4b866f551673e1ffb930a8682757af365d4a0","title":"","text":"I've hit the same bug as described in The root of the problem seems to be missing configuration file which should be placed somewhere and made accessible by . It is used by, for example, in Emacs. cc\ncc\nI'm just getting this warning: Otherwise the output seems normal to me, but I've never really used the utility.\nOh, I see, is still a problem, as it used to be in Debian.\nActually, that config file is provided by package, so if I include it in , it works fine even with . Still, it's a bit confusing that the core provides binary but doesn't fully support it.\nI currently can't see a simple way how to improve that.\nI am not able to use on because it does not accept the option . In the command line I get: Is it related to this issue, or should I report a new issue?\ncc When explicitly adding to there are checksum errors. The following patch fixes it for me: With that, does not give the error anymore.\nOh, no, they're updating files in-place on the only mirror. Many of them won't download anymore :angry:\nBetter discuss the mirroring stuff at this thread:\ntriage: this might have been fixed in the meantime, is that so?\nit's still necessary to explicitly add the package, otherwise the problem persists.\nCould anyone, please, provide steps to reproduce?\nThe \"chktex -v\" works for me, I have installed with .\nworks in but not .\nThis issue still persists as of today under the tetex scheme. the addition of the chktex package is mandatory to not get this error. I was getting this error in emacs: chktex: WARNING -- Could not find global resource file. chktex: ERROR -- Illegal verbosity level. I didn't thought that this was a NixOS related issue so this thread was quite hard to stumble upon.\nI can't reproduce:\nI guess I forgot . If I include that then it just gives \"chktex: command not found\". So how do I trigger the issue?"}
{"_id":"doc-en-nixpkgs-7ade68d8c2fd64aec2802727697e92e626054336ef52b948c770e432424df472","title":"","text":"fails to build. Looking at hydra when it started to fail () it could be due to GCC 11 update. Just adding to the only leads to the next error. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --"}
{"_id":"doc-en-nixpkgs-d5e9156f156bd91ebc6fcfdb185e53da8f1901af07ed0d3d0afcb82c94fd6f7a","title":"","text":"Steps to reproduce the behavior: try to install/build the package using nix-shell or nixos the Domain is no longer configured. Teamspeak Download Pages redirects to this place: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nYou might want to check out\nNot merged yet\nAs a workaround, until this is fixed in nixpkgs: The file is still available at the Internet Archive. You can fetch it from there and write it into the store, with something like this:"}
{"_id":"doc-en-nixpkgs-043737207f88022ae6be87885e40e80a3ae6e911a597b1946a45fc3126a51235","title":"","text":"Describe the bug The stable channel was last updated 5 days before. The blocking issue seems to be the build of nlohmannjson timing out. To Reproduce Steps to reproduce the behavior: to local nixpkgs repo: latest changes: stable channel: : That works, so there is no actual issue with the build. The problem is that a test times out on the CI: Maintainer information:"}
{"_id":"doc-en-nixpkgs-ff33a7066ab5154cdc011de51b7e9a70720069daa4581a1588ebf73385602e2b","title":"","text":"After commit, just enabling does not work because node-red package is under Steps to reproduce the behavior: enable Pull package correctly ! I think the package option should be something like this instead of easy fix I guess I don't know where is found for nixos modules <!-- 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-899ee81454025c402599829408bafbb7142d9f64e0a280e699a043e50176439c","title":"","text":"Describe the bug When i open the About dialog in any program provided by gnunet-gtk, for example , i notice that the logo is missing. ! To Reproduce Steps to reproduce the behavior: (wait for ) Help -About Expected behavior no icons missing Notify maintainers (who fixed the build last) Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nPR:"}
{"_id":"doc-en-nixpkgs-ac275771c026a79347a997b8fe86310934c9e693bfdfaae8c8658da2526df274","title":"","text":"on Hydra: cc\nSince it's been building for me, checked if I was sitting on any changes and while the commit message doesn't indicate that it fixes anything (eep), it does seem to fix this issue: Don't remember enough details to justify it fully offhand (again d'oh for not writing it down at the time hehe) but hopefully this helps work towards a suitable resolution :).\nNaturally this breaks in as well.\nYep, broken for me too. Haven't had time to tinker yet.\nI have the same problem, but the commit mentioned fixes it for me.\nSo are we just waiting for this commit to be in the unstable channels?"}
{"_id":"doc-en-nixpkgs-071917ab067034474b553d929ea64080a4e6fad1d741bab5fb8a01e8aeaaad5e","title":"","text":"A Go program compiled using nix-shell returns an error when running on a separate server and trying to load a timezone file. file with: $nix-shell $<inside shellgo build $exit $ ./app # name of the app you just created 2019/01/25 20:04:58 All went well: America/NewYork Now copy this file to another computer #./app 2019/01/26 01:01:34 could not load new york locationopen /nix/store/0596k27r6pacyx4jp1bcn8zqyjhji52l-go- no such file or directory The error includes the zip name due to internal reasons the Go team has, but the real problem is that nix replaced with I would be more than happy to send a Pull Request if you agree with the proposed solution of prepending instead of replacing. $ nix-shell -p nix-info --run \"nix-info -m\" these paths will be fetched (0.00 MiB download, 0.00 MiB unpacked): /nix/store/dzvh4f6ihkwg44mmf2awxg564k1s8khg-nix-info copying path '/nix/store/dzvh4f6ihkwg44mmf2awxg564k1s8khg-nix-info' from ''... system: host os: multi-user?: sandbox: version: channels(diego): nixpkgs: version is nixos-unstable-2019-01-22 The file replaces the path that the go runtime looks for the timezone information. Original Go code is: But nix changes the first entry, for This works fine if you end up running your go application in the same nix env you compiled it, but when you deploy your go program to a separate server, the path, that can look like isn't present on the separate server and then the lookup fails. is a very common path in Linux distributions. A better way to solve this would be to prepend the nix only path, as the first entry, and then keep and the other entries as they are in the original go source code. The benefits are that those who compile and run in the same nix environment will use the nix path, but those who deploy somewhere else won't have to do any extra work."}
{"_id":"doc-en-nixpkgs-24db2fc9b222118405c5c849a8c3c9d41ddde5eaf269ad5508376780d745726c","title":"","text":"I doubt anyone ever considered support for non-Nix and therefore I will mark it also as . I'll leave it open for now as maybe it can be supported (I doubt it).\nwould you accept a PR with my proposed solution? It won't hurt nix deployments but will help a use case of building a go program in nix but deploying outside of nix.\ncross referencing a thread on the mailing list about this ticket/issue so both conversations are linked.\nYour explanation and proposed solution seem to be very reasonable to me. I suggest that you submit a PR."}
{"_id":"doc-en-nixpkgs-afcc842adac95055cdc1d30b859b6800274d24178bd79b8a275c2939f8361a41","title":"","text":"Project description An end-to-end encrypted, peer-to-peer file storage, sharing and communication network. It's written in Java and uses IPFS. A bit similar to Nextcloud. Metadata homepage URL: source URL: license: AGPL3 platforms: linux (JVM)\nRelated:\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 .\nStill important\nI marked this as stale due to inactivity. &rarr;\nStill important\nI marked this as stale due to inactivity. &rarr;\nI've a working package of peergos. after some testing i've experienced it a little buggy, so i don't want to push it into release. Let's see what i can do as it's my first package. The example bug: after i've created task, clicking \"tasks\" from left menu forces me to create new task. However thecreated task is visible in my drive.\nThanks!"}
{"_id":"doc-en-nixpkgs-9ba3497a6debd3dfe6a7b16c7431537e982760d7288a113bdca21275317454fd","title":"","text":"Virtualbox corrupts guest filesystems by randomly flipping bits when the guest writes data to the virtual hard disks. virtualbox on the host with a new virtual machine for linux 2.6/3.x/4.x with default settings (1GiB RAM, 8GiB harddisk). \"Insert\" a linux live medium into the virtual CD drive. The virtual hard disk should be placed on a filesystem on a physical hard disk (the bug cannot be triggered if the virtual hard disk is placed on a tmpfs, see below). the machine and open a root shell after booting. these commands inside the guest's root shell to write random data onto the hard disk, then read it back and compare it: Caution: This will overwrite anything on the guest's virtual hard disk The shown hashes should match, but in 90% of test runs, they won't. This bug makes virtualbox quite unreliable: It is still possible to install NixOS inside a virtualbox, but during installation, Nix will report a couple of checksum failures, and sometimes the installation is to be tried more then once. After that, random failures of random programs occur. If btrfs is used, this will also complain about checksum errors. After observing this on my production machine with NixOS 22.05, I tried narrowing down the offending commit. To this end, I adapted the nixpkgs minimal live cd build recipe to build an image with virtualbox installed on it, and built this agains different nixpkgs versions. So most of my tests have been performed on a test machine booted from a usb flash drive. The offending commit seems to be . I guess that commit brings in some kernel patch, which is incompatible with the way virtualbox handles disk images. The bug occurs when the host's filesystem containing the disk image is or . In both cases, I tried with freshly created filesystems. The bug does not occur if the disk image is on (or it occurs with very low probablity). I haven't tried any other filesystems on the host. Just to be sure there isn't a general problem with virtualization: I failed to reproduce the bug with qemu and a qcow2 disk image. So it seems to be a virtualbox-only problem."}
{"_id":"doc-en-nixpkgs-44f02c082d4c97fe82511b48ef3bc28cbe53fdec8b066cd4188f3da4386c5d6c","title":"","text":"I observed the bug on three different machines (two desktop machines with NixOS 22.05 and NixOS 21.11, and one laptop with NixOS 21.11). I was also able to reproduce the bug with a linux live cd inside the guest. So the bug can probably be triggered by any linux in the guest. I haven't, however, tried with anything else (e.g. Windows). I was also able to reproduce the bug with a live iso based on (currently ), i.e., with virtualbox 6.1.30 (as opposed to virtualbox 6.1.34 from , currently ). By default, the virtual disk controller has it's checkmark \"Use Host I/O cache\" turned off in the vm config dialog. Turning it on doesn't help (). I cannot reproduce the bug with these linux kernel versions (all checked with current ) (4.19.247) (5.4.198) (5.18.4) So users of these kernel branches are safe ... until the breaking kernel patch also reaches these branches. <details<summaryFor the record: This is the build recipe I'm using for the live iso</summary<p</p</detailsMaybe I can try to bisect inside the kernel sources, but the compile-reboot-test cycle is quite slow on my machine. Strangely, I cannot find any reports about similar behaviour. The closest report might be . It would be interesting for me if this bug can be reproduced/verified by someone else. I'm not sure if this should be considered a kernel bug (the kernel should probably not change the way disk writes are handled), or a virtualbox bug (at the moment I don't know of any other software affected). kernel maintainer team: virtualbox maintainer: (by the way: I'm surprised there's only one maintainer for virtualbox. Thanks for your good work, ; I'm a heavy user!) This is my production system, which also shows that bug. But I did most of the tests to reproduce the bug and narrow down the cause with live iso images based on current ().\nI bisected the linux kernel tree to find as the cause for the guest data corruption. Googling the commit's hash leads to this issue in the VirtualBox bug tracker."}
{"_id":"doc-en-nixpkgs-23a1c6db570f50092f920d401c22186c0fdfc83fd8cc6736ff9a1c98f8fa9997","title":"","text":"According to the information therein, the bug only occurs on some CPU models. The issue there also contains two patches: from This one fixes the problem on linux 5.18. It got already included in nixpkgs' master branch with . It is on it's way to being backported to NixOS 22.05 with . Note that this patch contains several clauses and does not fix the problem on earlier LTS kernel versions. from This one fixes the problem on linux 5.18+, but also on LTS kernel versions. I tested the following combinations with (currently on , where VirtualBox 6.1.34 with and linux 5.15.51 are used by default): VirtualBox version & patch 5.18.8 -----------------------------:------: 6.1.34 + OK 6.1.34 + OK I also tested the following combinations with (currently on , where VirtualBox 6.1.30 and linux 5.15.49 are used by default): VirtualBox version & patch 5.18.6 -----------------------------:------------: 6.1.30 won't build 6.1.34 + OK 6.1.34 + OK To replace VirtualBox 6.1.30 with 6.1.34, I cherry-picked . All tests have been performed on an Intel Core i5-4460 as host, by repeatedly writing/reading 4GiB of random data onto/from a virtual hard disk. Based on these tests, I suggest to use VirtualBox 6.1.34 with the in NixOS 22.05 and in NixOS unstable, as currently, both channels will exhibit the bug in their default configurations (i.e., with kernel 5.15). I will submit a pull request for master shortly."}
{"_id":"doc-en-nixpkgs-985393dd2fb7756f7b7e459e43009685aec394e4fe5de7e39321e5eba7add8c9","title":"","text":"qimgv fails to build when . Steps to reproduce the behavior: No build errors. N/A. N/A. Maintainer information:\nI am working on a patch to OpenCV to fix this issue correctly. In the meantime, you can replace with and it will build and operate properly. On my system I also had to add to to stop it crashing when I tried to open a file dialog but maybe that is just because I run Nix on Ubuntu instead of NixOS."}
{"_id":"doc-en-nixpkgs-388f9dd6ec884b5ef5b8901d3d812edf444f4455bd6fb42f860fb564548205cb","title":"","text":"Cannot view any content when running the program because it complains about missing binaries. Steps to reproduce the behavior: to watch any stream No errors, stream works system: host os: multi-user?: sandbox: version: channels(admin): nixpkgs: Add and as runtime dependencies because the following works for me:"}
{"_id":"doc-en-nixpkgs-5519824d217095c326cd9d69b66af1a8f5bd81902722a6e82a1a9c38fc5255e3","title":"","text":"There are a few more flags we should enable on : - (I had to add these flags for the sake of something that depends on secp256k1 - I don't remember for sure, but I think it's bitcoinj.)\nThe schnorr flag appears to be gone in the latest version."}
{"_id":"doc-en-nixpkgs-ab07be9828612af6fd72b534c4b3cc37c6cc7427be57725882e563ba6e5fa1ac","title":"","text":"Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-7d9e38ca05c0373afb7207ebfc7e97bf3876c0f4b9d978aaed36a7c8ff21333d","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: gping <!-- 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.2.1 desired version: 1.2.6 <!-- 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-42614d180ad06562daab1d8f22c717bbd0b0a6da236dfea1cb0034cb1ac0d3c0","title":"","text":"It would be nice if generated and options (only ). Processors without microcode update might run with misbehaving flashed microcode: /cc\nDo you mean like setting it to or just mentioning it? It's a good thing for sure to have working hardware as opposed to not working, but OTOH it pulls non free code...\nOf course setting it to true (actually to ), mentioning it would have no effect. First, already pulls in literal unfree code, e.g. Wi-Fi drivers on MacBook Air 6,x, not even redistributable. Second, non-free code is already running on Intel processors, I don't see any difference whether it's flashed or not (I know this is controversial). Third, for purposes of Nixpkgs, is free. And of course the kernel contains a whole lot of firmware blobs.\nStrongly disagree here as its an equivalent of setting = true; thus will taint every installation by default, which is a reverse policy of the current nixos from optin to optout. That said, being complete new user, I have myself figured and found these options myself. My system booted without them likewise fine. In general, AMD patches CPUs with AGEISA BIOS updates, so does Intel - however these updates are optional and up to the user. This is should be mentioned on a) Installation page b) NIxos wiki - not be made default option, because this action is in conflict with policy.\nI disagree that this is equivalent. CPU comes preflashed with microcode, BIOS comes with updated microcode for the processor to boot correctly (microcode that comes with CPU is very buggy and usually can't go through boot sequence correctly). It's not clear how it would add to the problem if we were to load an up-to-date microcode image. This is equivalent to shipping firmware to users that haven't set flag, which is current NixOS policy. Intel microcode is freely redistributable AFAIK.\nThe default state for these two switches is very clearly \"disabled\", plus they have no affect on non-AMD/intel CPUs. Flipping the switch in hardware-, is basically flipping the default state in the backstage, which is much worse than setting the defaults to \"enabled\", as it creates distrust and inconsistency cases. Further, firmware updates can cause real issues, not only solve them."}
{"_id":"doc-en-nixpkgs-5b217a68d66af1734eb5b71984811e987fb7670ed88ad162b0c9a8cfdac7d37f","title":"","text":"It is irresponsible to think that they only solve issues. AMD AGEISA updates on 785G on has actually been broken for over a year for me, refusing to react to USB events on boot until I manually bypassed the tier 1&2 support (which is hell of a job for Linux user) to get to actual support for testing. About Intel, I have only encountered issues with gen3 PCIe cards in Intel motherboard for 2nd gen Core CPUs, but fixing this also required a year of waiting and UEFI reflash. Also speaking as an owner of HP() and Epson(sx525wd) printers - updating ucode actually caused hardware reflash and made legally purchased cartridges worthless. I am yet to encounter a CPU that can't pass boot sequence due to buggy ucode, but I doubt hot-loading it on OS stage would fix it, because it needs first to get to this stage. However I can clearly imagine the unpredictability if these switches are properly enabled.\nMicrocode is essentially a firmware for the CPU. NixOS, more specifically, the Linux kernel, will load firmwares for any device with support for that without asking the user. Loading microcode updates does not require a policy change, if anything, this would make the policy more consistent across the board. On a tangent, I don't understand why anyone would tolerate a blob flashed on CPU, and in BIOS, but would not tolerate the same blob being loaded by the kernel. That can be said about any software. Usually, the opposite is true. What I mean is that every BIOS except Libreboot contains microcode blobs that it loads onto the processor early in the boot sequence. Without that blob, boot sequence will most likely fail somewhere along the way. That's the reason why Libreboot doesn't support modern Intel/AMD CPUs, and why there is Coreboot/Libreboot split in the first place.\nYou are mixing very different cases into one bottle. Some hardware requires ucode to be loaded to function and won't function without. Some hardware has optional ucode updates. For this hardware, some classes load firmware update and then flash themselves - some lock the possibility to install previous revision, and some classes load the ucode as temporary override (which is case with AMD/Intel). Some hardware has open firmware (sources), but majority does not offer source."}
{"_id":"doc-en-nixpkgs-2f02b828015c0c66e5b57c87bbac05772cb6c253303b2e0693242a0a5340e317","title":"","text":"In essence, ucode is a blackbox and live-updating ucode is unpredictable black box. For some devices, ucode loading is a must, for others its optional. I suggest that we limit ourselves to specific case of Intel/AMD ucode, for which ucode updates are optional and crucial updates are applied only via hardware flashing. I am pretty sure that the reason why Libreboot supports less hardware has to do purely with acceptance criteria for how tainted (\"blackboxed\") the firmware is, and that both support little of x86, because Intel refused to provide specifications and AMD was open to some extent, but then closed up the AGESA after Phenom II because they most possibly implemented TPM in firmware(fTPM). About EULA-d + encrypted software, we are talking about closed-source hardware. For manufacturers of such software, surely opposite is true and the updates are usually used to keep their policy consistent and enforced, for users it means giving up and restricting all rights. That said, I found those options myself easily as a new user (yet my hardware functioned without issues without them) and I see a problem if they default to one value, but change \"automatically\" and unnoticed at run-time. Either way, this option should be documented better - and this includes places where its flipped.\nIt's not clear what difference does it make. Say, from freedom perspective, it would not be OK to use Windows even if I were to ignore any updates for it. If we ship updated microcode, which includes security fixes foremost, how would that taint installs any more than they currently are, with in-kernel blobs and such?\nIt has to do with blobs for the most part. See:\nIt replaces non-free code with a more up2date non-free code. Given Meltdown and Spectre this should be the default. Especially since it would be generated at installation time. Accompanied with the right comment, users who really want to have outdated CPUs will be notified and can delete one line. (well two with the comment).\nI would like this to default to (microcode essentially is firmware). isn't supposed to be edited, it should just use so that user can override it in their config.\nThank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days."}
{"_id":"doc-en-nixpkgs-6c157630df878e5ef31df6e26df79339463e0c0fa99a2914ddd096c46782f126","title":"","text":"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 think this should be done, as new users probably don't know this option exists at all and that you have to enable it by yourself in NixOS. With concerns on, this should at least be generated as commented out, with a hint \"while you will probably want this, note that it is unfree software\".\nI marked this as stale due to inactivity. &rarr;\nWhy is this no longer in discussion? As someone new to the NixOS universe and coming from Ubuntu I wasn't aware that I had to explicitely include this in my hardware configuration on NixOS until I stumbled across other people's configuration files. I definitely think it should at least be prominently featured in the installation manual or even better be enabled by default, as mentioned.\nOne way or another, needs to be enabled by default. These updates fix security issues, there are probably a lot of NixOS users now that don't even know that they're running insecure microcode. See also the discussion in\nI've never replied to the first comment! While I still support the open hardware movement (and thus free software firmware) I also believe that having QEMU misbehave because of a missing update is not really a good default option. If the user is concerned about the microcode updates or about managing security at this level then they will probably read the auto-generated configuration and immediately spot an and will comment it out :-) So thanks for the PR, I can't review because I don't know perl :-p"}
{"_id":"doc-en-nixpkgs-cfc944e3ff75cd8b88d714d9d00b36dc72ad9d24f7b574bf86ed37fab89d7275","title":"","text":"Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc\nYou can puts secrets in an additionnal initrd readable by root only, and use See\nThere is more generic option now, . We probably want to merge those."}
{"_id":"doc-en-nixpkgs-3eaaedb56fcd4e2cbaab13bd37a50ae1cdc811e7b75d7995167c62fde6b424c2","title":"","text":"via In short: rainloop, a php-based webmail client, features a trivially exploitable stored xss vulnerability. Upstream is unresponsive, and seem to have ceased development. This page explains how the XSS works and proposes an unofficial patch: Example of an other distro applying this very patch:"}
{"_id":"doc-en-nixpkgs-2b13e3d9fa207734d6091484ac303e6d71db2dd653e0b9c7f2cadd49fdf91f18","title":"","text":"Package name: keepmenu Latest released version: 1.3.1 Current version on the unstable channel: 1.2.2 Current version on the stable/release channel: 1.2.2 Notify maintainers Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-46a1f204c79f80b21ff5a6bdfbef8842229badfe1b11ca667b776397d8f6e3e5","title":"","text":"uses to determine the substitute for the shebang path. This selects the wrong path during cross-builds and results in x8664 binaries getting pulled in as dependencies to cross-built binaries that can't possibly use them at runtime. I don't know if we can reliably pick the correct /bin/sh without it being in the PATH envvar. I presume patchShebangs works fine for binaries that don't overlap with stdenv's and are included in buildInputs. If you cross-build some packages to ARM platforms, patchShebangs runs in the fixup phase and run , you'll see it points to the native /bin/sh rather than the cross one. I was considering a PR to just add to the cross build of glibc, but figured it'd be better if the root issue were fixed instead. System: \"16.03pre75806.\" Nix version: nix-env (Nix) 1.12pre1234abcdef Nixpkgs version: (Gorilla)\n/participate. (I've stumbled across this too.)\nIs it safe to assume are the only paths that will ever realistically have this problem? If so, how and where would we pull in as a buildInput without it clobbering the native /bin/sh used by stdenv to run the builder? Once we're already executing , it's too late to find any s. This problem overlaps with another, , which is that crossDrvs clobber stdenv's binaries in the PATH. The best solution I can come up with is to manually include in of e.g. glibc, add logic in to not add to the PATH when crossbuilding, based on some new derivation attr like , then search during , independently of what's set in the PATH. Or we could just make smarter about importing /bin/ PATHs that contain elements of the stdenv, namely: .\nis essential to fix this without greatly complicating bootstrapping.\ndon't forget to close. :)\nAddressed in"}
{"_id":"doc-en-nixpkgs-f7eebc3a2cf59fa1b877c1e72aa3cddaa58e943112fdb8e811c501e06c0652dc","title":"","text":"Describe the bug VAAPI records repeated frames (see upstream bug report). upstream fix: To Reproduce Steps to reproduce the behavior: ... open OBS ... try recording using VAAPI (possible AMD hardware required?) ... watch replay Expected behavior full FPS. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:\nAs for 21.0, the fix contained in upstream release = 21.0.2 so e.g. PR\nSadly a look at that thread, it's blocked because something broke, and they're not pushing it to 21.05, so this bug is going to exist until someone figures this out the regression, this patch is only one line of code, maybe it can be supplied as a patch until they get 21.0.3 working? Is there a way to build a patched mesa without rebuilding my entire desktop stack? It's currently stupidly slow on my computer when doing a packageOverride.\nThis will not be the only bug people will have to deal with on 21.05 unless we backport a more recent mesa (=21.1). Alternative we could also start to includes as well. Without it, this will lead to crashes in wine (incl. steam proton) when on some hardware ( for reference). While one can set as a workaround, it is hardly ideal and difficult to diagnose from within steam alone. Would it be possible to backport the mesa update currently in staging-next () once it is merged?\nI don't know... this is hard. Maybe after a version has been a couple weeks in , we might be sufficiently confident that it won't make things worse overall.\nI'm okay with backporting it, but probably as its own job set, just to get a better idea of regressions.\nI'm not afraid of build-time regressions in this case. Those would be easy (to find). And mesa isn't such a big rebuild now anyway.\nIf it's been on unstable for a while, I guess I'm okay with it as well\nI guess we can close this now, I haven't noticed any problems recently."}
{"_id":"doc-en-nixpkgs-a311f77ded34a466978f3112c166b771660c8817dba359884f5a6bfc50ceed3e","title":"","text":"Describe the bug nixpkgs has moved to unified cgroups (woo :tada:) as of recently (). Unfortunately, k3s fails to start correctly with unified cgroups without , which isn't included in a release yet. Until that lands in a release and nixpkgs is updated, it can be worked around by setting I intend to work on fixing this; I'll drop any notes along the way in this issue.\nI've updated the title to be more specific, since my actual errors are coming from using k3s with , and the error is specifically about kubelet and docker's cgroup driver mismatching. I see that the unified cgroup PR did disable unified cgroups in the k3s module, so that probably should work before adding in the docker runtime. I need to do a little more investigation here.\nPlease let me know, if this is related: I'm trying to follow the wiki article on kubernetes on nixos: With the configs shown there I run into an error when starting The full error is very long, I've uploaded it here:\nThanks for looking into this.\nJust tried the workaround mentioned above: Setting also fixes the problem for the kubernetes service\nWe have observed that unified cgroups also breaks Kubernetes-in-Docker for node images prior to 1.19. The observed behavior is that the kubelet fails to start, with the message: Also able to work around with\nFor k3s, the v1.20.4+k3s1 release includes unified cgroups support. It fixes my use of k3s, though I also had to set a flag in the nixos module ( to make docker+kubelet match). I've opened up a PR to bump the package (), and I'll make a separate PR to fix the nixos module to pass that arg. I think those two changes together should fix this issue. It sounds like there's other work to be done for other ways of running kubernetes on nixos too, but I think we should open separate issues for those to avoid conflating too many issues at once.\nThis would be the fix: I was not invested enough at the time to also write release notes, but if you want you can pick up the change.\nsee\nThis PR should also help:\nThis issue has been mentioned on NixOS Discourse."}
{"_id":"doc-en-nixpkgs-dc037b5d228f034989b2e94c1dd4d20687476d6eb2283b123f465f9604fb7e7e","title":"","text":"There might be relevant details there:\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-3800278f71ed9b0308c8ca3f2e4c11ccc2d70addfa299d7b2252258726bbe4da","title":"","text":"Running a fresh fails, the core message being: Steps to reproduce the behavior: a rust project (or if you already have one) Either the rustup gcc/ld to be patched for NixOS use, or rust to use the system gcc/ld. Please run and paste the result.\nActually, it looks like this is an issue specifically appearing with ; so I'll try to pass the message upstream.\nVery specifically, introducing the issue, when it has been decided to switch from the system linker to . I suppose the new binaries should also be elf-patched?\nPatching those binaries will make them execute, but they also need the applied so that the binaries they build will also get patched automatically."}
{"_id":"doc-en-nixpkgs-3ff732e1a55cc098dc036bf4b1ca8c308b79202bfc929d01f128b812494bc7ab","title":"","text":"Trying to compile fails with Install (not ) Create with run observe error\nhas gmp but doesn't have Base or Prelude (which is needed for stuff as simple as )\nFor reference, I think this issue is related:\nYou are meant to use to install additional packages with the compiler. I don't understand why the attribute it broken though from a brief look.\nI bisected to the commit that caused this: This was in the idris update from 1.3.0 to 1.3.1 Currently looking into how this can be solved elegantly\nIn the meantime, is there a workaround for this?\nYes, the PR linked above () fixes this, but I'm not sure what to do with it, because it breaks Darwin in weird ways."}
{"_id":"doc-en-nixpkgs-3d837407570ef0746d109f05cbb051835cbb029eac3fc3be766b7c9131706812","title":"","text":"Olaris server requires ffmpeg to be available and raises an error when it can't be found: Steps to reproduce the behavior: olaris-server a library. The software runs correctly. There are two main ways to fix this: the software to use the full path to the ffmpeg dependency (ideally upstream). the program to add ffmpeg to its path. Please run and paste the result.\nIn fact it looks like it needs a custom image as it passes arguments that only exist on the modified version.\nActually it looks like the fork is no longer required: But this doesn't seem to be released yet. But probably is still a better option than packaging the custom ffmpeg.\nyep, this looks like an easy fix EDIT: I was keen to try building the ffmpeg fork so that we can stick to a released version, however that proved prohibitively difficult, so tip of the default branch it is\nno action required, but note the way I used in the pr and commit, means this issue would have autoclosed when the change merged\nThat is what happened.\nsorry, I only saw this issue's update and assumed that you manually closed it; I assume most people involved in nixpkgs prs do not have merge perms, and github really needs to work on their ux. terribly sorry for the hassle, and assuming you were a more novice user.\nNo worries, GitHub really doesn't make it clear."}
{"_id":"doc-en-nixpkgs-7217fef016741e1e171b812784843cabb8dd2e003c3af604d43bf381b78421d4","title":"","text":"The current wxmac port fails to build. Build wxmac from latest git. wxWidgets uses some deprecated CoreFoundation functions, which are no longer there. Upstream version 3.0.4 still uses these functions. Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(sperber): nixpkgs:\nThat's very annoying! There has been a recent update of CF by that uses CF from Apparently they don't implement these deprecated APIs. We should be able to patch it to fix these references and use updated APIs. For now though you will probably be stuck on 18.03 or 18.09 if you need wxmac.\nYeah, I looked into that for a while, but the references to the now-unsupported FSRef type are pretty widespread in the wxmac codebase. :-( (I don't need wxmac directly, but erlang depends on it.)\nYeah, I patched those calls out of QT 4 but haven't gone and looked for other stuff that uses them.\nLooking at source, it doesn't look like those functions are really used in any essential way. If you look at who calls , it doesn't really seem to be used anywhere much, and is used to set some icons. Or vice versa, but either way doesn't seem like it would be hard to patch out.\nI was thinking the same thing, but my impression was that these are part of the public API of wxWidgets.\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-f8b0af8258b445f697091bd21f8c0e094d69162ee96eb14f3a359771047ecb23","title":"","text":"Steps to reproduce the behavior: Tested on a MacOS 12.6.7 (Monterey) on a MacBook Pro 2016 (x86) Please run and paste the result.\nThe logs above say 1.6.1, not 1.5.1 - I think the title needs to be edited to reflect the correct version I'm seeing the same error with poetry 1.6.1 on macOS Venture 13.4.1, 2018 MacBook.\nThanks , that's strange, I'm new on nix and I thought the version nix were installing was the one I got using (). Looking on github the official poetry version is 1.5.1 () while poetry-core is 1.6.1 () but it seems that poetry-1.5.1 is failing. If not, can I ask your support to \"decode\" the logs? :) Thanks\nIt's poetry-core 1.6.1 that's failing to build. Try building .\nOh, that's right, thank you. I'll update the title and the notes."}
{"_id":"doc-en-nixpkgs-9d82085bcd7b6fc81837c390ef969ac7fd7329969e463aa5686ba84230ebed6a","title":"","text":"Package name: cypress Latest released version: 13.13.2 <!-- Search your package here: --- Current version on the unstable channel: 13.2.0 Current version on the stable/release channel: 13.2.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! --- The following PR exists but seems to be abandoned: Weirdly enough I am also experiencing that the 13.2.0 version actually delivers 12.17.1, I don't know why...: ! 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-175c9a3d1d04a313068892412bf6d217025f64739c076c88485615603d3b16ff","title":"","text":"Project description Yark lets you continuously archive all videos and metadata for YouTube channels. You can also view your archive as a seamless offline website. Not a high priority request, but could be useful. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin (anything with Python 3)"}
{"_id":"doc-en-nixpkgs-792daead3c7abfd024b3b9d2055871074f96e2a592f1e95604cb7e8e32ce76d9","title":"","text":"the python binding for krita are not build correctly. Please run and paste the results.\nmore details wouldn't hurt...\nwell I don't exactly know what is happening here, to build the python binding, it requires and . So when are to the buildInputs, cmake finds all the dependencies correctly; however, at around 98% the compilation fails due to not finding some sip bindings. Alternatively, if is to the buildInputs, everything works fine as intended. But the python interpreter overwrite the python interpreter in the nix-env, so that doesn't seem to be the right fix.\nalso tried setting the variable, but that didn't work either.\ncc who worked on / in"}
{"_id":"doc-en-nixpkgs-026ea8ca8a162def863ee871975c11bfe5a612f41ed0c3f078858bf62f5bc3f7","title":"","text":"A clear and concise description of what the bug is. Prism Launcher doesn't allow enabling Feral GameMode or MangoHud under the \"Performance\" tab because it can't find it. Steps to reproduce the behavior: GameMode ( ) MangoHud ( ) Prism Launcher ( ) new instance in Prism Launcher instance and go to \"Performance\" tab A clear and concise description of what you expected to happen. GameMode and MangoHud should be able to be enabled when installed. 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.\nAddressed here -"}
{"_id":"doc-en-nixpkgs-ff90696f9af111ddf69aa3a3a37be6b0b319ac884e4569743b17f4b7df269aa8","title":"","text":"Neovim frequently coredump It is hard to reproduce the behavior, it always breaks down in unexpected situations no core dump ! <!-- 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.\nIt might be caused by neo-tree. I haven't seen any crashes since I moved from neo-tree to nvimtree.\nAlso pretty sure it's neo-tree, I have the same issue . I've already built debug symbols for and am waiting for the next crash to get a detailed report.\nnot nixpkgs relevant (report to neovim with stacktrace)."}
{"_id":"doc-en-nixpkgs-51401085a799343ca4dd3e22aff0c2c7c48787d43df9af19699f7c3443b2cef5","title":"","text":"Steps to reproduce the behavior: auth0-cli from the unstable Failing to fetch sources following The 1.5.0 release from Auth0-cli has disapeared from GitHub Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-008e56dbddb48bb3695bd4eefd3f7783ce29dc52f97c5823e1a90c84bd7c3842","title":"","text":"Project description Scala 3 is more than a year old. It would be nice to have it packaged in nixpkgs as well. Maybe it is, but I couldn't find it under \"scala-3\" or respective versions. Metadata homepage URL: https://scala- source URL: license: Apache-2.0 License platforms: unix, linux, darwin, ...\nis already packaged.\nIndeed: the Scala 3 compiler started out under the codename 'dotty', and that's how it was packaged initially in nixpkgs. Now that dotty has become the 'official' scala 3 compiler (see also ), we should probably rename the package to as well? /cc\nFeel free to update, rename and alias the old name :) Maybe should point at and can be"}
{"_id":"doc-en-nixpkgs-abdca4f00a84d0c57e5992280d0a91aa8674f172a4d23edff6c1324822c47a7b","title":"","text":"In combination with 21.11 adding it to the job, this prevents channel. The keymap tests don't have any maintainers. That's quite an issue for channel-blocking jobs, I think.\nWell, we could remove from the blocking set, at least for now. It certainly doesn't feel so critical to me. (Though qwertz layout gets vast majority in my country actually.)\nIn it was discussed wether Linux 5.15 could be the cause, but the way I see it the test is running with Linux 5.10? 5.15 seems only to be used for the stdenv.\nYes, It is at least surprising that a large part of the channel tests is about keyboard layouts.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nif the keymap tests have no maintainers, perhaps they should be removed, or at leat disabled for now.\nit looks like its random which one symbol fails azerty fails sometimes too\nThis test has been flaky since and does not provide much value. I propose to simply remove it from the tested job.\nI'm thinking this is a race condition with sending keys too fast, maybe made worse when a builder is under high load. Something like this perhaps?\nEDIT: it takes way too long to run the test without kvm so i didn't i'll run the test with and without that. and with running to mimic high load i had to apply this patch to run the test vm because kvm was failing but its very very slow now\nSo, at least the simple step for now?\nthe sleep patch does indeed fix the issue, at least when building on my Honeycomb. I do think it's odd though that the test fails in exactly the same way every time I run it. I'd expect it to fail less consistently, or in different ways…\nazerty test fails sometimes too\nWhile it's far from elegant, I'd be fine with adding the sleep patch. Since it's only 10ms per character, I don't think the performance impact will be significant, and I'd prefer to start verifying the functionality again (major use case: encryption passphrase input, where the results aren't even visible)."}
{"_id":"doc-en-nixpkgs-98090c5786e880665981d54124e0870d0462818f45c7d9f412d81357e2465bca","title":"","text":"i've run some tests on my rpi4b and found that applying this patch fixes the issue even with load and no delay(i still think we should leave the delay) <pre<del0.02 sometimes works if there is no other load at least 0.04 is needed to sometimes not fail when i run 1 is safe according to this the average inter-key interval of a human is 238ms INTER-KEY INTERVALS Average inter-key interval is 238.656 ms (SD = 111.6). A lower bound of about 60 ms can be observed.</del</pre"}
{"_id":"doc-en-nixpkgs-341c76e7c9894ea557cfb006d79dce60ac4381fb75e55a7b5970a2a6a87a0227","title":"","text":"Since commit the command is missing. It is used by xscreensaver to display text inside the screensavers like system information and kernel versions. It used to be in the package, as can be seen from this diff: The same applies to which was also removed by that commit Steps to reproduce the behavior: Text is printed when running instead of If applicable, add screenshots to help explain your problem. Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(root): channels(pinpox): nixpkgs: Maintainer information:\n«removed» here means «same lack of special measures as before» (the lines you cite are just fixes for the installed stuff), but upstream underwent a major rewrite. (Not saying that fix is not most welcome, just that this was not a removal as much as lack of finding out what to do now) Apparently the scripts are there in the tarball, maybe they need manual copying now, not sure\nI just noticed it seems to work fine in the previewer application that comes with xscreensaver . E.g.: ! The same screensaver does not work though, when it starts \"on it's own\" after some idle time. The text then only reads Not sure what the difference is.\nxscreensaver-text and others are in $out/libexec/xscreensaver btw speeds up the build of xscreensaver by a lot\nHm, is not in my path, but hacks launched via XScreenSaver proper find text just fine. And the daemon source code implies that is indeed to PATH in a normal situation.\nNot sure if it's related, but it is also missing commands like and (output is shown in some of the screensavers). I have enabled xsceensaver with the home-manager option"}
{"_id":"doc-en-nixpkgs-c35aba1824f05a6f963f1b6c2e1791d86292abf331dbe75c04858348d908f93a","title":"","text":"Project description A dbus api to start programs on a different GPU Metadata homepage URL: source license: gpl3 platforms: linux\nDuplicate"}
{"_id":"doc-en-nixpkgs-2ad151effaeea91f6f10ce3eeb9184b52fd4392437b6c9805fe88b556d231412","title":"","text":"Package name: LLVM Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 18.1.4 Current version on the stable/release channel: 18.1.4 <!-- 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]:\nWant to submit a PR? The last upgrade was very straightforward:\nI'll give it a shot"}
{"_id":"doc-en-nixpkgs-b580e120d23680f874d0e57b8a2a1deb79dd5af540acf9df8617b37d6af60b0a","title":"","text":"We already have in , but only with iptables support. It would be nice to have the nftables version available as well.\nBeing worked on in , I'm trying to test myself but couldn't make it to work yet.\nI think the PR is ready now, testing welcome!\nMaybe add an option for will be better?"}
{"_id":"doc-en-nixpkgs-c9c6a7b3bccce75eed4f8d044a2b97cee7a7543ab21b6a305908762577d2e083","title":"","text":"Project description Hardened patchset got released for Linux 6.6. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nHi, created the following merge request. Would appreciate a review.\nwill try to check that tomorrow's morning if my ibs allows me to, thanks"}
{"_id":"doc-en-nixpkgs-e74717216072e8d825772673ac903e367c9a0125b9a14f8551510ff929cd5662","title":"","text":"Originally spotted by (thank you!). Steps to reproduce the behavior (assuming and are both ): The environment variable contains semicolons and must be quoted, otherwise bash will interpret the semicolons as command separators.\n- Hey, I am not sure how to clean up the mess I just made on . Really embarrassed. I intended to rebase and hit merge instead, which pulled in 10k changes.\nNo worries, Happens to everyone at some point :) Personally, I'd just open a new PR.\nHere it is: . Does the commit history look clean enough? I'll try to rebase it later, but I am concerned about retagging all of those folks.\nI'd say don't worry about it -- as far as best practice goes, I'm actually not sure what's recommended for commits. do we recommend squashing before merge? I know I typically just do force pushes to avoid any commit history :l\nI went ahead and squashed, and I'll post a nixpkgs-review when it's finished.\nI don't think we have an official stance on this. Contributors use their best judgement for whatever keeps the commit history simplest and easiest to use"}
{"_id":"doc-en-nixpkgs-7038467b19a86149a839ccf4a5afb8e85ba15494630aba38e6a444adb8a9ec39","title":"","text":"Describe the bug In NixOS 20.09, Emacs now has the output of gtk+ in its closure, which in turn causes it to pull in stuff like mesa-drivers (424 MiB): This caused the closure size of Emacs to increase from 339 MiB in NixOS 20.03 to 1324 MiB in 20.09. Metadata NixOS 20.09..\ncc\nThis was reverted in\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:"}
{"_id":"doc-en-nixpkgs-d6bd09ec96880ca6d9e0062d93efccf5d716aa3c65268ba6e35d73e0735ed8b8","title":"","text":"Steps to reproduce the behavior: g810-led Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-12f34057e0a18cf4ed2f00ea8b6fa4b4074b17e8d531ca863901c9e76b7c5de6","title":"","text":"Package name: Latest released version: 555.42.02 <!-- Search your package here: --- Current version on the unstable channel: 550.78 Current version on the stable/release channel: 545.29.02 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-e60648377720b383c169f24114629dbd4582ae69439fd9ebb8179ef2c2279be1","title":"","text":"I'm trying to install joblib for python 2.7 on a Mac, but the threading and multiprocessing tests fail. System: Darwin Kernel Version 13.4.0 Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: \"16.09pre83147.\"\nAs I mentioned in you're not supposed to install Python libraries like that. Even so, the error is still a bug. Unfortunately I'm not using OSX myself so I can't be much of help I'm afraid. I do know there are issues with multiprocessing on OSX with Apple vecLib / Accelerate.\nOk, now I know you have to use nix-shell to load python libraries. Just adding here that gives the same error."}
{"_id":"doc-en-nixpkgs-6f569b6738a4bb07c7a981305ac7cd0343f24184d8270e08186f16e51a485732","title":"","text":", CVSSv3=7.5 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc"}
{"_id":"doc-en-nixpkgs-46d046f221f9ab1d009937f952032b2875d5db56c4c7fe622413847e29ff5a3d","title":"","text":", CVSSv3=9.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc"}
{"_id":"doc-en-nixpkgs-9c939a151dcd90c8e948b71d1101b5697da3c65371221dd2fc722cfd96e17fba","title":"","text":"gv crashes with a segmentation fault immediately upon starting, before a window is visible. This happens even with an empty dummy document (created using latex and pdf2ps). For ease of reproducibility, you can find it . $ nix-shell -p gv [nix-shell:~]$ gv Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nThanks for merging! Glad that this is fixed. :-)"}
{"_id":"doc-en-nixpkgs-503c3de22b7640323f0f8d53d36601206cdb15ae1f443dc7517fd3d2609b7a1a","title":"","text":"Steps to reproduce the behavior: error occurs is installed as a standalone binary. There is custom configuration: The test that fails is : I would, but it depends on coreutils. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSeems like a \"known issue\" without a solution with cephfs and that test: If you can use default path for store instead of: you won't have to build it yourself as it should be fetched from instead.\nUnfortunately, I very much cannot use . Given that it's a known bug with that test, would a PR disabling that test likely be accepted into nixpkgs?\nMaintainers for in nixpkgs would probably be able answer it better. But you can always overlay/add patch to your own config. Considering you are already building everything from scratch there won't be that much difference there.\nNot sure why this wasn't auto closed."}
{"_id":"doc-en-nixpkgs-39f16984caea6c27f39207069ab7d445b50eaa5f25a70d0a6fb3a0e9aae1b237","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-d4dd50e17fe60a9d8d698537e21739b338e736c280cfb89898bc5c979f255a36","title":"","text":"The Haskell package chell does not build due to missing dependency . I think this the culprit: Try to get a nix-shell with purescript and nixpgks pinned to . Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(stefan): nixpkgs: (Note that this fails with a pinned nixpkg, see above.)"}
{"_id":"doc-en-nixpkgs-3365c4c5422ca3f7323fa4415145f44ddc3221b7e1c14735e24d5665df168927","title":"","text":"During systemd-boot update step attempts to touch EFI variables, even when is set to . Steps to reproduce the behavior: NixOS 21.05 with systemd-boot and to NixOS 21.11 () switch fails with: An error is just an indication of update trying to touch EFI variables. (I have EFI vars touching disabled on that system because of some unrelated firmware breakage) Manually running properly finishes, further switches work fine. systemd-boot update should not touch EFI variables during upgrade. <!-- 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:\nI had a similar issue which I fixed by running \"sudo nixos-rebuild --install-bootloader switch\"\nThe fix for this got reverted in"}
{"_id":"doc-en-nixpkgs-dc0ddcf372ad5879478138c1d6c1c17d9ea7848e3f3dccc5e77cb459b8b8cb1a","title":"","text":"Describe the bug The menu icon for Stepmania is missing. To Reproduce Steps to reproduce the behavior: to find it in the Applications menu. Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-e4a5d2e448e13b08d64220f5b2613c1cd1c13cf5abc26914d8a66c2ce6d04cbe","title":"","text":"Steps to reproduce the behavior:\nI don't have an M1 to test\nOh, it suffices to use . I'll open a pull request."}
{"_id":"doc-en-nixpkgs-36423f37579cc5b66e4b506f3e944b9bdd7d34497be22ad6b2219d3c771fabea","title":"","text":"Steps to reproduce the behavior: truststore Output of : Adding to solves this issue. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-ce6359f5c944e8d15376b7c92a3e9ba560f74f1bf2127f8440dfa42df85ed855","title":"","text":"Describe the bug fails to run because setuptools is no longer propagated implictly. If were purely a python application built with then we would just need to add to propagatedBuildInputs and be done. However, is not simply a Python application, but a wrapper around , and isn't built using. The derivation patches the script as follows: This does result in the site-packages directories from all python packages ending up in , including setuptools (e.g. ). I'm not that familiar with Python packaging but from experimenting I found that the full path to the Python egg needs to be included (e.g. ) in order for this method to work. I made an attempt at resolving the issue but being new to Python packaging in Nix, neither are likely to be ideal: We could use buildPythonPackage in place of mkDerivation, using and use Or continue to use mkDerivation and manually set for patchPythonScript: I'm happy to submit a PR but I'm not sure what the recommended solution is here. To Reproduce Steps to reproduce the behavior: Expected behavior should launch with the extension loaded: Metadata system: host os: multi-user?: sandbox: version: nixpkgs: Maintainer information:\nIt seems is normally used by adding a to , or calling with (what the wrapper registered in does). This script then just does some addition calculations to register itself (we probably don't that at all) and some python 2 specific fixups, and then calls , which starts executing some code on import. I'd suggest to package it as a regular python application first (via ), so you can successfully import it inside a . The python tooling should automatically take care of patching the python shebang properly if you make script executable.\nproposed fix"}
{"_id":"doc-en-nixpkgs-d7878f3d32b5f93f56f0ecee2cb2b0acf9d682536b8cda884d3e5f6867f31dff","title":"","text":"Unfortunately I can not pinpoint the issue, but it seems that after a on Feb 1st, starts to omit a key file out of 3 key files and completely fails with a fresh system installation. Steps to reproduce the behavior: .nix contains the following lines All three files exist on disk. -rebuild switch produces a initrd-secret archive that is missing the third key file. system installation produces the following: All key files are included in generated initrd-secrets and does not fail. This issue does not exist before system update. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --This option is declared in <nixpkgs/nixos/modules/system/boot/stage-1.nix. Please run and paste the result.\nI specifically installed an encrypted root on zfs system with . GRUB will decrypt disk on boot and initrd will re-decrypt disk partitions and swap with the keys embedded here.\nI have that too, there seem to be a problem with here: Not sure where it is set from, but its value should be relative to the chroot, e.g. , not . It can be worked around by setting to an existing directory before installing/rebuilding, for example: Or by preparing a directory with yourself:\nMay be a duplicate of\nDuplicate of indeed."}
{"_id":"doc-en-nixpkgs-78dffdf175489c154bcfc237ff25f4b6de481da17cd59e5223141eeed04fc02c","title":"","text":"When trying to start the App from the launcher, nothing happens. In the terminal starts the text based version, but typing throws the following error =Source: Also check: And this is my system: !"}
{"_id":"doc-en-nixpkgs-a3862f47b58f1ea32fa8709f9c242743f0a82da095fbf0b05d5b864f0c975b62","title":"","text":"Building uses more () threads than it should (i.e. 2 if / ). Steps to reproduce the behavior: as the build will use way more than 2 cores. Build should honour properly. This was with . This does not in fact use just 1 thread. :smilingfacewith_tear:. ! Happens on master () and 22.11.\nI don't have any time planned to fix this but if you figure it out please send a PR."}
{"_id":"doc-en-nixpkgs-a2a224b1a4723fa4db3fe2e90819cffaac908a7d62565a3c2c96089b4d8735f5","title":"","text":"I ran into a problem when trying to install PHP + PECL extensions (via package). When PHP compiles, it installs extensions configured during build into a default directory like which differs for each PHP version and compile configurations (like ZTS support). When installing PECL extensions via ontop of PHP, they are installed into a fixed directory which makes it impossible to load those via (without knowing the absolute path) as PHP expects them to find in . In scenarios where you define your outside of nix context, it is impossible to load the PECL extensions. I wonder if a consistent extension directory for both PHP and PECL extensions could be established. Maybe the PHP package could set the (see ) environment variable to before like it is done in the . That would make it much easier to configure PHP extensions. See my profile to get an impression: /cc"}
{"_id":"doc-en-nixpkgs-e52ceda066b88b18beb080b42c20c1583adf0cf3469cfdd2a1a31ab24e64601d","title":"","text":"Describe the bug I don't know if we should just update it or not. To Reproduce Steps to reproduce the behavior: on master Expected behavior Screenshots Additional context Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(bbigras): channels(root): nixpkgs: Maintainer information:\nI can reproduce the issue locally It used to build previously The current is not in the Hydra cache because was never built by Hydra, so, unless someone else has the , we can't compare Upstream tag doesn't appear to be updated, git repo doesn't use export-subst It is not clear to me what has happened here.\nDear all, the tag v1.7.4 has been changed after October 2019. It was not published for long as it involuntarily got into a commit. There have been no public releases for v1.7.4 marked on Github or our the FIRESTARTER Website as of October 2019.\nThanks everyone for the help. :heart:"}
{"_id":"doc-en-nixpkgs-ec7382fae197d115ee515ef50618c31f5235d8890d900943e363a26e0da4b748","title":"","text":"Package name: clipboard-jh Latest released version: 0.9.0 <!-- Search your package here: --- Current version on the unstable channel: 0.8.3 Current version on the stable/release channel: 0.8.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-52c03266a90003464588c79ed4378f159a5f4de443df1fe8742a3cd8145a8881","title":"","text":"Describe the bug As of rust nightly 2020-06-22, Rust nightly cannot find This issue is not present in Rust nightly 2020-06-21. To Reproduce Steps to reproduce the behavior: Expected behavior rustc works Additional context This also happens with rust nightly from Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(jade): nixpkgs: Maintainer information:\nWe are currently using in internally to set the elf interpreter. Looks like we need to extend this to also extend the RPATH to add zlib. If someone makes a PR, I will review it! Not sure when I would get to implement that myself.\nHere is where we add :\nI'm working on a patch for this. This is definitely the issue, just need to find the right way to extend the RPATH. I have something replacing it with a path containing zlib, but that overwrites the existing , which breaks it. I would like to verify what is setting there but hardcoding it should provide an early fix\nExtending the RPATH seems not to have worked\nI'm investigating patching the files in lib This issue may have been introduced by rust-lang/rust so it's likely the new zlib dependency shows up in the LLVM libraries"}
{"_id":"doc-en-nixpkgs-be3a71f8ba7875c19739147137473a9aaf9dbf873536cb7c10194e39da90694d","title":"","text":"tests link to , however is not explicitly included in of . This issue is normally hidden, because (for example) links to and so it is brought along as a transitive dependency of . However, may not always be set to . For example, doesn't link to . As a consequence, applying the following overlay and attempting to build results in the following errors: does list in its , however actually refers to that only includes the wrapped compiler binaries. If my understanding is correct, is provided by instead. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-c77a043f38981170b115faeffe437bf4188dbcb09ca198501d19632433274dd4","title":"","text":"name: hilbish I guess? dunno how to use current version: 1.0.4 desired version: maintainers: Please tag this issue in your PR. I tried to update it myself: But that's not enough to get it to build and I have no experience with Golang stuff: Also: This is outdated. , and the releases have pre-compiled builds for both of them as well: !"}
{"_id":"doc-en-nixpkgs-aa62fcb303ed52a607784b35915b1fa64b600a88f20e590bf2636e2f7c715ad8","title":"","text":"Steps to reproduce the behavior: firefox-unwrapped from master branch Please run and paste the result.\nThe hash listed in has apparently changed at 16:36 UTC today. The tarball was already available earlier than that, so the release apparently changed later that day. That would also line up with the hash you are seeing. ` In fact, we have the same hash as e.g. . Will investigate the change shortly, then update the hash."}
{"_id":"doc-en-nixpkgs-a55ecc7875035a29f11dc5bbd94e35bc02992c57d750a8bddc3efc44cdff538a","title":"","text":"Describe the bug Just lost on two different NixOS machine my Signal Desktop history because of this faulty update... I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss To Reproduce Steps to reproduce the behavior: Signal Desktop Signal Desktop you to delete db, if you interact in a wrong way it will delete your data Notify maintainers ( and\nSorry to hear that. I recently lost my history too... It's really frustrating! Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers). AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime (\"expire\" 90 days after the release, see my comment in ). Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough. (I raged a bit here but after I realized that one cannot even import old backups I had to take a break.)\nI just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database). After many things, the easiest fix to ensure proper functionalities IMHO is installing: This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess. That might not fix everything though :upsidedownface: Opened a PR:\nFYI, in case anyone has feedback/suggestions: We might merge soon and it should cause another \"Database startup error: Error: SQLITE_NOTADB: file is not a database\" error (which is really unfortunate but not easily avoidable).\nHeads-up: I've just merged to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup first in case the script fails unexpectedly.\nThank you, I just upgraded Signal on my computer and the re-encryption did work as intended"}
{"_id":"doc-en-nixpkgs-3175f034fa4c89202ca68f1b6a868cb38219da16cb930b3203ac54a1f8b8e9be","title":"","text":"With and , I still have to type my LUKS passphrase in qwerty. The logs say this: but not much else apparently. The vconsole is set up fine by the time I get a login prompt.\nDup of"}
{"_id":"doc-en-nixpkgs-a4fe6c22249cfb542793af24ce6d4e3bbf5832eaba41784380247365ce54cb01","title":"","text":"The option, which enables by default on high-resolution displays like my 4K laptop screen, is supposed to set the console font within the initrd before displaying the LUKS password prompt. However, with , this does not happen until stage 2, so the prompt is tiny. Enable , , and . The console font should be switched before the LUKS password prompt, not after.\nRelevant code is probably that it sets . should then properly set everything up if it can find its files in :\nDoes it work when you do ?\nNo, it can’t, because points to a font file that’s not present in the initrd.\nThis works though. It’s a little jarring in that the font is changed about a second before the framebuffer resolution is changed, so it’s temporarily huge. Ideally those would happen simultaneously. But at least they both happen in time for the LUKS prompt."}
{"_id":"doc-en-nixpkgs-29b367b6930ac438f385974e019914924836038c6782d4b997e87ef2505106ef","title":"","text":"The is from over 3 months ago. Some background info: Previously it was updated automatically by bot that runs . But the last builds have failed, e.g.:"}
{"_id":"doc-en-nixpkgs-2795165d691019f2668b70b6cb4d978ce697db03f10282914795e4497d6b18c8","title":"","text":"The emacs package fails to build against the poppler version introduced in . See upstream issue vedang/pdf-tools. Steps to reproduce the behavior: should build Build log: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nI'm seeing the same thing.\nSame for me\nHere's a work around:\nSince above PR is merged and pdf-tools builds on current HEAD, I will close this."}
{"_id":"doc-en-nixpkgs-275562f6627171f1286a2489da383d745a15bb245458ef9243e90f67435e5aa0","title":"","text":"Scream does not compile with jack support when it is explicitly enabled through an overlay. nixpkgs.overlays = [ (final: prev: { scream = { jackSupport = true; }; }) ]\nError message?\nThere is no error, it just skips compiling it. someone else ran it and i think they said that it skips compiling it with jack support because soxr is missing -- Checking for module 'jack' -- Found jack, version 1.9.19 -- Checking for module 'soxr' -- No package 'soxr' found\nSee . In the meantime, you can try: nixpkgs.overlays = [ (final: prev: { scream = ( { jackSupport = true; }).overrideAttrs (old: { buildInputs = old.buildInputs ++ [ ]; }); }) ]"}
{"_id":"doc-en-nixpkgs-548b45f559d6862e469dbd31c93cff3123eda1e1fb30d8190d341de5554eea90","title":"","text":"In the vault options, vaults can only be mounted as . Steps to reproduce the behavior: cryptomator to a vault options the tab, the combo box does not contain a FUSE item Vaults can be mounted as FUSE volumes In the console output, cryptomator seems to have access to the fuse3 libs in its PATH: Full console output:\nI think this might be related to It seems since they switched to the new fuse integration they only search a predefined number of paths. This is also consistent as the nix build of cryptomator works on non nixos linux.\nI have the same issue. Does somebody have some workaraound yet? EDIT: so what I am currently doing, which is really not ideal, is just mounting the webdav directory with rclone, which, well, uses FUSE. so yeah rclone has no problems with using FUSE...\nThe fix for this is merged but not yet released It's in the 4.0.0 milestone of fuse-nio-adapter. I'm currently using the flapak version of Cryptomator.\nthank you for the answer! i don't quite understand what is. Is it a dependency of ? Is there a way to manually fetch this so that it works? I'm gonna try the flatpak version of Cryptomator out, thanks for the hint. I actually tried out appimage, but that didn't change anything.\nIn the 1.11.0-beta2 release of cryptomator, vaults are able to be mounted as FUSE volumes. So once 1.11.0 is fully released (and the nixpkgs version updated), this issue should be fixed. Until the new version of cryptomator is released, you could create an overlay to use the beta version, like I am doing at the moment. Apart from changing the version and hashes, I also needed to change the jdk used to a jdk21 and overriding it to enable JavaFX:\nthank you for your response! i hope i am not rude to ask for your help in achieving this myself. i put the following in my : and i also did the overlay."}
{"_id":"doc-en-nixpkgs-44b531c1504dbe6d8257944dc094ed8051bc352403cacbe3c1505d95e308a826","title":"","text":"i get the following error when building: haven't been able to successfully find a solution via search engines...\nFor overlays, I simply copy the nix files and doing the following overlay: This is quite crude, and there is probably a better way to do it, but it at least avoids any weird errors like the one you are having."}
{"_id":"doc-en-nixpkgs-7e86f246376e53dd0fcf6726f39df4b95835396417c41eec1e6c1bf30effa0b1","title":"","text":"Hello, I recently submitted a pull request to update Tailscale in the NixOS repository (). After updating my laptop, I noticed that Tailscale has indeed been updated. However, upon checking the Tailscale dashboard, I discovered an issue with the displayed version number. Here's a screenshot that demonstrates the problem: ! It's possible that something has changed on Tailscale's end, which may require us to modify our build script accordingly. Unfortunately, I am not well-versed in Go yet and could use some assistance in resolving this issue. Any help or guidance would be greatly appreciated. Ping maintainers:"}
{"_id":"doc-en-nixpkgs-bad9210657d79fdc8308cbac4166169e7fadb70be6893796d6c52ec05e32bd51","title":"","text":"Steps to reproduce the behavior: stig I got this when switching from 23.05 to 23.11 system: host os: multi-user?: sandbox: version: channels(root): channels(ao): nixpkgs:\nThanks for the report, this is supposed to be fixed in . I will wait for Darwin CI to be green there and merge it. Ping me if I forget. Follow that PR at:\nGreat, thanks!"}
{"_id":"doc-en-nixpkgs-3da26f1d9e4e5f3c8f0168f35b9f12b423be788f7388a8df747ce899625f9b8c","title":"","text":"Steps to reproduce the behavior: spotdl I just tried to install it, doing it from or gives the same result. Let me know if I can provide more useful information."}
{"_id":"doc-en-nixpkgs-af13201e9c432c42c0ed93594c1f7dcc129086c77d907766511a719b1ceed63a","title":"","text":"nix fails to build libjack2 and libpulseaudio on darwin too (probably another two issues should be filed?). mpd build log is the third one. After disabling libjack2: After disabling libpulseaudio: I'm no expert in c++ but quick googling shows that exceptions are disabled by default when building with xcode toolchain. On a side note, which way is proper to manage ? I'm editing expression in but not sure if that is the right way. I'm using OS X 10.10.4, nix-env 1.9, nixpkgs from master HEAD.\nCompilation fails on throw from boost library and mpd sources are compiling with , so I've to mpd expression but still no luck here.\nSeems like this didn't get resolved and it's been a while... I have mpd failing to build on Darwin also, but with a different error, CoreAudio related. I'm using a local nixpkgs checked out at , OS X 10.11.3. Here's the failure:"}
{"_id":"doc-en-nixpkgs-7741aa2667b295fa03517329f8062a69693a4d80760643a9429ddd656c33e691","title":"","text":", CVSSv3=7.5 (nixos-20.03) Scanned versions: nixos-20.03: . Cc Cc\nFixed by"}
{"_id":"doc-en-nixpkgs-9cb6c18949279eb2f4a42fa262c941834b026d91ab75fc106aadec730ac8c998","title":"","text":"Package name: vorta Latest released version: 0.9.1 <!-- Search your package here: --- Current version on the unstable channel: 0.8.12 Current version on the stable/release channel: 0.8.12 <!-- 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-1f710ee83af855cea5d253c159eae0bc31762a83232842f1299c48b881464511","title":"","text":"Describe the bug flatpak-builder for some reasons can't use rofiles-fuse To Reproduce Steps to reproduce the behavior: build any app using flatpak-builder Expected behavior flatpak-builder should use rofiles-fuse. Screenshots Additional context Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(piotrek): nixpkgs: Maintainer information:\ninstalling solve this problem so maybe should be ?\nWe patch the paths to the executables to be hardcoded, so the program doesn't have to rely on something like ostree being installed. I believe one path isn't hardcoded with the current patch That looks it up in PATH, probably why it was working once you installed it.\ncc\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 .\nshould fix that issue."}
{"_id":"doc-en-nixpkgs-82903ca7bd306d5887b30fa100a7fb4a6cd3fdd2328506d4a2736b91f0e87f4a","title":"","text":"cudaPackages.cudagdb is broken for aarch64. Steps to reproduce the behavior: latest nix on system (e.g. Linux docker container on Apple Silicon Mac, Graviton instance on AWS, Nvidia Jetson device, Raspberry Pi) use , i.e. run command fails with Derivation success without an error. I also made an investigation and corresponding fix. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-01add96a9bf9b6c53882fdfdbaeef6889eafe5d36b5c616756593563df808231","title":"","text":"In current master branch pythonPackages.mysqlclient fails to build. Checkout nixpkgs on revision and run: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nMost likely caused by . Unfortunately, the config-tools are not very configuration friendly. Until is resolved, I would add to the package.\nUnfortunately this does not change anything, still failing with the same error message..\nHmm, apparently just hardcodes the path without the ability to override it from the attrset passed to : Is that intentional, Until this is resolved, you can use :"}
{"_id":"doc-en-nixpkgs-f61bf7bff175f27639ad6f7d3a7c588bc0ce18e5b742758de6bef5f2bad17805","title":"","text":"Steps to reproduce the behavior: Confirmed locally against recent master () system: host os: multi-user?: sandbox: version: nixpkgs:\nThere's already a PR fixing this build failure:\nlooks like this is being addressed in\nCan confirm, fixes build-issues on unstable :)\nFix has been merged. Feel free to reopen if the issue persists after the next channel bump"}
{"_id":"doc-en-nixpkgs-0d5c1d462872c62739e2c977e5586e8cff2a31031f2dbeeb4eb6a4156567af8e","title":"","text":"When setting a registerPassword for the public server list, it doesn't actually write it to the file, forcing me to hardcode it with extraConfig. Steps to reproduce the behavior: the registerPassword option; the system; the contents of . The registerPassword option should be written to It may be a problem with at line 36 where it has a double equals instead of a exclamation mark equals like the other parameters in that code block, although I'm not really sure. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nOof that's exactly right. It seems to have been by by"}
{"_id":"doc-en-nixpkgs-fbfd1fdb8c47d9295dca3dceb5c69a323bdfeba422a2fb191c2b2c4092cb3f94","title":"","text":"Steps to reproduce the behavior: distutils module was removed in python 3.12 <!-- 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-dfdd4e6dc4f346d9c80ff57330783a791c8a0b23eda563649c22171185c26c97","title":"","text":"Can't run insomnia in the latest . It works <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- I use flakes, but From\nHaving the same error\nI'm facing the same issue (gonna submit a PR to fix this), do you know when did this issue get introduced?\nNot at all, first time insomnia user, I had a bad timing"}
{"_id":"doc-en-nixpkgs-a05a2e78b0d3a427819a955020fe717f24d8c3983e0bebf5bd17e90e815d33a5","title":"","text":"The application fails to start with the following error: Steps to reproduce the behavior: to run the application The application should start and work properly.\nSame issue with  (\nI was looking at fractal-next as well, and found possibly related - [HELP] \"Failed to retrieve template child\" for Rust 1.67.0-nightly - Dec 4, 2022 - closed with Fixed in 0.5.3 a day later.\nAh, I see. There is a related PR for Amberol:\nWhat commit did you build from? I’d like to bisect\nMy first try of fractal-next was about a week ago and it was failing already. I've tried HEAD and branch () although I'm not entlrely sure is the correct way to refer to that branch.\nif you’re updating the version to point to an unreleased version the should\nIndeed, thanks. What I meant was that I'm not entirely sure that setting in to (via ) does indeed let me build from a branch. I could not find a definitive reference for that, but it seems to work. I've the rust backtrace to - Draft: general: Use AdwDualPaneView and AdwAdaptiveState_\nHi there :) This is an unfortunate gtk-rs bug, and there's nothing to do on the app side for this. In addition, draft MRs are not expected to be packaged. That MR in particular depends on unstable libadwaita features and unstable bindings.\nIs the gtk-rs package version something I can control? I was under the impression that this is managed in . I understand the branches/merge-requests I tried are not to be packaged. I'm merely trying to get fractal-next to run at all, as element is unusable on my phone.\nIn it is the minimum version we want to use. The pinned version (the one that is compiled) is in , and it is currently  on . This issue should have been fixed in . I don't know much about packaging for Nix but looking at the diff you posted , have you tried with the whole commit hash? Also don't you need to update the sha256 hash?\nWe’re not building from , we’re building from . I’m gonna check if we can just bump the version in to and leave it at that.\n(how naive of me."}
{"_id":"doc-en-nixpkgs-90863d56a5ba1ab71c80de12583909565229a67a8810da5a3474fc8e2bdec109","title":"","text":"maybe just building from is better)\nOpened a PR that should solve this, assuming it's accepted. In the meantime you can use it in an overlay if you want a fix now.\nYou were right - thanks for the hint! - I was indeed still building fractal-next from before the fix :disappointed:"}
{"_id":"doc-en-nixpkgs-9cb6dd832c51dee855382f84eef1db783514c715f1c1fc84daa1b78c497c9ab3","title":"","text":"Describe the bug Seems like some updates to pango broke a few packages Among the broken ones: ettercap (see ) pangox-compat (which anydesk needs) probably a few more To Reproduce Steps to reproduce the behavior: to build ettercap or anydesk from master will fail to build with some pango-related errors Expected behavior It should work Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata system: host os: multi-user?: sandbox: version: channels(maciej): nixpkgs: Maintainer information:\nAlso remmina is broken But doesn't seem to depend on pango directly, so unsure which dependency actually is broken\nHere's an issue for pangox-compat\nLutris is broken too - not an urgent requirement but just making you fine folks aware!\nNot sure why Lutris is broken, but Lutris-unwrap is fine.\nIt's a failure in the dependency chain, in this case .\nno longer depends on on its master branch: We should probably switch to that. should not be needed in according to the README in , I suspect it was only there because we did not propagate it until ebassi also suggests switching to HEAD and says we need not worry about ABI changes:\nNot having pangox_compat fixed is definitively still an issue. Can this be re-opened?\nAfter , the only program depending on this is anydesk and openmodelica which is broken.\nSo it breaks anydesk thus either we mark anydesk as broken or we fix that?\nAnydesk shouldn't use this deprecated library. Yes, we can mark it as broken."}
{"_id":"doc-en-nixpkgs-112fc7cbbba6e04d26d5c9717feef255f93511c4634f72e34bbdb74a127ded41","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: miller <!-- 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.10.3 desired version: 6.1.0 miller is now written in Go; there's still a configure script and a makefile, but I don't know if it's now more complicated to package because of fetching dependencies in a reproducible way or whatever. <!-- 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-eeb330d2df4b3889c916a04cb26d2f04903e74214edddbb09515e4da80c20be3","title":"","text":"Project description see Metadata homepage URL: source URL: license: unfree platforms: darwin, linux\nI was just checking myself and it's been there since November apparently\nAh, don't mind me, not checking the platforms..."}
{"_id":"doc-en-nixpkgs-c27e9aec7df39482b683200b125bfcdc64e0085d57fbbe43f6cce66acf3ad8de","title":"","text":"When I try to open a file dialog in Bitwig Studio 4.1.0 I am getting that error: I can manually start from command line and I'm seeing the file dialog and it returns the selected file. Unsure if this is of any use but is the decompiled class that calls . Steps to reproduce the behavior: bitwig (or open any other file dialog in bitwig) GTK file dialog opens Maintainer information: EDIT: more information\nI am not a maintainer of bitwig sudio. Just because I changed some lines does not make me knowledgeable about this issue.\nSorry for that. I just did what the bug report template told me:\nI played a little bit around with that problem. It seems to be connected to a change of to . further references: As a quick workaround you can launch the application with: is using an embedded version of java 16.\n/cc\nThe cause may be here: We must not wrap :\nTwo ways to fix: Fix the embedded JDK. Replace the embedded JDK with package.\nThanks for having a look into this. I guess we should fix the embedded JDK as it's the way how it is shipped and it should be a compatible version. I tried to add to which does not improve the situation.\nI tried to do the same thing and I noticed that the exact error message changed to: but I can still run . Not sure what that means. EDIT: I've found in another package that they do run patchelf on jspawnhelper. I've also this to the postFixup: and that made it work. Not sure if this is the most elegant way to do it but I can open a PR and we can discuss that there. Thanks :)"}
{"_id":"doc-en-nixpkgs-16a37da892febb33cb01308b3e2db17660648ea5e29ea2cf0c9234eda433720a","title":"","text":"introduced systemd syscall filtering which seems overly restrictive for common use cases. We use for coverage reports of our Rust projects which makes use of the ptrace(2) system call (denied by ). Android projects commonly rely on which uses chown(2) (denied by ). In my opinion, those use cases are too common and should work out of the box. Also, workflow failures are difficult to debug if syscall filtering (or any hardening) steps in. I'd suggest to revise the syscall filtering: Also, it might help with debugging or employing a custom hardening configuration if we add a module option which defaults to . Please run and paste the result.\nI agree that if the hardening make github-runner not to work as expected or as \"standard\" installation, we should remove them or make them optional with new option Do you want it to default to ? Maybe better with so it work as expected out of box?\nalso noted problems with makefile workflows in that I have been able to reproduce. I am sorry I did not catch this when making the changes originally. My usecase was running binaries on uncommon targets (e.g. ) connected over USB; and I only had light testing for other usecases. I have since a makefile test to the runner I use for testing package/module updates and will add a coverage workflow now too. I am ok with removing the harderning entirely, or making it more permissive. I only this because at the time I thought it would be a sane default for majority of applications. I would prefer we keep some hardening. Most people probably do not want a CI process to change the clock, hostname, or reboot the system entirely. I have been working on this in the background since reported issues; this is what I have come up with so far, I have not tested it with yet (will do that later this weekend); but it does allow and debug related tools such as to function. In addition to changes should also be changed to so that nix does not emit warnings when running.\n:+1: :+1: Yes, all this hardening is already available and entirely optional! Every user is free to add anything to that they want."}
{"_id":"doc-en-nixpkgs-ea57f52e5ff9162453829fbe5e83ce7125b2d754242478506b7557d86fd138fe","title":"","text":"I understand that NixOS developers are super keen on hardening, which is generally good, but for certain applications I just don't think it makes sense to go over the top... or even provide \"curated\" selections behind 'enableHardening' type flags. CI software is so broad I think we're providing more trouble and confusion than value here. My personal recommendation for this specific module is to follow what suggested as a reasonable default and let users decide any hardening they want for themselves. But I'm not the maintainer of this module in NixOS, just a user, so I defer to those who are volunteering their time to maintain this module :bowing_man:\nPR to fix is here: Mentions do not generate notifications, just making a comment so that anyone subscribed to this issue gets a notification."}
{"_id":"doc-en-nixpkgs-e1a39ff5408551eb3577f1d40d50daaf669e6ddbc44b19520624f63c058d3ae6","title":"","text":"low priority qt6.qtdeclarative is a large package, so it should be excluded for non-GUI qt apps () currently, when i build a package with and empty buildInputs, it pulls qt6.qtwayland qt6.qtdeclarative qt6.qtshadertools the problem is wrapQtAppsHook and its deps and qtwayland pulls qtdeclarative the problem is fixed by removing from deps wrapQtAppsHook should use only the declared buildInputs disabling wrapQtAppsHook (dontWrapQtApps = true) is no option, as also CLI qt apps need the qt wrapper qtwayland is there, so that users dont need to add it to buildInputs assuming that all qt apps are GUI apps im in favor of making this consistent with cmake so that all GUI apps must add qtwayland to buildInputs CLI qt app: GUI qt app: since cc\nI'm in favour of this change, but the proportion of qt cli app night be relatively small, and it's not immediately clear that qtwayland should be if the build log yields Qt6::Widgets is missing.\nActually we are abusing qtwayland as a shortcut to bringing in qtdeclarative, this should be fixed too.\nwe could patch the cmake message to \"please add qtdeclarative to your propagatedBuildInputs\" the alternative would be to add a flag, but thats more obscure than buildInputs\nAdding the lines to nixpkgs manual is sufficient.\nBy the way, is not only needed to pull in , but it's required for all GUI apps so that they work seamlessly on X11 or Wayland."}
{"_id":"doc-en-nixpkgs-04ff5a6b9de4e226b95a4b3bfa80f0851ed46120358a0280a2c168cfb259bc00","title":"","text":"Hi, I'm a Keybase developer and some of our users reported that the Nix packages were out of date. Keybase 4.1.0 was released a while ago, so I believe these need to be updated: Additionally, the KBFS nix should point to the new remote, with , and be on the same version as the other packages (4.1.0). Please let me know if you have any questions, happy to answer! Thanks. N/A N/A\nif the users are using the stable branch, then the update will need to be backported. Otherwise if they are unstable then it should be just a few short moments ;)\nKBFS has not been updated as directed here."}
{"_id":"doc-en-nixpkgs-8dbdd7d5ae26fbdb7091cc0b8ac649354ed2df588d596f0cc327572877616257","title":"","text":"Project description <!-- Describe the project a little: --An implementation of the Language Server Protocol for . Metadata homepage URL: source URL: license: mit platforms: unix Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: It has a pnpm lockfile for which we for yet, this package request should wait."}
{"_id":"doc-en-nixpkgs-874c0e23f9c5a91af2990b431f6eb267e2804076bfe7da0946db6e22e0b8e89a","title":"","text":"Build on () and when running I find the following in the runtime closure: pytest shouldn't be a runtime dependency Seems to be a regression, did not have this issue Might be able to bisect this one, but it'll take a while <!-- 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]:\nAfter bisecting, first bad commit is ("}
{"_id":"doc-en-nixpkgs-e7534e0064bb36e1b8ffceeef20a2ae70954c728ddf290165477c85b2f84900d","title":"","text":"System hangs during boot when the timer configured via fires during the boot sequence. option. option such that the timer will be due to run immediately upon the next reboot of the system. ; allow sufficient amount of time to pass. Boot the system, observe the system to hang during the boot sequence. system: host os: multi-user?: sandbox: version: channels(pbogdan): nixpkgs:\nDoes setting help?\nbut otherwise yes, it does help, thank you.\nHi, I reproduced this on 19.03 yesterday. The unit already contained , so it seems it is not sufficient to fix this. Some data about my system:"}
{"_id":"doc-en-nixpkgs-ae7cffe4a9406351b076b6162d01c2655d6c161433fa2602fd4b9042669937b3","title":"","text":"Package name: rnnoise Latest released version: 0.2 <!-- Search your package here: --- Current version on the unstable channel: 2021-01-22 Current version on the stable/release channel: 2021-01-22 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Tried building with but it got a missing file. There’s also warning about not using SSE3/AVX/AVX2, but Nix only supports the bottom of the barrel, common x86 instructions, but I usually compile this one out with some flags. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [^1] or offering a non-proprietary, non-US-corporate-controlled mirror for this free software project. I wish to delete this Microsoft account in the future, but I need more projects like this to support alternative methods to send patches & contribute.\nThe missing file is downloaded as part of the '' It looks like they a step to the build process.\nPerhaps it can be fetched using fetchurl/fetchpatch?\nYou're correct. The relevant file is retrieved in the script . It fetches a single file from the URL , where the version is extracted from the file , currently set to . Hence, we can emulate the download script and execute something similar to:\nAlternatively you could use instead of a separate model + . While we are at it, we should be using the main repository instead just Microsoft GitHub which is explicitly listed as a mirror, not the primary code forge. Something like Referencing both mirrors would be more resilient for when one of these platforms goes down.\nMade a PR , but still having trouble designing a ."}
{"_id":"doc-en-nixpkgs-3d1ad36d47f0db7b6c16186fdb40a59e7cb10f3f4890c7bbcbde4ce5a6cbbebe","title":"","text":"only returns the hostname, even when both and are set. Steps to reproduce the behavior: and . . should return the FQDN defined by and . The breakage happens when is used, which is now the default in NixOS after Stopping causes to return the correct value. reproduces the issue. It broke at , which is when became enabled by default. It's still broken on which is at time of writing. Possibly related issues:\nThis seems to happen because the resolution flow (when nscd is running) looks like: calls , which uses the nodename (), which is the short hostname then calls , which invokes the nss machinery gets the request and processes the request according to the NSS rules; on my NixOS system this is (from systemd) doesn't match (from systemd) does match, and returns a synthesized record; systemd internally determines the hostname for this using only the nodename, so unless the nodename is already the FQDN then we fail here, and it does this before checking /etc/hosts. I wonder if we can fix this by patching out the support in systemd-resolved for looking up the nodename, which will make it fall back to the result from /etc/hosts instead; on NixOS we can (probably) always assume that /etc/hosts will actually have the correct system hostname in it.\nNo, this is most likely We wanted to polish that PR in the next days, and once merged, bump our nixpkgs pin (and resurrect the upstreaming attempts). If you want, can you check if using nsncd from this PR fixes the problem for you?\nAh, actually, I think I'm just talking out of my ass. systemd-resolved seems to be able to cope with this properly when I query it over DNS, so it probably isn't to blame.\ntests fail at that PR. Setting gets a successful build, which then passes the test in , but it fails on the test.\nThis is a pretty weird behavior. What's (likely) failing here is the IPv6 resolution of . The test does pass on some NixOS setup, like my desktop (and the Ubuntu CI) but does fail on my laptop. I'm still not sure what's happening, is present in ."}
{"_id":"doc-en-nixpkgs-92ea1e6729ab8faca7224af21f75c1b8d200b5906fc4e070b48ea08a905c154d","title":"","text":"There's something wrong with some NixOS setup, it'd be nice to fix that as well. By any chance, did you disable systemd-resolved? Thanks for the heads up wrt. . I'll have a look today.\nThe behavior I described is from the Nix build environment. I used the nixpkgs derivation for nsncd and updated the source to the PR."}
{"_id":"doc-en-nixpkgs-32ce634507ace1521de9a77f127ef1de6b1579a1b0c8753c11aa882427f00770","title":"","text":"In NixOS 22.05, the domain name is not set correctly when is set to . 1) It's working with IPv6: 2) .. but broken without: Obviously, it should work in both cases. The issue seems to be related to : also fixes the problem. Similar issues seem to have been discussed in , and , but it's still broken. Please run and paste the result.\nI also seem to have hit this, but do not run , but a customized . I have however not tested removing , as my servers rely on the configuration section to run. Have a feeling it may be a fragile section when changes in happens. Also stopping solves it as well. Running nixos unstable.\nI can reproduce this on nixos-unstable (without disabling IPv6), but also managed to get it working when stopping nscd. I found while googling around. And while points out a possible solution[^1], I did not find this to be working for me. [^1]: Effectively translating to\nI've also encountered this issue, with the same reproduction and issues as Any idea how to resolve this? I particularly need to be able to set for containers using ...\nFWIW, setting to seems to resolve this issue. cc\nHmm, this doesn't make too much sense - I'd assume and should behave the same when it comes to that. They're simply calling out to the same NSS modules to do the work. We do have which tests that works. It currently seems to be failing in the testcase, when run with nsncd, and succeeds when setting to . - cc Let's figure out this regression first, and not draw too early conclusions about this being a \"IPv6 is disabled issue\".\nSo, there's definitely something wrong with the current nsncd implementation. Dumping the Nscd socket, we can see that nsncd is lacking some getai entries. Entries that are probably used by hostname to get the FQDN: Let's track and fix this issue on the Nsncd repo."}
{"_id":"doc-en-nixpkgs-32dcf88ef15bde4b6d48718b1c6789cbbcb131cd60d0f5585ab8be4021077d20","title":"","text":"Project description EveBox is a Suricata alert and event management tool for the Suricata IDS/NSM Engine. 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-4ea5a4f3d3a80ed5fbb8f90080194f27d396beb1485adf5b48abc7972658f8d2","title":"","text":"Project description A terminal based slideshow tool. Metadata homepage URL: source URL: license: bsd 2 clause platforms: unix, linux CC:\n- You can follow the status of the pr/package .\nPlease include presenterm-export as well, or a new presenterm-export package"}
{"_id":"doc-en-nixpkgs-8adbd0ab0019aa839ffea8b1372a02c1e107284b1b6003c135b3ccf068aac836","title":"","text":"Steps to reproduce the behavior: build .#fdroidserver Git bisect predictably found the culprit as , so it is related to the Python 3.12 upgrade. I suspect that all setuptools-based modules are broken; e.g. also stops building. Interestingly, built before, but not after. Not sure what that implies. (Originally I had notified the Python team, but I removed them from this list because I am suspecting this regression may not be the result of any problem with the version flip itself, but the broken packages instead. Sorry.) Notifying from fdroidserver maintainers. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-94243185e7fc919dfc105113432ac9435f92caf03548388355baa42a0c2c6579","title":"","text":"Version 1.8.0 is available and . It looks like this should be a trivial bump in the luarocks csv. <!-- 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.7.0-2 desired version: 1.8.0-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.\nWanna take a stab at it then ? we can help you through the process"}
{"_id":"doc-en-nixpkgs-9ba11d153c6c5c0ec370c0d64f6e02dd1dd390ff57b55528b25209714e4eb8c5","title":"","text":"When defining the desktop shortcut that gets installed globally doesn't point to the correct executable. The executable that it points to is the one of the non-wrapped package, causing any plugins that are installed to fail to load. Steps to reproduce the behavior: the following in a launching the application from your desktop menu/launcher the command pallete inside of the program in - THIS fails HOWEVER, if we launch octave from the commandline instead by issuing the command, everything works as it should. When you launch octaveFull from the desktop menu it should behave the same as if it was launched from the commandline. When launched from the OS desktop menu. ! When launched from the command-line ! Inside of your octave-env derivation that's generated when you do a system rebuild, theres a file located, there you'd be able to see that the wrong executable path is used for it. Please fix this. <!-- 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 report! Indeed we never thought about this detail. I pushed a fix in . Here's how I tested it: And note how the paths in the line above is the same as the path to the wrapping derivation (from ). I also checked with that I can in the GUI. Your approval on will be welcomed.\nWill take a while to build as I don't use unstable, there's a ton of dependencies"}
{"_id":"doc-en-nixpkgs-a418da652f340f0488fc6516505e726a3e64b40b712ac9ad551cf4288b717945","title":"","text":"Describe the bug I have configured the new ACME module (from 20.03) and after a rebuild nothing happened. I expected to have a certificate or a (failed) certificate request, but neither of these happened. Apparently I have to wait four days until my certificates would automatically appear, that is a bit long. To Reproduce Steps to reproduce the behavior: a certificate through certificate request doesn't happen before the systemd-timer is due Expected behavior I should have a certificate as soon as possible. Metadata Maintainer information:\npresumably you have a service which requires this certificate. You should make that service require your certificate service. Both and services do this with their options and could demonstrate for you how to do this. If any part of what I said isn't clear, or any part of the code please do not hesitate to ask for details.\nGot it, I can make that work. But is that really the intended behaviour?\nWould you want each certificate to renew each and every time you rebuilt your system? That sounds like much more of a problem. You could always manually execute the certificate service any time you want, but the intention is that you utilize systemd and make services depend on other services. Why provision a certificate unless you need it. If you need it, declare it so and it will be provisioned.\nIt wouldn't renew on every rebuild: Starting the renew service doesn't do anything if no renew is needed. I think having the certificate be created when a rebuild is done sounds reasonable. I think it might simply be a matter of adding to the acme services.\nThat and also making sure on boot that the certificate is in order is also a good practice.\nthanks for clarifying that. I think I was mistaking the implementation which did attempt to renew every time it was called, if I recall correctly :thinking:"}
{"_id":"doc-en-nixpkgs-be836afc40587243a21508678d4064bcf9ed0a866f64c283b18fb5b6f1596a50","title":"","text":"remarkable-mouse doesn't work for me, exiting with the following traceback: Digging through github issues led me to , and the following traceback: I guess this is a problem with screeninfo's packaging, but I'm unsure what exactly the issue is, or how to fix it; maybe related to ? screeninfo (and, by extension, remarkable-mouse) should work. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nAs far as I know there is no infrastructure in place that lets (in ) work correctly, since it has no knowledge about the Nix store or the buildInputs of screeninfo. There used to be a call which replaced all findlibrary calls with store paths, but it was removed in I think the two load_library related substitutions need to be back in (compare with , which contains comparable code).\nReplacing calls seems sensible, I will try to make a PR. A workaround for now (e.g. for remarkable-mouse users) is to set $LDLIBRARY_PATH to , but that probably isn't usable within the library itself."}
{"_id":"doc-en-nixpkgs-81358e1f03a5f1d4a89e32ba3a241f849504cfd788005428dd7d96bf62dea78a","title":"","text":"waveterm Modern open-source terminal emulator supporting inline rendering. homepage URL: source URL: license: Apache-2.0 platforms: linux, darwin\nI've tried, got stuck at packaging waveterm with scripthaus. However i have packaged scripthaus which is required here. Maybe someone with better understanding of nodejs will make it.\nHere's my attempt at cobbling something together for linux, which seems to be working locally for me (well, it's \"working\" in the sense that it builds, the GUI shows up and the basic shell features seem to be working): I wasn't able to get it building using the provided scripthaus scripts yet, but I'm also quite inexperienced in this area so that could be why. I'm currently using and instead, basing it off from a bunch of other electron and go packages on nixpkgs. I haven't carried across all the build flags from waveterm's provided scripthaus scripts though, and you might also see some vestigial code that I copied from other packages that don't apply for waveterm which I haven't cleaned up yet. If I have time I might give the scripthaus scripts another try. Some other remaining todos that I'm aware of include the desktop icon, getting it working on darwin, checking the AI features, checking that the package includes all the dependencies it needs at runtime, and fixing a failing test regarding command completions. Please feel free to continue working off from what I have if it helps, especially if I don't get back to this soon.\nWaveterm offers a packages. I was installing and noticed that it fetched a package and installed it. Is it not possible to do the same? I also saw in this that packages are pulled for Opera and Skype as well. So, is it possible to do the same for Waveterm as well?\nForced M1 user here, tried packaging wave but didn't manage to make the scripthaus scripts run without fails, mainly because both go and scripthaus try to create cache directories and I didn't manage to disable this behaviour."}
{"_id":"doc-en-nixpkgs-5d02e3e9626ae326dd3ecfa4d4d65ed1f2245bf064359f1b3d25ef1f24e82a00","title":"","text":"I also tried to use package but due to it requiring electron and it not being available for the M1 architecture I couldn't compile the application from source, so I think packaging for the M1 will have to be done through the .dmg that they have on the realeases page. I'll try packaging the application when I have time this weekend.\nIn the end I couldn't resist and worked something out for M1 in my free time, this works and creates a ./result directory with an application I can open, so I think it's pretty much done. The only thing missing is integrating with solution... I'll try doing it this weekend.\nwhere did you get that info from?\nWhen I searched for electron on Nix packages it never appeared a platform for darwin... I know it should be possible to have electron in M1 but at least on Nix it isn't packaged for it already. <img width=\"313\" alt=\"image\" src=\"\"\nOh, nice! I thought the panel with platforms displayed all of them, clearly it doesn't. I'll first merge the linux build mentioned previously and then I'll try using that electron to build the app from scratch. Thank you!"}
{"_id":"doc-en-nixpkgs-caf4fdd7066e5309fe262dca1f0acc175af38e819db32d15a45147e9f00c01f2","title":"","text":"I enabled the following chromium enterprise policy: This created a .desktop file in But the command crashes, because it tries to start the unwrapped binary directly from the nix store. We should try to point Exec at just so the wrapper from PATH is used.\nCC\nNot sure what's happening here. On my system it seems to be fine:\nPlease read the description again, specifically I am talking about the .desktop files created by chromium, at runtime.\nOk, I was assuming NixOS put it there. Chromium creating files at runtime sucks... (unfortunately it's not even surprising :o)\nsetting the env var in the wrapper script may help ;drc=;l=405\nI marked this as stale due to inactivity. &rarr;\n(as already mentioned) would probably work for Chromium too. Just in case someone's still interested and has time and motivation to test it and submit a PR ;)\nThis is not exactly a NixOS caused issue. As chrome creates the shortcut wherever the binary is currently installed, and there is no nice way (other than patching chrome) to solve this. While discussion of patching chromium to always point to relative chrome i cant say much about. To get this working today, you need to edit each desktop file manually from to its relative name . and use at the top of the file. While this adds a minor security issue due to executable being relative and not absolute, it seems like the simplest solution for now. There is also this flake that will run a service in the background to do this editing automatically for you: Hope this helps! :D"}
{"_id":"doc-en-nixpkgs-17c59a2fa4f6dd485e5ed880dd95090d59c1486c0ee00cf726d7db405d7d19e8","title":"","text":"We need to standardize and document this. The current contents in nixpkgs manual seems obsolete (section 4.2). I suggest at least these should be standardized: preference for usage of <codelib.licenses.*</codeinstead of the choice from some strings, meta.licenses semantics (any license at your choice, or different parts under different licenses?).\n:+1:\nI'd go for a documentation changes with pull request and point people to read that.\nIs someone working on this? Would be good to get into (which also will presumably have with its new way of handling attributes)\nFirst bullet is addressed in . For more complicated cases when it's not all one single license, I don't know how deep should we go. Choice from multiple licenses is probably the most common and using nix lists for that is suggestive, but it occasionally happens that multiple licenses need to be complied to at once (different files/parts under different licenses) or even more complex combinations. I don't see any possibility of \"smooth extension\" in such directions.\nSolutions I encountered: Debian has per-file license granularity , and offers some RDF-based solution.\nwhat's missing here?\nI see the first bullet was fixed in . Attribute is still unspecified, but IMHO describing the licensing precisely in all cases is out of the scope of nixpkgs.\nBTW, thanks for the notification. I forget to pass through old open issues."}
{"_id":"doc-en-nixpkgs-cdff7172ba387c8b1576ac17a45cd353e33b11eecdf6541f3e190e16be8f3da6","title":"","text":"Describe the bug libbladeRF fails to build on the nixos-unstable channel and latest master: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nCannot reproduce this in master. I am on . Was this fixed in ?\nI have just tried on , here is a full log:\nCan also confirm that the build fails on .\nThis appears to me a genuine error in the source. Live bladerf1.c:841 (and also bladerf2.c:283) reference , but it should be . With , we stop the build on purpose. Luckily the typo is not of further consequence, since both values are numerically the same (both zero). I will try to report this to upstream.\nOh nice, this has already been fixed in upstream master (in from last May to be precise), but there isn't yet a new release containing a fix. I'll prepare a pull request cherrypicking this patch. Be aware though that I cannot test libbladeRF (in fact I don't even know what it is about :-)).\nmaybe also add . This options is meant for development where there is control over the compiler, but in nixpkgs we want to update gcc without breaking half the packages due to warnings.\nI see, thank you for the suggestion! Generally I'm in favor of , but your argument is quite reasonable. I'll force-push in a second."}
{"_id":"doc-en-nixpkgs-1fba775f69136d3801eef1f476cf8fb9f62f65e4217c17ac787985f8f6851b27","title":"","text":"After installing a fresh system with the following configuration: the file is not created, hence wpasupplicant fails to start with the following error: nixpkgs\nI don't know the logic of , but I think you're supposed to provide the file yourself. I guess it could be ed if wpa_supplicant fails without one.\nYou can do\nThat probably wouldn't work due to permissions. EDIT: wpa_supplicant is still running as root, so it should work.\nFixed in"}
{"_id":"doc-en-nixpkgs-f0c14d60e8d754c86309beb8706fd746c15c5400297a3a01b14aca1dd436d60d","title":"","text":"When I try and install the package it fails because the installation procedure iterates over all the test-short executable's dependencies and is unable to locate the required It seems this dependency comes from the test-short binary being linked against the that comes with . This has a record that says it is This results in test-short requiring the library The only provides a though, so the installation then explodes when it tries to loop over the dependencies of the binary it just created and finds it can't find It is not clear to me if this would be considered an issue with or . Two possibly fixes are to for before , or a step to to provide the symlink. Try and install package System: Nix version: Nixpkgs version: Sandboxing enabled:\nI decided to give the latest unstable a try as well. It dies during the as it cannot find at all anymore. Looking through the source it looks like the recent commit stripped out all together. I guess that makes (1) above the correct solution.\nforgot to CC relevant people on this issue with (should be an easy fix -- just add to the )"}
{"_id":"doc-en-nixpkgs-31699079a7e4cf88355acfc36bb71c1436fc8ff7b3381803805f7f3dcfe9910c","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: minio <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 2022-05-08 desired version: 2022-07-15 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-3de6ed76ce200dc59818ad4dfd304cd5fdafe4fd3dcef5bb41c0bbba13472a1e","title":"","text":"When flexget starts up, it crashes with this error: . The version of transmission-rpc in nixpkgs is currently 7.x.x. Steps to reproduce the behavior: a flexget config that uses transmission. . Flexget runs normally. (transmission-rpc) (flexget) Please run and paste the result.\nUpstream flexget has some discussion about upgrading to transmission-rpc v7:\nWorkaround: the last transmission-rpc 4 version in nixpkgs to transmission-rpc-4.nix: it to an overlay"}
{"_id":"doc-en-nixpkgs-e0b7bd5436772ed9c8f9da1cba27c7b5049f3f3a4b50d0200ac189f99c4c7c74","title":"","text":"Package name: rgbds Latest released version: 0.7.0 <!-- Search your package here: --- Current version on the unstable channel: 0.6.1 Current version on the stable/release channel: 0.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]:"}
{"_id":"doc-en-nixpkgs-faba3b0de3e61a459ed2d93ad1cfc38f9c5b2cc3c78551bbaa1f77e665aedf6c","title":"","text":"I ran gimp from terminal and noticed that it prints out following warnings: I don't see anything clearly broken in the UI, but just thought that probably this is some issue that could be fixed. Run Gimp from a terminal. Please run and paste the results.\nOh, and in case it makes a difference, I'm not running GNOME but i3+none.\nTry installing , GTK 2 is weird.\nThanks for the suggestion. I still get the warnings: I also noticed it warns about interpreters. Maybe those should be fixed too? I have some issues with one plugin, not sure if that interpreter issue is related to that.\nYeah, you would need to install it globally, so that GTK can find it under . Alternately, adding it to env var should also work.\nThanks, that fixed the theme issue! So maybe that should be as a propagated build input for gimp? The interpreter warnings are still there. Should I open another issue for those?\nPropagating will not do anything. You would need to add it to the wrapper is citrix does.\nYeah, please open a new issue for the interpreters.\nThanks! I made a pull request. Seems to fix the issue."}
{"_id":"doc-en-nixpkgs-8e7750c6e51e96c62f88d37dd3ab2df7ceb11ea7beed35d0274b23225fe836d8","title":"","text":"The NixOS manual's section on Emacs has a . It states which is at the very least misleading and potentially confusing since the docbook migration. Either remove these references to the manual being in docbook, or remove the section in its entirety, since (with the completion of the docbook migration) it seems unclear what relevance xml editing in emacs has to NixOS at all, and people interested in the topic will presumably look to other resources elsewhere (e.g. ). (I'd open a PR for either, but am unsure which one to prefer, hence this issue) <!-- 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]:"}
{"_id":"doc-en-nixpkgs-87a800e2b00a4d85277983b41696b2b0b13d620cdb564fe79a5ab633cc1abd78","title":"","text":"Package name: Latest released version: 5.2.0 Current version on the unstable channel: 5.2.0 Current version on the stable/release channel: 5.2.0 Notify maintainers Note for maintainers: Please tag this issue in your PR.\nPending on"}
{"_id":"doc-en-nixpkgs-dc96d10512b08334efa526464e3de342d5d64eef0a4e3598c615e0189b9baa29","title":"","text":"The latest heisenbridge version doesn't build on nixpkgs-unstable (). Steps to reproduce the behavior: error: This repro's on darwin and on linux, using this nixpkgs revision. I believe this may be due to , where mautrix was bumped to version 0.11.3, but heisenbridge requires 0.10.x. build success. Please run and paste the result. Maintainer information:\nThe requirement is adjusted in heisenbridge 1.7.0:"}
{"_id":"doc-en-nixpkgs-df14a15b16368641eed16ec3ddca0fdba7989ffffc9f5efac6ad3143347daf6b","title":"","text":"I noticed my locatedb hasn't been updated in ~34 days. The is failing. Here's the full output: And for some reason, some of the log lines are missing from that, so here's the systemctl status output for that service: Relevant lines:\nI can't find any trace of (with a ), at least on master and the latest unstable channel. What service do you mean?\nArgh, sorry, I read it (notice ). Sorry, sleepy.\nhas problems on my unstable NixOS system too:\nI confirm the problem\nI have the same problem and see this in systemd's journal: The systemd service seems to have been defined like this: So it seems that is not being correctly specified.\nThis is what I wanted to write: However, this is still not fixed: returns (after a call to (which has exit status 0)) So, this is not fixed in 16.03. Please reopen. If is not meant to be callable as root, then should be a wrapper of some kind which would say However, I think pretty much anyone with some Linux experience wants to be able to easily build a new index when they want and has historically been the UI/API to do that. Changing that, if that was the intention, is a rather ill-conceived idea.\nSo, is this supposed to be working? I am still getting the same error.\nThis issue was about the systemd service failing with a / , it wasn't about not being able to find the file, even after running manually (I would file a separate issue for that). is the error you are still getting the failure in the systemd service? If so, which release / branch / channel are you running?\nI still get the same error \"read-only filesystem.\" I suspect this is because the only service I have running that wants to create /var/cache is the one for updatedb, which still doesn't have write permissions to /var to do so. Manually creating /var/cache as root fixes the problem.\nJust installed nixos. I to get this errror. Is there any fix for this.?"}
{"_id":"doc-en-nixpkgs-1b48bb20463c78e5892bd1802e47c0a53eb33d62638eb4aa086ab78ef11a4b44","title":"","text":"Same here on a fresh install as root: nixos /nix/store/w1gzi0342kiha08pym7qj09w09ffzhj4-findutils-4.6.0/bin/updatedb: line 323: /nix/store/w1gzi0342kiha08pym7qj09w09ffzhj4-findutils-4.6.0/var/locatedb.n: Read-only file system\njust installed 16.09 and I'm getting the same, Read-only file system on updatedb\nVERSION=\"16.09.1836. (Flounder)\" nix-env (Nix) 1.11.7 works fine if updatedb is used with --output and later locate is used with --database when invoked by root in a login shell, updatedb tries to write to: /nix/store/95vfigaqdg8jg5bk961k1x06j86p5fh0-findutils-4.6.0/var/locatedb.n: Read-only file system when invoked by user in a login shell, updatedb tries to write to: /nix/store/95vfigaqdg8jg5bk961k1x06j86p5fh0-findutils-4.6.0/var/locatedb.n: Read-only file system this path comes from updatedb shell script which was modified in nix (this line is different in the gnu sources): 186: ${LOCATE_DB=/nix/store/95vfigaqdg8jg5bk961k1x06j86p5fh0-findutils-4.6.0/var/locatedb} systemd service seems to be updating the db: but doesn't have access to some dirs: I'm not surprised it doesn't have access to home, but shouldn't the service be able to list /nix/store files? There are no error messages for /nix/store: the ticket is about service failing to write to /var/cache/locatedb, but it works fine on 16.09, so I think it can be closed."}
{"_id":"doc-en-nixpkgs-396bbb5223746fd291e1e902c5dc4a9288a0dbd9726929b6b64afd405606ab6d","title":"","text":"I see two other problems though: update-locatedb service not being able to process /nix/store running updatedb on the cli tries to write to /nix/store which is a read-only file system\nis caused by an option, now named , which contains \"/nix/store\" by default, the issue is closed already. is resolved by merged , the issue can be closed. is about using updatedb from cli and missing /var/cache directory and needs a decision."}
{"_id":"doc-en-nixpkgs-9569e073a129a4fbc05ad8656f3778566be3ed41a9449030fbc75424a1a7fa61","title":"","text":"The v8 derivation used by plv8 fails to link: cc Using . Hydra job: Maintainer information:\nAccording to it should be fixed by ;a=commit;h=."}
{"_id":"doc-en-nixpkgs-9698ed08419be90805c639bfbd28c812802285e4c9f050b57260e454268bf590","title":"","text":"When booting up SABnzbd having done an update recently (5min ago at time of writing), I'm getting the following errors: ! Steps to reproduce the behavior: your on NixOS using current unstable, include the following: . I expected it to pick up SABCtools 7.1.2, but it got 7.0.2 instead. See above N/a\nOpened a PR to fix this and provide better testing.\n:+1: thanks"}
{"_id":"doc-en-nixpkgs-332c14ddea0aa772bf263d5c32ffa64d76e711ecc27c93d6ef465e49564c09fa","title":"","text":"Project description It's a new version of Grafana Agent in Flow mode, but based on the OpenTelemetry Collector instead of the custom internals it was previously built on. Metadata homepage URL: source URL: license: Apache 2.0 platforms: linux and darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-35cc658830e11a9ea0a845efa1a1705e232f94d80f1ef924aec465065082370b","title":"","text":"GitLab service do not start with configuration . TLDR should be used instead of when creating config file. There is an error message in the log: To Reproduce Steps to reproduce the behavior: to Expected behavior GitLab service should be running after switching to new configuration. Additional context The file mentioned in the error: Note the missing value for . The problem seems to be at , generates empty string: Notify maintainers Metadata Maintainer information:\nThank you for reporting this! I've fixed this on master and will backport the fix to 20.03 and 19.09."}
{"_id":"doc-en-nixpkgs-c2d04f803692d38e20574189c2ff21d4fa99472b8290ef33634a6979feace2e7","title":"","text":"Package name: raysession Latest released version: 0.14.2 Current version on the unstable channel: 0.13.1 Current version on the stable/release channel: 0.13.1 Notify maintainers Note for maintainers: Please tag this issue in your PR.\nUpdate PR:"}
{"_id":"doc-en-nixpkgs-e354f734d96caad30bc25fcef8199c136aa410f851bdf5eb8a28e0570941a1b9","title":"","text":"When \"set as default browser\" is clicked from within Firefox, it places a custom .desktop file in , and points to this from in the same directory. This file launches Firefox without the wrapper when it's opened using xdg-open. The result is that if xdg-open is used when no Firefox window exists, it will be opened without environment variables set correctly, and without plugins.\nThis is a great example why wrappers are error prone.\nIs there a easy way to fix this? I don't see one\nThe easy way is to use a non-absolute path in the .desktop file, i.e. . This also ensures that after an upgrade, the new Firefox will be invoked.\nThis .desktop file is generated by Firefox when \"set as default browser\" is clicked - it's not one of nixpkgs's .desktop files. That'd involve a patch (which would have to be kept up to date with each Firefox release).\nRight, shouldn't be hard to do.\nTesting a patch now...\nI can't see the patch anywhere -- did it work?\nChromium .desktop file includes and suffers from the same problem.\nThis is handled and detected with mimetypes.\nWould be really nice to fix this one, any takers?\nI think I have solved it for Firefox; as for Chromium — apparently it is non-trivial to test for me (StumpWM, not a DE)\nThere's still no obvious way to set the default browser that I can find - anyone know what the status is here?\nA possibly reasonable option in the case of Firefox would be to disable the default browser check using the preferences file, and write a custom dialog for selecting the default browser in the wrapper itself, a very rough basis being: According to a google, similar should work for Chrome/Chromium, except passing instead of messing with config files. Opinions?\nIs there no way to trick firefox into thinking its executable name is the wrapper ?\nYes: but this needs some testing, and it affects many browsers.\nI fixed the wrapper to work with (), but we get another issue. When we update firefox, we end up with a different /nix path, which firefox considers as a different browser. If you restart firefox (for example when installing addons) then you get the not-your-default-browser\" warning. Investaigating MOZAPPLAUNCHER as solution, but I start to think that may be the most general solution."}
{"_id":"doc-en-nixpkgs-8c676d772c9487ac7ce2521e3455a32cc34f258419e118caf7a6232d27416167","title":"","text":"Package name: senpai Latest released version: 0.3.0 <!-- Search your package here: --- Current version on the unstable channel: 0.2.0 Current version on the stable/release channel: 0.2.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. Has new maintainer There are issues where the pulled dependencies don’t work with the 1.16 specified version. + (as well as 19) created a new batch of errors I decided to give up on. I did ask about in on their SourceHut issue tracker: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8075cf188a4a1958efe022bfab9ac82de8627d7e25f2f30be1b891685682a68e","title":"","text":"The package has been . Trying to install results in the following error: Why was the package marked as broken? Is there a way to help fix it? System: Nix version: Nixpkgs version:\nAccording to the project homepage it requires a different version of the vte library: If you package this one and add it as a dependency the package should work again.\nThanks for the response . Could you help understand the reasoning behind the commit that marked it as broken? Was the problem that was being packaged with the wrong dependency?\nThe dependency it needs is not in NixPkgs, so it has to be packaged and nobody cared enough to do it.\nWe had the patched vte under gnome-3.20, but 3.20 was now removed whole without porting that to the vte in 3.22. EDIT: refs and .\nI've wasted hours trying to fix building the special vte library, you may try to continue: This fails with: I don't see marking one package broken preferable to keeping the whole gnome-3.20 in tree, sadly. Please open a pull request if you manage to succeed, but I don't see myself wasting more time on this otherwise soon.\nI fixed the errors you found during compilation and submitted a PR to upstream VTE. As the changes may take a while to propagate down into vte-ng, I them as patches to the vte-ng package, which is now used to compile termite."}
{"_id":"doc-en-nixpkgs-7dda5702282a3f4be32837958c0cf40806962a392317a8fd455d8eab65a65ab1","title":"","text":"Package name: feishin Latest released version: 0.7.1 <!-- Search your package here: --- Current version on the unstable channel: 0.6.1 Current version on the stable/release channel: 0.5.1 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nthanks for reporting this, just noticed I hadn't subscribed to release notifications. Shouldn't miss any from now on :) Fixed by (awaiting review)."}
{"_id":"doc-en-nixpkgs-6114ffe22cbcc4f2e6dfd32cc1825d2af1f25b4fb1f53e266fd9086563cbdfe2","title":"","text":"Project description A markdown-like text editor designed for writing novels and larger projects of many smaller plain text documents. Metadata homepage URL: source URL: license: gpl3 platforms: linux, win, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-3aaa4d17fcbe48932f906f5fd5818bf1c7ab2b9cd8fcc3e015e10a2f5dbaf28e","title":"","text":"Describe the bug nix-gitignore lets the hash of the source change when some file changes in .git (notably .git/FETCHHEAD) To Reproduce Steps to reproduce the behavior: a git repo in a as follows: Expected behavior Hash does not change Additional context I intend to open a PR to fix this soon Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(symphorien): channels(foo): nixpkgs: Maintainer information:"}
{"_id":"doc-en-nixpkgs-e32d6b6e9e554f44ad42efb2bf424b2922793bccbed6660195842dca6290b077","title":"","text":"Package name: blesh Latest released version: unstable-2022-07-29 <!-- Search your package here: --- Current version on the unstable channel: unstable-2022-07-29 Current version on the stable/release channel: unstable-2022-07-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! --- 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-24f39b0d9498ef72ecb82cc74825fce7c2214e8eeb6167519d064017047aaf8d","title":"","text":"While going through the documentation I came about a that explicitly requires matplotlib with the TkAgg backend. I tried to generate a nix-shell with matplotlib and tcl/tk and tkinter. However, the script does not execute and instead I get the following error message: In a simplified form: Start nix-shell:Start Python:Try to import matplotlib, configure the backend, and import parts of Tk:Observe the following error message:System: NixPkgs on openSuse 13.2 (Harlequin) (x86_64) Nix version: nix-env (Nix) 1.10 Nixpkgs version: \"16.09pre83147.\" Matplotlib Maintainer:\nJudging from the matplotlib expression we don't build against tcl/tk.\nI made an attempt to build matplotlib against tcl/tk with the following patch: Unfortunately, compilation fails with the following error message: The linker cannot find the tcl/tk libraries. The linker flags are quite off: They include and the like. This must be due to matplotlib's own build script, as no such flags are set in my bash environment and is executed with the flag anyway."}
{"_id":"doc-en-nixpkgs-0c718a5da9e090710d017db901c112f1469de4eb501c4327652bcf5981271b1b","title":"","text":"CoolerControl does not detect Nvidia GPU when enabled via options Steps to reproduce the behavior: GPU with proprietary drivers (version 555, but might not matter) spits out error about missing and CoolerControl to detect Nvidia GPU ! Logging output: If I manually stop the systemd process and start it detects the requested binaries correctly, which makes me think that the coolercontrold binary just doesn't search the correct paths. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThe tools should be on PATH if you check the generated service file. And restarting the daemon would support that I think, since it shouldn't pick up any new paths from the env AFAIU. So might not like whatever state your system is in whenever first launches? I sadly don't have any nvidia system to test this with… I think if you try something like this you could delay the service startup to check if the above guess is correct? (Or override the package with an overlay and patch it into the service that way if this doesn't work the way I think it does)\nRestarting the service does not work, as that throws out the same identical error. After adding that to my config, rebuilding and restarting the service, I get this output: which looks like sleep succeeded, but not sure how that would help so I did this instead: Which I either did wrong, but it seems to print the GPU fine? But that made me realize one difference. I am on beta drivers, but as per your code block, you pull in the stable ones... Could that be the distinguishing factor? In which case, maybe it might be better if it pulled in the field rather than hardcode to stable drivers?\nOh sorry, I thought that read \"restart coolercontrold\". Maybe. Likely."}
{"_id":"doc-en-nixpkgs-43ddc15c8b17001b899c5a58ca2af8664a065b36ccbf00f4d376e5943d8b4eb7","title":"","text":"Steps to reproduce the behavior: tarsnapper on nixos-24.05 @ system: host os: multi-user?: sandbox: version: channels(root): channels(asymmetric): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-8471c3fa654179999dbd734de64966ceb98f9c8cc3f4399bf30989868a99d5a2","title":"","text":"Build . Because this hash was updated not long ago by , I think the package may still need some refactor? We may also expect to get everything settled. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nHuh, weird. When I wrote that hash worked fine. I wonder what changed?\nYes I was wondering about the same thing because I knew you updated that hash not long ago. Does that hash depend on any online resources that may change or on other packages? If not, then this package may have some obscure reproducibility issues. This package is so complex that I cannot see what it is doing there at glances.\nYes, but it is my understanding that its pulling resources that are hash-fixed in bazel-land, so iiuc they shouldn't change unless changes... but then again clearly i have some misunderstanding of the behavior here\nbuilds fine for me on .\nIs this issue still reproducible for you?\nYes. I just tested on master branch at commit . The exact same error.\nAre you using any overlays? Have you set any nixpkgs flags?\nI have a local clone of nixpkgs at , and I ran the command Does it depend on my nixos system config?\niirc it will depend on eg but i'm not sure about the nixos system config. What commit of nixpkgs are you on? Does it reproduce on the latest master?\nI don't have . I said I was on , which is the latest.\nLatest (at the time of writing) is does building on that commit work for you?\nThat commit does not build either.\nHi, I'm also having the same issue with same hash mismatch. I tested the build on two different systems. If you happen to have a system in which the build runs fine, would you mind sharing the output of the derivation: so I can diff it? I could also send you mine."}
{"_id":"doc-en-nixpkgs-a18f92448369f384d3b16abd23f43d712d2ffed18937d39accaa790fd90093cd","title":"","text":"Should be fixed by\nFixed by\nHi everyone, sorry to reactivate this issue but if I check out the current master branch and run , I end up with the same error as above (just with different hashes). Can anyone reproduce this behaviour?\nwhat hashes are you seeing now?\nI can rebuild the package just fine...\n! These are the hashes I get after running on the current master (). I am puzzled by the fact that this exact commands builds fine for . My expectation would have been that the behaviour should be the same if we are on the same platform (I am on x86_64-linux). Do you have an idea how we can dig deeper into this?\nI also just stumbled upon this issue and I do get the exact same hash mismatch as :\nWell, my only hypothesis is that the bazel dependencies derivation is nothing more than non-deterministic :'(\nDoes this still build for you? If it does I can offer to send you an archive of my jaxlib with the changed hash so you can run a diff to find out what is wrong. (Or the other way round ofc)\nYes, I have tried once again right now and it works fine... Sure, Send me what you have :)\nAlright, I've updated today and will build against nixpkgs . My machine will probably take some time to completely build it though, so I'll post back once it's done.\nI'm getting a similar problem when I'm trying to compile . The commit is from the branch. The commit was the only commit I found after going through multiple issues and threads which worked on my system. I have also observed this issue when compiling (), so the issue of build failures due to bazel hash mismatch isn't just limited to . So, I don't think that this issue has been properly resolved yet.\nI'm not sure if this is helpful--or noise!--but I just hit a similar issue with (see below for output, repro, and system info).\nBtw we're tracking the hash issues in ."}
{"_id":"doc-en-nixpkgs-ac0099e9536c54b38482c97328ae02ae34928de5d855bba20660bfef2e278ee2","title":"","text":"systemd seems to use the term split-usr to refer to an attribute of a system, where: is a mount point. is not mounted \"at boot\". Since systemd v248, support for a split-usr system is deprecated: While don't seem to mention a formal removal of support of split-usr, it seems that . According to : It seems that if is a mount point, this unit calls with on it, regardless of whether it is already mounted — making the assumption that it had already been mounted \"at boot\". When I installed my first NixOS on my workstation, I made a filesystem for each path under . This let me customize options per directory as I wished, both at install and later on. ZFS's sharing of storage space between filesystems in the same zpool takes the cost out of being \"generous\" with the number of filesystems. I didn't know that is merely that happens to be generated at boot. I also didn't know that systemd deprecated split-usr. So I did not mark as . The system built successfully and booted successfully. Except for an error in the logs: The failure seems to be due to the attempt to remount using with the option a non-mounted filesystem — . is later successfully mounted along with the rest of the filesystems. Since systemd seems to expect that if is a mount point it would have already been mounted \"at boot\", I would expect NixOS to: 's to by default, . to build when 's is (that could be ). Understanding this error took around three hours of collaborative debugging with the tremendous help of A workaround is to set for , or to not have a mount point at all. The suggested solution (expected behavior) is with the goal of sparing all future users an investigation of this error. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Not sure who to mention. Please ignore if you no longer wish to be involved. If you happen to know who should be mentioned here and is not, please comment mentioning them. Please run and paste the result. Maintainer information:\ngentoo notes this in their wiki as well\nping a couple people who might care: and probably others."}
{"_id":"doc-en-nixpkgs-c5604a8b1ab9b49486c7879c3f746f6b8538297ae17a6d7d5239632b007c832d","title":"","text":"Describe the issue In the opencv build for mac, why is off by default? What needs to be done to enable it? (either development work, dependencies that aren't yet nixpkgs, or, if possible, how to manually override the argument and simply set to ) To Reproduce See above Expected behavior There may be a good reason it's disabled, so I can't say that I'd expect videoio to be enabled by default. Notify maintainers Metadata Please run and paste the result. Maintainer information:\nIt was removed here 15 months ago: See this PR: due to apple removing most of QTkit in 10.12 Brew does not use this option. You can use an overlay or a nixpkgs checkout with this patch to build with videoio The following will drop you into a nix-shell with the patched opencv, which you can use for testing. I'm not sure if it builds. FWIW, I get the following build failure which indicates the upstream issue might not be resolved, or we're missing some thing in our derivation.\nI was originally attempting to use an overlay. After getting nowhere, I made a , which is what redirected me to the nix build. So if you want to help me close that thread, that'd be awesome cause both me and the person that helped me still don't know how to access/change the from an overlay."}
{"_id":"doc-en-nixpkgs-c1c2c0245757112c0199043946acee66eb141344ee4df372abe0c1b1b01f9b71","title":"","text":"RStudio () fails to build from nixpkgs master with a 404 on downloading sources. 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. Maintainer information:"}
{"_id":"doc-en-nixpkgs-aacc0eb331f5c24cbe3c07a8504dd45bc203fe9d0b59ffe127d96faf749b81d4","title":"","text":", CVSSv3=8.8 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc"}
{"_id":"doc-en-nixpkgs-77eb0b8a5f3028ea8d7ed25b29efba133d91dcc102a442455b7adeaed78aca7c","title":"","text":"Describe the bug After electron 12 came out, adding in home-manager succeeds, but trying to start the app fails mentioning a missing javascript function from an older version of electron. To Reproduce Steps to reproduce the behavior: to home-manager's app from terminal with Expected behavior Expected the application start as it had before. Additional context I was able to get it working locally by providing an overlay to home-manager: I would have created a PR myself, but I'm still new to nix and not sure entirely how to require a different electron version in the package derivation. Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(jon): nixpkgs: Maintainer information:\nthanks for catching this! Just fixed in the PR above."}
{"_id":"doc-en-nixpkgs-46a6afbfb48ffe96d96bcf89dcc898b900b7d31b1c3d7e152aa671a70346f18d","title":"","text":"Describe the bug The rhdf5 library does not work on latest release. To Reproduce Expected behavior A shell with R and rhdf5. Additional context Instead I get: Notify maintainers Metadata Maintainer information:\n\"6.topic: rust\" should be removed, this is an R package, not Rust.\nThis was fixed in"}
{"_id":"doc-en-nixpkgs-183241dd579912259bcbef8587bc106f0835bf846a61d6d5ef4b8484710d1344","title":"","text":"Steps to reproduce the behavior: So when I wanted to dig deeper, with I'm trying to recreate with a toolchain that's on hydra so I don't have to compile GCC for myself (twice!) Please run and paste the result. In particular, is pinned to:\nDiff-ing the two files, I get: I suspect the problem comes from in the that isn't present in the . I wonder why so many differences are present though? I've confirmed this by adding to the derivation, but again why are the differences present? Even if they have been helpful to track this down\nI suspect there were impurities in your environment but the difference is still weird. I don't know why would be there but not Adding to the mingw build in"}
{"_id":"doc-en-nixpkgs-1b9abcc5999b18c890e9b72b838bc298b6f07bc5e1611cef5464636c4ba28d0d","title":"","text":"Fail to connect to a l2tp + ipsec VPN after putting in all information. This happens on both Latest Gnome ISO and after NixOS installation. Message received on Gnome Desktop: Connection Failed Activation of network connection failed Steps to reproduce the behavior: Live Gnome ISO. l2tp + ipsec (strongswan) details in NetworkManager. on VPN connection. There are several fixes listed in this issue I was able to fix the problem by creating the file AFTER creating the connection and failing to connect once. (I also created the file BEFORE creating the connection, but that did not fix the issue.) After successfully connecting, this was content of file include The following is the failure output from journalctl From ISO system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nI was also having issues and tried the above suggested by and was able to connect only after a failed connection !\nThis seems to fix the bug May we have this to the default package?\nFix in"}
{"_id":"doc-en-nixpkgs-459b29eb6a7a00b365dc2eb9a5b2a2ce4750d8e4e76d32065d9dbad0006b0c97","title":"","text":"Phew, a big title! Trying to write down as much as I can before I forget. First, the last part: If doesn't exist, will show failing like: fixes this problem. NixOS should probably create this file. I'm not sure if this file should be writable or not, when it exists, I have only ever seen it contain: I don't know what writes that there. Now for can't edit L2TP VPNs, but (GUI) can, even though nm-applet doesn't work under sway. If you see this in the system logs: try enabling \"legacy proposals\" in nm-connection-editor's IPSec Settings and try again. system: host os: multi-user?: sandbox: version: channels(root): channels(grahamc): nixpkgs:\nSide note, how do I know for sure fixes it? I erased my dozens of times nailing it down, reproducing it to exactly this.\nI think the strongswan module creates that file and the actual L2TP plugin appends that line to this file.\nNice find that the strongswan module does create that file! I don't have the strongswan module enabled, it seems something else in the stack would periodically create this file?\nI'm not sure what does create it eventually, but it appears the plugin expects the file to exist so we should just do exactly that. It doesn't help that it expects it to be mutable, so maybe we can handle this within the NM module to add more secrets. Though it would probably duplicate what the strongswan module does.\n^ does this make sense to you?\nSo I just remembered about this module I have: maybe instead we should have the networkmanager do when it detects the l2tp plugin but I am not sure how to do that. Maybe we would need to introduce a new option in networkmanager to add the nm-l2tp plugin and create the file. I tend to connect physically to the private network and only as a last resort rely to nm-l2tp since it tends to not work regularly and I am not sure if it's blocked by the network or some l2tp breakage."}
{"_id":"doc-en-nixpkgs-01bf05955183055e43e15df94f456dd5489e3adc88325d65af43de1fc63a3fbe","title":"","text":"We could add an option to networkmanager in the same way there's one for strongswan there\nWas there ever any follow up on :\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 guess, it's still relevant, maybe not so urgent. this helped me big time:\nI marked this as stale due to inactivity. &rarr;\nI just ran into this on 21.05. Seeing a log like this: <details<summaryjournalctl log when starting vpn</summary<pre<codecharon[2059]: 00[CFG] loading ca certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/cacerts' charon[2059]: 00[CFG] loading aa certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/aacerts' charon[2059]: 00[CFG] loading ocsp signer certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec."}
{"_id":"doc-en-nixpkgs-4bfe7c67586d5a08e25c73dc1e6d55e5fc3370bba9e0c784d7f12ac26b3b6031","title":"","text":"d/ocspcerts' charon[2059]: 00[CFG] loading attribute certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/acerts' charon[2059]: 00[CFG] loading crls from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/crls' charon[2059]: 00[CFG] loading secrets from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.secrets' charon[2059]: 00[CFG] expanding file expression '/etc/ipsec.secrets' failed charon[2059]: 00[CFG] opening triplet file /nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan- failed: No such file or directory charon[2059]: 00[CFG] loaded 0 RADIUS server configurations charon[2059]: 00[CFG] no script for ext-auth script defined,"}
{"_id":"doc-en-nixpkgs-9a98539d19b7881f97ef0dc57203e3f3fbd679e5012f516d0c596ad4ff48e363","title":"","text":"disabled charon[2059]: 00[LIB] loaded plugins: charon unbound pkcs11 aesni aes des rc2 sha2 sha1 md5 mgf1 rdrand random nonce x509 revocation constraints acert pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey dnscert pem openssl af-alg fips-prf gmp curve25519 chapoly xcbc cmac hmac curl attr kernel-netlink resolve socket-default connmark forecast farp stroke vici updown eap-identity eap-sim eap-sim-pcsc eap-aka eap-aka-3gpp2 eap-simaka-pseudonym eap-simaka-reauth eap-md5 eap-gtc eap-mschapv2 eap-radius xauth-generic xauth-eap xauth-pam dhcp counters charon[2059]: 00[JOB] spawning 16 worker threads ipsecstarter[2058]: charon (2059) started after 660 ms charon[2059]: 11[CFG] received stroke: add connection '-ebef-4658-8991-' charon[2059]: 11[CFG] configuration '-ebef-4658-8991-' charon[2059]: 13[CFG] rereading secrets charon[2059]: 13[CFG] loading secrets from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.secrets' charon[2059]: 13[CFG] expanding file expression '/etc/ipsec.secrets' failed charon[2059]: 14[CFG] received stroke: initiate '-ebef-4658-8991-' charon[2059]: 15[IKE] initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111.111 charon[2059]: 15[IKE] initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111."}
{"_id":"doc-en-nixpkgs-5454b73c2b916239670c972c6c3e1aff1d31be4e26db9e2757bde4ea2e06654e","title":"","text":"111 charon[2059]: 15[ENC] generating IDPROT request 0 [ SA V V V V V ] charon[2059]: 15[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (304 bytes) charon[2059]: 03[NET] received packet: from 123.111.111.111[500] to 192.168.1.11[500] (204 bytes) charon[2059]: 03[ENC] parsed IDPROT response 0 [ SA V V V V V V ] charon[2059]: 03[IKE] received NAT-T (RFC 3947) vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-03 vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-02n vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-02 vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-00 vendor ID charon[2059]: 03[IKE] received DPD vendor ID charon[2059]: 03[CFG] selected proposal: IKE:AESCBC128/HMACSHA196/PRFHMACSHA1/MODP2048 charon[2059]: 03[ENC] generating IDPROT request 0 [ KE No NAT-D NAT-D ] charon[2059]: 03[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (372 bytes) charon[2059]: 04[NET] received packet: from 123.111.111.111[500] to 192.168.1.11[500] (356 bytes) charon[2059]: 04[ENC] parsed IDPROT response 0 [ KE No NAT-D NAT-D ] charon[2059]: 04[IKE] no shared key found for 192.168.1.11 - 123.111.111."}
{"_id":"doc-en-nixpkgs-3ef8b4aa22b51eec87eba56eca601e6e47ea55bbbe07447bdd79eaaa01f9b61b","title":"","text":"111 charon[2059]: 04[ENC] generating INFORMATIONALV1 request [ N(INVALKE) ] charon[2059]: 04[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (56 bytes) NetworkManager[2277]: initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111.111 NetworkManager[2277]: generating IDPROT request 0 [ SA V V V V V ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (304 bytes) NetworkManager[2277]: received packet: from 123.111.111.111[500] to 192.168.1.11[500] (204 bytes) NetworkManager[2277]: parsed IDPROT response 0 [ SA V V V V V V ] NetworkManager[2277]: received NAT-T (RFC 3947) vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-03 vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-02n vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-02 vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-00 vendor ID NetworkManager[2277]: received DPD vendor ID NetworkManager[2277]: selected proposal: IKE:AESCBC128/HMACSHA196/PRFHMACSHA1/MODP2048 NetworkManager[2277]: generating IDPROT request 0 [ KE No NAT-D NAT-D ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (372 bytes) NetworkManager[2277]: received packet: from 123.111.111.111[500] to 192.168.1.11[500] (356 bytes) NetworkManager[2277]: parsed IDPROT response 0 [ KE No NAT-D NAT-D ] NetworkManager[2277]: no shared key found for 192.168.1.11 - 123.111.111."}
{"_id":"doc-en-nixpkgs-1e05314f608412071ecf860b1ccc3abd8b52327fbbcdc48a7559708be9252249","title":"","text":"111 NetworkManager[2277]: generating INFORMATIONALV1 request [ N(INVALKE) ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (56 bytes) NetworkManager[2277]: establishing connection '-ebef-4658-8991-' failed NetworkManager[2283]: Stopping strongSwan IPsec. charon[2059]: 00[DMN] signal of type SIGINT received. Shutting down ipsecstarter[2058]: child 2059 (charon) has quit (exit code 0) ipsecstarter[2058]: ipsecstarter[2058]: charon stopped after 200 ms ipsecstarter[2058]: ipsec starter stopped nm-l2tp-service[2039]: gdbusmethodinvocationtake_error: assertion 'error != NULL' failed NetworkManager[954]: <warn[.6803] vpn-connection[0x24c60a0,-ebef-4658-8991-,\"my-l2tp-vpn\",0]: VPN connection: failed to connect: 'Message recipient disconnected from message bus without replying' .nm-applet-wrap[1470]: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files </pre</code</detailsRunning the following command fixed my error and allowed me to connect: The networking part of my only has .\nThis still appears relevant in 21.11. Adding this (as mentioned above) to my config appears to get an L2TP and IPSec VPN working with NetworkManager:\nStill relevant in 22.05. I am confirming that with a clean install, trying to set up L2TP/IPsec VPNs fail with the following indicator: fixed the issue for me straight away as well.\nFix in"}
{"_id":"doc-en-nixpkgs-002931ebb652788b31a08c618f61485176b295d35c2cda0833f7d4ddfda87955","title":"","text":"Describe the bug Thunderbird 78.2.1 is working. master (Thunderbird 78.2.2) has rendering issues (see screenshot). Most buttons do not react to clicks and the menu is also not reacting. To Reproduce Switch to the mentioned commit and rebuild. Expected behavior Normally working thunderbird. Screenshots ! Notify maintainers Metadata\nThis was also a bug in Ubuntu, it was fixed there with:\nUpstream bug appears to be\nBtw temporary workaround would be to switch to thunderbird-bin-78 if you are not opposed to binaries"}
{"_id":"doc-en-nixpkgs-1a09dafd2a3ccd19245aa3e7403902c50e204952543f16118739e3284243f9c3","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]:\nmight be fixed by confirmed. closing.\nHello. I'm new to NixOS, and also facing this problem: How can I apply that fix? I just updated my NixOS system flake to latest version: But still getting error during system rebuild:\ntry and update again, the fix is in unstable now."}
{"_id":"doc-en-nixpkgs-338fb88b497bf8f422af3d41cc2d76d6cc0b98f1ba93562c6714699ad99bef7f","title":"","text":"Add any other context about the problem here. Please run and paste the result. repro'd on commit id\nbacktrace: <details<summaryBacktrace from lldb</summary</details\nshapely 1.8.4 with the fix is now in pypi, I saw you wanted to upgrade it, did you get around to do it?\nthanks for the reminder, committed it"}
{"_id":"doc-en-nixpkgs-d8f69a1a789e862118319aab8110d078e16536dfb2148ebe04f07644e5cfe51d","title":"","text":"When adding a text in Gimp, a green border is visible: ! However, I would expect something like that: ! After , a on both Gimp (need 3.10.30) and (need 1.18 apparently). However, in NixOs Cairo 1.16 is used instead, so I guess it is necessary to upgrade cairo. Steps to reproduce the behavior: some text on gimp, say white text on black background I expect Cairo does not have maintainers so I'm pinging random people that contributed: Running NixOs with KDE Plasma.\nLooking at no distributions ship 1.18 yet. I wonder why. Is it an API-breaking release?\nProposed cairo one-liner backport as\nThe 1.18 branch yet. We could switch to development snapshots (1.17.x) if there are more concerns. But cherry-picks will probably be enough for now.\nThe above PR solved the issue, thanks a lot! For people wanting to test before it gets into unstable you can do: but it takes a few hours to compile until Hydra compiles it.\nActually I'll maybe let it open until it's merged to unstable (for now it's in stagging) and backported.\nGitHub should auto-close once the fixing commit reaches master branch. Though I'm not sure if that wasn't broken by closing and reopening.\nIt's reached all channels."}
{"_id":"doc-en-nixpkgs-7b22d8b6831425ecc5a4ca9a12b25089f85158c0f554dafd0164dc075a002a74","title":"","text":"Project description <!-- Describe the project a little: --: Newt is a programming library for color text mode, widget based user interfaces. Newt can be used to add stacked windows, entry widgets, checkboxes, radio buttons, labels, plain text fields, scrollbars, etc., to text mode user interfaces. Newt is based on the slang library. is in nixpkgs but only built for targets. It would be great if it could also be built for Homebrew has a , but since I just started using Nix I wasn't able yet to port it to a Nix file. My best try can be . Metadata homepage URL: source URL: license: gpl2+ platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-4e79a625944561eb4cd6d93925610c25d885f5e890eb61f365e201abc5515369","title":"","text":"Describe the bug With default settings, sound won't play in the stable repository Tor Browser. I managed to get it working: for some reason, says this: I am still new to Nix so I am not sure what it should say, but it can't be right since this piece in got it working: (after of course) To Reproduce Steps to reproduce the behavior: to your system configuration but leave ALSA disabled to do anything that requires sound in the browser. Metadata system: host os: multi-user?: sandbox: version: channels: nixpkgs: Maintainer information:\nI marked this as stale due to inactivity. &rarr;\nme, too. any word on this? just open any youtube video, and there's no sound. if it matters, i'm using the latest on using overlays.\nI marked this as stale due to inactivity. &rarr;\nI am also interested in solving this. I am using nixos: 21.05.3761. (Okapi) Since I am new to nix, I just tried the package override from above, but this is not working. Reading through nix-pills is not really enlightening which files are involved in what...\nDid you remember to uninstall and install after adding the override?\nI get an error: but my is located in\nTwo possibilities that come to mind: 1: You didn't install by attribute. you need to do (assuming your nix channel name is ) as opposed to 2: Your is indeed in the wrong place or wrongly named. I don't recall straight how it should be named. Believe the nixpkgs manual with this one, not me.\nAfter reading I put my stuff now into So tor browser sources are not there anymore... mhhhh... so in that sense I feel nixos is not holding its promises of reliability (caused by external party)\nIt's our problem, and a known issue. More info .\nThey have an alternative mirror recently to the unstable channel. If you try the newest unstable, it might download. Can't guarantee that though."}
{"_id":"doc-en-nixpkgs-dd26cdca5b89fa05e23460e320138d2b0b124088a448336754bd8e5a83fddeca","title":"","text":"thank you for your attention/help - I will try this later and report back...\nI have the following override: So tor-browser reports back the new version: 10.5.10 but I get the following error when playing a video - so audio does still not work:\n... it seems that the overlay does not affect of the original package. This part of is not contained in the generated file: since I am quite a novice with nixos, any hint is welcome....\nthat worked, thanks alot!"}
{"_id":"doc-en-nixpkgs-cf8654009c3d3b71d797c2aad31532aa532374bffad9b8da1821412d55bf8d0f","title":"","text":"For Chromium, there's a convenient way to define custom flags through . However, there doesn't seem to be a similar option for . I tried setting to \"--touch-events\", but touchscreen scrolling is not enabled when starting VSCode from desktop launcher, while running in console works as expected. Steps to reproduce the behavior: to \"--touch-events\" VSCode from desktop launcher on the editor area through touchscreen The editor should scroll as I drag. system: host os: multi-user?: sandbox: version: channels(yes): channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-4ad01d7b761c3ecc3d63d51f4c03c8b92fe88b10e5aff0eb8cd7ddaecbbdeeb2","title":"","text":"Overriding idris-no-deps in nixpkgs results in a mismatch between versions of builtin packages and the compiler. With this derivation: I would expect to end up overriding the version of idris-no-deps in idrisPackages would change the derivations of builtin packages to be built with the supplied version of Idris. However, instead they are built with the Idris from the channel used. Leading to this error at build time (for Idris2): By examining the final result of the build I can see 2 versions of idris being used: Please run and paste the results.\nThought I might be able to solve this issue by specifying overrides as well. But no luck This is what the derivation for base looks like Specifically: Which contains the wrong version of Idris.\nSame issue with non builtin packages as well. Also perhaps this is a better demonstration of the build time dependencies:\nThanks for the report, above PR should fix it, let me know if it works for you, then I'll merge it :)\nWell actually I know it will work, but still. As a workaround if you don't want to change nixpkgs, an overlay should give no problems too:\nBrilliant! Yes it's working for me and I'm now able to build Idris 2. Thank you very much!"}
{"_id":"doc-en-nixpkgs-38b1b1256938e37ba2eadeac10da05ea0aa2050adea4293c8cf359828c8712e6","title":"","text":"The Haskell Hackage database allows distros to report which packages they ship, and include a link. Right now, it seems that nixpkgs reports all haskell packags, including broken ones. This makes for a bad user experience – I might see on hackage that nixos comes with a certain package, and then happily go ahead trying to use it, only later to get the dreaded error message. Same actually for repology, reporting packages as available that we know do not build is not great.\nWe intend to support all package. We just need haskell maintainer\nOh, absolutely! Maybe I shouldn't say “supported” but “available”.\nNo, we don't. We only intend to support packages which have value to our users. Hackage is append only and contains a lot of dead or niche packages.\nI agree this should have been fixed long ago."}
{"_id":"doc-en-nixpkgs-218ed6cf9472dc10c1596ae2fec318fb52df6df7a71b7ab2d29148fa9cdca91e","title":"","text":"Cc: First of all, thanks to everyone for working on NixOS. Awesome 4.3 has a module called , it allows It can be used for theming, as shown in . However, the current build does not include the typelib files needed by the module making it unusable. The  implementation uses lgi to obtain via gobject-introspec return require('lgi').Gtk Since the current build does not include the typelib files needed, the above call fails. After some experimentation, I found out that both and are needed. For example: and try to load Gtk: fails with (the package that actually includes the typelib file) and add the folder to the environment variable: fails with and add it to and finally loads. Awesome as window manager to load the example gtk theme awesome the warnings issues by Awesome: I suggest that both and are as build inputs to the awesome package, I tried this out and it actually works. The catch is that the closure size increases by 123.9M: build awesome without gtk3-x11 and atk -99.6M build awesome with gtk3-x11 and atk -223.4M So, instead of adding the packages unconditionally, we could add an optional flag, like e.g. , defaulting to false. In this way, one could always build awesome and add it to . Ideally one could even add something like to the top level , a bit like : If a decision is made, I'd be happy to submit a PR. system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: awesome 4.3 (Too long) Compiled against Lua 5.2.4 (running with Lua 5.2) D-Bus support: execinfo support: xcb-randr version: 1.6 LGI version: 0.9.2\nIt should not be necessary to use , should work just fine. See for docs on , which will populate the environment variable automatically.\nThanks, I'll have a look. For the record, I used because that's where told be the typelib files where. I am still keen on hearing what the correct solution would be regarding how to add support (closure size, optional arguments etc.). Thanks.\nthanks for our suggestions."}
{"_id":"doc-en-nixpkgs-ca6f5909d8e59340243f0b1c82bc6dd5ecae40ce5912d586c0d286cfc9bfc4e8","title":"","text":"Here are my thoughts: seems to work as well, the closure size is 222.9M instead of 223.4M seems quite conveniet, but awesome needs additional options in the wrapper and it's unclear to me whether we could do that after introducint uses that seems to have negative effects, see so we may have to look for alternative solutions anyway (Awesome does not seem to use much of GTK anyway as it's not a GTK app)\nhow could it shrink? can use as described in the doc PR to add more options. , I am aware of that but other than hardcoding the typelibs like we do in GNOME Shell extensions, we do not have anything better at the moment. See for deeper analysis.\n¯()/¯ maybe it's got less dependencies built than the one? I see, I somehow missed that. It seems that works OK (I am using this in an overlay on NixOS waiting for the patches to land in the stable channel): In the end, AwesomeWM should not need the whole of gtk, I think that gtk should be made optional so one can turn it on or off. Thanks, I did notice that and I'll keep an eye on it"}
{"_id":"doc-en-nixpkgs-ff5de244771ed882005a4f584a02a667615c73919657594614565281aabbc6a1","title":"","text":"fails to compile on unstable. on (Flounder) System: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: \"16.09pre88945.\" trace:"}
{"_id":"doc-en-nixpkgs-0063329d9739f04683501ef0d0588f5ab2f9e2b650ca385f1da53666d24d0a68","title":"","text":"Project description simplescreenrecorder is not that user-friendly and has problems (). right now i use OBS, but it's overkill for the task. maybe this is a good alternative Metadata homepage URL: source URL: license: GPL-3.0-or-later () platforms: linux, more?"}
{"_id":"doc-en-nixpkgs-4df336f9ca1fa2bc2a48cfb498bd236f1f4e3ea87fe2e7bdc253ee0177a6a0d7","title":"","text":"If I only do: then I get virtualbox + nvidia: If I enable virtualbox guest additions: then I get only virtualbox!!! and nvidia does not work anymore on my machine: this is because virtualbox guest additions is overriding services.xserver.videoDrivers: this is not necessary since by default the lists are merged workaround: then I get virtualbox + guest additions + nvidia: Ideally this should work out-of-the box, debugging this kind of behavior is very obscure, and also different configuration options should cohexist"}
{"_id":"doc-en-nixpkgs-c91792fd59f7bce381d1793f71069a17588ff0f14a49fa5e0714302f6155102a","title":"","text":"On the master branch ethminer fails to compile with messages about missing getglobalepochcontext from ethash namespace. Attempt to build ethminer on master branch. Successful compilation. Root of the failure is in changes done to the structure of the dependency chfast/ethash; specifically, 0.6.0 -0.7.0. Patching the libethcore/EthashAux.h file in the ethminer repo, by adding to the headers, and the file by changing the line to does the job."}
{"_id":"doc-en-nixpkgs-f2a96f6056fa57cb2f97675603fde5ea3aa8761850f86c7267ed867e5c4757ee","title":"","text":"Describe the bug doesn't run on Darwin, due to some Perl / shebang errors. To Reproduce Steps to reproduce the behavior: Darwin, run the only produced binary , ie. following output is produced: Expected behavior The executable should output its help text when run without arguments: Additional context I managed to get it running using a wrapper script that runs . Notify maintainers Metadata Maintainer information:"}
{"_id":"doc-en-nixpkgs-a87822a548bc8ca2fcce95f514ca94bfc6926607e617ac963a3aaf5f5391ccef","title":"","text":"name: current version: 0.10.1 desired version: 0.11.0 maintainers: The last few updates were done by r-ryantm, I don't know why it didn't do this time. I checked the logs, apparently it didn't even try building it."}
{"_id":"doc-en-nixpkgs-796a778ccb6b013b74fc524cd779282dd6da0403d9cdddd615826f45e93ba0f4","title":"","text":"In gnome runs fine, in KDE plasma there are a couple problems: Unable to open file explorer when pressing \"+\", crashes with error Unable to add account, getting error Run in a pure shell: , use the and try to use it OR plasma installed and no other desktop environment: onedriver from nixpkgs (with home manager for example:) and press the button to add a folder. No errors we're missing the inputs and . should fix the gsettings schemas error (). The error requires env variable , we should probably wrap as explained . Quick and dirty way to make it work now, without wrapping, is adding those dependencies and adding the variable to the whole system: and to buildInputs and nativeBuildInputs respectively. (not sure which one for either): to the nixOS configuration the location of the variable: We should create a option eventually ahahha This is my configuration for the onedriver user service: <!-- 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]:\nHello and thanks for reporting this! The is although it is only available in the channel for now, can you please test if the derivation from nixpkgs-unstable works for you? If not, I will add the missing dependency and make a PR asap :) As for the GIOEXTRAMODULES variable I am not sure there is something I can do at the derivation level.\nThanks I can confirm the version on the unstable channel doesn't crash with , but without the variable set the error is still present. I tried to wrap it by adding this line in the end of the postInstall script but it didn't fix it, running now shows two GIOEXTRAMODULES variables set tho I'll keep this open for now because of this problem and update the title the workaround for now is adding to the system configuration\nHey, I just pushed a small branch which should fix your issue with . I built the derivation locally and I get the right GIOEXTRAMODULES path set correctly by the script."}
{"_id":"doc-en-nixpkgs-9fcb657d1ab5b89b5c19f7b6818dde620f48f6e38f690a64142c04a88fc2fb8f","title":"","text":"In my attempt in my previous comment, I had also tried a method that seemed to have set the correct GIOEXTRAMODULES path, but I tried your derivation and still: ! I grabbed your commit like this and it took a couple hours to build, it seems to have built a lot of programs besides onedriver, I'm still not a great nixOS wizard:\nnever mind, I'm dumb, forgot to change the package used in , now the error doesn't appear, but the window comes up grey? !\nTrying to use the code from in my own config with callPackage gives me if I use instead of it works perfectly\nusing just also works\nThat is because is only on right now, if you're using you need to use , which is the same thing :) Glad to know the problem has been fixed for you. As for the blank page, it seems to be an upstream issue with onedriver and Plasma 6 (see jstaf/onedriver), but since I don't use Plasma I'm afraid I cannot help.."}
{"_id":"doc-en-nixpkgs-68a20a0421cb6ae5dc88828ea10e6fb67d99730c63906980f95ba399a4e8b0d2","title":"","text":"Project description The Open Observatory of Network Interference (OONI) is a free software project that aims to empower decentralized efforts in increasing transparency of Internet censorship around the world. please package as \"ooniprobe-cli\" (\"ooniprobe\" as alias) and \"ooniprobe-desktop\" like used here: Metadata homepage URL: source URL: license: mit (hidden in ) / BSD 3-Clause platforms: unix, linux, darwin, windows\nI marked this as stale due to inactivity. &rarr;\n...\nI marked this as stale due to inactivity. &rarr;\nStill relevant."}
{"_id":"doc-en-nixpkgs-cd4c0bfa0e6a972ceb46d2c6b9dee508a8bba3056f1c6a991c020a541b501a4e","title":"","text":"For visibility of our project it would be good if Steam can detect NixOS. Then it might appear in their stats: Error on console: Related to Currently detected system informations: steam system informations system: host os: multi-user?: sandbox: version: channels(davidak): channels(root): nixpkgs:\nNixOS isn't configured to have . Kinda surprised they don't fallback to in favor of .\nThey actually do fall back but our doesn't support any files besides deprecated . We had a discussion before about correctness of providing on NixOS but I think we could do that, just print some error when supported LSB version is requested. Maybe we could steal Debian's modern implementation - I think they even use ."}
{"_id":"doc-en-nixpkgs-126012b178288cb3e9c25249e096a87c68e9896c8b7967f3a999886f54b2e953","title":"","text":"Hi there I installed but the driver is not available on CUPS; the printer (Brother HL-1223WE) is detected correctly. My system is on . Steps to reproduce the behavior: to to add the printer on CUPS.\nSubmitted a with a fix for this issue."}
{"_id":"doc-en-nixpkgs-01944d0a395f0c2fd47ae9a22a201e8e01fddeee0766f969b6ebad6104d1da10","title":"","text":"Project description From the home page: Metadata homepage URL: URL: public domain with two files under 3 clause BSD () platforms: \"The system is known to run on Linux and BSD-based UNIX systems. Supported target architectures are x86-64 armv6 (hardfp), AArch64, Apple M1 and riscv64 (R64IMAFD).\""}
{"_id":"doc-en-nixpkgs-e013115cf5529568c0aec5d7bd01fee5b78eee5e9fc8539c6cd4b0ee728451fc","title":"","text":"For a few days, when booting my amd computer with plymouth enabled I can't enter my passphrase anymore. Pushing keys multiple times eventually end up in one key-press being accepted. Booting with instead of suddenly has no more issues with keyboard entries. Steps to reproduce the behavior: NixOS Unstable to and with a LUKS/ZFS Passphrase -presses are omitted Every key I hit will be used. <!-- 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(pl): channels(root): nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nUpstream bug report Fixed in upstream already"}
{"_id":"doc-en-nixpkgs-522749b63bd72f901e1423d08567ac3ac4a2c8b6b5035238af2d2c1378835a8e","title":"","text":"Project description nodenv is one of version managers. I know you can manege with Nix itself, but majority of people in the frontend world assume everyone uses version managers which respect files like or , so you have to use them when you're working with them. Metadata homepage URL: source URL: license: MIT platforms: I'm not sure actually, but it's distributed as a homebrew formula\nHello, please check the merged pull request for notes on the package. The package works, but might need some changes or be extended to work better in the future.\nWow, thanks a lot for your help!"}
{"_id":"doc-en-nixpkgs-8ec161f7b621c8399fdba1fde63ccfbf3f51552df1457bd80f3aedee780ee07f","title":"","text":", (nixos-unstable, nixos-19.03, nixos-18.09) Scanned versions: nixos-unstable: ; nixos-19.03: ; nixos-18.09: . May contain false positives."}
{"_id":"doc-en-nixpkgs-ee131ce63d374e1a4ea431fde04b66fa5f61b7f8708ebfe13affac71c28aba00","title":"","text":"Can't simply apply the upstream commits, unfortunately (AFAICT). This looks pretty serious!\nThank you!! :sparkle:"}
{"_id":"doc-en-nixpkgs-fc5a2bfbec3f759f2cfff19f48f8826daf45b151aa5237c6842e745592d22cf8","title":"","text":"The audacious package imports audacious-plugins to build most of the common plugins and then link them into the audacious lib path. However, this makes it hard to add more audacious plugins, like vgmstream. The vgmstream package currently has its , because importing the audacious package causes an infinite recursion error. Steps to reproduce the behavior: vgmstream to audacious-plugins buildInputs audacious to vgmstream's buildInputs and comment out the disable configure flag -shell -p audacious-plugins I expected that adding vgmstream to audacious-plugins would enable the plugin. Instead, the build crashes with an infinite recursion. How is it currently working for audacious to import audacious-plugins and audacious-plugins to import audacious? Can this same magic be extended to other plugins? This about how fcitx is packaged shows that fcitx-addons imports fcitx with no reverse import, should the audacious package be refactored to be similar? Should the audacious package gain an extra parameter to take extra plugin derivations, which can be created outside of the audacious-plugins derivation? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nInstead of adding , did you try to add instead? is without as input, and it is used to break the loop.\nThank you for the quick response! That would be elegant, but I don't see any result in my grep of nixpkgs or in the .\nSorry, it is here: Basically you need to do and this should do the trick. Considering that we are going to use this in more than one place it probably makes sense to introduce it as a , but the result is the same regardless.\nOh that's a neat trick! I'll try that approach out next. Thank you so much! I tried out the extra-plugins approach here, seems to work but is not ergonomic:\nI , and it's a lot easier to use as a user! If it looks good as an approach, please provide some review feedback and I'll squash it down for a PR :)\nShall I send a PR for a final review?"}
{"_id":"doc-en-nixpkgs-99998133db4606d013b2cfaaeb8a5e5d7ad758dfcfb0e54d1ec1074cf95ff80a","title":"","text":"Package name: juce Latest released version: 7.0.10 Current version on the unstable channel: 7.0.9 Current version on the stable/release channel: 7.0.7 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-ff2735316c42d7680fbb93546e39a847028948372646627e82d769619a132074","title":"","text":"Steps to reproduce the behavior: hydra build: build logs: 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]:\nNot sure why this suddenly started failing after it worked fine for the last 11 days. Reproduced this and submitted a patch in that fixed it for me locally.\nThanks, I can confirm that the patch does work.\nIn my observation, it only breaks on , the works just fine. That's extremely weird.\nI logged the test phase on the latest commit and the one before that, here’s what’s changed: Looks like it is to do with the\nNice work, It looks like is the commit that upgraded to pytest 8, but that was two weeks ago. So I'm not sure how this passed for 4 days ago.\nThe build that passed 4 days ago used as and the also wasn’t pointing to , here’s a snippet from the logs: The log file: But the latest build which failed, had set to and set to ."}
{"_id":"doc-en-nixpkgs-084a0e4dfd66d60c8af3c42319bdf01944df0cfb9e041ab2d23f1e4618f834b3","title":"","text":"Steps to reproduce the behavior: oterm 0.2.7 unstable (I'm doing via home-manager on rev ) Fails finding a typer version Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI will check on my NixOS host later in the day to see if I can replicate.\nThere's a quick way to fix it:\nAlso, a PR in upstream:"}
{"_id":"doc-en-nixpkgs-e20489714512ccbf30f6137f83aaa9a171f687289f6d04ec5eb14165be66b25a","title":"","text":"Steps to reproduce the behavior: something which uses (easily ) 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. --No maintainers, blame says last made a modification. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nNo maintainers, blame says last made a modification. Hm, I can’t recall changing anything remotely related to LLVM and/or wrapper stuff recently. Which file(s) are you referring to?"}
{"_id":"doc-en-nixpkgs-59ac1b753390d90ab6a570a66eabfaa9ee2c0f13caed6dc45087a97f747a2168","title":"","text":"Describe the bug nixos-unstable-small's package is broken: Seems related to beancount/fava To Reproduce Steps to reproduce the behavior: Expected behavior Fava builds correctly Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:\nI suspect this isn't the only app that broke with the switch from flask 1.2 to 2.0 and jinja 2 to 3.0.1\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nYou can use in the expression for to pin and to compatible versions."}
{"_id":"doc-en-nixpkgs-ddc91f10877ffc9e4e352a39b4abc901d0fadd77d8ca8944a3eeb67221584b3f","title":"","text":"it does not start anymore Steps to reproduce the behavior: davinci-resolve davinci-resolve Working Program. Installed from unstable 22.11pre420742.. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-709e105391110d0a1ec5f1d5f85d9e0fd0436be31631affb4a1a937b2deac051","title":"","text":", (nixos-unstable) (nixos-unstable) (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.\nSee also"}
{"_id":"doc-en-nixpkgs-6c109ece633fad1fe383ac353c779e2ea738546a7afeef8a96378cf7a14dee79","title":"","text":"See:\nI've been using cryptsetup with an SSD and without kernel crypto to run my entire NixOS and didn't noted any performance issues, but I agree that my patch was a temporary workaround, so enabling the crypto module would be a better solution.\nThe option also breaks the feature of that can be used when installing nixos to reason about the speed of disk encryption\nThe NixOS test works with and the kernel userapace crypto API enabled in on at least 19.03. was updated to 2.0.6 in the meantime, maybe the bug was fixed? Haven't noticed anything in release notes. This API shouldn't in fact be need for LUKS, only for tcrypt and the benchmark. Did you also run the test or did you just notice that on your local machine? Do you have any non-standard config concerning the initrd?\nHmm, even with the test succeeds. We need more information.\nI haven't ran any tests, I just tested it in my work laptop and in a VM used to isolate the issue. I used a non-standard initrd config only for debugging, but after finding the problem I used the standard one. The only strange thing I did was to have a LUKS2 encrypted volume, which isn't very common (or at least it wasn't at the moment I experienced the issue). In a few days I will try to boot my system both with and without kernel crypto to check whether it is necessary or not.\nI can confirm that I still have problems booting my system when kernel crypto is enabled. I put this in my , in an updated unstable NixOS: With this configuration, my system boots. If I uncomment the line, it doesn't because it fails to unencrypt my root partition. I'm using LVM inside a LUKS2 partition.\nHere is the result of using when mounting my LUKS2 volume with kernel crypto enabled. The last image is the most important. Sorry for pasting screenshots, I didn't have a flash drive to copy the logs. ! ! ! ! !\nThank you very much for your detailed analysis. :+1: Oh, LUKS2! Seems the userspace API is indeed needed for LUKS2 but not LUKS1. I'll try to adapt the test and fix this issue. There are probably just some modules missing."}
{"_id":"doc-en-nixpkgs-93cde1c6f21f07cc65ae70fc5940d0cb2c8c9ab524052c2065cf85ac498c9209","title":"","text":"Commit introduced to the configuration of . This causes to no longer work, with the following message: Run , where is a truecrypt volume. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nThe issue for re-enabling kernel_crypto is\nIt also breaks\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\nI marked this as stale due to inactivity. &rarr;\nare you sure this is still an issue? This seems to have been solved by . e.g. cryptsetup benchmark works just fine on my machine.\nI did not check and do not care anymore. Thanks!"}
{"_id":"doc-en-nixpkgs-9978542da65cd21ec618a9b5466eb9b3283f27b7d623529a6436fc04d1e6090b","title":"","text":"The tray icon appears, but he according window shows: Steps to reproduce the behavior: syncthingtray (through home.packages in home-manager in my case) on the tray icon The proper GUI with shiny buttons and stuff\nDidn't have time to do actual digging yet, but seems like it's actually a matter of launching it / nixos weirdness rather then the package itself at fault: if I run manually from the terminal it actually works as expected. if I have it launched by plasma's autostart it sits in the tray failed with the message above. if I have it launched as user systemd service through the according home-manager option, it fails to launch because it can not find the tray altogether (probably launched before plasma is ready). So the question is, why is it different when launched from autostart... The message shows the right path in after all... (Disclaimer: total nixos noob here. Maybe it's obvious for a more experienced user...)\nI'd investigate this by comparing the environment of your terminal to the environment of autostart's file - try to override the line to something like:\nOh I see what's the problem.. the file generates is pointing in to the unwrapped executable.. This needs to be patched locally in nixpkgs!\nThat would explain it. What do you mean by \"patched locally\"?\nI mean this:\nyou are invited to test the fix for your issue in .\nI'm really sorry it took me forever to actually test it - had issues with the system I use it on. Anyway, the desktop file wasn't my issue either - I didn't realize the thing in tray is not the autostarted desktop file / syncthingtray process, but the plasmoid which is apparently a completely different beast running within the plasmashell process rather then a separate one. It appears automatically in tray unless I use syncthingtray with and can not be removed from there through plasma controls. Launching the process actually creates a second icon, which behaves properly.\nI'm not sure I followed.. Does it work if you set ? has landed in so the environment issue fixed there should affect you somehow I think. Feel free to reopen the issue.\nNo, the plasmoid is what fails. The plasmoid seems to be launched in a different way, independent from the desktop file."}
{"_id":"doc-en-nixpkgs-183e8a901641f0b5c53e44266814fdf5b21bd9fed4f00d28dab00a9c42760951","title":"","text":"Whenever I include syncthingtray in the home manager with (which is default), the plasmoid appears in tray on next login - but no process exists. It seems to run as part of plasmashell instead and is not in the autostart at this point. Autostart seems to be a different way to start it as an alternative to the plasmoid stuff, the plasmoid is however what is running by default with the current syncthingtray package. Doesn't seem like I have permissions to reopen it in place.\nAccording to the initially reported issue description it is indeed the Plasmoid that's causing problems here. On Plasma the Plasmoid is supposedly the preferred UI. So the goal should be to fix it. If you nevertheless want to use the executable instead you can do that of course as well. Then you can simply disable the Plasmoid by removing it from all panels/screen as usual. If the Plasmoid is shown as part of Plasma's system tray Plasmoid, you can disable it via the settings of the system tray Plasmoid. To fix the actual issue of the Plasmoid: Supposedly a file is missing in the package. The full list of files to be contained by the package should currently look like this: Of course the exact paths depend on your install prefix and paths of your Qt and Plasma installation. Maybe something is not missing but installed to the wrong directory. Did the Plasmoid (not the stand-alone executable) ever work with your packaging? If it did then I'd try to compare the last working package with the first bad.\nNote that an override for the executable path (via a CMake option that then sets a define which is used if present like in your patch) could be upstreamed.\nI was thinking about it just today, since usually you'd want it to be the permanent symlink and not the path (to the wrapped executable) that might be removed after a garbage collection.. Let's continue this discussion in\nWhat is the status on this?"}
{"_id":"doc-en-nixpkgs-61ade85fc14e9a0752beed5e90a667ec0659ddba4ed2def65ba09c9a5d13beb1","title":"","text":"I'm still encountering this issue on my machine\nI'm not sure what more could I do here.. I will report here after comment that there are no much differences between the files installed by our package and what should be installed: <details<summary<codediff our- upstream-</code</summary</details\nIs this a problem affecting all NixOS users or is it just reproducible in the setup of a few people. For debugging it might help to start with the env variable set.\nI'd only compare the packaging with how other Plasmoids for NixOS are packaged. Maybe there actually needs to be a difference compared to my \"upstream packaging\".\nI don't experience this issue, here on Gnome, naturally. Other packages in Nixpkgs, like , and also put files in , according to .\nYes, you would obviously need to start a Plasma session to reproduce the issue. (Or just launch or in another session. I suppose will work in any X11 session and in any X11 or Wayland session.) Maybe it makes more sense if the users that actually use Plasma would do further debugging on their side, though. By the way, how do you use Syncthing Tray under GNOME? Last time I've checked whether it works there was no general support for system tray icons at all and issues like suggest that GNOME has no generic system tray icon support at all right now. If there are any workarounds those might be worth documenting under and could be extended with a remark to the workaround section.\nAs a note, I'm a pretty new NixOS user, but I switched yesterday to the unstable channel, and syncthingtray is working completely fine now.\nUsing .\nThanks for the report. I wonder what was the problem... I'll close this in the meantime, unless someone from the stable channels will give a detailed bug report."}
{"_id":"doc-en-nixpkgs-6ba5b5b777df947cd2895fffeb49e9c73e334de864d072be458c5c26d73b3fc2","title":"","text":"Unable to launch gplates on NixOS. A shared object file appears to be missing. Steps to reproduce the behavior: : gplates is expected to launch and be usable. N/A N/A No listed maintainers on Nix Packages but was the last to touch the source for this application. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nProbably adding to and/or adding to might help, but I'm too tired to debug tonight. I'll look into it in the next few days.\nThank you, I was reading about the first option you suggested being a potential fix. I'll see if I can wrap my head around doing it on my own as well this week, though I don't have a lot of experience contributing to projects likes this."}
{"_id":"doc-en-nixpkgs-bdc908b0302a74b6bab5346361bc2d848ade96a4b61cd19007c33c437eb8f77f","title":"","text":"Steps to reproduce the behavior: trueseeing dependency check fails due to missing termcolor. Full logs : <summary<details<preSourcing python-remove-tests-dir-hook Sourcing python-catch-conflicts- Sourcing python-remove-bin-bytecode- Sourcing pypa-build-hook Using pypaBuildPhase Sourcing python-runtime-deps-check-hook Using pythonRuntimeDepsCheckHook Sourcing pypa-install-hook Using pypaInstallPhase Sourcing python-imports-check- Using pythonImportsCheckPhase Sourcing python-namespaces-hook Sourcing python-catch-conflicts- { \"action\": \"setPhase\", \"phase\": \"unpackPhase\" } Running phase: unpackPhase unpacking source archive /nix/store/p05bg72wb6ihkj9jjmdgzsnjifd0m0ar-source source root is source setting SOURCEDATEEPOCH to timestamp of file { \"action\": \"setPhase\", \"phase\": \"patchPhase\" } Running phase: patchPhase { \"action\": \"setPhase\", \"phase\": \"updateAutotoolsGnuConfigScriptsPhase\" } Running phase: updateAutotoolsGnuConfigScriptsPhase { \"action\": \"setPhase\", \"phase\": \"configurePhase\" } Running phase: configurePhase no configure script, doing nothing { \"action\": \"setPhase\", \"phase\": \"buildPhase\" } Running phase: buildPhase Executing pypaBuildPhase Creating a wheel... Getting build dependencies for wheel... Building wheel... Successfully built trueseeing-2.1.9-py3-none- Finished creating a wheel... Finished executing pypaBuildPhase { \"action\": \"setPhase\", \"phase\": \"pythonRuntimeDepsCheckHook\" } Running phase: pythonRuntimeDepsCheckHook Executing pythonRuntimeDepsCheck Checking runtime dependencies for trueseeing-2.1.9-py3-none- termcolor not installed </pre</details</summaryAdd 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. system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: I believe trueseeing is missing the termcolor dependency hence the failure happening during the build."}
{"_id":"doc-en-nixpkgs-2f62529c126c612a49b698881e57d6f545893e6133fd94f2be3fd1d161ab7740","title":"","text":"I can try and PR a fix but I did not try and reproduce the bug under NixOS. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nSeems a lot of other packages have broken in similar ways, mitmproxy, ioccheck, theharvester but they all fail due to missing runtime dependencies or version of modules that are not meeting constraints.\nI had the same issue with mitmproxy and found this issue because you've mentioned it here. ~git bisect for mitmproxy pointed to this commit for me: ~ Edit: apologies, I used git bisect wrongly. The first bad commit seems to be .\nThis seems relevant:\nThat shouldn't change whether or not a package builds.\nYeah, my nightly session of bisecting for pointed to , which is from . I guess affected packages do have to be fixed one-by-one manually."}
{"_id":"doc-en-nixpkgs-71597e531d9937759747d12ad184cf822e162db047d285881e6e1f3fb7493e6f","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-e6d90bf20d1858b60f2526e3943d860b50b7b7f31ae4af00f5e32d045b1d3d09","title":"","text":"shadowsocks-v2ray-plugin doesn't work anymore in nixos-unstable. Try to use it with shadowsocks-rust. Here what I have in logs: It works. If applicable, add screenshots to help explain your problem. Add any other context about the problem here.\nVersion from works.\nLooks like it got updated again: :)\ncc\nJust a note - it seems v2ray plugin is not maintained, but maybe can be used instead."}
{"_id":"doc-en-nixpkgs-0c09c87847f563d72f3134383aa6d9c0c8dba4b84ceaf5746a58a2fb20088cc0","title":"","text":"Configuration summary shows several incorrect paths: liblouis tables can probably be easily corrected, not sure what to do about cups dom socket and font directory. nixpkgs: cc\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-04e5b69b98484717fa044ca9c98bf42f822b088b10f86a77c4609f337217450a","title":"","text":"Links like do not work, since the scheme handler is not registered in the desktop entry file. Steps to reproduce the behavior: Zotero stuff to biblography to select item using a url The correct item is selected Related flathub issue: I'm using 21.11 stable, a backport would be appreciated. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --"}
{"_id":"doc-en-nixpkgs-077065f7fdba2937234e76abe5acf0b5d156c3e60429c38f9d25e4b365b1cda0","title":"","text":"Steps to reproduce the behavior: alternatively (the output is the same) Found this while trying to build on my mac I also tested this running on my nixos work computer instead of via a remote builder 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. Though the actual building is done by a remote builder with .\nFortunately it seemed OK after a quick glance, on x86_64-linux at least. Feel free to review.\nYep, this seems to have fixed it, thanks :) building a static lmdb seems to work for at least x86_64-linux and aarch64-darwin. I'll continue my adventure of trying to get murmur to build statically"}
{"_id":"doc-en-nixpkgs-689d33199430430a7c00d1a57dc47f9b833e2271fab9766610b85946636329fb","title":"","text":"twmnd does not launch because qt5 library path is missing. Install the twmn package and run twmnd. twmnd works when I manually set the LDLIBRARYPATH to <qtbase/lib. System: NixOS 16.09.931. Nix version: 1.11.4 Nixpkgs version:16.09.931.\nI noticed the same or similar thing when trying to run twmnd as a systemd user service. It just SIGABRTs: I could reproduce with Although works fine... So clearly there is some impurity in my local environment which is making twmnd work \"by accident?\" Possibly related?:"}
{"_id":"doc-en-nixpkgs-4d7caa5db7f4176a8551df8bfeb57be1d2fdc0458e6c759bcb43512e7a9a009d","title":"","text":"the attribute inside a user-level systemd service seems to be ignored. I have three observations to suggest this. With this snippet from (service details aren't important, just for concreteness) If I run , I see batterycheck.service, but no corresponding timer. If I run , I again see the .service file, but no timer file. If I remove the startAt line and run , I can see from the output that no new environment is being built. I'm pretty sure that this functionality used to work several months ago, when I created this unit definition."}
{"_id":"doc-en-nixpkgs-c2209d6bba8b3787d141e3b15de039117f31039d7ae6e2c3bdc944950ac1fc06","title":"","text":"Package name: oracle-instantclient Latest released version:21.9.0.0.0 <!-- Search your package here: --- Current version on the unstable channel:19.16.0.0.0 Current version on the stable/release channel:19.16.0.0.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! -- looks like it tried to upgrade v19 of instant client, but it is stale and not targeting v21. Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.\nIt looks like you were the last one to touch instant client.\nPackage sources:"}
{"_id":"doc-en-nixpkgs-634c8301a6630758c3449285395fa2de6102ccb6a48c59a548fee45e0417c315","title":"","text":"Describe the bug gitea fails to start due to a too restrictive systemd setup To Reproduce Looks like is a bit too restrictive. :smile:\nping\nRemoving the blacklist of and gets us past the test, I think, but there's still problems with the socket.\nJudging from this error output: it looks like it fails in prescript during in Interestingly enough, there is a right underneath that, in which does not seem to be the issue. This does not look like an issue with Gitea itself, since it fails during the service pre script. Since the and will only be run if the configuration is managed by nix, the tests pass if I set in the test config. (unfortunatly I don't know much about systemd services and especially systemd sanboxing, so I'm not sure if the information from above is useful or not)\nAny chance the service is broken too? I recently updated and service failed to start. I haven't dug into it yet... I may have seen something about a database permission issue.\nTemporary fix for someone who using bleeding-edge Gitea:\nThis doesn't solve the issue for me. I get the following output:\nPretty strange. It works for me (). You can try to disable it at all () and if it'll still not work then just change in the same way all other parameters to default values that were introduced in . p.s. probably there's must be something like a mkForceRemove, but I haven't found anything in manual.\nOk the fix is actually working, I just had an own AmbientCapabilities definition in my configuration which didn't play nicely with the new options."}
{"_id":"doc-en-nixpkgs-2c5a2b91eada13488c51abe6ace656e8b588db8dbf2498836eb6c1a5e379da82","title":"","text":"For example: fails similarly. The line that causes the failure according to my testing is: A list of some packages that didn't break: Could be this is an upstream issue.\nSo digging into it, this is an issue raised by Octave's package management system itself. Namely, this -statement from Line 80 in that file is the statement. It expects to remove a file, which is not existing. The reason the other packages did not break was because they either do not have a directory () or they actually do have a generated file (netcdf & control). You can technically solve this by adding an empty script to the directory. I manually did this, and the package built correctly again. As for why this change happened, I cannot tell. The particular statement shown did not change between 6.4.0 and 7.1.0 in the file.\nLooks like\nThat's the exact issue. Seems like we will need to wait for upstream to fix it. How does this usually get handled\nSeems like we should apply to the patch:\nThere are still 5 packages failing to build, but that is a lot fewer than before."}
{"_id":"doc-en-nixpkgs-1dcab762183c768770e447720db3974194cd855dc44dff580321c82b6885dd71","title":"","text":"When using file picker in calibre e.g. on first launch after install that pops up file picker to select library path or by clicking \"Add books\" in menu calibre will crash with error Steps to reproduce the behavior: not yet crashed - select \"Add books\" item in menu Calibre should work without issues From i figured adding to solves problem, so running it like this works: Please run and paste the result."}
{"_id":"doc-en-nixpkgs-becccc30792825d48a327fd8c49fcc1f29870dff59bb800d45a0285a0b4da11e","title":"","text":"The soundfont that is packaged in is no longer available. The URL in that file is , but that page says: \"Sorry, this is a wrong download link.\". No packages depend on this package."}
{"_id":"doc-en-nixpkgs-6173dc1eff451a2d5b5df134ea4f3485490062f56e99062c5efeedb57fb60f98","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 I'd like to work in this issue. First one with documentation so I will probably need to understand a few things first.\nThanks, let us know if you need help!\nHi thanks for picking this up. Are you still working on this? If you're stuck, you could create a draft PR so someone can help, or if you've changed your mind that's also ok.\nHi Sorry for late reply. I worked a little bit, on and off during the holidays, I do not finished yet, I had some problems during the build of the documentation, but from what I read (pandoc output) I made some mistakes during the file conversion. For now, I didn't commit, It's on my personal computer only. As the week is a little difficult, I'll see if I finish it at the weekend. (Maybe I should have asked for this issue just now, just see 14 days ago and I was like \"What ?! That was 2 weeks ago ?!\" LOL) Thanks for asking!\nHi I followed your suggestion to create a draft PR, at the moment I'm stuck in two things, the first is how to create a note and the second reference errors during the build of the documentation. For the first, pandoc created notes with the following formats: , in this case I should use the default way to create notes in markdown (using ) or wrap this in docbook way? If I remove the references that generate the error below, I can verify that using the markdown format, this note is styled differently from the rest of the documentation. And for the build errors, here is log: For this I tried per but build fails with same error. Any help is appreciated."}
{"_id":"doc-en-nixpkgs-95556984319c083effb7dd4e1f2e86ca5705f6c43099cc9c5b7dd7c9da49f523","title":"","text":"Project description Netdata agent plugin Metadata homepage URL: source URL: license: GPL 3.0 platforms: unix, linux, darwin We already do have netdata, however it seems to be built without support for the cloud agent that allows it to stream to the cloud or other netdata servers.\nI have a local checkout with some edits that allow me to build netdata with cloud support. Unfortunately they also require a change in the libwebsockets build expression. Should I open a PR to integrate my changes into nixpkgs?\nA PR would be great! I'm not a maintainer, but if they decide it's out of scope for nixpkgs, perhaps one on NUR might work - I'd try for a PR here first though\nGreat, I think having a configuration option that is per default would make sense. Maybe ?\nYeah, that seems to fall in line with the various flags present in other packages\nI marked this as stale due to inactivity. &rarr;\nUpstream has incorporated some of the suggestions in this thread, I intend to pick up on it again soon\nwhat would be needed to make this work? Perhaps I can help?\nThe newest major release of Netdata (1.30.0) includes a cloud link implementation without the need for vendored dependencies. Unfortunately, it is not currently in a reliable state because of a bug in the custom HTTPS implementation. The has already been merged into Netdata master and will be included in the next release. I plan to make a PR that enables cloud support as soon as that release is available.\nv1.31.0 dropped 12 minutes ago :) Anything I can do to help?\nThanks, I've already gotten a notification for that. Planning to make a PR when I get off work today. When my PR is done, it would be helpful if you could test my changes on your machines.\nJust FYI, I have opened the PR that enables cloud support a few days ago. If you are still interested it would be greatly appreciated if you could test if everything works for you and maybe drop a comment.\nSorry, missed this but the pr looks good! I propose we backport this to stable?"}
{"_id":"doc-en-nixpkgs-67ce9917e375fe4ee9b3878660b2b71ef010799e7464d60fd171ce01cbdfd3b8","title":"","text":"Steps to reproduce the behavior: nixos-unstable to home.packages -rebuild build Please run and paste the result."}
{"_id":"doc-en-nixpkgs-4f68c3d733b72dbbfa8e2dd5d672264ccbe9e8fed30b9861339d689a3d9e56ff","title":"","text":"Package name: organicmaps Latest released version: 2023.04.02-7Current version on the unstable channel: 2023.03.05-5 Current version on the stable/release channel: 2023.01.25-3 Notify maintainers Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-de4ed279fed0328641857308b5fef4a5519d004ef7735a2b0fc7096fb974e770","title":"","text":"Steps to reproduce the behavior: macOS: Since , this fails on macOS due to case-insensitivity (). The offending PR had no description, no reviews and no reports of tests on any platform. It was merged by the author four days after it was opened. Please run and paste the result.\nFuck MacOS and their stupid case insensitive file system.\nCan you try mv'ing the file first to another name like?"}
{"_id":"doc-en-nixpkgs-1fc45d803f783a448c27e1858db5c56ddef85ab98f378e68a62faf9ec9deea58","title":"","text":"I'm using NixOS \"/ on tmpfs\" mode, so I persist my dconf by using a module of home-manager. When I persist the state of GNOME app drawer, I need to write down desktop file name to .nix config. But currently, Android Studio's desktop contains a string of version, this because contains . Details: I also notice used in icon too, which will cause icon file contains version string, I think we can remove them too. If maintainer agrees, I will make a PR to deal with this. Also, I noticed another maintainer deleted the account: Maybe I can send him / her an E-mail for asking what happened, and drop the maintainer info."}
{"_id":"doc-en-nixpkgs-40db58e56f6986a2a35929211414ea6ccd1bc05b8da5880428bab813d730f6b6","title":"","text":"On running I get: Add to and run. system: host os: multi-user?: sandbox: version: channels(lev): channels(root): nixpkgs:\nWell, the output has at least changed a bit:\nmy pull request fixes the . It broke down because the package had moved to but requires . But according to the browser is discontinued and `firefox-esr-5.2' is marked as unsecure so I would rather advocate for removing this package altogether."}
{"_id":"doc-en-nixpkgs-68f97dbb3d8a5a919595e742ba8c8e3c46834b5c03d54f00cac440fabad291c1","title":"","text":"name: flexoptix-app current version: 5.11.0 desired version: 5.12.1 maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-2aba8e98b3beab88f4ab05f7e80189db34e21f80dd8b743a5ca4d09e92bd592e","title":"","text":"Enabling fails with: Steps to reproduce the behavior: and enable Nextcloud The notify_push service starts. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nHm, I thought I had tested that. Can you test if it works if you modify the module to drop the parameters from the script where it executes ?\nDoesn't work either. I don't know PHP, but it seems that is unable to parse the inline function.\nYeah, notify_push is written in rust and doesn't actually execute php to parse the config, which is why this doesn't work.\nUpon further investigation, dropping only works. Dropping the whole result a failure with: It needs an option to set .\ncan be set like . Maybe we should transition away from putting a function into the nextcloud config and just modify the file in the setup service.\nit works, but if the Redis URL has a password it ends up in the Nix store.\nI have the same and I can't reproduce this issue.\ndo you have the line in your ? I think the reason is because I'm using an external DB and S3 storage.\nIf you have passwords used in the config the nixos module does inject that lookup function. In the initial PR of notifypush was already a discussion how to handle that, and there was already a suggestion to drop I dont remember why it was not done there, i basically withed to non password authentication (as everything is running on the same machine anyways, so using the socket solved the issue back then, so i forgot about it).\nnope, I am using socket authentication."}
{"_id":"doc-en-nixpkgs-cc70e5a0a108c3db0bc6a0c319c8d4c4c85d6d1d8e5bd8c7d88f6eecb7f4b9e1","title":"","text":"Hayabusa is a swift rust fetch program. <!-- Describe the project a little: --Metadata homepage URL: source URL: license: Attribution-NonCommercial-NoDerivatives 4.0 International platforms: linux, windows Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-09f5f19f3f0955676d720ca9f02bc7ef9447115531a19cb2ce7856f9488acaf4","title":"","text":"After switching from 21.11 to unstable and a clean reboot ts3client crashes as soon as it tries to access the microphone. Steps to reproduce the behavior: to current unstable ts3client to a server or click Options -Recording -Test Not crash when using microphone Attached the coredump i am receiving. I am using pipewire in this context, but i can't circumscribe the issue on pipewire as other applications still work and are able to record without issues, also switching pipewire out and use pulseaudio seem not to solve the issue. I tried to overlay the package with libForQt512 (just playing around with it) as one of the differences between stable and unstable are version changes on qt libraries. But that did not fix anything. I have also tried the flatpack version, to check it there is something wrong with my pipewire config, but the flatpack version runs fine. Switching back the nixpkg from unstable to 21.11 and rebooting fixes the issue, so at least would tackle it down to changes related with changes in unstable. As stable and unstable ship the same ts3client version it has to be somehow related in between, or (hopefully not) just on my machine. I would not rule out that the issue is somewhere on my side. Please run and paste the result.\nRunning the version of a previous nixpkgs works just fine, even with an up-to-date environment. It must be a problem with the ts3 drv itself. I'll hopefully have time to run a bisect later.\nBad is which is a staging-next merge. Bisecting staging-next now...\nBad is . (Note: Injecting a cached qtwebengine saves a lot of time here and doesn't falsify results.)"}
{"_id":"doc-en-nixpkgs-51d79b6906888e8be9beb2cddaaa72eba6055f3218ed204b76de18b636a94075","title":"","text":"crackmapexec fails to run on the unstable branch. Full backtrace : Steps to reproduce the behavior: Should be marked as broken for python 3.12 and above due to not being maintained anymore, it should be recommended to use the maintained fork . If applicable, add screenshots to help explain your problem. I may PR a proper fix later if I find time to do so <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI don't know if removal was the best choice for this tool but maybe has all the features that had so it's alright. It's just that I'm not aware if there are any bugs that are not in that are in but I understand why removal makes sense since later we'll move onto later version of Python such as 3.13 and further more\nAs is a fork, I guess that the feature set is comparable or even bigger in the meantime. is still available for 24.05 and could still be used after 24.11 with some magic.\nI ran into this issue where didn't have it, it is just a minor issue so it's alright on my side, but not sure if there will be any more issues I'll ran into later :"}
{"_id":"doc-en-nixpkgs-e0c4426a0773fbbc0d8d7bf3e1d0c754c00f6b2a591a91df363e14b72250f26a","title":"","text":"CMake seems to use ps command internally, but looks like CMake in nix on darwin can not find ps command, so it complains with message \"sh: ps: command not found.\" (very many times) Although this does not seem to harm build, it is desirable if this can be solved quite easily by some simple patch.\nI found a similar problem report in macports. Shall we include /bin/ps visible in cmake environment in darwin systems?\nIs there no way to hard-code the path of into CMake?\nisn't actually in .\nThe relevant code in cmake is I believe. The package on contains the Apple ps. I'll likely get it building as part of my revamp of the darwin stdenv, and if I'm feeling particularly charitable I might even hook it into cmake. In the mean time, I'd probably just leave this alone, since I don't think we're far off from having a sensible darwin stdenv.\nWe definitely can't use procps on Darwin since it doesn't have /proc. Also, these warnings are not always harmless: MySQL's startup scripts won't work unless it has ps in scope during the build process. Right now the workaround is this\nThis was fixed as part of the new darwin stdenv."}
{"_id":"doc-en-nixpkgs-fc30d8151ee985a2f7fe0067e714726fb58587c14b545d8d64c447a78621701e","title":"","text":", CVSSv3=9.8 (nixos-20.09) Scanned versions: nixos-20.09: . Cc"}
{"_id":"doc-en-nixpkgs-5f7400bb2adc9ec0f4ee239d1301330d056f85099f4a144044fdd35fb01ca0e6","title":"","text":"We currently use version and export it to The help page suggests there is version 201 and the file name should be : () The change will also likely need a hwdb file according to: This is apparently required to support cameras that use SCSI tunneling support: cc (maintainer) ( the udev file)\nFor reference Fedora"}
{"_id":"doc-en-nixpkgs-7a3a997ecf476bd61de3d81b80a414de7bfc71c73f636c917efbde739699fa12","title":"","text":"Describe the bug , which is depended on by , has been failing to build on both Linux and macOS since / , perhaps since was updated in . of a contemporary build attempt indicate that the immediate problem is that the current version of tokenizers depends on a vendored copy of v0.10.0 of the parkinglot crate, via its cargoDeps dependency. Further research suggests that the -issue reported in the logs was fixed in Amanieu/parkinglot which it looks like is included in v0.10.1 and successors. As a result, I think that someone just needs to refresh tokenizers' (possibly by way of simply updating the package) or, failing that, to try to get it to build with an older version of . (That said, I have yet to test these changes myself, so I don't know if they are truly enough or if additional modifications are required.) To Reproduce Expected behavior The build should succeed. Notify maintainers (also /cc (since this looks like an interaction with and since there is a commit linked to above updating in the scmdiff from the last successful build to the first failing build, per hydra.) Metadata $ nix-shell -p nix-info --run \"nix-info -m\" system: host os: multi-user?: sandbox: version: channels(...): nixpkgs: Maintainer information:\nThanks for the bug report (still hoping for Hydra notifications some day)! The linked PR should fix this issue. I am also working on some other PRs to make transformers work on Linux/AArch64 and Darwin/x86_64."}
{"_id":"doc-en-nixpkgs-cc467fc04107f415b0616bc6f6a2210e2c2d0017e11262ec7d14a0ccb1638ee1","title":"","text":"I'm told a lot of people favor Paul Phillips' SBT wrapper over vanilla SBT. We probably ought to have a package for it.\nMinus the parts where it auto-downloads sbt for you, I expect\nMmm, I don't know. Isn't it kind of important to be able to auto-download the appropriate version of sbt for each project?\nMaybe? Seems hard to keep it Nix-flavored though, given that it wants to retrieve unhashed versions from the outside. I guess we could either patch it to call out to nix to download scala and sbt, or we could leave it alone and users can decide whether they care about Nix-like behavior here."}
{"_id":"doc-en-nixpkgs-7e024aebd2caec98aebc1e3a2dd99193fc3f9ecd386110c4d9283ff2d42f527a","title":"","text":"Steps to reproduce the behavior: udocker against the master branch of Nixpkgs () 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-6abd93a6c8ee1aa4d8c3ee0e1f1e8751d73c5251baef3b3aad6379d153f58fa7","title":"","text":"Steps to reproduce the behavior: from I guess is too new? :) <!-- 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-9d1af6dcb84b578af219087f08ea9d798d86137724df2d5efff3a86032852ad1","title":"","text":"This patch is needed to build texlive but the patch can't be downloaded. It doesn't seem to be there in the Arch Linux repo anymore. I found the desired file at a different URL here: We probably need to find/create a reliable place to download this patch?\nProbably should just add into nixpkgs instead of fetching it.\nanother alternative is add the commit rev which seems to have the same hash"}
{"_id":"doc-en-nixpkgs-5894d9f573893558848ca0cd95926ad4ca8609ca15eb9ec0674e4609bdc1c279","title":"","text":"Describe the bug on macos fails because it can't find . To Reproduce Steps to reproduce the behavior: lean: leanprover. It bails out with OSX 'readlink' command does not support option '-f', please install 'greadlink'. If you use 'brew', you can install 'greadlink' using 'brew install coreutils' Expected behavior No errors. Additional context This is because leanpkg has an : It can be worked around presently by installing . Options I see for fixing the package: depend on on darwin patch out this check, since (presumably) nix provides the GNU anyway fix this upstream by changing the check to not fail under nix (e.g. by having an explicit check for the argument instead of relying on command name), and pull in the fixed version Metadata system: host os: multi-user?: sandbox: version: channels(rob): nixpkgs:\nSounds most easiest to implement and maintain."}
{"_id":"doc-en-nixpkgs-196e289fe36e8483e1dd263ce093a711492d2834b1307af5b9e03ca9130887a1","title":"","text":"According to , Django 2.0 will reach EOL in April 2019, i.e. just after the release of 19.03. Better not include it in the first place. cc\nagreed. For 19.03 we will only support 1.11 and 2.1 (and probably port 2.2 when it gets available)."}
{"_id":"doc-en-nixpkgs-1343355cb2b3ad6bdb8e5f8ad4864219ff39ed52b0343bcae37d1c8801a7c6fa","title":"","text":"Package name: proton-pass Latest released version: 1.22.0 <!-- Search your package here: --- Current version on the unstable channel: 1.20.2 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]:"}
{"_id":"doc-en-nixpkgs-c4fccd6b3b4dad98f527381d7fc26f64d540a95a807e18d0f5e5c1120f1da1e2","title":"","text":"Package name: adbfs-rootless Latest released version: 2023-03-21 <!-- Search your package here: --- Current version on the unstable channel: 2016-10-02 Current version on the stable/release channel: 2016-10-02 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR."}
{"_id":"doc-en-nixpkgs-52b64353fb4b0512b17e3ae83a4a162e76cf01efa5f69ab3d27ad117d1e65827","title":"","text":"Steps to reproduce the behavior: bsddb3 Python312packages Python 3.12 seems to have removed distutils package but it should be inside setuptools module according Sadly this package is a dependency of several Python packages. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- PS: the package has not maintainers. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nIf bsddb imports distutils, then it is not compatible with Python 3.12. This is something for upstream to solve, but is unlikely to happen:\nSo all those packages that depend on this package, like must be labeled as broken?\nScrapy claims to support Python 3.12. Are you sure bsddb3 is still in their dependency chain?\nIm not sure about that.\nI see this merged PR that probably should solve the issue on scrapy... but about bsddb3, it must be removed from python 3.12 package group...\ndistutils is used in the test of bsddb3 to get the platform data, we patched this behavior in the following PR\nIsn't It better to patch the test to avoid using distutils but still having it run ?"}
{"_id":"doc-en-nixpkgs-f26f5565a5dc4e97a7711f329fb878790795ef9fd5aebf0e063582f9c080f690","title":"","text":"Project description Metadata homepage URL: source URL: license: bsd3 platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-3c7c4d845f6eea1c0e1f4eb444e289e41fcaaa0a1f0754f40a2e7d6b8f0549f8","title":"","text":"Failed to cross compile batctl package for riscv64 using nixpkgs on Ubuntu. Nix is not able to meat the dependency for the package: While the package successfully cross compiles on a NixOS* machine. Steps to reproduce the behavior: nix environment on a Ubuntu machine. and cross compile batctl package for riscv64. Below is the command I am using: attached nix-info not availble on Ubuntu\ncan you give the version of nix and the revision of nixpkgs (it might be in a file called .git-revision).\nis the sandbox enabled, if they're at the same rev\nTurns out I couldn't reproduce it because my machine has riscv emulation enabled, the makefile is calling a riscv version of pkg-config. I'm testing a fix to the problem at the moment"}
{"_id":"doc-en-nixpkgs-cbfa0a8ffcb688ba98797584ec2776b87df1762d4300cb909f0d1bafe0ddd196","title":"","text":"I note that the package sets in .[(1)] says [(2)] that the reason to disable \"JBIG\" is patent concerns, that disabling it removes support for many printers, and that \"The patent will expire on April 4, 2012\". Given the last, need we still disable this feature? [(1)]: [(2)]:\nI don't think so. openSUSE enabled it, too. Other distributions might have done the same, not sure.\nA PR that implements this change request would be very welcome. I'd rather not have this issue lying around, though, without someone having committed to actually work on it."}
{"_id":"doc-en-nixpkgs-7dfaa1452b92bc9fd0001fef64137bfceb8666d021913569b3131a2ca6c5813c","title":"","text":"Steps to reproduce the behavior: pkgs.transmission to your environment.systemPackages (or use = true;) build will fail when trying to download a file that does not exist That does not seem to exist (I think, sorry for the @ otherwise) <!-- 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-27dd10b9878cb6e87aaff678187427562c8b290ac10b3b3ae8b2989ddbeec708","title":"","text":"Steps to reproduce the behavior: nix on x86_64-darwin experimental features nix-command and flakes to install nushell v0.75.0 via . Please run and paste the result.\nI can confirm the bug, the following PR could resolve it.\nthat is great news! I am hopeful that can resolve it. I see that you marked this as resolved by . However, this does not seem to have resolved the issue for me. I am still receiving the same error when trying to build :\nThe ofborg test did pass, see Maybe you have to build it on master? Also, I don't think will help, as the author of that PR.\nHmm, after upgrading nix and updating my nixpkgs-unstable channel, I'm still receiving the same error.\nYou have to wait for the commit to arrive on nixpkgs-unstable.\nThank you your PR resolved it. the fix is in the nixpkgs-unstable channel. Much appreciated!"}
{"_id":"doc-en-nixpkgs-bcd5f7b8a9f3ef8b1f0386757802bf34e723e6f39683742020905b8a97515f7f","title":"","text":", CVSSv3=9.8 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc\nSee also: , ,"}
{"_id":"doc-en-nixpkgs-1a40d5cad3674fdefdb3a2f4d7e8f27959dc64f7ef5de7b49a26c08b46379aa3","title":"","text":", CVSSv3=9.8 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc Cc\nSee also:"}
{"_id":"doc-en-nixpkgs-8e3c3a014ce8b0b9c512b0d50d2cc46fc98c636ee833e2c61b803c24aec5ef45","title":"","text":", CVSSv3=7.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc Cc"}
{"_id":"doc-en-nixpkgs-f76cd9d5de6e373adba957d50a6c65ec35f6bdb1ddd7bcd22610ce6fd07dfd30","title":"","text":", CVSSv3=9.8 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.0 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc Cc\nSee also: ,"}
{"_id":"doc-en-nixpkgs-bbb777404eccef915341b0753c73014a39e52dd64af532aa74f95b0c4cf157c3","title":"","text":", CVSSv3=9.8 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.\nSee also:"}
{"_id":"doc-en-nixpkgs-4e647841492bd73f9c39dbc7dbcf823db6591f7d787da400626919e242347cae","title":"","text":", CVSSv3=9.8 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives."}
{"_id":"doc-en-nixpkgs-830a1a4dee0c487771540879199e343727bf0e4fe33d8a554fe9f1a528bafd7d","title":"","text":", CVSSv3=9.8 (nixos-20.03) CVSSv3=9.8 (nixos-20.03) CVSSv3=9.8 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=7.5 (nixos-20.03) CVSSv3=5.9 (nixos-20.03) CVSSv3=5.5 (nixos-20.03) CVSSv3=5.3 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives.\nSee also:"}
{"_id":"doc-en-nixpkgs-697603c4b3fcfd3ea75f3e3e320dfb0605ab7b36e519ae726758d38df9c994d6","title":"","text":", CVSSv3=9.8 (nixos-19.09) CVSSv3=9.8 (nixos-19.09) CVSSv3=9.8 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09, nixos-unstable) CVSSv3=7.5 (nixos-19.09) CVSSv3=5.9 (nixos-19.09) CVSSv3=5.5 (nixos-19.09) CVSSv3=5.3 (nixos-19.09, nixos-unstable) Scanned versions: nixos-19.09: ; nixos-unstable: . May contain false positives.\nSee also:\n30.1 is also the default version in 20.03 ATM."}
{"_id":"doc-en-nixpkgs-dd1d25852faf8861dca8d14638866989ec9e5523ad6b59575b3389c43f9c2dc0","title":"","text":"I can't figure out which are the problematic lines! 5 and 9 do not seem to be any valid lines considering the error descriptions, or they're the lines in the expanded output(??) - I don't get it. I hope it wasn't something I did here: this /etc/nixos/nixpkgs/ git pull (this was last: ) sudo -i nixos-rebuild switch --fallback System: (Flounder) Nix version: nix-env (Nix) 1.11.2 Nixpkgs version: \"\""}
{"_id":"doc-en-nixpkgs-0b6fd5ab65f29ff3ae4422f5966e788bcacacf49f0dc72c096d90fbb27ec550a","title":"","text":"Describe the bug Slicing fails on latest Cura (4.3). When trying to slice any model the slicing progress bar will get stuck at about ~20%. I tried various printer presets and the problem persists. From looking at the logs it seems like that CuraEngine is unable to get a value for 'machineheatedbuildvolume', which was To Reproduce Steps to reproduce the behavior: any printer preset any model Slice Cura log relevant parts to the problem seem to be aditional information it seems like , from the nix package, indeed is missing the new setting. For comparison the upstream definition. Metadata Maintainer information:"}
{"_id":"doc-en-nixpkgs-ffaf83d7a9a81f3b85c8b2f0a048edd01984f790b34d903d09829f0be81fb1e1","title":"","text":"name: flutter current version: 2.5.1 desired version: 2.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.\ndone on"}
{"_id":"doc-en-nixpkgs-15f01cf31e2a41985717625b2342c9e9e1e9f90578e288eaec7e586448964fd6","title":"","text":"Project description PreviewQt is a simple application for previewing all kinds of files, based on Qt/QML, published as open-source and completely free. Metadata homepage URL: source URL: license: gpl2+ platforms: linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-bc3656d9358b8fa55e357a96ecdb3eb4184019e2de1adf017d39b83f1fac7fae","title":"","text":"Input methods based on do not work as of , at least on my machine as it is now. Upstream, I think the change comes from , which made start using . Other IBus input methods still work (mozc, hangul, Anthy). It feels as if this should have an easy solution amounting to “do what worked for other packages using ”, but I can't work out what it is that they do that makes them work. It's also believable that from is not being run. 1) 2) Switch to an -base input method (example: from ). Then, the input method is not changed, and the rest of the output is: Alternatively: 1) 2) Try to open the preferences for an -based input method. No preferences are shown. The following error message is printed. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nSo, adding to stops the error message, but preference dialogs still do not show and all of the problems with actually using remain.\nHow did you install and activate the input method? i18n.inputMethod.enabled = \"ibus\"; = with ; [ table ]; does not seem to be enough.\nChange to (ibus-table acts like a framework within a framework, and provides some actual input methods using it). Then, use -Input Method -Add -More... -Others -IPA-X-SAMPA (and maybe another to see the switching behaviour). Then, switch using the key combination from the preferences (I forget what the default is; maybe Ctrl-space). Expected behaviour from IPA-X-SAMPA includes ↦ and ↦ .\nHave you managed to reproduce this problem?\nI can confirm your observations in Maybe this could be the culprit:\nI've found what appears to be a solution, but it's in some sense weird. Looking at other input methods, they seem to use rather than . Replacing the latter with the former on seems to fix the issue. I have no idea, though, why isn't broken on other platforms. is the new package description."}
{"_id":"doc-en-nixpkgs-b6100568f00d5891fa8845fa9b84840a5d3939fde2b1bcc1428b00d4cf5b882e","title":"","text":"Describe the bug pciutils is using a really old file which doesn't include any definitions for AMD Radeon 6800 XT cards. When running you get the following output If you get a newer version of the file from https://pci- which update-pciids script in package normally updates (but is disabled in nix package). You get the following: Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(wil): nixpkgs: Maintainer information:\nShould also mention when running strace on lspci it reads the file from /nix/store/464020m9r6mhsivgp9v1bhkyzz5pa0gq-pciutils- and not from hwdata like I originally thought.\nWould it make sense to make lspci depend on hwdata and then use from hwdata? cc'ing (who is listed as shadow maintainer of pciutils)\nHmm, makes sense. Except that seems to be in significantly more closures than , so depending on the extra 6+ MB of other data seems significant. Perhaps make put it into a separate output? Or could just copy it as a quick work-around (that's free for people with )\nOh, we can't \"just\" make multi-output, as it's a fixed-output derivation, but we could fake it through multiple derivations. Maybe just the work-around for simplicity then?\nI think the work-around is actually pretty sensible. I'll prepare a pull request :-) Update: Did so, . Once both and are merged, our issue should be resolved.\nThanks for fixing that :). I tried your two updates on my machine and it appears to be resolved. Closing the issue out. Now we just wait for this to get into unstable :)."}
{"_id":"doc-en-nixpkgs-77346cabb9ceabea31bb1116e536804ba6df2b0a78f7d60c9ba18faf79d17680","title":"","text":"See We should probably remove some of the Eclipse versions we have as we seem to be carrying lots of them. If there are objections to removing, we should at the very least clean up this area.\nyou can probably close this one now?"}
{"_id":"doc-en-nixpkgs-ba80ad9f97328b434680c3a5f5ffdab40c584a06e5960dd45ff1b4a42c0732ba","title":"","text":"In is installed if it exists, and the install siliently continues if it doesn't exist. In the service the script is executed unconditionally, even if the script doesn't exist. That breaks suspend with the 465 beta driver, because there the script does not exist. I think we should [ ] fail loudly if it doesn't exist (so that if you close the laptop and put it in a bag, it doesn't catch fire) [ ] figure out where the script went / what the replacement is. CC\nI will look into this in an hour or two, have a thing to do soon."}
{"_id":"doc-en-nixpkgs-95d6d2e236645e727713b5eceae2892d44fcc5d2745be6fde47a808131b3a36b","title":"","text":"Steps to reproduce the behavior: -rebuild of NixOS with GNOME Known workaround: reverting ( ) Please run and paste the result.\nOpened an issue but unsure about what is going on / how to fix other than reverting that commit. I don't know that much nix :C\ndoes fix the issue for you?\nIt does, thanks for the fix. :3"}
{"_id":"doc-en-nixpkgs-8b0e47b29e8a864ff86c6bb1f55dee4032d8215c00cac6fa9b71cb6d26425a4b","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: texlive- current version: 2.9.1 desired version: 2.10.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.\nCan you tell a bit about your use case?\nI knew I forgot something! :smile: I'm using emacs + org-mode, and am using the =unicode-math= package with =stix2-otf= along with lualatex. In order to preview equations, the pipeline goes /However/, =dvisvgm= 2.9.1 doesn't understand the extended font data that lualatex emits (see the comments in ), and so produces corrupt output images. This was fixed in 2.10.1, which was recently released and pushed to CTAN."}
{"_id":"doc-en-nixpkgs-4eee1ebf7b6d6ea8e5296b18b1d275a4ca905e210a9f121f7265385584190cc9","title":"","text":"Describe the bug It is not possible to delete files in atom. To Reproduce Steps to reproduce the behavior: to delete a file Expected behavior This action should not result in an error. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\ngvfs-trash has been removed for a few years () after several years of deprecation period. For the atom issue, this is likely a duplicate of\nAh thank you for this, I will update the title and description accordingly\nYou can try installing globally. That contains command, which is ’s successor and most programs support it. Not sure about Atom though."}
{"_id":"doc-en-nixpkgs-cc8511bb0214c7a8471708bb1bf84596610c2b7ebb353eb0b624d9952163a3dd","title":"","text":"Project description HTTP, HTTP2, HTTPS, Websocket debugging proxy Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-9cdd501cb81c58093b5ee3879fc53345c221393cfa4c29b7312f04347d0f52c3","title":"","text":"The application is crashing when trying to open a file Steps to reproduce the behavior: to open a repository application crashes Supposed to open a file exploer Using KDE Plasma 5 under wayland <!-- 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’m running Gnome 45 under Wayland and the « Open a Repository » feature is working fine. I’ll give a look with KDE Plasma 5 when I have some time.\nsame here\nAs in it it works or it does not?\nnot work kde + wayland"}
{"_id":"doc-en-nixpkgs-a3902d4ff4e5ac8373f8cbe0fbb4e7c701ee97e3e901d107f97bc4992d66afec","title":"","text":"Describe the bug The file has this function: Since this is called for every dependency, we get quadratic complexity. This may cause a non-trivial slowdown - building digikam I noticed it takes a few seconds just to get to , but there might be other causes. It also causes huge amounts of debug output when you add a to (about 600 MB for digikam). We should use an associative array for this like stdenv does (see ). Notify maintainers\nWe also need to do this in the setup hook for paths seen by .\nI marked this as stale due to inactivity. &rarr;\nNot stale.\nFixed in ."}
{"_id":"doc-en-nixpkgs-4be804e9a43fbb8c440d4ceba8336433fcb43237f18b6b6dfcec197260d8884b","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: materia-kde-theme <!-- 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: desired version: <!-- 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-45784e5db4bd80decfb6429067c95d08a757a8aa722445ca2698279e8fc98e37","title":"","text":"Package name: snipaste Latest released version: 2.9.2-Beta <!-- Search your package here: --- Current version on the unstable channel: 2.9-Beta2 Current version on the stable/release channel: n/a <!-- 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-9831826e4a143e058bec631e0d61c7c228ceea01a5a132964e4dc62eb45aa061","title":"","text":"tests pass, while tests fail with: Official Hydra sees the same thing: with their Travis setup. (That is a build of a recent commit, but I still see the same failures after pointing at a checkout of ) Does anyone have any ideas? With nixpkgs master,\nSee scrapinghub/dateparser, scrapinghub/dateparser and scrapinghub/dateparser.\nAs long as this problem remains, the best thing to do is using for affected application. Switching to should be done in commits that don't change anything else and that reference this issue in their commit message so that they can easily be reverted. Simply skipping the tests does not make much sense since these are real incompatibilities."}
{"_id":"doc-en-nixpkgs-729519a7bdb8a927bd4f98ab62a7c81a6d059094275ad154bd9016cd0b4a6ca2","title":"","text":"Project description is an audio processing program with an interactive mode. Also has a LADSPA frontend. Metadata homepage URL: source URL: license: isc platforms: linux"}
{"_id":"doc-en-nixpkgs-7d593f895b49fe9f58e675708c53d749d5d78b9e53e2d717bdf9ec7120718208","title":"","text":"Describe the bug fails on Darwin. To Reproduce Steps to reproduce the behavior: Expected behavior Package builds Additional context Error log: <details<summaryError log</summary</detailsMetadata Please run and paste the result. host os: multi-user?: sandbox: version: channels(yl): nixpkgs: Maintainer information: Possibly related to\nOn the master branch, I removed the derivation from the nix store with and I built it without substitutes; failed with the same message. This is not caused by , but help me discover it due to the update of the requests python package.\nmaintainer:\nI don't have a way to test on joblib for darwin so this is why I didn't have input on this PR. Is there an easy way to test nixpkgs on darwin? Hackintosh via kvm?\nThere is that works with some tweaking but I wouldn't describe it as easy. Another option is to ask @ GrahamcOfBorg to do the builds on the PR if there are not too many iterations to do."}
{"_id":"doc-en-nixpkgs-54aaac9593ac002416ab3c45f9eb6d5216fd8457af126cd19c7e0128d8518111","title":"","text":"The nixopsUnstable version is not set correctly. It should show the version. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --"}
{"_id":"doc-en-nixpkgs-3cddee3582fd8097d3b37018f623cdb8082b087b4c4ed806937e39ebe243e0c2","title":"","text":"The symlinking between the multiple outputs of seems to prevent it from installing. I was looking to install it to have the dig command available. - System: 17.03pre94050. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: \"17.03pre94050.\"\n11.4 still doesn't contain :-( How could we have that as default in 16.09? I consider it quite an important feature for + multiple outputs. would you be against porting that PR to 1.11.5 and making that default in 16.09 and master?\n+1 for a 1.11.5 Nix release in general :)\nSince this seems to be an issue for multiple packages, I am raising the severity on here.\nLooks like the same kind of issue as So +1 for Nix 1.11.5 on NixOS 16.09, if that's what it takes to fix this.\nping again about nix-1.11.5 (my comment above)."}
{"_id":"doc-en-nixpkgs-3c4471bc2b4bf1d694d111d27075db18837b2466be2a58f69ac9c600fb264c97","title":"","text":"Describe the bug When I try to preview videos like .mp4 or webm in Nautilus using Sushi, it says \"Your GStreamer installation is missing a plug-in\". To Reproduce Steps to reproduce the behavior: NixOS with Gnome3 desktop space on a video file in Nautilus Additional context It's possible that there's some configuration in my homedir that makes it break, since I have the same homedir that I had under other Linux installs, not sure how to find it however. outputs Notify maintainers maybe? Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(wmertens): channels(root): nixpkgs: Maintainer information:\nWould need to add here, I think.\nthat makes sense - it seems like I would like the bad and the ugly too. How about a nixpkgs configuration setting that decides which plugin sets to load, and having plugins-base include them? That should make it backwards-compatible.\nMost of them depend on base so that would be a dependency cycle. Also we would need to move the wrappers into a separate derivation or we would have to rebuild everything. Alternately, you can set environment variable (I believe some NixOS module does that). Not a fan but it should work provided some ABI break does not sneak in.\nI marked this as stale due to inactivity. &rarr;\nStill a problem\nI marked this as stale due to inactivity. &rarr;\nif sushi is not a dependent of any package then why would we have to rebuild everything? What do you mean by everything? Perhaps until a separate wrapper derivation is composed we can add a configuration option to the nixos module that would add these gstreamer to it if needed. Also, doesn't work at all for me nowadays, I think since Gnome 41.\nI was replying to Wout’s question above regarding a general solution pulling extra plug-ins into gst-plugins-base. For now, I would be fine with adding everything unconditionally to sushi as mentioned in I must have forgotten to test it during the update when I removed libmusicbrainz but forgot to add libsoup: Could you try"}
{"_id":"doc-en-nixpkgs-46a725d5b2fe25ac24e057c26348dbf83c860b00a40b7866886cf11da0d8e95e","title":"","text":"When using filters, look for them in and co. Instead it should look for it in for example. Setting the environment variable can work around that issue: . But it would be nice to have it work out of the box. Result: System: 17.03.1556. (Gorilla)"}
{"_id":"doc-en-nixpkgs-48bcc478953a3fec5e8cebf4d6f7f23a41c1686d043ef0f990e69f40bf251b4e","title":"","text":"Xpra supports forwarding invocations from the server to the client. The Xpra client defaults to hardcoding as the command to invoke on the client, which does not exist in NixOS. This bug does not impact hosts other than NixOS. Steps to reproduce the behavior: somehow. The Xpra client should invoke the local . N/A. This could be fixed by setting the open command to just , but it might match the intent better to change it to something like perhaps. Presumably, the point of doing it this way is to avoid any other copies of that might appear on the , e.g. Xpra's own. I suppose we can't really rely on to exist: even if we could on NixOS, we can't on other Linux distributions running Nix, where might make more sense. It seems to me that the best compromise, then, is to hardcode a path to copy of and users can override this using the option if needed. The open command that Xpra uses is configurable on the client-side, but the default is set as a platform-specific variable. On Linux, it is set in . Because there are separate values for both Windows and Darwin hosts, patching the value to shouldn't ever break them (but of course it should still be a Linux-specific patch, otherwise it unnecessarily brings into the closure.) Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-d93fad39230dce3adc53b55f21983f136c40177f5a6b3c9457980e5dad61b510","title":"","text":"Julia 1.5 is out, see: and we don't have it packaged. More over, see how defines our other Julias: Several issues: is pointing to a TLS version which is old IMO. Certainly there are breaking changes seen in , but since Nixpkgs is a somewhat rolling release distro, are we going to keep these older versions and default to them for ever? I've once tried to reach for the community to hear if there's a strict policy regarding such scenarios, but Anyway, I'd like to propose a change that will keep only the LTS version and the latest - currently 1.4, and perhaps make the attribute , point to the latest. Any thoughts from maintainers or users? cc\nAlso, now I noticed all of our Julias fail to build, e.g:\nI agree. And the 1.5 release candidates are out, so this will become the latest version in the near future. Last time I looked, the package built the same deps for all versions, including 0.7. In versions 1.0 and later, there are actually fewer dependencies (e.g. arpack and fftw have been dropped), so the package should be cleaned up to not include these unnecessary libraries in the build. I also think the default version should be the latest version (i.e., unless somebody explicitly installs julia-1-lts, they should get the latest).\nOK I'm glad I have your support. I'll let this issue stay open for a while and hopefully I'll be able to take care of this a month or so from now.\ncc\nBack when Julia tests were not so messed up, I think there was often 1 previous version. I guess with 1.3 needing overriding to no tests, it is fine to just have julia-1-lts and Julia 1.4 as julia once Julia 1.4 gets built fine with some tests.\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nThis issue has been mentioned on NixOS Discourse. There might be relevant details there:\nHaven't had a lot of time to work on julia in nixpkgs, so just posting this as a FYI."}
{"_id":"doc-en-nixpkgs-61fa69788cd356eb3d765932d7d53d2ae52b14e65f22154abf936fc69c237890","title":"","text":"We used multiple versions of julia at work, but we use a custom derivation, similar to this: We also do not run the tests, but in general it has been working great. Previously we also used the binary builds patched with patchelf, as there were some differences in the structure of the results of the vanilla binary build provided by julia and what we got when building from source. We gave up on using 'system' libraries, and build the releases that julia provides, as julia is very specific in the versions for its dependencies (LLVM patches mostly).\nI tried to use that tarball in order to write a derivation from scratch. Here's my attempt: It fails with: Naturally I didn't further attempt to add curl or wget to the inputs, as that would fail in a sandbox as well. I've opened an issue upstream: complaining that that tarball doesn't really contain all dependencies.\nI ran with sandbox enabled, and the expression I linked with works for me. So I think it is fine to just add curl to the deps, as with the full tarball, it isn't actually used.\nThere is another approach to avoid running tests: using precompiled binary. I tried downloading the 1.4.2 binary from and then afterward ran on the binary, then I got a running Julia interpreter just like that.\nWe did the same for a while using code similar to this: Unfortunately, we actually sometimes need to patch Julia, so we switched to the julia expressions from source, that I posted earlier.\nThanks that expression works well thanks to . I'm testing it now.\nOK so after a long build, I got a working Julia derivation with these references: And this closure size: Which I must say it is satisfying. The question is, is this how we'd want it to be built? Using all of their dependencies and practically non of ours? Some of their dependencies are required to be patched, according to and they also specify that using the OS' libraries is not officially supported? Anyway I'd happy to get help on deciding this.\ndoes this lead to Julia tests passing? I think for every dependency they patch, it is OK to just use their patched version. I guess it could be nice to use a separate build unpatched (but using the exact same version sounds like a likely restriction), but whatever dependency does not work right away can be switched to bundled."}
{"_id":"doc-en-nixpkgs-de71f395381d75e18fc392c4c29991193ac737a43afd071e4b21b48ae6caa16d","title":"","text":"I think it did, I've set and the build passed but I haven't inspected the log much, but here it is: Currently produces this log but there's no PR yet as I think there are many makeFlags that should probably be set as well. If anyone feels confident to open a PR with this feel free to ping me for a review. I agree with the idea, but what's bothering me is that it's not absolutely clear what versions are patched and which are not - the docs vs what's actually found in is not totally inline. Also, it seems that some of the patches are old, and were suggested upstream (to the libraries) but they weren't merged there for some reason. I'm still investigating, See My current target is to decide what libraries to use our version vs their version, with the preference to use our version, in order to hopefully reduce closure size due to sharing shared libraries. The idea is to decide this by checking whether the libraries have included the patch Julia suggests, and then whether the library's maintainer has released a new version that includes Julia's maintainers' patch, and whether we ship that new version.\ndoes this lead to Julia tests passing? I think this log is cut short before the interesting part…\nI've uploaded it here:\nHmmm. Reading the log does not convince me the tests were run… Pity.\nSince 1.5 was just released, the title should probably be updated to be 1.5.\nDownside with the patching approach, is users lose the ability to compile against MKL, which has HUGE performance increase (last I saw showed that MKL was ~4x faster at matrix multiplication!!). Would need to also package JuliaPro to get MKL. Of course, anything working nothing working, although would be a shame to lose compilation options.\nSays\nThanks garrison, I saw that, but I have a feeling it won't play nicely with Nix...although if we go patching route, perhaps could do that during buildPhase\nAre you concerned about specifically or all packages that use BinaryBuilder? There are a lot of them. More on this at\nAs I understand binary builder, that all happens in userspace, but modifies , which is in /nix/store\nThe installation instructions for do not seem to require root. My guess is that it stores the modified sysimage somewhere in ."}
{"_id":"doc-en-nixpkgs-0150e9ae21d749ba3271df659a10e654c7992e3e66e2879aac586be11421a0db","title":"","text":"Am I wrong?\nI just tried it with Julia 1.4 installed with Nix, and as I suspected fails to build due to\nWe need to have a interface - that would support building binary packages, and make the interpreter aware of them. I wish I was a bit more motivated to do this, but upstream disappoints me regarding the humble task of compiling Julia as is, with the right selection of a few system dependencies - no response at all at & . I'm also dis-motivated to explore this aspect, since their build system is of plain makefiles, and they keep patches of dependencies from so long ago, without documenting whether they are needed / used or not...\nNix behind It is a shame to see julia's support in NixOS languish. It seems pretty clear to me that upstream is only interested in supporting the configuration obtained by cloning their repository and typing on a stock Linux distribution. I understand their perspective in many ways, as having julia and all of its packages \"just work\" requires a lot of care, and building with unsupported configurations is very likely to result in brokenness somewhere in the package ecosystem if not in julia itself. Julia is a bit special in this regard because of its emphasis on performance and also its need to support interfaces to other languages/frameworks that often have weird requirements. I have found that typically, there is very good reason for these patches, even though at times they may not be documented except in git and github history. (Admittedly, I am less involved in upstream than I used to be.)\nI think Julia team initially evaluated Nix as their binary distributor () but decided against it—there was a discussion somewhere but can’t find it. IIRC lack of Windows / desire to tie into native pkg management systems were factors. Julia’s does a pretty great job, and uses a solver to properly resolve dependency versions based on constraints. I’ve been incredibly frustrated by the withPackages pattern, at least in python. I constantly run into problems due to nixpkgs ignoring version constraints. There are some other nice advantages to nix of course: binary dependencies are shared across language ecosystems for example, and there are lots of supremely annoying packages (I’m looking at you CUDA...) that Nix makes delightfully easy to install, use, and maintain parallel versions."}
{"_id":"doc-en-nixpkgs-9721dc2395508a57efdbdf58f6507b11c1de77da06777014ddc36935d309d873","title":"","text":"But until Nixpkgs supports multiple versions across the board, and has a solver baked in, I’m honestly not sure Nix brings enough advantages to bail on Edit: I think the approach done by poetry2nix and Mach-nix are the way to go for Julia packages + nix. yarn2nix is another shining example. I would love to see a solution in this vein—didn’t mean to douse any enthusiasm for people interested in helping improve the Julia situation on NixOS :)\nMaybe it is worth to reaching out to Julia Computing folks at to get their attention on ?\nWe'd probably need to put this information in our attribute sets, just like our Python packages know what deps they need. Hmm that's a bit surprising to hear as the Python ecosystem seems most well organized. Have you ever encountered a real bug with a mismatched version of a dependency with a specific version specified in a package's ? IIRC fails if a version is used and it's not exactly what's available. If you've ever felt there's a certain python package of a certain version missing, have you considered contributing it? Even if not, was it too hard to override it? What do you mean \"across the board\"? That might be much more harder then it sounds, due to the constraints of Nix it self when being evaluated everytime you run and friends, see It's not a question of whether Nix brings an advantage or not, it's a question of whether there are any Julia packages that are built at other distros imperatively with a , and this produces (or even worse, downloads) shared objects or executables into (not in ), linked to Julia or other Nix deps that do reside in . If the answer is yes, than every Nix user will experience breakage after Julia is updated in his - not necessarily if it's a version bump of Julia, it could be a mere rebuild of Julia by hydra. Yea Mach-nix is an awesome idea well implemented ( thanks for the inspiration :heart:). I've also reached a similar conclusion at . However, this is my opinion for Rust and Go, and I tend to think that for a small ecosystem like Julia, perhaps it'll be too much - it shouldn't be that hard to manage all of these pacakges like Python is managed in Nixpkgs.\nI opened\nFrequently."}
{"_id":"doc-en-nixpkgs-0032c741a689712abc96bd7db1f20742dbf9354c224d09114857086b23a01aa0","title":"","text":"Especially with Scipy, matplotlib, bokeh, sklearn, tensorflow, pytorch, etc... Often, nixpkgs used to have it until it was updated. Except in very rare circumstances, we do not keep more than one version of a python package around. I have no interest wasting time working around bugs that authors tried to spare me by specifying precise versions. It seems a sort of cognitive dissonance in our next community that we all care so deeply about reproducible builds, but for convenience often disregard the officially supported dependencies. As a result, there are often subtle bugs in software on NixOS that do not appear on other platforms. (Eg x11vnc crashes, shared memory problems, etc). Nix supports crazy high specificity in versioning, well we past semantic versioning down the the bit in many cases. And yet in nixpkgs, by convention, we remove the old version anytime we update. It’s understandable that Hydra cannot build everything, but it’s always bothered me that I have to pin nixpkgs if I want a build to stay functional over 1+ years. is mostly declarative. Of course, Julia is constantly re-compiling code, and until there is true support for precompilation, I don’t see how it’s possible to use nix store. This is due to multiple dispatch. Suppose I wrote a library to do an efficient k-nearest-neighbor query using some fancy free structure. Perhaps the core algorithms simply require a function for your types. When you write this new function, Julia has to compile all the code in the k-nearest neighbor library for this new type. Thus, it is not possible right now to compile a package on its own as the core pattern in Julia involves extending the function of other packages via multiple dispatch. You can only compile a package in context of the code that is running. Therefore, the Nix store approach is not appropriate. See\nI see. You are talking about \"authors\" of Nixpkgs' expressions? I'm still a bit perplexed, as I earlier said, and correct me if I'm wrong: should fail if is used in , and the exact version is not available. Sometimes (), we do hardcode such version requirement changes in our expressions, but hopefully that's done only when it's justified."}
{"_id":"doc-en-nixpkgs-54596d859ef37339a6df406d7ca2901fabd34a1825bc1dafde06bcdf8240edb1","title":"","text":"I agree (maybe a bit ). Generally I think, every dep's version related issue should be handled by someone like you, who's familiar with python packages you use. I'd at least (open PRs) to fix the issues I encounter :). I see. I guess the situation is more complex than I thought, but I don't think I'd be able to form a strong opinion until I'll get a Julia interpreter from an expression I'm satisfied with. Thanks for the link :).\nUnfortunately, this pattern is done constantly (including in my own contributions!). The problem is that, except an extremely rare cases like tensorflow, nixpkgs does not allow multiple versions of same python package to co-exist. Every time we update a package, we remove the previous version from nixpkgs. Confounding this issue, we often disable tests because sometimes the effort is just too high when developers bake in assumptions that aren’t compatible with the Nix ethos (for some reason this seems to happen more with tests then source code...). The most frequent cause of failure is the code needs to download something to run the test. (I’ve tried to lobby in the past that the test phase should be permitted to have Internet access as long as it doesn’t modify /nix/store, but I digress). In any case, the end result is that using a python package on Nix typically means you aren’t using the exact dependencies that upstream declared, and you’re more likely to have a package that despite having changes in dependencies has never had the test run. Thus, amazingly, I’ve had more luck with Julia packages working on NixOS than Python when all other binaries are present in environment.\nI don't think there's a strong policy in our Python ecosystem against multiple versions of packages - if this is what upstream recommends. Anyway, the whole topic is out of scope for this issue. Feel free to open a new issue and cc me and who's working hard to ship a 20.09 release.\nYes, sorry getting a little off topic here. I mainly mention it to suggest that our efforts in Julia that start from scratch Can learn from these issues. I’m not too familiar with the new binary builder, but was quite nice in that it would first search for libraries before attempting to install."}
{"_id":"doc-en-nixpkgs-cf9aec941dd4d142ce95f7278077382c6ddc81086b2d0d5e03cf109c6c1337d9","title":"","text":"See this issue for some context: Note that a core Julia dev gave a pretty great endorsement on Nix (albeit back in 2014): I think it might be most productive to do this development outside of nixpkgs, and do it in Julia to hook in with nixpkgs as needed. That way users could seamlessly use Pkg in Julia. I’d love to and have it just work instead of the current hack that I wrote that a lot of people seem to be using ()\nShort summary of the Discourse thread: for LLVM and libuv it is essential to use the patches/forks. For other packages it is probably unnecessary to use the exact version specified by upstream.\nThanks for being there with me :). I think I'm gonna work on this once we are through with , to avoid merge conflicts.\nTIL Guix manages to package Julia 1.4.1: What's interesting, is that they but they build it with Julia's LLVM patches fetched from the internet - they don't rely on Julia's build system to build it's own LLVM. For similar dependencies which the real system's version can't be used, they do the same. I think we should try to copy this approach.\nFWIW I did that in Fedora originally, but I stopped. Since LLVM makes breaking releases very quickly, you'll probably want to move to a new version that Julia doesn't support quite soon.\nMaybe I don't understand, but why should I move to an LLVM version that julia doesn't support? Also, aren't the and versions don't introduce breaking changes between minor releases? We could stick to since that's what Guix does and I think Julia uses this version as a base too.\nI don't really know how NixOS works, hence the \"FWIW\". If you used versioned LLVM packages and keep older major versions then it's probably OK.\nJust offering a user perspective: Julia provides a package manager that provides mostly reproducible (in a practical/scientific reproducibility sense rather than a bit-identical sense) environments easily from manifests. Increasingly, these environments are isolated from the host OS by binary packages for dependencies being served by Julia. I don't want Nix to manage dependencies that can handle for me: Julia already handles those excellently and conveniently. I just want Nix to handle the (usually few) system dependencies."}
{"_id":"doc-en-nixpkgs-789f56a3e3695f6928c22bb9e185e5bd799d961ec8073af0ccdf5b0f649f314d","title":"","text":"What I would like as a NixOS user is for Nix to provide me with a working Julia 1.5 derivation that provides: julia, a FHS wrapper or something providing compatible versions of the few things that Julia's binary packages need (just libc, libstdc++, libgfortran; I think. ). When I say \"compatible\", I mean that these libraries should work with the binaries and with the julia binary provided by Nix. Not all Julia packages are BinaryBuilder-ised yet, so I'd also want an easy way to specify that I want compatible versions of other packages installed (e.g. Qt, cairo, etc). For packages that need python, I don't know if I'd like Julia or Nix to handle installing and managing that. The simplest approach would be to tell Julia to do it (there is pretty good support in Julia for distributing isolated environments of python + packages + dependencies; better than in , imo). I don't know how doable any of that is in Nix, just describing what a good outcome would look like to me.\nI think this is quite doable. I would propose that we add a new package, , that is a \"batteries included\" build that contains system libraries for all common Julia packages. Would this approach work for BinaryBuilder? I haven't used this yet. If not, we could fall back to a FHSuserenv, but I'm reluctant to do so if at all avoidable as there are outstanding nix bugs () that create seg faults in some heavy data processing workflows.\nI think that is a good proposal and I think it will work with BinaryBuilder packages (e.g. SDL2_jll). In any case, some approach that works with BinaryBuilder packages should be found because those are a critical part of the Julia environment now :) Some important packages (e.g. GR) still want to build and install their own software dynamically, and that doesn't work well in Nix, but most of those can plausibly move to the BinaryBuilder system (PR for GR ), so I think letting those be broken would be tolerable (and a big improvement over the status quo of Julia on nix). Perhaps we can get something working quickly by just patchelf'ing the official Julia builds for now? (I don't understand how all of this stuff works!)"}
{"_id":"doc-en-nixpkgs-a6234b6220484469322e36556c232fb45953661bea2159d093fce881537e9df0","title":"","text":"Is there anything presently blocking just getting julia 1.5 into nixpkgs? I don't care about ecosystem working with nixpkgs, just a good ol' fashioned julia install.\nyes, see\nIf you just want Julia and don't mind about binary packages breaking you can just download Julia from the official site and patchelf it. On Sun, 4 Oct 2020, 09:32 Tyler Benster, <:\nOn the there was also the idea floated to patch to patchelf dynamically loaded binary dependencies.\nGuix has a Julia package and it works quite well. Perhaps some ideas can be borrowed from there: It'd be really useful to get Julia working on Nix. It's the only big outstanding thing that doesn't work and prevents me from migrating some servers in my organization.\nI tried to copy their expressions in and it doesn't work yet, but there's also another seemingly working attempt by at .\nSo, do we want anything else now that 1.5.3 is packaged (:greenheart: ? I think we: 't need clean up the expressions a bit - not use the file if it's not shared. I did (2) along with the julia_10 fix in As for (1) I will need a bit of feedback.\nI guess some people like me still use julia_13 via test-disabling overrides, so a bit of time after 1.5 reaches channels for smooth transition could make sense?\nMaybe backport 1.5 to 20.09?\nOK so I disabled the tests for julia13 in and made the default there as well. All merged pull requests referenced here should be backported."}
{"_id":"doc-en-nixpkgs-bcffb77eb9fec2d3842fd35e08ddde1b44ca3d4c3dd5945923d5514bd55f650f","title":"","text":"Project description Client for authenticating to services using a German ID Metadata homepage URL: source URL: license: EUPL platforms: unix, linux, darwin, win32"}
{"_id":"doc-en-nixpkgs-a0c0675a89c9da78b5f1d108f3d3a87b8579e21c67fece1f34d834f7c7e0d16f","title":"","text":"Synergy crashes without an X Display available, but the autostart option attempts to start synergy regardless of whether login is graphical or TTY. It would probably make more sense to spawn this after\n(triage) status?\nIn case this is still relevant - would it make sense for those to run as user services instead to take advantage of recent changes merged in\nI think this is probably still relevant, and I think your suggestion is probably a good one, . With this config: out of the box, I get the following: But if I kill the service and start the synergyc command manually as my unprivileged desktop user, it works just fine:"}
{"_id":"doc-en-nixpkgs-b33fd03c57ec200b7477f2d531e1a0d4a5e4fc8b96a561f8ec86e5e2189acdc2","title":"","text":"was looking to resume my work on espanso's (which has been somewhat impeded by ), and now I find that espanso no longer builds at all. As those issues haven't gotten much attention thought I'd reach out to to see if anyone can at least confirm (as my understanding is that the reproducibility on darwin can't be quite as good as NixOS -- especially when one ). Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThank you so much for the quick fix! I keep running into these issues on darwin, I really want / need to learn more so I can contribute back! Unfortunately I'm still getting a build error, which looks to be a sandbox issue: This seems to fix the issue: Could you take a look and if appropriate merge? Many thanks!"}
{"_id":"doc-en-nixpkgs-e565ff2c4c82499fdf5f8ca3a2b12175d2906f715dac3abe821219383b77cddb","title":"","text":"Rendering a project in Kdenlive with default rendering settings leads to the following error: Steps to reproduce the behavior: ( is the latest revision of at the moment of writing this) any clip to the timeline (for example, drag in an image) \"Render...\" \"Render to File\" You might need to use as your desktop manager to reproduce this issue. There is claiming that this crash doesn't happen on Plasma 6. I am using Plasma 5, but I am currently unable to verify if Plasma 6 would fix this issue (Plasma 6 is broken for me for unrelated reasons). Render should succeed. See issue for the previous instance of this problem. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nAre you using the kdenlive matching to your desktop? Edit: nope, you are using the plasma 6 package. You want to use plasma5Packages.kdenlive.\nis plasma6? Wow, that's quite a foot gun. Shouldn't it be called ? Also, fails with the same error.\nIt really should not matter, and will (once is entirely gone) be whatever versions upstream ships.\nit seems that the problem either wasn't fixed or has resurfaced again? I was able to reproduce the exact same error with and (where is the latest revision of at the moment of writing this)\nPlease try again after the staging-next merge (which should make its way to unstable in a few hours).\nI will. Could you explain why staging-next is relevant in this case, though? I am just curious. I checked using and in the github UI directly, and it seems that the changes from should be already present in revision .\nstaging-next reshuffles protobuf versions again.\nI wasn't sure which staging-next merge you were originally talking about, so I tried the same thing with commits (current nixos-unstable), (current staging-next) and (current master) and I am still getting the same error. Can you reopen this issue, or should I open a new one?\nHm. Actually, I think that I figured out, what the problem is. It seems that actually saves some paths in ."}
{"_id":"doc-en-nixpkgs-c5f70ada44ca32ae3ce3348af1f6ccbd9c4f5a77c677de088a0805accf8038ea","title":"","text":"For example, my had the following lines: Deleting the line fixes the issue, but then adds it back again with the new path, so it will almost certainly eventually break again. I am honestly not sure, why does do this, but we should probably either patch this behavior or report it upstream.\nThat sounds very wrong because you have defaults from two different kdenlive versions in there.\nI can tell you that I've never touched prior to this debugging session. I didn't even know it existed. Those lines seem to be automatically populated on demand. Most likely, these lines were simply generated at different times, and so they picked up different paths to the \"current\" version of . Also, the fact that these paths are different from each other is mostly irrelevant in this case. The real problem is that they are cached once and aren't updated when a different version of is used."}
{"_id":"doc-en-nixpkgs-cc5eeb54525366ef700f5ba4d2163d75ec11527fd16ee059d2ce26f4a812e9e8","title":"","text":"Describe the bug fails to build on current master To Reproduce Steps to reproduce the behavior: a checkout of the current nixpkgs master Expected behavior Build succeeds Screenshots <details<summaryNot a screenshot, but build output </summary<p</p</detailsAdditional context The kind of error (not including a needed header) seems to be an upstream bug for me. Metadata Please run and paste the result. Maintainer information:\nFixed by upstream in See my PR"}
{"_id":"doc-en-nixpkgs-1defe19d55c7f5b901d97f7cd9e0592dbdaaa908936c439fa6964fbafc64686d","title":"","text":"On an apple silicon: $ nix-env -iA I thought was supposed to add support for macos. <!-- 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.\nWhy don't you ping\nI don't own a mac currently and I don't use the package, can't help you unfortunately."}
{"_id":"doc-en-nixpkgs-1f6686260b66ad2d69cc35764281af60c654ac49ab677445cc24c7ee4fd07b4f","title":"","text":"Opensnitch requires system- file to be placed under /etc/opensnitchd/system- to be able to enable its System rules/Firewall settings to be active and changeable. Steps to reproduce the behavior: to OpenSnitch Statistics to the button on the left navigation window just right of Rules/System Rules. cannot change the firewall settings there. the service complains about it. Being able to access that windows' setting. These screenshot shows the corrected version of the window. ! ! Can be solved temporarily with the nixos config below (the file can be found in opensnitch github repo): <!-- 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.\nExplain this line to me My hardware wouldn't be \"asus\" how do I find the directory for that?\nthe latest change to the opensnitch module (in unstable) has again a change for deploying the system- file, see the file comes from the opensnitch package and is linked to /etc/openstnichd/system- configuring this file is currently not supported. what would your use case be?"}
{"_id":"doc-en-nixpkgs-1fae022d922f77f78dab5e14faedf4fde2c6e24fb29414017270fc73e7f949c3","title":"","text":"Project description ! Metadata homepage URL: source URL: license: gpl3 platforms: linux\nFTR: This requires an update of .\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-8dc6214e848816496123e8e3d1c27804611cc2a9bafbb548fca3a1b6ed8f81de","title":"","text":"Maybe it's a problem with the ? Don't seem so. I can also not download it manually with curl: (i get a 0 byte file) But i can download it using a browser from the website. But the hash is also different: So they prevent us from downloading the file using something else than their website. Maybe the referer is not enough now? system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-e169c7bdaada213b056cae7e9c311397e9040b7baecfbc353712e148321f99c7","title":"","text":"Describe the bug Test  is broken on Master To Reproduce Steps to reproduce the behavior: Expected behavior For the test to pass Additional context I've bisected the problem to this commit:\nThank you for opening this :sparkles:\nIn that case let's it.\nThat is weird. How does depend on rsyslog?\nThis test is kind of flaky, there's some chance I incorrectly bisected it?\nI'm bisecting again starting at\ngoing to plug :grin: At a glance I don't see rysyslog having any relation, and likely if the tests are flakey enough bisecting can't give reliable results.\nI didn't use that tool because I was bisecting by running the test thrice and only if all fail considering it a bad commit :P\ncc. maybe add a flag to :P\nThat kind of unforseen usecase is exactly why nix-bisect is not just a tool, but a library ;) So you could write your own bisect script in python (a much more pleasant experience than doing so in bash). I may add that feature to the CLI at some poing though, since its probably a pretty common usecase. would probably be a better name, since we really want a minimum number of tries. Feel free to file an issue against :)\nI tried bisecting again, but I think this result is also nonsense:\nCore of the issue seems to be this:\nI don't know &ndash; locally I'm getting this :arrow_up: error even on which (I tried several times).\nCareful (manual) bisect lead me to a surprising result: I'll try a few more experiments now. Many my steps failed for other reasons (e.g. libselinux not building), so I suspect that's where you were led astray. I did 2-3 attempts on every step to be surer, but I found no non-determinism on my machine.\nI had quite a few steps where the first attempt at building failed, but the second one succeeded, I was bisecting manually with this:\nI re-confirmed that reverting that commit atop master () fixes the test for me. (Still no idea why so far.)\ncc for the linux config change\nNarrowed down just to the kernel option. I don't know... maybe the JIT has some bad interaction with the VM."}
{"_id":"doc-en-nixpkgs-8008eb7c068d369177d81aca90deda09c6659a399e50ffb1e50f124e2cdcbda8","title":"","text":"For now I suppose I'll push a revert of that single option, unless someone suggests a better idea very soon.\nSounds good to me"}
{"_id":"doc-en-nixpkgs-6f85a38350f07c3b5137b6c2429ac51889fcd8dfa72fc5974c1a6e29dd664449","title":"","text":"I enabled budgie: = true; I opened Budgie Desktop Settings. ! The font is \"None\", which is wrong. I expect a font be set. I am on a (neraly) freshly installed NixOS. It would be nice if a \"Reset to default\" button would be there (or some NixOS \"magic\" for configuring Budgie), but I did not found anything at Default fonts are listed at"}
{"_id":"doc-en-nixpkgs-a240089918aaf3a77559464b3f299dd1aa34038675bc14993caddaaf68383156","title":"","text":"The license listed for is incorrect. It has been re-licensed upstream: name: current version: desired version: n/a maintainers: Please tag this issue in your PR.\nFix in (which also updates the package)"}
{"_id":"doc-en-nixpkgs-3fd69891d270fd2ccf1de0067adedc82e87baef2337c0b5451f6a9d28edcf267","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 <!-- 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-f2d35867cca1d53b885f871662b3b607cb2f3e43a24e3fa9647adaa7efc0ee25","title":"","text":"Project description Mathematical modelling software Metadata homepage URL: source URL: license: gpl2 platforms: cross-platform\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 .\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-8c83b31c119b875274edb78ba54871d156911496212bf3dad8c2ecc7b9c66c6c","title":"","text":"NixOS unstable is affected by on Wayland. Steps to reproduce the behavior: signal-desktop on Wayland. No crash. Add any other context about the problem here. Please run and paste the result.\nI am also getting a crash every once in a while on startup. Starting it again works so far and it seems stable after that. Don't know what to do about that.\nI've fixed this locally by using the following overlay:\nApparently, Signal beta works again on Wayland.\nJust adding a data point. Having Wayland disabled actually caused more bugs for me. Re-enabling Wayland via 's overlay helped fix my compositor crashing whenever I clicked on certain UI like \"preferences\" in the \"file\" menu. Currently running: with set to and have the following env variables set:"}
{"_id":"doc-en-nixpkgs-c47f31e0997cb9b79b26e9b830dfa18a0e0523caeadb425890c39af467dd30dc","title":"","text":"I just discovered and i can't use it on NixOS Pulling image seems good Trying to run image fail because it try to mount some specials folders The : Trying without mounting folder fail because it can't find Start a shell with still fail because it can't find Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(pinage404): channels(root): 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\". 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 .\nIt could still be important.\nI marked this as stale due to inactivity. &rarr;"}
{"_id":"doc-en-nixpkgs-75f3b65106251c8a67a7908cbaa6c536ab4eba1c2aa289fc5955ce15a67cbea9","title":"","text":"Describe the bug While the configuration contains no settings related to LVM, is launched during boot, and so on, and the \"lvm2-activation-generator: lvmconfig failed\" message is logged in the journal. Expected behavior At least, does not produce error messages. It might be better if the service is not activated if the system does not use LVM at all. Additional context may or may not be relevant. Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(omasanori): nixpkgs: Maintainer information:\ncc\nI'll try to find some time to look into this, as I might be responsible for this.\nI got this error when running in the console. It just froze, didn't reboot. Hitting enter put me back into the shell. Doing shutdown -h now worked. Very strange ..\nI strongly suspect that your freeze was not caused by this warning message.\nYeah, so this was most likely caused by , which combined with the rest of leads to systemd being aware of lvm2 things. lvm2 was already in and for anything that's not a container, before this, but now it's also in . As for why this happens, it looks like it's , which fails when does not return what it expects. Since we do not install the default lvm config, it fails like so: The easiest solution to this is probably to install the default config file to . There is a problem with that though. If we use , we cannot use anymore to append any settings. We also cannot \"copy\" the defaults into e.g. with , because that would be import from derivation. So the remaining option is to simply set some default settings, which also kind of sucks, because then we need to track upstream on those, but it's probably our best option. If you have any other/better ideas, I'd gladly go for those, but if nobody does, I'll go with specifying some defaults, in a few days.\n+1 to importing upstream defaults as it seems the safest option if it tracks upstream properly, even though it will certainly increase the maintenance cost.\nI also would just create a default configuration if it is not possible to disable lvm2-activation-generator somehow if lvm is not used.\nDetecting if lvm is used sadly isn't trivial."}
{"_id":"doc-en-nixpkgs-8c1b4ab9f173e1ee12d50af6d85f6c08d8367867780463e973135978d84fbcdc","title":"","text":"For filesystems (in ) we can just look at the and enable the respective kernel modules and tools, but how would that be done for lvm?\nMaybe it would be possible to fix/patch(&upstream) the generator?\nlvm seems to have its default hard coded so we don't need to copy over the whole file. To fix the loading error I just an almost empty configuration to make the warning go away:"}
{"_id":"doc-en-nixpkgs-8ca0a30a270a15b2e84a1a4d8ee313d4bd3c36d68a88274a0a71d683ae16604b","title":"","text":"The pkg-config file in pkg looks like this: The and variables are empty. The keyword is also empty. As a result, the flags returned by pkg-config are wrong and checking the version does not work. Note the empty and and that the package version is actually 3.0.1, i.e. = 3.0.0. and should point to the correct directories in the and outputs of the pkg."}
{"_id":"doc-en-nixpkgs-f52ad7abe32b6fa5f59c6c02072a5612d3976e9100cafaa862ca7fce66dbb204","title":"","text":", CVSSv3=6.5 (nixos-21.11, nixos-unstable) A NULL pointer dereference issue was found in the block mirror layer of QEMU in versions prior to 6.2.0. The pointer is dereferenced in mirrorwaiton_conflicts() without ensuring that it's not NULL. A malicious unprivileged user within the guest could use this flaw to crash the QEMU process on the host when writing data reaches the threshold of mirroring node. Scanned versions: nixos-21.11: ; nixos-unstable: . Cc Cc\nThis is fixed on master since we have QEMU 6.2.0. It's not included in 6.1.1 though, so needs to be fixed on stable. Probably after since it'd be a merge conflict."}
{"_id":"doc-en-nixpkgs-98fb148129529288788d3770143c60d0f68e43140ce184d5e163effae1219caf","title":"","text":"Package name: osu-lazer-bin Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 2023.1026.0 Current version on the stable/release channel: 2023.511.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."}
{"_id":"doc-en-nixpkgs-f154a35ecbae122ce1b7d20a7881ea095947f514cc483d50952feec6e6411a86","title":"","text":"The auto-multiple-choice program does not start, on NixOS 22.11 : Steps to reproduce the behavior: auto-multiple-choice auto-multiple-choice that it's not really working A clear and concise description of what you expected to happen.\nI'm trying to reproduce, without success so far. Did you install AMC from , or through nix-env/nix-shell? (I'm rebuilding my system without the global AMC to test those cases, but it triggered a full Emacs recompilation which will take some time)\nI installed it using nix-env. I'll try with the systemPackage option later today. I'm using wayland with sway.\nI don't think that's the issue there (also I have the very same setup, on unstable though). This message means that the program can't find the perl source module of its gui component, which indicates an installation/path issue.\nI really can't reproduce, sorry. Please let me know how things go with . Does exist?\nYup, it exists : After switching with the system version, I get the same error. After updating the channels () and rebuilding () I still get the same error.\nIs there a /lib/ directory at your FS root?\nYup, there is, it contains a subdirectory (modules) which is empty. Deleting it makes auto-multiple-choice work as expected.\nOk, I believe that's the root issue, but I'm not sure how to fix this. If it's fully empty besides subdirs, you should just delete it.\nDoes that mean that auto-multiple-choice is also broken on non nixos installations ?\nNo, because on those, the Perl modules AMC needs are on the global , or , or whatever. The NixOS package, OTOH, is a self-contained, so-called \"portable\" build where everything (libs, executables, doc…) lives in a single directory. Your issue comes from the fact that AMC tries to detect such a portable build by first looking for a global , then defaulting to dir iff the former doesn't exist: I think I can solve this by just changing the default lib dir, please don't close the issue.\nwill fix this.\nreverted the \"fix\" to that issue, because it broke everything else (my fault). For the time being you need to make sure there's no on your system for AMC to work.\nNo problem, good luck with that !"}
{"_id":"doc-en-nixpkgs-7a04782d0d9287b1989de8f3e94f16173916a2b834eafd8c0da6f9e6e035493d","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]:\nThis looks to me like the compiler wrapper isn't respecting and/or , and it's inappropriately passing the libunwind shared object. I don't have immediate time to investigate further but did discover this minimal reproducer:\nlooks the same as which is due to (search path prefers .so files with ). i agree that passing in libunwind unconditionally seems not good. if one builds libcxx with the linker script at will result in but we don't so we add unconditionally. it is not clear to me why c code needs libunwind."}
{"_id":"doc-en-nixpkgs-10afca828444b33a93c67b49c725dceb6bd1a9b6f2d4f61055d83bc35ddc6e78","title":"","text":"needs in it's path to be able to use the fuzzy file picker, e.g. produces file picker should open <!-- 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-4d040b24740a18df2aa604ffc2924255273a05e8bdbda557786bc3cc02bb46ba","title":"","text":"I bumped the version in which fixed the problem for me. Can you confirm?\nconfirm: Fix the issue. (your changes not in unstable yet). Thank you!"}
{"_id":"doc-en-nixpkgs-cc9318edc0dbadfffdc8652c6b4824d98e08e273bf28c1cb8a6861894da19b74","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: dstp <!-- 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.3.0 desired version: 0.4.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: I'd love to update the package myself without annoying you :) If there is a documentation about how to upgrade packages, i'd love to learn it and try my best next time, thanks in advance!\nFor simple version updates, I update the version number and to get the new hash I run (in the nixpkgs top directory): For go packages, we also have to update the hash, that one is tricky, and what I do is to try to build the package. That will fail, but it gives us the new hash, I don't know a better way. There is also a bot () creating PR for those simple version updates. It uses repology to find the latest version:\nAwesome, thanks!"}
{"_id":"doc-en-nixpkgs-3d5b17446b3f0669b0b0eed2db3c0897a9c3ebde568d5ca94ac243f85d3b32f4","title":"","text":"Trying to install tetrio fails (see screenshots) Steps to reproduce the behavior: tetrio-desktop from nixpkgs-unstable (I did it using a flake) The package should install with no errors. ! <!-- 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.\nOops, it looks like I accidentally used a non-direct download link for the source. It also looks like audio is broken, so I'll start a PR soon."}
{"_id":"doc-en-nixpkgs-b8af3be2c949034ca6a9bf83554e11498c4756e19772a04aec920618b457f624","title":"","text":"Project description <!-- Describe the project a little: --Switchres is a modeline generation engine for emulation. Its purpose is on-the-fly creation of fully customized video modes that accurately reproduce those of the emulated systems. Based on a monitor profile, it will provide the best video mode for a given width, height, and refresh rate. Switchres features the most versatile modeline generation ever, ranging from 15-kHz low resolutions up to modern 8K, with full geometry control, smart scaling, refresh scaling, mode rotation, aspect ratio correction and much more. Metadata homepage URL: source URL: license: GPL-2.0+ platforms: linux, windows P.S. Switchres is used in RetroArch so there might be something to reference from there. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-f5a5b99d6c08d7f71cebd95304b76dc01506033f8fd8b4ddf24deda541e8290d","title":"","text":"In executing ibus-setup-hangul, got this error message: .nix -rebuild switch ibus-setup-hangul in a shell System: NixOS 17.03.1584. (Gorilla) Nix version: 1.11.11 Nixpkgs version: 17.03.1584. Sandboxing enabled: build-use-sandbox = false\nMight be due to . What was the reason to remove from dependencies?\nI think that was because I noticed that it is propagated from some other package, but looking at this now it doesn't seem to be the case. I'll investigate this today!\nThis seems more deep than I thought. The bug is two-fold: script is not patched as needed for Python scripts; should be propagated from . However, only its output is propagated, so it's not as a Python library. I can fix the first one but not sure what to do about the second -- maybe we should change behaviour of this propagation in some way.\nThe same problem appears with anthy, and directly adding the same pyEnv to buildInputs like did in ibus definitely fixes the build fails (tested with both anthy and hangul), but the python environment isn't propagated by itself."}
{"_id":"doc-en-nixpkgs-72f3fffcda6256458dc2fdc3003de678a23b8a7c54dad692bd05dbdef07a378f","title":"","text":"Steps to reproduce the behavior: ocf-resource-agents. Relevant: () Looks like a GCC update deprecated , which is used by ocf-resource-agents. This also causes the pacemaker build to fail, due to the circular dependency. system: host os: multi-user?: sandbox: version: nixpkgs: (I'm using commit ) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI fixed it in my flake for pcs / pacemaker here:"}
{"_id":"doc-en-nixpkgs-0edec83b6ade513a5cfc78972086224790d0580882f49d32b976bedfb907ba81","title":"","text":"Project description Fprintd replacement which allows you to have your own backend as a standalone service. Metadata homepage URL: source URL: license: GPL2 platforms: linux"}
{"_id":"doc-en-nixpkgs-d0e090baf3adce07f6ed7002582cf16323f1bf7779d342e09f39565fec196e31","title":"","text":"Describe the bug Libvirt usually handles virtual network devices, interfaces, bridges and also the DHCP range. This seems to be broken. To Reproduce Steps to reproduce the behavior: a VM connected to the default network 't get an IP Expected behavior DHCP is working Screenshots If applicable, add screenshots to help explain your problem. Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nLikely fixed by If you are fine with rebuilding libvirt your could use this locally. Alternatively if this is your home computer and you are in a safe network you could temporarily set to disable your whole system's firewall but this is not recommended. Edit: Rebuliding should be really quick (on a decent laptop)\nThanks - looks right. I will try to use the overlay first.\nI think it's related... When I try to start a VM using Gnome-boxes or Virtual-manager with VM using bridge this error happens:\nhave you updated to the latest nixos-unstable version? This issue itself should be fixed and you should probably create a new issue if your problem persists.\nit's still happening, even with the last version.\nthen you should probably create a new issue as I don't think it's the same issue. It may still be related so maybe reference this issue. There wasn't an error with the original issue I think"}
{"_id":"doc-en-nixpkgs-83b8f707266accae3499d277d5d77d47a001561407d4c920bf0614a6dad778f0","title":"","text":"Describe the bug results in the following error on : Seems like the writer expects to be executed in a stdenv environment to find instead of knowing the path to it. To Reproduce Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (rust maintainers)\nThis should work as long as GHC is proper dep, because libiconv is propagated.\nThis should be independent of GHC entirely: only relation to GHC is probably that I mistook the error for one coming from GHC initially, but this is not the case ( doesn't allow building the writers individually what confused me).\nI'm facing this issue trying to build from on macOS Big Sur. (wasmer is a dependency of FastAPI, which is the package I'm actually interested in) <details<summaryLogs:</summary</details\nI think adding to could also help there.\nFix here:"}
{"_id":"doc-en-nixpkgs-7cf9bf16a0cd6ea601d8ed3a654a4ca23257036d0a7eb7ab2ff94b5cfee3433b","title":"","text":"Project description Turtle is a graphical interface for version control intended to run on gnome and nautilus. Currently these dialogs are implemented: commit, add, stage, unstage, revert, resolve sync (pull+push), pull, push checkout, create branch init, clone remotes, submodules log, diff settings and about Metadata homepage URL: source URL: license: gpl3+ platforms: linux"}
{"_id":"doc-en-nixpkgs-311633c2522fe2194c160b8d9fbd5f0e1a8c72dfdf0d29b35b59202c61b21f42","title":"","text":"The last fzf update in nixos-unstable breaks certain bash-completions, for example git. This happens since Then try bash completion for git. My looks like this <details</detailsThe regular bash completions for git should work. As a fix I found this old issue in fzf To test this, I tried simply replacing with an edited version that puts the fzf eval after the bash completions code (and before the alias declarations). This fixes the issue. However, I am not sure how to solve this cleanly in NixOS. The bash completion code is inserted using but I don't know how to enforce ordering so that the fzf eval happens after the completions. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nThanks for the report, I started a PR super-seeded by fixing this issue. As what I found this issue was already there previously but as most people didn't had the full integration enabled it didn't triggered the issue.\nIs there any progress on this? Solution PRs seem to have been closed?\nThe fix already got merged and will be soon on unstable - otherwise you might cherry-pick/overlay it.\nCool, so we can close this presumably?\nI looked at this in master and now we're basically back to how the fzf module was previously, right? So then it should still be an issue when enabling .\nAlright, so now I'm just gonna try my luck with a PR. It definitely works for me and makes a difference."}
{"_id":"doc-en-nixpkgs-8f557b128825fb4df2b55b6c70e40d520856b2090deaa2895a0450771f48aac1","title":"","text":"of repo is a branch, not a tag, and there were a few commits to that branch since then. At the moment fresh fetching of source is broken because of wrong : it should be now . should probably be pointed to a specific commit, not a branch? Originally posted by in"}
{"_id":"doc-en-nixpkgs-9cbfb7b1a250714a124722ee83c2804c83c087b04e2fc3e1bd4b12973914248a","title":"","text":"The laptop screen freezes with the current contents (systemd startup messages) at the point starts. Nothing else visible happens. I can switch VT's back to text consoles, switching back to VT7 again just freezes the display. All the normal processes seem to be running, but they don't draw anything. I'm using gnome and wayland. Updated to today's () Booted previous system generation, was working again. With some excellent help on Matrix from I have confirmed that: building from previous branch revision () and switching (no reboot) makes gdm work again. building from current revision () with also works. building from the previous revision with that line fails to evaluate, because the multi-version package change isn't there yet. So / are clearly implicated. K900 suggested raising this as an upstream Mesa bug. I had some issues registering there, but may try again later and will add a link here in case system: host os: multi-user?: sandbox: version: channels(root): channels(dan): nixpkgs: bits of relevant config: note that the displaylink driver is not in use (no device connected) at this point, it's all on the internal display only. Hardware is a Dell XPS 13 9360"}
{"_id":"doc-en-nixpkgs-525713e4e06448fb4b19c9906fc9ad7c36bb1b4005b994bf2a063a797d2f9281","title":"","text":"If gdm is enabled with Gnome enabled, gdm will crash and not load into the login screen after logout or reboot. This is due to gdm using wayland as the default. Once wayland is disabled in gdm, the login works. Steps to reproduce the behavior: channel nixos-unstable, \"sudo nixos-rebuild switch upgrade-all\" with Gnome enabled and gdm enabled in will hang at the gdm check point. gdm wayland in and the reboot works but with Wayland not working. Reboot into gdm with Wayland <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --\nI just hit the same issue. After updating to latest nixos-unstable, the boot hangs just before login screen I think this is related to , at least the workaround posted there worked for me also\nWould be relevant with a machine without AMD graphics and without KDE? As, I am running Intel's build in graphics and using Gnome. Also, I did find a \"workaround\" by disabling wayland in gdm then nixos-unstable will boot.\nI managed to work around this issue with on GNOME Wayland. Graphic card: Intel Xe Graphics (TGL GT2)\nTotally worked! Thanks and ! Should I leave this open as this is a bug or a new config that needs to be applied to 23.05?"}
{"_id":"doc-en-nixpkgs-707df18c165f5def219f0dd86602acfc9d0fdea10b804e23354f538ac49b4dd0","title":"","text":"Describe the bug A clear and concise description of what the bug is. Rambox apps cause rambox to crash when attempting to upload a file. It gives the message: To Reproduce Steps to reproduce the behavior: rambox rambox in terminal any app that has file upload functionality (I tested Google Messages, Element, and Slack) to upload file Expected behavior Rambox apps should be able to upload files from filesystem Additional context I've seen from browsing other issues that this has been solved before for riot-desktop at first by adding gsettings schema to the package wrapper but currently fixed by using in electron. However, for some reason this did not fix the issue in Rambox. 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. these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked): /nix/store/d43v6bx7r6fcaq3fbbfd5mwh1f5s7rmg-bash-interactive-4.4-p23-dev copying path '/nix/store/d43v6bx7r6fcaq3fbbfd5mwh1f5s7rmg-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:\nAdd wrapGAppsHook to"}
{"_id":"doc-en-nixpkgs-f1c1fb02ef5c55b2e924d47bed758b8d847f807b0e6d5912adbc6bfba8080aa9","title":"","text":", CVSSv3=9.8 (nixos-20.03, nixos-unstable) CVSSv3=7.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives.\nneeds 1.3.2 for CVE-2016- needs 1.3.1 for CVE-2016-3092"}
{"_id":"doc-en-nixpkgs-40761a4870190e8740ac145924076ff1393a138a2c11a9cebeb54f9e2104c9fd","title":"","text":"After enable HBase module , and rebuild. The service unit cannot start, it says JVM option not exists. Steps to reproduce the behavior: HBase by adding config . , it should be failed. shows VM option is Unrecognized. I found the same issues on the StackOverFlow, it seems jre 15 dropped the option: I fixes this by adding this line, but it should be fixed in module. I can do the fixes PR if you want. Maintainer information:\ngo for it. I'm also not maintaining this anymore, so may be best to also remove from ."}
{"_id":"doc-en-nixpkgs-9177652ce26462cc69837a58f3d9a871c63dd34dc0e3a6cc880c62838eb7929c","title":"","text":"Project description This project is used by programmers looking to explore the Rust programming language and learn more about it while doing exercises. These exercises are meant to get you comfortable with the language itself and its features. Metadata homepage URL: source URL: license: MIT platforms: MacOS, Linux Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nInteresting package request. But does it make sense given that you need to modify the rustling files in order to use it? I personally used the that's included in the project. which I think are removed in the new release :(\nTake a look at . The maintainer of rustlings explained why the was removed.\nTL;DR: All required files are embedded in the binary now. The exercises are dumped on initialization. I am the new author. If you need any help, don't hesitate to ping me. Note that a new version was published yesterday."}
{"_id":"doc-en-nixpkgs-8de943bf3ce53c0a75dc98c9ac74f564953e7ae6328c36e837729c472508bdcf","title":"","text":"I'm using Nix 1.9 on OS X 10.10.4 (Yosemite) with the package. It installs without issues, but when I try to use the tool I get this error: I'm using the unstable channel:\nHrm, I get (also Nix 1.9 and OS X 10.10.4) It seems to be an issue with the shebang in as seems to work just fine. I don't see anything obviously wrong with though... (PS hi long time no see :)\nI just hit this issue too. Weirdly, just running from different shells would give different errors (I use fish normally, so it's always an early suspect around problems like this). I would get an error like got from , and an error like from . When I change my to this: Everything works, and in all shells the same way. Is this a valid fix? (By \"works\", I mean I get , but maybe that's a separate issue, or due to a lack of familiarity with Elixir/Erlang...)\nNice catch. Doing will generate a new app skeleton if everything is working as it should.\nTurns out I just forgot to put the at the end of my fixed version, so no args were getting through :P Is what I mentioned above an acceptable fix? If so, I can submit a PR."}
{"_id":"doc-en-nixpkgs-671dc757920d31255b080b8ecdc3c85d3cde4fd0e9c9f6f25eaf87deb42f4b8e","title":"","text":"I have installed sage thorough the nix package manager and it is the only thing I use nix for so it is entirely possible I am doing something stupid and wrong. I have the latest from here build When I try to get to the index for all entries which is located on my computer, I get a page with very few entries (see the screenshot) below ! While I expect something more like Compare /nix/store/r77k14kq9iw92w32bd9sny7d98dbrq32-sagedoc-9.6/share/doc/sage/html/en/reference/genindex- and A full fledged index. I want to use to generate a docset which I can then search following the answer here I can build a docset after copying the reference directory to somewhere I have write access to. However when I try to search there are almost no results and I think this might be responsible. Please run and paste the result.\nI'm not very involved in sage maintenance these days, I mostly contribute by reviewing and PRs every now and then. They are probably better qualified to help you :) Maybe we should drop me from the maintainers list, or at least change the order to reflect reality?\nSorry for the bother then! I was actually going by the information here which looked outdated but I didn't have any better idea.\nThanks for the report! Will take a look today.\nThanks a lot!\nNo bother :) Thanks for the pointer, I have updated the maintainer information there."}
{"_id":"doc-en-nixpkgs-91f8915a1636ab69ebb1d519479445d9c67cba294e65368518cc960905bb4582","title":"","text":"I have an EPSON DS-530 scanner, that I can't use to scan anymore. Prior to upgrading to NixOS 22.05, it worked perfectly fine. Steps to reproduce the behavior: scanning as follows: a sheet of paper in the scanner and scan it using utsushi, scanimage, simple-scan, xscan, … scanner pulls the paper through, but this does not result in a scanned document with any of the programs I tested. The (probably) relevant lines of the full log output (see below) are: The page is scanned successfully. The symptoms look exactly like those described in . The full debug output is as follows: <details<summaryLog</summary</details\nI just noticed that utsushi reports version 0.65.0, which doesn't match the supposed version 3.65.0 in the channel. Though it seems kinda plausible to me that utsushi just reports major version 0, as the rest matches?\nTrying to debug this further by scanning with , I got the following lines of output: The line () looked suspicious to me. I attempted to narrow this down further using strace: Interestingly, this refers to a file called , that supposedly should exist in the / package's directory, but doesn't as the strace indicates. The only reference to this that I could find is in the . If not provided with a different engine as a command line parameter, it should just use tesseract. This in turn led me to in the utsushi codebase, which calls the filter. I stopped my investigation there for now. Maybe can give more context, as they came up in many of my searches regarding this.\ncan you try adding to and see if that works? It looks like calls out to and expects to have it in , so probably falls back to ?\ncan you check if fixes this?\nThank you but unfortunately this didn't help. I'm still seeing references to in the where I suspect that I should see references to tesseract instead. It would be sufficient for me to deactivate all the postprocessing that happens, but this doesn't seem intended feature in utsushi :/\nAs I had amassed quite a backlog of documents to scan, I started a nix shell with the utsushi version I used previously, using the following command: This works."}
{"_id":"doc-en-nixpkgs-127f86f538361d12a3d83925006825c9dbdb74c78ced7887ac7ea173df6d3f0e","title":"","text":"However, this is only a workaround, as this means that I need to use the interface for scanning, which is somewhat cumbersome to use and this also pulls in a lot of old packages via the dependencies. I'd be happy to try out anything at this point.\nHey, I started looking into this again and noticed that in you switched the sources from the to the repository on gitlab. I'm wondering what the reason for this was. Do you remember?\nI think back than the maintainer of utsushi suggested this. Imagescan just tries to mirror the driver as it is release by epson, while utsushi contains community maintained patches, but unfortunately no clear versioning scheme.\nI just bisected the changes and it turns out that is indeed the commit at which utsushi stops working for me.\nThat is unfortunate. Maybe we should offer both utsushi and imagescan as packages, than the user can choose.\nThis could be a solution. I am not sure yet, whether the problem may also stem from one of the patches introduced or the command removed in that commit. As I am getting a error, I think it possible that the problem may be related to the imagick (or a similar) dependency.\nIt turns out, that this problem had a . Adding the following line back to the derivation makes utsushi work again. PR adds it back to the derivation and fixes scanning on my machine."}
{"_id":"doc-en-nixpkgs-920a9c2f9f65b6a9cfbf0abeb2fff02721cd9c958bf19d0c106039374f9a588f","title":"","text":"Describe the bug After upgrading to nixos-20.03 and enabling pulseaudio support I started experiencing the \"Gah! tab crashed\" error too often, to the point that browsing sites with certain types of embedded media (mostly audio/video) instantly triggers the error (e.g browsing ). While troubleshooting this I also noticed that opening crashes not the tab but the browser. On the console I can see: This crash is present with default options (i.e. and ). In addition, after several crashes Tor asks to start in \"Safe mode\". I'm not sure what safe mode disables but it allows opening without crashing and/or triggering the segfault. This seems to hint at some interaction with external libraries and my assumption that this is somehow related to pulseaudio. To Reproduce Steps to reproduce the behavior: the URL will crash Notify maintainers Metadata The following expression was used to enable and : and installed with .\nCan you try with override ?\nThis helps. On a quick test I didn't see any \"Gah! Tab crashed\" error and works fine.\nIt should be off by default then, it used to work :(\nCould this be triggered by a missing or mismatched library? I also only started noticing this after enabling pulseaudio system-wide. If this helps diagnosing the issue...\nI think it's simply because the firefox jemalloc is incompatible with the hardened allocator. firefox has to be built with for that to work. I wonder why this appears to have worked before; maybe the tbb build has changed. Relevant mailing list thread here (fair warning: it turns into a not-so-productive exchange after a few messages):\nI think that at this point it'd be appropriate to revert the commit that hardened alloc support, with a note as to why, maybe opening an issue to track work (if anyone cares) to make hardened malloc work with tbb/firefox.\nI'm not into the differences/advantages of each allocator. In this case I have the user hat on and unless there's a critical aspect of relevance I'm happy to trade that in favour of a functional browser."}
{"_id":"doc-en-nixpkgs-b55591e62831b4973058f3e204019f5384415ad08ad1d805e33ef591af883ebb","title":"","text":"Unstable Bitwig doesn't know where libpipewire- is when attempting to load the Pipewire audio device. Console error !"}
{"_id":"doc-en-nixpkgs-7b6c30edf3ae228e2c3069eed6ea98ee524266eb1c7cc351fe567103192ed3d2","title":"","text":"Project description A cross platform front-end GUI of the popular youtube-dl written in wxPython. This makes the awesome commandline tool usable for more people! Most repositories use the package name youtube-dl-gui, so i recommend to use it tool. Schould be quiet easy to package. Metadata homepage URL: source URL: license: The Unlicense platforms: unix, linux, darwin, ... (Python)\nSadly the project is not maintained anymore and has issues. We shouldn't add it.\nThere is an active fork:"}
{"_id":"doc-en-nixpkgs-385f535a744b4e8591d412d0756b84aa1230890de27aa1b6588a960714119909","title":"","text":"The systemd initrd (or stage1) does not work with a volatile root when there are 9p mounts present. A result of this is that VMs built with nixos/qemu-vm do not work when disabling the (and thus running on a tmpfs) and using the systemd initrd. Create a test that sets these options: The test should work just like the test works in who has identified the root cause (an ordering issue where the tmpfs is mounted before the 9p infrastructure is up) and found a hack around this behaviour.\nI this to the board because it will require a test when it is fixed.\nAs a side note, we should consider using to implement volatile root with systemd stage 1.\nAs far as I can tell we could only do this if we mounted under .\nSo this works probabilistically. Sometimes it succeeds, and sometimes it fails with for one of the 9p file systems.\nOk this patch seems to fix it Which begs the question... why does it ever work, with or without volatile root? EDIT: Oh I bet it's a race condition caused by not depending on . In order for to appear, virtio modules need to have already been loaded. So, because gets mounted first, and needs to wait for to appear, that means virtio modules are definitely already loaded before any children of are mounted. And indeed, switching from to just does the trick as well."}
{"_id":"doc-en-nixpkgs-d48af55b0bb3fb3ad7f1adca278662aa8aa2e1c0137b2427327b07d0c0096e78","title":"","text":"When opted in to the latest Steam Beta (version ) starting Steam fails with the error Looking at the log output, it looks like it fails to load : Steps to reproduce the behavior: into Steam Beta steam Steam runs ! stdout when running : Please run and paste the result.\ni'm able to reproduce this as well\nIn case anyone experiences this and wants a temporary workaround, you can opt out of the Steam Beta by running\nI think this might be due to a change in nixpkgs rather than steam, since this works for me on: But it breaks for me when I update to:\nBuilding with running with and using the bad commit is part of cc\nPlease test ."}
{"_id":"doc-en-nixpkgs-724e5becf91ad18990c1bc72fadf6618e9800ae61f2d816238b85ea704b967ae","title":"","text":"Specs-nvim does not work in Neovim 0.10 and the author has not updated the upstream version. The derivation should point to the updated fork instead: Steps to reproduce the behavior: specs-nvim with Neovim 0.10 specs-nvim errors Should I have used the out-of-date packaging report issue template instead? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nno pb for me. Feel free to submit a PR. Pinging as he might know better.\nWhat does no pb mean? I'll make a PR\nI guess that it means \"go for it, let's switch to the fork\"."}
{"_id":"doc-en-nixpkgs-f2f53e0ae146dd07c66b5991508475fdddfda5ebe1aa098a7984f244641711c0","title":"","text":"To make sure that we are on the same page: When I run ledger-autosync, it complains about a missing module. I expect it to run It prints:\nLet me know if there is any other information you would like me to provide.\ncc maintainer (btw, nlewo, your nick in is wrong)"}
{"_id":"doc-en-nixpkgs-b3b3c8f7bebb52d76d6497ba1b2217f4d7a3fcea16f1e988288f41d4b3826bce","title":"","text":"crashes, even when installed into the system. Steps to reproduce the behavior: shell \"nixpkgs#gnome-frog\" -c frog Program doesn’t crash Please run and paste the result.\nInterestingly, I was able to build and run the app in commit (I also rebuild it with just to double check). ! Though, it does fail to build and run in recent revisions (at least in ). It needs to apply to be able to build. Running it however gives me the following error: Not exactly familiar with GTK development but I'll see what I can do. Thank you for reporting!\nRunning it on my end gives me another error:\nfrog+main+Application' doesn't support property gobject-introspectionbuildInputsnativeBuildInputswrapGAppsHookGITYPELIB_PATH`, resulting in typelibs being picked up from the environment.\nThank you for the explanation, . Simply putting into did build and run the app (at least in the recent commits)."}
{"_id":"doc-en-nixpkgs-a0173afbfb6a9425ca21bd1bfc8e79556ac6e8d8196e9ee9d0990549c1d8d132","title":"","text":"Describe the bug Shell with and will fail to start with a following message: This is an issue because depends on so they would be always included to the shell started by nix-review. I noticed this issue while reviewing . I suspect this is caused by . To Reproduce Steps to reproduce the behavior: This does not reproduce on release-19.09 Expected behavior Shell will start, shell prompt will appear. Metadata Please run and paste the result. Maintainer information: cc\nI'm getting \"CLASSPATH: unbound variable\" since updating master an hour ago from last Sunday, and reports \"JAVA_HOME: unbound variable\" started happening while working on eleven hours ago."}
{"_id":"doc-en-nixpkgs-10d15116f882f59d1dbe926c9e6da84b76e1e8f2f8ee8fcbeb9a6ab2e9f02ebd","title":"","text":"The IGV package freezes and crashed when a file dialog should open (open file, save as, etc.). Steps to reproduce the behavior: igv: igv \"File\" -\"Load from File..\" application crashes The file dialog should open and allow me to open a file. If I open igv through the terminal, then this error is shown: This error is the same as previously reported issues for other application, e.g. I'll shortly open a PR with the same fix. I'll rather do that in the PR with the fix. Please run and paste the result. NA"}
{"_id":"doc-en-nixpkgs-041d74e0c6d0dfecb3108793e45abfa4fda55be2e32ae8fac27da73804c3c997","title":"","text":"Steps to reproduce the behavior: for n/a <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --built from nixpkgs master () Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-7b86ac1f080b4664d08da5029cab7605b3a8083fd5f5b19bffa77f85a076c6aa","title":"","text":"The version claimed to be produced by the openmw derivation is , however once installed it is still version system: host os: multi-user?: sandbox: version: channels(avery): channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-2ffa35ecdd4a7a929d0b78ea68afdfce98d64d9ef7335376a3e85772db929869","title":"","text":"Running shows a version that is different from the one in the Nix store file name. Run The output will look something like: Notice the store path says while the command show that the version is actually 0.19.12. The two versions match. I ran into this because I tried to use and got the error \"has no attribute 'replace'\": According to this part of the API was released at least in version 0.19.16, so it would confirm that the version I have installed is in fact 0.19.12. <!-- 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]:\nPR only updated the version and not the hash.\nThanks, well spotted! when I merely update the hash I end up with this error:\nhey, after having had just a quick look, I've opened I haven't tested though, could you help with testing and let me know if that works ?\nah, I've just had a compilation failure. This is because the maturin used currently is 1.3.0 and polars requires 1.3.2. the bump is also going to require a maturin bump. Are you interested in taking care of it ? Otherwise I should be able to make some time at some point.\nThanks for this! I might try it out in the next few days :)\nalright, I've tried with maturin 1.3.2, but I still get a rust compilation failure. I've checked their MSRV and it's only 1.71. So I don't know what could be causing this compilation failure. if you have any ideas, feel free to re-use anything from that PR without any need for attribution. I'll be happy to help merge a solution.\nmight be worth setting the version back to in the meantime so the package will build on a cache miss.\nso version has been set back to 0.19.12. I have finally had some luck in compiling the latest polars version in if anyone is interested to test the PR, feel free to post a comment. I'm running a nixpkgs-review to check what the update breaks"}
{"_id":"doc-en-nixpkgs-4e194afba2a9ed5fc6f975f08fd342907f5f071a1517663166ebfd73eba2083d","title":"","text":", CVSSv3=7.5 (nixos-21.05) CVSSv3=7.5 (nixos-21.05) CVSSv3=7.5 (nixos-21.05) NLnet Labs Routinator prior to 0.10.2 happily processes a chain of RRDP repositories of infinite length causing it to never finish a validation run. In RPKI, a CA can choose the RRDP repository it wishes to publish its data in. By continuously generating a new child CA that only consists of another CA using a different RRDP repository, a malicious CA can create a chain of CAs of de-facto infinite length. Routinator prior to version 0.10.2 did not contain a limit on the length of such a chain and will therefore continue to process this chain forever. As a result, the validation run will never finish, leading to Routinator continuing to serve the old data set or, if in the initial validation run directly after starting, never serve any data at all. In NLnet Labs Routinator prior to 0.10.2, a validation run can be delayed significantly by an RRDP repository by not answering but slowly drip-feeding bytes to keep the connection alive. This can be used to effectively stall validation. While Routinator has a configurable time-out value for RRDP connections, this time-out was only applied to individual read or write operations rather than the complete request. Thus, if an RRDP repository sends a little bit of data before that time-out expired, it can continuously extend the time it takes for the request to finish. Since validation will only continue once the update of an RRDP repository has concluded, this delay will cause validation to stall, leading to Routinator continuing to serve the old data set or, if in the initial validation run directly after starting, never serve any data at all. NLnet Labs Routinator versions 0.9.0 up to and including 0.10.1, support the gzip transfer encoding when querying RRDP repositories. This encoding can be used by an RRDP repository to cause an out-of-memory crash in these versions of Routinator. RRDP uses XML which allows arbitrary amounts of white space in the encoded data."}
{"_id":"doc-en-nixpkgs-5637ab36c95e6a977c4af89345a72c57bb1e3a34c16f90398d2226af15645086","title":"","text":"The gzip scheme compresses such white space extremely well, leading to very small compressed files that become huge when being decompressed for further processing, big enough that Routinator runs out of memory when parsing input data waiting for the next XML element. Scanned versions: nixos-21.05: . Cc"}
{"_id":"doc-en-nixpkgs-b12a2a927f385b4f8913af6785073d052a44b5c336ba214450870949bdd0f557","title":"","text":"On aarch64-darwin, while neovide does build and install successfully and I can launch it from the terminal, there is no app bundle that can be found in finder to launch neovide from there or pin it to the dock to launch from. Once opened the global menu calls it .neovide-unwrapped and the icon in the dock is a blank white page as a generic icon. I can only assume that once is fixed, that this will also be applicable to x86_64-darwin Steps to reproduce the behavior: neovide as either a system app in nix-darwin or a user app in home-manager on aarch64-darwin An app bundle name that will be linked into or depending on and usage I'd like to point out that the global menu title is .neovide-unwrapped to for sure indicate that this is the nix neovide and not the homebrew neovide ! ! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nFollowing PR MacOS app information a few days ago: We can install the files with next release of neovide."}
{"_id":"doc-en-nixpkgs-6853ba43be1c26c39f644f3dedce2694437c2027368e5cf0bfeca5c44d3d57f1","title":"","text":", CVSSv3=7.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc\n09 is still vulnerable\nNixOS 20.09 is EOL, so this issue isn't actionable anymore."}
{"_id":"doc-en-nixpkgs-ccf5bf3669d5b0707518cde5cbf36e63aff068be446521ec457e060408f9fc22","title":"","text":", CVSSv3=7.8 (nixos-20.09, nixos-unstable) Scanned versions: nixos-20.09: ; nixos-unstable: . Cc Cc\n09 is still vulnerable\n09 is EOL"}
{"_id":"doc-en-nixpkgs-db736f8483e06bdb0692ffc9c3985b8acbf2056f78f0b97a2132efd8fbacd302","title":"","text":"Describe the bug When I did we assumed that variables like and would be replaced with or . This is not true and in the pam configuration we have variables. cc"}
{"_id":"doc-en-nixpkgs-8a44c42bf4d8bd5a23e9262d4b35cb3bb9c3055eeeaefe1232d288e7018b2c45","title":"","text":"Unable to build libxml2 Repro: nix-env -i libxml2 make[4]: Entering directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' CC CC libxml2- CC libxml.c:1649:43: warning: passing 'unsigned char ' to parameter of type 'const char ' converts between pointers to integer types with different sign [-Wpointer-sign] message = libxmlcharPtrConstWrap(ptr); ^~~ ./libxmlwrap.h:240:48: note: passing argument to parameter 'str' here PyObject libxmlcharPtrConstWrap(const char str); ^ 1 warning generated."}
{"_id":"doc-en-nixpkgs-60a93ff659709a34277f8dcb941c372246c1bfdfa105f52a71fc776a571ef8c0","title":"","text":"CCLD ld: library not found for -lintl clang-7: error: linker command failed with exit code 1 (use -v to see invocation) make[4]: [Makefile:600: ] Error 1 make[4]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make[3]: [Makefile:694: all-recursive] Error 1 make[3]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make[2]: [Makefile:528: all] Error 2 make[2]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make[1]: [Makefile:1479: all-recursive] Error 1 make[1]: Leaving directory '/private/var/folders/7g/1ptqqd597r76dqzk7hjy0bgc0000gn/T/nix-build-libxml2-' make: [Makefile:893: all] Error 2 builder for '/nix/store/xcqdl8cfjjbjvh7g9ka0ip3r4awy80a8-libxml2-' failed with exit code 2 error: build of '/nix/store/xcqdl8cfjjbjvh7g9ka0ip3r4awy80a8-libxml2-' failed Metadata* system: host os: multi-user?: sandbox: version: channels(swarnpriya): nixpkgs:\nDisclaimer: I barely know what I'm doing. I tried adding as a build input to libxml2. That got this error:\nI've been getting this as well, since . Any clue? I think this sort of thing has happened before, but I don't recall the details.\nI thought somebody else already fixed this after some discussion no irc. My proposal was essentially the patch above but guarded for python2 only."}
{"_id":"doc-en-nixpkgs-ef765ed31ab27722cb7b016c364d76c963e2e8650063f74b4ea56cf42b04dd5f","title":"","text":"Steps to reproduce the behavior: Commit seems likely to have broken the build for bitsandbytes. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nI suspect the above output is related to that commit modifies or creates the module referenced above. I'm rebuilding setting the to and to to see if having dummy definitions solves the problem. Unfortunately it's slow going as it requires a full pytorch rebuild to see if it repaired bitsandbytes.\nthe trivial fix proposed above appears to resolve the build. Not sure if this would have ramifications elsewhere in the tree. Happy to PR the change if others want to help kick the tires\nOh!!! was mean to be a not ... how on earth did this even pass the tests (i.e. I only meant to abuse python's imperative-ness to override and keep all other symbols intact...)\na PR would be very welcome\nlooks like your original idea should also work, and be less broken in mysterious ways, I can do a quick PR after I make sure it works on my end."}
{"_id":"doc-en-nixpkgs-fd77b961c7f2892fd0b81b27f48d7df07326b06c480dd2ab02aca479e61e4d01","title":"","text":"Gotenberg crashes immediately on startup Enter the following into your nix config: It not crashing but starting up normally ! Gotenberg was to be used in conjunction with paperless-ngx. is the entire file Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nAre there any more logs from the Gotenberg service? Or is the coredump all that's available?\nSadly that is all. The service log literally doesn't say anything. There you only see that the service started and immediately exited. This log i got by typing\nSorry for the slow response, but I looked at this and figured out the issue. Could you test and see if it fixes your issue?"}
{"_id":"doc-en-nixpkgs-8be087a16f78220fc4d75935f65326600b3354d0d7d4c539277c770b6a8aca5b","title":"","text":"Describe the bug After upgrading to NixOS 20.03, sudo often (but not always) segfaults: From the logs: Disabling appears to have made this problem to away, so the problem may be in . Metadata NixOS 20.03..\nMaybe the patch to use a not insecure openssl is the source of the issue for you\nsame issue here - the sourceforge repo is way old, there's a github mirror but not maintained either, and there's a fork of the mirror which includes fixes for openssl 1.1.1:\nI marked this as stale due to inactivity. &rarr;\nHmm, kinda forgot about this\nI missed the fact that the \"supported\" branch didn't actually include the patch to fix this."}
{"_id":"doc-en-nixpkgs-45eefc09372430461c2664403f5d42b5231dfbcb18b78484912f62d19d5105e4","title":"","text":"I saw the following during a rebuild: Error in file \"/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-\": \"font/ttf\" is an invalid MIME type (\"font\" is an unregistered media type) Error in file \"/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-\": \"font/ttf\" is an invalid MIME type (\"font\" is an unregistered media type) Error in file \"/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-\": \"font/opentype\" is an invalid MIME type (\"font\" is an unregistered media type) Error in file \"/nix/store/vwd5hb2n6m7nwqijlz0rsmn5x6fpmlhw-system-\": \"font/collection\" is an invalid MIME type (\"font\" is an unregistered media type) Unknown system: host os: multi-user?: sandbox: version: nixpkgs:\nI think we just need to update , c.f.\nAh, it seems that upstream has not released a version with the fixed commit in. The last tagged release was , they haven't tagged anything with the fix commit in. We could build from their git head, I guess, although I'm reluctant to do so. Perhaps complain ?\nIf the commit applies as a patch that would also be fine.\nI'm still having this. had it for build and build (separately). build"}
{"_id":"doc-en-nixpkgs-67cfc549f68ef597a18c96ab52385136f55f9434d343a6be8b46151cf506eb3d","title":"","text":"Project description Metadata homepage URL: source URL: license: lgpl2/lgpl3 platforms: linux\nPreviously: (which I never finished, sorry, but linking in case helps anyone tackle this)."}
{"_id":"doc-en-nixpkgs-88e32e32efdec3ae91cb2c871ca931126ebe542c1331a818d198589bdb7b3630","title":"","text":"Steps to reproduce the behavior: pyload-ng <!-- 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]:\nThank you for notifying me, the failure is caused by the lib not yet working on python 3.12. Apparently the git upstream of pyload replaced it with which I'm packaging in , so once that's done I'll get around to updating pyload (will probably have to switch to the git version since they rarely upload new releases to pypi). For now you can override the python version as a workaround:\nThe override works great. Thanks!"}
{"_id":"doc-en-nixpkgs-e1630ca61c56460dad56a603d7bd106d074847aeb67fbbc84258c59a35e15729","title":"","text":"Hi there! I’m sorry to bother you with a ping. We realized that in the form of . All of our Nix expressions are meant to be MIT‐licensed, so this is a big problem, especially as packages using / may count as derivative works, potentially jeopardizing the licence status of Nixpkgs as a whole. We would therefore like to get permission from all contributors to this code to relicense their changes under the MIT license used for Nixpkgs. If you have any questions or concerns about this, please ask them in so that this issue can purely be for tracking the sign‐offs we’ve received. To agree to the relicensing, please reply to this issue with the following verbatim text: [x] [x] [x] [x] [x] [x] (confirmed via email) [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [x] [ ] [x] [x] [ ] (GitHub account is gone, although as this was just a treewide removal with no other changes it’s unlikely to be copyrightable) [x] Authors of unmerged pull requests in the old repository (just in case we ever take code from them): [x] [x] [ ] [x] [ ] [x] [x] [x] (I have not checked for unmerged PRs to this part of Nixpkgs yet because it’s a pain.)\nApparently I can only ping so many people at once; please look at the original issue text, sorry!\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs."}
{"_id":"doc-en-nixpkgs-8dae9f04282912a9545ba99e9556ef1c662c2df41744f3f97a826007d7c3f5d5","title":"","text":"I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs. PS: nice catch and thanks for taking care of it\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs."}
{"_id":"doc-en-nixpkgs-44562566db2e5f00debeb6fb7791db53e47f2f7ff4d40aacae1376fea0d04262","title":"","text":"I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs. Like, sure, we still use it in our toolchain, and this move is very nice.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs."}
{"_id":"doc-en-nixpkgs-63c1960fc72fc080a4e19fa711926536dbcb7f629d842ac4c6965dc69368decb","title":"","text":"I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , and the pkgs/development/tools/yarn2nix-moretea directory of the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs."}
{"_id":"doc-en-nixpkgs-ceeb0eb22aa586aeaecb1182da0883278b638cfce892d15a35bcaaa702aa2871","title":"","text":"I agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs or any other OSI considered free software license. IIRC if we get everyone else on the list, then will be fine.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nJust another gentle ping; if you could check the original post at respond as requested it’d help us resolve this licensing issue.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs."}
{"_id":"doc-en-nixpkgs-e3acc3ca122724ed7ab73345b9c3b3d354edd865ea90a19aba7bfa4eb41242d9","title":"","text":"While it wouldn't hurt to get approval from the last 4 people, I don't think we need that to move ahead: gebner only authored , a minimal change that I don't think would be copyrightable egasismus only authored , another minimal change that I don't think would be copyrightable chawki008 only authored a PR that was never merged: eqyiel also only authored a PR that was never merged:\nYeah, I agree those changes aren’t copyrightable. I did email the authors of them but I’ll proceed with opening a PR to do the relicensing now.\nI agree to license all of my past contributions to , , and the pkgs/development/tools/yarn2nix-moretea directory of under the MIT license used by Nixpkgs.\nThanks so much to everyone for helping get this done so quickly, and for your contributions to the Nixpkgs ecosystem"}
{"_id":"doc-en-nixpkgs-255eb6688c8edef0762c1767e4b7eee76b9c8411b9ebb5ec3887b4ffdf795af7","title":"","text":"All expressions in nixpkgs are supposed to be MIT licensed, but is licensed under GPL-3.0. as an externally developed project under different licensing terms that we use for nixpkgs. It was merged into nixpgks in without the license being changed to MIT or a compatible license. Every package using is using improperly licensed expressions, which at the time of writing looks to be a bit more than 25 packages. I have two proposed solutions, neither of which are particularly appealing: -license under MIT This would require assembling relicensing signatures from all existing yarn2nix authors which include both contributors when it was in nix-community & in nixpkgs. It's gonna take some time and keep us in license non-compliance in the mean time. , migrate packages to something else The newly looks like a good contender as pointed out by in chat. CCing authors and other relevant parties Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nJust to repeat what I said on Matrix, if we can’t figure out something better in a few days I will open a relicensing issue and start the work of pinging all the contributors. Reimplementing it sounds nice, but I suspect it would take quite a while given the speed at which Nixpkgs language ecosystems tend to move.\nyarn2nix can be easily misused and trigger IFD. I think too that in the long run we should replace it. Maybe yarnBuildHook/yarnConfigHook from are already enough and the package can easily be migrated?\n(Nixpkgs potentially actually being GPLv3 is very much a bug IMO.) Migration is all well and good, but we probably ought to try to relicense anyway: we can’t change old revisions of Nixpkgs and it’s not good for multiple years of Nixpkgs history to be under unclear licensing conditions.\nI guess re-licensing is the better way for now? We can ping all the contributors, from a glance I read most of the names before.\nYes, I think we should probably at least try. I will open a new GitHub issue for it today so that we can discuss here without it getting bogged down in rote responses.\nOkay, here we go I guess:\nOof, thank you for trying to clean up that mess."}
{"_id":"doc-en-nixpkgs-722d3dc33bc60ec22093f077856d95ba1d4cbf23bfae81c684e000a3d9e0184b","title":"","text":"I just got the notification from the tracking issue and I feel that a big portion of any blame should go towards my direction because of the introduction in , rather than While I (try to) put a lot more thought into licenses today, it didn't cross my mind back then that vendoring with the included license could have such implications.\nNo worries – thanks for trying to improve the Node packaging situation in Nixpkgs and for your quick reply to the ping! This is an institutional failure IMO, and I think that it would have been caught before merge these days.\nseems still active. It might be worth posting the same as on Discourse if you want people's replies to be public (unlike with email)."}
{"_id":"doc-en-nixpkgs-082128a24e24b04d091188b3d3de55fe6d09cfa7390b61726d2d1264301e9cd3","title":"","text":"Steps to reproduce the behavior: -env -iA (full output here: ) 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.\nThe error is not in pgcli but in psycopg which tries to import a .so which does not work under darwin."}
{"_id":"doc-en-nixpkgs-d2cc741f0a6e76c42077bee66b3792a885b5ebb2d2a1202a946de0c6c4a89e0e","title":"","text":"The project seems slow with releasing the latest changes, which (among other things) includes Package name: tiramisu Latest released version: 2.0., I suggest using the latest commit instead since there is no newer release yet <!-- Search your package here: --- Current version on the unstable channel: 2.0. Current version on the stable/release channel: 2.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."}
{"_id":"doc-en-nixpkgs-49b818b5e89df91625fa9609a8adf82158108980a8ff617500d42e3e0f8965d1","title":"","text":"Describe the bug The example given for does not seem work as expected. To Reproduce Steps to reproduce the behavior: the following to nixos-rebuild switch Expected behavior Creation of a proper ceph client configuration. Additional context I am trying to build a NixOS configuration with a minimal ceph client configuration. Metadata Maintainer information:"}
{"_id":"doc-en-nixpkgs-37fb74931d817fcd89534c60217519fe656611a872eeb777de31d035bc081a45","title":"","text":"Package name: fluent-gtk-theme Latest released version: 2024-04-28 <!-- Search your package here: --- Current version on the unstable channel: 2023-06-20 Current version on the stable/release channel: 2023-06-20 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:"}
{"_id":"doc-en-nixpkgs-c30474595fa567ec6dac7921be3930d4442f95aa751807029875ee14c4cda4ce","title":"","text":"Hardening gives old Clang flags that it cannot handle and fails. A same problem, I imagine, would arise with old GCC versions. A possible solution is to list somewhere what hardening methods are supported and use the list when deciding what hardening to apply. For example: a file : an error. Nixpkgs version: (run ) Sandboxing enabled: (run ) yes"}
{"_id":"doc-en-nixpkgs-aaf077cc7faa4bd96170ee6d9b1db1e53612f558fff944f99d491de7e4880a9d","title":"","text":"Describe The package rtl8821ce can't be compiled due to errors.\nThe package is the upstream GitHub repository it tracks which is the cause of this breakage. Bumping it to master should suffice in resolving this. Specifically, commit is the one that fixes the failure I too observed in rtl8821ce today while setting up NixOS.\nfixes this for me and WiFi works perfectly."}
{"_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-1a297d491ab320066101d0172105ecb1326a4acedf7fe4624969084bf1ec8cc9","title":"","text":"example: This one is low on the massive bucket list, but extending the number of retries and the timeout between each retry will reduce friction.\nThis might be caused by , in which case increasing the timeout wouldn't help much. We can try though, PR appreciated!\nplease view"}
{"_id":"doc-en-nixpkgs-0086b89fbe9f0e12e14b4dfb64dac30b9e01275681f7507b7cce73faf898fb6e","title":"","text":"Our current legacy nvidia driver of the 340 branch does not work with kernel version 4.19.2: NixOS is currently on the 340.104 version, but upstream is on 340.107: I hope that updating to 340.107 resolves the issue, but I don't understand how to update the different checksums for the nvidia driver. /nix/store/kic17fw8wil74k04kzh3dha43izrr9j3-bash-interactive-4.4-p23-dev copying path '/nix/store/kic17fw8wil74k04kzh3dha43izrr9j3-bash-interactive-4.4-p23-dev' from ''... system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:\nThe hashes are located at and can be generated like so: Please try:\nThanks alot for giving me a hand and teaching me how to get those four hashes! :+1: Updating to 340.107 indeed resolves this issue. PR:"}
{"_id":"doc-en-nixpkgs-f46566e29d98ab4b5a08cca7364a81d2bf59dc33c63126ec740f4d1169bb5a75","title":"","text":"Hi. Some Emacs packages which were ok at 16.09 got broken with 17.03 Adding leads to error If I activate , Emacs shows the error . It doesn't matter whether it was installed from or . One from loads but produces a warning System: (NixOS: , Ubuntu/Fedora: , ...) Nix version: (run ) Nixpkgs version: (run )\nWith regard to the sha issue with ---I think this is just an inherent conflict between melpa being willing to get code off of , and nix's desire for stable identifiers---if you look at the sha on , it matches what is expected, but it only dates back to 2017-03-02. should we update the sha in the expression for the release?\nWith regard to ---whatever it's baroque initialization code is doing, it is apparently not smart enough to simply , instead electing to get itself into some infinite-seeming loop. I would suggest reporting a bug upstream. Doing that manually allowed it to start, at which point I discovered it was apparently written by someone who doesn't actually like emacs---I barely escaped. :) Good luck!\nI have the same problem with a fresh NixOS 17.03. Script to reproduce this problem: Will produce the following output:\nThank you much for fixing zerodark-theme! ergoemacs-mode fixed in"}
{"_id":"doc-en-nixpkgs-34e8f574ed10ee08fead9b8fcb317f4f6cb8e57034eb148811370cdba0c7a43d","title":"","text":"Project description Ciao is a programming language that builds up from a logic-based simple kernel, and is designed to be extensible and modular. Its supports: constraint logic programming (and, in particular, Prolog), different levels of modularity (from small to large scale): modules as (analysis-friendly) compilation units bundles as collections of modules, packages as modules implementing language extensions (syntactic definitions, compilation options, compiler plugins), assertions (as a homogeneous framework that allows static and dynamic verification to work cooperatively in a unified way), multiparadigm constructs (meta-programming, higher-order, mutables, concurrency, functions, etc.) and interfacing with foreign code. Metadata homepage URL: https://ciao- source URL: license: lgpl2 platforms: unix, linux, darwin"}
{"_id":"doc-en-nixpkgs-f2f9f290997cf6f09837bf2fc15b4592160296b323934893061ec10258581bff","title":"","text":"Describe the bug The description of is: Path to the unix socket file on which to accept FastCGI requests. This option is read-only and managed by NixOS. So i can't set it. But how can i figure out how the socket path is now? Please add an example to the description! To Reproduce Steps to reproduce the behavior: option desciption Expected behavior Useful description. Metadata same in 19.09 and 20.03 Maintainer information:\nThe point of the option is that you don't need to find out, just reference it. That being said I agree with your issue and it would be helpful to set an example\nThe point of the option is that you don't need to find out, just reference it. Sure, that works in but i have that path explicitely in my webserver config which is next to the content, e.g. . For reference: The path is actually as i set it before: So i can just remove the option from my ."}
{"_id":"doc-en-nixpkgs-3114651a643cd1bf8920ca0e44f2753633720ff8f858f891a82130bc638381c5","title":"","text":"When adding as a plugin I get: . completes without issue. I have plenty of other vim plugins in the exact same manner without issue."}
{"_id":"doc-en-nixpkgs-0dfc591a2d438a669f8e0f283ded234fa580b89d305cdd0cc9cc61e03010b97d","title":"","text":"Building the manpages for 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: (please share the relevant fragment of the diffoscope output here, and any additional analysis you may have done)"}
{"_id":"doc-en-nixpkgs-728b448dc8f432f3e84ae8cd97081ee5983fe8cd00129ee3a85b22cc5d717a6f","title":"","text":"Describe the bug A clear and concise description of what the bug is. I am using nixops to manage a number of machines, some of which use nixpkgs-unstable. When deploying a machine with nixpkgs-unstable, I started getting errors stating . These are likely linked to a change in the last week or so, as I've been able to deploy the same machine perfectly fine last week. When run with , I get: After getting this error the first time, I initialHashedPassword to all 2 of my users, as well as root, as follows: This fails with the same error. Deploying with nixpkgs 20.03 works fine. The error seems to originate from , specifically: I also tried adding , which naturally fails as that attribute doesn't exist. It also fails with the same trace when using instead of To Reproduce Steps to reproduce the behavior: to deploy a machine (maybe nixops is required?) with the latest nixpkgs-unstable Expected behavior The machine should deploy normally, even without , as it used to last week Screenshots N/A Additional context I suspect it might be linked to Notify maintainers - Tagging you as your PR was the last one to touch this area Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(raghav): nixpkgs: I'm using nixops release-1.7 Maintainer information:\nYeah, this really smells like .\nArgh, I made a stupid typo. I'll fix this ASAP."}
{"_id":"doc-en-nixpkgs-9f153ea408db8008ca65a272f43afc230171fda8d73318f6a195a3d8ef895602","title":"","text":"Neomutt's bundled tool is unable to find . We should probably replace that string in the perl script. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:"}
{"_id":"doc-en-nixpkgs-9fa7dd7dcf1ecd1f67b5605b1c08cbd4f9c0b0bebd8589c80884418e86b106f4","title":"","text":"default value causes previews to fail. the usual homeserver config Do not configure (so that the default value is used) Post URL into a preview enabled room Find similar error in synapse log: The option defaults to . Were those values intended as default for the option? Excerpt from a working configuration: /cc (as you discussed the security implications in )\nSeems like a good bet.\nthanks for fixing this, I was just wondering about this earlier today:"}
{"_id":"doc-en-nixpkgs-723b09a78d45e9118985eff1d8143d6bd5a9a57f9fcc4f2caa51b01d35ec74d7","title":"","text":"I'm getting an error /nix/store/jx2hdq8n3fdj0bm58qxgy0psyyl0vd05-nuget-to-nix/bin/nuget-to-nix: line 56: baseaddresses[$usedsource]: unbound variable when trying to generate a lockfile for . Steps to reproduce the behavior: this simple file: to generate the script the error Be able to generate the lockfile. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. I guess was the one to introduce the variable there.\ncould you give a try?\nThe problem seems to be that there's a repo in the sdk at , containing only . This is somehow referenced implicitly. I'm not sure if we should do anything more to handle this situation, but the message fix should do for now."}
{"_id":"doc-en-nixpkgs-5293a495ab903a54c5f0b3c2c79ff99734e07dfa77949ca6f1544f97f0fba387","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: clojure <!-- 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.10.3.855 desired version: 1.10.3.933 <!-- 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.\nOpened a PR:"}
{"_id":"doc-en-nixpkgs-d41b07265f3f6bb8a848117aefa11e2b7a48cea73efe797c1dcc68556d20262a","title":"","text":"Upon launching,  white screens without any visible errors. or the app white screen It works without white screening Since runs fine when using its pre-built AppImage, I don't suspect that there is any issue with my hardware, drivers, or software. After testing, I have found out that the issue exists on specifically. It works fine on KDE. (Note: I haven't tried on similar environments like Sway) Running produces the following output upon exiting : Hello,\nI am thinking of adding a package so that any user facing this or similar issues can use pre-built binaries as a instant solution than waiting for existing nix expressions to be fixed. Please guide me if you guys think this should/can be done. (The NixOS manual doesn't provide much help with wrappers around AppImages)\nCould you please run in a terminal (in the environment where the issue occurs) and paste the output in a comment, in a . I also have a few questions, you get those same errors when you run from the terminal? this X11 KDE, or Wayland KDE? is your GPU, and which drivers are you using? I don't think we should do this. If a user wants to run pre-built binaries from upstream, there are straightforward ways to do so. Since Heroic ships an AppImage, you can use .\nI've already tried running heroic from a terminal and weirdly, there's absolutely no error that shows up. Which makes me think it's a purely front-end error given heroic uses electron. , I do. KDE . My driver setup is contained in Yeah, that makes sense. But how do I make sure it's always installed on my system? Do I have to run every single time I need to launch?\nUpdate: I have tested this in Sway as well and the app does white screen with no errors in the terminal.\nTry running Heroic from the branch I just pushed (command below) to see if it resolves the issue. I've changed the Electron version the package uses to match that of the upstream package, as there seems to be a regression in the latest version of Electron.\nJust tested this. I don't get the white screen anymore!!\nThis happens for me now, trying the nix shell now.\nThat fixed it, thanks!"}
{"_id":"doc-en-nixpkgs-d5727612721984c9ceeddb374e247b9a7641c4130b733c1c68d0070e9acf5875","title":"","text":"Package name: zoom-us Latest released version: 5.15.2.4260 <!-- Search your package here: --- Current version on the unstable channel: 5.15.0.4063 Current version on the stable/release channel: 5.14.7.2928 <!-- 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-153f5679e99c3c1ff90f4715bb35364f11e564f8a9d469c13c03bce6f5684ffa","title":"","text":"When used with latest Nix the \"new\" hash is extracted incorrectly, or thereabouts. This seems to be due to Nix changing the message used to be more friendly to humans: Use an update script invoking common-updater-scripts. Sorry, LMK if repro is needed. Please run and paste the results. I don't expect this to be helpful but happy to provide anyway! system: host os: multi-user?: sandbox: version: channels(will): channels(root): nixpkgs:\nIt is increasingly messy, perhaps we can drop the old regexes, most people probably set instead of changing nix in overlays so this would not be affected.\nWhat about adding a flag to nix, which turns on machine readable error messages with a guaranty that those messages will not change in a backward incompatible way? Would need someone to add that. But wouldn't that be better to parse error messages intended for human readers with shell tools?\nAlternatively, if the build fails, I think we could do something like:\nI'm not sure I follow, but FWIW I ran into this and I set and don't set it via overlay. Looks like the new behavior is in 2.2, the current default for : (err formatting might not work for email responses, maybe? sorry :)) I think it's reasonable to drop support for nix older than what's in the tree-- especially since you'd have to overlay to replace it and as you say would likely do via anyway. Oh... that's probably what you meant! :D\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 .\nAny updates on this?\nI marked this as stale due to inactivity. &rarr;\nShould have been fixed by\nThanks!"}
{"_id":"doc-en-nixpkgs-3a8920fe07d1adb5f5a7243faede2b9f1995cef14b9d010cda4fa6d8b18a9b70","title":"","text":"Describe the bug On a cold boot, exits uncleanly, leaving a black screen. This issue seems to have appeared on 20.03 (stable) up to the (at the time of this report) latest channel. Running from a different TTY will immediately load Plasma with the expected automatic login. To Reproduce Steps to reproduce the behavior: as an import at the top of the system configuration and set Expected behavior Automatic login to Plasma after the Plymouth screen. Screenshots No screenshots, but here's an excerpt of the output of : Additional context Using the same configuration this issue appears on only 2 of my 3 machines. The affected ones are using Intel integrated graphics with SSDs, while the other one has an older AMD GPU and HDD. I'm unsure if this could be an issue relating to drivers (with autologin off, SDDM and X work OOTB) or the significant difference in boot times. Notify maintainers Metadata Maintainer information:\nI can reproduce this on a machine with AMD graphics; the issue seems to be a race condition with individual user login not being permitted before SDDM starts. Normally you don't notice because it's done by the time you finish typing in your password, but with autologin enabled it doesn't have to wait for the human. I have had luck with this configuration: Which may be overkill, but does appear to work.\nThat doesn't sound like overkill to me. As a user, I definitely want the network and user sessions available before I log in! :sweat_smile:\nWell yes :P But I mean, it's possible that it only needs one of or , not both, or that, say, implies so there's no need to explicitly list the latter.\nI doubt this part: and are independent, and we need the display manager to wait until the other services are started, so we probably do need both. I'm not sure about the second part, I need to investigate.\nI marked this as stale due to inactivity. &rarr;\nShouldn't be marked as stale, there are still . Would it be wise to start a PR for the tweaks suggested by They seem to work on hardware and configurations affected by this.\nI agree, this is not stale. I think the suggestion above is the appropriate solution.\nThanks a lot, the annoying workaround is no longer needed and time to desktop is fast again!"}
{"_id":"doc-en-nixpkgs-ee94ea2edf7a435c623dd923effb390985900fb004db38e39650c34ccd80419b","title":"","text":"Steps to reproduce the behavior: vimPlugin.deoplete-go Yet another python 3.12 distutils breakage <!-- 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-38e38bb0a50b005bfa7554cbea050dd7da8f19077bb88453d1cbe4cc381f68d9","title":"","text":"Steps to reproduce the behavior: vulkan-validation-layers 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.\nThe dependency causing this is vulkan-utility-libraries: 1.3.269 -1.3.270 This version bump causes vulkan-validation-layers to fail. Its only dependency is and that is fine. So problem is\nThe latest SDK version is 1.3.268. vulkan-utility-libraries should be rolled back to that version; we should not be packaging non-SDK versions of Vulkan SDK components, and especially not piecemeal.\nindeed reverting it to fixed the build and runtime"}
{"_id":"doc-en-nixpkgs-35c4e0debd512c79d89f0a0e6dab1dc2463d5cacb84754a5bc2441917deb4268","title":"","text":"roc-toolkit fails to build on aarch64-linux, with the following error: roc-toolkit should build successfully. N/A N/A Please run and paste the result.\nlibunwind/libunwind looks relevant\nDoes upstream support this target?\nBoth libunwind and roc-toolkit seem to support aarch64, yes."}
{"_id":"doc-en-nixpkgs-4526593be160691daa37eabd0f784fdbaae0a46d3dfc2f10abee7f25b494ef19","title":"","text":"Both and are failing on master, which prevents nixos-unstable from advancing. Hydra log: Bisected to: Introduced in\nRevert for now in order to get the zlib update to ? (also needs merging and maybe fixing additional stuff)"}
{"_id":"doc-en-nixpkgs-8787a7ae041dbc2b7ec5a45fd1812088cceeb28bbbe4d3fcf58824e113622c85","title":"","text":"Describe the bug When using mosh/tmux is first read by the login shell that spawns mosh-server, which sets . The actual user shell spawned by mosh will therefor ignore this file and not set its fpath. For that reason all system provided completion functions are ignored.\nThis bug was introduced by in who changed this variable to . What was the reasoning for not changing the environment of interactive non-login shells?\nUm, this was six years ago, but I will attempt to answer the question. :sweat_smile: Consider this scenario: log in and the shell environment is initialized. make some local changes to the environment, and export them. open a sub-shell and the shell environment is re-initialized. changes made in the parent shell environment are not present in the sub-shell, as one would expect. Basically, the zsh initialization process would clobber any environment that you tried to propagate from a parent shell into a child sub-shell.\nCurrently zshenv by default only set fpath and HELPDIR without exporting them. A parent shell would also not set those variables usually as they are shell local. It also sources a file called set-environment but this is protected by an environment variable called . Hence any modification done by the parent shell should persist as long as NIXOSSETENVIRONMENTDONE is not unset. This behavior deviates from what we do in bashrc and breaks common setups such as tmux/mosh or screen. Hence I would revert it.\nI don't think, at that time, this worked as you describe, but it was six years ago, and I haven't used zsh in years anyway, so my memory is not entirely trustworthy. If reverting my commit fixes mosh and tmux, and doesn't obviously break anything else, then go for it!"}
{"_id":"doc-en-nixpkgs-76f313d0173d067adf88236f2c6ccb24f4690c2608336605589e426254494481","title":"","text":"Steps to reproduce the behavior: -rebuild with Just broke a few days ago. Right now I'm trying out Nyx's Cachyos Kernel, but I tried to change to pkgs.linuxPackages_latest. I have not tried to build it on vanilla kernel, as any rebuild fails right now due to this error. Something similar also happened with my framework laptop, but that seems to be resolved <!-- 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. Yes, its cachyos kernel, I to my config though and the issue persists. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:\nProbably needs a update, I'll try looking at this when I get back.\nIndeed there was a patch two weeks ago. Currently not near my desktop machine though."}