jiebi/CodeConvo huggingface dataset:
Change:
- The `nomad` package now defaults to a 1.1.x release instead of 1.0.x <ins> - If `exfat` is included in `boot.supportedFilesystems` and when using kernel 5.7 or later, the `exfatprogs` user-space utilities are used instead of `exfat`. </ins> ## Other Notable Changes {#sec-release-21.11-notable-changes} - The setting [`services.openssh.logLevel`](options.html#opt-services.openssh.logLevel) `"VERBOSE"` `"INFO"`. This brings NixOS in line with upstream and other Linux distributions, and reduces log spam on servers due to bruteforcing botnets.

Discussion:
Describe the bug On kernels newer than 5.8 exfat is natively supported by the kernel. However, if is used, nix will pull in exfat package and will use the fuse driver. This can be bypassed by not using the type and mounting by hand (there is no link for , but works still). To Reproduce Steps to reproduce the behavior: an exfat volume it to the attribute, e.g. that filesystem type is using . Expected behavior Using native kernel module for mounting exfat filesystems when kernel version is newer than 5.8. Additional context A check alike this already exists for the package () It seems that the check in could be responsible for this. Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
should be for proper userspace to go with the new in kernel driver
Just got bitten by this on . Both FUSE and native can coexist, but if (from the package) is in the path, the utility will prefer it unless called with the flag (even with ). As there's no way to disable the utility from being built from current exfat, I suggest we switch to (I can submit a PR to package this) for applicable kernels.
Can confirm this behavior, having exfatprogs with newer kernels is definitely recommended.
Change:
rm test/conftest.py ''; <ins> nativeBuildInputs = [ setuptools pythonRelaxDepsHook ]; </ins> propagatedBuildInputs = [ pandas numpy

Discussion:
Steps to reproduce the behavior: stanio bump caused a build faliure. <!-- 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]:
It turns out it's actually an issue with he python package. It looks like the fact that uses the new builder made it so that it even if builds without complaining (probably something to do with the legacy builder), trying to include it as a dependency of will detect the version error. I'll try to open a PR, which updates to use the new builder (and I'll relax the dependency constraint too).
Thank you Toma for fast response and resolution!
Change:
set +h ${cfg.promptInit} <del> ${bashCompletion} ${lsColors} </del> <ins> ${cfg.promptPluginInit} </ins> ${bashAliases} ${cfge.interactiveShellInit}

Discussion:
Project description A bash utility; "Notifies you when long-running terminal commands complete." Metadata homepage URL: license: "All of undistract-me, including this file, is made available with the Expat license. See LICENSE for details."
Change:
openbabel = callPackage ../development/libraries/openbabel { inherit (self) python; }; }; <ins> opencensus = callPackage ../development/python-modules/opencensus { }; </ins> opencv3 = toPythonModule (pkgs.opencv3.override { enablePython = true; pythonPackages = self;

Discussion:
Project description Ray is a fast and simple framework for building and running distributed applications. It is packaged with RLlib, a scalable reinforcement learning library. The project provides a wheel at , but according to NixOs is by default not compatible. Metadata homepage URL: source URL: license: apache2 platforms: unix, linux
I'm interested in this as well, when I try to use any sort of non-local mode with ray installed in a nix-shell environment via pip, it throws errors launching redis. Even though redis-server exists at the aforemention path. It fails to launch when I attempt to execute redis directly.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I haven't tested, but since manylinux1 is available by default now (), does it work on your machine on the latest unstable?
I still have the issue with redis unfortunately
this seems to work
I see, the s fixed it.
I marked this as stale due to inactivity. &rarr;
Still important to me.
I marked this as stale due to inactivity. &rarr;
In case anyone is still looking for this - it is packaged in python-on-nix
Change:
# find editline/gmp. stdenv.lib.optionalString stdenv.isLinux '' mkdir -p "$out/lib" <del> ln -sv "${ncurses.out}/lib/libncurses.so" "$out/lib/libncurses${stdenv.lib.optionalString stdenv.is64bit "w"}.so.5" </del> <ins> ln -sv "${ncurses5.out}/lib/libncurses.so" "$out/lib/libncurses${stdenv.lib.optionalString stdenv.is64bit "w"}.so.5" </ins> find . -type f -perm -0100  -exec patchelf --interpreter "$(cat $NIX_CC/nix-support/dynamic-linker)"  --set-rpath "$out/lib:${gmp.out}/lib" {} ;

Discussion:
Commit from broke haskell.compiler.ghc6102Binary haskell.compiler.ghc704Binary and therefore the packages haskell.compiler.ghc6104 haskell.compiler.ghc704 haskell.compiler.ghc722 haskell.compiler.ghc742 haskell.compiler.ghc763 which depend on them.
Please try . I test-built the binary GHCs but no further.
Aha. I relied on the update being API-compatible, but the first bootstraping steps don't recompile...
I'm test-building the whole list above.
All succeeded on x86_64-linux.
Change:
postInstall = '' substituteInPlace $out/lib/pkgconfig/${pname}.pc  <del> --replace "''${prefix}" "" </del> <ins> --replace "''${prefix}/" "" </ins> ''; doCheck = true;

Discussion:
tblite is unusable in python at the moment, failing with I think this is due to incorrect pkgconfig setups - look at which is correct and outputs vs which is missing the trailing Which results in a pkgconfig of Steps to reproduce the behavior: a nix environment with the python interpreter, run failure A clear and concise description of what you expected to happen. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. Please run and paste the result.
i'm having the exact same issue as well :'(
Change:
<del> { lib, fetchFromGitLab, buildGoModule, scdoc, nix-update-script }: </del> <ins> { lib , fetchFromGitLab , buildGoModule , scdoc , nix-update-script }: </ins> buildGoModule rec { pname = "darkman"; <del> version = "1.5.4"; </del> <ins> version = "2.0.1"; </ins> src = fetchFromGitLab { owner = "WhyNotHugo"; repo = "darkman"; rev = "v${version}"; <del> sha256 = "sha256-6SNXVe6EfVwcXH9O6BxNw+v4/uhKhCtVS3XE2GTc2Sc="; </del> <ins> sha256 = "sha256-FaEpVy/0PqY5Bmw00hMyFZb9wcwYwEuCKMatYN8Xk3o="; </ins> }; <del> vendorHash = "sha256-xEPmNnaDwFU4l2G4cMvtNeQ9KneF5g9ViQSFrDkrafY="; nativeBuildInputs = [ scdoc ]; </del> <ins> patches = [ ./go-mod.patch ./makefile.patch ]; </ins> postPatch = '' substituteInPlace darkman.service  <del> --replace "/usr/bin/darkman" "$out/bin/darkman" </del> <ins> --replace-fail /usr/bin/darkman $out/bin/darkman </ins> substituteInPlace contrib/dbus/nl.whynothugo.darkman.service  <del> --replace "/usr/bin/darkman" "$out/bin/darkman" </del> <ins> --replace-fail /usr/bin/darkman $out/bin/darkman </ins> substituteInPlace contrib/dbus/org.freedesktop.impl.portal.desktop.darkman.service  <del> --replace "/usr/bin/darkman" "$out/bin/darkman" </del> <ins> --replace-fail /usr/bin/darkman $out/bin/darkman </ins> ''; <ins> vendorHash = "sha256-3lILSVm7mtquCdR7+cDMuDpHihG+gDJTcQa1cM2o7ZU="; nativeBuildInputs = [ scdoc ]; </ins> buildPhase = '' runHook preBuild make build

Discussion:
Package name: darkman Latest released version: 2.0.1 Current version on the unstable channel: 1.5.4 Current version on the stable/release channel: 1.5.4 Notify maintainers Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Updating this package will resolve nix-community/home-manager too.
I've had a go at updating this but failed at the same point as . I don't know enough about nix or go to take it any further right now though. The part of the go language framework seems to be using a really old version of go (1.16) to try to build the package, which is not able to compile the code:
Change:
<del> { lib, stdenv </del> <ins> { lib , stdenv </ins> , fetchFromGitHub <ins> , fetchpatch </ins> , pkg-config , cmake , zlib

Discussion:
Steps to reproduce the behavior: See . Regression of Blocks: Blocks: porting GSound and GNOME Clocks to macOS Notify upstream: libproxy/libproxy <!-- 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.
A possible fix:
That looks like an upstream bug – the build system should never use functions it is undefining. And either way, on Darwin, I would expect system JavaScriptCore to be used instead of Duktape.
Change:
]; })) <del> (patchExtension "unite@hardpixel.eu" (old: { buildInputs = [ xprop ]; meta.maintainers = with lib.maintainers; [ rhoriguchi ]; })) </del> (patchExtension "x11gestures@joseexposito.github.io" (old: { # Extension can't find Touchegg # https://github.com/NixOS/nixpkgs/issues/137621

Discussion:
Package name: Latest released version: 77 <!-- Search your package here: --- Current version on the unstable channel: 72 Current version on the stable/release channel: 70 <!-- 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. -- Thanks a lot! Note for maintainers: Please tag this issue in your PR. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> { lib , buildPythonPackage , fetchPypi , pythonOlder , setuptools , numpy </del> <ins> { lib, buildPythonPackage, fetchPypi, pythonOlder, setuptools, numpy, </ins> }: buildPythonPackage rec {

Discussion:
Minimal flake to reproduce the issue: : : Disabling install checks using fixes the issue. If you uncomment the commented overlay in the minimal flake I provided, the build will succeed and the package will work properly.
+1 Same issue with same log. (tagging, as you are in maintainers list)
Looks like a bug upstream:
As per the Biopython issue linked, Debian sid is failing in the same way. Specifically, converting two annotated sequence files (one in EMBL format, one in Genbank format) into SeqXML format and then attempting to read this XML file back fails. Narrower tests from that issue: File expected is here (with .txt to the filename): This seems to fail (but shouldn't): This appears to be something breaking via the XML SAX expat parser. Can you see anything relevant which has changed on your platform to help narrow this down?
Hi, I tracked this issue down to a upgrade from 2.5.0 to 2.6.1 from Debian testing to sid. [Debian CI] suggests this could also cause regression in Python tests. Is this consistent with what you observe on Nix? If so, I strongly believe the root cause of the Biopython issue is ingrained in a bad interaction between the newer expat version and the Python interpreter, notably: [Debian CI]: In hope this helps, Étienne.
I can confirm that latest 1.84-dev works. We have to wait for update to be tagged. Until then, you can modify on to use
We have a few NumPy 2.0 test incompatibilities to fix (due to their scalar repr changes), and then we want to release Biopython 1.84 which would include the libexpat fix (moving a close earlier):
Change:
sourceVersion = { major = "3"; minor = "12"; <del> patch = "3"; </del> <ins> patch = "4"; </ins> suffix = ""; }; <del> hash = "sha256-Vr/vH9/BIhzmcg5DpmHj60F4XdkUzplpjYx4lq9L2qE="; </del> <ins> hash = "sha256-9tQZpth0OrJnAIAbSQjSbZfouYbhT5XeMbMt4rDnlVQ="; </ins> inherit (darwin) configd; inherit passthruFun; };

Discussion:
Package name: python312 Latest released version: 3.12.4 <!-- Search your package here: --- Current version on the unstable channel: 3.12.3 Current version on the stable/release channel: 3.12.3 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> { appimageTools, lib, fetchurl, version, sha256 }: let pname = "losslesscut"; nameRepo = "lossless-cut"; nameCamel = "LosslessCut"; name = "${pname}-${version}"; nameSource = "${nameCamel}-linux-x86_64.AppImage"; nameExecutable = "losslesscut"; owner = "mifi"; src = fetchurl { url = "https://github.com/${owner}/${nameRepo}/releases/download/v${version}/${nameSource}"; name = nameSource; inherit sha256; }; extracted = appimageTools.extractType2 { inherit name src; }; in appimageTools.wrapType2 { inherit name src; profile = '' export LC_ALL=C.UTF-8 ''; extraPkgs = ps: appimageTools.defaultFhsEnvArgs.multiPkgs ps; extraInstallCommands = '' mv $out/bin/{${name},${nameExecutable}} ( mkdir -p $out/share cd ${extracted}/usr find share -mindepth 1 -type d -exec mkdir -p $out/{} ; find share -mindepth 1 -type f,l -exec ln -s $PWD/{} $out/{} ; ) ln -s ${extracted}/${nameExecutable}.png $out/share/icons/${nameExecutable}.png mkdir $out/share/applications cp ${extracted}/${nameExecutable}.desktop $out/share/applications substituteInPlace $out/share/applications/${nameExecutable}.desktop  --replace AppRun ${nameExecutable} ''; meta.platforms = with lib.platforms; [ "x86_64-linux" ]; } </del>

Discussion:
Losslesscut crashes at startup due to missing Steps to reproduce the behavior: # crash # works Losslesscut works out-of-the-box. probably just needs a in .
It seems to come from a sandboxing feature of Chromium. (LosslessCut is an Electron app, and Electron uses Chromium, IIUC.) I'll add the flag when I'm available. Should it be to both the Linux and the Darwin binary, or just to the former?
I was only able to test on Linux. While you're at it: When bumping the version, filenames need a change (only tested for Linux): and is still open.
Thank you for reminding! After a quick test, 3.43.0 does run out-of-the-box on my machine Does it crash because the user namespaces is unavailable? Does the same problem happen to , it is another electron app packaged the same way. Does it happen to itself?
I can confirm that it works ootb on NixOS 21.11, but not on 22.05. Caprine crashes in a similar way on NixOS 22.05: Chromium works on both.
How about onlyoffice-bin? If does work, it might have something to do with .
works on 22.05
I'm working on it, but couldn't find a way to call in . To be exact, I don't know how to inject the dependency , a setup hook, into the builder. How should I do it? Thanks a lot for your patience.
Is this issue still relevant?
Last time I checked: Yes. I've got this still on my list and will close in case it is resolved.
It should now be fixed in .
Confirmed.
Change:
<del> # TODO: get rid of this (https://github.com/NixOS/nixpkgs/issues/32883) { stdenv, lib, fetchurl, cmake, ninja, pkgconfig, libiconv, libintlOrEmpty , zlib, curl, cairo, freetype, fontconfig, lcms2, libjpeg, openjpeg , poppler_data, qt4 }: let # Last version supporting QT4 version = "0.61.1"; in stdenv.mkDerivation rec { name = "poppler-qt4-${version}"; src = fetchurl { url = "${meta.homepage}/poppler-${version}.tar.xz"; sha256 = "1afdrxxkaivvviazxkg5blsf2x24sjkfj92ib0d3q5pm8dihjrhj"; }; outputs = [ "out" "dev" ]; buildInputs = [ libiconv poppler_data ] ++ libintlOrEmpty; propagatedBuildInputs = [ zlib freetype fontconfig libjpeg openjpeg cairo lcms2 curl qt4 ]; nativeBuildInputs = [ cmake ninja pkgconfig ]; cmakeFlags = [ "-DENABLE_XPDF_HEADERS=on" "-DENABLE_UTILS=off" ]; meta = with lib; { homepage = https://poppler.freedesktop.org/; description = "A PDF rendering library"; longDescription = '' Poppler is a PDF rendering library based on the xpdf-3.0 code base. ''; license = licenses.gpl2; platforms = platforms.all; maintainers = with maintainers; [ ttuegel ]; }; } </del>

Discussion:
Recently released removes the QT4 support. For now, we will split the package and keep on 0.61.
It is still used so it should remain at an older version.
~It's used just in two packages, apparently ( and ).~ Hopefully those can be soon migrated to Qt5. Otherwise we can keep old version for only and keep updating the rest...
Those are only python dependents. It is also referenced from calligra, texstudio, texmaker, qpdfview, diffpdf,
Thanks, I grepped for a wrong string.
Yeah. (I meant that should remain at an older version, while can be decoupled and upgraded.)
moves diffpdf away from poppler_qt4, FWIW.
currently working on a fix for package as its latest version uses qt5 now, so poppler_qt4 isn't needed anymore
I opened a updating qpdfview, which makes open-pdf-presenter the last thing depending on (via the python library). Since it is abandoned, it is not likely to be updated. Do we remove it?
almost done, need some rest for now, PR for will come tomorrow :)
Finally getting rid of this in .
Change:
deer = callPackage ../shells/zsh/zsh-deer { }; <ins> deno = callPackage ../development/web/deno { inherit (darwin.apple_sdk.frameworks) Security CoreServices; }; </ins> detox = callPackage ../tools/misc/detox { }; devilspie2 = callPackage ../applications/misc/devilspie2 {

Discussion:
Project description Deno - A secure JavaScript and TypeScript runtime Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
I have it building on nix. However it needs modifications to rusty_v8 so we can use our llvm9 instead of the llvm10 that ships with it. It also needs modification to use libstdc++ instead of custom libc++ incase you want to build against musl.
Do you have it anywhere in the open? I want to continue working on it from there. I couldn't get it to work initially.
I don't have a nix expression to build it as a derivation, I just made a with the dependencies and manually edited the files in the cargo cache. give me a few days and I'll push what I've done to get it to work at the very least.
I'm extremely sorry, this is first few lines of code I ever have written in nix (and I feel like it could be my last) but I want to share it anyway p.s. I don't even know how to provide some examples of using this since it only works in one particular project and fails with example code I got online, I hope someone can use it anyway
I tested your build, and it doesn't seem to work due to linking issues that I've noticed just using the binary on its own. I'm not sure how to solve them though.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
halftone = callPackage ../applications/graphics/halftone { }; <del> halloy = callPackage ../applications/networking/irc/halloy { }; </del> harminv = callPackage ../development/libraries/science/chemistry/harminv { }; igrep = callPackage ../tools/text/igrep {

Discussion:
Package name: halloy Latest released version: 2024.5 <!-- Search your package here: --- Current version on the unstable channel: 2024.3 Current version on the stable/release channel: 2023.5 <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- Notify maintainers <!-- If the result shows no maintainers, tag the person that last updated the package. --Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
substituteInPlace setup.cfg  --replace "cps = calibreweb:main" "calibre-web = calibreweb:main"  <del> --replace "flask-wtf>=0.14.2,<0.16.0" "flask-wtf>=0.14.2"  --replace "lxml>=3.8.0,<4.7.0" "lxml>=3.8.0"  --replace "PyPDF3>=1.0.0,<1.0.4" "PyPDF3>=1.0.0"  --replace "requests>=2.11.1,<2.25.0" "requests"  --replace "unidecode>=0.04.19,<1.3.0" "unidecode>=0.04.19" </del> <ins> --replace "Flask>=1.0.2,<2.1.0" "Flask>=1.0.2"  --replace "Flask-Login>=0.3.2,<0.5.1" "Flask-Login>=0.3.2"  --replace "flask-wtf>=0.14.2,<1.1.0" "flask-wtf>=0.14.2"  --replace "lxml>=3.8.0,<4.9.0" "lxml>=3.8.0"  --replace "PyPDF3>=1.0.0,<1.0.7" "PyPDF3>=1.0.0"  --replace "requests>=2.11.1,<2.28.0" "requests"  --replace "unidecode>=0.04.19,<1.4.0" "unidecode>=0.04.19"  --replace "werkzeug<2.1.0" "" </ins> ''; # Upstream repo doesn't provide any tests.

Discussion:
, CVSSv3=9.8 (nixos-21.11) CVSSv3=9.8 (nixos-21.11) CVSSv3=8.8 (nixos-21.11) CVSSv3=6.5 (nixos-21.11) CVSSv3=6.1 (nixos-21.11) CVSSv3=5.4 (nixos-21.11) calibre-web is vulnerable to Business Logic Errors Server-Side Request Forgery (SSRF) in Pypi calibreweb prior to 0.6.16. calibre-web is vulnerable to Cross-Site Request Forgery (CSRF) Improper Access Control in Pypi calibreweb prior to 0.6.16. Cross-site Scripting (XSS) - Reflected in Pypi calibreweb prior to 0.6.16. calibre-web is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') Scanned versions: nixos-21.11: . Cc
Fixed in
Change:
builder = attrs.realBuilder or stdenv.shell; args = attrs.args or ["-e" (attrs.builder or ./default-builder.sh)]; inherit stdenv; <del> inherit (stdenv.hostPlatform) system; </del> <ins> # The `system` attribute of a derivation has special meaning to Nix. # Derivations set it to choose what sort of machine could be used to # execute the build, The build platform entirely determines this, # indeed more finely than Nix knows or cares about. The `system` # attribute of `buildPlatfom` matches Nix's degree of specificity. # exactly. inherit (stdenv.buildPlatform) system; </ins> userHook = config.stdenv.userHook or null; __ignoreNulls = true;

Discussion:
See and below.
I'll be back on my laptop to work on this tonight. Sorry for the disruption. Time permitting, I might try to combine some of release and release-cross so as to catch/prevent such things post release.
Change:
version = "0.8.4"; sha256 = "1hl4n900d24gl4vd65qdzq4m62b7bpvckldazcbd1xqcn8xhi6wp"; <ins> extraPatches = [ ./BACKPORT-Linux-5.8-compat-__vmalloc.patch ]; </ins> }; zfsUnstable = common {

Discussion:
Hello! I'd like to know whether, as the title says, it would be possible to update the ZFS derivation to the latest release candidate, , as it allows for compression, and I am exceptionally eager to try it out; if not, how could I update the derivation in my own configuration? Thank you kindly for your consideration on the matter!
Crosspost:
Change:
]; mesonFlags = [ <del> "-Dgtk-doc=true" </del> "-Dmrg=disabled" # not sure what that is "-Dsdl2=disabled" "-Dpygobject=disabled"

Discussion:
Package name: gegl Latest released version: 0.4.48 <!-- Search your package here: --- Current version on the unstable channel: 0.4.46 Current version on the stable/release channel: 0.4.46 <!-- 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. -- I can take over the package if you wish. Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
If you are able to bump the package (and babl), feel free. I probably will not be able to get to it this week.