Question: <del> { lib, buildGoPackage, fetchurl, fetchFromGitHub, go-bindata }: </del> <ins> { lib, buildGoModule, fetchurl, fetchFromGitHub }: </ins> let <del> version = "1.6.4"; </del> <ins> version = "1.8.0"; </ins> # TODO: must build the extension instead of downloading it. But since it's # literally an asset that is indifferent regardless of the platform, this # might be just enough. webext = fetchurl { <del> url = "https://github.com/browsh-org/browsh/releases/download/v${version}/browsh-${version}-an.fx.xpi"; sha256 = "1shf1s9s525wns5vrsc4ns21zjxm1si43lx6v0q8ma6vd5x5445l"; </del> <ins> url = "https://github.com/browsh-org/browsh/releases/download/v${version}/browsh-${version}.xpi"; sha256 = "sha256-12xWbf4ngYHWLKV9yyxyi0Ny/zHSj2o7Icats+Ef+pA="; </ins> }; <del> in buildGoPackage rec { </del> <ins> in buildGoModule rec { </ins> inherit version; pname = "browsh"; <del> goPackagePath = "browsh"; </del> <ins> sourceRoot = "source/interfacer"; </ins> <del> # further go package dependencies are defined in deps.nix, see line below. </del> src = fetchFromGitHub { owner = "browsh-org"; repo = "browsh"; rev = "v${version}"; <del> sha256 = "0gvf5k1gm81xxg7ha309kgfkgl5357dli0fbc4z01rmfgbl0rfa0"; </del> <ins> sha256 = "sha256-/tH1w6qi+rimsqtk8Y8AYljU3X4vbmoDtV07piWSBdw="; </ins> }; <del> nativeBuildInputs = [ go-bindata ]; </del> <ins> vendorSha256 = "sha256-eCvV3UuM/JtCgMqvwvqWF3bpOmPSos5Pfhu6ETaS58c="; </ins> <del> # embed the web extension in a go file and place it where it's supposed to # be. See # https://github.com/browsh-org/browsh/blob/v1.5.0/interfacer/contrib/xpi2bin.sh </del> preBuild = '' <del> xpiprefix="$(mktemp -d)" cp "${webext}" "$xpiprefix/browsh.xpi" go-bindata  -prefix "$xpiprefix"  -pkg browsh  -o "$NIX_BUILD_TOP/go/src/${goPackagePath}/interfacer/src/browsh/webextension.go"  "$xpiprefix/browsh.xpi" sed  -e 's:Asset("/browsh.xpi"):Asset("browsh.xpi"):g'  -i "$NIX_BUILD_TOP/go/src/${goPackagePath}/interfacer/src/browsh/firefox.go" ''; postBuild = '' mv "$NIX_BUILD_TOP/go/bin/src" "$NIX_BUILD_TOP/go/bin/browsh" </del> <ins> cp "${webext}" src/browsh/browsh.xpi </ins> ''; <del> goDeps = ./deps.nix; </del> <ins> # Tests require network access doCheck = false; </ins> meta = with lib; { description = "A fully-modern text-based browser, rendering to TTY and browsers"; homepage = "https://www.brow.sh/"; <del> maintainers = [ maintainers.kalbasit ]; </del> <ins> maintainers = with maintainers; [ kalbasit siraben ]; </ins> license = lib.licenses.lgpl21; platforms = lib.platforms.linux ++ lib.platforms.darwin; };

First release in three years. <!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: <!-- The current version can be found easily with the same process as above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 1.6.4 desired version: 1.8.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
cc who might be able to help with building the extension from source


Question: (fetchNuGet { pname = "Nito.AsyncEx.Tasks"; version = "5.1.2"; sha256 = "11wp47kc69sjdxrbg5pgx0wlffqlp0x5kr54ggnz2v19kmjz362v"; }) (fetchNuGet { pname = "Nito.Collections.Deque"; version = "1.1.1"; sha256 = "152564q3s0n5swfv5p5rx0ghn2sm0g2xsnbd7gv8vb9yfklv7yg8"; }) (fetchNuGet { pname = "Nito.Disposables"; version = "2.2.1"; sha256 = "1hx5k8497j34kxxgh060bvij0vfnraw90dmm3h9bmamcdi8wp80l"; }) <del> (fetchNuGet { pname = "NLog"; version = "5.2.7"; sha256 = "1gq5l9qv3vnl0rvxa110bbqsq6m43h8h912xijqab1hsjdpb46q3"; }) (fetchNuGet { pname = "NLog.Extensions.Logging"; version = "5.3.7"; sha256 = "1hv2v4hqqq86vjvxa0cbk4klaii8n8h1wjrlsfzbp9nnxnzg9pzi"; }) (fetchNuGet { pname = "NLog.Web.AspNetCore"; version = "5.3.7"; sha256 = "1jifwnvkfi3jankan7543q985gzrywddvajlqrf573aa2dbp5n1f"; }) </del> <ins> (fetchNuGet { pname = "NLog"; version = "5.2.8"; sha256 = "1z3h20m5rjnizm1jbf5j0vpdc1f373rzzkg6478p1lxv5j385c12"; }) (fetchNuGet { pname = "NLog.Extensions.Logging"; version = "5.3.8"; sha256 = "1qnz91099f51vk7f5g2ig0041maw5hcbyqllxvj5zj7zkp0qw9b8"; }) (fetchNuGet { pname = "NLog.Web.AspNetCore"; version = "5.3.8"; sha256 = "05a6bzvdf63lbnn6sj3yfggxcgv96j91kdbcw0ac5hxl58df58r6"; }) (fetchNuGet { pname = "NuGet.Frameworks"; version = "5.11.0"; sha256 = "0wv26gq39hfqw9md32amr5771s73f5zn1z9vs4y77cgynxr73s4z"; }) </ins> (fetchNuGet { pname = "NuGet.Frameworks"; version = "6.5.0"; sha256 = "0s37d1p4md0k6d4cy6sq36f2dgkd9qfbzapxhkvi8awwh0vrynhj"; }) (fetchNuGet { pname = "protobuf-net"; version = "3.2.26"; sha256 = "1mcg46xnhgqwjacy6j8kvp3rylpi26wjnmhwv8mh5cwjya9nynqb"; }) (fetchNuGet { pname = "protobuf-net.Core"; version = "3.2.26"; sha256 = "1wrr38ygdanf121bkl8b1d4kz1pawm064z69bqf3qbr46h4j575w"; })

Package name: ArchiSteamFarm Latest released version: 5.5.2.3 <!-- Search your package here: --- Current version on the unstable channel: 5.5.0.11 Current version on the stable/release channel: 5.4.12.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It helps if I also open the PR when doing the update


Question: meta.maintainers = with maintainers; [ etu stunkymonkey mattchrist ]; options.services.freshrss = { <del> enable = mkEnableOption "FreshRSS feed reader"; </del> <ins> enable = mkEnableOption "FreshRSS RSS aggregator and reader with php-fpm backend."; </ins> package = mkPackageOption pkgs "freshrss" { };

When enabling freshrss and rebuilding, no freshrss systemd service is started. Steps to reproduce the behavior: (as well other requirements for minimal config) (with , for me) The only freshrss units are and . to in browser. Unable to connect. A service with (or something?) is created and runs automatically. The http server is accessible from a browser. I initially tried running in a container, but running on the host OS had the same result Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Freshrss doesn't run as a systemd service. It runs under php-fpm. The associated systemd service is . This is then exposed via nginx. I believe the default nginx configuration will expose freshrss on port 80, so http://localhost may work for your current configuration. The used by nginx for freshrss is . My guess is you'll need to configure it. If you want to access freshrss via "http://localhost:8080" you could use a config like:
Sorry I never responded to this! This worked, thank you.
i guess we can close this then? please report back if i am wrong.
I do agree with qyriad that this could be explicitly documented better, but I don't have any further issue to specifically track
any specific location where you want this documented? where would you look something like this up?
I would probably put in the description of the option.


Question: }; }; <ins> patches = [ (substituteAll { src = ./fix_gmenu.patch; gmenu_path = "${gnome3.gnome-menus}/lib/girepository-1.0"; }) ]; </ins> doCheck = true; nativeBuildInputs = [ meson ninja pkgconfig gettext glib ];

The meson build doesn't compile the schemas, opting to do it instead in a package shell script. Unfortunately it seems that compiling the schemas aren't enough to make all the extensions work. In particular at least and still won't work (seems to fix though). With the schemas installed Tweaks simply complains that the extension is incorrectly installed. complains about lacking any typelib file for . I'm not sure how well these extensions worked before 3.28, but a report on irc indicated that at least worked before. cc Run Tweaks on nixos-unstable, try to enable eg. the extension under or . Running a schema fix on top of system: host os: multi-user?: sandbox: version: channels(hed): channels(root): nixpkgs:
The extension works for me when I manually change the directory structure to: As for the , I removed from dependencies so that might explain this failure. The extension should probably be fixed like .
You're able to switch switch themes in in Tweaks? Might be something wrong on my end. I'll submit a PR fixing the schemas at least.
Testing out a fix for .
Hmm, I can enable it but the theme switching does not work. I seems to require the extension schemas in when running Tweaks. Maybe it got picked up from global for bash users, but the option was always disabled for me with fish.
We might want to add as a dependency to Tweaks so that it could work for non-bash users. Then we will need to fix the schemas: the schemas in and find a hack similar to to add the schemas path to the extension. like the following to put the schemas where extensions can find them and add symlink for Tweaks. same thing as the second point but accomplished by patching files.
Your suggested fix worked for at least :) I went with basically adding the code from to to fix the schema problem. Generating the directory structure you quoted above seems the most sane and keeping with upstream. Tested things out in a vm with bash, and didn't seem to work there either. So not sure if the problem is non bash. Anyway, adding to fixes , so I think that's appropriate. I should've got everything now, will submit a PR :)
I think it only works in bash and globally installed packages or something.


Question: }; }; <ins> patches = [ (substituteAll { src = ./fix_gmenu.patch; gmenu_path = "${gnome3.gnome-menus}/lib/girepository-1.0"; }) ]; </ins> doCheck = true; nativeBuildInputs = [ meson ninja pkgconfig gettext glib ];

I would not rely on it since I consider it an ugly impurity. I would prefer the first solution since it will be the cleanest and could be possibly automated in the future, but number two is fine too.


