Question: <ins> #!/usr/bin/env nix-shell /* #!nix-shell -i node -p nodejs_18 */ import { promises as fs } from 'node:fs'; const constants = { githubUrl: "https://api.github.com/repos/pulsar-edit/pulsar/releases", sha256FileURL: (newVersion) => `https://github.com/pulsar-edit/pulsar/releases/download/v${newVersion}/SHA256SUMS.txt`, x86_64FileName: (newVersion) => `Linux.pulsar-${newVersion}.tar.gz`, aarch64FileName: (newVersion) => `ARM.Linux.pulsar-${newVersion}-arm64.tar.gz`, targetFile: new URL("default.nix", import.meta.url).pathname, }; async function utf16ToUtf8(blob) { // Sometime, upstream saves the SHA256SUMS.txt file in UTF-16, which absolutely breaks node's string handling // So we need to convert this blob to UTF-8 // We need to skip the first 2 bytes, which are the BOM const arrayBuffer = await blob.slice(2).arrayBuffer(); const buffer = Buffer.from(arrayBuffer); const utf8String = buffer.toString('utf16le'); return utf8String; } async function getLatestVersion() { const requestResult = await fetch(constants.githubUrl); if (!requestResult.ok) { console.error("Failed to fetch releases"); console.error(requestResult); process.exit(1); }; let jsonResult = await requestResult.json(); jsonResult = jsonResult.filter((release) => !release.prerelease && !release.draft); if (jsonResult.length == 0) { console.error("No releases found"); process.exit(1); } return jsonResult[0].tag_name.replace(/^v/, ''); } async function getSha256Sum(hashFileContent, targetFile) { // The upstream file has a fomat like this: // 0000000000000000000000000000000000000000000000000000000000000000 targetFile let sha256 = hashFileContent. split('n'). map(line => line.replace("r", "")). // Side-effect of the UTF-16 conversion, if the file was created from Windows filter((line) => line.endsWith(targetFile))[0]. split(' ')[0]; return "sha256-" + Buffer.from(sha256, 'hex').toString('base64'); } async function getSha256Sums(newVersion) { // Upstream provides a file with the hashes of the files, but it's not in the SRI format, and it refers to the compressed tarball // So let's just use nix-prefetch-url to get the hashes of the decompressed tarball, and `nix hash to-sri` to convert them to SRI format const hashFileUrl = constants.sha256FileURL(newVersion); const hashFileContent = await fetch(hashFileUrl).then((response) => response.blob()); const headerbuffer = await hashFileContent.slice(0, 2).arrayBuffer() const header = Buffer.from(headerbuffer).toString('hex'); // We must detect if it's UTF-16 or UTF-8. If it's UTF-16, we must convert it to UTF-8, otherwise just use it as-is const hashFileContentString = header == 'fffe' ? await utf16ToUtf8(hashFileContent) : await hashFileContent.text(); let x86_64; let aarch64; console.log("Getting new hashes"); let promises = [ getSha256Sum(hashFileContentString, constants.x86_64FileName(newVersion)).then((hash) => { x86_64 = hash; }), getSha256Sum(hashFileContentString, constants.aarch64FileName(newVersion)).then((hash) => { aarch64 = hash; }), ]; await Promise.all(promises); return { x86_64, aarch64 }; } async function updateFile(newVersion, sha256Sums, currentFile) { // There is some assumptions in how the file is formatted, but nothing egregious let newFile = currentFile.replace(/version = "(.*)";/, `version = "${newVersion}";`); newFile = newFile.replace(/x86_64-linux.hash = "(.*)";/, `x86_64-linux.hash = "${sha256Sums.x86_64}";`); newFile = newFile.replace(/aarch64-linux.hash = "(.*)";/, `aarch64-linux.hash = "${sha256Sums.aarch64}";`); await fs.writeFile(constants.targetFile, newFile); }; let currentFile = await fs.readFile(constants.targetFile, 'utf8'); let currentVersion = currentFile.match(/version = "(.*)";/)[1]; const newVersion = await getLatestVersion(); if (currentVersion === newVersion) { console.error("Already up to date"); process.exit(0); } console.log("New version: " + newVersion); const sha256Sums = await getSha256Sums(newVersion); console.log(sha256Sums) if (!sha256Sums.x86_64 || !sha256Sums.aarch64) { console.error("Failed to find sha256 sums for the 2 files"); process.exit(1); } updateFile(newVersion, sha256Sums, currentFile); </ins>

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


