Question: githubId = 13000278; name = "Maksim Bronsky"; }; <ins> PlushBeaver = { name = "Dmitry Kozlyuk"; email = "dmitry.kozliuk+nixpkgs@gmail.com"; github = "PlushBeaver"; githubId = 8988269; }; </ins> pmahoney = { email = "pat@polycrystal.org"; github = "pmahoney";

Would be a very useful package to have for ML Enthusiasts Project description Machine Learning Catboost Library Metadata CatBoost is a high-performance open source library for gradient boosting on decision trees homepage URL: source URL: license: Apache License 2.0 platforms: Linux installation instructions: Please let me know if I should stop tagging you in random issues and it bothers you (sorry, i'll stop), but I thought this might be of interest to you since you are very involved in tensorflow.
taggining maintainers of xgboost and lightgbm. Wondering if you could look into compiling catboost too?
I use tensorflow at work, which is why I care :). But I'm not a data-scientist
understood, thank you. GPU support for catboost would also be very welcome.
Looks like they have a non standard install script. But definitely doable. Sadly I don't think I have time in the near future but would be happy to point you in the right direction to get stared with a PR
both eyes wide open - i'll try to start this w/e, any pointers very welcome, thank you.
Currently failing to build on nix, although the file clearly exists.
- maybe it's easier if you create a work-in-progress pull request so other people can check? Two things that stand out are: looks like something is being downloaded during the build process. This won't work with sandboxing because there won't be a working network. builds should be isolated, i.e. access to should be rewritten to the local build directory, not (probably hardcoded somewhere in the build scripts). Packaging for nix can be quite fiddly - I think might be a good example for fetching complex dependencies + build script patches.
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: # filters assert enableExtraPlugins || enableDitaaFilter || enableMscgenFilter || enableDiagFilter || enableQrcodeFilter || enableAafigureFilter -> unzip != null; <del> assert enableExtraPlugins || enableDitaaFilter -> jre != null; </del> <ins> assert (enableExtraPlugins && enableJava) || enableDitaaFilter -> jre != null; </ins> assert enableExtraPlugins || enableMscgenFilter -> mscgen != null; assert enableExtraPlugins || enableDiagFilter -> blockdiag != null && seqdiag != null && actdiag != null && nwdiag != null; assert enableExtraPlugins || enableMatplotlibFilter -> matplotlib != null && numpy != null;

Since is provided by the non-free on aarch64, I'm not able to install asciidoc-full or any software that requires it to create e.g. the man pages. Can we make an option different from ? /cc
Making new granular options is fine, but I think enableStandardFeatures should still include java. (Or else the option is dishonest.) Alternatively, can we switch to openjdk (assuming that works on aarch64)?
It was just recently changed to in I'm fine with granular options, even though it will be quite some work to make packages not use anymore.
Oh, so this problem is due to licensing, not wanting to use non-free software? I didn't pick up on that earlier. How about adding a disableJava option, that has priority over enableStandardFeatures? Hm, this feels like a local solution to a global problem.
is a good idea! What do you think should be the default?
If enableStandardFeatures is true, you should get java. Setting disableJava then enables standard features except those requiring java. I'm not sure if doing this (per package) is a good idea though. Isn't this the start of a new whack-a-mole game?
Yes, it's certainly not a perfect solution, but I can then use an overlay which sets for . Alternatively, we could enable Java for x86 only by default.
Perhaps it would be less confusing to have so the additive condition is positive.


Question: <del> { lib, stdenv, fetchurl, unzip, pkgs, dataPath ? "/var/lib/rainloop" }: let </del> <ins> { lib, stdenv, fetchurl, unzip, writeText, dos2unix, dataPath ? "/var/lib/rainloop" }: let </ins> common = { edition, sha256 }: stdenv.mkDerivation (rec { pname = "rainloop${lib.optionalString (edition != "") "-${edition}"}"; version = "1.16.0"; <del> nativeBuildInputs = [ unzip ]; </del> <ins> nativeBuildInputs = [ unzip dos2unix ]; </ins> unpackPhase = '' mkdir rainloop

via In short: rainloop, a php-based webmail client, features a trivially exploitable stored xss vulnerability. Upstream is unresponsive, and seem to have ceased development. This page explains how the XSS works and proposes an unofficial patch: Example of an other distro applying this very patch:


Question: let efiSysMountPoint = if args.efiSysMountPoint == null then args.path else args.efiSysMountPoint; efiSysMountPoint' = replaceChars [ "/" ] [ "-" ] efiSysMountPoint; <ins> initrdSecrets = config.boot.initrd.secrets != {}; </ins> in pkgs.writeText "grub-config.xml" (builtins.toXML { splashImage = f cfg.splashImage;

Ditto. I have noticed this accidentially whily working at . Nixpkgs version: (run ) cc
You can puts secrets in an additionnal initrd readable by root only, and use See
There is more generic option now, . We probably want to merge those.


Question: # - https://github.com/NixOS/nixpkgs/issues/108772 # - https://github.com/NixOS/nixpkgs/pull/117555 print(machine.succeed("su - alice -c 'file ~/.config/Signal/sql/db.sqlite'")) <del> # TODO: The DB should be encrypted and the following should be machine.fail # instead of machine.succeed but the DB is currently unencrypted and we # want to notice if this isn't the case anymore as the transition to a # encrypted DB can cause data loss!: </del> machine.succeed( <del> "su - alice -c 'file ~/.config/Signal/sql/db.sqlite' | grep -i sqlite" </del> <ins> "su - alice -c 'file ~/.config/Signal/sql/db.sqlite' | grep 'db.sqlite: data'" ) machine.fail( "su - alice -c 'file ~/.config/Signal/sql/db.sqlite' | grep -e SQLite -e database" </ins> ) ''; })

Describe the bug Just lost on two different NixOS machine my Signal Desktop history because of this faulty update... I don't know, probably doesn't make sense for people to downgrade who are already upgraded but for others it dataloss To Reproduce Steps to reproduce the behavior: Signal Desktop Signal Desktop you to delete db, if you interact in a wrong way it will delete your data Notify maintainers ( and
Sorry to hear that. I recently lost my history too... It's really frustrating! Yeah, unfortunately I don't think there's anything we can do about it (as downstream package maintainers). AFAIK the source of the bug is still unknown, it doesn't seem to affect all users, and all releases have a limited lifetime ("expire" 90 days after the release, see my comment in ). Thanks for saying that! This really bothered me too... I just didn't say anything because I was too angry to keep it nice enough. (I raged a bit here but after I realized that one cannot even import old backups I had to take a break.)
I just got hit by a similar issue by moving from Archlinux (encrypted database) to NixOS (non encrypted database). After many things, the easiest fix to ensure proper functionalities IMHO is installing: This will disable tracker3 and prevent SQLite to be loaded in the process which will replace SQLCipher and cause the SQLite3 API to be the original one (i.e. non-encrypted) and cause many issues down the road I guess. That might not fix everything though :upsidedownface: Opened a PR:
FYI, in case anyone has feedback/suggestions: We might merge soon and it should cause another "Database startup error: Error: SQLITE_NOTADB: file is not a database" error (which is really unfortunate but not easily avoidable).
Heads-up: I've just merged to hopefully resolve this once and for all and the Python wrapper script should take care of the database re-encryption when launching Signal-Desktop as usual but the user experience isn't that great and you probably want to backup first in case the script fails unexpectedly.
Thank you, I just upgraded Signal on my computer and the re-encryption did work as intended


Question: (callPackage ../development/libraries/volk { }) ; <del> vorta = libsForQt5.callPackage ../applications/backup/vorta { }; </del> <ins> vorta = qt6Packages.callPackage ../applications/backup/vorta { }; </ins> vowpal-wabbit = callPackage ../applications/science/machine-learning/vowpal-wabbit { };

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


Question: in stdenv.mkDerivation rec { inherit pname version; <del> src = srcs.toolbox; postUnpack = '' mkdir -p $sourceRoot/third_party/{rxcpp,gtest} ln -s ${srcs.rxcpp} $sourceRoot/third_party/rxcpp/v${rxcppVersion}.tar.gz ln -s ${srcs.gtest} $sourceRoot/third_party/gtest/release-${gtestVersion}.tar.gz ''; </del> <ins> outputs = [ "out" "dev" "doc" ]; </ins> <del> # broken doCheck = false; </del> <ins> src = srcs.toolbox; </ins> patches = [ <ins> # Fix compile errors with json-c # https://github.com/shogun-toolbox/shogun/pull/4104 </ins> (fetchpatch { <del> url = "https://github.com/awild82/shogun/commit/365ce4c4c700736d2eec8ba6c975327a5ac2cd9b.patch"; </del> <ins> url = "https://github.com/shogun-toolbox/shogun/commit/365ce4c4c700736d2eec8ba6c975327a5ac2cd9b.patch"; </ins> sha256 = "158hqv4xzw648pmjbwrhxjp7qcppqa7kvriif87gn3zdn711c49s"; }) <ins> # Fix compile errors with GCC 9+ # https://github.com/shogun-toolbox/shogun/pull/4811 (fetchpatch { url = "https://github.com/shogun-toolbox/shogun/commit/c8b670be4790e0f06804b048a6f3d77c17c3ee95.patch"; sha256 = "sha256-MxsR3Y2noFQevfqWK3nmX5iK4OVWeKBl5tfeDNgjcXk="; }) (fetchpatch { url = "https://github.com/shogun-toolbox/shogun/commit/5aceefd9fb0e2132c354b9a0c0ceb9160cc9b2f7.patch"; sha256 = "sha256-AgJJKQA8vc5oKaTQDqMdwBR4hT4sn9+uW0jLe7GteJw="; }) # Fix compile errors with Eigen 3.4 ./eigen-3.4.patch </ins> ] ++ lib.optional (!withSvmLight) ./svmlight-scrubber.patch; <del> CCACHE_DISABLE="1"; CCACHE_DIR=".ccache"; nativeBuildInputs = [ cmake ]; buildInputs = with lib; [ blas lapack bzip2 colpack curl ctags eigen hdf5 json_c lp_solve xz lzo protobuf nlopt snappy swig (libarchive.dev) libxml2 lapack glpk ] ++ optionals (pythonSupport) (with pythonPackages; [ python ply numpy ]) ++ optional  (opencvSupport) opencv; NIX_CFLAGS_COMPILE="-faligned-new"; cmakeFlags = let onOff = b: if b then "ON" else "OFF"; flag = n: b: "-D"+n+"="+onOff b; in with lib; [ (flag "ENABLE_TESTING" doCheck) (flag "BUILD_META_EXAMPLES" doCheck) (flag "CMAKE_VERBOSE_MAKEFILE:BOOL" doCheck) (flag "PythonModular" pythonSupport) (flag "OpenCV" opencvSupport) (flag "USE_SVMLIGHT" withSvmLight) </del> <ins> nativeBuildInputs = [ cmake swig ctags ] ++ (with pythonPackages; [ python jinja2 ply ]); buildInputs = [ eigen blas lapack glpk protobuf json_c libxml2 hdf5 curl libarchive bzip2 xz snappy lzo nlopt lp_solve colpack ] ++ lib.optionals pythonSupport (with pythonPackages; [ python numpy ]) ++ lib.optional opencvSupport opencv; cmakeFlags = let enableIf = cond: if cond then "ON" else "OFF"; in [ "-DBUILD_META_EXAMPLES=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_ARPACK=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_ARPREC=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_CPLEX=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_Mosek=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_TFLogger=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_ViennaCL=ON" "-DCMAKE_SKIP_BUILD_RPATH=OFF" "-DCMAKE_CTEST_ARGUMENTS='--exclude-regex;TrainedModelSerialization'"  # Sporadic segfault "-DENABLE_TESTING=${enableIf doCheck}" "-DDISABLE_META_INTEGRATION_TESTS=ON" "-DTRAVIS_DISABLE_META_CPP=ON" "-DPythonModular=${enableIf pythonSupport}" "-DOpenCV=${enableIf opencvSupport}" "-DUSE_SVMLIGHT=${enableIf withSvmLight}" </ins> ]; <ins> CXXFLAGS = "-faligned-new"; doCheck = true; postUnpack = '' mkdir -p $sourceRoot/third_party/{rxcpp,GoogleMock} ln -s ${srcs.rxcpp} $sourceRoot/third_party/rxcpp/v${rxcppVersion}.tar.gz ln -s ${srcs.gtest} $sourceRoot/third_party/GoogleMock/release-${gtestVersion}.tar.gz ''; </ins> postPatch = '' # Fix preprocessing SVMlight code sed -i

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: in stdenv.mkDerivation rec { inherit pname version; <del> src = srcs.toolbox; postUnpack = '' mkdir -p $sourceRoot/third_party/{rxcpp,gtest} ln -s ${srcs.rxcpp} $sourceRoot/third_party/rxcpp/v${rxcppVersion}.tar.gz ln -s ${srcs.gtest} $sourceRoot/third_party/gtest/release-${gtestVersion}.tar.gz ''; </del> <ins> outputs = [ "out" "dev" "doc" ]; </ins> <del> # broken doCheck = false; </del> <ins> src = srcs.toolbox; </ins> patches = [ <ins> # Fix compile errors with json-c # https://github.com/shogun-toolbox/shogun/pull/4104 </ins> (fetchpatch { <del> url = "https://github.com/awild82/shogun/commit/365ce4c4c700736d2eec8ba6c975327a5ac2cd9b.patch"; </del> <ins> url = "https://github.com/shogun-toolbox/shogun/commit/365ce4c4c700736d2eec8ba6c975327a5ac2cd9b.patch"; </ins> sha256 = "158hqv4xzw648pmjbwrhxjp7qcppqa7kvriif87gn3zdn711c49s"; }) <ins> # Fix compile errors with GCC 9+ # https://github.com/shogun-toolbox/shogun/pull/4811 (fetchpatch { url = "https://github.com/shogun-toolbox/shogun/commit/c8b670be4790e0f06804b048a6f3d77c17c3ee95.patch"; sha256 = "sha256-MxsR3Y2noFQevfqWK3nmX5iK4OVWeKBl5tfeDNgjcXk="; }) (fetchpatch { url = "https://github.com/shogun-toolbox/shogun/commit/5aceefd9fb0e2132c354b9a0c0ceb9160cc9b2f7.patch"; sha256 = "sha256-AgJJKQA8vc5oKaTQDqMdwBR4hT4sn9+uW0jLe7GteJw="; }) # Fix compile errors with Eigen 3.4 ./eigen-3.4.patch </ins> ] ++ lib.optional (!withSvmLight) ./svmlight-scrubber.patch; <del> CCACHE_DISABLE="1"; CCACHE_DIR=".ccache"; nativeBuildInputs = [ cmake ]; buildInputs = with lib; [ blas lapack bzip2 colpack curl ctags eigen hdf5 json_c lp_solve xz lzo protobuf nlopt snappy swig (libarchive.dev) libxml2 lapack glpk ] ++ optionals (pythonSupport) (with pythonPackages; [ python ply numpy ]) ++ optional  (opencvSupport) opencv; NIX_CFLAGS_COMPILE="-faligned-new"; cmakeFlags = let onOff = b: if b then "ON" else "OFF"; flag = n: b: "-D"+n+"="+onOff b; in with lib; [ (flag "ENABLE_TESTING" doCheck) (flag "BUILD_META_EXAMPLES" doCheck) (flag "CMAKE_VERBOSE_MAKEFILE:BOOL" doCheck) (flag "PythonModular" pythonSupport) (flag "OpenCV" opencvSupport) (flag "USE_SVMLIGHT" withSvmLight) </del> <ins> nativeBuildInputs = [ cmake swig ctags ] ++ (with pythonPackages; [ python jinja2 ply ]); buildInputs = [ eigen blas lapack glpk protobuf json_c libxml2 hdf5 curl libarchive bzip2 xz snappy lzo nlopt lp_solve colpack ] ++ lib.optionals pythonSupport (with pythonPackages; [ python numpy ]) ++ lib.optional opencvSupport opencv; cmakeFlags = let enableIf = cond: if cond then "ON" else "OFF"; in [ "-DBUILD_META_EXAMPLES=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_ARPACK=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_ARPREC=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_CPLEX=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_Mosek=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_TFLogger=ON" "-DCMAKE_DISABLE_FIND_PACKAGE_ViennaCL=ON" "-DCMAKE_SKIP_BUILD_RPATH=OFF" "-DCMAKE_CTEST_ARGUMENTS='--exclude-regex;TrainedModelSerialization'"  # Sporadic segfault "-DENABLE_TESTING=${enableIf doCheck}" "-DDISABLE_META_INTEGRATION_TESTS=ON" "-DTRAVIS_DISABLE_META_CPP=ON" "-DPythonModular=${enableIf pythonSupport}" "-DOpenCV=${enableIf opencvSupport}" "-DUSE_SVMLIGHT=${enableIf withSvmLight}" </ins> ]; <ins> CXXFLAGS = "-faligned-new"; doCheck = true; postUnpack = '' mkdir -p $sourceRoot/third_party/{rxcpp,GoogleMock} ln -s ${srcs.rxcpp} $sourceRoot/third_party/rxcpp/v${rxcppVersion}.tar.gz ln -s ${srcs.gtest} $sourceRoot/third_party/GoogleMock/release-${gtestVersion}.tar.gz ''; </ins> postPatch = '' # Fix preprocessing SVMlight code sed -i

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: nsh = callPackage ../shells/nsh { }; <del> nushell = callPackage ../shells/nushell { inherit (darwin.apple_sdk.frameworks) AppKit Foundation Security; </del> <ins> nushell = darwin.apple_sdk_11_0.callPackage ../shells/nushell { inherit (darwin.apple_sdk_11_0.frameworks) AppKit Security; </ins> inherit (darwin.apple_sdk) sdk; };

Steps to reproduce the behavior: nix on x86_64-darwin experimental features nix-command and flakes to install nushell v0.75.0 via . Please run and paste the result.
I can confirm the bug, the following PR could resolve it.
that is great news! I am hopeful that can resolve it. I see that you marked this as resolved by . However, this does not seem to have resolved the issue for me. I am still receiving the same error when trying to build :
The ofborg test did pass, see Maybe you have to build it on master? Also, I don't think will help, as the author of that PR.
Hmm, after upgrading nix and updating my nixpkgs-unstable channel, I'm still receiving the same error.
You have to wait for the commit to arrive on nixpkgs-unstable.
Thank you your PR resolved it. the fix is in the nixpkgs-unstable channel. Much appreciated!


Question: unbound = handleTest ./unbound.nix {}; unifi = handleTest ./unifi.nix {}; unit-php = handleTest ./web-servers/unit-php.nix {}; <del> upnp = handleTest ./upnp.nix {}; </del> <ins> upnp.iptables = handleTest ./upnp.nix { useNftables = false; }; upnp.nftables = handleTest ./upnp.nix { useNftables = true; }; </ins> uptermd = handleTest ./uptermd.nix {}; uptime-kuma = handleTest ./uptime-kuma.nix {}; usbguard = handleTest ./usbguard.nix {};

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


Question: <ins> diff --git a/setup/main.py b/setup/main.py index 8d581cd..2ac47b9 100644 --- a/setup/main.py +++ b/setup/main.py @@ -37,7 +37,7 @@ def get_hangul_keyboard_list(): from ctypes import CDLL, c_int, c_char_p -    libhangul = CDLL('libhangul.so.1') +    libhangul = CDLL('@libhangul@') libhangul.hangul_ic_get_n_keyboards.argtypes = [] libhangul.hangul_ic_get_n_keyboards.restype = c_int libhangul.hangul_ic_get_keyboard_id.argtypes = [c_int] </ins>

In executing ibus-setup-hangul, got this error message: .nix -rebuild switch ibus-setup-hangul in a shell System: NixOS 17.03.1584. (Gorilla) Nix version: 1.11.11 Nixpkgs version: 17.03.1584. Sandboxing enabled: build-use-sandbox = false
Might be due to . What was the reason to remove from dependencies?
I think that was because I noticed that it is propagated from some other package, but looking at this now it doesn't seem to be the case. I'll investigate this today!
This seems more deep than I thought. The bug is two-fold: script is not patched as needed for Python scripts; should be propagated from . However, only its output is propagated, so it's not as a Python library. I can fix the first one but not sure what to do about the second -- maybe we should change behaviour of this propagation in some way.
The same problem appears with anthy, and directly adding the same pyEnv to buildInputs like did in ibus definitely fixes the build fails (tested with both anthy and hangul), but the python environment isn't propagated by itself.


Question: <del> { stdenv, fetchgit, unzip, firefox-esr, makeWrapper }: </del> <ins> { stdenv, fetchgit, unzip, firefox-esr-52, makeWrapper }: </ins> stdenv.mkDerivation rec { pkgname = "conkeror"; version = "1.0.4"; name = "${pkgname}-${version}"; src = fetchgit { url = git://repo.or.cz/conkeror.git; rev = "refs/tags/${version}";

On running I get: Add to and run. system: host os: multi-user?: sandbox: version: channels(lev): channels(root): nixpkgs:
Well, the output has at least changed a bit:
my pull request fixes the . It broke down because the package had moved to but requires . But according to the browser is discontinued and `firefox-esr-5.2' is marked as unsecure so I would rather advocate for removing this package altogether.


Question: <del> diff --git a/thirdparty/CMakeLists.txt b/thirdparty/CMakeLists.txt index f33b3bf3f..1214f179c 100644 --- a/thirdparty/CMakeLists.txt +++ b/thirdparty/CMakeLists.txt @@ -16,6 +16,5 @@ if(NOT "${SRB2_CONFIG_SYSTEM_LIBRARIES}") include("cpm-png.cmake") include("cpm-curl.cmake") include("cpm-openmpt.cmake") +	include("cpm-libgme.cmake") endif() - -include("cpm-libgme.cmake") </del>

use instead of pulling the windows zip from github releases
I can review if you want to PR this
upstream has said that they'd rather us use the github mirror that they're going to set up
the github mirror has been created
Sorry, I have to delete the github mirror, due to bandwidth limits. Please use
the "SRB22.2" branch and/or "SRB2release_2.2.13" tag
Getting 500 errors when trying to access
does this work for you?
The link works however the download buttons don't. PRs welcome if anyone can get it working, but wait for to be merged first to avoid merge conflicts.
i have had another look, and have found that it might be better to pull directly from branch
Thanks, was able to get it to work with :+1:


Question: , systemd , enableProprietaryCodecs ? true , gn <del> , cups, darwin, openbsm, runCommand, xcbuild </del> <ins> , cups, darwin, openbsm, runCommand, xcbuild, writeScriptBin </ins> , ffmpeg_3 ? null , lib, stdenv }:

The component of the derivation fails to compile on MacOS. But in two ways, and I can't tell what causes one or the other to trigger. On command: On command: the channel compilation failure Compiles.
It has been broken for a while now for different reasons. Maintaining it for darwin is a lot of work and nobody has stepped up to do that. Also, this is a duplicate of
By the way, what is your use case for ?
We're building a desktop version of mobile application and we need for our in-app browser with Ethereum support.


Question: , systemd , enableProprietaryCodecs ? true , gn <del> , cups, darwin, openbsm, runCommand, xcbuild </del> <ins> , cups, darwin, openbsm, runCommand, xcbuild, writeScriptBin </ins> , ffmpeg_3 ? null , lib, stdenv }:

Full log: Error message: That's the result I get from my macOS remote builder. When I run the build on my desktop Mac, it builds fine and uses the impure SDK from my Catalina install (10.15.1): However, the local build displays this warning repeatedly: I assume this is related to the macOS patches and hopefully gives some clue as to why it's broken.
qtbase builds fine on hydra: qtwebengine fails:
Those links point to the same thing. Anyway, strictly speaking I'm trying to build , but it's failing in .
Can you explain what do you mean? How are you using ?
It's a dependency of . edit: sorry, I see what you mean now. is a dependency of . I was confused by the message from the build saying that QT would be installed in .
Sure, depends on . Realistically, your best bet for now is to just use anki from an old version of nixpkgs. You see, doesn't have a darwin maintainer. I think, I was the last person to fix it around last January. The problem is that it's hard to keep up with all the updates. Every "minor" Qt version bump brings serious breaking changes for on darwin (like they might not even support our version of SDK anymore...). To make things worse we port all those bumps to the stable branch, so it quickly breaks there too.
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 . on the on .
Still important to me, many qt apps are broken on darwin due to this one.


Question: env.NIX_CFLAGS_COMPILE = toString (lib.optionals stdenv.cc.isGNU [ "-Wno-error=strict-prototypes" <ins> "-Wno-error=deprecated-declarations" </ins> ]); enableParallelBuilding = true;

Steps to reproduce the behavior: ocf-resource-agents. Relevant: () Looks like a GCC update deprecated , which is used by ocf-resource-agents. This also causes the pacemaker build to fail, due to the circular dependency. system: host os: multi-user?: sandbox: version: nixpkgs: (I'm using commit ) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I fixed it in my flake for pcs / pacemaker here:


Question: datacenter.settings = lib.mkOption { type = settingsFormat.type; default = { <del> LOG_LEVEL=4; LOG_FILE_NAME="/var/log/fabricmanager.log"; LOG_APPEND_TO_LOG=1; LOG_FILE_MAX_SIZE=1024; LOG_USE_SYSLOG=0; DAEMONIZE=1; BIND_INTERFACE_IP="127.0.0.1"; STARTING_TCP_PORT=16000; FABRIC_MODE=0; FABRIC_MODE_RESTART=0; STATE_FILE_NAME="/var/tmp/fabricmanager.state"; FM_CMD_BIND_INTERFACE="127.0.0.1"; FM_CMD_PORT_NUMBER=6666; FM_STAY_RESIDENT_ON_FAILURES=0; ACCESS_LINK_FAILURE_MODE=0; TRUNK_LINK_FAILURE_MODE=0; NVSWITCH_FAILURE_MODE=0; ABORT_CUDA_JOBS_ON_FM_EXIT=1; TOPOLOGY_FILE_PATH="${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; DATABASE_PATH="${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; </del> <ins> LOG_LEVEL = 4; LOG_FILE_NAME = "/var/log/fabricmanager.log"; LOG_APPEND_TO_LOG = 1; LOG_FILE_MAX_SIZE = 1024; LOG_USE_SYSLOG = 0; DAEMONIZE = 1; BIND_INTERFACE_IP = "127.0.0.1"; STARTING_TCP_PORT = 16000; FABRIC_MODE = 0; FABRIC_MODE_RESTART = 0; STATE_FILE_NAME = "/var/tmp/fabricmanager.state"; FM_CMD_BIND_INTERFACE = "127.0.0.1"; FM_CMD_PORT_NUMBER = 6666; FM_STAY_RESIDENT_ON_FAILURES = 0; ACCESS_LINK_FAILURE_MODE = 0; TRUNK_LINK_FAILURE_MODE = 0; NVSWITCH_FAILURE_MODE = 0; ABORT_CUDA_JOBS_ON_FM_EXIT = 1; TOPOLOGY_FILE_PATH = "${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; DATABASE_PATH = "${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; </ins> }; defaultText = lib.literalExpression '' <del> { LOG_LEVEL=4; LOG_FILE_NAME="/var/log/fabricmanager.log"; LOG_APPEND_TO_LOG=1; LOG_FILE_MAX_SIZE=1024; LOG_USE_SYSLOG=0; DAEMONIZE=1; BIND_INTERFACE_IP="127.0.0.1"; STARTING_TCP_PORT=16000; FABRIC_MODE=0; FABRIC_MODE_RESTART=0; STATE_FILE_NAME="/var/tmp/fabricmanager.state"; FM_CMD_BIND_INTERFACE="127.0.0.1"; FM_CMD_PORT_NUMBER=6666; FM_STAY_RESIDENT_ON_FAILURES=0; ACCESS_LINK_FAILURE_MODE=0; TRUNK_LINK_FAILURE_MODE=0; NVSWITCH_FAILURE_MODE=0; ABORT_CUDA_JOBS_ON_FM_EXIT=1; TOPOLOGY_FILE_PATH="''${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; DATABASE_PATH="''${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; } </del> <ins> { LOG_LEVEL=4; LOG_FILE_NAME="/var/log/fabricmanager.log"; LOG_APPEND_TO_LOG=1; LOG_FILE_MAX_SIZE=1024; LOG_USE_SYSLOG=0; DAEMONIZE=1; BIND_INTERFACE_IP="127.0.0.1"; STARTING_TCP_PORT=16000; FABRIC_MODE=0; FABRIC_MODE_RESTART=0; STATE_FILE_NAME="/var/tmp/fabricmanager.state"; FM_CMD_BIND_INTERFACE="127.0.0.1"; FM_CMD_PORT_NUMBER=6666; FM_STAY_RESIDENT_ON_FAILURES=0; ACCESS_LINK_FAILURE_MODE=0; TRUNK_LINK_FAILURE_MODE=0; NVSWITCH_FAILURE_MODE=0; ABORT_CUDA_JOBS_ON_FM_EXIT=1; TOPOLOGY_FILE_PATH="''${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; DATABASE_PATH="''${nvidia_x11.fabricmanager}/share/nvidia-fabricmanager/nvidia/nvswitch"; } </ins> ''; description = '' Additional configuration options for fabricmanager.

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


Question: <ins> { lib, fetchFromGitHub, python3Packages }: python3Packages.buildPythonPackage rec { pname = "open-fprintd"; version = "0.6"; src = fetchFromGitHub { owner = "uunicorn"; repo = pname; rev = version; sha256 = "sha256-uVFuwtsmR/9epoqot3lJ/5v5OuJjuRjL7FJF7oXNDzU="; }; propagatedBuildInputs = with python3Packages; [ dbus-python pygobject3 ]; checkInputs = with python3Packages; [ dbus-python ]; postInstall = '' install -D -m 644 debian/open-fprintd.service  $out/lib/systemd/system/open-fprintd.service install -D -m 644 debian/open-fprintd-resume.service  $out/lib/systemd/system/open-fprintd-resume.service install -D -m 644 debian/open-fprintd-suspend.service  $out/lib/systemd/system/open-fprintd-suspend.service substituteInPlace $out/lib/systemd/system/open-fprintd.service  --replace /usr/lib/open-fprintd "$out/lib/open-fprintd" substituteInPlace $out/lib/systemd/system/open-fprintd-resume.service  --replace /usr/lib/open-fprintd "$out/lib/open-fprintd" substituteInPlace $out/lib/systemd/system/open-fprintd-suspend.service  --replace /usr/lib/open-fprintd "$out/lib/open-fprintd" ''; postFixup = '' wrapPythonProgramsIn "$out/lib/open-fprintd" "$out $pythonPath" ''; meta = with lib; { description = "Fprintd replacement which allows you to have your own backend as a standalone service"; homepage = "https://github.com/uunicorn/open-fprintd"; license = licenses.gpl2Only; platforms = platforms.linux; }; } </ins>

Project description Fprintd replacement which allows you to have your own backend as a standalone service. Metadata homepage URL: source URL: license: GPL2 platforms: linux


Question: <del> { lib, fetchFromGitHub, proot, patchelf, fakechroot, runc, simplejson, pycurl, coreutils, nose, mock, buildPythonApplication }: </del> <ins> { lib , fetchFromGitHub , singularity , python3Packages }: </ins> <del> buildPythonApplication rec { version = "1.1.3"; </del> <ins> python3Packages.buildPythonApplication rec { </ins> pname = "udocker"; <ins> version = "1.3.1"; </ins> src = fetchFromGitHub { owner = "indigo-dc"; <del> repo = "udocker" ; </del> <ins> repo = "udocker"; </ins> rev = "v${version}"; <del> sha256 = "1c8y1p3brj987drikwrby8m1hdr40ja4anx0p4xsij3ll2h62w6z"; </del> <ins> sha256 = "0dfsjgidsnah8nrclrq10yz3ja859123z81kq4zdifbrhnrn5a2x"; </ins> }; <del> buildInputs = [ proot patchelf fakechroot runc simplejson pycurl coreutils ]; postPatch = '' substituteInPlace udocker.py --replace /usr/sbin:/sbin:/usr/bin:/bin $PATH substituteInPlace udocker.py --replace /bin/chmod ${coreutils}/bin/chmod substituteInPlace udocker.py --replace /bin/rm ${coreutils}/bin/rm substituteInPlace tests/unit_tests.py --replace /bin/rm ${coreutils}/bin/rm substituteInPlace udocker.py --replace "autoinstall = True" "autoinstall = False" ''; </del> <ins> # crun patchelf proot runc fakechroot # are download statistically linked during runtime buildInputs = [ singularity ] ++ (with python3Packages; [ pytest-runner pycurl ]); checkInputs = with python3Packages; [ pytestCheckHook ]; </ins> <del> checkInputs = [ nose mock </del> <ins> disabledTests = [ "test_05__get_volume_bindings" </ins> ]; <del> checkPhase = '' NOSE_EXCLUDE=test_03_create_repo,test_04_is_repo,test_02__get_group_from_host nosetests -v tests/unit_tests.py ''; </del> <ins> disabledTestPaths = [ # Network "tests/unit/test_curl.py" "tests/unit/test_dockerioapi.py" ]; </ins> meta = with lib; { description = "basic user tool to execute simple docker containers in user space without root privileges";

I just discovered and i can't use it on NixOS Pulling image seems good Trying to run image fail because it try to mount some specials folders The : Trying without mounting folder fail because it can't find Start a shell with still fail because it can't find Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(pinage404): channels(root): nixpkgs:
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 . on the on .
It could still be important.
I marked this as stale due to inactivity. →


Question: vendorHash = "sha256-OOiiKtKb+BiFkoSBUQQfqm4dMfDW3Is+30Kwcdg8LNA="; nativeBuildInputs = [ pkg-config installShellFiles wrapGAppsHook3 ]; <del> buildInputs = [ webkitgtk_4_1 glib fuse ]; </del> <ins> buildInputs = [ webkitgtk_4_1 glib fuse glib-networking ]; </ins> ldflags = [ "-X github.com/jstaf/onedriver/cmd/common.commit=v${version}" ];

In gnome runs fine, in KDE plasma there are a couple problems: Unable to open file explorer when pressing "+", crashes with error Unable to add account, getting error Run in a pure shell: , use the and try to use it OR plasma installed and no other desktop environment: onedriver from nixpkgs (with home manager for example:) and press the button to add a folder. No errors we're missing the inputs and . should fix the gsettings schemas error (). The error requires env variable , we should probably wrap as explained . Quick and dirty way to make it work now, without wrapping, is adding those dependencies and adding the variable to the whole system: and to buildInputs and nativeBuildInputs respectively. (not sure which one for either): to the nixOS configuration the location of the variable: We should create a option eventually ahahha This is my configuration for the onedriver user service: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hello and thanks for reporting this! The is although it is only available in the channel for now, can you please test if the derivation from nixpkgs-unstable works for you? If not, I will add the missing dependency and make a PR asap :) As for the GIOEXTRAMODULES variable I am not sure there is something I can do at the derivation level.
Thanks I can confirm the version on the unstable channel doesn't crash with , but without the variable set the error is still present. I tried to wrap it by adding this line in the end of the postInstall script but it didn't fix it, running now shows two GIOEXTRAMODULES variables set tho I'll keep this open for now because of this problem and update the title the workaround for now is adding to the system configuration
Hey, I just pushed a small branch which should fix your issue with . I built the derivation locally and I get the right GIOEXTRAMODULES path set correctly by the script.


Question: vendorHash = "sha256-OOiiKtKb+BiFkoSBUQQfqm4dMfDW3Is+30Kwcdg8LNA="; nativeBuildInputs = [ pkg-config installShellFiles wrapGAppsHook3 ]; <del> buildInputs = [ webkitgtk_4_1 glib fuse ]; </del> <ins> buildInputs = [ webkitgtk_4_1 glib fuse glib-networking ]; </ins> ldflags = [ "-X github.com/jstaf/onedriver/cmd/common.commit=v${version}" ];

In my attempt in my previous comment, I had also tried a method that seemed to have set the correct GIOEXTRAMODULES path, but I tried your derivation and still: ! I grabbed your commit like this and it took a couple hours to build, it seems to have built a lot of programs besides onedriver, I'm still not a great nixOS wizard:
never mind, I'm dumb, forgot to change the package used in , now the error doesn't appear, but the window comes up grey? !
Trying to use the code from in my own config with callPackage gives me if I use instead of it works perfectly
using just also works
That is because is only on right now, if you're using you need to use , which is the same thing :) Glad to know the problem has been fixed for you. As for the blank page, it seems to be an upstream issue with onedriver and Plasma 6 (see jstaf/onedriver), but since I don't use Plasma I'm afraid I cannot help..


Question: nix-build-uncached = callPackage ../development/tools/misc/nix-build-uncached { }; <del> nexus = callPackage ../development/tools/repository-managers/nexus { jre_headless = jre8_headless; }; </del> nexusmods-app-unfree = callPackage ../by-name/ne/nexusmods-app/package.nix { enableUnfree = true; };

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: "--enable-docs" "--enable-tools" "--enable-guest-agent" <ins> "--sysconfdir=/etc" </ins> ] # disable sysctl check on darwin. ++ optional stdenv.isDarwin "--cpu=x86_64"

Describe the bug Libvirt usually handles virtual network devices, interfaces, bridges and also the DHCP range. This seems to be broken. To Reproduce Steps to reproduce the behavior: a VM connected to the default network 't get an IP Expected behavior DHCP is working Screenshots If applicable, add screenshots to help explain your problem. Notify maintainers Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Likely fixed by If you are fine with rebuilding libvirt your could use this locally. Alternatively if this is your home computer and you are in a safe network you could temporarily set to disable your whole system's firewall but this is not recommended. Edit: Rebuliding should be really quick (on a decent laptop)
Thanks - looks right. I will try to use the overlay first.
I think it's related... When I try to start a VM using Gnome-boxes or Virtual-manager with VM using bridge this error happens:
have you updated to the latest nixos-unstable version? This issue itself should be fixed and you should probably create a new issue if your problem persists.
it's still happening, even with the last version.
then you should probably create a new issue as I don't think it's the same issue. It may still be related so maybe reference this issue. There wasn't an error with the original issue I think


Question: $CXX -o cxx-check ${./cxx-main.cc} ${emulator} ./cxx-check <ins> # test for https://github.com/NixOS/nixpkgs/issues/214524#issuecomment-1431745905 # .../include/cxxabi.h:20:10: fatal error: '__cxxabi_config.h' file not found # in libcxxStdenv echo "checking whether cxxabi.h can be included... " >&2 $CXX -o include-cxxabi ${./include-cxxabi.cc} ${emulator} ./include-cxxabi </ins> ${lib.optionalString (stdenv.isDarwin && stdenv.cc.isClang) '' echo "checking whether compiler can build with CoreFoundation.framework... " >&2 mkdir -p foo/lib

Clang's wrapper does not set as an include path. Compiling files with since <cxxabi.hrequires is present in the aforementioned path I created the environment using this minimal mkShell expression Adding to
Proposed solution seems reasonable to me. See also started by
Please can you also include the nixpkgs commit hash in the repro (sorry if it's there and I missed it).
Oh thank you, that makes so much sense, I was also looking at how the monorepo handles things as well as their tests on finding the system include headers and what you said is probably the correct reason. Ah, it was the nixpkgs-unstable revision updated just then. Sorry I do not have that, but you can reproduce it with the current master as well.


Question: cuda-native-redist = symlinkJoin { name = "cuda-redist"; <del> paths = with cudaPackages; [ cuda_cudart # cuda_runtime.h cuda_nvcc ] ++ cuda-common-redist; </del> <ins> paths = with cudaPackages; [cuda_nvcc] ++ cuda-common-redist; </ins> }; cuda-redist = symlinkJoin {

Originally spotted by (thank you!). Steps to reproduce the behavior (assuming and are both ): The environment variable contains semicolons and must be quoted, otherwise bash will interpret the semicolons as command separators.
- Hey, I am not sure how to clean up the mess I just made on . Really embarrassed. I intended to rebase and hit merge instead, which pulled in 10k changes.
No worries, Happens to everyone at some point :) Personally, I'd just open a new PR.
Here it is: . Does the commit history look clean enough? I'll try to rebase it later, but I am concerned about retagging all of those folks.
I'd say don't worry about it -- as far as best practice goes, I'm actually not sure what's recommended for commits. do we recommend squashing before merge? I know I typically just do force pushes to avoid any commit history :l
I went ahead and squashed, and I'll post a nixpkgs-review when it's finished.
I don't think we have an official stance on this. Contributors use their best judgement for whatever keeps the commit history simplest and easiest to use


Question: # # The following selects the correct Clang version, matching the version # used in Swift, and applies the same libc overrides as `apple_sdk.stdenv`. <del> clang = let # https://github.com/NixOS/nixpkgs/issues/295322 clangNoMarch = swiftLlvmPackages.clang.override { disableMarch = true; }; in if pkgs.stdenv.isDarwin </del> <ins> clang = if pkgs.stdenv.isDarwin </ins> then <del> clangNoMarch.override rec { </del> <ins> swiftLlvmPackages.clang.override rec { </ins> libc = apple_sdk.Libsystem; bintools = pkgs.bintools.override { inherit libc; }; # Ensure that Swift’s internal clang uses the same libc++ and libc++abi as the

Since was merged into the master, swift cannot be built on aarch64. Steps to reproduce the behavior: reported in I'm not familiar with swift or clang, but I'm using the following overlay as a workaround until it's fixed. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
states that this only fixed the swift build but all downstream packages are still broken. re-opening.
Actually, it seems only dark-mode-notify is broken, others seem fine. Probably because it uses Cocoa or disables sandbox. I don't know for sure.
I noticed that my personal package does not build either. Maybe it's because of swift itself or swiftpm?
The above open PR seems to run into the same issue…


Question: }; "kicad-unstable" = { kicadVersion = { <del> version =			"2022-06-21"; </del> <ins> version =			"2022-09-18"; </ins> src = { <del> rev =			"b54bb909755d39dcce38ef277c715d7f31ab8e00"; sha256 =		"0nzgrkkvc66hgqdrwfmh5fjw4ffr8gc3bw3n44sa6zjkkz5s6p48"; </del> <ins> rev =			"0efc1149afed2af5b81e4555de4623217ece650f"; sha256 =		"19fqy8yvvl45izg5ynhch9r4gl4ncx0bz9s6n1x98bgzxkdyc14q"; </ins> }; }; libVersion = { <del> version =			"2022-06-21"; </del> <ins> version =			"2022-09-18"; </ins> libSources = { <del> symbols.rev =		"a003b00f6f1056d726e32e911cd65b32946f5503"; symbols.sha256 =	"02z3vqhz1rlf57zi8vyrlxvvdl1hpsh447p41qdgcpn5dyjycb9d"; </del> <ins> symbols.rev =		"879023fba005d23f285b6d052d9e6bcba1d754aa"; symbols.sha256 =	"1nxz8r3h3j62fs3s77lj27333fsj5c4i01n05lv0gqx36h28hqxk"; </ins> templates.rev =		"ae2b46f8756d79379b90fec01d4fdde1ccfd73c1"; templates.sha256 =	"08zxh83fbygh1x2jhca8nrp3f9kihf7kmg65qmyp95wvps4p5h8v"; <del> footprints.rev =	"5df530ec44892407d6382d933ff9ad42dd19df0e"; footprints.sha256 =	"1phynxisha2pq2knbx5l1hkdz1bmjm0qxl3lcb4ab82h8d35r37c"; packages3d.rev =	"6bfd8dfa3adc6ac316b9857977c87f22282c6e24"; packages3d.sha256 =	"0ci9gxbpfnfqwah95ki4qcwlca78s1z6s7hckisnp58a1cm9siya"; </del> <ins> footprints.rev =	"b1dfe894de90b0063befc02b914dc9e2b47e3a62"; footprints.sha256 =	"06kn6c00wlnr33mks582xhadvkbbgmqhb4qc1wjfw264pavz7v7y"; packages3d.rev =	"45df600c5e3dd5113d62e6445115e7c37bdf362f"; packages3d.sha256 =	"0cnrg7mr3khpglviid1adk2ihs1qwj0r7l32z2vqsl8aidzbg9kr"; </ins> }; }; };

Steps to reproduce the behavior: kicad (tested on ) The relevant part of the build log is: Complete build log is here: Setting the flag in the cmake build flags, solves the issue. Please run and paste the result.
thanks for filing an issue i'm not sure what changed to cause this issue, or why that change didn't notify me of the breakage... i'll try to get your fix or something similar in a PR today


Question: <ins> diff --git a/pre_commit/languages/pygrep.py b/pre_commit/languages/pygrep.py index ec55560..44e08a1 100644 --- a/pre_commit/languages/pygrep.py +++ b/pre_commit/languages/pygrep.py @@ -98,7 +98,7 @@ def run_hook( color: bool, ) -> tuple[int, bytes]: cmd = (sys.executable, '-m', __name__, *args, entry) -    return xargs(cmd, file_args, color=color) +    return xargs(cmd, file_args, color=color, env={ "PYTHONPATH": ':'.join(sys.path) }) def main(argv: Sequence[str] | None = None) -> int: </ins>

hooks with work by . This fails because is a plain binary that doesn’t have in its environment. Steps to reproduce the behavior:
A workaround is to use the binary from instead.
It seems the above fix is insufficient. While works correctly, the hook installed into doesn't have the Python environment with the pygrep package. tested on:
Still same problem...
If you pull in the above mentioned into your environment, it should work. For best results, I recommend putting it into your (& use direnv) or systemPackages.
Potential fix which doesn't require changing the python provided in the nix shell:


Question: <ins> { stdenv, mkDerivation, fetchFromGitHub, cmake, pkgconfig, pcsclite, qtsvg, qttools, qtwebsockets , qtquickcontrols2, qtgraphicaleffects }: mkDerivation rec { pname = "AusweisApp2"; version = "1.20.0"; src = fetchFromGitHub { owner = "Governikus"; repo = "AusweisApp2"; rev = "${version}"; sha256 = "0qkwdaxhig4qjim7h20j6ln6w76ycppfc786nd8l69bd1qv46m40"; }; nativeBuildInputs = [ cmake pkgconfig ]; buildInputs = [ qtsvg qttools qtwebsockets qtquickcontrols2 qtgraphicaleffects pcsclite ]; meta = with stdenv.lib; { description = "Authentication software for the German ID card"; downloadPage = "https://github.com/Governikus/AusweisApp2/releases"; homepage = "https://www.ausweisapp.bund.de/ausweisapp2/"; license = licenses.eupl12; maintainers = with maintainers; [ b4dm4n ]; platforms = platforms.linux; }; } </ins>

Project description Client for authenticating to services using a German ID Metadata homepage URL: source URL: license: EUPL platforms: unix, linux, darwin, win32


Question: ''; }) super.haskell-language-server; <ins> # NOTE: this patch updates the hevm code to work with the latest packages that broke the build # it's temporary until hevm version 0.50.0 is released - https://github.com/ethereum/hevm/milestone/1 </ins> # tests depend on a specific version of solc <del> hevm = dontCheck (doJailbreak super.hevm); </del> <ins> hevm = dontCheck (appendPatch ./patches/hevm-update-deps.patch super.hevm); </ins> # hadolint enables static linking by default in the cabal file, so we have to explicitly disable it. # https://github.com/hadolint/hadolint/commit/e1305042c62d52c2af4d77cdce5d62f6a0a3ce7b

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


Question: stdenv.mkDerivation rec { pname = "igraph"; <del> version = "0.7.1"; </del> <ins> version = "0.8.2"; </ins> src = fetchFromGitHub { owner = "igraph"; repo = pname; rev = version; <del> sha256 = "1wsy0r511gk069il6iqjs27q8cjvqz20gf0a7inybx1bw84845z8"; </del> <ins> sha256 = "015yh9s19lmxm7l1ld8adlsqh1lrmzicl801saixdwl9w05hfva4"; </ins> }; nativeBuildInputs = [ pkgconfig autoreconfHook ]; buildInputs = [ flex yacc zlib libxml2 ]; <del> # This file is normally generated by igraph's bootstrap.sh, but we can do it # ourselves. ~ C. </del> <ins> # Normally, igraph wants us to call bootstrap.sh, which will call # tools/getversion.sh. Instead, we're going to put the version directly # where igraph wants, and then let autoreconfHook do the rest of the # bootstrap. ~ C. </ins> postPatch = '' <del> echo "${version}" > VERSION </del> <ins> echo "${version}" > IGRAPH_VERSION </ins> ''; <ins> doCheck = true; </ins> meta = { description = "The network analysis package"; homepage = "https://igraph.org/"; license = lib.licenses.gpl2; <ins> # NB: Known to fail tests on aarch64. platforms = [ "x86_64-linux" ]; </ins> maintainers = [ lib.maintainers.MostAwesomeDude ]; }; }

, CVSSv3=6.5 (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: ; nixos-unstable: . May contain false positives. Cc
I couldn't get the vulnerability to compile and run, so I don't know for sure whether this version bump is actually a fix. Nonetheless, here's a PR.


Question: stdenv.mkDerivation rec { pname = "igraph"; <del> version = "0.7.1"; </del> <ins> version = "0.8.2"; </ins> src = fetchFromGitHub { owner = "igraph"; repo = pname; rev = version; <del> sha256 = "1wsy0r511gk069il6iqjs27q8cjvqz20gf0a7inybx1bw84845z8"; </del> <ins> sha256 = "015yh9s19lmxm7l1ld8adlsqh1lrmzicl801saixdwl9w05hfva4"; </ins> }; nativeBuildInputs = [ pkgconfig autoreconfHook ]; buildInputs = [ flex yacc zlib libxml2 ]; <del> # This file is normally generated by igraph's bootstrap.sh, but we can do it # ourselves. ~ C. </del> <ins> # Normally, igraph wants us to call bootstrap.sh, which will call # tools/getversion.sh. Instead, we're going to put the version directly # where igraph wants, and then let autoreconfHook do the rest of the # bootstrap. ~ C. </ins> postPatch = '' <del> echo "${version}" > VERSION </del> <ins> echo "${version}" > IGRAPH_VERSION </ins> ''; <ins> doCheck = true; </ins> meta = { description = "The network analysis package"; homepage = "https://igraph.org/"; license = lib.licenses.gpl2; <ins> # NB: Known to fail tests on aarch64. platforms = [ "x86_64-linux" ]; </ins> maintainers = [ lib.maintainers.MostAwesomeDude ]; }; }

Describe the bug Build fails when trying to install . I get: To Reproduce Expected behavior The package should install without error. Metadata Maintainer information:
cc
Related to
Tried the following: It doesn't even bother about the C-core Version 6 that I asked: What am I doing wrong ?
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 .
Refreshed. My PR will fix this issue. Thanks for your patience.


Question: <del> { stdenv, fetchFromGitHub, cmake, gmp }: </del> <ins> { stdenv, fetchFromGitHub, cmake, gmp, coreutils }: </ins> stdenv.mkDerivation rec { pname = "lean"; <del> version = "3.10.0"; </del> <ins> version = "3.13.1"; </ins> src = fetchFromGitHub { owner  = "leanprover-community"; repo   = "lean"; rev    = "v${version}"; <del> sha256 = "0nmh09x3scfqg0bg1qf8b7z67s11hbfd7kr1h6k1zw94fyn2mg8q"; </del> <ins> sha256 = "1ak5l40h5yjlbzz92l724l6bm5q341cg6k1yk13sbwn42l8szsar"; </ins> }; nativeBuildInputs = [ cmake ];

Describe the bug on macos fails because it can't find . To Reproduce Steps to reproduce the behavior: lean: leanprover. It bails out with OSX 'readlink' command does not support option '-f', please install 'greadlink'. If you use 'brew', you can install 'greadlink' using 'brew install coreutils' Expected behavior No errors. Additional context This is because leanpkg has an : It can be worked around presently by installing . Options I see for fixing the package: depend on on darwin patch out this check, since (presumably) nix provides the GNU anyway fix this upstream by changing the check to not fail under nix (e.g. by having an explicit check for the argument instead of relying on command name), and pull in the fixed version Metadata system: host os: multi-user?: sandbox: version: channels(rob): nixpkgs:
Sounds most easiest to implement and maintain.


Question: <del> { stdenv, lib, zlib, glib, alsaLib, dbus, gtk2, atk, pango, freetype, fontconfig </del> <ins> { stdenv, lib, zlib, glib, alsaLib, dbus, gtk3, atk, pango, freetype, fontconfig </ins> , libgnome-keyring3, gdk_pixbuf, gvfs, cairo, cups, expat, libgpgerror, nspr , gconf, nss, xorg, libcap, systemd, libnotify, libsecret }: let packages = [ <del> stdenv.cc.cc zlib glib dbus gtk2 atk pango freetype libgnome-keyring3 </del> <ins> stdenv.cc.cc zlib glib dbus gtk3 atk pango freetype libgnome-keyring3 </ins> fontconfig gdk_pixbuf cairo cups expat libgpgerror alsaLib nspr gconf nss xorg.libXrender xorg.libX11 xorg.libXext xorg.libXdamage xorg.libXtst xorg.libXcomposite xorg.libXi xorg.libXfixes xorg.libXrandr

We've had issues with building atom-beautify since This happens now in both Atom and Atom Beta channels. Error for Atom: Error for Atom Beta: Travis CI for your fork Travis CI or a Docker image for nix and checkout master from atom and atom-beta Last successful beta/stable build: https://travis- Last successful stable build: https://travis- Both failed: https://travis-
here is a new issue.
Seems to be related to
For stable maybe, beta is slightly different error.


Question: <ins> { lib , stdenv , fetchFromGitHub , buildPythonPackage , unittestCheckHook , cython , setuptools , wheel , numpy }: buildPythonPackage { pname = "daqp"; version = "0.5.1"; format = "pyproject"; src = fetchFromGitHub { owner = "darnstrom"; repo = "daqp"; rev = "5a15a3d16731d3d50f867218c1b281567db556fd"; hash = "sha256-in7Ci/wM7i0csJ4XVfo1lboWOyfuuU+8E+TzGmMV3x0="; }; sourceRoot = "source/interfaces/daqp-python"; postPatch = '' sed -i 's|../../../daqp|../..|' setup.py sed -i 's|if src_path and os.path.exists(src_path):|if False:|' setup.py ''; nativeCheckInputs = [ unittestCheckHook ]; unittestFlagsArray = [ "-s" "test" "-p" "'*.py'" "-v" ]; nativeBuildInputs = [ cython setuptools wheel ]; propagatedBuildInputs = [ numpy ]; pythonImportsCheck = [ "daqp" ]; meta = with lib; { description = "A dual active-set algorithm for convex quadratic programming"; homepage = "https://github.com/darnstrom/daqp"; license = licenses.mit; maintainers = with maintainers; [ renesat ]; }; } </ins>

Project description qpsolvers is python library for solving quadratic programming problems. It contains wrappers for multiple solvers like osqp, cvxopt, quadprog and much more. Metadata homepage URL: source URL: license: LGPLv3 platforms: platform independent (python3.10)
This package wants new version of and new package - . I will try add PR today, but now you can use my NUR repo if you want:


Question: , nlopt , ipopt , boost <ins> , tbb </ins> }: stdenv.mkDerivation rec { pname = "pagmo2"; <del> version = "2.9"; </del> <ins> version = "2.18.0"; </ins> src = fetchFromGitHub { owner = "esa"; repo = "pagmo2"; rev = "v${version}"; <del> sha256 = "0al2i59m5qr83wz5n5408zvys0b3mc40rszf0l5b9a0gp1axj400"; </del> <ins> sha256 = "0rd8scs4hj6qd8ylmn5hafncml2vr4fvcgm3agz3jrvmnc7hadrj"; </ins> }; nativeBuildInputs = [ cmake ]; <del> buildInputs = [ eigen nlopt ipopt boost ]; </del> <ins> buildInputs = [ eigen nlopt ipopt boost tbb ]; </ins> cmakeFlags = [ "-DPAGMO_BUILD_TESTS=no"

A clear and concise description of what the bug is. The package doesn't include a folder. I am looking for a version of which includes the executable. Are we building the package incorrectly such that it doesn't include a binary? Any and all help/advice is much appreciated :bow: Steps to reproduce the behavior: output - notice there is no folder A clear and concise description of what you expected to happen. I want the executable. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- might know something about this? :man_shrugging:
was the binary there before On a quick note: I have never used , so I am not familiar with the package. It seems that the package also needs an update:
It appears that the binary requires AMPL, a commercial package, which is not packaged in nixpkgs. See: https://coin-
ah, I understand. Thank you.


Question: <ins> # pkgs.appimageTools {#sec-pkgs-appimageTools} `pkgs.appimageTools` is a set of functions for extracting and wrapping [AppImage](https://appimage.org/) files. They are meant to be used if traditional packaging from source is infeasible, or it would take too long. To quickly run an AppImage file, `pkgs.appimage-run` can be used as well. ::: warning The `appimageTools` API is unstable and may be subject to backwards-incompatible changes in the future. ::: ## AppImage formats {#ssec-pkgs-appimageTools-formats} There are different formats for AppImages, see [the specification](https://github.com/AppImage/AppImageSpec/blob/74ad9ca2f94bf864a4a0dac1f369dd4f00bd1c28/draft.md#image-format) for details. - Type 1 images are ISO 9660 files that are also ELF executables. - Type 2 images are ELF executables with an appended filesystem. They can be told apart with `file -k`: ```ShellSession $ file -k type1.AppImage type1.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) ISO 9660 CD-ROM filesystem data 'AppImage' (Lepton 3.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=d629f6099d2344ad82818172add1d38c5e11bc6d, stripped012- data $ file -k type2.AppImage type2.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) (Lepton 3.x), scale 232-60668, spot sensor temperature -4.187500, color scheme 15, show scale bar, calibration: offset -0.000000, slope 0.000000 (Lepton 2.x), scale 4111-45000, spot sensor temperature 412442.250000, color scheme 3, minimum point enabled, calibration: offset -75402534979642766821519867692934234112.000000, slope 5815371847733706829839455140374904832.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=79dcc4e55a61c293c5e19edbd8d65b202842579f, stripped012- data ``` Note how the type 1 AppImage is described as an `ISO 9660 CD-ROM filesystem`, and the type 2 AppImage is not. ## Wrapping {#ssec-pkgs-appimageTools-wrapping} Depending on the type of AppImage you're wrapping, you'll have to use `wrapType1` or `wrapType2`. ```nix appimageTools.wrapType2 { # or wrapType1 name = "patchwork"; src = fetchurl { url = "https://github.com/ssbc/patchwork/releases/download/v3.11.4/Patchwork-3.11.4-linux-x86_64.AppImage"; sha256 = "1blsprpkvm0ws9b96gb36f0rbf8f5jgmw4x6dsb1kswr4ysf591s"; }; extraPkgs = pkgs: with pkgs; [ ]; } ``` - `name` specifies the name of the resulting image. - `src` specifies the AppImage file to extract. - `extraPkgs` allows you to pass a function to include additional packages inside the FHS environment your AppImage is going to run in. There are a few ways to learn which dependencies an application needs: - Looking through the extracted AppImage files, reading its scripts and running `patchelf` and `ldd` on its executables. This can also be done in `appimage-run`, by setting `APPIMAGE_DEBUG_EXEC=bash`. - Running `strace -vfefile` on the wrapped executable, looking for libraries that can't be found. </ins>

This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.


Question: <ins> # pkgs.appimageTools {#sec-pkgs-appimageTools} `pkgs.appimageTools` is a set of functions for extracting and wrapping [AppImage](https://appimage.org/) files. They are meant to be used if traditional packaging from source is infeasible, or it would take too long. To quickly run an AppImage file, `pkgs.appimage-run` can be used as well. ::: warning The `appimageTools` API is unstable and may be subject to backwards-incompatible changes in the future. ::: ## AppImage formats {#ssec-pkgs-appimageTools-formats} There are different formats for AppImages, see [the specification](https://github.com/AppImage/AppImageSpec/blob/74ad9ca2f94bf864a4a0dac1f369dd4f00bd1c28/draft.md#image-format) for details. - Type 1 images are ISO 9660 files that are also ELF executables. - Type 2 images are ELF executables with an appended filesystem. They can be told apart with `file -k`: ```ShellSession $ file -k type1.AppImage type1.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) ISO 9660 CD-ROM filesystem data 'AppImage' (Lepton 3.x), scale 0-0, spot sensor temperature 0.000000, unit celsius, color scheme 0, calibration: offset 0.000000, slope 0.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=d629f6099d2344ad82818172add1d38c5e11bc6d, stripped012- data $ file -k type2.AppImage type2.AppImage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV) (Lepton 3.x), scale 232-60668, spot sensor temperature -4.187500, color scheme 15, show scale bar, calibration: offset -0.000000, slope 0.000000 (Lepton 2.x), scale 4111-45000, spot sensor temperature 412442.250000, color scheme 3, minimum point enabled, calibration: offset -75402534979642766821519867692934234112.000000, slope 5815371847733706829839455140374904832.000000, dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.18, BuildID[sha1]=79dcc4e55a61c293c5e19edbd8d65b202842579f, stripped012- data ``` Note how the type 1 AppImage is described as an `ISO 9660 CD-ROM filesystem`, and the type 2 AppImage is not. ## Wrapping {#ssec-pkgs-appimageTools-wrapping} Depending on the type of AppImage you're wrapping, you'll have to use `wrapType1` or `wrapType2`. ```nix appimageTools.wrapType2 { # or wrapType1 name = "patchwork"; src = fetchurl { url = "https://github.com/ssbc/patchwork/releases/download/v3.11.4/Patchwork-3.11.4-linux-x86_64.AppImage"; sha256 = "1blsprpkvm0ws9b96gb36f0rbf8f5jgmw4x6dsb1kswr4ysf591s"; }; extraPkgs = pkgs: with pkgs; [ ]; } ``` - `name` specifies the name of the resulting image. - `src` specifies the AppImage file to extract. - `extraPkgs` allows you to pass a function to include additional packages inside the FHS environment your AppImage is going to run in. There are a few ways to learn which dependencies an application needs: - Looking through the extracted AppImage files, reading its scripts and running `patchelf` and `ldd` on its executables. This can also be done in `appimage-run`, by setting `APPIMAGE_DEBUG_EXEC=bash`. - Running `strace -vfefile` on the wrapped executable, looking for libraries that can't be found. </ins>

This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I opened a PR here: Thanks in advance for reviewing :-)


Question: ]; disabledTests = [ <del> # Test are failing due to scipy update (removal of scipy.random in 1.9.0) # Is fixed upstream but requires a new release "test_feasibility_problem" </del> <ins> # Need an unfree license package - mkl </ins> "test_issue14" <del> "test_polish_random" "test_polish_unconstrained" "test_primal_and_dual_infeasible_problem" "test_primal_infeasible_problem" "test_solve" "test_unconstrained_problem" "test_update_A_allind" "test_update_A" "test_update_bounds" "test_update_l" "test_update_P_A_allind" "test_update_P_A_indA" "test_update_P_A_indP_indA" "test_update_P_A_indP" "test_update_P_allind" "test_update_P" "test_update_q" "test_update_u" "test_warm_start" </del> ]; meta = with lib; {


Question: lapack blas python3 <ins> (getLib gfortran.cc) # libgfortran.so </ins> ] ++ lists.optionals cudaSupport (with effectiveCudaPackages; [ cuda_cudart # cuda_runtime.h libcublas # cublas_v2.h

tests link to , however is not explicitly included in of . This issue is normally hidden, because (for example) links to and so it is brought along as a transitive dependency of . However, may not always be set to . For example, doesn't link to . As a consequence, applying the following overlay and attempting to build results in the following errors: does list in its , however actually refers to that only includes the wrapped compiler binaries. If my understanding is correct, is provided by instead. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:


Question: <para> This chapter contains information about how to use and maintain the Nix expressions for a number of specific packages, such as the Linux kernel or X.org. </para> <del> <xi:include href="citrix.xml" /> </del> <ins> <xi:include href="citrix.section.xml" /> </ins> <xi:include href="dlib.xml" /> <xi:include href="eclipse.section.xml" /> <xi:include href="elm.section.xml" />

This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. : change to . to . the contents from Docbook to . Follow . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
Hi Opened PR for this.


Question: rustcArgs ? [], strip ? true }: <ins> let darwinArgs = lib.optionals stdenv.isDarwin [ "-L${lib.getLib libiconv}/lib" ]; in </ins> makeBinWriter { compileScript = '' cp "$contentPath" tmp.rs <del> PATH=${makeBinPath [pkgs.gcc]} ${lib.getBin rustc}/bin/rustc ${lib.escapeShellArgs rustcArgs} -o "$out" tmp.rs </del> <ins> PATH=${makeBinPath [pkgs.gcc]} ${lib.getBin rustc}/bin/rustc ${lib.escapeShellArgs rustcArgs} ${lib.escapeShellArgs darwinArgs} -o "$out" tmp.rs </ins> ''; inherit strip; } name;

Describe the bug results in the following error on : Seems like the writer expects to be executed in a stdenv environment to find instead of knowing the path to it. To Reproduce Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (rust maintainers)
This should work as long as GHC is proper dep, because libiconv is propagated.
This should be independent of GHC entirely: only relation to GHC is probably that I mistook the error for one coming from GHC initially, but this is not the case ( doesn't allow building the writers individually what confused me).
I'm facing this issue trying to build from on macOS Big Sur. (wasmer is a dependency of FastAPI, which is the package I'm actually interested in) <details<summaryLogs:</summary</details
I think adding to could also help there.
Fix here:


Question: <del> From d55c3e36094f06bb1fb02f5eac19fdccf1d91f7e Mon Sep 17 00:00:00 2001 From: "H.J. Lu" <hjl.tools@gmail.com> Date: Wed, 8 Aug 2018 06:09:15 -0700 Subject: [PATCH] x86: Properly merge GNU_PROPERTY_X86_ISA_1_USED MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Without the GNU_PROPERTY_X86_ISA_1_USED property, all ISAs may be used. If a bit in the GNU_PROPERTY_X86_ISA_1_USED property is unset, the corresponding x86 instruction set isn’t used.  When merging properties from 2 input files and one input file doesn't have the GNU_PROPERTY_X86_ISA_1_USED property, the output file shouldn't have it neither.  This patch removes the GNU_PROPERTY_X86_ISA_1_USED property if an input file doesn't have it. This patch replaces the GNU_PROPERTY_X86_ISA_1_USED property with the GNU_PROPERTY_X86_ISA_1_NEEDED property which is the minimum ISA requirement. bfd/ PR ld/23486 * elfxx-x86.c (_bfd_x86_elf_merge_gnu_properties): Remove GNU_PROPERTY_X86_ISA_1_USED if an input file doesn't have it. (_bfd_x86_elf_link_setup_gnu_properties): Adding the GNU_PROPERTY_X86_ISA_1_NEEDED, instead of GNU_PROPERTY_X86_ISA_1_USED, property. ld/ PR ld/23486 * testsuite/ld-i386/i386.exp: Run PR ld/23486 tests. * testsuite/ld-x86-64/x86-64.exp: Likewise. * testsuite/ld-i386/pr23486a.d: New file. * testsuite/ld-i386/pr23486b.d: Likewise. * testsuite/ld-x86-64/pr23486a-x32.d: Likewise. * testsuite/ld-x86-64/pr23486a.d: Likewise. * testsuite/ld-x86-64/pr23486a.s: Likewise. * testsuite/ld-x86-64/pr23486b-x32.d: Likewise. * testsuite/ld-x86-64/pr23486b.d: Likewise. * testsuite/ld-x86-64/pr23486b.s: Likewise. * testsuite/ld-i386/property-3.r: Remove "x86 ISA used". * testsuite/ld-i386/property-4.r: Likewise. * testsuite/ld-i386/property-5.r: Likewise. * testsuite/ld-i386/property-x86-ibt3a.d: Likewise. * testsuite/ld-i386/property-x86-ibt3b.d: Likewise. * testsuite/ld-i386/property-x86-shstk3a.d: Likewise. * testsuite/ld-i386/property-x86-shstk3b.d: Likewise. * testsuite/ld-x86-64/property-3.r: Likewise. * testsuite/ld-x86-64/property-4.r: Likewise. * testsuite/ld-x86-64/property-5.r: Likewise. * testsuite/ld-x86-64/property-x86-ibt3a-x32.d: Likewise. * testsuite/ld-x86-64/property-x86-ibt3a.d: Likewise. * testsuite/ld-x86-64/property-x86-ibt3b-x32.d: Likewise. * testsuite/ld-x86-64/property-x86-ibt3b.d: Likewise. * testsuite/ld-x86-64/property-x86-shstk3a-x32.d: Likewise. * testsuite/ld-x86-64/property-x86-shstk3a.d: Likewise. * testsuite/ld-x86-64/property-x86-shstk3b-x32.d: Likewise. * testsuite/ld-x86-64/property-x86-shstk3b.d: Likewise. (cherry picked from commit f7309df20c4e787041cedc4a6aced89c15259e54) --- bfd/elfxx-x86.c                               | 25 ++++++++++++--- ld/testsuite/ld-i386/i386.exp                 |  2 ++ ld/testsuite/ld-i386/pr23486a.d               | 10 ++++++ ld/testsuite/ld-i386/pr23486b.d               | 10 ++++++ ld/testsuite/ld-i386/property-3.r             |  1 - ld/testsuite/ld-i386/property-4.r             |  1 - ld/testsuite/ld-i386/property-5.r             |  1 - ld/testsuite/ld-i386/property-x86-ibt3a.d     |  5 ++- ld/testsuite/ld-i386/property-x86-ibt3b.d     |  5 ++- ld/testsuite/ld-i386/property-x86-shstk3a.d   |  5 ++- ld/testsuite/ld-i386/property-x86-shstk3b.d   |  5 ++- ld/testsuite/ld-x86-64/pr23486a-x32.d         | 10 ++++++ ld/testsuite/ld-x86-64/pr23486a.d             | 10 ++++++ ld/testsuite/ld-x86-64/pr23486a.s             | 30 +++++++++++++++++ ld/testsuite/ld-x86-64/pr23486b-x32.d         | 10 ++++++ ld/testsuite/ld-x86-64/pr23486b.d             | 10 ++++++ ld/testsuite/ld-x86-64/pr23486b.s             | 30 +++++++++++++++++ ld/testsuite/ld-x86-64/property-3.r           |  1 - ld/testsuite/ld-x86-64/property-4.r           |  1 - ld/testsuite/ld-x86-64/property-5.r           |  1 - .../ld-x86-64/property-x86-ibt3a-x32.d        |  5 ++- ld/testsuite/ld-x86-64/property-x86-ibt3a.d   |  5 ++- .../ld-x86-64/property-x86-ibt3b-x32.d        |  5 ++- ld/testsuite/ld-x86-64/property-x86-ibt3b.d   |  5 ++- .../ld-x86-64/property-x86-shstk3a-x32.d      |  5 ++- ld/testsuite/ld-x86-64/property-x86-shstk3a.d |  5 ++- .../ld-x86-64/property-x86-shstk3b-x32.d      |  5 ++- ld/testsuite/ld-x86-64/property-x86-shstk3b.d |  5 ++- ld/testsuite/ld-x86-64/x86-64.exp             |  4 +++ 31 files changed, 211 insertions(+), 47 deletions(-) create mode 100644 ld/testsuite/ld-i386/pr23486a.d create mode 100644 ld/testsuite/ld-i386/pr23486b.d create mode 100644 ld/testsuite/ld-x86-64/pr23486a-x32.d create mode 100644 ld/testsuite/ld-x86-64/pr23486a.d create mode 100644 ld/testsuite/ld-x86-64/pr23486a.s create mode 100644 ld/testsuite/ld-x86-64/pr23486b-x32.d create mode 100644 ld/testsuite/ld-x86-64/pr23486b.d create mode 100644 ld/testsuite/ld-x86-64/pr23486b.s --- a/bfd/elfxx-x86.c +++ b/bfd/elfxx-x86.c @@ -2407,12 +2407,27 @@ _bfd_x86_elf_merge_gnu_properties (struct bfd_link_info *info, switch (pr_type) { case GNU_PROPERTY_X86_ISA_1_USED: +      if (aprop == NULL || bprop == NULL) +	{ +	  /* Only one of APROP and BPROP can be NULL.  */ +	  if (aprop != NULL) +	    { +	      /* Remove this property since the other input file doesn't +		 have it.  */ +	      aprop->pr_kind = property_remove; +	      updated = TRUE; +	    } +	  break; +	} +      goto or_property; + case GNU_PROPERTY_X86_ISA_1_NEEDED: if (aprop != NULL && bprop != NULL) { +or_property: number = aprop->u.number; aprop->u.number = number | bprop->u.number; -	  /* Remove the property if ISA bits are empty.  */ +	  /* Remove the property if all bits are empty.  */ if (aprop->u.number == 0) { aprop->pr_kind = property_remove; @@ -2428,14 +2443,14 @@ _bfd_x86_elf_merge_gnu_properties (struct bfd_link_info *info, { if (aprop->u.number == 0) { -		  /* Remove APROP if ISA bits are empty.  */ +		  /* Remove APROP if all bits are empty.  */ aprop->pr_kind = property_remove; updated = TRUE; } } else { -	      /* Return TRUE if APROP is NULL and ISA bits of BPROP +	      /* Return TRUE if APROP is NULL and all bits of BPROP aren't empty to indicate that BPROP should be added to ABFD.  */ updated = bprop->u.number != 0; @@ -2582,9 +2597,9 @@ _bfd_x86_elf_link_setup_gnu_properties { /* If the separate code program header is needed, make sure that the first read-only PT_LOAD segment has no code by -	     adding a GNU_PROPERTY_X86_ISA_1_USED note.  */ +	     adding a GNU_PROPERTY_X86_ISA_1_NEEDED note.  */ prop = _bfd_elf_get_property (ebfd, -					GNU_PROPERTY_X86_ISA_1_USED, +					GNU_PROPERTY_X86_ISA_1_NEEDED, 4); prop->u.number = GNU_PROPERTY_X86_ISA_1_486; prop->pr_kind = property_number; diff --git a/ld/testsuite/ld-i386/i386.exp b/ld/testsuite/ld-i386/i386.exp index 6d794fe653..78dad02579 100644 --- a/ld/testsuite/ld-i386/i386.exp +++ b/ld/testsuite/ld-i386/i386.exp @@ -462,6 +462,8 @@ run_dump_test "pr23189" run_dump_test "pr23194" run_dump_test "pr23372a" run_dump_test "pr23372b" +run_dump_test "pr23486a" +run_dump_test "pr23486b" if { !([istarget "i?86-*-linux*"] || [istarget "i?86-*-gnu*"] diff --git a/ld/testsuite/ld-i386/pr23486a.d b/ld/testsuite/ld-i386/pr23486a.d new file mode 100644 index 0000000000..41a6dcf7d5 --- /dev/null +++ b/ld/testsuite/ld-i386/pr23486a.d @@ -0,0 +1,10 @@ +#source: ../ld-x86-64/pr23486a.s +#source: ../ld-x86-64/pr23486b.s +#as: --32 +#ld: -r -m elf_i386 +#readelf: -n + +Displaying notes found in: .note.gnu.property +  Owner                 Data size	Description +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586 diff --git a/ld/testsuite/ld-i386/pr23486b.d b/ld/testsuite/ld-i386/pr23486b.d new file mode 100644 index 0000000000..08019b7274 --- /dev/null +++ b/ld/testsuite/ld-i386/pr23486b.d @@ -0,0 +1,10 @@ +#source: ../ld-x86-64/pr23486b.s +#source: ../ld-x86-64/pr23486a.s +#as: --32 +#ld: -r -m elf_i386 +#readelf: -n + +Displaying notes found in: .note.gnu.property +  Owner                 Data size	Description +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586 diff --git a/ld/testsuite/ld-i386/property-3.r b/ld/testsuite/ld-i386/property-3.r index 0ed91f5922..d03203c1e5 100644 --- a/ld/testsuite/ld-i386/property-3.r +++ b/ld/testsuite/ld-i386/property-3.r @@ -3,6 +3,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description GNU                  0x[0-9a-f]+	NT_GNU_PROPERTY_TYPE_0 Properties: stack size: 0x800000 -	x86 ISA used: 586, SSE x86 ISA needed: i486, 586 #pass diff --git a/ld/testsuite/ld-i386/property-4.r b/ld/testsuite/ld-i386/property-4.r index cb2bc15d9a..da295eb6c7 100644 --- a/ld/testsuite/ld-i386/property-4.r +++ b/ld/testsuite/ld-i386/property-4.r @@ -3,6 +3,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description GNU                  0x[0-9a-f]+	NT_GNU_PROPERTY_TYPE_0 Properties: stack size: 0x800000 -	x86 ISA used: i486, 586, SSE x86 ISA needed: i486, 586, SSE #pass diff --git a/ld/testsuite/ld-i386/property-5.r b/ld/testsuite/ld-i386/property-5.r index 552965058c..e4141594b3 100644 --- a/ld/testsuite/ld-i386/property-5.r +++ b/ld/testsuite/ld-i386/property-5.r @@ -3,6 +3,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description GNU                  0x[0-9a-f]+	NT_GNU_PROPERTY_TYPE_0 Properties: stack size: 0x900000 -	x86 ISA used: i486, 586, SSE x86 ISA needed: i486, 586, SSE #pass diff --git a/ld/testsuite/ld-i386/property-x86-ibt3a.d b/ld/testsuite/ld-i386/property-x86-ibt3a.d index 4bb35b00fb..0aedea1614 100644 --- a/ld/testsuite/ld-i386/property-x86-ibt3a.d +++ b/ld/testsuite/ld-i386/property-x86-ibt3a.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: i486, 586, SSE2, SSE3 -	x86 ISA needed: 586, SSE, SSE3, SSE4_1 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: 586, SSE, SSE3, SSE4_1 diff --git a/ld/testsuite/ld-i386/property-x86-ibt3b.d b/ld/testsuite/ld-i386/property-x86-ibt3b.d index 418d58a8f7..bd69ac6478 100644 --- a/ld/testsuite/ld-i386/property-x86-ibt3b.d +++ b/ld/testsuite/ld-i386/property-x86-ibt3b.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: i486, 586, SSE2, SSE3 -	x86 ISA needed: 586, SSE, SSE3, SSE4_1 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: 586, SSE, SSE3, SSE4_1 diff --git a/ld/testsuite/ld-i386/property-x86-shstk3a.d b/ld/testsuite/ld-i386/property-x86-shstk3a.d index e261038f60..76d2a39f2c 100644 --- a/ld/testsuite/ld-i386/property-x86-shstk3a.d +++ b/ld/testsuite/ld-i386/property-x86-shstk3a.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: i486, 586, SSE2, SSE3 -	x86 ISA needed: 586, SSE, SSE3, SSE4_1 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: 586, SSE, SSE3, SSE4_1 diff --git a/ld/testsuite/ld-i386/property-x86-shstk3b.d b/ld/testsuite/ld-i386/property-x86-shstk3b.d index 25f3d2361e..e770ecffa5 100644 --- a/ld/testsuite/ld-i386/property-x86-shstk3b.d +++ b/ld/testsuite/ld-i386/property-x86-shstk3b.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: i486, 586, SSE2, SSE3 -	x86 ISA needed: 586, SSE, SSE3, SSE4_1 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: 586, SSE, SSE3, SSE4_1 diff --git a/ld/testsuite/ld-x86-64/pr23486a-x32.d b/ld/testsuite/ld-x86-64/pr23486a-x32.d new file mode 100644 index 0000000000..6d9fa68cdb --- /dev/null +++ b/ld/testsuite/ld-x86-64/pr23486a-x32.d @@ -0,0 +1,10 @@ +#source: pr23486a.s +#source: pr23486b.s +#as: --x32 +#ld: -r -m elf32_x86_64 +#readelf: -n + +Displaying notes found in: .note.gnu.property +  Owner                 Data size	Description +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586 diff --git a/ld/testsuite/ld-x86-64/pr23486a.d b/ld/testsuite/ld-x86-64/pr23486a.d new file mode 100644 index 0000000000..dc2b7bf760 --- /dev/null +++ b/ld/testsuite/ld-x86-64/pr23486a.d @@ -0,0 +1,10 @@ +#source: pr23486a.s +#source: pr23486b.s +#as: --64 -defsym __64_bit__=1 +#ld: -r -m elf_x86_64 +#readelf: -n + +Displaying notes found in: .note.gnu.property +  Owner                 Data size	Description +  GNU                  0x00000010	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586 diff --git a/ld/testsuite/ld-x86-64/pr23486a.s b/ld/testsuite/ld-x86-64/pr23486a.s new file mode 100644 index 0000000000..a07d0c7ced --- /dev/null +++ b/ld/testsuite/ld-x86-64/pr23486a.s @@ -0,0 +1,30 @@ +	.section ".note.gnu.property", "a" +.ifdef __64_bit__ +	.p2align 3 +.else +	.p2align 2 +.endif +	.long 1f - 0f		/* name length.  */ +	.long 4f - 1f		/* data length.  */ +	/* NT_GNU_PROPERTY_TYPE_0 */ +	.long 5			/* note type.  */ +0: +	.asciz "GNU"		/* vendor name.  */ +1: +.ifdef __64_bit__ +	.p2align 3 +.else +	.p2align 2 +.endif +	/* GNU_PROPERTY_X86_ISA_1_USED */ +	.long 0xc0000000	/* pr_type.  */ +	.long 3f - 2f		/* pr_datasz.  */ +2: +	.long 0xa +3: +.ifdef __64_bit__ +	.p2align 3 +.else +	.p2align 2 +.endif +4: diff --git a/ld/testsuite/ld-x86-64/pr23486b-x32.d b/ld/testsuite/ld-x86-64/pr23486b-x32.d new file mode 100644 index 0000000000..0445e69d82 --- /dev/null +++ b/ld/testsuite/ld-x86-64/pr23486b-x32.d @@ -0,0 +1,10 @@ +#source: pr23486b.s +#source: pr23486a.s +#as: --x32 +#ld: -r -m elf32_x86_64 +#readelf: -n + +Displaying notes found in: .note.gnu.property +  Owner                 Data size	Description +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586 diff --git a/ld/testsuite/ld-x86-64/pr23486b.d b/ld/testsuite/ld-x86-64/pr23486b.d new file mode 100644 index 0000000000..dc2b7bf760 --- /dev/null +++ b/ld/testsuite/ld-x86-64/pr23486b.d @@ -0,0 +1,10 @@ +#source: pr23486a.s +#source: pr23486b.s +#as: --64 -defsym __64_bit__=1 +#ld: -r -m elf_x86_64 +#readelf: -n + +Displaying notes found in: .note.gnu.property +  Owner                 Data size	Description +  GNU                  0x00000010	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586 diff --git a/ld/testsuite/ld-x86-64/pr23486b.s b/ld/testsuite/ld-x86-64/pr23486b.s new file mode 100644 index 0000000000..c5167eeb65 --- /dev/null +++ b/ld/testsuite/ld-x86-64/pr23486b.s @@ -0,0 +1,30 @@ +	.section ".note.gnu.property", "a" +.ifdef __64_bit__ +	.p2align 3 +.else +	.p2align 2 +.endif +	.long 1f - 0f		/* name length.  */ +	.long 4f - 1f		/* data length.  */ +	/* NT_GNU_PROPERTY_TYPE_0 */ +	.long 5			/* note type.  */ +0: +	.asciz "GNU"		/* vendor name.  */ +1: +.ifdef __64_bit__ +	.p2align 3 +.else +	.p2align 2 +.endif +	/* GNU_PROPERTY_X86_ISA_1_NEEDED */ +	.long 0xc0000001	/* pr_type.  */ +	.long 3f - 2f		/* pr_datasz.  */ +2: +	.long 0x3 +3: +.ifdef __64_bit__ +	.p2align 3 +.else +	.p2align 2 +.endif +4: diff --git a/ld/testsuite/ld-x86-64/property-3.r b/ld/testsuite/ld-x86-64/property-3.r index 0ed91f5922..d03203c1e5 100644 --- a/ld/testsuite/ld-x86-64/property-3.r +++ b/ld/testsuite/ld-x86-64/property-3.r @@ -3,6 +3,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description GNU                  0x[0-9a-f]+	NT_GNU_PROPERTY_TYPE_0 Properties: stack size: 0x800000 -	x86 ISA used: 586, SSE x86 ISA needed: i486, 586 #pass diff --git a/ld/testsuite/ld-x86-64/property-4.r b/ld/testsuite/ld-x86-64/property-4.r index cb2bc15d9a..da295eb6c7 100644 --- a/ld/testsuite/ld-x86-64/property-4.r +++ b/ld/testsuite/ld-x86-64/property-4.r @@ -3,6 +3,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description GNU                  0x[0-9a-f]+	NT_GNU_PROPERTY_TYPE_0 Properties: stack size: 0x800000 -	x86 ISA used: i486, 586, SSE x86 ISA needed: i486, 586, SSE #pass diff --git a/ld/testsuite/ld-x86-64/property-5.r b/ld/testsuite/ld-x86-64/property-5.r index 552965058c..e4141594b3 100644 --- a/ld/testsuite/ld-x86-64/property-5.r +++ b/ld/testsuite/ld-x86-64/property-5.r @@ -3,6 +3,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description GNU                  0x[0-9a-f]+	NT_GNU_PROPERTY_TYPE_0 Properties: stack size: 0x900000 -	x86 ISA used: i486, 586, SSE x86 ISA needed: i486, 586, SSE #pass diff --git a/ld/testsuite/ld-x86-64/property-x86-ibt3a-x32.d b/ld/testsuite/ld-x86-64/property-x86-ibt3a-x32.d index 011426f5a4..4cec728dc7 100644 --- a/ld/testsuite/ld-x86-64/property-x86-ibt3a-x32.d +++ b/ld/testsuite/ld-x86-64/property-x86-ibt3a-x32.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-ibt3a.d b/ld/testsuite/ld-x86-64/property-x86-ibt3a.d index 1b4229a037..a8df49a351 100644 --- a/ld/testsuite/ld-x86-64/property-x86-ibt3a.d +++ b/ld/testsuite/ld-x86-64/property-x86-ibt3a.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000020	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x00000010	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-ibt3b-x32.d b/ld/testsuite/ld-x86-64/property-x86-ibt3b-x32.d index 290ed6abf1..c112626711 100644 --- a/ld/testsuite/ld-x86-64/property-x86-ibt3b-x32.d +++ b/ld/testsuite/ld-x86-64/property-x86-ibt3b-x32.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-ibt3b.d b/ld/testsuite/ld-x86-64/property-x86-ibt3b.d index 1142e03272..f10dffdc2c 100644 --- a/ld/testsuite/ld-x86-64/property-x86-ibt3b.d +++ b/ld/testsuite/ld-x86-64/property-x86-ibt3b.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000020	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x00000010	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-shstk3a-x32.d b/ld/testsuite/ld-x86-64/property-x86-shstk3a-x32.d index 819542d181..0147a3c7b6 100644 --- a/ld/testsuite/ld-x86-64/property-x86-shstk3a-x32.d +++ b/ld/testsuite/ld-x86-64/property-x86-shstk3a-x32.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-shstk3a.d b/ld/testsuite/ld-x86-64/property-x86-shstk3a.d index 4c5d0e0a18..1f8c2dc929 100644 --- a/ld/testsuite/ld-x86-64/property-x86-shstk3a.d +++ b/ld/testsuite/ld-x86-64/property-x86-shstk3a.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000020	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x00000010	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-shstk3b-x32.d b/ld/testsuite/ld-x86-64/property-x86-shstk3b-x32.d index ba181e0bc5..7ca2539ca5 100644 --- a/ld/testsuite/ld-x86-64/property-x86-shstk3b-x32.d +++ b/ld/testsuite/ld-x86-64/property-x86-shstk3b-x32.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000018	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x0000000c	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/property-x86-shstk3b.d b/ld/testsuite/ld-x86-64/property-x86-shstk3b.d index 5216f385dd..f66a40e449 100644 --- a/ld/testsuite/ld-x86-64/property-x86-shstk3b.d +++ b/ld/testsuite/ld-x86-64/property-x86-shstk3b.d @@ -6,6 +6,5 @@ Displaying notes found in: .note.gnu.property Owner                 Data size	Description -  GNU                  0x00000020	NT_GNU_PROPERTY_TYPE_0 -      Properties: x86 ISA used: 586, SSE, SSE3, SSE4_1 -	x86 ISA needed: i486, 586, SSE2, SSE3 +  GNU                  0x00000010	NT_GNU_PROPERTY_TYPE_0 +      Properties: x86 ISA needed: i486, 586, SSE2, SSE3 diff --git a/ld/testsuite/ld-x86-64/x86-64.exp b/ld/testsuite/ld-x86-64/x86-64.exp index 6edb9e86f4..ae21e554ad 100644 --- a/ld/testsuite/ld-x86-64/x86-64.exp +++ b/ld/testsuite/ld-x86-64/x86-64.exp @@ -403,6 +403,10 @@ run_dump_test "pr23372a" run_dump_test "pr23372a-x32" run_dump_test "pr23372b" run_dump_test "pr23372b-x32" +run_dump_test "pr23486a" +run_dump_test "pr23486a-x32" +run_dump_test "pr23486b" +run_dump_test "pr23486b-x32" if { ![istarget "x86_64-*-linux*"] && ![istarget "x86_64-*-nacl*"]} { return -- 2.20.1 </del>

Describe the bug is currently in nixpkgs master. It was released in July 2018. was released in October 2019. It contains a few improvements and may also contains fix for some vulnerabilities: Is there a reason to keep the old version in nixpkgs, other than a lack of manpower? I'd be happy to do this work, but I just want to be sure that I was not starting a long, difficult and redundant work. I already tried a "naive" bump of the and but it does not work, mostly because most of the patchs are not valid anymore.
This was solved by cc.
Thank you for continuing this work!