jiebi/CodeConvo huggingface dataset:
Change:
in stdenv.mkDerivation (finalAttrs: { pname = "prl-tools"; <del> version = "19.0.0-54570"; </del> <ins> version = "19.1.0-54729"; </ins> # We download the full distribution to extract prl-tools-lin.iso from # => ${dmg}/Parallels Desktop.app/Contents/Resources/Tools/prl-tools-lin.iso src = fetchurl { url = "https://download.parallels.com/desktop/v${lib.versions.major finalAttrs.version}/${finalAttrs.version}/ParallelsDesktop-${finalAttrs.version}.dmg"; <del> hash = "sha256-y7UC+E5i2cxkOJ9nVI6aQAFJ5kTXv9uaZoMO4/SCS6k="; </del> <ins> hash = "sha256-Qo/6EuILu5i3hjhxecf3qfoMFEJHJZVY19tDIXDJiag="; </ins> }; hardeningDisable = [ "pic" "format" ];

Discussion:
Attempting to upgrade to kernel v6.5.x results in the arm64 prl-tools package (18.3.0-) failing to compile. Steps to reproduce the behavior: NixOS in a Parallels VM from kernel version v6.4.x to v6.5.x nixos-rebuild to complete without error Using allows an upgrade to succeed with no tools installed. Attempting an upgrade with the unstable version of (19.0.0-) results in a similar build error. Please run and paste the result.
Just noticed a new DMG is available with Linux 6.5 mentioned in the : Not sure how to patch locally to test this.
I've already opened for that.
Change:
<ins> { udis86 , fetchFromGitHub }: udis86.overrideAttrs (old: { version = "unstable-2022-10-13"; src = fetchFromGitHub { owner = "canihavesomecoffee"; repo = "udis86"; rev = "5336633af70f3917760a6d441ff02d93477b0c86"; hash = "sha256-HifdUQPGsKQKQprByeIznvRLONdOXeolOsU5nkwIv3g="; }; patches = [ ]; }) </ins>

Discussion:
Project description A wlroots-compatible Wayland color picker that does not suck. Metadata homepage URL: source URL: license: platforms: linux Just because you made available on NixOS, I wanted to point you on hyprpicker, too - if you're interested to have a look into this(?)
I'll take a look into packaging this.
Change:
stdenv.mkDerivation rec { pname = "mullvad-vpn"; <del> version = "2022.1"; </del> <ins> version = "2022.2"; </ins> src = fetchurl { url = "https://github.com/mullvad/mullvadvpn-app/releases/download/${version}/MullvadVPN-${version}_amd64.deb"; <del> sha256 = "0s12y9j75k59kqkcvfflb1v5p3ny7xgc1m5bd635lvql1bv46c3i"; </del> <ins> sha256 = "sha256-h/c4aPH6E2TzbXGROpLJgF9uHYcjvKiW5upIobpJM9o="; </ins> }; nativeBuildInputs = [

Discussion:
Latest version uses Electron 18 instead of 16, which fixes issues with Wayland + Nvidia graphics. <!-- 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: mullvad-vpn <!-- 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: 2022.1 desired version: 2022.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.
Change:
mesa, validatePkgConfig, testers, <ins> wayland-scanner, </ins> }: stdenv.mkDerivation (finalAttrs: {

Discussion:
Steps to reproduce the behavior: scenefx <!-- 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]:
Change:
postInstall = stdenv.lib.optionalString stdenv.isDarwin '' wrapProgram $out/bin/xpdf  <del> --set QT_QPA_PLATFORM_PLUGIN_PATH ${qtbase.bin}/lib/qt-*/plugins/platforms </del> <ins> --set QT_PLUGIN_PATH ${qtbase.bin}/${qtbase.qtPluginPrefix}:${qtsvg.bin}/${qtbase.qtPluginPrefix} </ins> ''; meta = {

Discussion:
! system: host os: multi-user?: sandbox: version: nixpkgs:
I thought the problem might be due to imageformat plugin not being found, so I try: Result: ! There is some improvement, but still no icons. This seems to be same as on Linux. xpdf seems to use svg:
Change:
xfceUnstable = throw "xfceUnstable has been removed, use xfce instead"; # added 2022-12-25 xineLib = xine-lib; # Added 2021-04-27 xineUI = xine-ui; # Added 2021-04-27 <ins> xlibsWrapper = throw "'xlibsWrapper' has been replaced by its constituents"; # Converted to throw 2022-12-27 </ins> xmonad_log_applet_gnome3 = throw "'xmonad_log_applet_gnome3' has been renamed to/replaced by 'xmonad_log_applet'"; # Converted to throw 2022-02-22 xmpp-client = throw "xmpp-client has been dropped due to the lack of maintanence from upstream since 2017"; # Added 2022-06-02 xmpppy = throw "xmpppy has been removed from nixpkgs as it is unmaintained and python2-only";

Discussion:
In I noticed unusual behaviour of when is overridden. That PR handles override part. But I think should just disappear. Where should be no reason (for example) for to depend on at build time. is just the wrapper around a few libraries. Quoting : Mechanically we can replace with the list of packages it provides. Even better would be to audit needed libraries for each user and use only a subset of them. Example fix: [x] perlPackages.X11Protocol: [x] pulseaudio: More packages to fix: [x] Xaw3d: [x] emacs: [x] fox16: [x] geant4: [x] [x] gtk2: [x] [x] haskellPackages.greenclip: [x] [x] lesstif: [x] monotoneViz: [x] motif: [x] mythtv: [x] ocaml- [x] [x] [x] pypy2, pypy3: [x] qgis: [x] qgis-ltr: [x] [x] qt6Packages.qtwayland: [x] rPackages.Cairo: [x] rPackages.devEMF: [x] [x] rPackages,rgl: [x] tightvnc: [x] weston: Fixed packages: [x] astromenace: [x] catclock: [x] clanlib: [x] conky: [x] elinks: [x] fox: [x] freeglut: [x] ghostscript, ghostscriptX: [x] gnome2.libgnomeui: [x] glbinding: [x] glew, glew-egl: [x] glew110: [x] imhex: [x] imlib2,

imlib2Full: [x] ion3: [x] libagar: [x] libstroke: [x] lirc: [x] mitschemeX11: [x] ncview: [x] nedit: [x] notion: [x] oneko: [x] openrw: [x] pasystray: [x] pcb: [x] povray: [x] pythonFull: [x] qemacs: [x] qmmp: [x] rss-glx: [x] scrot: [x] soxt: [x] survex: [x] synergy: [x] ted: [x] unclutter: [x] unclutter-xfixes: [x] vlc: [x] voxelands: [x] wordnet: [x] xautolock: [x] xfe: [x] x11sshaskpass: [x] xfig: [x] xidlehook: [x] xine-ui: [x] xinputcalibrator: [x] xmountains: [x] xspim: [x] xtrlock-pam: [x] xwinwrap: [x] xxgdb: [x] zoom:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
meta = with lib; { description = "Lightweight, alternative desktop client for Discord"; <del> homepage = "https://github.com/ArmCord/ArmCord"; </del> <ins> homepage = "https://armcord.app"; downloadPage = "https://github.com/ArmCord/ArmCord"; </ins> sourceProvenance = with sourceTypes; [ binaryNativeCode ]; license = licenses.osl3; maintainers = with maintainers; [ wrmilling ];

Discussion:
Package name: ArmCord Latest released version: 3.2.3 <!-- Search your package here: --- Current version on the unstable channel: 3.2.1 Current version on the stable/release channel: 3.2.0 Repository: Website: <!-- 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.
Change:
) # Only SQLCipher should be able to read the encrypted DB: machine.fail( <del> "su - alice -c 'sqlite3 ~/.config/Signal/sql/db.sqlite .databases'" </del> <ins> "su - alice -c 'sqlite3 ~/.config/Signal/sql/db.sqlite .tables'" </ins> ) print(machine.succeed( "su - alice -c 'sqlcipher ~/.config/Signal/sql/db.sqlite'"

Discussion:
The nixos test for signal-desktop with the following error According to a comment in the source code, trying to access the encrypted signal database with should fail, because only should be able to read it: Steps to reproduce the behavior: on master The between the last succeeding and the first failing build: doesn't include changes to does include a version bump of So the issue might be caused by some changes to .
can you try a bisect between these two changesets?
I tried bisecting the issue, but running the test () requires mass rebuilds for most of the commits, so at least on my machine it's not feasible to find the faulty commit in a timely manner.
I just had a brief look (sorry for the delay, I don't have as much time anymore). Luckily the encryption still seems to work. is fine and I also dumped the content to the log with and it looks like random data / garbage (-encrypted). However, the behaviour of seems to have indeed changed... :o The command succeeds now and outputs just this: Theoretically we could just remove that command but for extra security I'd find it best to replace it with something that still works. However, it seems best to simply replace with (or (full)schema): I'll send in a quick PR. Thanks for the report and pinging me! :)
Change:
<del> source $stdenv/setup installFlags="PREFIX=$out" preBuild() { cp Makefile.def Makefile sed -i GNUmakefile -e 's/compress %/%/g' } postInstall() { rm $out/bin/uncompress* $out/bin/zcat* ln -s compress $out/bin/uncompress ln -s compress $out/bin/zcat } genericBuild </del>

Discussion:
The and packages both provide an implementation of that is incompatible. This is leading to some trouble when having both packages installed and executing shell scripts that expect to be present in the path. Since isn't that widely used I would recommend to either remove from (it is a symbolic link anyway) or to rename it to . Steps to reproduce the behavior: and on a gzip compressed file (example: some ) There might be valid use cases where from is used, for example for very old shell scripts dating back to the early 1990s or earlier. These days the default is expected to be from and other distributions (like Fedora) do not seem to be creating the symlink for .
Change:
{ stdenv, fetchurl, autoPatchelfHook, makeWrapper <del> , alsaLib, xorg </del> <ins> , alsaLib, xorg, libjack2 </ins> , gtk3, pango, gdk-pixbuf, cairo, glib, freetype , libpulseaudio, xdg_utils }: stdenv.mkDerivation rec { pname = "reaper"; <del> version = "5.987"; </del> <ins> version = "6.10"; </ins> src = fetchurl { url = "https://www.reaper.fm/files/${stdenv.lib.versions.major version}.x/reaper${builtins.replaceStrings ["."] [""] version}_linux_x86_64.tar.xz"; <del> sha256 = "040k5inzj7mmi75fc6hr0ym18y5xss1675bl5rmhn4sq535m289k"; </del> <ins> sha256 = "1p54phmsa6xbqxb5cpgwnz7ny4famb8zi25y3cmxwgr4pfy94b2p"; </ins> }; nativeBuildInputs = [ autoPatchelfHook makeWrapper ];

Discussion:
Package reaper-5.981 is out of date. Latest available version is 6.03.
cc

Describe the bug NixOS’ Reaper package is not configured to work with Jack2 backend. To Reproduce Expected behavior Reaper should manage jack backend. See for instance . For now, Reaper only says in Reaper Preferences/Audio/Device. Additional context Everything is working fine on my system with jack2 (Ardour, Supercollider, VLC, etc.), except Reaper. Metadata
Change:
ExecStart = "${lib.getExe ollamaPackage} serve"; WorkingDirectory = cfg.home; StateDirectory = [ "ollama" ]; <del> DynamicUser = true; </del> <ins> DynamicUser = cfg.sandbox; ReadWritePaths = cfg.writablePaths; </ins> }; };

Discussion:
Steps to reproduce the behavior: ollama service the model dir Ollama should work, files and directories have rw permissions for anyone and the file system is not read-only. It used to work before an update. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Could you try manually renaming the file to see if you get the same error? If you still get the error, the problem is probably with your system config. If you don't get the error, the problem could be with the ollama binary, or with the service config. Maybe try it as root as well to see if there's a difference. By the way, the reason it's trying to rename the files is due to a change in .
Renaming files solves the problem of starting ollama, but does not solve the overall problem. I can't install a new model, for example.
I found what the problem is. The ollama service has set, which creates a new user for the service and enables some sandboxing that includes making most of the filesystem read-only. I'm not sure at the moment the best way to fix this without compromising on security, so I'll do some more research on how systemd works, and any relevant systemd options. At worst, I should be able to create a nixos option that disables this sandboxing entirely. If you have any suggestions, I'd be happy to hear them.
In the meantime, a temporary workaround that I think should work is this nixos config:
Change:
buildPythonApplication rec { pname = "rare"; <del> version = "1.9.2"; </del> <ins> version = "1.9.3"; </ins> src = fetchFromGitHub { owner = "Dummerle"; repo = "Rare"; rev = version; <del> sha256 = "sha256-mL23tq5Fvd/kXAr7PZ+le5lRXwV3rKG/s8GuXE+S11M="; </del> <ins> sha256 = "sha256-M+OMsyamh4WHIx7Pv2sLylOrnSmYrv1aEm3atqXrDaw="; </ins> }; nativeBuildInputs = [

Discussion:
on nixpkgs-unstable, rare fails to start should display a GUI
a bisect led to this faulty commit:
Reported upstream:
Change:
./services/misc/prowlarr.nix ./services/misc/pykms.nix ./services/misc/radarr.nix <ins> ./services/misc/readarr.nix </ins> ./services/misc/redmine.nix ./services/misc/ripple-data-api.nix ./services/misc/rippled.nix

Discussion:
Readarr Readarr is a ebook collection manager for Usenet and BitTorrent users. It can monitor multiple RSS feeds for new books from your favorite authors and will interface with clients and indexers to grab, sort, and rename them. Metadata homepage URL: source URL: license: GNU GPL v3 platforms: Windows, Linux, macOS, Raspberry Pi, etc.
As you bundled some of the *arr software earlier, I'd be interested in trying out to package readarr, however I have 0 experience with these kind of package and the dotnet environment. Would one of you be willing to help me?
Pretty much the same tbh, I'd honestly just start with a copy of one of the existing snippets and change the appropriate parts.
Change:
buildLua rec { pname = "mpv-notify-send"; <del> version = "0-unstable-2020-02-24"; </del> <ins> version = "0-unstable-2024-07-11"; </ins> src = fetchFromGitHub { <del> owner = "emilazy"; repo = pname; rev = "a2bab8b2fd8e8d14faa875b5cc3a73f1276cd88a"; sha256 = "sha256-EwVkhyB87TJ3i9xJmmZMSTMUKvfbImI1S+y1vgRWbDk="; </del> <ins> owner = "Parranoh"; repo = "mpv-notify-send"; rev = "d98d9fe566b222c5b909e3905e9e201eaec34959"; hash = "sha256-H8WIKfQnle27eiwnz2sxC8D1EwQplY4N7Qg5+c1e/uU="; </ins> }; <del> patches = [ # show title of online videos instead of url (fetchpatch { name = "6.patch"; # https://github.com/emilazy/mpv-notify-send/pull/6 url = "https://github.com/emilazy/mpv-notify-send/commit/948347e14890e15e89cd1e069beb1140e2d01dce.patch"; hash = "sha256-7aXQ8qeqG4yX0Uyn09xCIESnwPZsb6Frd7C49XgbpFw="; }) ]; </del> passthru.extraWrapperArgs = [ "--prefix" "PATH" ":" <del> (lib.makeBinPath libnotify) </del> <ins> (lib.makeBinPath [ libnotify ]) </ins> ]; passthru.updateScript = unstableGitUpdater { }; <del> meta = with lib; { </del> <ins> meta = { </ins> description = "Lua script for mpv to send notifications with notify-send"; <del> homepage = "https://github.com/emilazy/mpv-notify-send"; license = licenses.wtfpl; maintainers = with maintainers; [ r3n3gad3p3arl ]; </del> <ins> homepage = "https://github.com/Parranoh/mpv-notify-send"; license = lib.licenses.wtfpl; maintainers = with lib.maintainers; [ r3n3gad3p3arl ]; </ins> }; }

Discussion:
Steps to reproduce the behavior: OR I'll be honest, I am not sure if this is catalogued as a build failure or not, because if I add to , without modifying the wrapper of mpv or creating an overlay for it, the configuration builds. So, adding it as a script is at fault, not the derivation itself Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
mkdir -p "$out/bin" makeWrapper "${sage-with-env}/bin/sage" "$out/bin/sage"  --set SAGE_DOC_SRC_OVERRIDE "${src}/src/doc" ${ <del> stdenv.lib.optionalString withDoc "--set SAGE_DOC_OVERRIDE ${sagedoc}/share/doc/sage" } </del> <ins> stdenv.lib.optionalString withDoc "--set SAGE_DOC_OVERRIDE ${sagedoc}/share/doc/sage" }  --prefix JUPYTER_PATH : "${kernel-specs}" </ins> ''; doInstallCheck = withDoc;

Discussion:
When I run , I have the jupyter website that opens, however when I open a sage notebook, the sage kernel fails to start, and I've an error Install sage, tested on both latest nixos-unstable (that took ages to compile), and using the one provided here: Then run and try to open a sage notebook. You should see on the top right a red error "Kernel error", and the console should display the above errors Please run and paste the results.
/cc maintainer
Thanks for the report :) The immediate cause for the error is that contains while it should be . I have never used jupyter so I'm not sure if that is all. Integrating with would probably be good / maybe be necessary. I don't know when/if I'll get to debugging this since I don't currently use it myself, but I'll happily help you do it if you want to try. Note that the regular sage cli does work.
I also experience this issue. I thought I was installing Jupyter incorrectly. Lol, I should have checked for a bug report, I asked for help at
This is now fixed in master.
Change:
''; # needed on non-x86 linux <del> setupPyBuildFlags = lib.optionals stdenv.isLinux [ "--plat-name" "linux" ]; </del> <ins> setupPyBuildFlags = lib.optionals stdenv.isLinux [ "--plat-name" "linux" ] # aarch64 only available from MacOS SDK 11 onwards, so fix the version tag. # otherwise, bdist_wheel may detect "macosx_10_6_arm64" which doesn't make sense. ++ lib.optionals (stdenv.isDarwin && stdenv.isAarch64) [ "--plat-name" "macosx_11_0" ]; </ins> propagatedBuildInputs = [ setuptools

Discussion:
The python package fails to build on aarch64-darwin with the error: Steps to reproduce the behavior: Package builds.
Doing some digging, posting my notes here... Note that the whl is named: Following the thread here: Looks like pip expects for the binary format or for the SDK. I suspect this could be fixed during build, or perhaps by renaming the whl. Will continue to investigate. via here: <img width="717" alt="image" src="https://user-" pip seems to think that would not ever be generated, so it doesn't look for whls in this format. When I patch in the binary format, installation succeeds: <img width="675" alt="image" src="https://user-"But this obviously isn't a great solution. So, I'll try to figure out how to fix the build so that it emits or similar. According to here: support cli options to override the Python tag and similar when generating the wheel: <img width="674" alt="image" src="https://user-"
I was able to fix the build on aarch64-darwin by explicitly providing to similar to how its done for Linux: <img width="1030" alt="image" src="https://user-"I still don't have a perfect understanding of why bdist is pulling SDK 10.6 with aarch64 to create the tag; I guess this happens in some upstream python part of nix (which I don't really understand well yet).
Change:
, fetchurl, fetchpatch, fetchFromSavannah, fetchFromGitHub , useRailsExpress ? true , rubygemsSupport ? true <ins> , JitSupport ? true </ins> , zlib, zlibSupport ? true , openssl, opensslSupport ? true , gdbm, gdbmSupport ? true

Discussion:
Describe the bug I'm hunting down packages that reference gcc. One of them is (maintainers: & ). Here's why: The fault is the fact that the build flag doesn't remove all references, as one might expect (EDIT, see: ). I'm up to including this feature, but I was wondering perhaps it'd be legit to disable this feature for the derivation? I opened a PR at (EDIT).
But that would mean gems that require a compiler would no longer work.
The suggestion is for , not . Isn't the derivation that's used to build the gems? According to:
It still has support for gems, so some will fail with gcc. What exactly is the use case for ?
Technically it's not used anywhere, according to .
I'd like to make my - with an overlay. The goal is to make the 1 or 2 pure ruby scripts I have on my system not pull , as they do today.
But what is the reason? You're likely to have a version of ruby that includes gcc on your system anyway, so you don't really save any space. And the use-case would be plain ruby scripts with only the gems that don't require system libraries. We have no users in nixpkgs of presumably because it's rather pointless. And while of course we can strip gcc from rubyMinimal (there's no harm), I'd rather say drop instead.
Not If I'll apply and this overlay: This allows me to not need GCC for for example - which is the only ruby gem I use. For example, run with this PR and that overlay applied: And you should get: And without , (and without the overlay because it would fail) you should get: is the only derivation that needs ruby that I actually use. I've updated the 1st comment in to exemplify this overlay as a possible usecase. Well I tend to agree - even for asciidoctor which should be pretty much a pure ruby gem, it still required and which aren't enabled in current . Hence I tend to agree. OK so I've updated to include a drop to , including release notes and an alias. Waiting for your review :crossed_fingers: .
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
nwg-bar = callPackage ../applications/misc/nwg-bar { }; <ins> nwg-displays = callPackage ../applications/misc/nwg-displays { }; </ins> nwg-dock = callPackage ../applications/misc/nwg-dock { }; nwg-dock-hyprland = callPackage ../applications/misc/nwg-dock-hyprland { };

Discussion:
Project description Output management utility for sway and Hyprland. Metadata homepage URL: https://nwg- source URL: license: mit platforms: linux
Change:
<ins> import ./make-test-python.nix ( { pkgs, ... }: let port = "7745"; in { name = "homebox"; meta = with pkgs.lib.maintainers; { maintainers = [ patrickdag ]; }; nodes.machine = { services.homebox = { enable = true; settings.HBOX_WEB_PORT = port; }; }; testScript = '' machine.wait_for_unit("homebox.service") machine.wait_for_open_port(${port}) machine.succeed("curl --fail -X GET 'http://localhost:${port}/'") out = machine.succeed("curl --fail 'http://localhost:${port}/api/v1/status'") assert '"health":true' in out ''; } ) </ins>

Discussion:
Project description Like a simpler Snipe-IT for home usage. Keep track of inventories, warranties, and manuals. Metadata homepage URL: https://hay- source URL: license: APL3 platforms: presumably Go's platforms? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
It makes use of , so is technically a blocker. I'm hoping it will work with to bypass that issue.
homebox was archived:
feel free to reopen if there's maintained, viable fork.
I see picking up activity, tentatively re-opening the issue for now. Will revisit to see if it keeps being maintained long term.
There's an active repo being worked on here: