Question: touch .${projectName}.d/env/94-appsbase.sh cd .. <del> mkdir -p /var/lib/${projectName}/mnt/{container,final,overlay,session,source} </del> <ins> mkdir -p /var/lib/${projectName}/mnt/session </ins> echo "root:x:0:0:System administrator:/root:/bin/sh" > /etc/passwd echo > /etc/resolv.conf TMPDIR=$(pwd -P) ${projectName} build $out ./img

The derivation is missing the directory to work properly. Steps to reproduce the behavior: A clear and concise description of what you expected to happen. is output without error. This can be fixed by creating the directory manually (). I guess this could be to the derivation. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Please run and paste the result.
NixOS module provides those top-level directories. discussed with one of the main Apptainer developer in . He think it should be easy to specify a directory that will always exist at build time. Regalding this, I'm considering the possibility to put those dilectories under the derivation store path. Not sure if there would be potential problem using a store path as a mount point, but it seems to work without problem.
Could you help me take a look at ?
If you have time, please help me test the PR . It should fundamentally solve this issue. If applied, you no longer need the NixOS module or just to run images. It specifies the LOCALSTATEDIR as , making both Apptainer and Sylabs SingularityCE works without . (The image running still depends on and to run images, which might be the final obstacle to build images as a package without invoking a virtual machine. Other than that, it should not be an issue for most users, as are available on most of the UNIX/UNIX-like systems.)
I removed (the temporary fix for this issue) and ran the following and it seems to work fine: Thank you for this fix!
Glad to hear that! Would you mind ? I've heard that committers tend to merge PRs getting two approvals.
Done!


Question: # Check whenever fileSystem is needed for boot.  NOTE: Make sure # pathsNeededForBoot is closed under the parent relationship, i.e. if /a/b/c # is in the list, put /a and /a/b in as well. <del> pathsNeededForBoot = [ "/" "/nix" "/nix/store" "/var" "/var/log" "/var/lib" "/var/lib/nixos" "/etc" ]; </del> <ins> pathsNeededForBoot = [ "/" "/nix" "/nix/store" "/var" "/var/log" "/var/lib" "/var/lib/nixos" "/etc" "/usr" ]; </ins> fsNeededForBoot = fs: fs.neededForBoot || elem fs.mountPoint pathsNeededForBoot; # Check whenever `b` depends on `a` as a fileSystem

systemd seems to use the term split-usr to refer to an attribute of a system, where: is a mount point. is not mounted "at boot". Since systemd v248, support for a split-usr system is deprecated: While don't seem to mention a formal removal of support of split-usr, it seems that . According to : It seems that if is a mount point, this unit calls with on it, regardless of whether it is already mounted — making the assumption that it had already been mounted "at boot". When I installed my first NixOS on my workstation, I made a filesystem for each path under . This let me customize options per directory as I wished, both at install and later on. ZFS's sharing of storage space between filesystems in the same zpool takes the cost out of being "generous" with the number of filesystems. I didn't know that is merely that happens to be generated at boot. I also didn't know that systemd deprecated split-usr. So I did not mark as . The system built successfully and booted successfully. Except for an error in the logs: The failure seems to be due to the attempt to remount using with the option a non-mounted filesystem — . is later successfully mounted along with the rest of the filesystems. Since systemd seems to expect that if is a mount point it would have already been mounted "at boot", I would expect NixOS to: 's to by default, . to build when 's is (that could be ). Understanding this error took around three hours of collaborative debugging with the tremendous help of A workaround is to set for , or to not have a mount point at all. The suggested solution (expected behavior) is with the goal of sparing all future users an investigation of this error. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Not sure who to mention. Please ignore if you no longer wish to be involved. If you happen to know who should be mentioned here and is not, please comment mentioning them. Please run and paste the result. Maintainer information:
gentoo notes this in their wiki as well
ping a couple people who might care: and probably others.