Question: [ zlib glib libpng freetype xorg.libSM xorg.libICE xorg.libXrender openssl xorg.libXrandr xorg.libXfixes xorg.libXcursor xorg.libXinerama xorg.libxcb fontconfig xorg.libXext xorg.libX11 alsa-lib qtbase qtwebengine qtwebchannel qtsvg <del> qtwebsockets libpulseaudio quazip llvmPackages.libcxx llvmPackages.libcxxabi </del> <ins> qtwebsockets libpulseaudio quazip llvmPackages_10.libcxx llvmPackages_10.libcxxabi # llvmPackages_11 and higher crash https://github.com/NixOS/nixpkgs/issues/161395 </ins> ]; desktopItem = makeDesktopItem {

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.
Running 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.
Bad is which is a staging-next merge. Bisecting staging-next now...
Bad is . (Note: Injecting a cached qtwebengine saves a lot of time here and doesn't falsify results.)


Question: <ins> diff --git a/build.gradle b/build.gradle index c206e2f..cdaddf7 100644 --- a/build.gradle +++ b/build.gradle @@ -16,7 +16,7 @@ version = '0.22.3' sourceCompatibility = '17' repositories { -    mavenCentral() +    maven { url '@deps@' } } diff --git a/settings.gradle b/settings.gradle index f813993..2c87f3c 100644 --- a/settings.gradle +++ b/settings.gradle @@ -1 +1,7 @@ +pluginManagement { +    repositories { +        maven { url '@deps@' } +    } +} + rootProject.name = 'Stirling-PDF' </ins>

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]:
I'll see what I can do, should be good practice working with Gradle apps
Thank you Tom, much appreciated, best of luck.
By 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.
See if this helps you.. or this discussion from the top (concerning java apps)...
Thanks 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
Thank 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.


Question: <del> { lib , fetchFromGitHub , python3 }: python3.pkgs.buildPythonApplication rec { pname = "crackmapexec"; version = "5.4.0"; format = "pyproject"; src = fetchFromGitHub { owner = "Porchetta-Industries"; repo = "CrackMapExec"; rev = "refs/tags/v${version}"; hash = "sha256-V2n840QyLofTfQE4vtFYGfQwl65sklp+KfNS9RCLvI8="; }; nativeBuildInputs = with python3.pkgs; [ poetry-core ]; propagatedBuildInputs = with python3.pkgs; [ aioconsole aardwolf beautifulsoup4 dsinternals impacket lsassy masky msgpack neo4j paramiko pylnk3 pypsrp pywerview requests requests-ntlm termcolor terminaltables xmltodict ]; postPatch = '' substituteInPlace pyproject.toml  --replace '{ git = "https://github.com/mpgn/impacket.git", branch = "master" }' '"x"' ''; pythonRelaxDeps = true; # Project has no tests doCheck = false; pythonImportsCheck = [ "cme" ]; meta = with lib; { description = "Tool for pentesting networks"; homepage = "https://github.com/Porchetta-Industries/CrackMapExec"; changelog = "https://github.com/Porchetta-Industries/CrackMapExec/releases/tag/v${version}"; license = with licenses; [ bsd2 ]; maintainers = with maintainers; [ fab ]; mainProgram = "cme"; }; } </del>

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


Question: meta = with lib; { description = "Your everyday IRC student"; homepage = "https://sr.ht/~taiite/senpai/"; <ins> changelog = "https://git.sr.ht/~delthas/senpai/refs/v${version}"; </ins> license = licenses.isc; maintainers = with maintainers; [ malte-v ]; };

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


Question: (fetchNuGet { pname = "System.Security.Permissions"; version = "6.0.0"; sha256 = "0jsl4xdrkqi11iwmisi1r2f2qn5pbvl79mzq877gndw6ans2zhzw"; }) (fetchNuGet { pname = "System.Security.Principal"; version = "4.3.0"; sha256 = "12cm2zws06z4lfc4dn31iqv7072zyi4m910d4r6wm8yx85arsfxf"; }) (fetchNuGet { pname = "System.Security.Principal.Windows"; version = "4.3.0"; sha256 = "00a0a7c40i3v4cb20s2cmh9csb5jv2l0frvnlzyfxh848xalpdwr"; }) <ins> (fetchNuGet { pname = "System.Security.Principal.Windows"; version = "5.0.0"; sha256 = "1mpk7xj76lxgz97a5yg93wi8lj0l8p157a5d50mmjy3gbz1904q8"; }) </ins> (fetchNuGet { pname = "System.Security.Principal.Windows"; version = "6.0.0-preview.5.21301.5"; sha256 = "1q3iikvjcfrm5p89p1j7qlw1szvryq680qypk023wgy9phmlwi57"; }) (fetchNuGet { pname = "System.Text.Encoding"; version = "4.0.11"; sha256 = "1dyqv0hijg265dwxg6l7aiv74102d6xjiwplh2ar1ly6xfaa4iiw"; }) (fetchNuGet { pname = "System.Text.Encoding"; version = "4.3.0"; sha256 = "1f04lkir4iladpp51sdgmis9dj4y8v08cka0mbmsy0frc9a4gjqr"; })

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.


Question: src = fetchsvn { url = "http://winetricks.googlecode.com/svn/trunk"; inherit rev; <ins> sha256 = "01v13qw4sxmfm09g9amqycnzy743gdrhvv23rjr9255dzlrj1s8f"; </ins> }; buildInputs = [ perl which ];

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.
I found a similar problem report in macports. Shall we include /bin/ps visible in cmake environment in darwin systems?
Is there no way to hard-code the path of into CMake?
isn't actually in .
The 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.
We 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
This was fixed as part of the new darwin stdenv.


Question: <ins> { lib , stdenvNoCC , fetchFromGitHub }: stdenvNoCC.mkDerivation (finalAttrs: { pname = "cmrc"; version = "2.0.1"; src = fetchFromGitHub { owner = "vector-of-bool"; repo = "cmrc"; rev = finalAttrs.version; hash = "sha256-++16WAs2K9BKk8384yaSI/YD1CdtdyXVBIjGhqi4JIk="; }; installPhase = '' runHook preInstall install CMakeRC.cmake -DT $out/share/cmakerc/cmakerc-config.cmake runHook postInstall ''; meta = { description = "A Resource Compiler in a Single CMake Script"; homepage = "https://github.com/vector-of-bool/cmrc"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ guekka ]; platforms = lib.platforms.all; }; }) </ins>

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
I'll try something now.
Reading the , it looks like a case for a module, not merely a package.
I'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.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Maybe 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).
Would be nice to have!
Work is ongoing here:


Question: final Uri entryUri = globals.fs.path.toUri(font['asset'] as String); result.add(_Asset( -        baseDir: globals.fs.path.join(Cache.flutterRoot, 'bin', 'cache', 'artifacts', 'material_fonts'), <del> +        baseDir: globals.fs.path.join(homeDirPath, '.cache', 'flutter', 'artifacts', 'material_fonts'), </del> <ins> +        baseDir: globals.fs.path.join(globals.fsUtils.homeDirPath, '.cache', 'flutter', 'artifacts', 'material_fonts'), </ins> relativeUri: Uri(path: entryUri.pathSegments.last), entryUri: entryUri, ));

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?
Hey it's fixed in the latest commit. Can you try it ?
Works fine, thank you very much for the fast fix!


Question: stdenv.mkDerivation rec { pname = "tomb"; <del> version = "2.7"; </del> <ins> version = "2.9"; </ins> src = fetchFromGitHub { owner  = "dyne"; repo   = "Tomb"; rev    = "v${version}"; <del> sha256 = "1vzkpzci6cp1r1q2n34pcgcns78i726k8d89dd6pibyj0vfnkl57"; </del> <ins> sha256 = "0d6vmfcf4kd0p2bcljmdnyc2fmbwvar81cc472zx86r7yc3ih102"; </ins> }; buildInputs = [ sudo zsh pinentry ];

, CVSSv3=9.8 (nixos-20.09) Scanned versions: nixos-20.09: . Cc


Question: buildPackages.libgphoto2; in '' <del> mkdir -p $out/lib/udev/rules.d </del> <ins> mkdir -p $out/lib/udev/{rules.d,hwdb.d} </ins> ${executablePrefix}/lib/libgphoto2/print-camera-list  <del> udev-rules version 175 group camera  >$out/lib/udev/rules.d/40-gphoto2.rules </del> <ins> udev-rules version 201 group camera  >$out/lib/udev/rules.d/40-libgphoto2.rules ${executablePrefix}/lib/libgphoto2/print-camera-list  hwdb version 201 group camera  >$out/lib/udev/hwdb.d/20-gphoto.hwdb </ins> ''; meta = {

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)
For reference Fedora


Question: qtwebsockets = callPackage ./modules/qtwebsockets.nix { }; qtwebview = callPackage ./modules/qtwebview.nix { }; <del> wrapQtAppsHook = makeSetupHook { deps = [ self.qtbase.dev self.qtwayland.dev makeWrapper ]; </del> <ins> wrapQtAppsHook = makeSetupHook { deps = [ makeWrapper ]; </ins> } ./hooks/wrap-qt-apps-hook.sh; };

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
I'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.
Actually we are abusing qtwayland as a shortcut to bringing in qtdeclarative, this should be fixed too.
we 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
Adding the lines to nixpkgs manual is sufficient.
By 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.


Question: esneider/YUNOcommit.vim euclidianAce/BetterLua.vim euclio/vim-markdown-composer <ins> evanleck/vim-svelte </ins> f-person/git-blame.nvim f3fora/cmp-spell famiu/bufdelete.nvim

Project description Various vim plugins iamcco/coc-tailwindcss coc-extensions/coc-svelte evanleck/vim-svelte


Question: , zlib , alsa-lib , dbus <ins> , libGL </ins> , libXcursor , libXext , libXi

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]:
I noticed this as well yesterday running nixos-unstable


Question: <ins> { lib , stdenv , fetchFromGitHub , cacert , cmake , cmakerc , fmt , git , gzip , makeWrapper , meson , ninja , openssh , python3 , zip , zstd , extraRuntimeDeps ? [] }: stdenv.mkDerivation (finalAttrs: { pname = "vcpkg-tool"; version = "2023-10-18"; src = fetchFromGitHub { owner = "microsoft"; repo = "vcpkg-tool"; rev = finalAttrs.version; hash = "sha256-Hm+GSKov9A6tmN10BHOTVy8aWkLOJNBMOQJNm4HnWuI="; }; nativeBuildInputs = [ cmake cmakerc fmt ninja makeWrapper ]; patches = [ ./change-lock-location.patch ]; cmakeFlags = [ "-DVCPKG_DEPENDENCY_EXTERNAL_FMT=ON" "-DVCPKG_DEPENDENCY_CMAKERC=ON" ]; postFixup = let # These are the most common binaries used by vcpkg # Extra binaries can be added via overlay when needed runtimeDeps = [ cacert cmake git gzip meson ninja openssh python3 zip zstd ] ++ extraRuntimeDeps; in '' wrapProgram $out/bin/vcpkg --prefix PATH ${lib.makeBinPath runtimeDeps} ''; meta = { description = "Components of microsoft/vcpkg's binary"; homepage = "https://github.com/microsoft/vcpkg-tool"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ guekka gracicot ]; platforms = lib.platforms.all; }; }) </ins>


Question: }; in rustPlatform.buildRustPackage rec { pname = "tokenizers"; <del> version = "0.8.1.rc1"; </del> <ins> version = "0.8.1"; </ins> src = fetchFromGitHub { owner = "huggingface"; repo = pname; rev = "python-v${version}"; <del> sha256 = "1bzvfffnjjskx8zlq1qsqfd47570my2wnbq4ip8i1hkz10q900qv"; </del> <ins> sha256 = "0sxdwx05hr87j2z32rk4rgwn6a26w9r7m5fgj6ah1sgagiiyxbjw"; </ins> }; <del> cargoSha256 = "0s5z3g1njb7wlyb32ba6xas4zc62c3zhmp1mrvghmaxpvljp6k7b"; </del> <ins> # Update parking_lot to be compatible with recent Rust versions, that # replace asm! by llvm_asm!: # # https://github.com/Amanieu/parking_lot/pull/223 # # Remove once upstream updates this dependency. cargoPatches = [ ./update-parking-lot.diff ]; cargoSha256 = "0cdkxmj8z2wdspn6r62lqlpvd0sj1z0cmb1zpqaajxvr0b2kjlj8"; </ins> sourceRoot = "source/bindings/python";

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:
Thanks 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.


Question: doCheck = true; <ins> preFixup = '' makeWrapperArgs+=(  "''${gappsWrapperArgs[@]}"  --prefix PATH : "${lib.makeBinPath [ iw ]}"  ) ''; </ins> postFixup = '' wrapPythonPrograms <del> wrapProgram $out/bin/networkd-dispatcher --prefix PATH : ${lib.makeBinPath [ iw ]} </del> ''; meta = with lib; {

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


Question: sbt-with-scala-native = callPackage ../development/tools/build-managers/sbt/scala-native.nix { }; simpleBuildTool = sbt; <ins> sbt-extras = callPackage ../development/tools/build-managers/sbt-extras { }; </ins> shallot = callPackage ../tools/misc/shallot { }; shards = callPackage ../development/tools/build-managers/shards { };

I'm told a lot of people favor Paul Phillips' SBT wrapper over vanilla SBT. We probably ought to have a package for it.
Minus the parts where it auto-downloads sbt for you, I expect
Mmm, I don't know. Isn't it kind of important to be able to auto-download the appropriate version of sbt for each project?
Maybe? 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.


Question: listening_ip=${range} '') cfg.internalIPs} <ins> ${lib.optionalString (firewall == "nftables") '' upnp_table_name=miniupnpd upnp_nat_table_name=miniupnpd ''} </ins> ${cfg.appendConfig} ''; <ins> firewall = if config.networking.nftables.enable then "nftables" else "iptables"; miniupnpd = pkgs.miniupnpd.override { inherit firewall; }; firewallScripts = lib.optionals (firewall == "iptables") ([ "iptables"] ++ lib.optional (config.networking.enableIPv6) "ip6tables"); </ins> in { options = {

We already have in , but only with iptables support. It would be nice to have the nftables version available as well.
Being worked on in , I'm trying to test myself but couldn't make it to work yet.
I think the PR is ready now, testing welcome!
Maybe add an option for will be better?


Question: <ins> --- old/build/pkgs/python2/spkg-install	2017-07-21 14:10:00.000000000 -0500 +++ new/build/pkgs/python2/spkg-install	2017-10-15 11:26:54.823134067 -0500 @@ -22,6 +22,9 @@ cd src +LDFLAGS="-lcrypt $LDFLAGS" +export LDFLAGS + if [ "$SAGE_DEBUG" = "yes" ]; then echo "Building Python with pydebug" PYTHON_CONFIGURE="$PYTHON_CONFIGURE --with-pydebug" </ins>

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:
thanks for picking this up
Me 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.
Can 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
I 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.
In 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.


Question: <ins> --- old/build/pkgs/python2/spkg-install	2017-07-21 14:10:00.000000000 -0500 +++ new/build/pkgs/python2/spkg-install	2017-10-15 11:26:54.823134067 -0500 @@ -22,6 +22,9 @@ cd src +LDFLAGS="-lcrypt $LDFLAGS" +export LDFLAGS + if [ "$SAGE_DEBUG" = "yes" ]; then echo "Building Python with pydebug" PYTHON_CONFIGURE="$PYTHON_CONFIGURE --with-pydebug" </ins>

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:


Question: <del> { lib, buildGoModule, installShellFiles, fetchFromGitHub, ffmpeg, ttyd, makeWrapper }: </del> <ins> { lib, buildGoModule, installShellFiles, fetchFromGitHub, ffmpeg, ttyd, chromium, makeWrapper }: </ins> buildGoModule rec { pname = "vhs";

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.
Nixpkgs has since been updated to the latest version (v0.2.0), and the error still occurs on the latest Nixpkgs commit ()
Any suggestions on a fix?
I 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):
The PR for this breaks vhs on darwin, since chromium isn't supported on that platform
Thanks for filing a new issue


Question: { lib , stdenvNoCC <ins> , stdenv </ins> , fetchurl <ins> , autoPatchelfHook </ins> , undmg <ins> , zstd , curl , fontconfig , libglvnd , libxkbcommon , vulkan-loader , xdg-utils , xorg , zlib </ins> }: <del> stdenvNoCC.mkDerivation (finalAttrs: { pname = "warp-terminal"; version = "0.2023.12.05.08.02.stable_00"; </del> <ins> let pname = "warp-terminal"; version = "0.2024.02.20.08.01.stable_01"; linux = stdenv.mkDerivation (finalAttrs:  { inherit pname version meta; src = fetchurl { url = "https://releases.warp.dev/stable/v${finalAttrs.version}/warp-terminal-v${finalAttrs.version}-1-x86_64.pkg.tar.zst"; hash = "sha256-L8alnqSE4crrDozRfPaAAMkLc+5+8d9XBKd5ddsxmD0="; }; sourceRoot = "."; postPatch = '' substituteInPlace usr/bin/warp-terminal  --replace-fail /opt/ $out/opt/ ''; nativeBuildInputs = [ autoPatchelfHook zstd ]; buildInputs = [ curl fontconfig stdenv.cc.cc.lib # libstdc++.so libgcc_s.so zlib ]; runtimeDependencies = [ libglvnd # for libegl libxkbcommon stdenv.cc.libc vulkan-loader xdg-utils xorg.libX11 xorg.libxcb xorg.libXcursor xorg.libXi ]; installPhase = '' runHook preInstall mkdir $out cp -r opt usr/* $out runHook postInstall ''; }); darwin = stdenvNoCC.mkDerivation (finalAttrs: { inherit pname version meta; </ins> src = fetchurl { url = "https://releases.warp.dev/stable/v${finalAttrs.version}/Warp.dmg"; <del> hash = "sha256-9olAmczIPRXV15NYCOYmwuEmJ7lMeaQRTTfukaYXMR0="; </del> <ins> hash = "sha256-tFtoD8URMFfJ3HRkyKStuDStFkoRIV97y9kV4pbDPro="; </ins> }; sourceRoot = ".";

Project description see Metadata homepage URL: source URL: license: unfree platforms: darwin, linux
I was just checking myself and it's been there since November apparently
Ah, don't mind me, not checking the platforms...


Question: githubId = 21156405; name = "GuangTao Zhang"; }; <ins> guekka = { github = "Guekka"; githubId = 39066502; name = "Guekka"; }; </ins> guibert = { email = "david.guibert@gmail.com"; github = "dguibert";


Question: { stdenv, lib, runCommand, patchelf , fetchFromGitHub, rustPlatform <del> , pkgconfig, curl, Security, CoreServices }: </del> <ins> , pkgconfig, curl, zlib, Security, CoreServices }: </ins> rustPlatform.buildRustPackage rec { pname = "rustup";

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:
We 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.
Here is where we add :
I'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
Extending the RPATH seems not to have worked
I'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


Question: pycharm-professional = buildPycharm rec { name = "pycharm-professional-${version}"; <del> version = "2019.3.4"; /* updated by script */ </del> <ins> version = "2020.1"; /* updated by script */ </ins> description = "PyCharm Professional Edition"; license = stdenv.lib.licenses.unfree; src = fetchurl { url = "https://download.jetbrains.com/python/${name}.tar.gz"; <del> sha256 = "1hdwzkh6qzad2pqskqw9m8glj15x9d2g4csl0dxk6an82ps52naz"; /* updated by script */ </del> <ins> sha256 = "1swd2qfhsa6i1aq7z2s183d0hif2gmk1kkw9ns4aybny0wvvnqw2"; /* updated by script */ </ins> }; wmClass = "jetbrains-pycharm"; update-channel = "PyCharm RELEASE";

Please update Goland to a current version. The Current Version is now 2020.1 Thx and Greetz


Question: <del> let inherit (import <nixpkgs> { }) snapTools firefox; in snapTools.makeSnap { meta = { name = "nix-example-firefox"; summary = firefox.meta.description; architectures = [ "amd64" ]; apps.nix-example-firefox = { command = "${firefox}/bin/firefox"; plugs = [ "pulseaudio" "camera" "browser-support" "avahi-observe" "cups-control" "desktop" "desktop-legacy" "gsettings" "home" "network" "mount-observe" "removable-media" "x11" ]; }; confinement = "strict"; }; } </del>

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.


Question: <del> let inherit (import <nixpkgs> { }) snapTools firefox; in snapTools.makeSnap { meta = { name = "nix-example-firefox"; summary = firefox.meta.description; architectures = [ "amd64" ]; apps.nix-example-firefox = { command = "${firefox}/bin/firefox"; plugs = [ "pulseaudio" "camera" "browser-support" "avahi-observe" "cups-control" "desktop" "desktop-legacy" "gsettings" "home" "network" "mount-observe" "removable-media" "x11" ]; }; confinement = "strict"; }; } </del>

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.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I opened a PR here: Thanks in advance for reviewing :-)


Question: <del> diff -ru binutils-2.27-orig/bfd/plugin.c binutils-2.27/bfd/plugin.c --- binutils-2.27-orig/bfd/plugin.c	2016-10-14 17:46:30.791315555 +0200 +++ binutils-2.27/bfd/plugin.c	2016-10-14 17:46:38.583298765 +0200 @@ -333,6 +333,7 @@ </del> <ins> diff --git a/bfd/plugin.c b/bfd/plugin.c index 537ab60311..bfe7957f96 100644 --- a/bfd/plugin.c +++ b/bfd/plugin.c @@ -386,6 +386,7 @@ load_plugin (bfd *abfd) </ins> if (plugin_program_name == NULL) return found; +#if 0 <del> plugin_dir = concat (BINDIR, "/../lib/bfd-plugins", NULL); p = make_relative_prefix (plugin_program_name, BINDIR, @@ -364,6 +365,7 @@ free (p); if (d) closedir (d); </del> <ins> /* Try not to search the same dir twice, by looking at st_dev and st_ino for the dir.  If we are on a file system that always sets st_ino to zero or the actual st_ino is zero we might waste some @@ -437,7 +438,7 @@ load_plugin (bfd *abfd) if (found) break; } - </ins> +#endif return found; }

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.
This was solved by cc.
Thank you for continuing this work!


Question: pycurl ]); <ins> patches = [ (fetchpatch { url = "https://github.com/indigo-dc/udocker/commit/9f7d6c5f9a3925bf87d000603c5b306d73bb0fa3.patch"; sha256 = "sha256-fiqvVqfdVIlILbSs6oDWmbWU9piZEI2oiAKUcmecx9Q="; }) ]; </ins> checkInputs = with python3Packages; [ pytestCheckHook ]; disabledTests = [ <ins> "test_02__load_structure" </ins> "test_05__get_volume_bindings" ];

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.


Question: buildPythonPackage rec { pname = "python-telegram-bot"; <del> version = "20.2"; </del> <ins> version = "20.4"; </ins> format = "setuptools"; <del> disabled = pythonOlder "3.7"; </del> <ins> disabled = pythonOlder "3.8"; </ins> src = fetchFromGitHub { owner = pname; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-OdjTlVUjlw+5K/kvL1Yx+7c/lIE52udUo6Ux18M9xmE="; </del> <ins> hash = "sha256-owbJJZjBkMjsgfBLRl+rnePrIvQ0sUZs7rP9ie912pw="; </ins> }; propagatedBuildInputs = [

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.


Question: patches = [ (fetchurl { name = "texlive-poppler-0.64.patch"; <del> url = https://git.archlinux.org/svntogit/packages.git/plain/trunk/texlive-poppler-0.64.patch?h=packages/texlive-bin; </del> <ins> url = https://git.archlinux.org/svntogit/packages.git/plain/trunk/texlive-poppler-0.64.patch?h=packages/texlive-bin&id=da56abf0f8a1e85daca0ec0f031b8fa268519e6b; </ins> sha256 = "0443d074zl3c5raba8jyhavish706arjcd80ibb84zwnwck4ai0w"; }) (fetchurl {

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?
Probably should just add into nixpkgs instead of fetching it.
another alternative is add the commit rev which seems to have the same hash


Question: <ins> { lib , buildPythonPackage , fetchFromGitHub , pythonOlder , dill , astropy , numpy , pandas , qt6 , pyqt6 , pyqt-builder , qtconsole , setuptools , setuptools-scm , scipy , ipython , ipykernel , h5py , matplotlib , xlrd , mpl-scatter-density , pvextractor , openpyxl , echo , pytest , pytest-flakes , pytest-cov }: buildPythonPackage rec { pname = "glueviz"; version = "1.14.1"; disabled = pythonOlder "3.7"; src = fetchFromGitHub { owner = "glue-viz"; repo = "glue"; rev = "refs/tags/v${version}"; sha256 = "sha256-pHUcvyDziE7l0foEz7cygMuAwggnIWzsQy9SFZCDkXA="; }; buildInputs = [ pyqt-builder ]; nativeBuildInputs = [ setuptools setuptools-scm qt6.wrapQtAppsHook ]; propagatedBuildInputs = [ astropy dill setuptools scipy numpy matplotlib pandas pyqt6 qtconsole ipython ipykernel h5py xlrd mpl-scatter-density pvextractor openpyxl echo ]; dontConfigure = true; env.SETUPTOOLS_SCM_PRETEND_VERSION = version; # collecting ... qt.qpa.xcb: could not connect to display # qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. doCheck = false; nativeCheckInputs = [ pytest pytest-flakes pytest-cov ]; pythonImportsCheck = [ "glue" ]; preFixup = '' makeWrapperArgs+=("''${qtWrapperArgs[@]}") ''; meta = with lib; { homepage = "https://glueviz.org"; description = "Linked Data Visualizations Across Multiple Files"; license = licenses.bsd3; # https://github.com/glue-viz/glue/blob/main/LICENSE maintainers = with maintainers; [ ifurther ]; }; } </ins>

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


Question: <ins> { stdenv, lib, python3Packages, fetchFromGitHub, copyDesktopItems, makeDesktopItem, wrapGAppsHook4, gobject-introspection, libadwaita, libportal, libportal-gtk4, xdg-desktop-portal, xdg-desktop-portal-gtk, }: stdenv.mkDerivation rec { pname = "streamcontroller"; # Note that the latest tagged version (1.5.0-beta.6) includes a python dependency # that doesn't exist anymore, so we package an unstable version instead. version = "1.5.0-beta.6-unstable-2024-08-13"; src = fetchFromGitHub { repo = "StreamController"; owner = "StreamController"; rev = "dbb6460a69137af192db09d504224ae9f1127cbd"; hash = "sha256-+YYzHLRU5MNjF3iaKIDj9k4PVg+vnEZhbc3ZmNI7xyw="; }; # The installation method documented upstream # (https://streamcontroller.github.io/docs/latest/installation/) is to clone the repo, # run `pip install`, then run `python3 main.py` to launch the program. # Due to how the code is structured upstream, it's infeasible to use `buildPythonApplication`. dontBuild = true; installPhase = '' runHook preInstall mkdir -p $out/usr/lib/streamcontroller cp -r ./* $out/usr/lib/streamcontroller/ mkdir -p $out/bin/ # Note that the implementation of main.py assumes # working directory to be at the root of the project's source code makeWrapper  ${python3Packages.python.interpreter}  $out/bin/streamcontroller  --add-flags main.py  --chdir $out/usr/lib/streamcontroller  --prefix PYTHONPATH : "$PYTHONPATH" mkdir -p "$out/etc/udev/rules.d" cp ./udev.rules $out/etc/udev/rules.d/70-streamcontroller.rules install -D ./flatpak/icon_256.png $out/share/icons/hicolor/256x256/apps/streamcontroller.png runHook postInstall ''; desktopItems = [ (makeDesktopItem { name = "StreamController"; desktopName = "StreamController"; exec = "streamcontroller"; icon = "streamcontroller"; comment = "Control your Elgato Stream Decks"; categories = [ "Utility" ]; }) ]; nativeBuildInputs = [ copyDesktopItems wrapGAppsHook4 gobject-introspection ]; buildInputs = [ libadwaita libportal libportal-gtk4 xdg-desktop-portal xdg-desktop-portal-gtk ] ++ (with python3Packages; [ annotated-types async-lru cairocffi cairosvg certifi cffi charset-normalizer click colorama contourpy cssselect2 cycler dbus-python decorator defusedxml distlib dnspython evdev filelock fonttools fuzzywuzzy gcodepy get-video-properties gitdb idna imageio imageio-ffmpeg indexed-bzip2 jinja2 joblib kiwisolver levenshtein linkify-it-py loguru markdown-it-py markupsafe matplotlib mdit-py-plugins mdurl meson meson-python natsort nltk numpy opencv4 packaging pillow platformdirs plumbum proglog psutil pulsectl pycairo pyclip pycparser pydantic pydantic-core pyenchant pygments pygobject3 pymongo pyparsing pyperclip pyproject-metadata pyro5 pyspellchecker python-dateutil pyudev pyusb pyyaml rapidfuzz regex requests requirements-parser rich rpyc serpent setproctitle six smmap speedtest-cli streamcontroller-plugin-tools streamdeck textual tinycss2 tqdm types-setuptools typing-extensions uc-micro-py urllib3 usb-monitor webencodings websocket-client ]); meta = with lib; { description = "Elegant Linux app for the Elgato Stream Deck with support for plugins"; homepage = "https://core447.com/"; license = licenses.gpl3; mainProgram = "streamcontroller"; maintainers = with maintainers; [ sifmelcara ]; platforms = lib.platforms.linux; }; } </ins>

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]:
For people who subscribed to this issue: I opened to add streamcontroller


Question: <ins> { config, lib, pkgs, ... }: let inherit (lib) types; cfg = config.services.open-webui; in { options = { services.open-webui = { enable = lib.mkEnableOption "Enable open-webui, an interactive chat web app"; package = lib.mkPackageOption pkgs "open-webui" { }; stateDir = lib.mkOption { type = types.path; default = "/var/lib/open-webui"; description = "State directory of open-webui."; }; host = lib.mkOption { type = types.str; default = "localhost"; description = "Host of open-webui"; }; port = lib.mkOption { type = types.port; default = 8080; description = "Port of open-webui"; }; environment = lib.mkOption { type = types.attrsOf types.str; default = { }; example = '' { OLLAMA_API_BASE_URL = "http://localhost:11434"; # Disable authentication WEBUI_AUTH = "False"; } ''; description = "Extra environment variables for open-webui"; }; }; }; config = lib.mkIf cfg.enable { systemd.services.open-webui = { description = "User-friendly WebUI for LLMs (Formerly Ollama WebUI)"; wantedBy = [ "multi-user.target" ]; after = [ "network.target" ]; preStart = '' mkdir -p ${cfg.stateDir}/static ''; environment = { STATIC_DIR = "${cfg.stateDir}/static"; DATA_DIR = "${cfg.stateDir}"; } // cfg.environment; serviceConfig = { ExecStart = "${lib.getExe cfg.package} serve --host ${cfg.host} --port ${toString cfg.port}"; WorkingDirectory = cfg.stateDir; StateDirectory = "open-webui"; RuntimeDirectory = "open-webui"; RuntimeDirectoryMode = "0755"; PrivateTmp = true; DynamicUser = true; DevicePolicy = "closed"; LockPersonality = true; MemoryDenyWriteExecute = false; # onnxruntime/capi/onnxruntime_pybind11_state.so: cannot enable executable stack as shared object requires: Permission Denied PrivateUsers = true; ProtectHome = true; ProtectHostname = true; ProtectKernelLogs = true; ProtectKernelModules = true; ProtectKernelTunables = true; ProtectControlGroups = true; ProcSubset = "all"; # Error in cpuinfo: failed to parse processor information from /proc/cpuinfo RestrictNamespaces = true; RestrictRealtime = true; SystemCallArchitectures = "native"; UMask = "0077"; }; }; }; meta.maintainers = with lib.maintainers; [ shivaraj-bh ]; } </ins>

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]:
Relevant Merge Request:
Just for reference / workaround here's another nix package:
Thanks 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.
I 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 .
I 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 !!!
Thank 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.


Question: cd src ''; <ins> postInstall = stdenv.lib.optionalString stdenv.isDarwin '' substituteInPlace $out/bin/leanpkg  --replace "greadlink" "${coreutils}/bin/readlink" ''; </ins> meta = with stdenv.lib; { description = "Automatic and interactive theorem prover"; homepage    = "https://leanprover.github.io/";

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:
Sounds most easiest to implement and maintain.


Question: , stdenv , fetchFromGitLab , appstream-glib <del> , clang </del> , desktop-file-utils , meson , ninja

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.
Same issue with  (
I 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.
Ah, I see. There is a related PR for Amberol:
What commit did you build from? I’d like to bisect
My 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.
if you’re updating the version to point to an unreleased version the should
Indeed, 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_
Hi 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.
Is 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.
In 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?
We’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.
(how naive of me.


Question: , stdenv , fetchFromGitLab , appstream-glib <del> , clang </del> , desktop-file-utils , meson , ninja

maybe just building from is better)
Opened 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.
You were right - thanks for the hint! - I was indeed still building fractal-next from before the fix :disappointed:


Question: lapack-reference = callPackage ../development/libraries/science/math/liblapack { }; liblapack = lapack-reference; <ins> libamplsolver = callPackage ../development/libraries/science/math/libamplsolver { }; </ins> libbraiding = callPackage ../development/libraries/science/math/libbraiding { }; libhomfly = callPackage ../development/libraries/science/math/libhomfly { };

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:
was 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:
It appears that the binary requires AMPL, a commercial package, which is not packaged in nixpkgs. See: https://coin-
ah, I understand. Thank you.


Question: gdal = self.gdal; }; <del> django_2_0 = callPackage ../development/python-modules/django/2_0.nix { gdal = self.gdal; }; </del> django_2_1 = callPackage ../development/python-modules/django/2_1.nix { gdal = self.gdal; };

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
agreed. For 19.03 we will only support 1.11 and 2.1 (and probably port 2.2 when it gets available).


Question: python = python3; in python.pkgs.buildPythonApplication rec { pname = "spotdl"; <del> version = "4.2.1"; format = "pyproject"; </del> <ins> version = "4.2.2"; pyproject = true; </ins> src = fetchFromGitHub { owner = "spotDL"; repo = "spotify-downloader"; rev = "refs/tags/v${version}"; <del> hash = "sha256-xKas3WO3uigY1iFfxIN3+d+5U31vM7cLv08oMef8trc="; </del> <ins> hash = "sha256-pJr0OGUI3OcFsmvn9eqkvpFeF1EkHDdNoWc91s8h9O8="; </ins> }; nativeBuildInputs = with python.pkgs; [

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.


Question: komorebi = callPackage ../applications/graphics/komorebi { }; <ins> konsave = callPackage ../applications/misc/konsave { }; </ins> krapslog = callPackage ../tools/misc/krapslog { }; krelay = callPackage ../applications/networking/cluster/krelay { };

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


Question: postInstall = '' mkdir -p $out/bin ln -s $out/stepmania-5.1/stepmania $out/bin/stepmania <ins> mkdir -p $out/share/ cp -r $src/icons $out/share/ install -Dm444 $src/stepmania.desktop -t $out/share/applications </ins> ''; meta = with lib; {

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:
I marked this as stale due to inactivity. →


Question: sourceProvenance = with sourceTypes; [ binaryBytecode ]; license = licenses.unfree; platforms = [ "x86_64-linux" "aarch64-linux" "x86_64-darwin" ]; <del> maintainers = with maintainers; [ flokli ]; </del> <ins> maintainers = with maintainers; [ flokli dylanmtaylor ]; </ins> hydraPlatforms = [ ]; }; }

Package name: oracle-instantclient Latest released version:21.9.0.0.0 <!-- Search your package here: --- Current version on the unstable channel:19.16.0.0.0 Current version on the stable/release channel:19.16.0.0.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! -- looks like it tried to upgrade v19 of instant client, but it is stale and not targeting v21. Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
It looks like you were the last one to touch instant client.
Package sources:


Question: - [touchegg](https://github.com/JoseExposito/touchegg), a multi-touch gesture recognizer. Available as [services.touchegg](#opt-services.touchegg.enable). <ins> - [pantheon-tweaks](https://github.com/pantheon-tweaks/pantheon-tweaks), an unofficial system settings panel for Pantheon. Available as [programs.pantheon-tweaks](#opt-programs.pantheon-tweaks.enable). </ins> ## Backward Incompatibilities {#sec-release-21.11-incompatibilities}

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:
As 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 .
Then 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.
Ah yes, the repo says "Pantheon Tweaks is currently only supported on elementary OS Odin" :+1:
Did 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.
Did 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 .
Tested 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.
I am not sure as this is not an official part of Pantheon.


Question: - [touchegg](https://github.com/JoseExposito/touchegg), a multi-touch gesture recognizer. Available as [services.touchegg](#opt-services.touchegg.enable). <ins> - [pantheon-tweaks](https://github.com/pantheon-tweaks/pantheon-tweaks), an unofficial system settings panel for Pantheon. Available as [programs.pantheon-tweaks](#opt-programs.pantheon-tweaks.enable). </ins> ## Backward Incompatibilities {#sec-release-21.11-incompatibilities}

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?
I 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
thanks 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"
ah 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!
i suggest then


Question: patchShebangs --build configure ''; <ins> # JDK's build system attempts to specifically detect # and special-case WSL, and we don't want it to do that, # so pass the correct platform names explicitly configurePlatforms = ["build" "host"]; </ins> configureFlags = [ "--with-boot-jdk=${openjdk-bootstrap.home}" "--with-version-pre="

They're trying to be smart: We should probably patch that check out, but maybe people with actual Java experience will have better ideas.
We 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.
The 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.
I would recommend to just patch that out.


Question: patchShebangs --build configure ''; <ins> # JDK's build system attempts to specifically detect # and special-case WSL, and we don't want it to do that, # so pass the correct platform names explicitly configurePlatforms = ["build" "host"]; </ins> configureFlags = [ "--with-boot-jdk=${openjdk-bootstrap.home}" "--with-version-pre="

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-'.


Question: patchShebangs --build configure ''; <ins> # JDK's build system attempts to specifically detect # and special-case WSL, and we don't want it to do that, # so pass the correct platform names explicitly configurePlatforms = ["build" "host"]; </ins> configureFlags = [ "--with-boot-jdk=${openjdk-bootstrap.home}" "--with-version-pre="

error: 1 dependencies of derivation '/nix/store/9mds0h6675lnh8hgam63xycvv8lrb01v-jetbrains-jdk-jcef-17.0.6-' failed to build
WSL2 on aarch64? Also, this error is for Chromium.
Sorry, 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.


Question: , config , stdenv , fetchFromGitHub <ins> , fetchurl </ins> , cmake , qt6 , fmt

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]:
Hi, I don't maintain GPT4All any longer, I switched to some other technologies (Open-WebUI).
haha, maybe i'll give that one a try then :) ty for all your hard work


Question: <del> { lib , stdenv , fetchFromGitHub , cmake }: stdenv.mkDerivation rec { pname = "iir1"; version = "1.9.4"; src = fetchFromGitHub { owner = "berndporr"; repo = "iir1"; rev = version; hash = "sha256-T8gl51IkZIGq+6D5ge4Kb3wm5aw7Rhphmnf6TTGwHbs="; }; nativeBuildInputs = [ cmake ]; meta = { description = "A DSP IIR realtime filter library written in C++"; downloadPage = "https://github.com/berndporr/iir1"; homepage = "http://berndporr.github.io/iir1/"; license = lib.licenses.mit; maintainers = [ lib.maintainers.AndersonTorres ]; platforms = lib.platforms.unix; }; } </del>

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


Question: , enableDC1394    ? false, libdc1394 , enableDocs      ? false, doxygen, graphviz-nox <del> , AVFoundation, Cocoa, VideoDecodeAcceleration, bzip2 </del> <ins> , AVFoundation, Cocoa, VideoDecodeAcceleration, CoreMedia, MediaToolbox, bzip2 </ins> }: assert blas.implementation == "openblas" && lapack.implementation == "openblas";

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:
It 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.
I 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.


Question: fetchFromGitHub, immich, python3, <ins> nixosTests, </ins> }: let python = python3.override {

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]:
After bisecting, first bad commit is (


Question: runHook postUnpack ''; <ins> # Prevent double wrapping dontWrapGApps = true; </ins> installPhase = '' runHook preInstall

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:
I think that this issue is not NixOS specific:
Still seems to be an issue. I'm using flakes so above is not applicable I'm on.
Tail end of strace.
Yep I can confirm that. However, as IvanMalison commented above, the bug might be not by nixos but by upstream.
I'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?


Question: assert lib.assertMsg (!hidpiXWayland) "The option `hidpiXWayland` has been removed. Please refer https://wiki.hyprland.org/Configuring/XWayland"; stdenv.mkDerivation (finalAttrs: { pname = "hyprland" + lib.optionalString debug "-debug"; <del> version = "0.35.0"; </del> <ins> version = "0.36.0"; </ins> src = fetchFromGitHub { owner = "hyprwm"; repo = finalAttrs.pname; rev = "v${finalAttrs.version}"; <del> hash = "sha256-dU5m6Cd4+WQZal2ICDVf1kww/dNzo1YUWRxWeCctEig="; </del> <ins> hash = "sha256-oZe4k6jtO/0govmERGcbeyvE9EfTvXY5bnyIs6AsL9U="; </ins> }; patches = [

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.


Question: <ins> { lib, buildPythonPackage, fetchPypi, pyscard, ecdsa, pyaes , pythonOlder }: buildPythonPackage rec { pname = "pysatochip"; version = "0.11.4"; disabled = pythonOlder "3.6"; src = fetchPypi { inherit pname version; sha256 = "sha256-Jj/zZIS9aXmZ2xdi29Eun7iRIrIk9oBlrtN9+6opIMo="; }; propagatedBuildInputs = [ pyscard ecdsa pyaes ]; pythonImportsCheck = [ "pysatochip" ]; meta = with lib; { description = "Simple python library to communicate with a Satochip hardware wallet"; homepage = "https://github.com/Toporin/pysatochip"; license = licenses.lgpl3Only; maintainers = with maintainers; [ oxalica ]; }; } </ins>

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:


Question: { mkDerivation , lib , fetchFromGitHub <ins> , substituteAll </ins> , qtbase , qtwebengine , qtdeclarative

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
Didn'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...)
I'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:
Oh I see what's the problem.. the file generates is pointing in to the unwrapped executable.. This needs to be patched locally in nixpkgs!
That would explain it. What do you mean by "patched locally"?
I mean this:
you are invited to test the fix for your issue in .
I'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.
I'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.
No, the plasmoid is what fails. The plasmoid seems to be launched in a different way, independent from the desktop file.


Question: { mkDerivation , lib , fetchFromGitHub <ins> , substituteAll </ins> , qtbase , qtwebengine , qtdeclarative

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.
According 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.
Note 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.
I 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
What is the status on this?


Question: { mkDerivation , lib , fetchFromGitHub <ins> , substituteAll </ins> , qtbase , qtwebengine , qtdeclarative

I'm still encountering this issue on my machine
I'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
Is 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.
I'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".
I don't experience this issue, here on Gnome, naturally. Other packages in Nixpkgs, like , and also put files in , according to .
Yes, 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.
As a note, I'm a pretty new NixOS user, but I switched yesterday to the unstable channel, and syncthingtray is working completely fine now.
Using .
Thanks 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.


Question: description = "Desktop application for Proton Pass"; homepage = "https://proton.me/pass"; license = lib.licenses.gpl3Plus; <del> maintainers = with lib.maintainers; [ massimogengarelli sebtm ]; </del> <ins> maintainers = with lib.maintainers; [ luftmensch-luftmensch massimogengarelli sebtm ]; </ins> platforms = [ "x86_64-linux" ]; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; mainProgram = "proton-pass";

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


Question: abootimg = callPackage ../development/mobile/abootimg { }; <del> adbfs-rootless = callPackage ../development/mobile/adbfs-rootless { adb = androidenv.androidPkgs_9_0.platform-tools; }; </del> <ins> adbfs-rootless = callPackage ../development/mobile/adbfs-rootless { }; </ins> adb-sync = callPackage ../development/mobile/adb-sync { inherit (androidenv.androidPkgs_9_0) platform-tools;

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.


Question: ]; nativeCheckInputs = with python3Packages; [ <del> pytestCheckHook nose </del> <ins> pynose </ins> ]; # Remove standard module argparse from requirements

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


Question: protocol = "tcp"; user = "root"; server = "${pkgs.tcp_wrappers}/sbin/tcpd"; <del> serverArgs = "${pkgs.heimdal}/sbin/kadmind"; </del> <ins> serverArgs = "${pkgs.heimdalFull}/sbin/kadmind"; </ins> }; systemd.services.kdc = {

I to and I return I got:
cc (I had to look through essentially old SVN history to find a reference -- this service is untouched for a long time).
I don't use this service anymore. BTW I've fixed its evaluation in the PR .
Let's not close this unless fix hits master.
can you please test the fix and see if there are any more problems with the service?


Question: yarg = callPackage ../development/python-modules/yarg { }; <ins> yark = callPackage ../development/python-modules/yark { }; </ins> yarl = callPackage ../development/python-modules/yarl { }; yaspin = callPackage ../development/python-modules/yaspin { };

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)


Question: <ins> diff --git a/setup.cfg b/setup.cfg new file mode 100644 index 0000000..6f81985 --- /dev/null +++ b/setup.cfg @@ -0,0 +1,2 @@ +[directories] +basedirlist = . </ins>

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:
Judging from the matplotlib expression we don't build against tcl/tk.
I 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.


Question: { lib , buildPythonPackage , fetchPypi <ins> , setuptools </ins> , pkgs , python <ins> , pythonOlder </ins> }: buildPythonPackage rec { pname = "bsddb3"; version = "6.2.9"; <del> format = "setuptools"; </del> <ins> pyproject = true; </ins> src = fetchPypi { inherit pname version; sha256 = "70d05ec8dc568f42e70fc919a442e0daadc2a905a1cfb7ca77f549d49d6e7801"; }; <ins> build-system = [ setuptools ]; </ins> buildInputs = [ pkgs.db ]; <ins> doCheck = pythonOlder "3.12"; # distutils usage </ins> checkPhase = '' ${python.interpreter} test.py '';

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]:
If bsddb imports distutils, then it is not compatible with Python 3.12. This is something for upstream to solve, but is unlikely to happen:
So all those packages that depend on this package, like must be labeled as broken?
Scrapy claims to support Python 3.12. Are you sure bsddb3 is still in their dependency chain?
Im not sure about that.
I 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...
distutils is used in the test of bsddb3 to get the platform data, we patched this behavior in the following PR
Isn't It better to patch the test to avoid using distutils but still having it run ?


Question: audiowaveform = callPackage ../tools/audio/audiowaveform { }; <del> authenticator = callPackage ../applications/misc/authenticator { }; </del> <ins> authenticator = callPackage ../applications/misc/authenticator rec { # Remove when GTK is upgraded past 4.8 # https://github.com/NixOS/nixpkgs/issues/216770 gtk4 = pkgs.gtk4.overrideAttrs (_: rec { version = "4.9.4"; src = fetchurl { url = "mirror://gnome/sources/gtk/${lib.versions.majorMinor version}/gtk-${version}.tar.xz"; sha256 = "sha256-kaOv1YQB1OXYHjCwjuPxE6R2j/EBQDNqcqMmx3JyvjA="; }; }); wrapGAppsHook4 = wrapGAppsHook.override { gtk3 = gtk4; }; }; </ins> autoflake = with python3.pkgs; toPythonApplication autoflake;

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.
Same issue with  (
I 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.
Ah, I see. There is a related PR for Amberol:
What commit did you build from? I’d like to bisect
My 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.
if you’re updating the version to point to an unreleased version the should
Indeed, 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_
Hi 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.
Is 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.
In 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?
We’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.
(how naive of me.


Question: audiowaveform = callPackage ../tools/audio/audiowaveform { }; <del> authenticator = callPackage ../applications/misc/authenticator { }; </del> <ins> authenticator = callPackage ../applications/misc/authenticator rec { # Remove when GTK is upgraded past 4.8 # https://github.com/NixOS/nixpkgs/issues/216770 gtk4 = pkgs.gtk4.overrideAttrs (_: rec { version = "4.9.4"; src = fetchurl { url = "mirror://gnome/sources/gtk/${lib.versions.majorMinor version}/gtk-${version}.tar.xz"; sha256 = "sha256-kaOv1YQB1OXYHjCwjuPxE6R2j/EBQDNqcqMmx3JyvjA="; }; }); wrapGAppsHook4 = wrapGAppsHook.override { gtk3 = gtk4; }; }; </ins> autoflake = with python3.pkgs; toPythonApplication autoflake;

maybe just building from is better)
Opened 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.
You were right - thanks for the hint! - I was indeed still building fractal-next from before the fix :disappointed:


Question: optionalString config.security.pam.enableEcryptfs '' auth optional ${pkgs.ecryptfs}/lib/security/pam_ecryptfs.so unwrap '' + <ins> optionalString config.security.pam.enableFscrypt '' auth optional ${pkgs.fscrypt-experimental}/lib/security/pam_fscrypt.so '' + </ins> optionalString cfg.pamMount '' auth optional ${pkgs.pam_mount}/lib/security/pam_mount.so disable_interactive '' +

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.
This is just to say hi and to share that I too am interested in this feature
I marked this as stale due to inactivity. →


Question: networking.nat.enable = true; networking.nat.internalInterfaces = [ "eth2" ]; networking.nat.externalInterface = "eth1"; <ins> networking.nftables.enable = useNftables; </ins> networking.firewall.enable = true; networking.firewall.trustedInterfaces = [ "eth2" ]; networking.interfaces.eth1.ipv4.addresses = [

We already have in , but only with iptables support. It would be nice to have the nftables version available as well.
Being worked on in , I'm trying to test myself but couldn't make it to work yet.
I think the PR is ready now, testing welcome!
Maybe add an option for will be better?


Question: inherit sha256; }; <del> patches = [ ./0001-Setup-remove-custom-dbuser-creation-behavior.patch ]; </del> <ins> patches = [ (./patches + "/v${major}/0001-Setup-remove-custom-dbuser-creation-behavior.patch") ]; </ins> passthru.tests = nixosTests.nextcloud;

<!-- 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.


Question: buildPythonPackage rec { pname = "dvc-data"; <del> version = "3.15.2"; </del> <ins> version = "3.16.0"; </ins> pyproject = true; disabled = pythonOlder "3.8";

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]:
This happens not for the first time and probably not for the last time :cry:


Question: , qtmultimedia , qtx11extras , soxr <ins> , vgmstream </ins> , wavpack }:

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]:
Instead of adding , did you try to add instead? is without as input, and it is used to break the loop.
Thank you for the quick response! That would be elegant, but I don't see any result in my grep of nixpkgs or in the .
Sorry, 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.
Oh 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:
I , 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 :)
Shall I send a PR for a final review?


Question: <del> { lib , buildGoModule , fetchFromGitHub , stdenv , Cocoa , fetchpatch }: buildGoModule rec { pname = "butler"; version = "15.21.0"; src = fetchFromGitHub { owner = "itchio"; repo = pname; rev = "v${version}"; sha256 = "sha256-vciSmXR3wI3KcnC+Uz36AgI/WUfztA05MJv1InuOjJM="; }; buildInputs = lib.optionals stdenv.isDarwin [ Cocoa ]; patches = [ # update x/sys dependency for darwin build https://github.com/itchio/butler/pull/245 (fetchpatch { url = "https://github.com/itchio/butler/pull/245/commits/ef651d373e3061fda9692dd44ae0f7ce215e9655.patch"; hash = "sha256-rZZn/OGiv3mRyy89uORyJ99zWN21kZCCQAlFvSKxlPU="; }) ]; proxyVendor = true; vendorHash = "sha256-GvUUCQ2BPW0HlXZljBWJ2Wyys9OEIM55dEWAa6J19Zg="; doCheck = false; meta = with lib; { # butler cannot be build with Go >=1.21 # See https://github.com/itchio/butler/issues/256 # and https://github.com/itchio/dmcunrar-go/issues/1 # The dependency causing the issue is marked as 'no maintainence intended'. # Last butler release is from 05/2021. broken = true; description = "Command-line itch.io helper"; homepage = "https://github.com/itchio/butler"; license = licenses.mit; maintainers = with maintainers; [ martfont ]; }; } </del>

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]:
The latest version on seems to be 26.1.3 which is used in the package.
There is 26.1.5 as a source code , but current package uses binaryBytecode