{"query_id": "q-en-nixpkgs-00173aa3f82fc56034b96f6914b480abe903a49ef3dc3d3bf485374dfabaf0bf", "query": "])); RemoveIPC = true; RestrictAddressFamilies = [ \"AF_UNIX\" # for sd_notify() call \"AF_UNIX\" \"AF_INET\" \"AF_INET6\" \"AF_NETLINK\" ]; RestrictNamespaces = true; RestrictRealtime = true;", "positive_passages": [{"docid": "doc-en-nixpkgs-9a3fed3e5cfa4fe9faec71122ca8a2269be410e0b0f3d90e00be2f58a68836db", "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.", "commid": "nixpkgs_issue_172944", "tokennum": 62}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-006b8d12f75f556901e4ee744b5993d1f8a16bd2dd85711184b847df479859de", "query": "{ lib , buildGoModule , fetchFromGitHub , fetchYarnDeps , fixup_yarn_lock , grafana-agent , nixosTests , nodejs , stdenv , systemd , testers , yarn }: buildGoModule rec {", "positive_passages": [{"docid": "doc-en-nixpkgs-37c8cf8a361af109b648bdf4ce64fdf071659bbb47ff303d0a8ffd6100aa6124", "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 :) ^", "commid": "nixpkgs_issue_246742", "tokennum": 415}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-008adc617d403a721f6d9926a24517c2e6608051a0b1669ff8a41c307e73f1e5", "query": "buildInputs = [ nss nspr libqb ] ++ optional enableDbus dbus ++ optional enableInfiniBandRdma [ librdmacm libibverbs ] ++ optional enableInfiniBandRdma rdma-core ++ optional enableMonitoring libstatgrab ++ optional enableSnmp net_snmp;", "positive_passages": [{"docid": "doc-en-nixpkgs-010a2a3693a15d2bd177cbeee943f5b4d9e4c44588ef75b26a641ccc3bbfff94", "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 )", "commid": "nixpkgs_issue_34314", "tokennum": 138}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-00bb2a18117d3cbce89039eb97ae720f5603a6b56729774064bdfdd05b5538bb", "query": "{ lib , buildPythonPackage , fetchFromGitHub , setuptools , apispec , boto3 , cachetools", "positive_passages": [{"docid": "doc-en-nixpkgs-8b1f60a4da22f0634f69abae37f027ea0ecae0b0dd101ce64e0ff435d82d6aae", "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!", "commid": "nixpkgs_issue_306848", "tokennum": 158}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-00c3219bb91ff698a593951c56917aa90f7611f73f713ac3e2bab25bb4252058", "query": " { lib , mkYarnPackage , fetchFromGitHub , fetchYarnDeps }: let pname = \"ember-cli\"; version = \"5.3.0\"; src = fetchFromGitHub { owner = \"ember-cli\"; repo = \"ember-cli\"; rev = \"v${version}\"; hash = \"sha256-xkMsPE+iweIV14m4kE4ytEp4uHMJW6gr+n9oJblr4VQ=\"; }; in mkYarnPackage { inherit pname version src; offlineCache = fetchYarnDeps { yarnLock = src + \"/yarn.lock\"; hash = \"sha256-QgT2JFvMupJo+pJc13n2lmHMZkROJRJWoozCho3E6+c=\"; }; packageJSON = ./package.json; meta = with lib; { homepage = \"https://github.com/ember-cli/ember-cli\"; description = \"The Ember.js command line utility\"; license = licenses.mit; maintainers = with maintainers; [ jfvillablanca ]; platforms = platforms.all; mainProgram = \"ember\"; }; } ", "positive_passages": [{"docid": "doc-en-nixpkgs-71474bd610073a818f548a085cdcaaf38531270b5bd7b1f574e912255a4f51d6", "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", "commid": "nixpkgs_issue_250506", "tokennum": 53}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-00d5fe90c425ead71affd61bdc857ad6d311f2f891e6a0b18646b4ac41c822d0", "query": "mongoaudit = callPackage ../tools/security/mongoaudit { }; mongodb-compass = callPackage ../tools/misc/mongodb-compass { }; mongodb-tools = callPackage ../tools/misc/mongodb-tools { }; moosefs = callPackage ../tools/filesystems/moosefs { };", "positive_passages": [{"docid": "doc-en-nixpkgs-9b2ae468a0bb9c7ebe7d386ca9502d1a5cef2d03cd4f2b363afac4dcc6a5bf25", "text": "Package name: mongodb-compass Latest released version: By default, PostgreSQL stores its databases in /var/lib/postgresql/$psqlSchema. You can override this using , e.g. By default, PostgreSQL stores its databases in /var/lib/postgresql/$psqlSchema. You can override this using , e.g. = \"/data/postgresql\"; ", "positive_passages": [{"docid": "doc-en-nixpkgs-e2c8ee84a213c18923e2d9aef55fd9e118160725d549506a7446a052ac7ba782", "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.", "commid": "nixpkgs_issue_7454", "tokennum": 492}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-0b221d7203b5b500f24d6f4aa58625fae296d8fbf838ce23a0f9402ff338cfef", "query": "--> By default, PostgreSQL stores its databases in /var/lib/postgresql/$psqlSchema. You can override this using , e.g. By default, PostgreSQL stores its databases in /var/lib/postgresql/$psqlSchema. You can override this using , e.g. = \"/data/postgresql\"; ", "positive_passages": [{"docid": "doc-en-nixpkgs-b9dc4ebf514fb65f87e5ffe43b99c1cff4c2a6713c5bf4a56d3c890aac684425", "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)", "commid": "nixpkgs_issue_7454", "tokennum": 315}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-0b3c8c4ddcc1265569e92391ddc94358da86b5b706c12361f02b71d34ca4a73a", "query": " { lib , pkgs , alsa-lib , plugins ? [ pkgs.alsa-plugins ] , lndir , symlinkJoin , runCommand }: let merged = symlinkJoin { name = \"alsa-plugins-merged\"; paths = plugins; }; in runCommand \"${alsa-lib.pname}-${alsa-lib.version}\" { meta = with lib; { description = \"wrapper to ease access to ALSA plugins\"; platforms = platforms.linux; maintainers = with maintainers; [ gm6k ]; }; outputs = alsa-lib.outputs; } ( ( lib.concatMapStringsSep \"n\" ( output: '' mkdir ${builtins.placeholder output} ${lndir}/bin/lndir ${lib.attrByPath [output] null alsa-lib} ${builtins.placeholder output} '' ) alsa-lib.outputs ) + '' cp -r ${merged}/lib/alsa-lib $out/lib ( echo $out | wc -c echo ${alsa-lib} | wc -c ) | xargs echo | grep -q \"^(.*) 1$\" || ( echo cannot binary patch exit 1 ) rm $out/lib/libasound.la rm $out/lib/libasound.so.?.?.? rm $dev/lib/pkgconfig/alsa.pc rm $dev/nix-support/propagated-build-inputs cp ${alsa-lib}/lib/libasound.la $out/lib cp ${alsa-lib}/lib/libasound.so.?.?.? $out/lib cp ${alsa-lib.dev}/lib/pkgconfig/alsa.pc $dev/lib/pkgconfig cp ${alsa-lib.dev}/nix-support/propagated-build-inputs $dev/nix-support sed -i $out/lib/libasound.la $out/lib/libasound.so.?.?.? $dev/lib/pkgconfig/alsa.pc $dev/nix-support/propagated-build-inputs -e \"s@${alsa-lib}@$out@g\" '' ) ", "positive_passages": [{"docid": "doc-en-nixpkgs-519c4e91a9b5dbd968fa5be8b65f8ceabf6f7c68a90fc1e3027974a94fccb7a8", "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 \u201cspecial\u201d, or \u201cprofessional\u201d 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\u2019t 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\u2019t the commit that removed the \u201cunused\u201d 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.", "commid": "nixpkgs_issue_6860", "tokennum": 536}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-0b3c8c4ddcc1265569e92391ddc94358da86b5b706c12361f02b71d34ca4a73a", "query": " { lib , pkgs , alsa-lib , plugins ? [ pkgs.alsa-plugins ] , lndir , symlinkJoin , runCommand }: let merged = symlinkJoin { name = \"alsa-plugins-merged\"; paths = plugins; }; in runCommand \"${alsa-lib.pname}-${alsa-lib.version}\" { meta = with lib; { description = \"wrapper to ease access to ALSA plugins\"; platforms = platforms.linux; maintainers = with maintainers; [ gm6k ]; }; outputs = alsa-lib.outputs; } ( ( lib.concatMapStringsSep \"n\" ( output: '' mkdir ${builtins.placeholder output} ${lndir}/bin/lndir ${lib.attrByPath [output] null alsa-lib} ${builtins.placeholder output} '' ) alsa-lib.outputs ) + '' cp -r ${merged}/lib/alsa-lib $out/lib ( echo $out | wc -c echo ${alsa-lib} | wc -c ) | xargs echo | grep -q \"^(.*) 1$\" || ( echo cannot binary patch exit 1 ) rm $out/lib/libasound.la rm $out/lib/libasound.so.?.?.? rm $dev/lib/pkgconfig/alsa.pc rm $dev/nix-support/propagated-build-inputs cp ${alsa-lib}/lib/libasound.la $out/lib cp ${alsa-lib}/lib/libasound.so.?.?.? $out/lib cp ${alsa-lib.dev}/lib/pkgconfig/alsa.pc $dev/lib/pkgconfig cp ${alsa-lib.dev}/nix-support/propagated-build-inputs $dev/nix-support sed -i $out/lib/libasound.la $out/lib/libasound.so.?.?.? $dev/lib/pkgconfig/alsa.pc $dev/nix-support/propagated-build-inputs -e \"s@${alsa-lib}@$out@g\" '' ) ", "positive_passages": [{"docid": "doc-en-nixpkgs-18a978a88d3a4826f2a1d50bea87d4c4b0817e000b5a9acdc38f419c607a5f20", "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. { lib , pkgs , alsa-lib , plugins ? [ pkgs.alsa-plugins ] , lndir , symlinkJoin , runCommand }: let merged = symlinkJoin { name = \"alsa-plugins-merged\"; paths = plugins; }; in runCommand \"${alsa-lib.pname}-${alsa-lib.version}\" { meta = with lib; { description = \"wrapper to ease access to ALSA plugins\"; platforms = platforms.linux; maintainers = with maintainers; [ gm6k ]; }; outputs = alsa-lib.outputs; } ( ( lib.concatMapStringsSep \"n\" ( output: '' mkdir ${builtins.placeholder output} ${lndir}/bin/lndir ${lib.attrByPath [output] null alsa-lib} ${builtins.placeholder output} '' ) alsa-lib.outputs ) + '' cp -r ${merged}/lib/alsa-lib $out/lib ( echo $out | wc -c echo ${alsa-lib} | wc -c ) | xargs echo | grep -q \"^(.*) 1$\" || ( echo cannot binary patch exit 1 ) rm $out/lib/libasound.la rm $out/lib/libasound.so.?.?.? rm $dev/lib/pkgconfig/alsa.pc rm $dev/nix-support/propagated-build-inputs cp ${alsa-lib}/lib/libasound.la $out/lib cp ${alsa-lib}/lib/libasound.so.?.?.? $out/lib cp ${alsa-lib.dev}/lib/pkgconfig/alsa.pc $dev/lib/pkgconfig cp ${alsa-lib.dev}/nix-support/propagated-build-inputs $dev/nix-support sed -i $out/lib/libasound.la $out/lib/libasound.so.?.?.? $dev/lib/pkgconfig/alsa.pc $dev/nix-support/propagated-build-inputs -e \"s@${alsa-lib}@$out@g\" '' ) ", "positive_passages": [{"docid": "doc-en-nixpkgs-1e8505900df2b907f79409ee29ad0a8cbc41abf334d79cacd2583e3de09dd3af", "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.", "commid": "nixpkgs_issue_6860", "tokennum": 518}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-0b3c8c4ddcc1265569e92391ddc94358da86b5b706c12361f02b71d34ca4a73a", "query": " { lib , pkgs , alsa-lib , plugins ? [ pkgs.alsa-plugins ] , lndir , symlinkJoin , runCommand }: let merged = symlinkJoin { name = \"alsa-plugins-merged\"; paths = plugins; }; in runCommand \"${alsa-lib.pname}-${alsa-lib.version}\" { meta = with lib; { description = \"wrapper to ease access to ALSA plugins\"; platforms = platforms.linux; maintainers = with maintainers; [ gm6k ]; }; outputs = alsa-lib.outputs; } ( ( lib.concatMapStringsSep \"n\" ( output: '' mkdir ${builtins.placeholder output} ${lndir}/bin/lndir ${lib.attrByPath [output] null alsa-lib} ${builtins.placeholder output} '' ) alsa-lib.outputs ) + '' cp -r ${merged}/lib/alsa-lib $out/lib ( echo $out | wc -c echo ${alsa-lib} | wc -c ) | xargs echo | grep -q \"^(.*) 1$\" || ( echo cannot binary patch exit 1 ) rm $out/lib/libasound.la rm $out/lib/libasound.so.?.?.? rm $dev/lib/pkgconfig/alsa.pc rm $dev/nix-support/propagated-build-inputs cp ${alsa-lib}/lib/libasound.la $out/lib cp ${alsa-lib}/lib/libasound.so.?.?.? $out/lib cp ${alsa-lib.dev}/lib/pkgconfig/alsa.pc $dev/lib/pkgconfig cp ${alsa-lib.dev}/nix-support/propagated-build-inputs $dev/nix-support sed -i $out/lib/libasound.la $out/lib/libasound.so.?.?.? $dev/lib/pkgconfig/alsa.pc $dev/nix-support/propagated-build-inputs -e \"s@${alsa-lib}@$out@g\" '' ) ", "positive_passages": [{"docid": "doc-en-nixpkgs-4d395059ce1906654c05aa846fa68bccd3fa1ca80d5683d6b94b015958c368e3", "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 \u2014 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. →\nI implemented the aggregate package approach () and appreciate your thoughts on it.", "commid": "nixpkgs_issue_6860", "tokennum": 406}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-0b4ed2c240ed8c4f514b5eea8012023129d7fb423751f18d03410f86d3623705", "query": "{ lib , buildPythonPackage , fetchPypi , mock , nose , pytestCheckHook , pythonOlder , requests , yanc }: buildPythonPackage rec { pname = \"ovh\"; version = \"1.0.0\"; version = \"1.1.0\"; format = \"setuptools\"; disabled = pythonOlder \"3.7\"; src = fetchPypi { inherit pname version; hash = \"sha256-IQzwu0gwfPNPOLQLCO99KL5Hu2094Y+acQBFXVGzHhU=\"; hash = \"sha256-EI+bWjtHEZPOSkWJx3gvS8y//gugMWl3TrBHKsKO9nk=\"; }; propagatedBuildInputs = [ requests ]; preCheck = '' export HOME=$(mktemp -d) ''; nativeCheckInputs = [ mock nose yanc pytestCheckHook ]; # requires network checkPhase = '' nosetests . -e test_config_get_conf -e test_config_get_custom_conf -e test_endpoints -e test_init_from_custom_config ''; pythonImportsCheck = [ \"ovh\" ]; disabledTests = [ # Tests require network access \"test_config_from_files\" \"test_config_from_given_config_file\" \"test_config_from_invalid_ini_file\" \"test_config_from_only_one_file\" \"test_endpoints\" ]; meta = { meta = with lib; { description = \"Thin wrapper around OVH's APIs\"; homepage = \"https://github.com/ovh/python-ovh\"; license = lib.licenses.bsd2; maintainers = [ lib.maintainers.makefu ]; changelog = \"https://github.com/ovh/python-ovh/blob/v${version}/CHANGELOG.md\"; license = licenses.bsd2; maintainers = with maintainers; [ makefu ]; }; }", "positive_passages": [{"docid": "doc-en-nixpkgs-80f5c46561f7ab28752633fd9af584ffb0ecf02cc73993239caef92f717e712c", "text": "Package name: Latest released version: 1.1.0 Source:modules/services/databases/postgresql.nixSource:modules/services/databases/postgresql.nixUpstream documentation:Upstream documentation:", "positive_passages": [{"docid": "doc-en-nixpkgs-e2c8ee84a213c18923e2d9aef55fd9e118160725d549506a7446a052ac7ba782", "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.", "commid": "nixpkgs_issue_7454", "tokennum": 492}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-58f9c9949ba9fc193725363cdc14f3e57b6b49d1b77f4a0281f88ab1c84460ed", "query": " Source:modules/services/databases/postgresql.nixSource:modules/services/databases/postgresql.nixUpstream documentation:Upstream documentation:", "positive_passages": [{"docid": "doc-en-nixpkgs-b9dc4ebf514fb65f87e5ffe43b99c1cff4c2a6713c5bf4a56d3c890aac684425", "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)", "commid": "nixpkgs_issue_7454", "tokennum": 315}], "negative_passages": []}
{"query_id": "q-en-nixpkgs-59290ec2b74a8fb61397cd98ae509c31d5b31f28d83c853870dd6b2e16af0dec", "query": "# Replace version inside sd-boot with something older. See magic[] string in systemd src/boot/efi/boot.c machine.succeed( \"\"\" find /boot -iname '*.efi' -print0 | find /boot -iname '*boot*.efi' -print0 | xargs -0 -I '{}' sed -i 's/#### LoaderInfo: systemd-boot .* ####/#### LoaderInfo: systemd-boot 000.0-1-notnixos ####/' '{}' \"\"\" ) output = machine.succeed(\"/run/current-system/bin/switch-to-configuration boot\") assert \"updating systemd-boot from (000.0-1-notnixos) to \" in output assert \"updating systemd-boot from 000.0-1-notnixos to \" in output ''; };", "positive_passages": [{"docid": "doc-en-nixpkgs-3365c4c5422ca3f7323fa4415145f44ddc3221b7e1c14735e24d5665df168927", "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. ``` ::: ", "positive_passages": [{"docid": "doc-en-nixpkgs-8e7750c6e51e96c62f88d37dd3ab2df7ceb11ea7beed35d0274b23225fe836d8", "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)