Question: <ins> import ./make-test-python.nix ({ pkgs, ... }: { name = "monado"; nodes.machine = { pkgs, ... }: { hardware.opengl.enable = true; users.users.alice = { isNormalUser = true; uid = 1000; }; services.monado = { enable = true; defaultRuntime = true; }; # Stop Monado from probing for any hardware systemd.user.services.monado.environment.SIMULATED_ENABLE = "1"; environment.systemPackages = with pkgs; [ openxr-loader ]; }; testScript = { nodes, ... }: let userId = toString nodes.machine.users.users.alice.uid; runtimePath = "/run/user/${userId}"; in '' machine.succeed("loginctl enable-linger alice") machine.wait_for_unit("user@${userId}.service") machine.wait_for_unit("monado.socket", "alice") machine.systemctl("start monado.service", "alice") machine.wait_for_unit("monado.service", "alice") machine.succeed("su -- alice -c env XDG_RUNTIME_DIR=${runtimePath} openxr_runtime_list") ''; }) </ins>

The [monado] package doesn't install the udev rules generated by the [xr-hardware util] from the Monado project. Install the package and check the lack of udev rules in It was expected for the udev rules to be installted with the package. The udev rules are needed as some hmd's have some strange and specific permissions. Maybe instead of adding this to the package, monado could turn into an option like . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: [monado]: [xr-hardware util]:
Trying packaging the udev rules similar to how . [brscan4]:
I was working on a Monado NixOS module. Perhaps I can deal with udev rules there. See


Question: --set-rpath "${stdenv.lib.makeLibraryPath buildInputs}"  $out/bin/anydesk <ins> # pangox is not actually necessary (it was only added as a part of gtkglext) patchelf  --remove-needed libpangox-1.0.so.0  $out/bin/anydesk </ins> wrapProgram $out/bin/anydesk  --prefix PATH : ${stdenv.lib.makeBinPath [ lsb-release ]}

Describe the bug Seems like some updates to pango broke a few packages Among the broken ones: ettercap (see ) pangox-compat (which anydesk needs) probably a few more To Reproduce Steps to reproduce the behavior: to build ettercap or anydesk from master will fail to build with some pango-related errors Expected behavior It should work Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata system: host os: multi-user?: sandbox: version: channels(maciej): nixpkgs: Maintainer information:
Also remmina is broken But doesn't seem to depend on pango directly, so unsure which dependency actually is broken
Here's an issue for pangox-compat
Lutris is broken too - not an urgent requirement but just making you fine folks aware!
Not sure why Lutris is broken, but Lutris-unwrap is fine.
It's a failure in the dependency chain, in this case .
no longer depends on on its master branch: We should probably switch to that. should not be needed in according to the README in , I suspect it was only there because we did not propagate it until ebassi also suggests switching to HEAD and says we need not worry about ABI changes:
Not having pangox_compat fixed is definitively still an issue. Can this be re-opened?
After , the only program depending on this is anydesk and openmodelica which is broken.
So it breaks anydesk thus either we mark anydesk as broken or we fix that?
Anydesk shouldn't use this deprecated library. Yes, we can mark it as broken.


Question: mkdir -p "$doc" export SAGE_DOC="$doc" export SAGE_DOCBUILD_OPTS="--no-pdf-links -k" <ins> '' + stdenv.lib.optionalString (!optimize) '' export SAGE_FAT_BINARY=yes </ins> ''; buildFlags = if (buildDocs) then "doc" else "build";

The recent changes seem to make sage crash when it tries to run some code using openblas (I think). I installed the sage derivation from the latest github repository. In the sage interpreter, run the following sage crashes with the following message: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(okideal): channels(root): nixpkgs:
Procedural: as it is , please specify the CPU model. Looks like the Sage build system had the idea to use somewhere… I.e. the local build could work. I wonder how feasible it is to find where Sage does it — the Sage derivation is allowed to rebuild a lot of dependencies because it is just too much pain to make it use the system versions.
Here is the output of lscpu
From the traceback it presumably crashes here: which is which indeed is an AMD-only instruction (MMX? thought that would be long obsolete by now...)
You were right. A local build works fine. Thanks for the help.
Thanks for your report. do we set to and give up?
This should be fixed by exporting (see ). I'm not quite ready to give up (even though it would probably be the healthier choice :grin:). I'm actually currently experimenting with doing it the "right way" and replacing the sage buildsytem with nix (with a mix of sage and system dependencies).
can you confirm that the latest binary works?
Sorry for the late answer. The binaries from the master branch seem to work. The initial crashes are gone and running gives only unrelated failures. Installing from still gives me the old, faulty binaries though.
Are you sure you updated the channel? What do you mean by "binaries from master"?
I meant that installing from the master branch of the git repository works. I was not aware that there is a difference between nixos-unstable and nixpkgs-unstable. The latter does not seem to include the fix yet. Installing from nixos-unstable works well. Thanks for your help.
Okay, I guess hydra is a bit overwhelmed by all the fixes for the upcoming release. Thanks for reporting.


Question: assert stdenv.isLinux; # better than `called with unexpected argument 'enableJavaFX'` mavenJdk.buildMavenPackage rec { pname = "cryptomator"; <del> version = "1.10.1"; </del> <ins> version = "1.11.0"; </ins> src = fetchFromGitHub { owner = "cryptomator"; repo = "cryptomator"; rev = version; <del> hash = "sha256-xhj7RUurBRq9ZIDAlcq7KyYGnLqc+vTjaf2VMNStpVQ"; </del> <ins> hash = "sha256-NMNlDEUpwKUywzhXhxlNX7NiE+6wOov2Yt8nTfbKTNI="; </ins> }; mvnParameters = "-Dmaven.test.skip=true"; <del> mvnHash = "sha256-XAIwKn8wMqILMQbg9wM4kHAaRSGWQaBx9AXQyJuUO5k="; </del> <ins> mvnHash = "sha256-jIHMUj7ZQFu4XAvWUywj4f0PbmLHGtU5VRG0ZuKm3mA="; </ins> preBuild = '' VERSION=${version}

In the vault options, vaults can only be mounted as . Steps to reproduce the behavior: cryptomator to a vault options the tab, the combo box does not contain a FUSE item Vaults can be mounted as FUSE volumes In the console output, cryptomator seems to have access to the fuse3 libs in its PATH: Full console output:
I think this might be related to It seems since they switched to the new fuse integration they only search a predefined number of paths. This is also consistent as the nix build of cryptomator works on non nixos linux.
I have the same issue. Does somebody have some workaraound yet? EDIT: so what I am currently doing, which is really not ideal, is just mounting the webdav directory with rclone, which, well, uses FUSE. so yeah rclone has no problems with using FUSE...
The fix for this is merged but not yet released It's in the 4.0.0 milestone of fuse-nio-adapter. I'm currently using the flapak version of Cryptomator.
thank you for the answer! i don't quite understand what is. Is it a dependency of ? Is there a way to manually fetch this so that it works? I'm gonna try the flatpak version of Cryptomator out, thanks for the hint. I actually tried out appimage, but that didn't change anything.
In the 1.11.0-beta2 release of cryptomator, vaults are able to be mounted as FUSE volumes. So once 1.11.0 is fully released (and the nixpkgs version updated), this issue should be fixed. Until the new version of cryptomator is released, you could create an overlay to use the beta version, like I am doing at the moment. Apart from changing the version and hashes, I also needed to change the jdk used to a jdk21 and overriding it to enable JavaFX:
thank you for your response! i hope i am not rude to ask for your help in achieving this myself. i put the following in my : and i also did the overlay.


Question: assert stdenv.isLinux; # better than `called with unexpected argument 'enableJavaFX'` mavenJdk.buildMavenPackage rec { pname = "cryptomator"; <del> version = "1.10.1"; </del> <ins> version = "1.11.0"; </ins> src = fetchFromGitHub { owner = "cryptomator"; repo = "cryptomator"; rev = version; <del> hash = "sha256-xhj7RUurBRq9ZIDAlcq7KyYGnLqc+vTjaf2VMNStpVQ"; </del> <ins> hash = "sha256-NMNlDEUpwKUywzhXhxlNX7NiE+6wOov2Yt8nTfbKTNI="; </ins> }; mvnParameters = "-Dmaven.test.skip=true"; <del> mvnHash = "sha256-XAIwKn8wMqILMQbg9wM4kHAaRSGWQaBx9AXQyJuUO5k="; </del> <ins> mvnHash = "sha256-jIHMUj7ZQFu4XAvWUywj4f0PbmLHGtU5VRG0ZuKm3mA="; </ins> preBuild = '' VERSION=${version}

i get the following error when building: haven't been able to successfully find a solution via search engines...
For overlays, I simply copy the nix files and doing the following overlay: This is quite crude, and there is probably a better way to do it, but it at least avoids any weird errors like the one you are having.


Question: ++ lib.optionals enableTesseract [ tesseract leptonica ] ++ lib.optional enableTbb tbb ++ lib.optionals enableCuda [ cudatoolkit nvidia-optical-flow-sdk ] <del> ++ lib.optionals stdenv.isDarwin [ bzip2 AVFoundation Cocoa VideoDecodeAcceleration ] </del> <ins> ++ lib.optionals stdenv.isDarwin [ bzip2 AVFoundation Cocoa VideoDecodeAcceleration CoreMedia MediaToolbox ] </ins> ++ lib.optionals enableDocs [ doxygen graphviz-nox ]; propagatedBuildInputs = lib.optional enablePython pythonPackages.numpy;

Describe the issue In the opencv build for mac, why is off by default? What needs to be done to enable it? (either development work, dependencies that aren't yet nixpkgs, or, if possible, how to manually override the argument and simply set to ) To Reproduce See above Expected behavior There may be a good reason it's disabled, so I can't say that I'd expect videoio to be enabled by default. Notify maintainers Metadata Please run and paste the result. Maintainer information:
It was removed here 15 months ago: See this PR: due to apple removing most of QTkit in 10.12 Brew does not use this option. You can use an overlay or a nixpkgs checkout with this patch to build with videoio The following will drop you into a nix-shell with the patched opencv, which you can use for testing. I'm not sure if it builds. FWIW, I get the following build failure which indicates the upstream issue might not be resolved, or we're missing some thing in our derivation.
I was originally attempting to use an overlay. After getting nowhere, I made a , which is what redirected me to the nix build. So if you want to help me close that thread, that'd be awesome cause both me and the person that helped me still don't know how to access/change the from an overlay.


Question: src = fetchFromGitHub { owner = "rstudio"; repo = "rstudio"; <del> rev = version; </del> <ins> rev = "v${version}"; </ins> sha256 = "sha256-9c1bNsf8kJjpcZ2cMV/pPNtXQkFOntX29a1cdnXpllE="; };

RStudio () fails to build from nixpkgs master with a 404 on downloading sources. Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Maintainer information:


Question: <ins> { lib , stdenv , git , git-lfs , fetchurl , wrapGAppsHook3 , alsa-lib , at-spi2-atk , cairo , cups , dbus , expat , gdk-pixbuf , glib , gtk3 , mesa , nss , nspr , xorg , libdrm , libsecret , libxkbcommon , pango , systemd , hunspellDicts , useHunspell ? true , languages ? [ "en_US" ] , withNemoAction ? true , makeDesktopItem , copyDesktopItems , asar , python3 }: let pname = "pulsar"; version = "1.117.0"; sourcesPath = { x86_64-linux.tarname = "Linux.${pname}-${version}.tar.gz"; x86_64-linux.hash = "sha256-iDQV4wcb+TY5qv8X6UW6PumK9+i5cn705ZzCSx5VgMs="; aarch64-linux.tarname = "ARM.Linux.${pname}-${version}-arm64.tar.gz"; aarch64-linux.hash = "sha256-NJc6CQA7ZCX70ui+QcVcLW2qxM05A93yqpiiW+YosGc="; }.${stdenv.hostPlatform.system} or (throw "Unsupported system: ${stdenv.hostPlatform.system}"); newLibpath = lib.makeLibraryPath [ alsa-lib at-spi2-atk cairo cups dbus expat gdk-pixbuf glib gtk3 libsecret mesa nss nspr libdrm xorg.libX11 xorg.libxcb xorg.libXcomposite xorg.libXdamage xorg.libXext xorg.libXfixes xorg.libXrandr xorg.libxshmfence libxkbcommon xorg.libxkbfile pango stdenv.cc.cc.lib systemd ]; # Hunspell hunspellDirs = builtins.map (lang: "${hunspellDicts.${lang}}/share/hunspell") languages; hunspellTargetDirs = "$out/opt/Pulsar/resources/app.asar.unpacked/node_modules/spellchecker/vendor/hunspell_dictionaries"; hunspellCopyCommands = lib.concatMapStringsSep "n" (lang: "cp -r ${lang}/* ${hunspellTargetDirs};") hunspellDirs; in stdenv.mkDerivation rec { inherit pname version; src = with sourcesPath; fetchurl { url = "https://github.com/pulsar-edit/pulsar/releases/download/v${version}/${tarname}"; inherit hash; }; patches = [ ./001-patch-wrapper.patch ]; nativeBuildInputs = [ wrapGAppsHook3 copyDesktopItems asar ]; buildInputs = [ gtk3 xorg.libxkbfile ]; dontBuild = true; dontConfigure = true; installPhase = '' runHook preInstall mkdir -p $out/opt/Pulsar mv * $out/opt/Pulsar runHook postInstall ''; preFixup = '' gappsWrapperArgs+=( # needed for gio executable to be able to delete files --prefix "PATH" : "${lib.makeBinPath [ glib ]}" ) '' + lib.optionalString useHunspell '' # On all platforms, we must inject our dictionnaries ${hunspellCopyCommands} ''; postFixup = '' opt=$out/opt/Pulsar # Patch the prebuilt binaries patchelf --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  --set-rpath "${newLibpath}:$opt"  --add-needed libffmpeg.so  --add-needed libxshmfence.so.1  --add-needed libxkbcommon.so.0  --add-needed libxkbfile.so.1  --add-needed libsecret-1.so.0  $opt/pulsar patchelf --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  --set-rpath "${newLibpath}"  $opt/resources/app/ppm/bin/node patchelf --set-interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  $opt/resources/app.asar.unpacked/node_modules/symbol-provider-ctags/vendor/ctags-linux # Replace the bundled git with the one from nixpkgs dugite=$opt/resources/app.asar.unpacked/node_modules/dugite rm -f $dugite/git/bin/git ln -s ${git}/bin/git $dugite/git/bin/git # Not only do we need to replace the git binary itself, we also need to replace # all the symlinks in dugite/git/libexec/git-core. for file in "$dugite/git/libexec/git-core"/*; do if [ -x "$file" ] && file "$file" | grep -q "ELF"; then # Remove ELF executable rm "$file" # Get the corresponding filename in nixpkgs's git filename=$(basename "$file") git_executable="${git}/libexec/git-core/$filename" # Create symlink to $git_executable ln -s "$git_executable" "$file" echo "Replaced $file with symlink to $git_executable" fi done # Was symlinked in previous loop, but actually, nixpkgs has a separate package for git-lfs # Unlink to avoid a "File exists" error and relink correctly unlink $dugite/git/libexec/git-core/git-lfs ln -s ${git-lfs}/bin/git-lfs $dugite/git/libexec/git-core/git-lfs '' + lib.optionalString (stdenv.hostPlatform.system == "x86_64-linux") '' # We have to patch a prebuilt binary in the asar archive # But asar complains because the node_gyp unpacked dependency uses a prebuilt Python3 itself rm $opt/resources/app.asar.unpacked/node_modules/tree-sitter-bash/build/node_gyp_bins/python3 ln -s ${python3.interpreter} $opt/resources/app.asar.unpacked/node_modules/tree-sitter-bash/build/node_gyp_bins/python3 '' + '' # Patch the bundled node executables find $opt -name "*.node" -exec patchelf --set-rpath "${newLibpath}:$opt" {} ; # Also patch the node executable for apm patchelf --set-rpath "${newLibpath}:$opt" $opt/resources/app/ppm/bin/node # The pre-packaged ASAR bundle comes with prebuild binaries, expecting libstdc++.so.6 asarBundle=$TMPDIR/asarbundle asar e $opt/resources/app.asar $asarBundle find $asarBundle -name "*.node" -exec patchelf --set-rpath "${newLibpath}:$opt" --add-needed libstdc++.so.6 {} ; unlink $asarBundle/node_modules/document-register-element/dre # Self referencing symlink, breaking asar rebundling asar p $asarBundle $opt/resources/app.asar rm -rf $asarBundle # We have patched the original wrapper, but now it needs the "PULSAR_PATH" env var mkdir -p $out/bin wrapProgram $opt/resources/pulsar.sh  --prefix "PULSAR_PATH" : "$opt/pulsar" ln -s $opt/resources/pulsar.sh $out/bin/pulsar ln -s $opt/resources/app/ppm/bin/apm $out/bin/ppm # Copy the icons mkdir -p $out/share/icons/hicolor/scalable/apps $out/share/icons/hicolor/1024x1024/apps cp $opt/resources/pulsar.svg $out/share/icons/hicolor/scalable/apps/pulsar.svg cp $opt/resources/pulsar.png $out/share/icons/hicolor/1024x1024/apps/pulsar.png '' + lib.optionalString withNemoAction '' # Copy the nemo action file mkdir -p $out/share/nemo/actions cp ${./pulsar.nemo_action} $out/share/nemo/actions/pulsar.nemo_action ''; desktopItems = [ (makeDesktopItem { name = "Pulsar"; desktopName = "Pulsar"; exec = "pulsar"; icon = "pulsar"; comment = "A Community-led Hyper-Hackable Text Editor"; genericName = "Text Editor"; categories = [ "Development" "TextEditor" "Utility" ]; mimeTypes = [ "text/plain" ]; }) ]; passthru.updateScript = ./update.mjs; meta = { description = "A Community-led Hyper-Hackable Text Editor"; longDescription = '' A Community-led Hyper-Hackable Text Editor, Forked from Atom, built on Electron. Designed to be deeply customizable, but still approachable using the default configuration. ''; homepage = "https://github.com/pulsar-edit/pulsar"; sourceProvenance = with lib.sourceTypes; [ binaryNativeCode ]; license = lib.licenses.mit; platforms = lib.platforms.linux; maintainers = with lib.maintainers; [ bryango ]; knownVulnerabilities = [ "CVE-2023-5217" "CVE-2022-21718" "CVE-2022-29247" "CVE-2022-29257" "CVE-2022-36077" "CVE-2023-29198" "CVE-2023-39956" ]; }; } </ins>

Package name: pulsar Latest released version: 1.117.0 Current version on the unstable channel: 1.114.0 Current version on the stable/release channel: 1.117.0 Notify maintainers


Question: patches = [ ./sw_vers_root5.patch <del> (fetchpatch { name = "enable_new_gcc.patch"; url = "https://aur.archlinux.org/cgit/aur.git/plain/enable_new_gcc.patch?h=root5&id=91c50876081a0af36f84ec4f0f9dba869107fa4f"; sha256 = "1rnp0xlw0yqi7mjs4w145njd79i8kkir1qik7zwicdik9axf8ygm"; }) </del> # prevents rootcint from looking in /usr/includes and such ./purify_include_paths_root5.patch

, CVSSv3=8.8 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc


Question: ''; postFixup = '' <del> makeWrapper ${electron}/bin/electron $out/bin/${pname}  </del> <ins> makeWrapper ${electron_11}/bin/electron $out/bin/${pname}  </ins> --add-flags $out/share/${pname}/resources/app.asar  --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ stdenv.cc.cc libsecret ]}" '';

Describe the bug After electron 12 came out, adding in home-manager succeeds, but trying to start the app fails mentioning a missing javascript function from an older version of electron. To Reproduce Steps to reproduce the behavior: to home-manager's app from terminal with Expected behavior Expected the application start as it had before. Additional context I was able to get it working locally by providing an overlay to home-manager: I would have created a PR myself, but I'm still new to nix and not sure entirely how to require a different electron version in the package derivation. Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(jon): nixpkgs: Maintainer information:
thanks for catching this! Just fixed in the PR above.


Question: (buildGoModule { inherit pname version src; <ins> patches = lib.optionals (projectName == "apptainer") [ (substituteAll { src = ./apptainer/0001-ldCache-patch-for-driverLink.patch; inherit (addDriverRunpath) driverLink; }) ]; </ins> # Override vendorHash with the output got from # nix-prefetch -E "{ sha256 }: ((import ./. { }).apptainer.override { vendorHash = sha256; }).goModules" # or with `null` when using vendored source tarball.

singularity cannot use nvidia gpu because it does not access 'nvidia-container-cli' Steps to reproduce the behavior: return result of ! This is because the path is not listed in , as also in a. It is caused by neither the option nor . I tried to handle it with override, but since it was called in , I think it is impossible to handle. Also, I created a conf file in as shown in the singularity docs, but it was not read. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result.
Thank you for reporting and sorry for the trouble. I'll look at the SingularityCE documentation again. (Those configuration options has been deprecated by Apptainer.) Also, I created a conf file in /usr/local/etc/singularity/ as shown in the singularity docs, but it was not read.  shold be what you are looking for. The overriden package can be assigned to . (If you would like to bypass all the overriding done by the module and directly specify the package to install for some special reason, you can assign it to .)
Thanks for the reply. I followed your advice and tried the override and was able to use the GPU. Here is the code This is simply adding a process to append the nvidia-docker path to the I mentioned earlier that when conf was entered in , it was not reflected, and the same is true for '/etc/singularity'. I referred to .
At least we have confirmed that in works and the path is replaced by , but the product does not seem to be recognizable.
Does setting the to make ldconfig search in help? This is modified from the configuration proposed by (). There's also (probably) related to this topic.
Adding the path of to works well. This once removed from consideration. Next we have a patched version of ldconfig. This does not append the path of to the config. The result was an error that could not be found, and it could not be started.
Oh, I already forgot about this issue. Absolutely coincidentally, but maybe efforts such as might open up a way to implement this hack more reliably.


Question: (buildGoModule { inherit pname version src; <ins> patches = lib.optionals (projectName == "apptainer") [ (substituteAll { src = ./apptainer/0001-ldCache-patch-for-driverLink.patch; inherit (addDriverRunpath) driverLink; }) ]; </ins> # Override vendorHash with the output got from # nix-prefetch -E "{ sha256 }: ((import ./. { }).apptainer.override { vendorHash = sha256; }).goModules" # or with `null` when using vendored source tarball.

Meanwhile, in my config I'm still abusing You probably already have guessed, but singularity in nixpkgs is configured to read this config from the package-specific directory, rather than from the global . You could in principle override this behaviour, but there maybe isn't much value in supporting that
I tried to enable the use of external sysconfdir (), but have encountered issue trying to specify a directory under with the NixOS module ().
Have you tried to apply both at the same time?
The SingularityCE Admin Guide says If the value of nvidia-container-cli path is empty, SingularityCE will look for the binary on $PATH at runtime. It should work as long as is found in the run-time , even when is not set. As nvidia-container-cli is alredy included in the PATH-prefixing wrapper, we shouldn't have to set the .
Update: I found a bug in the prefixed PATH of the wrapper introduced in . The prefixing should be specified as (in Bash) I forgot to add , causing the trailing to be missing.
The statement in the SingularityCE Admin Guide turns out to be wrong / irrelevant. The source code clearly states that nvidia-container-cli will only be read from the configuration.
(we need to patch nvidia-container-cli, for many reasons )
Eh, actually, closed semi-automatically. Apptainer with is fixed (on NixOS), but not with . The fix doesn't concern singularity-ce either, unfortunately. Shouldn't be hard to make this work with singularity too, but I'm out of bandwidth
Hi folks, I've been trying to get apptainer to run this (which I've done previously successfully with a slight ldconfig hack -- that doesn't work anymore -- on NixOS 22.11), that will make use of the machine's Tesla V100 to do some simulation stuff. The machine is running NixOS 23.11. Using the workaround from 9th of May post further up, I was able to get past the ldconfig issue, but now I'm getting an error saying the driver and CUDA are not in sync.


Question: (buildGoModule { inherit pname version src; <ins> patches = lib.optionals (projectName == "apptainer") [ (substituteAll { src = ./apptainer/0001-ldCache-patch-for-driverLink.patch; inherit (addDriverRunpath) driverLink; }) ]; </ins> # Override vendorHash with the output got from # nix-prefetch -E "{ sha256 }: ((import ./. { }).apptainer.override { vendorHash = sha256; }).goModules" # or with `null` when using vendored source tarball.

Before I start posting any details (I don't want to re-open this issue, but I'm also not sure if I'm just doing something wrong) I was wondering if the current implementation of singularity/apptainer on NixOS is expected to work, and I'm just being an idiot, or if there are known breaking issues? I've seen the other issues about singularity/apptainer here, but I'm not knowledgeable enough to make a judgement call if they are responsible for my problem or not. Thanks very much in advance!
(If I understood the message correctly) That usually means you need a reboot, and you should experience the same issue outside the container
No, the reboot didn't help either. For some reason, though, after upgrading to 24.05, everything "just works[tm]" again. So, whatever the issue was, thanks for fixing it (probably)! :)
Thanks to Nixpkgs 24.05 includes GPU-related changes/fixes to the package and the module.
Well more like thanks to ShamrockLee


Question: <del> { mkDerivation, lib, stdenv, fetchurl, cmake, extra-cmake-modules </del> <ins> { mkDerivation, lib, stdenv, makeWrapper, fetchurl, cmake, extra-cmake-modules </ins> , karchive, kconfig, kwidgetsaddons, kcompletion, kcoreaddons , kguiaddons, ki18n, kitemmodels, kitemviews, kwindowsystem , kio, kcrash

the python binding for krita are not build correctly. Please run and paste the results.
more details wouldn't hurt...
well I don't exactly know what is happening here, to build the python binding, it requires and . So when are to the buildInputs, cmake finds all the dependencies correctly; however, at around 98% the compilation fails due to not finding some sip bindings. Alternatively, if is to the buildInputs, everything works fine as intended. But the python interpreter overwrite the python interpreter in the nix-env, so that doesn't seem to be the right fix.
also tried setting the variable, but that didn't work either.
cc who worked on / in


Question: https://git.sr.ht/~whynothugo/lsp_lines.nvim hura/vim-asymptote iamcco/coc-spell-checker <ins> iamcco/coc-tailwindcss </ins> iamcco/markdown-preview.nvim ianks/vim-tsx idanarye/vim-merginal

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


Question: index e2d292e..b13c0db 100755 --- a/configure +++ b/configure <del> @@ -2880,6 +2880,7 @@ $MAKE </del> <ins> @@ -3874,6 +3874,7 @@ </ins> echo "building the hdf5 library..."; cd ../; <del> ## we add the '-w' flag to suppress all the warnings hdf5 prints </del> +sed -i 's#/bin/mv#mv#' configure <del> ./configure --with-pic --enable-shared=no --enable-cxx  --with-szlib  CXX="${CXX}" CXFLAGS="${CXXFLAGS} -w"  </del> <ins> ./configure --with-pic --enable-shared=no --enable-cxx --enable-hl  --with-szlib=${SZIP_HOME} --with-zlib=${ZLIB_HOME}  ${WITH_S3_VFD}  </ins>

Describe the bug The rhdf5 library does not work on latest release. To Reproduce Expected behavior A shell with R and rhdf5. Additional context Instead I get: Notify maintainers Metadata Maintainer information:
"6.topic: rust" should be removed, this is an R package, not Rust.
This was fixed in


Question: maintainers = [ globin eqyiel ]; }; <del> nodes = { </del> <ins> nodes = rec { </ins> # The only thing the client needs to do is download a file. client = { ... }: { services.davfs2.enable = true;

There is about the use of imagemagick in NextCloud due to . Admins may want to disable it unless they are certain that users won't upload untrusted files (which can easily happen by accident if folder sync is active). NextCloud is only passing certain file types to imagemagick but it is doing so based on the file extension. Therefore, an attacker can pass any file type to imagemagick. I have tested this with a PNM image (not supported by NextCloud) that I have renamed to . doesn't get a preview image but does, i.e. NextCloud thinks it is HEIF and passes it to ImageMagick, which processes it as PNM. There are several ways to disable imagick: in the NextCloud config. This will not only disable imagick but also previews for PNG and JPEG (which do not use imagick). in the NextCloud config. This may need manual adjustment after a NextCloud update. the extension for PHP. This also disables it for NextCloud plugins. Option 1 and 2 can already be used by an admin if the drawbacks are acceptable. However, I think 3 is the best option in most cases. has options that disable the other PHP extensions that used to be by default. I think we should do the same for imagick. If imagick is disabled, NextCloud will automatically disable the preview generators that need it. It will also show a warning about that (which is subject to debate in the issue linked above) and there may be some implications for the themes app (which I don't use). Therefore, I think we should keep imagick enabled by default and leave the decision to the admin. We could also add a suitable policy for ImageMagick and thereby disable any file formats or features that are considered insecure. I don't think I could write such a policy and be sure that it is secure (or even "secure enough"). In addition, we will have to keep it up-to-date with newer versions and CVEs. That is why I recommend that we only add a simple off switch. The above information is based on NextCloud 20. I will wait until and NextCloud 21 have landed in nixos-unstable (and on my server) and then test again and create a PR if there is any interest in having this upstream.


Question: maintainers = [ globin eqyiel ]; }; <del> nodes = { </del> <ins> nodes = rec { </ins> # The only thing the client needs to do is download a file. client = { ... }: { services.davfs2.enable = true;

Ouch, decisions based purely on a file ext is a behavior that sounds pretty broken to me :/ Optiobally disabling imagemagick and adjusting the config accordingly sounds reasonable to me, so feel free to file a PR. You can ping me for a review or if you need assistance with modifying the module :)
It's ok for what they do with it. It won't do double duty as a mitigation but I guess that was never intended. Thanks. Any suggestions on a name for the new option? Simply ? Should I add any tests for that? The existing tests only test three different configurations so adding one just for imagick seems like overkill. It should be quite easy though. If we want to test that previews actually aren't generated... Well, that's a different story. We would have to automate the web interface, for that. I think the existing tests are only testing the service, CLI and WebDAV.
As imagemagick enabled will remain the default, I'd suggest . Yes, adding a fourth VM test just for imagemagick is indeed an overkill IMHO since those tend to be fairly expensive. I'd suggest to write a testcase in , other integrations such as are also tested there. Right that could be a non-trivial thing to solve. Maybe check if there's a REST API or a way to implement this with the CLI of . But I don't think it'd be worth spending too much time on this if there's no reasonable way to test :)
I think we still want to test the default option in so we will need a second configuration that disables imagick. We don't have to start that VM if we only want to check whether imagick is in its closure. As there isn't any test helper for that, we probably don't want to do that though ;-) see Unfortunately, qemu on ARM is too unreliable for the automatic tests because qemu crashes when started on one of the little cores (i.e. 4 out of 6 times). I have done some interactive testing of the above commit but not an automated run. I will have to find some system that is not ARM, not high-security, not already virtualized...
Qemu/KVM does work if a kernel build or stress-ng is hogging the big cores :) is ready for review.


Question: <command>nixos-rebuild switch</command>. </para> <del> <xi:include href="customizing-packages.xml" /> </del> <ins> <xi:include href="../from_md/configuration/customizing-packages.section.xml" /> </ins> <del> <xi:include href="adding-custom-packages.xml" /> </del> <ins> <xi:include href="../from_md/configuration/adding-custom-packages.section.xml" /> </ins> </section>

This tracks the conversion of from DocBook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.


Question: <command>nixos-rebuild switch</command>. </para> <del> <xi:include href="customizing-packages.xml" /> </del> <ins> <xi:include href="../from_md/configuration/customizing-packages.section.xml" /> </ins> <del> <xi:include href="adding-custom-packages.xml" /> </del> <ins> <xi:include href="../from_md/configuration/adding-custom-packages.section.xml" /> </ins> </section>

This tracks the conversion of from Docbook to CommonMark per . here that you intend to work on this. (Please also post if you stop working on this.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections in the NixOS and Nixpkgs manual for inspiration. the CommonMark back to DocBook xml with: from nixpkgs root dir with: a preview server with: your work at on steps 5-9. it looks good, commit both the new file and the generated file, submit a PR and reference this issue.
I opened a PR for and : PTAL, thanks in advance for reviewing :-)


Question: <ins> { pkgs, buildGoModule, fetchFromGitHub, lib, perl }: buildGoModule rec { pname = "XD"; version = "0.4.0"; src = fetchFromGitHub { owner = "majestrate"; repo = "XD"; rev = "v${version}"; sha256 = "sha256-fXENoqhR04TYS/kAJUqsqa0+j+KyzdsMlXIZ2GMPMhc="; }; vendorSha256 = "1wg3cym2rwrhjsqlgd38l8mdq5alccz808465117n3vyga9m35lq"; checkInputs = [ perl ]; postInstall = '' ln -s $out/bin/XD $out/bin/XD-CLI ''; meta = with lib; { description = "i2p bittorrent client"; homepage = "https://xd-torrent.github.io"; maintainers = with maintainers; [ nixbitcoin ]; license = licenses.mit; platforms = platforms.linux; }; } </ins>

Project description homepage URL: https://xd- source URL: license: mit platforms: linux
I marked this as stale due to inactivity. →


Question: <del> From 44c2c979c4f2222567ce65f506cf47fb87482348 Mon Sep 17 00:00:00 2001 From: Pontus Stenetorp <pontus@stenetorp.se> Date: Thu, 8 Apr 2021 04:37:44 +0000 Subject: [PATCH 5/6] nix: Enable parallel unit tests for sandbox Disabled by default due to lack of networking in the Nix sandbox. This greatly speeds up the build process on a multi-core system. --- test/runtests.jl | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/test/runtests.jl b/test/runtests.jl index 2f9cd058bb..2f8c19fa32 100644 --- a/test/runtests.jl +++ b/test/runtests.jl @@ -83,8 +83,9 @@ prepend!(tests, linalg_tests) import LinearAlgebra cd(@__DIR__) do n = 1 -    if net_on -        n = min(Sys.CPU_THREADS, length(tests)) +    if net_on || haskey(ENV, "NIX_BUILD_CORES") +        x = haskey(ENV, "NIX_BUILD_CORES") ? parse(Int, ENV["NIX_BUILD_CORES"]) : Sys.CPU_THREADS +        n = min(x, Sys.CPU_THREADS, length(tests)) n > 1 && addprocs_with_testenv(n) LinearAlgebra.BLAS.set_num_threads(1) end -- 2.29.3 </del>

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


Question: dontDisableStatic = withStatic; <ins> # libusb-1.0.rc:11: fatal error: opening dependency file .deps/libusb-1.0.Tpo: No such file or directory dontAddDisableDepTrack = stdenv.hostPlatform.isWindows; </ins> configureFlags = lib.optional (!enableUdev) "--disable-udev" ++ lib.optional (withExamples) "--enable-examples-build";

Steps to reproduce the behavior: So when I wanted to dig deeper, with I'm trying to recreate with a toolchain that's on hydra so I don't have to compile GCC for myself (twice!) Please run and paste the result. In particular, is pinned to:
Diff-ing the two files, I get: I suspect the problem comes from in the that isn't present in the . I wonder why so many differences are present though? I've confirmed this by adding to the derivation, but again why are the differences present? Even if they have been helpful to track this down
I suspect there were impurities in your environment but the difference is still weird. I don't know why would be there but not Adding to the mingw build in


Question: wrapQtAppsHook ]; <del> buildInputs = [ qtsvg ]; </del> <ins> buildInputs = [ qtbase qtwayland qtsvg ]; </ins> postInstall = lib.optionalString stdenv.isDarwin '' mkdir -p $out/Applications

low priority qt6.qtdeclarative is a large package, so it should be excluded for non-GUI qt apps () currently, when i build a package with and empty buildInputs, it pulls qt6.qtwayland qt6.qtdeclarative qt6.qtshadertools the problem is wrapQtAppsHook and its deps and qtwayland pulls qtdeclarative the problem is fixed by removing from deps wrapQtAppsHook should use only the declared buildInputs disabling wrapQtAppsHook (dontWrapQtApps = true) is no option, as also CLI qt apps need the qt wrapper qtwayland is there, so that users dont need to add it to buildInputs assuming that all qt apps are GUI apps im in favor of making this consistent with cmake so that all GUI apps must add qtwayland to buildInputs CLI qt app: GUI qt app: since cc
I'm in favour of this change, but the proportion of qt cli app night be relatively small, and it's not immediately clear that qtwayland should be if the build log yields Qt6::Widgets is missing.
Actually we are abusing qtwayland as a shortcut to bringing in qtdeclarative, this should be fixed too.
we could patch the cmake message to "please add qtdeclarative to your propagatedBuildInputs" the alternative would be to add a flag, but thats more obscure than buildInputs
Adding the lines to nixpkgs manual is sufficient.
By the way, is not only needed to pull in , but it's required for all GUI apps so that they work seamlessly on X11 or Wayland.


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

Fail to connect to a l2tp + ipsec VPN after putting in all information. This happens on both Latest Gnome ISO and after NixOS installation. Message received on Gnome Desktop: Connection Failed Activation of network connection failed Steps to reproduce the behavior: Live Gnome ISO. l2tp + ipsec (strongswan) details in NetworkManager. on VPN connection. There are several fixes listed in this issue I was able to fix the problem by creating the file AFTER creating the connection and failing to connect once. (I also created the file BEFORE creating the connection, but that did not fix the issue.) After successfully connecting, this was content of file include The following is the failure output from journalctl From ISO system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I was also having issues and tried the above suggested by and was able to connect only after a failed connection !
This seems to fix the bug May we have this to the default package?
Fix in


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

Phew, a big title! Trying to write down as much as I can before I forget. First, the last part: If doesn't exist, will show failing like: fixes this problem. NixOS should probably create this file. I'm not sure if this file should be writable or not, when it exists, I have only ever seen it contain: I don't know what writes that there. Now for can't edit L2TP VPNs, but (GUI) can, even though nm-applet doesn't work under sway. If you see this in the system logs: try enabling "legacy proposals" in nm-connection-editor's IPSec Settings and try again. system: host os: multi-user?: sandbox: version: channels(root): channels(grahamc): nixpkgs:
Side note, how do I know for sure fixes it? I erased my dozens of times nailing it down, reproducing it to exactly this.
I think the strongswan module creates that file and the actual L2TP plugin appends that line to this file.
Nice find that the strongswan module does create that file! I don't have the strongswan module enabled, it seems something else in the stack would periodically create this file?
I'm not sure what does create it eventually, but it appears the plugin expects the file to exist so we should just do exactly that. It doesn't help that it expects it to be mutable, so maybe we can handle this within the NM module to add more secrets. Though it would probably duplicate what the strongswan module does.
^ does this make sense to you?
So I just remembered about this module I have: maybe instead we should have the networkmanager do when it detects the l2tp plugin but I am not sure how to do that. Maybe we would need to introduce a new option in networkmanager to add the nm-l2tp plugin and create the file. I tend to connect physically to the private network and only as a last resort rely to nm-l2tp since it tends to not work regularly and I am not sure if it's blocked by the network or some l2tp breakage.


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

We could add an option to networkmanager in the same way there's one for strongswan there
Was there ever any follow up on :
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
i guess, it's still relevant, maybe not so urgent. this helped me big time:
I marked this as stale due to inactivity. →
I just ran into this on 21.05. Seeing a log like this: <details<summaryjournalctl log when starting vpn</summary<pre<codecharon[2059]: 00[CFG] loading ca certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/cacerts' charon[2059]: 00[CFG] loading aa certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/aacerts' charon[2059]: 00[CFG] loading ocsp signer certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

d/ocspcerts' charon[2059]: 00[CFG] loading attribute certificates from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/acerts' charon[2059]: 00[CFG] loading crls from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.d/crls' charon[2059]: 00[CFG] loading secrets from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.secrets' charon[2059]: 00[CFG] expanding file expression '/etc/ipsec.secrets' failed charon[2059]: 00[CFG] opening triplet file /nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan- failed: No such file or directory charon[2059]: 00[CFG] loaded 0 RADIUS server configurations charon[2059]: 00[CFG] no script for ext-auth script defined,


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

disabled charon[2059]: 00[LIB] loaded plugins: charon unbound pkcs11 aesni aes des rc2 sha2 sha1 md5 mgf1 rdrand random nonce x509 revocation constraints acert pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey dnscert pem openssl af-alg fips-prf gmp curve25519 chapoly xcbc cmac hmac curl attr kernel-netlink resolve socket-default connmark forecast farp stroke vici updown eap-identity eap-sim eap-sim-pcsc eap-aka eap-aka-3gpp2 eap-simaka-pseudonym eap-simaka-reauth eap-md5 eap-gtc eap-mschapv2 eap-radius xauth-generic xauth-eap xauth-pam dhcp counters charon[2059]: 00[JOB] spawning 16 worker threads ipsecstarter[2058]: charon (2059) started after 660 ms charon[2059]: 11[CFG] received stroke: add connection '-ebef-4658-8991-' charon[2059]: 11[CFG] configuration '-ebef-4658-8991-' charon[2059]: 13[CFG] rereading secrets charon[2059]: 13[CFG] loading secrets from '/nix/store/va01sq5aqg6p7yakvpg2zlnsdj4pm9dj-strongswan-5.8.1/etc/ipsec.secrets' charon[2059]: 13[CFG] expanding file expression '/etc/ipsec.secrets' failed charon[2059]: 14[CFG] received stroke: initiate '-ebef-4658-8991-' charon[2059]: 15[IKE] initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111.111 charon[2059]: 15[IKE] initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111.


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

111 charon[2059]: 15[ENC] generating IDPROT request 0 [ SA V V V V V ] charon[2059]: 15[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (304 bytes) charon[2059]: 03[NET] received packet: from 123.111.111.111[500] to 192.168.1.11[500] (204 bytes) charon[2059]: 03[ENC] parsed IDPROT response 0 [ SA V V V V V V ] charon[2059]: 03[IKE] received NAT-T (RFC 3947) vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-03 vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-02n vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-02 vendor ID charon[2059]: 03[IKE] received draft-ietf-ipsec-nat-t-ike-00 vendor ID charon[2059]: 03[IKE] received DPD vendor ID charon[2059]: 03[CFG] selected proposal: IKE:AESCBC128/HMACSHA196/PRFHMACSHA1/MODP2048 charon[2059]: 03[ENC] generating IDPROT request 0 [ KE No NAT-D NAT-D ] charon[2059]: 03[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (372 bytes) charon[2059]: 04[NET] received packet: from 123.111.111.111[500] to 192.168.1.11[500] (356 bytes) charon[2059]: 04[ENC] parsed IDPROT response 0 [ KE No NAT-D NAT-D ] charon[2059]: 04[IKE] no shared key found for 192.168.1.11 - 123.111.111.


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

111 charon[2059]: 04[ENC] generating INFORMATIONALV1 request [ N(INVALKE) ] charon[2059]: 04[NET] sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (56 bytes) NetworkManager[2277]: initiating Main Mode IKESA -ebef-4658-8991-[1] to 123.111.111.111 NetworkManager[2277]: generating IDPROT request 0 [ SA V V V V V ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (304 bytes) NetworkManager[2277]: received packet: from 123.111.111.111[500] to 192.168.1.11[500] (204 bytes) NetworkManager[2277]: parsed IDPROT response 0 [ SA V V V V V V ] NetworkManager[2277]: received NAT-T (RFC 3947) vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-03 vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-02n vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-02 vendor ID NetworkManager[2277]: received draft-ietf-ipsec-nat-t-ike-00 vendor ID NetworkManager[2277]: received DPD vendor ID NetworkManager[2277]: selected proposal: IKE:AESCBC128/HMACSHA196/PRFHMACSHA1/MODP2048 NetworkManager[2277]: generating IDPROT request 0 [ KE No NAT-D NAT-D ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (372 bytes) NetworkManager[2277]: received packet: from 123.111.111.111[500] to 192.168.1.11[500] (356 bytes) NetworkManager[2277]: parsed IDPROT response 0 [ KE No NAT-D NAT-D ] NetworkManager[2277]: no shared key found for 192.168.1.11 - 123.111.111.


Question: }; <del> config = with cfg; let secretsFile = ipsecSecrets cfg.secrets; in mkIf enable </del> <ins> config = with cfg; mkIf enable </ins> { # here we should use the default strongswan ipsec.secrets and # append to it (default one is empty so not a pb for now) <del> environment.etc."ipsec.secrets".source = secretsFile; </del> <ins> environment.etc."ipsec.secrets".text = ipsecSecrets cfg.secrets; </ins> systemd.services.strongswan = { description = "strongSwan IPSec Service";

111 NetworkManager[2277]: generating INFORMATIONALV1 request [ N(INVALKE) ] NetworkManager[2277]: sending packet: from 192.168.1.11[500] to 123.111.111.111[500] (56 bytes) NetworkManager[2277]: establishing connection '-ebef-4658-8991-' failed NetworkManager[2283]: Stopping strongSwan IPsec. charon[2059]: 00[DMN] signal of type SIGINT received. Shutting down ipsecstarter[2058]: child 2059 (charon) has quit (exit code 0) ipsecstarter[2058]: ipsecstarter[2058]: charon stopped after 200 ms ipsecstarter[2058]: ipsec starter stopped nm-l2tp-service[2039]: gdbusmethodinvocationtake_error: assertion 'error != NULL' failed NetworkManager[954]: <warn[.6803] vpn-connection[0x24c60a0,-ebef-4658-8991-,"my-l2tp-vpn",0]: VPN connection: failed to connect: 'Message recipient disconnected from message bus without replying' .nm-applet-wrap[1470]: Failed to show notification: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Notifications was not provided by any .service files </pre</code</detailsRunning the following command fixed my error and allowed me to connect: The networking part of my only has .
This still appears relevant in 21.11. Adding this (as mentioned above) to my config appears to get an L2TP and IPSec VPN working with NetworkManager:
Still relevant in 22.05. I am confirming that with a clean install, trying to set up L2TP/IPsec VPNs fail with the following indicator: fixed the issue for me straight away as well.
Fix in


Question: <ins> From a642ad542e3d3f34e949c5c66923ca8a6e6cbbd8 Mon Sep 17 00:00:00 2001 From: Stig Palmquist <stig@stig.io> Date: Tue, 11 Jan 2022 13:23:13 +0100 Subject: [PATCH] test: fix support for gpgsm in gnupg 2.3 gpgsm --list-keys output changed the label for fingerprints from "fingerprint: " to "sha[12] fpr: " breaking tests with gnupg 2.3. this adds support for both. --- test/test-lib.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/test-lib.sh b/test/test-lib.sh index 6bc0b723..3de608f9 100644 --- a/test/test-lib.sh +++ b/test/test-lib.sh @@ -145,7 +145,7 @@ add_gpgsm_home () { mkdir -p -m 0700 "$GNUPGHOME" gpgsm --batch --no-tty --no-common-certs-import --pinentry-mode=loopback --passphrase-fd 3  --disable-dirmngr --import  >"$GNUPGHOME"/import.log 2>&1 3<<<'' <$NOTMUCH_SRCDIR/test/smime/0xE0972A47.p12 -    fpr=$(gpgsm --batch --list-key test_suite@notmuchmail.org | sed -n 's/.*fingerprint: //p') +    fpr=$(gpgsm --batch --list-key test_suite@notmuchmail.org | sed -n 's/.*(fingerprint|sha1 fpr): //p') echo "$fpr S relax" >> "$GNUPGHOME/trustlist.txt" gpgsm --quiet --batch --no-tty --no-common-certs-import --disable-dirmngr --import < $NOTMUCH_SRCDIR/test/smime/ca.crt echo "4D:E0:FF:63:C0:E9:EC:01:29:11:C8:7A:EE:DA:3A:9A:7F:6E:C1:0D S" >> "$GNUPGHOME/trustlist.txt" -- 2.34.1 </ins>

The build is failing on master; it has been reproduced at . An example of the failure is below: There is a new release () which also doesn't pass, so I didn't send the PR as it'd fail on CI. Steps to reproduce the behavior:
Those aren't the failing tests (BROKEN means they are known to fail). These are the real failures: Looks like a broken test directory setup in the build environment.
fixed in the next point release I think
prior work


Question: machine.succeed("curl -sSI http://localhost/api/tasks 2>&1 | grep '401 Unauthorized'") <ins> file_name = "test.txt" file_name_base64 = b64encode(file_name.encode('ascii')).decode('ascii') file_name_base64_urlencode = quote(file_name_base64) machine.succeed( f"echo Sample equipment manual > /tmp/{file_name}" ) machine.succeed( f"curl -sSf -X 'PUT' -b 'grocy_session={cookie}' " + f" 'http://localhost/api/files/equipmentmanuals/{file_name_base64_urlencode}' " + "  --header 'Accept: */*' " + "  --header 'Content-Type: application/octet-stream' " + f" --data-binary '@/tmp/{file_name}' " ) machine.succeed( f"curl -sSf -X 'GET' -b 'grocy_session={cookie}' " + f" 'http://localhost/api/files/equipmentmanuals/{file_name_base64_urlencode}' " + "  --header 'Accept: application/octet-stream' " + f" | cmp /tmp/{file_name}" ) </ins> machine.shutdown() ''; })

Grocy does not properly save manuals for equipment The issue appears to be introduced by in a patch applied by nixpkgs. Changing that hunk to: Fixes the issue. I'm not currently setup for making a PR, I'm a bit busy, but I wanted an issue for other people to find if they run into the problem. grocy in nixos configuration (admin/admin is default) a new piece of equipment and attach a PDF manual to it to download manual; it will fail system: host os: multi-user?: sandbox: version: channels(aidenn): channels(root): nixpkgs:
appears to be the maintainer.
I marked this as stale due to inactivity. →


Question: <ins> --- a/resources/pulsar.sh	2023-03-16 04:11:14.000000000 +0100 +++ b/resources/pulsar.sh	2023-03-24 14:37:13.468813964 +0100 @@ -123,7 +123,7 @@ elif [ $OS == 'Linux' ]; then SCRIPT=$(readlink -f "$0") -  PULSAR_PATH="/opt/Pulsar/pulsar" +  # PULSAR_PATH is set-up via `wrapProgram` in the postFixup phase #Set tmpdir only if tmpdir is unset : ${TMPDIR:=/tmp} </ins>

Package name: pulsar Latest released version: 1.117.0 Current version on the unstable channel: 1.114.0 Current version on the stable/release channel: 1.117.0 Notify maintainers


Question: inherit fontforge; }; <ins> lmmath = callPackage ../data/fonts/lmodern/lmmath.nix {}; </ins> lmodern = callPackage ../data/fonts/lmodern { }; manpages = callPackage ../data/documentation/man-pages { };

Describe the bug Thunderbird 78.2.1 is working. master (Thunderbird 78.2.2) has rendering issues (see screenshot). Most buttons do not react to clicks and the menu is also not reacting. To Reproduce Switch to the mentioned commit and rebuild. Expected behavior Normally working thunderbird. Screenshots ! Notify maintainers Metadata
This was also a bug in Ubuntu, it was fixed there with:
Upstream bug appears to be
Btw temporary workaround would be to switch to thunderbird-bin-78 if you are not opposed to binaries


Question: inherit fontforge; }; <ins> lmmath = callPackage ../data/fonts/lmodern/lmmath.nix {}; </ins> lmodern = callPackage ../data/fonts/lmodern { }; manpages = callPackage ../data/documentation/man-pages { };

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]:
might be fixed by confirmed. closing.
Hello. I'm new to NixOS, and also facing this problem: How can I apply that fix? I just updated my NixOS system flake to latest version: But still getting error during system rebuild:
try and update again, the fix is in unstable now.


Question: blinker certifi cachecontrol <ins> dep-logic </ins> findpython installer packaging

Steps to reproduce the behavior: truststore Output of : Adding to solves this issue. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: headsetcontrol = callPackage ../tools/audio/headsetcontrol { }; <ins> httm = callPackage ../tools/filesystems/httm { }; </ins> ksnip = libsForQt5.callPackage ../tools/misc/ksnip { }; license-generator = callPackage ../tools/misc/license-generator { };

Project description httm prints the size, date and corresponding locations of available unique versions (deduplicated by modify time and size) of files residing on ZFS snapshots, but can also be used interactively to view and restore such files. httm might change the way you use ZFS snapshots (because ZFS isn't designed for finding for unique file versions) or the Time Machine concept (because httm is very fast!). Metadata homepage URL: source URL: license: Mozilla Public License 2.0 platforms: unix, linux, darwin
Oh great thanks! Searched first but missed this.


Question: <ins> diff --git a/bin/nexus b/bin/nexus index d06cb44..37c606e 100755 --- a/bin/nexus +++ b/bin/nexus @@ -88,7 +88,7 @@ create_db_entry() { fi db_new_file=${db_file}_new if [ -f "$db_file" ]; then -    awk '$2 != "'"$test_dir"'" {print $0}' $db_file > $db_new_file +    awk '$2 != "'"$test_dir"'" {print $scriptname}' $db_file > $db_new_file rm "$db_file" mv "$db_new_file" "$db_file" fi @@ -246,7 +246,7 @@ read_vmoptions() { unpack_file() { if [ -f "$1" ]; then -    jar_file=`echo "$1" | awk '{ print substr($0,1,length-5) }'` +    jar_file=`echo "$1" | awk '{ print substr($scriptname,1,length-5) }'` bin/unpack200 -r "$1" "$jar_file" if [ $? -ne 0 ]; then @@ -377,9 +377,14 @@ fi old_pwd=`pwd` -progname=`basename "$0"` -linkdir=`dirname "$0"` +scriptname=$0 +if [ ! -z "$ALTERNATIVE_NAME" ]; then +  scriptname=`dirname "$0"`"/"$ALTERNATIVE_NAME +fi + +progname=`basename "$scriptname"` +linkdir=`dirname "$scriptname"` cd "$linkdir" prg="$progname" @@ -590,7 +595,7 @@ return_code=$? ;; *) -        echo "Usage: $0 {start|stop|run|run-redirect|status|restart|force-reload}" +        echo "Usage: $scriptname {start|stop|run|run-redirect|status|restart|force-reload}" exit 1 ;; esac </ins>

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


Question: libgeos_c = GEOS_LIBRARY_PATH; libc = lib.optionalString (!stdenv.isDarwin) "${stdenv.cc.libc}/lib/libc${stdenv.hostPlatform.extensions.sharedLibrary}.6"; }) <del> (fetchpatch { name = "fix-tests-geos-3.11.patch"; url = "https://github.com/shapely/shapely/commit/21c8e8a7909e7fb3cce6daa5c5b8284ac927fcb0.patch"; includes = [ "tests/test_parallel_offset.py" ]; sha256 = "sha256-85c8NlmAzzfCgepe/411ug5Sq+665dFMb3ySaUt9Kew="; }) </del> ]; preCheck = '' rm -r shapely # prevent import of local shapely ''; <del> disabledTests = [ "test_collection" </del> <ins> disabledTests = lib.optionals (stdenv.isDarwin && stdenv.isAarch64) [ # FIXME(lf-): these logging tests are broken, which is definitely our # fault. I've tried figuring out the cause and failed. # # It is apparently some sandbox or no-sandbox related thing on macOS only # though. "test_error_handler_exception" "test_error_handler" "test_info_handler" </ins> ]; pythonImportsCheck = [ "shapely" ];

Add any other context about the problem here. Please run and paste the result. repro'd on commit id
backtrace: <details<summaryBacktrace from lldb</summary</details
shapely 1.8.4 with the fix is now in pypi, I saw you wanted to upgrade it, did you get around to do it?
thanks for the reminder, committed it


Question: export inhibit_libc=true '' <del> # Trick to build a gcc that is capable of emitting shared libraries *without* having the # targetPlatform libc available beforehand.  Taken from: #   https://web.archive.org/web/20170222224855/http://frank.harvard.edu/~coldwell/toolchain/ #   https://web.archive.org/web/20170224235700/http://frank.harvard.edu/~coldwell/toolchain/t-linux.diff </del> + lib.optionalString (targetPlatform != hostPlatform && withoutTargetLibc && enableShared) <del> (let # crt{i,n}.o are the first and last (respectively) object file # linked when producing an executable.  Traditionally these # files are delivered as part of the C library, but on GNU # systems they are in fact built by GCC.  Since libgcc needs to # build before glibc, we can't wait for them to be copied by # glibc.  At this early pre-glibc stage these files sometimes # have different names. crtstuff-ofiles = if targetPlatform.isPower then "ecrti.o ecrtn.o ncrti.o ncrtn.o" else "crti.o crtn.o"; # Normally, `SHLIB_LC` is set to `-lc`, which means that # `libgcc_s.so` cannot be built until `libc.so` is available. # The assignment below clobbers this variable, removing the # `-lc`. # # On PowerPC we add `-mnewlib`, which means "libc has not been # built yet".  This causes libgcc's Makefile to use the # gcc-built `{e,n}crt{n,i}.o` instead of failing to find the # versions which have been repackaged in libc as `crt{n,i}.o` # SHLIB_LC = lib.optionalString targetPlatform.isPower "-mnewlib"; in '' echo 'libgcc.a: ${crtstuff-ofiles}' >> libgcc/Makefile.in echo 'SHLIB_LC=${SHLIB_LC}' >> libgcc/Makefile.in '') </del> <ins> (import ./libgcc-buildstuff.nix { inherit lib stdenv; }) </ins>

On or cross-compiled from , breaks: From : You can either run this on another architecture using . or should not crash: This was responsible for failing to replicate datasets to my ARM NAS. The issue does not_ occur for natively compiled builds. It appears to be a cross-compilation issue only.
It is a bug in / derivations. In non-cross cases it gets copied from used to bid into output: But in cross-case used to build does not yet provide as it needs bits of for it (and the library path is slightly incorrect). One of possible workarounds is to try to add to to get it pulled via from expected location.
We don't do the copying to glibc anymore, but this error still occurs as described on current nixpkgs master.
Yup. cross-compilation never propagated to in any form (and does not today).
Could you please try this PR? It should fix the problem.
With that PR, I'm seeing this on both (a Raspberry Pi CM4) and with QEMU on : Log from aarch64 machine: Log from machine with QEMU:
Well it's finding now, so there's clearly some other problem with addition to that. When I run it with I even get line numbers from inside : That line () is the last line in the following snippet of code: ... so is deliberately ing here due to . Grepping through the docs turns up: This is happening because uses . Once you do that, glibc needs to unwind the stack frame of any thread that calls . And unwinders are a giant headache. I'm afraid that's all I've got here. I've removed the closed-by from since it was only part of the problem here.
Ah, I think I know what it is. We can compile a without , but it won't have an unwinder. We need to pass the glibc headers to the build in order to get one of those.
would you please try ? I believe it fixes one of the two problems which caused this issue, and it includes which fixes the other one. It works for me: BTW, this issue (cross-compile , then run it under qemu) is a really valuable test case. We really ought to add it to so Hydra will catch any regressions automatically.


Question: export inhibit_libc=true '' <del> # Trick to build a gcc that is capable of emitting shared libraries *without* having the # targetPlatform libc available beforehand.  Taken from: #   https://web.archive.org/web/20170222224855/http://frank.harvard.edu/~coldwell/toolchain/ #   https://web.archive.org/web/20170224235700/http://frank.harvard.edu/~coldwell/toolchain/t-linux.diff </del> + lib.optionalString (targetPlatform != hostPlatform && withoutTargetLibc && enableShared) <del> (let # crt{i,n}.o are the first and last (respectively) object file # linked when producing an executable.  Traditionally these # files are delivered as part of the C library, but on GNU # systems they are in fact built by GCC.  Since libgcc needs to # build before glibc, we can't wait for them to be copied by # glibc.  At this early pre-glibc stage these files sometimes # have different names. crtstuff-ofiles = if targetPlatform.isPower then "ecrti.o ecrtn.o ncrti.o ncrtn.o" else "crti.o crtn.o"; # Normally, `SHLIB_LC` is set to `-lc`, which means that # `libgcc_s.so` cannot be built until `libc.so` is available. # The assignment below clobbers this variable, removing the # `-lc`. # # On PowerPC we add `-mnewlib`, which means "libc has not been # built yet".  This causes libgcc's Makefile to use the # gcc-built `{e,n}crt{n,i}.o` instead of failing to find the # versions which have been repackaged in libc as `crt{n,i}.o` # SHLIB_LC = lib.optionalString targetPlatform.isPower "-mnewlib"; in '' echo 'libgcc.a: ${crtstuff-ofiles}' >> libgcc/Makefile.in echo 'SHLIB_LC=${SHLIB_LC}' >> libgcc/Makefile.in '') </del> <ins> (import ./libgcc-buildstuff.nix { inherit lib stdenv; }) </ins>

Especially since the failure mode gives the user no error message to help them troubleshoot the problem! is a great candidate for this since it's one of those very rare non-C++ programs that uses advanced stack-unwinding features from pthreads.
Confirming fixes the issue. Tested with both and on real hardware and with QEMU on x86_64.
~I think this is fixed, and more cleanly,~ by Edit: it is not. :frowning_face: I will keep trying. Test is in Currently building.
Added this to , but commented out since it is not fixed yet.


Question: "INITRAMFS_DIR=${placeholder "out"}/etc/initramfs-tools" ] ++ lib.optional fuseSupport "BCACHEFS_FUSE=1"; <ins> env = { CARGO_BUILD_TARGET = stdenv.hostPlatform.rust.rustcTargetSpec; "CARGO_TARGET_${stdenv.hostPlatform.rust.cargoEnvVarTarget}_LINKER" = "${stdenv.cc.targetPrefix}cc"; }; </ins> # FIXME: Try enabling this once the default linux kernel is at least 6.7 doCheck = false; # needs bcachefs module loaded on builder

This is . Trying to build bcachefs-tools` for an aarch64-linux from x86_64-linux produces: I think comes from binutils. Adding binutils to nativeBuildInputs wasn't enough to fix it.
It's using a non-prefixed version of , it should instead be using
And after that we need to pass something like to cargo (or maybe directly to rustc?) somewhere. And we're spoiled for choice here: from in the Makefile to and env variables to maybe even .
I was able to fix this partially with this diff: That fixed the issue but seems like our libraries are incompatible? <details</details
Something has to be substituted in the source because ar is hardcoded
Applying that patch and adding The build now fails at
command encounters an error? Weird.
The built file is in instead of


Question: idea-ultimate = buildIdea rec { name = "idea-ultimate-${version}"; <del> version = "2019.3.4"; /* updated by script */ </del> <ins> version = "2020.1"; /* updated by script */ </ins> description = "Integrated Development Environment (IDE) by Jetbrains, requires paid license"; license = stdenv.lib.licenses.unfree; src = fetchurl { url = "https://download.jetbrains.com/idea/ideaIU-${version}-no-jbr.tar.gz"; <del> sha256 = "1i34kcd2j1xwx3l2sqc6jh3b69wqbxwwlq5yb7kf2ms9x4144bn0"; /* updated by script */ </del> <ins> sha256 = "0lrimmczl49azwsms56l4dg7himzr991a209r921jxa32rdjfq6x"; /* updated by script */ </ins> }; wmClass = "jetbrains-idea"; update-channel = "IntelliJ IDEA RELEASE";

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


Question: <del> { stdenv, lib, fetchFromGitHub, fetchpatch, fetchurl, cmake, ctags, swig # data, compression , bzip2, curl, hdf5, json_c, xz, lzo, protobuf, snappy # maths , blas, lapack, eigen, nlopt, lp_solve, colpack, glpk # libraries , libarchive, libxml2 # extra support , pythonSupport ? true, pythonPackages ? null , opencvSupport ? false, opencv ? null </del> <ins> { lib , stdenv , fetchFromGitHub , fetchpatch , fetchurl # build , cmake , ctags , pythonPackages , swig # math , eigen , blas , lapack , glpk # data , protobuf , json_c , libxml2 , hdf5 , curl # compression , libarchive , bzip2 , xz , snappy , lzo # more math , nlopt , lp_solve , colpack # extra support , pythonSupport ? true , opencvSupport ? false , opencv ? null </ins> , withSvmLight ? false }:

shogun fails to build since the eigen 3.4.0 bump: The package is a likely candidate for removal. Upstream is unresponsive and development has halted. Removed from debian: Removed from fedora: Blocking vcpkg update: Please run and paste the result. Maintainer information:
I think you were the last one to modify this package, so please speak up if you need it. Also pinging Last call - if no one responds within the next week, I'll open a PR to remove this package.
Yes, I was working on making it build on Darwin and adding it as a Python 3 module. Well, I did, but I didn't feel motivated to create a PR. As you comment, upstream has been inactive for almost a year, the latest release is several years old, and it becomes harder and harder to make it work, and the patches would start to accumulate. To make it work on Darwin we need two upstream patches that fix the build with newer compiler versions. In the current derivation, the Python interface is not built because the CMake flag is not the right one. When enabled, Swig 3 is used to generate the Python interface, but Swig 3 doesn't support Python 3.8+ (and with Swig 4 just fails). It can be fixed with a patch, that feels more like a hack, intercepting the Makefile build, so I am not happy with it: Another small patch is needed to fix the deprecated . Also, I wasn't happy that adding it as a Python module will recompile the entire library again, which takes too much time IMO. I haven't checked if it is possible to build with Eigen 3.4 because it takes forever to compile. It could probably work on the development version. Note that the development version doesn't support Eigen 3.4 because of this, but it may work: But there is no such limitation on the 6.1.4 release, which probably means it would require another patch to fix the code, if somebody figures out. So, I'd argue that the package is too old now, and the derivation has too many issues, and it's too much of a hassle to maintain it, so it's probably better to just remove it.
I decided to sit and take a look at the error, and I actually fixed it.


Question: <del> { stdenv, lib, fetchFromGitHub, fetchpatch, fetchurl, cmake, ctags, swig # data, compression , bzip2, curl, hdf5, json_c, xz, lzo, protobuf, snappy # maths , blas, lapack, eigen, nlopt, lp_solve, colpack, glpk # libraries , libarchive, libxml2 # extra support , pythonSupport ? true, pythonPackages ? null , opencvSupport ? false, opencv ? null </del> <ins> { lib , stdenv , fetchFromGitHub , fetchpatch , fetchurl # build , cmake , ctags , pythonPackages , swig # math , eigen , blas , lapack , glpk # data , protobuf , json_c , libxml2 , hdf5 , curl # compression , libarchive , bzip2 , xz , snappy , lzo # more math , nlopt , lp_solve , colpack # extra support , pythonSupport ? true , opencvSupport ? false , opencv ? null </ins> , withSvmLight ? false }:

I don't really use Eigen but the patch makes sense. So, I can send a PR to keep this package on the repo for another cycle at least. I mean, I already did all of the work and it builds. Other distros end up removing it because nobody cares to maintain it.
Nice! Thanks for looking into it. Like you said, if you've already done the work to get it working I don't see why not. If it's too much work to keep it working in the future we can always revisit this and drop it.


Question: url = "https://gitlab.freedesktop.org/cairo/cairo/-/commit/e22d7212acb454daccc088619ee147af03883974.diff"; sha256 = "sha256-8G98nsPz3MLEWPDX9F0jKgXC4hC4NNdFQLSpmW3ay2s="; }) <ins> # Fix unexpected color addition on grayscale images (usually text). # Upstream fix: https://gitlab.freedesktop.org/cairo/cairo/-/merge_requests/114 # Can be removed after 1.18 release (fetchpatch { name = "fix-grayscale-anialias.patch"; url = "https://gitlab.freedesktop.org/cairo/cairo/-/commit/4f4d89506f58a64b4829b1bb239bab9e46d63727.diff"; sha256 = "sha256-mbTg67e7APfdELsuMAgXdY3xokWbGtHF7VDD5UyYqKM="; }) </ins> ]; outputs = [ "out" "dev" "devdoc" ];

When adding a text in Gimp, a green border is visible: ! However, I would expect something like that: ! After , a on both Gimp (need 3.10.30) and (need 1.18 apparently). However, in NixOs Cairo 1.16 is used instead, so I guess it is necessary to upgrade cairo. Steps to reproduce the behavior: some text on gimp, say white text on black background I expect Cairo does not have maintainers so I'm pinging random people that contributed: Running NixOs with KDE Plasma.
Looking at no distributions ship 1.18 yet. I wonder why. Is it an API-breaking release?
Proposed cairo one-liner backport as
The 1.18 branch yet. We could switch to development snapshots (1.17.x) if there are more concerns. But cherry-picks will probably be enough for now.
The above PR solved the issue, thanks a lot! For people wanting to test before it gets into unstable you can do: but it takes a few hours to compile until Hydra compiles it.
Actually I'll maybe let it open until it's merged to unstable (for now it's in stagging) and backported.
GitHub should auto-close once the fixing commit reaches master branch. Though I'm not sure if that wasn't broken by closing and reopening.
It's reached all channels.


Question: unset CPP ''; <ins> configureFlags = lib.optionals stdenv.isDarwin [ "--disable-nls" ]; </ins> makeFlags = lib.optionals (stdenv.buildPlatform != stdenv.hostPlatform) [ "CROSS_COMPILE=${stdenv.cc.targetPrefix}" ]; <ins> postFixup = lib.optionalString stdenv.isDarwin '' install_name_tool -id $out/lib/libnewt.so.${version} $out/lib/libnewt.so.${version} install_name_tool -change libnewt.so.${version} $out/lib/libnewt.so.${version} $out/bin/whiptail ''; </ins> meta = with lib; { homepage = "https://pagure.io/newt"; description = "Library for color text mode, widget based user interfaces"; license = licenses.lgpl2; <del> platforms = platforms.linux; </del> <ins> platforms = platforms.unix; </ins> maintainers = [ maintainers.viric ]; }; }

Project description <!-- Describe the project a little: --: Newt is a programming library for color text mode, widget based user interfaces. Newt can be used to add stacked windows, entry widgets, checkboxes, radio buttons, labels, plain text fields, scrollbars, etc., to text mode user interfaces. Newt is based on the slang library. is in nixpkgs but only built for targets. It would be great if it could also be built for Homebrew has a , but since I just started using Nix I wasn't able yet to port it to a Nix file. My best try can be . Metadata homepage URL: source URL: license: gpl2+ platforms: unix, linux, darwin


Question: $container->set('UrlManager', function (Container $container) { diff --git a/services/DatabaseService.php b/services/DatabaseService.php <del> index dfcd5d4b..bc8d1a1d 100644 </del> <ins> index c093f361..0894791f 100644 </ins> --- a/services/DatabaseService.php +++ b/services/DatabaseService.php <del> @@ -107,6 +107,6 @@ class DatabaseService </del> <ins> @@ -114,6 +114,6 @@ class DatabaseService </ins> return GROCY_DATAPATH . '/grocy_' . $dbSuffix . '.db'; }


Question: <del> { buildGoModule, fetchFromGitLab, fetchzip, installShellFiles, lib }: </del> <ins> { buildGoModule , fetchFromGitLab , fetchzip , ffmpeg , installShellFiles , lib , makeWrapper }: </ins> buildGoModule rec { pname = "olaris-server"; <del> version = "0.4.0"; </del> <ins> version = "unstable-2022-06-11"; </ins> src = fetchFromGitLab { <del> owner = "olaris"; </del> <ins> owner = "olaris"; </ins> repo = pname; <del> rev = "v${version}"; hash = "sha256-iworyQqyTabTI0NpZHTdUBGZSCaiC5Dhr69mRtsHLOs="; </del> <ins> rev = "bdb2aeb1595c941210249164a97c12404c1ae0d8"; hash = "sha256-Uhnh6GC85ORKnfHeYNtbSA40osuscxXDF5/kXJrF2Cs="; </ins> }; preBuild = let

Olaris server requires ffmpeg to be available and raises an error when it can't be found: Steps to reproduce the behavior: olaris-server a library. The software runs correctly. There are two main ways to fix this: the software to use the full path to the ffmpeg dependency (ideally upstream). the program to add ffmpeg to its path. Please run and paste the result.
In fact it looks like it needs a custom image as it passes arguments that only exist on the modified version.
Actually it looks like the fork is no longer required: But this doesn't seem to be released yet. But probably is still a better option than packaging the custom ffmpeg.
yep, this looks like an easy fix EDIT: I was keen to try building the ffmpeg fork so that we can stick to a released version, however that proved prohibitively difficult, so tip of the default branch it is
no action required, but note the way I used in the pr and commit, means this issue would have autoclosed when the change merged
That is what happened.
sorry, I only saw this issue's update and assumed that you manually closed it; I assume most people involved in nixpkgs prs do not have merge perms, and github really needs to work on their ux. terribly sorry for the hassle, and assuming you were a more novice user.
No worries, GitHub really doesn't make it clear.


Question: detect-secrets = with python3Packages; toPythonApplication detect-secrets; <ins> deterministic-uname = callPackage ../build-support/deterministic-uname { }; </ins> dfmt = callPackage ../tools/text/dfmt { }; diopser = callPackage ../applications/audio/diopser { stdenv = gcc10StdenvCompat; };

libgtop is not reproducible, since it embed the output of into one of its binaries. See or build on 2 machines with different kernel versions. Report attached since r13y will not keep it, I think: libgtop build should be reproducible. This patch works from a nixpkgs perspective: However, it should ideally be reported and fixed upstream. N/A Maintainer information:
I marked this as stale due to inactivity. →


Question: done mkdir $out/bin <ins> export localeArchive="${config.i18n.glibcLocales}/lib/locale/locale-archive" </ins> substituteAll ${./switch-to-configuration.pl} $out/bin/switch-to-configuration chmod +x $out/bin/switch-to-configuration

When executing switch-to-configuration in a pure environment it fails: I am calling switch-to-configuration via systemd-run to active a new profile using the Hail update tool. The actual executed script is as follows: Actual output: <preactivating the configuration... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = "enUS.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). setting up /etc... perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LCALL = (unset), LANG = "enUS.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). setting up tmpfiles Too few arguments. sh: systemctl: command not found </preThe script works if I pass on the PATH and LOCALE_ARCHIVE environment variables: System: (NixOS: 17.09pre-git (Hummingbird)) Nix version: nix-env (Nix) 1.11.13 Nixpkgs version: nixos-unstable (Commit ) Sandboxing enabled: no (Related Hail issue: )


Question: <ins> diff --git a/executer/src/executer.cpp b/executer/src/executer.cpp index da848dad..5bd7e986 100644 --- a/executer/src/executer.cpp +++ b/executer/src/executer.cpp @@ -45,7 +45,7 @@ bool Executer::start(QIODevice *device, const QString &filename) QSettings settings; QString locale = settings.value(QStringLiteral("gui/locale"), QLocale::system().name()).toString(); -    mActionFactory->loadActionPacks(QApplication::applicationDirPath() + QStringLiteral("/actions"), locale); +    mActionFactory->loadActionPacks(QStringLiteral("@out@/lib/actions"), locale); #ifndef Q_OS_WIN if(mActionFactory->actionPackCount() == 0) mActionFactory->loadActionPacks(QStringLiteral("actiona/actions/"), locale); diff --git a/gui/src/mainwindow.cpp b/gui/src/mainwindow.cpp index 6052648e..3c802d93 100644 --- a/gui/src/mainwindow.cpp +++ b/gui/src/mainwindow.cpp @@ -322,7 +322,7 @@ void MainWindow::postInit() if(mSplashScreen) mSplashScreen->showMessage(tr("Loading actions...")); -    mActionFactory->loadActionPacks(QApplication::applicationDirPath() + QStringLiteral("/actions"), mUsedLocale); +    mActionFactory->loadActionPacks(QStringLiteral("@out@/lib/actions"), mUsedLocale); #ifndef Q_OS_WIN if(mActionFactory->actionPackCount() == 0) mActionFactory->loadActionPacks(QStringLiteral("actiona/actions/"), mUsedLocale); diff --git a/tools/src/languages.cpp b/tools/src/languages.cpp index 4926936e..18e9aabb 100644 --- a/tools/src/languages.cpp +++ b/tools/src/languages.cpp @@ -79,7 +79,7 @@ namespace Tools void Languages::installTranslator(const QString &componentName, const QString &locale) { auto translator = new QTranslator(QCoreApplication::instance()); -		if(!translator->load(QStringLiteral("%1/translations/%2_%3").arg(QCoreApplication::applicationDirPath()).arg(componentName).arg(locale))) +		if(!translator->load(QStringLiteral("@out@/share/actiona/translations/%1_%2").arg(componentName).arg(locale))) { auto path = QStringLiteral("%1/translations/%2_%3").arg(QDir::currentPath()).arg(componentName).arg(locale); if(!translator->load(path)) </ins>

Project description mouse macro Actiona is a task automation tool. It allows you to create and execute action lists. You don't need to know any programming language to use it: its intuitive interface allows you to create action lists (scripts) using drag & drop. Advanced users can use JavaScript (EcmaScript) to extend its functionality. Actiona is free software and runs under Windows and GNU/Linux. Binaries are available for Windows and Ubuntu for both 32 and 64 bits. The program is developed in C++ and uses the Qt framework. Metadata homepage URL: source URL: license: gpl3 platforms: cross-platform
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: linuxPackages_4_19 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_4_19); linuxPackages_5_4 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_5_4); linuxPackages_5_7 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_5_7); <del> linuxPackages_5_8 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_5_8); </del> # When adding to this list: # - Update linuxPackages_latest to the latest version

Describe the bug The is failing. I bisected this problem to “linux: Init 5.8”. The error message matches , which points to both a workaround of recompiling systemd against Linux 5.8 headers, and an upstream systemd patch (systemd/systemd) that’s in systemd 246 () and was backported in 245.7 as systemd/systemd-stable To Reproduce Steps to reproduce the behavior: Notify maintainers Cc Metadata Please run and paste the result. Maintainer information:
My PR wasn't merged, Linux 5.8 ended up being by someone else.
Linking for visibility: that PR was
The PR bumping systemd to 245.7 is at
Is it really helpful to send systemd 245.7 to given that will be unable to advance without it? Or are you thinking we also want to revert the bump in for now?
Maybe we should revert in master, and re-revert it in staging again. I let and decide about this, they've been doing the staging rounds.
Hey all, question: How do you spot which tests block the channels? I always track and every few days I notice nixos-unstable doesn't progress. When it don't I see an issue with the "channel blocker" label and I always wonder..
Click on the “Hydra job for tests” link and go to the “Constituents” tab.


Question: , pango , audioSupport ? mediaSupport <del> , pulseaudioSupport ? false </del> <ins> , pulseaudioSupport ? mediaSupport </ins> , libpulseaudio , apulse

Describe the bug With default settings, sound won't play in the stable repository Tor Browser. I managed to get it working: for some reason, says this: I am still new to Nix so I am not sure what it should say, but it can't be right since this piece in got it working: (after of course) To Reproduce Steps to reproduce the behavior: to your system configuration but leave ALSA disabled to do anything that requires sound in the browser. Metadata system: host os: multi-user?: sandbox: version: channels: nixpkgs: Maintainer information:
I marked this as stale due to inactivity. →
me, too. any word on this? just open any youtube video, and there's no sound. if it matters, i'm using the latest on using overlays.
I marked this as stale due to inactivity. →
I am also interested in solving this. I am using nixos: 21.05.3761. (Okapi) Since I am new to nix, I just tried the package override from above, but this is not working. Reading through nix-pills is not really enlightening which files are involved in what...
Did you remember to uninstall and install after adding the override?
I get an error: but my is located in
Two possibilities that come to mind: 1: You didn't install by attribute. you need to do (assuming your nix channel name is ) as opposed to 2: Your is indeed in the wrong place or wrongly named. I don't recall straight how it should be named. Believe the nixpkgs manual with this one, not me.
After reading I put my stuff now into So tor browser sources are not there anymore... mhhhh... so in that sense I feel nixos is not holding its promises of reliability (caused by external party)
It's our problem, and a known issue. More info .
They have an alternative mirror recently to the unstable channel. If you try the newest unstable, it might download. Can't guarantee that though.


Question: , pango , audioSupport ? mediaSupport <del> , pulseaudioSupport ? false </del> <ins> , pulseaudioSupport ? mediaSupport </ins> , libpulseaudio , apulse

thank you for your attention/help - I will try this later and report back...
I have the following override: So tor-browser reports back the new version: 10.5.10 but I get the following error when playing a video - so audio does still not work:
... it seems that the overlay does not affect of the original package. This part of is not contained in the generated file: since I am quite a novice with nixos, any hint is welcome....
that worked, thanks alot!


Question: , debug ? false , enableXWayland ? true , legacyRenderer ? false <del> , withSystemd ? true </del> <ins> , withSystemd ? lib.meta.availableOn stdenv.hostPlatform systemd </ins> , wrapRuntimeDeps ? true # deprecated flags , nvidiaPatches ? false

Package name: hyprland Latest released version: 0.36.0 <!-- Search your package here: --- Current version on the unstable channel: 0.35.0 Current version on the stable/release channel: 0.32.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. -- Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: The 035.0 has a bug that makes my system crash very often (nullptr when monitor is disconnected) the issue is supposed to be fixed in 0.36.0.


Question: executableName = "code" + lib.optionalString isInsiders "-insiders"; longName = "Visual Studio Code" + lib.optionalString isInsiders " - Insiders"; shortName = "Code" + lib.optionalString isInsiders " - Insiders"; <ins> inherit commandLineArgs; </ins> src = fetchurl { name = "VSCode_${version}_${plat}.${archive_fmt}";

For Chromium, there's a convenient way to define custom flags through . However, there doesn't seem to be a similar option for . I tried setting to "--touch-events", but touchscreen scrolling is not enabled when starting VSCode from desktop launcher, while running in console works as expected. Steps to reproduce the behavior: to "--touch-events" VSCode from desktop launcher on the editor area through touchscreen The editor should scroll as I drag. system: host os: multi-user?: sandbox: version: channels(yes): channels(root): nixpkgs:


Question: { lib , mkDerivation <del> , cmake </del> , extra-cmake-modules , wrapGAppsHook , gst_all_1

plasmatube can't play the video (black screen). probably need to add a dependency or similar. Steps to reproduce the behavior: plasmatube can play videos from youtube. ! system: host os: multi-user?: sandbox: version: channels(hervyqa): channels(root): nixpkgs:
solved, need install . !