Question: , javaPackages }: <del> javaPackages.mavenfod rec { </del> <ins> (javaPackages.mavenfod.override { inherit maven; # use overridden maven version (see dbeaver's entry in all-packages.nix) }) rec { </ins> pname = "dbeaver"; <del> version = "22.0.1"; # When updating also update fetchedMavenDeps.sha256 </del> <ins> version = "22.0.1"; # When updating also update mvnSha256 </ins> src = fetchFromGitHub { owner = "dbeaver";

The dbeaver package does not build on . Steps to reproduce the behavior: Dbeaver should build <details<summaryTruncated build log</summary<br</details


Question: autoSuspend = mkOption { default = true; description = '' <del> Suspend the machine after inactivity. </del> <ins> On the GNOME Display Manager login screen, suspend the machine after inactivity. (Does not affect automatic suspend while logged in, or at lock screen.) </ins> ''; type = types.bool; };

Describe the bug It seems you can't disable GDM's auto suspend behaviour. Disable has no effect. To Reproduce laptop will auto suspend after timeout Expected behavior Suppress auto suspend. Additional context Follow up from Notify maintainers Metadata
I'm on Wayland if that matters.
I believe it only touches the dconf profile in gdm, and sets these settings You probably still have those set in your actual session. See the OP of for more details.
Though I could be misremembering things
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Not sure if it will work yet, but I ran these commands to make my settings match the autosuspend = false settings:
After making these changes, it still suspended. Then I killed , and since it has restarted it has not auto suspended. I'm not sure if this is the simplest thing, but what worked for me was: set , rebuild NixOS Kill so it restarts
returns nothing for me on unstable. I have set to false and it still suspends. (I not 100% sure this is caused by gdm).
Well, it started auto-suspending for me again, even with the above settings.
I'm trying this now:
Seems to be working!
In my case it was xorg, not gdm at all. I disabled screensaver and autosuspend with:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Wow, it's 2023, and this still appears to be the solution To clarify I actually did the suggestion in here, which has an additional line
I vote to reopen this. The fix is easy to configure, but difficult to understand.
It seems like "don't suspend my system, i'm running this as a server" should just be a single config option


Question: npmDepsHash = "sha256-157hm7h5FWuOuxoo6WTtlMPq5LcRZIsSt5NDg0pvim8="; npmFlags = [ "--legacy-peer-deps" ]; <del> nativeBuildInputs = [ (writeShellScriptBin "phantomjs" "echo 2.1.1") pkg-config ] ++ lib.optionals (! stdenv.isDarwin) [ makeWrapper copyDesktopItems ]; buildInputs = [ pixman cairo pango ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk_11_0.frameworks.CoreText giflib ]; </del> <ins> nativeBuildInputs = [ (writeShellScriptBin "phantomjs" "echo 2.1.1") pkg-config ] ++ lib.optionals (!stdenv.isDarwin) [ makeWrapper copyDesktopItems ]; buildInputs = [ pixman cairo pango ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk_11_0.frameworks.CoreText ]; </ins> desktopItems = [ (makeDesktopItem {

Attempt to build on Sample This is on an M2 chip, and it seems the issue is with node-canvas not being able to install due to missing giflib. Building with: Fixes this. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <ins> { buildPythonPackage , fetchFromGitHub , lib , writeShellScriptBin , cmake , doxygen , draco , graphviz-nox , ninja , setuptools , pyqt6 , pyopengl , jinja2 , pyside6 , boost , numpy , git , tbb , opensubdiv , openimageio , opencolorio , osl , ptex , embree , alembic , openexr , flex , bison , qt6 , python }: let # Matches the pyside6-uic implementation # https://code.qt.io/cgit/pyside/pyside-setup.git/tree/sources/pyside-tools/pyside_tool.py?id=e501cad66146a49c7a259579c7bb94bc93a67a08#n82 pyside-tools-uic = writeShellScriptBin "pyside6-uic" '' exec ${qt6.qtbase}/libexec/uic -g python "$@" ''; in buildPythonPackage rec { pname = "OpenUSD"; version = "23.11"; src = fetchFromGitHub { owner = "PixarAnimationStudios"; repo = pname; rev = "refs/tags/v${version}"; hash = "sha256-5zQrfB14kXs75WbL3s4eyhxELglhLNxU2L2aVXiyVjg="; }; outputs = ["out" "doc"]; format = "other"; propagatedBuildInputs = [ setuptools pyqt6 pyopengl jinja2 pyside6 pyside-tools-uic boost numpy ]; cmakeFlags = [ "-DPXR_BUILD_EXAMPLES=OFF" "-DPXR_BUILD_TUTORIALS=OFF" "-DPXR_BUILD_USD_TOOLS=ON" "-DPXR_BUILD_IMAGING=ON" "-DPXR_BUILD_USD_IMAGING=ON" "-DPXR_BUILD_USDVIEW=ON" "-DPXR_BUILD_DOCUMENTATION=ON" "-DPXR_BUILD_PYTHON_DOCUMENTATION=ON" "-DPXR_BUILD_EMBREE_PLUGIN=ON" "-DPXR_BUILD_ALEMBIC_PLUGIN=ON" "-DPXR_ENABLE_OSL_SUPPORT=ON" "-DPXR_BUILD_DRACO_PLUGIN=ON" "-DPXR_BUILD_MONOLITHIC=ON" # Seems to be commonly linked to monolithically ]; nativeBuildInputs = [ cmake ninja git qt6.wrapQtAppsHook doxygen graphviz-nox ]; buildInputs = [ tbb opensubdiv openimageio opencolorio osl ptex embree alembic.dev openexr flex bison boost draco qt6.qtbase qt6.qtwayland ]; pythonImportsCheck = [ "pxr" "pxr.Usd" ]; postInstall = '' # Make python lib properly accessible target_dir=$out/${python.sitePackages} mkdir -p $(dirname $target_dir) mv $out/lib/python $target_dir mv $out/docs $doc rm $out/share -r # only examples rm $out/tests -r ''; meta = { description = "Universal Scene Description"; longDescription = '' Universal Scene Description (USD) is an efficient, scalable system for authoring, reading, and streaming time-sampled scene description for interchange between graphics applications. ''; homepage = "https://openusd.org/"; license = lib.licenses.asl20; maintainers = with lib.maintainers; [ shaddydc ]; }; } </ins>

Project description Universal Scene Description (USD) is an efficient, scalable system for authoring, reading, and streaming time-sampled scene description for interchange between graphics applications. OpenUSD is AFAIK the library to work with the USD format. Metadata homepage URL: source URL: license: Modified Apache 2.0 License platforms: unix, linux, darwin
I've got a working derivation, but I'm not sure if this is already in a state that is good enough for a PR. In particular, packaging the pyside tools properly didn't seem straightforward to me. AFAICT, it just copies some binaries from other QT parts and wraps them with extra arguments, so that's what I'm doing here. While the python package seems to be working properly, I ran into an issue before when trying to include the headers into a C++ project, and I believe it failed to find some python headers? Maybe that needs some extra buildInput? I haven't investigated more. Locally, I've just been using a version compiled with for that. The binaries, such as , are working by my testing, besides requiring on wayland. I'd be happy to make a PR for this if this is a good-enough state.


Question: stdenv.mkDerivation (finalAttrs: { pname = "quickemu"; <del> version = "4.9.4"; </del> <ins> version = "4.9.4-unstable-2024-05-28"; </ins> src = fetchFromGitHub { owner = "quickemu-project"; repo = "quickemu"; <del> rev = finalAttrs.version; hash = "sha256-fjbXgze6klvbRgkJtPIUh9kEkP/As7dAj+cazpzelBY="; </del> <ins> rev = "d78255b097b599e8ab3713cb61c4085cc45f5a95"; # TODO: return to version on next release hash = "sha256-fF306CdGqKM+779OLm0NNyqPBtm7TuU7UN/NanT12y8="; </ins> }; postPatch = ''

There is a bug in the latest release of quickemu (present in nixpkgs), that sends invalid flags to qemu and thus doesn't work for MacOS (maybe others too). The fix I was planning to PR was to simply move the src to point to the most current revision. I wasn't 100% sure if that was something that I should do however, given it would set the precedent that we follow revisions for this package instead of the version tag, which may add maintenance burden. Just wanted opinions before I made a PR, would it be acceptable to bump the revision temporarily to avoid this issue? It's niche but its real and could affect users of this package. Steps to reproduce the behavior: Pops open a Qemu window with the appropriate screens. Fails with a strange "macos-ventura/macos- file not found", but it is related to the bugged release. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Don't know of any official policy on this. My opinion: If it's a single commit that fixes the issue, you can add a patch. If it's spread out over multiple commits, use current unstable, but that may introduce other unknown regressions and breaking changes. And in any case we'd go back to the release tag on the next release.
Patching sounds like a good idea, hopefully it is just one commit. Though honestly from personal testing the newest release worked perfectly fine (I tested via an override).


Question: User = "unifi"; UMask = "0077"; WorkingDirectory = "${stateDir}"; <ins> # Hardening AmbientCapabilities = ""; CapabilityBoundingSet = ""; # ProtectClock= adds DeviceAllow=char-rtc r DeviceAllow = ""; DevicePolicy = "closed"; LockPersonality = true; NoNewPrivileges = true; PrivateDevices = true; PrivateMounts = true; PrivateTmp = true; PrivateUsers = true; ProtectClock = true; ProtectControlGroups = true; ProtectHome = true; ProtectHostname = true; ProtectKernelLogs = true; ProtectKernelModules = true; ProtectKernelTunables = true; ProtectSystem = "strict"; RemoveIPC = true; RestrictNamespaces = true; RestrictRealtime = true; RestrictSUIDSGID = true; SystemCallErrorNumber = "EPERM"; SystemCallFilter = [ "@system-service" ]; # Required for ProtectSystem=strict BindPaths = [ stateDir ]; # Needs network access PrivateNetwork = false; # Cannot be true due to OpenJDK MemoryDenyWriteExecute = false; </ins> }; };

Describe the bug The unifi controller has dropped a present in my : Seeing as Unifi support has asked me about "temp", the "device tab", and my network topology, I'm not holding out on getting a good answer as to what it's doing. Short of that, I'd like to prevent it from having any access anywhere except a single temp, non-executable location managed by systemd.
I marked this as stale due to inactivity. →


Question: meta = with stdenv.lib; { homepage = "https://01.org/linuxmedia"; license = licenses.mit; <del> description = "Intel driver for the VAAPI library"; platforms = platforms.unix; maintainers = with maintainers; [ ]; </del> <ins> description = "VA-API user mode driver for Intel GEN Graphics family"; longDescription = '' This VA-API video driver backend provides a bridge to the GEN GPUs through the packaging of buffers and commands to be sent to the i915 driver for exercising both hardware and shader functionality for video decode, encode, and processing. VA-API is an open-source library and API specification, which provides access to graphics hardware acceleration capabilities for video processing. It consists of a main library and driver-specific acceleration backends for each supported hardware vendor. ''; platforms = [ "x86_64-linux" "i686-linux" ]; maintainers = with maintainers; [ primeos ]; </ins> }; }

Describe the bug Upstream intel-vaapi-driver removed the --enable-drm ./configure option. It is now turned on by default. Happened in commit To Reproduce Steps to reproduce the behavior: the package and read through compile log Additional context This is a warning, package builds just fine despite this. Metadata Please run and paste the result. Maintainer information: (I don't know if I am dealing with attribute or module. I think attribute, but just to cover all bases.)
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .


Question: pydf = callPackage ../applications/misc/pydf { }; <del> pygmentex = callPackage ../tools/typesetting/pygmentex { }; </del> pympress = callPackage ../applications/office/pympress { }; pythonIRClib = pythonPackages.pythonIRClib;

I have installed the TeXLive package on my system, but its binary script fails to run because: its directory is not found in it does not have an explicitly dependency on it does not have an explicitly dependency on the module for Python 2 cannot be found. Please fix this issues so that the script can be run. (Maybe can take a look at this.)
cc
Well, the first two bullets would be fixed very simply by but I don't yet have framework to add external python dependencies to the scripts.
Nothing new here? A similar problem happens with :
cc Maybe while a good solution is not engineered, a package for without the TeX stuff can be to . It would contain the binary with support for the needed Python dependencies. What do you think?
There aren't any true binaries, are there? It's just python scripts IIRC. But still, what you propose is probably the easiest way to resolve this somehow.
It is just a Python script that depends on the module.
My attempt at it:
So pygmentex works as expected now?
It works! It can be tested by downloading the example document from the distribution on , unzipping the downloaded files, removing the Python script and the LaTeX style class, and than compiling : The result is , with many examples of code listings typeset by Pygments.
OK, then I think we can close this.
Sorry for necromancing this (should I have opened a new issue instead?), but it doesn't "just work" – or needs further documentation on how to use it: The created by building the pygmentex texlive package can not find the module. gives us such an environment, just try running the command from there -The package though provides a executable which works just fine and finds the needed pygments python module. So how to combine these both packages? In particular I ran into this when trying to use the texlive package, as that seems to directly invoke the executable during build. Issue appears on release-18.09
I encountered the same issue, the latex package seems to be working fine tough (and can be used as a replacement)
I have in both with (which provides the style file and a non-functional Python script, because of missing Python dependencies) and (which provides the script). This setup works for me.
I still do not know a way of allowing Python module dependencies for Python scripts installed through .
This is to be fixed in


Question: When this command successfully finishes, it will tell you where the manual got generated. The HTML will be accessible through the `result` symlink at `./result/share/doc/nixos/index.html`. <del> ## Editing DocBook XML {#sec-writing-docs-editing-docbook-xml} For general information on how to write in DocBook, see [DocBook 5: The Definitive Guide](https://tdg.docbook.org/tdg/5.1/). Emacs nXML Mode is very helpful for editing DocBook XML because it validates the document as you write, and precisely locates errors. To use it, see [](#sec-emacs-docbook-xml). [Pandoc](https://pandoc.org/) can generate DocBook XML from a multitude of formats, which makes a good starting point. Here is an example of Pandoc invocation to convert GitHub-Flavoured MarkDown to DocBook 5 XML: ```ShellSession pandoc -f markdown_github -t docbook5 docs.md -o my-section.md ``` Pandoc can also quickly convert a single `section.xml` to HTML, which is helpful when drafting. Sometimes writing valid DocBook is too difficult. In this case, submit your documentation updates in a [GitHub Issue](https://github.com/NixOS/nixpkgs/issues/new) and someone will handle the conversion to XML for you. ## Creating a Topic {#sec-writing-docs-creating-a-topic} You can use an existing topic as a basis for the new topic or create a topic from scratch. Keep the following guidelines in mind when you create and add a topic: -   The NixOS [`book`](https://tdg.docbook.org/tdg/5.0/book.html) element is in `nixos/doc/manual/manual.xml`. It includes several [`parts`](https://tdg.docbook.org/tdg/5.0/book.html) which are in subdirectories. -   Store the topic file in the same directory as the `part` to which it belongs. If your topic is about configuring a NixOS module, then the XML file can be stored alongside the module definition `nix` file. -   If you include multiple words in the file name, separate the words with a dash. For example: `ipv6-config.xml`. -   Make sure that the `xml:id` value is unique. You can use abbreviations if the ID is too long. For example: `nixos-config`. -   Determine whether your topic is a chapter or a section. If you are unsure, open an existing topic file and check whether the main element is chapter or section. ## Adding a Topic to the Book {#sec-writing-docs-adding-a-topic} Open the parent CommonMark file and add a line to the list of chapters with the file name of the topic that you created. If you created a `section`, you add the file to the `chapter` file. If you created a `chapter`, you add the file to the `part` file. If the topic is about configuring a NixOS module, it can be automatically included in the manual by using the `meta.doc` attribute. See [](#sec-meta-attributes) for an explanation. </del>

Contributors working on improving the nixpkgs manual would be redirected to the . This section is not up-to-date with all the syntax features supported by , forcing contributors to look for use examples over the whole manual. The same markdown syntax is used to write and generate the NixOS manual. However, this manual does not make any mention of the supported syntax. This makes it hard to contribute to the NixOS manual with relative isolation from the nixpkgs manual. Update in Nixpkgs manual to include reference material and examples on all the syntax features supported by . Link in Nixos manual for completion. [x] remove references to in the . : [x] remove references to in the . [x] add a redirecting to the syntax section in . [x] add reference to lack of support for [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support [x] add reference to support () () )


Question: <del> { lib, buildPythonPackage, fetchPypi , billiard, click, click-didyoumean, click-plugins, click-repl, kombu, pytz, vine , boto3, case, moto, pytest, pytest-celery, pytest-subtests, pytest-timeout </del> <ins> { lib , billiard , boto3 , buildPythonPackage , case , click , click-didyoumean , click-plugins , click-repl , fetchPypi , kombu , moto , pymongo , pytest-celery , pytest-subtests , pytest-timeout , pytestCheckHook , pythonOlder , pytz , vine </ins> }: buildPythonPackage rec { pname = "celery"; version = "5.2.1"; <ins> format = "setuptools"; disabled = pythonOlder "3.7"; </ins> src = fetchPypi { inherit pname version; sha256 = "sha256-tBpZC0nK+OZJilfbYo5YDV+Nxv69oPQt5deDrtW3+Ag="; }; <del> propagatedBuildInputs = [ billiard click click-didyoumean click-plugins click-repl kombu pytz vine ]; </del> <ins> propagatedBuildInputs = [ billiard click click-didyoumean click-plugins click-repl kombu pytz vine ]; checkInputs = [ boto3 case moto pymongo pytest-celery pytest-subtests pytest-timeout pytestCheckHook ]; disabledTestPaths = [ # test_eventlet touches network "t/unit/concurrency/test_eventlet.py" # test_multi tries to create directories under /var "t/unit/bin/test_multi.py" "t/unit/apps/test_multi.py" ]; </ins> <del> checkInputs = [ boto3 case moto pytest pytest-celery pytest-subtests pytest-timeout ]; </del> <ins> disabledTests = [ "msgpack" "test_check_privileges_no_fchown" ]; </ins> <del> # ignore test that's incompatible with pytest5 # test_eventlet touches network # test_mongodb requires pymongo # test_multi tries to create directories under /var checkPhase = '' pytest -k 'not restore_current_app_fallback and not msgpack and not on_apply and not pytest'  --ignore=t/unit/contrib/test_pytest.py  --ignore=t/unit/concurrency/test_eventlet.py  --ignore=t/unit/bin/test_multi.py  --ignore=t/unit/apps/test_multi.py  --ignore=t/unit/backends/test_mongodb.py ''; </del> <ins> pythonImportsCheck = [ "celery" ]; </ins> meta = with lib; { <del> homepage = "https://github.com/celery/celery/"; </del> description = "Distributed task queue"; <ins> homepage = "https://github.com/celery/celery/"; </ins> license = licenses.bsd3; <del> maintainers = [ ]; </del> <ins> maintainers = with maintainers; [ ]; </ins> }; }

Octoprint can't build on unstable due to a conflict of the required version for . octoprint , while the dependency requires (due to ) . Octoprint builds successfully I ran a between and (known good) , the first bad commit was I suspect that it's necessary to pin the additional dependencies (and maybe some more), too, but I'm not that experienced with packaging python packages. made the first bad commit Octoprint maintainers: system: host os: multi-user?: sandbox: version: channels(root): channels(richard): nixpkgs: Maintainer information:


Question: <ins> diff --git a/hotspot/src/os/linux/vm/os_linux.cpp b/hotspot/src/os/linux/vm/os_linux.cpp index c477851c1b..ff5e28d95b 100644 --- a/hotspot/src/os/linux/vm/os_linux.cpp +++ b/hotspot/src/os/linux/vm/os_linux.cpp @@ -368,13 +368,13 @@ void os::init_system_properties_values() { //        ... //        7: The default directories, normally /lib and /usr/lib. #if defined(AMD64) || defined(_LP64) && (defined(SPARC) || defined(PPC) || defined(S390)) -#define DEFAULT_LIBPATH "/usr/lib64:/lib64:/lib:/usr/lib" +#define DEFAULT_LIBPATH "" #else -#define DEFAULT_LIBPATH "/lib:/usr/lib" +#define DEFAULT_LIBPATH "" #endif // Base path of extensions installed on the system. -#define SYS_EXT_DIR     "/usr/java/packages" +#define SYS_EXT_DIR     "" #define EXTENSIONS_DIR  "/lib/ext" #define ENDORSED_DIR    "/lib/endorsed" @@ -437,13 +437,13 @@ void os::init_system_properties_values() { strlen(v) + 1 + sizeof(SYS_EXT_DIR) + sizeof("/lib/") + strlen(cpu_arch) + sizeof(DEFAULT_LIBPATH) + 1, mtInternal); -    sprintf(ld_library_path, "%s%s" SYS_EXT_DIR "/lib/%s:" DEFAULT_LIBPATH, v, v_colon, cpu_arch); +    sprintf(ld_library_path, "%s%s", v); Arguments::set_library_path(ld_library_path); FREE_C_HEAP_ARRAY(char, ld_library_path, mtInternal); } // Extensions directories. -  sprintf(buf, "%s" EXTENSIONS_DIR ":" SYS_EXT_DIR EXTENSIONS_DIR, Arguments::get_java_home()); +  sprintf(buf, "%s" EXTENSIONS_DIR, Arguments::get_java_home()); Arguments::set_ext_dirs(buf); // Endorsed standards default directory. </ins>

Describe the bug I encountered this bug when trying to use that does FFI. The particular call in general was the equivalent dlopen on the libc library and resolving to the system one which would cause a SIGSEGV. Digging into the source some more, you discover that Java sets a default value for if it's not explicitly set. Adding system libraries (i.e. /usr/lib) breaks/invalidates the hermetic invariant needed by Nix. These library paths are also searched first before those set in the DTRUNPATH of the ELF header as documented. I suggest the OVERRIDELIBPATH is either set to empty string maybe or even the contents of the ELF RUNPATH header itself. To Reproduce I was using JRuby which makes it easy to reproduce by using a gem which ultimately calls the JNR FFI. (The following reproduction results in the SIGSEGGV) Expected behavior Expected behavior is for the FFI call to work! This can be resolved by setting to the correct lib. NOTE: I could not merely set LDLIBRARYPATH because that would apply to everything in my nix-shell. Furthermore, wrapping java is somewhat tedious, seemed pragmatic for now. Notify maintainers Metadata Maintainer information: All JDK derivations
If you are curious for the JNR call that loads the C library:
OVERRIDELIBPATH is not sufficient, because it still SYSEXTDIR/lib, which is somewhere in . We'll need a patch. This also means we might as well write C code to get the right rpath value, even when . Although less useful, I'd be ok with a patch that just makes it . At least that will give a somewhat useful error message instead of a crash. ~It seems like OVERRIDELIBPATH was designed for cases like ours. Setting it to a static rpath value is tricky because that way we're duplicating it in a way that can't be later. It a statically known value. So I'd go with the empty value.~
I'm hoping (haven't tested) that with an empty OVERRIDELIBPATH the DTRUNPATH at least will be searched for. Do you want to work on this change together ?


Question: <ins> diff --git a/hotspot/src/os/linux/vm/os_linux.cpp b/hotspot/src/os/linux/vm/os_linux.cpp index c477851c1b..ff5e28d95b 100644 --- a/hotspot/src/os/linux/vm/os_linux.cpp +++ b/hotspot/src/os/linux/vm/os_linux.cpp @@ -368,13 +368,13 @@ void os::init_system_properties_values() { //        ... //        7: The default directories, normally /lib and /usr/lib. #if defined(AMD64) || defined(_LP64) && (defined(SPARC) || defined(PPC) || defined(S390)) -#define DEFAULT_LIBPATH "/usr/lib64:/lib64:/lib:/usr/lib" +#define DEFAULT_LIBPATH "" #else -#define DEFAULT_LIBPATH "/lib:/usr/lib" +#define DEFAULT_LIBPATH "" #endif // Base path of extensions installed on the system. -#define SYS_EXT_DIR     "/usr/java/packages" +#define SYS_EXT_DIR     "" #define EXTENSIONS_DIR  "/lib/ext" #define ENDORSED_DIR    "/lib/endorsed" @@ -437,13 +437,13 @@ void os::init_system_properties_values() { strlen(v) + 1 + sizeof(SYS_EXT_DIR) + sizeof("/lib/") + strlen(cpu_arch) + sizeof(DEFAULT_LIBPATH) + 1, mtInternal); -    sprintf(ld_library_path, "%s%s" SYS_EXT_DIR "/lib/%s:" DEFAULT_LIBPATH, v, v_colon, cpu_arch); +    sprintf(ld_library_path, "%s%s", v); Arguments::set_library_path(ld_library_path); FREE_C_HEAP_ARRAY(char, ld_library_path, mtInternal); } // Extensions directories. -  sprintf(buf, "%s" EXTENSIONS_DIR ":" SYS_EXT_DIR EXTENSIONS_DIR, Arguments::get_java_home()); +  sprintf(buf, "%s" EXTENSIONS_DIR, Arguments::get_java_home()); Arguments::set_ext_dirs(buf); // Endorsed standards default directory. </ins>

I don't have a lot of experience yet with the JDK derivation (8.nix etc..)
I don't have a lot of experience with that either, but I do implement RubberDuck and I'm happy to review Nix+Java ecosystem stuff.
Tagging who seems to do a lot of JVM Java work as well.
Reopening: more versions to be done
I marked this as stale due to inactivity. →
[x] OpenJDK 8: [x] OpenJDK 11: [ ] OpenJDK 17
why does openjdk 17 not have a mr?
Do you have a specific problem? With the example above I could not reproduce the jvm crash.
sorry, i thought i was hitting this bug, but turns out that the bug i hit is different
Is there a way to reproduce this issue for openjdk17? Otherwise I'd propose to close the issue.
Afaict, it has not been written yet. You may not have the "right" libraries in to make it crash. I don't think we need a reproducer. We know that the unpatched behavior is bad, and it is highly unlikely that upstream's behavior changes, because the rest of the world depends on it. did you have a specific reason not to patch OpenJDK 17? Could you patch it?
That patch does not seem to be too complicated. I could prepare it, but I'd feel better if I had some use case to test if the patch is working.
I mostly just forgot about it sadly. Some other stuff picked up and it kind of fell by the wayside sorry about that. On Thu, Jul 28, 2022, 2:19 AM Benjamin Asbach
Closing since it looks like the last bit of this was fixed by . Happy to reopen if I'm mistaken.


Question: installShellFiles = callPackage ../build-support/install-shell-files {}; <ins> # See doc/builders/special/invalidateFetcherByDrvHash.section.md or # https://nixos.org/manual/nixpkgs/unstable/#sec-pkgs-invalidateFetcherByDrvHash invalidateFetcherByDrvHash = f: args: let drvPath = (f args).drvPath; # It's safe to discard the context, because we don't access the path. salt = builtins.unsafeDiscardStringContext (lib.substring 0 12 (baseNameOf drvPath)); in f (args // { name = "${args.name or "source"}-salted-${salt}"; }); </ins> lazydocker = callPackage ../tools/misc/lazydocker { }; ld-is-cc-hook = makeSetupHook { name = "ld-is-cc-hook"; }

Fetchers are hard to test because when the output sha is verified, Nix won't download it again. This leads to confusion and PRs that are effectively untested because the others do not realize that they need to remove the store path before testing. Examples: Steps to reproduce the behavior: a fetcher -build the fetcher -build "success" but the fetcher is broken a PR effort The fetcher runs every time. This is expected but not realistic, because Nix can not guess what to re-fetch. Instead, we can make fetcher testing easier by adding fetcher tests following the pattern: So this uses IFD which is probably ok for ofborg? Regarding ; instead of somewhere, we'll have to use to set on the fetchers because they're functions. The salt may need to be passed externally in case of pure evaluation. We could make it a Nixpkgs parameter that defaults to . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Maintainer information:
Workaround: Use followed by
Or we can just put the salt in the parameter. Nix isn't clever enough to find same-hash renames in the store :)
And the salt can be derived from the unsalted drv path, which is exactly what we want. See


Question: path = with pkgs; [ iptables ipset iproute systemd ]; postStart = '' <del> ${pkgs.ipset}/bin/ipset -quiet create -exist sshguard4 hash:ip family inet ${pkgs.ipset}/bin/ipset -quiet create -exist sshguard6 hash:ip family inet6 </del> ${pkgs.iptables}/bin/iptables  -I INPUT -m set --match-set sshguard4 src -j DROP ${pkgs.iptables}/bin/ip6tables -I INPUT -m set --match-set sshguard6 src -j DROP '';

When the service starts, the following message is printed to the logs: sshguard[]: sshg-fw-ipset: Could not initialize firewall Blocking does not actually work. Blocked hosts can still initialize ssh connections. Default sshguard config. system: host os: multi-user?: sandbox: version: channels(root): channels(XXXX): nixpkgs:
It seems like that is due to ipsets being created of different types than intended. I'm not sure where it's getting created with that though: # ipset -L Name: sshguard4 Type: hash:ip Revision: 4 Header: family inet hashsize 1024 maxelem Size in memory: 88 References: 1 Number of entries: 0 Members: Name: sshguard6 Type: hash:ip Revision: 4 Header: family inet6 hashsize 1024 maxelem Size in memory: 104 References: 2 Number of entries: 0 Members: Whereas the script intends to create types which is why it returns with an error. I do not see where in the sshguard is type of ipset getting created. I came across though.


Question: { stdenv, fetchurl, nss, python3 , blacklist ? [] <del> , includeEmail ? false </del> <ins> # Used for tests only , runCommand , cacert , openssl </ins> }: with stdenv.lib;

Describe the bug Putting a valid certificate name in will cause nixos-rebuild to fail. To Reproduce Steps to reproduce the behavior: this line in . This command will fail. Expected behavior finishes sucessfully. Additional context This error message is related to : I guess this error is caused by switching to python 3. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata Please run and paste the result. Maintainer information:
isn't compatible with Python 3, it seems. We'll need to update or carry a patch.
MRTC:


Question: import ../make-test-python.nix ( <del> { pkgs, lib, ... }: { </del> <ins> { pkgs, lib, ... }: let quadletContainerFile = pkgs.writeText "quadlet.container" '' [Unit] Description=A test quadlet container [Container] Image=localhost/scratchimg:latest Exec=bash -c 'trap exit SIGTERM SIGINT; while true; do sleep 1; done' ContainerName=quadlet Volume=/nix/store:/nix/store Volume=/run/current-system/sw/bin:/bin [Install] WantedBy=default.target ''; in { </ins> name = "podman"; meta = { maintainers = lib.teams.podman.members;

Unable to use Podman's quadlets feature for a user, since the service unit files are not generated by systemd. Steps to reproduce the behavior: a quadlet file in (say, ) . Systemd says that no unit files were found. Caddy service should have been generated and its status displayed. This issue is caused by not symlinking the provided by the package to . Does not occur at the system level, since is already symlinked to Fix: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Confirmed the quadlet systemd user generator is not found in /etc/systemd. I'm gonna take this one and try to come up with a fix in NixOS module.


Question: wrapFirefox = { browser, browserName ? "firefox", desktopName ? "Firefox", nameSuffix ? "" <del> , icon ? "${browser}/lib/${browser.name}/icons/mozicon128.png" }: </del> <ins> , icon ? "${browser}/lib/${browser.name}/browser/icons/mozicon128.png" }: </ins> let cfg = stdenv.lib.attrByPath [ browserName ] {} config; enableAdobeFlash = cfg.enableAdobeFlash or false;

firefox package is missing its icon in the KDE4 menu whatever its called today.
Any update on this issue? Is it a license problem?
Try firefoxWrapper.


Question: { stdenv, lib, fetchurl, docbook_xsl, docbook_xsl_ns, gettext, libxslt, glibcLocales, docbook_xml_dtd_412, docbook_sgml_dtd_41, texlive, opensp <del> , perl, buildPerlPackage, ModuleBuild, TextWrapI18N, LocaleGettext, TermReadKey, SGMLSpm, UnicodeLineBreak, PodParser, YAMLTiny }: </del> <ins> , perl, buildPerlPackage, ModuleBuild, TextWrapI18N, LocaleGettext, TermReadKey, SGMLSpm, UnicodeLineBreak, PodParser, YAMLTiny , fetchpatch }: </ins> buildPerlPackage rec { pname = "po4a";

Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . nix-build '<nixpkgs' -A --check --keep-failed You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: nix-store --read-log $(nix-instantiate '<nixpkgs' -A ) Tested on nixpkgs
PR was merged and made it to nixos-unstable, so this should be fixed


Question: libnotify libxfce4ui libxfce4util <ins> pcre </ins> xfconf ];

Describe the bug The Thunar bulk-rename dialog doesn't support regular expressions. To Reproduce Steps to reproduce the behavior: multiple files. -Click → Rename. "Search & Replace" Expected behavior The "Regular Expression" option can be checked. Screenshots ! Additional context This appears to be because it is not using PCRE or PCRE doesn't support UTF-8. I support it isn't being built with PCRE at all. Notify maintainers No maintainers, touched it last. Metadata system: host os: multi-user?: sandbox: version: channels(kevincox): channels(root): nixpkgs: Maintainer information:


Question: "colorlog" "emoji" "immutabledict" <ins> "sarge" </ins> "sentry-sdk" "watchdog" "wrapt"


Question: <ins> { lib, rustPlatform, fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "typst-fmt"; version = "unstable-2023-04-16"; src = fetchFromGitHub { owner = "astrale-sharp"; repo = pname; rev = "9ed1fd1656f8e776b6c8d9d326c488f5ba1091eb"; hash = "sha256-yHR13n5yx5Yl2atteGQq+qqz21zsy37ZJfGllbvSZcQ="; }; cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "typst-0.2.0" = "sha256-+YHyxZTzMG9zpzLV9NgJsMtrXG+/ymPQo5b26HDYJaQ="; }; }; postPatch = '' cp ${./Cargo.lock} Cargo.lock ''; checkFlags = [ # test_eof is ignored upstream "--skip=rules::tests_typst_format::test_eof" ]; meta = with lib; { description = "A formatter for the Typst language"; homepage = "https://github.com/astrale-sharp/typst-fmt"; license = licenses.mit; maintainers = with maintainers; [ geri1701 ]; }; } </ins>

Project description Formatter for typst. Metadata homepage URL: source URL: license: mit, bsd, gpl2+ , ... platforms: unix, linux, darwin, ...
There is no CLI:
Looks like the author use .
looks like it is still a WIP in
what do you mean wrong default branch? Hi there, I wasn't sure there was interest for a cli, I'll merge the cli in a few days, want a ping then?
I merged my change, it should be good to package!
has renamed the project from typst-fmt to typstfmt in


Question: <ins> { lib , buildPythonApplication , fetchFromGitHub , gitMinimal , arrow , click , sh , wheel }: buildPythonApplication rec { pname = "gitlint"; version = "0.15.1"; src = fetchFromGitHub { owner = "jorisroovers"; repo = "gitlint"; rev = "v${version}"; sha256 = "sha256-CqmE4V+svSuQAsoX0I3NpUqPU5CQf3fyCHJPrjUjHF4="; }; nativeBuildInputs = [ wheel ]; propagatedBuildInputs = [ arrow click sh ]; preCheck = '' export PATH="$out/bin:$PATH" ''; checkInputs = [ gitMinimal ]; meta = { description = "Linting for your git commit messages"; homepage = "http://jorisroovers.github.io/gitlint"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ ethancedwards8 ]; }; } </ins>

Gitlint CLI tool and pre-commit hook plugin to lint commit messages with presets Metadata homepage URL: source URL: license: MIT platforms: linux, unix, darwin (python3)
This isn't my library, I simply requested for this package. should i still be included as maintainer?
Also, do I make a PR with the code above? Or is there already a PR
There is no PR yet. New packages need a maintainer and I don't want to maintain this.
I'll do it. I'll send in a PR now.


Question: nativeBuildInputs = [ autoconf cargo <del> dump_syms </del> llvmPackages.llvm # llvm-objdump makeWrapper nodejs

Steps to reproduce the behavior: librewolf from nixpkgs master Add any other context about the problem here. Please run and paste the result.
I have the exact same issue but my machine is a little slower :|. Also this means (not just Git ) is now broken.
I also reproduced this on master.
I think it's related to . I'm guessing the crash reporter symbols aren't generated because we disable the crash reporter. Running some tests to confirm.
is the first broken commit on master.
I'm going to close this. The PR by fixes the problem.


Question: <del> { lib, stdenv, fetchFromGitHub, rustPlatform, Security, installShellFiles }: </del> <ins> { lib , stdenv , fetchFromGitHub , rustPlatform , Security , SystemConfiguration , installShellFiles }: </ins> rustPlatform.buildRustPackage rec { pname = "ferium";

Steps to reproduce the behavior: ferium cc thanks! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: ./darwin-mutexes-4.8.patch ]; <ins> drvArgs.configureFlags = lib.optional (targetPlatform.useLLVM or false) "--with-mutex=POSIX/pthreads"; </ins> drvArgs.hardeningDisable = [ "format" ]; drvArgs.doCheck = false; })

Steps to reproduce the behavior: Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: openai = with python3Packages; toPythonApplication openai; <ins> openai-whisper = with python3.pkgs; toPythonApplication openai-whisper; </ins> opengrok = callPackage ../development/tools/misc/opengrok { }; openocd = callPackage ../development/embedded/openocd { };

Project description Whisper is a general-purpose speech recognition model. It is trained on a large dataset of diverse audio and is also a multi-task model that can perform multilingual speech recognition as well as speech translation and language identification. Metadata homepage URL: source URL: license: mit platforms: all
PTAL.


Question: if (ipc) { const generator = (stdout: any, res: any) => { <del> diff --git a/src/floating_exceptions/src/main.ts b/src/floating_exceptions/src/main.ts index f298ec7..87a6bc4 100644 --- a/src/floating_exceptions/src/main.ts +++ b/src/floating_exceptions/src/main.ts @@ -1,4 +1,4 @@ -#!/usr/bin/gjs +#!/usr/bin/env gjs imports.gi.versions.Gtk = '3.0' @@ -329,4 +329,4 @@ function main() { Gtk.main() } -main()  No newline at end of file +main() </del> diff --git a/src/panel_settings.ts b/src/panel_settings.ts index 83ff56c..1bc1e98 100644 --- a/src/panel_settings.ts

In 's tray menu the options "Floating Window Exceptions" & "Active Hint Color" don't work. Steps to reproduce the behavior: & enable pop-shell in GNOME (Wayland). pop-shell's tray menu and try clicking the mentioned options. Further dialogs should open for the respective features.
I found the problem: the compiled (g)js are not executible in filesystem. I do not know a solution yet. Most beautiful solution, fix chmod in pop-shell (but how ...). Or after compiling with an workaround in nix. Other solutions are set path to gjs during patching. Till fixing, you can run this features in your in, with calling it per gjs ...


Question: , zlib , zstd <ins> # Dependencies of overridden Python dependencies, hopefully we can remove these soon. , rustPlatform </ins> # Optional Dependencies , curl ? null , expat ? null

Steps to reproduce the behavior:  nixos-unstable Noticed when setting and rebuilding <!-- 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]:
You won't get a reply if you leave that empty.
I'm having the same issue I didn't notice when it happened, but I also have sambaFull
Same error whit the package .
This seems related to
That turned out not to be the issue. The actual error: In colour so that one can actually make sense of C++ error messages: ! One potential problem here: This is because of having: Switching to : Builds Removing entirely (which swiches to ): Fails on new related errors (see below) Removing and : Fails because Ceph requires lua = 5.3 and nixpkgs's default is still 5.2: CMake saysCould NOT find Lua (missing: LUAINCLUDEDIR) (Required is at least version "5.3")` Build failure with : <details</detailsI noticed Arch . But we can just use to fix the build.
PR for the


Question: || cfg.openssh.authorizedKeys.keyFiles != []) ) cfg.users) ++ [ config.security.googleOsLogin.enable <del> ]); </del> <ins> ]; </ins> message = '' Neither the root account nor any wheel user has a password or SSH authorized key. <del> You must set one to prevent being locked out of your system.''; </del> <ins> You must set one to prevent being locked out of your system. If you really want to be locked out of your system, set users.allowNoPasswordLogin = true; However you are most probably better off by setting users.mutableUsers = true; and manually running passwd root to set the root password. ''; </ins> } ] ++ flatten (flip mapAttrsToList cfg.users (name: user: [

Describe the bug There are reasons to want a system, that has no user that can log in by SSH or with their password, for example in a declarative container To Reproduce Steps to reproduce the behavior: up a minimal declarative container asserts that I will be locked out from the system and refuses to build the configuration with Expected behavior nix generates me a container that I can log in with , or maybe I don't want to log into it at all (because it's a disposable VM or something of the like). I think there should be a check whether the generated system is a container and an additional "I know what I'm doing" override for other cases. I'll create a PR once we agreed on what's best. Maintainer information: Code causing the problem: mentioning since you the check.
Is it an option to set a randomly-generated (the hash itself would be generated, not obtained by honestly hashing a password)? Recovering the password from such a hash is probably harder than a lot of other attack vectors. But an override «doLockOutEveryone» sounds fine.
Setting a password would certainly be a possibility, but somewhat (for lack of a better word) really lame. Having slept a night over it, I propose , that disables all the assertions at the bottom. I can see scenarios where two users with the same uid could be wanted. I want my unixoid to always give me enough rope to shoot myself in the leg.
What about not enabling ssh and disabling the getty? It should completely lock anyone out, unless I am missing something. Take a look at the profile.
In case of a nixos declaratively defined nixos container, you are not logged out because the root system(d) can generate a root shell without any authentication, which is why I consider this a bug. Having to "fool" the assertion to actually lock oneself out is another matter, I could live with that but I don't think it's nice behavior.
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this.


Question: || cfg.openssh.authorizedKeys.keyFiles != []) ) cfg.users) ++ [ config.security.googleOsLogin.enable <del> ]); </del> <ins> ]; </ins> message = '' Neither the root account nor any wheel user has a password or SSH authorized key. <del> You must set one to prevent being locked out of your system.''; </del> <ins> You must set one to prevent being locked out of your system. If you really want to be locked out of your system, set users.allowNoPasswordLogin = true; However you are most probably better off by setting users.mutableUsers = true; and manually running passwd root to set the root password. ''; </ins> } ] ++ flatten (flip mapAttrsToList cfg.users (name: user: [

Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .
This is still an issue.
I marked this as stale due to inactivity. →
Fixed via


Question: # Splicer will pull out correct variations libDeps = platform: [ ncurses ] ++ stdenv.lib.optional (!enableIntegerSimple) gmp <del> ++ stdenv.lib.optional (platform.libc != "glibc") libiconv ++ stdenv.lib.optional enableDwarf elfutils; </del> <ins> ++ stdenv.lib.optional (platform.libc != "glibc") libiconv; </ins> toolsForTarget = [ pkgsBuildTarget.targetPackages.stdenv.cc

Our can no longer link executables. For example: This issue is present in current versions of . Compiling and linking works fine with an older revision, say . It looks like this might be related to some change in binutils, maybe?
This is probably from
Yes, it is. came to the same conclusion.
This probably is GHC bug though. Things like gmp and libiconv get their paths hardcoded so this isn't a problem. I would expect the same treatment for elfutils. should provide a arg.
/cc
I guess now I know why there's a patch in branch.
I'll reopen the PR fixing the linking issues.
I opened while we wait on upstream fix.
Which one, from
Yes, although it doesn't help. See
Yes, it would have surprised me a bit if it helped against that symptom -- my patch fixes that DWARF-enabling is skipped completely.
I'm surprised this worked for you back then and now there are linking errors.


Question: ${pkgs.remarshal}/bin/json2yaml -i ${lovelaceConfigJSON} -o $out ''; <del> availableComponents = pkgs.home-assistant.availableComponents; </del> <ins> availableComponents = cfg.package.availableComponents; </ins> # Given component "parentConfig.platform", returns whether config.parentConfig # is a list containing a set with set.platform == "platform".

Nixos build error when using a MQTT sensor, following . being the channel. The corresponding line seems to have been removed in : which is the commit for the update to . Maybe the code has changed and the python script no longer recognises sensors correctly ? system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
The configuration you listed above does not yield an evaluation error. I have verified that by building it myself. You must have specified somewhere else.
I don't have any other mention of in my config, although I have also configured an external mqtt brocker with which might change the evaluation. I can confirm that when I remove the sensor config, the evaluation error goes away, which is why I didn't think I needed to include the brocker config. Those are the only mention of in my config I promise! Still it's strange that the line was removed from no ?
I've just noticed now that I have forgotten in my config... Here is the actual pieces of relevant config:
That's the default. No need to include it. After all, I was able to reproduce your error by building NixOS from the stable channel. My bad. It's caused by the following line: which will use the from the stable package. However, if I set I get which I still have to investigate.
I really have no idea what's going on. The way I test this is by having a file with the following content: and a checkout of the branch with the following diff at : When building the configuration I get What's strange is that there is no error when points to the branch with the diff applied. Maybe or have a clue.
I am happy you could reproduce this! Still, I don't see any line for in the (but I see it in the ), which I think it will lead to problems when it will be merged, no ? What I still find strange, is that the referred file in my original error is from ... Is this making any sense ?
Yes, this makes sense: The module is taking the list of from the stable channel and passing those used in your config to the package from the unstable channel, which obviously can't find the component since it's no longer in .
Ok, thank you for your explanations, I understand where the error comes from now !


Question: ${pkgs.remarshal}/bin/json2yaml -i ${lovelaceConfigJSON} -o $out ''; <del> availableComponents = pkgs.home-assistant.availableComponents; </del> <ins> availableComponents = cfg.package.availableComponents; </ins> # Given component "parentConfig.platform", returns whether config.parentConfig # is a list containing a set with set.platform == "platform".

I did some digging around to know why the line has disappeared from the with the update. This is what I found out: on the home-assistant repository, the code for the mqtt sensor was moved from the to between and this means that the is now in the When I define a mqtt sensor in my nixos config, will the nixos module be able to do the conversion from to (I don't fully understand the code in the nixos module, especially the code) ?
Not yet. I will implement that once I was able to solve the stack overflow issue.
The problem should be solved once you upgrade your system since is now in the channel. Can you please try again?
I can confirm that I don't have the build error anymore, thank you ! However, the home-assistant environment is missing component dependencies. Same as stated previously, home-assistant code has been refactored, but config is the same, which means that dependencies are not found. For example, I have declared in config, but dependencies are at the key.
Adjusting the code for is on my TODO list. For now, please override the package's .
Ok, at the moment, I am using manual config because I am testing home-assistant, using and the automation editor, so I have manually set the . Do you think we could add a package (something like ) which would have all possible dependencies (the idea being that I would also be built by hydra) - a little like the docker/distro image that distributes ?
Sure, no problem. However, I suscpect that will often not build due to some Python packages not building. Do you want to make a PR or should I do it?
I can surely try, but I am not sure how I should proceed : I define a new option for package that populates to all packages referenced in should I call the package with all packages referenced in (in a new file next to ), and call it in a new in . Which option do you think is best ?
I guess the first option comes close to the best one. However, please don't use for that but directly add the packages to . Maybe we could also add a few lines to to add a list of all packages to so that we don't go through all components to generate that list.


Question: configureFlags = [ "--with-gtk" "--with--board3d" ]; <ins> desktopItems = makeDesktopItem { desktopName = "GNU Backgammon"; name = pname; genericName = "Backgammon"; comment = meta.description; exec = pname; icon = pname; categories = [ "Game" "GTK" "StrategyGame" ]; }; </ins> meta = with lib; { description = "World class backgammon application"; homepage = "https://www.gnu.org/software/gnubg/";

Package name: gnubg Latest released version: 1.07.001 <!-- Search your package here: --- Current version on the unstable channel: 1.06.002 Current version on the stable/release channel: 1.06.002 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR.
I packaged this in 2015 and I have no idea why.


Question: fsck = handleTest ./fsck.nix {}; fwupd = handleTestOn ["x86_64-linux"] ./fwupd.nix {}; # libsmbios is unsupported on aarch64 gdk-pixbuf = handleTest ./gdk-pixbuf.nix {}; <ins> gotify-server = handleTest ./gotify-server.nix {}; </ins> gitea = handleTest ./gitea.nix {}; gitlab = handleTest ./gitlab.nix {}; gitolite = handleTest ./gitolite.nix {};

Project description A simple server for sending and receiving messages in real-time per WebSocket. Includes a web UI, also has an Android client for receiving notifications and an optional CLI program (distributed separately) for sending notifications. Metadata homepage URL: source URL: license: MIT platforms: anything Go runs on
I started an attempt locally, however it failed due to some timeouts while fetching Go dependencies... will retry during this week :)
I think the main difficulty is the UI, which needs to be compiled with NPM. In essence, I think the build is three-staged: fetch UI dependencies, fetch Go dependencies, do the actual build.
You may want to take a look at .


Question: <ins> { lib, stdenv, fetchFromGitHub, cmake, libminc }: stdenv.mkDerivation { pname = "ebtks"; version  = "unstable-2017-09-23"; src = fetchFromGitHub { owner  = "BIC-MNI"; repo   = "EBTKS"; rev    = "67e4e197d8a32d6462c9bdc7af44d64ebde4fb5c"; sha256 = "1a1qw6i47fs1izx60l1ysabpmyx9j5sjnbdv8b47wi2xcc9i3hpq"; }; # error: use of undeclared identifier 'finite'; did you mean 'isfinite'? postPatch = '' substituteInPlace templates/EBTKS/SimpleArray.h  --replace "#define FINITE(x) finite(x)" "#define FINITE(x) isfinite(x)" '' # error: ISO C++17 does not allow 'register' storage class specifier + '' find . -type f -exec sed -i -e 's/register //g' {} + ''; nativeBuildInputs = [ cmake ]; buildInputs = [ libminc ]; cmakeFlags = [ "-DLIBMINC_DIR=${libminc}/lib/cmake" ]; meta = with lib; { homepage = "https://github.com/BIC-MNI/EBTKS"; description = "Library for working with MINC files"; maintainers = with maintainers; [ bcdarwin ]; platforms = platforms.unix; license   = licenses.free; }; } </ins>

For x8664-darwin, aarch64-darwin: build .#EBTKS x8664-darwin: aarch64-darwin:


Question: openapi-core = callPackage ../development/python-modules/openapi-core { }; <ins> openusd = callPackage ../development/python-modules/openusd { alembic = pkgs.alembic; }; </ins> overly = callPackage ../development/python-modules/overly { }; overpy = callPackage ../development/python-modules/overpy { };

Project description Universal Scene Description (USD) is an efficient, scalable system for authoring, reading, and streaming time-sampled scene description for interchange between graphics applications. OpenUSD is AFAIK the library to work with the USD format. Metadata homepage URL: source URL: license: Modified Apache 2.0 License platforms: unix, linux, darwin
I've got a working derivation, but I'm not sure if this is already in a state that is good enough for a PR. In particular, packaging the pyside tools properly didn't seem straightforward to me. AFAICT, it just copies some binaries from other QT parts and wraps them with extra arguments, so that's what I'm doing here. While the python package seems to be working properly, I ran into an issue before when trying to include the headers into a C++ project, and I believe it failed to find some python headers? Maybe that needs some extra buildInput? I haven't investigated more. Locally, I've just been using a version compiled with for that. The binaries, such as , are working by my testing, besides requiring on wayland. I'd be happy to make a PR for this if this is a good-enough state.


Question: ''; strictDeps = true; <del> propagatedBuildInputs = [ bintools ] ++ extraTools ++ optionals cc.langD or false [ zlib ]; </del> <ins> propagatedBuildInputs = [ bintools ] ++ extraTools ++ optionals cc.langD or cc.langJava or false [ zlib ]; </ins> depsTargetTargetPropagated = optional (libcxx != null) libcxx ++ extraPackages; setupHooks = [

NixOS's wrappers for gcc also apply for gcj, which is a Java compiler. The wrappers add the flag to gcj's command line, however the Java language does not have a preprocessor, and means a different thing for gcj. This means that gcj cannot compile anything. Another issue is that gcj links to zlib by default, but does not pull zlib into the environment. This means that, even if the former issue is silenced with , compilation still wouldn't work.
A similar problem for gfortran:
I marked this as stale due to inactivity. →


Question: <del> { lib, stdenv, fetchurl, fetchpatch, libtool }: </del> <ins> { lib, stdenv, fetchurl, fetchpatch, libtool, libtommath }: </ins> stdenv.mkDerivation rec { pname = "libtomcrypt";

Bug description nixos-build switch produces a build error due to firebird-2.5.7.-0 while firebird is not explicitly mentioned anywhere in the file... To Reproduce -channel --update -build switch error message a few apps from file hoping that one of them would be asking for firebird to be installed behind the scene at no avail... Expected behavior A clean error free build. Screenshot ... making all in engines/ccgost... g++ -DREENTRANT -I. -I../common -I../common -I./unicode -I./.. -DREENTRANT -DHAVECONFIGH -DULAYOUTIMPLEMENTATION -O -c -DPIC -fPIC -o HebrewLigatureData.o make[2]: Entering directory '/build/openssl-1.0.2u/engines/ccgost' gcc -I../../include -fPIC -DOPENSSLPIC -DOPENSSLTHREADS -DREENTRANT -DDSODLFCN -DHAVEDLFCNH -m64 -DLENDIAN -O3 -Wall -DOPENSSLIA32SSE2 -DOPENSSLBNASMMONT -DOPENSSLBNASMMONT5 -DOPENSSLBNASMGF2m -DRC4ASM -DSHA1ASM -DSHA256ASM -DSHA512ASM -DMD5ASM -DAESASM -DVPAESASM -DBSAESASM -DWHIRLPOOLASM -DGHASHASM -DECPNISTZ256ASM -c -o egosterr.o egosterr.c g++ -DREENTRANT -I. -I../common -I../common -I./unicode -I./.. -DREENTRANT -DHAVECONFIGH -DULAYOUTIMPLEMENTATION -O -c -DPIC -fPIC -o HebrewShaping.o g++ -DREENTRANT -I. -I./common -I./common -I./unicode -I./. -DREENTRANT -DHAVECONFIGH -DULAYOUTIMPLEMENTATION -O -c -DPIC -fPIC -o IndicClassTables.o gcc -I./.


Question: <del> { lib, stdenv, fetchurl, fetchpatch, libtool }: </del> <ins> { lib, stdenv, fetchurl, fetchpatch, libtool, libtommath }: </ins> stdenv.mkDerivation rec { pname = "libtomcrypt";

/include -fPIC -DOPENSSLPIC -DOPENSSLTHREADS -DREENTRANT -DDSODLFCN -DHAVEDLFCNH -m64 -DLENDIAN -O3 -Wall -DOPENSSLIA32SSE2 -DOPENSSLBNASMMONT -DOPENSSLBNASMMONT5 -DOPENSSLBNASMGF2m -DRC4ASM -DSHA1ASM -DSHA256ASM -DSHA512ASM -DMD5ASM -DAESASM -DVPAESASM -DBSAESASM -DWHIRLPOOLASM -DGHASHASM -DECPNISTZ256ASM -c -o gost2001keyx.o gost2001keyx.c error: narrowing conversion of '' from 'unsigned int' to 'icu30::IndicClassTable::ScriptFlags' {aka 'int'} [-Wnarrowing] 229 | static const IndicClassTable teluClassTable = {0x0C00, 0x0C6F, 3, TELUSCRIPTFLAGS, teluCharClasses, teluSplitTable}; | ^ error: narrowing conversion of '' from 'unsigned int' to 'icu30::IndicClassTable::ScriptFlags' {aka 'int'} [-Wnarrowing] 231 | static const IndicClassTable kndaClassTable = {0x0C80, 0x0CEF, 4, KNDASCRIPTFLAGS, kndaCharClasses, kndaSplitTable}; | ^ make[4]: [./config/mh-linux:43: IndicClassTables.o] Error 1 make[4]: Leaving directory '/build/Firebird-2.5.7.-0/extern/icu/source/layout' make[3]: [Makefile:98: all-recursive] Error 2 make[3]: Leaving directory '/build/Firebird-2.5.7.-0/extern/icu/source' make[2]: [ libicu] Error 2 make[2]: Leaving directory '/build/Firebird-2.5.7.-0/gen' make[1]: [Makefile:193: externallibraries] Error 2 make[1]: Leaving directory '/build/Firebird-2.5.7.


Question: <del> { lib, stdenv, fetchurl, fetchpatch, libtool }: </del> <ins> { lib, stdenv, fetchurl, fetchpatch, libtool, libtommath }: </ins> stdenv.mkDerivation rec { pname = "libtomcrypt";

-0/gen' make: [Makefile:6: firebird] Error 2 builder for '/nix/store/589jgyzjbbn6zl870qswm80pi4xh8ffq-firebird-2.5.7.-0.drv' failed with exit code 2 building '/nix/store/f5v53hni9pnldx4l0v4svxv0ibl62ir3-tor-browser-linux64-9.0.9en-'. cannot build derivation '/nix/store/c1wpclz112ssp5ki6m546llszn144bq8-wt-': 1 dependencies couldn't be built cannot build derivation '/nix/store/8izfzp2k51zz3385cq14ffd31l2c8bwg-fileshelter-': 1 dependencies couldn't be built cannot build derivation '/nix/store/wi7fzbgmwj9rrzm48mlcsvw51lymmcz8-system-': 1 dependencies couldn't be built building '/nix/store/75r17sql3df7jq3azd76w9fjw6870wm6-'. building '/nix/store/0zq0cb92k0w72ri9jb2zd65gzpnhx6fv-udev-'. building '/nix/store/jqc775s8a0m6r6qhwcfssjdya326s6z0-unit-NetworkManager-'. building '/nix/store/bvg0a7ah4bd77s86f16rq7jsl7sh3nxy-unit-NetworkManager-wait-'. building '/nix/store/vbnnzk9kdx828c8vi3pqcjayrf1ja43n-unit-'. building '/nix/store/df1ffd22pbca5x7ya5mwa8prm40mg54p-unit-alsa-'.


Question: <del> { lib, stdenv, fetchurl, fetchpatch, libtool }: </del> <ins> { lib, stdenv, fetchurl, fetchpatch, libtool, libtommath }: </ins> stdenv.mkDerivation rec { pname = "libtomcrypt";

cannot build derivation '/nix/store/4375h9w8pmppld22s4jb6ag05riw87vg-xsession-': 1 dependencies couldn't be built cannot build derivation '/nix/store/gi689m2ph1avv6n2svvlzr5d2v2xm4p1-nixos-system-bx26-': 1 dependencies couldn't be built error: build of '/nix/store/gi689m2ph1avv6n2svvlzr5d2v2xm4p1-nixos-system-bx26-' failed Notify Weber <marco-<!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Metadata* system: host os: multi-user?: sandbox: version: channels(root): channels(k): nixpkgs:
This is pulled in as an indirect dependency of via .
I marked this as stale due to inactivity. →


Question: <del> { haskellLib }: </del> <ins> { haskellLib, fetchpatch, buildPackages }: </ins> <del> let inherit (haskellLib) addBuildTools appendConfigureFlag dontHaddock doJailbreak; </del> <ins> let inherit (haskellLib) addBuildTools appendConfigureFlag dontHaddock doJailbreak markUnbroken overrideCabal; </ins> in self: super: { <del> ghcjs = doJailbreak (super.ghcjs.overrideScope (self: super: { </del> <ins> ghcjs = overrideCabal (drv: { # Jailbreak and patch can be dropped after https://github.com/ghcjs/ghcjs/pull/833 jailbreak = true; patches = drv.patches or [] ++ [ (fetchpatch { name = "ghcjs-aeson-2.0.patch"; url = "https://github.com/ghcjs/ghcjs/commit/9ef1f92d740e8503d15d91699f57db147f0474cc.patch"; sha256 = "0cgxcy6b5870bv4kj54n3bzcqinh4gl4w4r78dg43h2mblhkzbnj"; }) ]; }) (super.ghcjs.overrideScope (self: super: { </ins> optparse-applicative = self.optparse-applicative_0_15_1_0; <ins> webdriver = overrideCabal (drv: { patches = drv.patches or [] ++ [ # Patch for aeson 2.0 which adds a lower bound on it, so we don't apply it globally # Pending https://github.com/kallisti-dev/hs-webdriver/pull/183 (fetchpatch { name = "webdriver-aeson-2.0.patch"; url = "https://github.com/georgefst/hs-webdriver/commit/90ded63218da17fc0bd9f9b208b0b3f60b135757.patch"; sha256 = "1xvkk51r2v020xlmci5n1fd1na8raa332lrj7r9f0ijsyfvnqlv0"; excludes = [ "webdriver.cabal" ]; }) ]; # Fix line endings so patch applies prePatch = drv.prePatch or "" + '' find . -name '*.hs' | xargs "${buildPackages.dos2unix}/bin/dos2unix" ''; jailbreak = true; broken = false; }) super.webdriver; </ins> })); }

As a fallout of the migration to GHC 9.0.2 got marked as broken, as it failed to build with GHC 9.0.2 and the Stackage LTS 19 package set we now have. It would be necessary to investigate if survived this (i.e. if it still builds) and if not to get it to work again. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc
should compile again. The bootstrap is additionally built by Hydra, so only the GHC bundled libraries will need to be compiled (which is an improvement to before at least).


Question: # package customization , channel ? "stable" , enableNaCl ? false <del> , enableHotwording ? false </del> , gnomeSupport ? false, gnome ? null , gnomeKeyringSupport ? false , proprietaryCodecs ? true

When building chromium with args like this and the gn args aren't known/accepted by chromium (like the above one actually is that is still given incorrectly in 18.03), it will print: but continue to build anyway, which can be super surprising when your build doesn't do what you expect. We should catch that when building. Unfortunately doesn't seem to have a feature to warn. But we can run to see the in stdout and grep for it: I have confirmed that only seems to work that way when giving a build target, like . CC
Suggestion: We switch to
PR
pull request was merged.


Question: <del> { lib, stdenv, fetchFromGitHub, makeWrapper, perl, procps, file, gnused, bash }: </del> <ins> { lib, stdenv, fetchFromGitHub, makeWrapper, perl, procps, file, gnused, bash, binutils }: </ins> stdenv.mkDerivation rec { pname = "lesspipe";

According to documentation of the app: there's a dozen dependencies we don't explicitly have a dependency on, so there's multitude of bugs that might appear depending on what's on $PATH.
Do we need a new maintainer of to move this issue forward?
We should pull the package from NixOS core...absolutely no reason to have such a bloated less ship by default.


Question: pnpmWorkspace prePnpmInstall ; <del> hash = "sha256-n7HTd/rKxJdQKnty5TeOcyvBU9j/EClQ9IHqbBaEwQE="; </del> <ins> hash = "sha256-q9a4nFPRhR6W/PT1l/Q1799iDmI+WTsudUP8rb8e97g="; </ins> }; nativeBuildInputs = [

Package name: astro-language-server Latest released version: 2.14.2 <!-- Search your package here: --- Current version on the unstable channel: 2.10.0 Current version on the stable/release channel: None <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'm on it ^^. I've got a working version. Gonna soon open a PR :+1:


Question: stdenv.mkDerivation rec { pname = "opensc"; <del> version = "0.20.0"; </del> <ins> version = "0.21.0"; </ins> src = fetchFromGitHub { owner = "OpenSC"; repo = "OpenSC"; rev = version; <del> sha256 = "0mg8qmhww3li1isfgvn5hang1hq58zra057ilvgci88csfziv5lv"; </del> <ins> sha256 = "sha256-OjOfA1pIu8NeN+hPuow5UVMKsg0PrsLojw5h05/Qm+o="; </ins> }; <del> patches = [ (fetchpatch { # https://nvd.nist.gov/vuln/detail/CVE-2020-26570 name = "CVE-2020-26570.patch"; url = "https://github.com/OpenSC/OpenSC/commit/6903aebfddc466d966c7b865fae34572bf3ed23e.patch"; sha256 = "sha256-aB9iCVcdp9zFhZiSv5A399Ttj7NUHRVgXr0EfmMwKN4="; }) (fetchpatch { # https://nvd.nist.gov/vuln/detail/CVE-2020-26572 name = "CVE-2020-26572.patch"; url = "https://github.com/OpenSC/OpenSC/commit/9d294de90d1cc66956389856e60b6944b27b4817.patch"; sha256 = "sha256-gKJaR5K+NaXh4NeTkGpzHzHCdpt6n54Hnt1GAq0tA9o="; }) ]; </del> nativeBuildInputs = [ pkgconfig autoreconfHook ]; buildInputs = [ zlib readline openssl libassuan

, CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) CVSSv3=5.5 (nixos-20.03, nixos-20.09, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-20.09: ; nixos-unstable: . Cc
CVE-2020- doesn't seem to have a patch yet. The rest (for all mentioned branches) is going to be addressed in .


Question: in python3.pkgs.buildPythonApplication rec { pname = "matrix-synapse"; <del> version = "1.112.0"; </del> <ins> version = "1.113.0"; </ins> format = "pyproject"; src = fetchFromGitHub { owner = "element-hq"; repo = "synapse"; rev = "v${version}"; <del> hash = "sha256-8iXw9C91kPWDlzo/3AA/iVCQqq47eGSORMTzEQTTS+8="; </del> <ins> hash = "sha256-8Ts2QOSugPU8Do1Mpusez9tSqiaB+UzCWWY4XJk/KRM="; </ins> }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}"; <del> hash = "sha256-hx/IMOxk4vUHXMMIcnxnC3RJcIvJL+IooZnf+m+VKSs="; </del> <ins> hash = "sha256-Jlnv3GAobrXaO5fBq6oI9Gq8phz2/jFc+QIUYsUyeNo="; </ins> }; postPatch = ''

Package name: matrix-synapse Latest released version: v1.113.0 <!-- Search your package here: --- Current version on the unstable channel: 1.112.0 Current version on the stable/release channel: 1.112.0 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: cmakeFlags = [ "-DBUILD_SHARED_LIBS=${if static then "OFF" else "ON"}" "-DCMAKE_SKIP_BUILD_RPATH=OFF" <ins> "-DSNAPPY_BUILD_TESTS=OFF" "-DSNAPPY_BUILD_BENCHMARKS=OFF" </ins> ]; postInstall = '' substituteInPlace "$out"/lib/cmake/Snappy/SnappyTargets.cmake  --replace 'INTERFACE_INCLUDE_DIRECTORIES "''${_IMPORT_PREFIX}/include"' 'INTERFACE_INCLUDE_DIRECTORIES "'$dev'"' <ins> mkdir -p $dev/lib/pkgconfig cat <<EOF > $dev/lib/pkgconfig/snappy.pc Name: snappy Description: Fast compressor/decompressor library. Version: ${version} Libs: -L$out/lib -lsnappy Cflags: -I$dev/include EOF </ins> ''; <del> checkTarget = "test"; </del> <ins> #checkTarget = "test"; </ins> <del> doCheck = true; </del> <ins> # requires gbenchmark and gtest but it also installs them out $dev doCheck = false; </ins> meta = with lib; { homepage = "https://google.github.io/snappy/";

Describe the bug Because snappy does not install a pkgconfig file, you can't take snappy as a buildInput, packages will never find it. To Reproduce Expected behavior Metadata system: host os: multi-user?: sandbox: version: channels(seb): nixpkgs: Maintainer information: cc
I have opened a PR on the snappy codebase: It is waiting for review and then nixpkgs will need to be updated. Note how the PR has to handle the absolute path being configured in cmake by nix
has decided not to take the patch upstream, so I will work on adding the pkg-config file as part of the nix installation
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . 3. Ask on the on .


Question: , fetchurl , dpkg , autoPatchelfHook <ins> , copyDesktopItems </ins> , pango , gtk3 , alsa-lib

When installed through Nix, Bluemail does not create a desktop shortcut in $out/share/applications. The program can only be run through the terminal by default. The program also fails to load unless the --disable-gpu-sandbox option is used. Steps to reproduce the behavior: Bluemail by adding to , and rebuild. for Bluemail in the Application Launcher - not present in terminal - core dumps on gpu process not usable in terminal - bluemail opens with the default wayland icon What currently happens is detailed step-by-step above. What I'd expect to happen is that a desktop icon is created when I rebuild to install bluemail, and that clicking the application from the Application Launcher opens bluemail without a core dump. Installing from NixOS-Unstable Running on Intel UHD Graphics (10th Gen)


Question: stdenv.mkDerivation rec { pname = "calibre"; <del> version = "6.11.0"; </del> <ins> version = "6.15.1"; </ins> src = fetchurl { url = "https://download.calibre-ebook.com/${version}/${pname}-${version}.tar.xz"; <del> hash = "sha256-ylOZ5ljA5uBb2bX/qFhsmPQW6dJVEH9jxQaR2u8C4Wc="; </del> <ins> hash = "sha256-t9fG1hBlQmDh0i5ezBoqk9C9oliNNF0peKDz1YH7RBo="; </ins> }; # https://sources.debian.org/patches/calibre/${version}+dfsg-1

Package name: Latest released version: Current version on the unstable channel: Current version on the stable/release channel: Notify maintainers I attempted to update the version myself, but encountered an issue: Unfortunately, I don't have the time to investigate further at the moment. Therefore, I would appreciate it if someone else could take it from here. Note for maintainers: Please tag this issue in your PR.
I've updated the issue to reflect that the same error persists even with version .


Question: phases = [ "installPhase" "fixupPhase" ]; installPhase = '' <del> mkdir -p $out/bin cp ${src} $out/bin/kpcli chmod +x $out/bin/kpcli </del> <ins> mkdir -p $out/{bin,share} cp ${src} $out/share/kpcli.pl chmod +x $out/share/kpcli.pl </ins> <del> wrapProgram $out/bin/kpcli --set PERL5LIB  </del> <ins> makeWrapper $out/share/kpcli.pl $out/bin/kpcli --set PERL5LIB  </ins> "${with perlPackages; stdenv.lib.makePerlPath ([ CaptureTiny Clipboard Clone CryptRijndael SortNaturally TermReadKey TermShellUI FileKeePass TermReadLineGnu XMLParser ] ++ stdenv.lib.optional stdenv.isDarwin MacPasteboard)}"

Minor cosmetic issue: when using kpcli, the prompt shown to the user says ".kpcli-wrapped:/" instead of the usual "kpcli:/". system: host os: multi-user?: sandbox: version: channels(delroth): channels(root): nixpkgs:
Usually this can be fixed with the --argv0 flag:
kpcli uses wrapProgram which already sets --argv0 correctly AFAICT. Looks like this is a kpcli specific problem:
OK, I understand the reason why --argv0 did not work now. Since this is an interpreted script, we are indeed setting Perl's argv[0] to the right value, but within Perl 0) - Sent to just wrap the script manually and thus control the basename of the wrapped script.
Fixed in


Question: gspeech = callPackage ../applications/audio/gspeech { }; <ins> haruna = libsForQt5.callPackage ../applications/video/haruna { }; </ins> icesl = callPackage ../applications/misc/icesl { }; keepassx = callPackage ../applications/misc/keepassx { };

Project description Metadata homepage URL: source URL: license: idk, its not obvious and im not a lawyer platforms: unix/linux?


Question: terminal-parrot = callPackage ../applications/misc/terminal-parrot { }; <ins> epsonscan2 = pkgs.libsForQt5.callPackage ../misc/drivers/epsonscan2 { }; </ins> epson-alc1100 = callPackage ../misc/drivers/epson-alc1100 { }; epson-escpr = callPackage ../misc/drivers/epson-escpr { };

Project description Epson Scan 2 is a scanning utility for epson printers and scanners. Metadata homepage URL: source URL: license: platforms: linux
I spent some time on this, but probably packaging epsonscan2 isn't worth the effort. My findings: build is quite tricky, as the sources contain some amount of tweaks (overrides) to standard cmake variables for build/install paths, and some install commands don't use , non-free software plugin is required for network scanning: sources of epsonscan2 are hard-coded to search the plugin in same path as is the installation path of epsonscan2, which doesn't play nice the immutability, the scanner might be supported already by My all-in-one printer is EcoTank L3160, which isn't listed in , but is similar to EcoTank L3150. And, all that was need is the following config: Terminal output:
I've managed to get this working on PR . As you said, building is a complete pain and required a fair bit of patching. It would be great if other Epson scanner owners could test this!
Works for me with Epson L3150 with wifi connection and non free plugins.


Question: wayshot = callPackage ../tools/misc/wayshot { }; <ins> waylevel = callPackage ../tools/misc/waylevel { }; </ins> wbg = callPackage ../applications/misc/wbg { }; hikari = callPackage ../applications/window-managers/hikari {

Project description A tool to print Wayland toplevels status and info. Metadata homepage URL: source URL: license: bsd platforms: linux


Question: src = fetchurl { url = "https://www.expressvpn.works/clients/linux/expressvpn_${version}-1_amd64.deb"; <del> hash = "sha256-lyDjG346FrgT7SZbsWET+Hexl9Un6mzMukfO2PwlInA="; </del> <ins> hash = "sha256-cDZ9R+MA3FXEto518bH4/c1X4W9XxgTvXns7zisylew="; </ins> }; nativeBuildInputs = [ dpkg autoPatchelfHook ];

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


Question: # Update submodules init_submodules(){ <del> # Add urls into .git/config file clean_git submodule init # list submodule directories and their hashes git submodule status | while read -r l; do local hash local dir local name local url # checkout each submodule hash=$(echo "$l" | awk '{print $1}' | tr -d '-') dir=$(echo "$l" | sed -n 's/^.[0-9a-f]+ (.*[^)]*)( (.*))?$/1/p') name=$( git config -f .gitmodules --get-regexp submodule..*.path | sed -n "s,^(.*).path $dir$,1,p") url=$(git config --get "${name}.url") clone "$dir" "$url" "$hash" "" done </del> <ins> clean_git submodule update --init --recursive -j $NIX_BUILD_CORES </ins> } clone(){

Describe the bug clones each submodule in sequence instead of in parallel, which is unnecessarily slow for repos that have a lot of submodules (such as which has 64 direct submodules). At first I thought this was because git's setting defaults to , but it turns out doesn't even use that, it instead recursively clones the submodules by hand. it looks like you this 10 years ago; is there any reason we can't just use today? I don't know why it doesn't just use git's built-in submodule handling, doing so would make fixing this trivial. Parallelizing the manual clone loop seems a lot more complicated (especially because of the problem of mixed output). To Reproduce Steps to reproduce the behavior: from scratch. (Edit: was recently updated to not use submodules anymore. This can be reproduced using an older version) Expected behavior It should clone the repo in a reasonable amount of time. Notify maintainers Last few changes to were and Metadata system: host os: multi-user?: sandbox: version: channels(lily): nixpkgs: Maintainer information:
I marked this as stale due to inactivity. →
See
Simplified in


Question: ''; homepage = "https://nixos.org/"; license = licenses.lgpl2Plus; <del> maintainers = with maintainers; [ eelco lovesegfault artturin ]; </del> <ins> inherit maintainers; </ins> platforms = platforms.unix; outputsToInstall = [ "out" ] ++ optional enableDocumentation "man"; mainProgram = "nix";

Package name: nix23 Latest released version: 2.3.17 (see ) Current version on the unstable channel: 2.3.16 Current version on the stable/release channel: 2.3.16 Notify maintainers Note for maintainers: Please tag this issue in your PR. See for context. The release script apparently doesn't upload source tarballs anymore, so 2.3.17 sources look more like the other ones. There's a bunch of expressions in that might need to be revisited.


Question: description = "Open Source Routing Machine computes shortest paths in a graph. It was designed to run well with map data from the Openstreetmap Project"; license = lib.licenses.bsd2; maintainers = with lib.maintainers;[ erictapen ]; <del> platforms = lib.platforms.linux; </del> <ins> platforms = lib.platforms.unix; </ins> }; }

Steps to reproduce the behavior: FWIW: my fix is here, - but it is using a fork of . If somebody has the time to create a minimal patch on top of the current source, please feel free to. Please run and paste the result.
Looks like you are on a good path. Unfortunately I have no access to Apple hardware at all, but would be happy to merge a PR.
Yes, is working on it. There is a more active fork of luabind here: - how about we switch to using it? It'll obviate a bunch of patches as well.
I agree, sounds sensible.


Question: owner = "draios"; repo = "sysdig"; rev = version; <del> hash = "sha256-y6WArSz57w8vb3A3nHT37G6D8++6en2jQfeIS4YCD9U="; </del> <ins> hash = "sha256-oufRTr5TFdpF50pmem2L3bBFIfwxCR8f1xi0A328iHo="; </ins> }; nativeBuildInputs = [

Steps to reproduce the behavior: sysdig Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Can't repro on master () and the error isn't in the log output, can you provide additional info?
Hey, thanks for the response - checking again - it only happens if for me if I enable the sysdig-option in my config not building the sysdig-package - maybe this helps to reproduce and depends on the used kernel-version? I've uploaded the full build log:
Thanks, seems this is the error:
I guess this is already fixed upstream in the drivers () but needs to be to nixpkgs to fix 6.10-kernel builds.
fixes it for me
~Ah 0.38.1 - got released somehow oversaw it should check first if that includes the fix~ 38.1 does not include a driver-bump


Question: distro josepy parsedatetime <del> psutil </del> pyRFC3339 pyopenssl pytz <ins> requests </ins> six zope_component zope_interface ]; <del> buildInputs = [ dialog ] ++ (with python37Packages; [ mock gnureadline ]); </del> <ins> buildInputs = [ dialog mock gnureadline ]; </ins> <del> checkInputs = with python37Packages; [ pytest_xdist pytest dateutil ]; </del> <ins> checkInputs = [ pytest_xdist pytest dateutil ]; </ins> <del> postPatch = '' </del> <ins> preBuild = '' </ins> cd certbot <del> substituteInPlace certbot/_internal/notify.py --replace "/usr/sbin/sendmail" "/run/wrappers/bin/sendmail" </del> ''; postInstall = ''

Update certbot Current packaged version is 0.39.0, upstream version is 1.2.0.
Fix in


Question: , callPackage , cargo , cffi <ins> , cryptography-vectors ? (callPackage ./vectors.nix { }) </ins> , fetchPypi , hypothesis , iso8601

Steps to reproduce the behavior:  nixos-unstable Noticed when setting and rebuilding <!-- 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]:
You won't get a reply if you leave that empty.
I'm having the same issue I didn't notice when it happened, but I also have sambaFull
Same error whit the package .
This seems related to
That turned out not to be the issue. The actual error: In colour so that one can actually make sense of C++ error messages: ! One potential problem here: This is because of having: Switching to : Builds Removing entirely (which swiches to ): Fails on new related errors (see below) Removing and : Fails because Ceph requires lua = 5.3 and nixpkgs's default is still 5.2: CMake saysCould NOT find Lua (missing: LUAINCLUDEDIR) (Required is at least version "5.3")` Build failure with : <details</detailsI noticed Arch . But we can just use to fix the build.
PR for the


Question: }); contentsList = if builtins.isList contents then contents else [ contents ]; <ins> bind-paths = builtins.toString (builtins.map (path: "--bind=${path}:${path}!") [ "/dev/" "/proc/" "/sys/" "${builtins.storeDir}/" "$out/layer.tar" ]); </ins> # We store the customisation layer as a tarball, to make sure that # things like permissions set on 'extraCommands' are not overridden

Relevant snippet while building it fails with I copied over the for debugging, this is the full output: Steps to reproduce the behavior: snippet as flake default output Build should succeed and images should be loadable via Patching the as follows: fixes the problem, but would probably hide other cp errors. Maybe the behavior of coreutils/cp changed in the recent versions. At least the current manual states it will fail silently. I'm using a linux-builder on my machine.
Thank you for reporting this. I’ll try to replicate this locally. The lines do not look like errors to me. It looks like is informing that those files already exist in the output and thus are skipped (--no-clobber). However, if the build is failing there’s something going wrong.
Thank you for linking the manual. It looks like will exit with a non-zero status code in case of files that are already present now. The coreutils changelog states that now reproduces the behavior had at the time I wrote the mergeImages script. I was able to build by changing to . I don't know how to best go about obtaining the behavior everywhere, should the flag be dependent on the version of somehow? Maybe we can just assume that in will be a new version from now so that we can use everywhere? Given that all files that are present in both docker images apart from the and repositories files should be content addressed the only issue with removing is that time is spent unnecessarily writing content that's already present, so removing the flag altogether might make sense.
Thanks for investigating! I'm not familiar with the backward compatibility policy of the nix ecosystem, but I would assume that the most recent version of can assume most recent coreutils. Might happen that someone is overlaying old coreutils but then you might just need to overlay the old too, if you can pinpoint it down to coreutils cp.
True, but then apparently they have a legacy software problem, in which case they should use overrides only where it is necessary, instead of a blanket override in an overlay. It is not realistic to expect all of Nixpkgs to work with arbitrary changes. The cost of such compat logic isn't worth it; certainly not in this case, until proven otherwise. If they contribute a full time maintainer it is worth it, and if they have a legacy software problem they probably can.


Question: update-source-version perlPackages.SysVirt "$sysvirtVersion" --file="pkgs/top-level/perl-packages.nix" ''; <ins> passthru.tests.libvirtd = nixosTests.libvirtd; </ins> meta = { homepage = "https://libvirt.org/"; description = ''

When attempting to create a volume on a physical node pool parted is not found. Steps to reproduce the behavior: Create a physical disk node pool. Attempt to create a volume using that node pool. In this case I have created a node pool called and I am attempting to create a volume called Volume is created normally. If applicable, add screenshots to help explain your problem. I have tried to add parted manually using and overriding the package in the libvirtd module: but this did not fix the issue.
That won't work, it seems like we need to wrap to include in its . I'll take a look.
You most likely need to add it to in because libvirtd will probably call it.