jiebi/CodeConvo huggingface dataset:
Change:
postgresql_10 = self.callPackage generic { version = "10.6"; <del> psqlSchema = "10.0"; </del> <ins> psqlSchema = "10.0"; # should be 10, but changing it is invasive </ins> sha256 = "0jv26y3f10svrjxzsgqxg956c86b664azyk2wppzpa5x11pjga38"; this = self.postgresql_10; inherit self;

Discussion:
updates postgresql11 from 11.1 to 11.2. <delIt seems like this includes breaking changes, since neither my Gitea nor my Quassel servers can properly work with 11.2.</delWhen upgrading, the new service is configured to use a different storage directory, because the psqlSchema version was changed: /var/lib/postgresql/11.2/ instead of /var/lib/postgresql/11.1/. This means when upgrading to 11.2, the data is not transferred and applications crash because their databases don't exist anymore. <delI'm also confused as to why postgresql96 has an own package as a minor version, while postgresql 11.x share one package. Shouldn't there be postgresql111 and postgresql112 if 11.2 includes breaking changes?</delRebuild a system with postgresql with the current unstable channel. postgresql 11.1 will be updated to postgresql 11.2, and all databases will not exist with the new versions, applications will crash. system: host os: multi-user?: sandbox: version: channels(pbb): channels(root): nixpkgs:
Thanks for report. PG changed it's version schema since v10. Previously v9.6.1 and 9.6.2 were considered compatible, but 9.5 and 9.6 - not compatible. Now 11.1 and 11.2 are considered compatible, but 10 and 11 - are not. In case they really have introduced a breaking change, it should be reported upstream. We can add old PG as workaround. Can you describe what exactly was broken (test case)?
I was running Quassel and Gitea with postgresql_11 pinned in my config. Last night the nixos-upgrade ran and updated from 11.1 to 11.2. After restarting, both Gitea and Quassel could not access their databases properly. For Gitea it just looked like the database was empty, all repositories and users were missing. I could not see any related messages in the log. For Quassel, the log looked like this:
As a quickfix I have my own postgresql111 package in my system configuration. After downgrading, everything works as expected again.

Okay, I can now tell what causes this behaviour: When upgrading, the new service is configured to use a different storage directory: /var/lib/postgresql/11.2/ instead of /var/lib/postgresql/11.1/. This means when upgrading to 11.2, the data is not transferred. Both applications failed, because their databases were missing.
Probably the psqlSchema version for 11.1 and 11.2 should be 11.0.
Change:
cp -v ${driverdb} drivedb.h ''; <del> configureFlags = lib.optional enableMail "--with-scriptpath=${lib.makeBinPath [ gnused inetutils mailutils ]}"; </del> <ins> configureFlags = [ "--with-scriptpath=${scriptPath}" ]; </ins> nativeBuildInputs = [ autoreconfHook ]; buildInputs = lib.optionals stdenv.isDarwin [ IOKit ApplicationServices ];

Discussion:
I noticed that was failing to run warning scripts after enabling it. This appears to be caused by : Steps to reproduce the behavior: in status of smart with : successfully generated a notification. I tried to fix this in in smartmontools stops hardcoding PATH if you specify . This can be done when is false. <!-- 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.
Maybe you need ? I use this config and do get notifications (by email at least -- the machine is now headless so I don't know about the x11 notifications): And I don't have "sed: command not found" in my system log.
Do you have the set to true for  (or , which also overrides it for )? is correctly specified in that case. Is set in ? It should be located in .
I don't have in my (Unless it's being set indirectly via some other option.) I happen to have other smartmontools store paths on this machine (because it's a binary cache for my machines), with different PATH=:
Unfortunately I'm still seeing this after : This is what my looks like (the environment variables are set by overriding : I have set to false. only fixes the script bin path if is true (as far as I can tell).
Sorry I didn't see your comment on the original PR. should fix it for you.
Thanks!
Change:
dart_stable = dart; # Added 2020-01-15 dart-sass-embedded = throw "dart-sass-embedded has been removed from nixpkgs, as is now included in Dart Sass itself."; dat = nodePackages.dat; <ins> dbeaver = throw "'dbeaver' has been renamed to/replaced by 'dbeaver-bin'"; # Added 2024-05-16 </ins> deadcode = throw "'deadcode' has been removed, as upstream is abandoned since 2019-04-27. Use the official deadcode from 'gotools' package."; # Added 2023-12-28 deadpixi-sam = deadpixi-sam-unstable;

Discussion:
The dbeaver build uses , which keeps the maven dependencies in a Fixed-Output Derivation (FOD). Building this FOD tries to fetch dependencies from , which is now 404. This is obscured by the fact that the FOD is in the binary cache, but means the package cannot be rebuilt. remove the from
There have been at least 6 unsuccessful attempts to update in nixpkgs. Could we simply drop it in favor of a ?
I tried to update to a newer version, did all the maven hacks I could, but didn't get anywhere... I think that the fact that upstream uses tycho is the main culprit Here's the of build twice There are timestamps and whatnot all over the place, the whole thing is a mess It also looks like it's using different mirrors for the same file, but putting it in a directory named after the mirror. Maybe there's a way to override the mirror sites to only use 1 (bad solution IMO). Honestly, no idea how to proceed from source...
Agreed, Tycho was the issue in my failed update
Change:
linuxPackages_rt_5_4 = linuxKernel.packages.linux_rt_5_4; linux_4_14 = linuxKernel.kernels.linux_4_14; linux_4_19 = linuxKernel.kernels.linux_4_19; <del> linux_4_4 = linuxKernel.kernels.linux_4_4; </del> linux_4_9 = linuxKernel.kernels.linux_4_9; linux_5_10 = linuxKernel.kernels.linux_5_10; linux_5_15 = linuxKernel.kernels.linux_5_15; <del> linux_5_16 = linuxKernel.kernels.linux_5_16; </del> linux_5_17 = linuxKernel.kernels.linux_5_17; linux_5_18 = linuxKernel.kernels.linux_5_18; linux_5_19 = linuxKernel.kernels.linux_5_19;

Discussion:
The Linux 4.9 LTS release will be EOL after 2023/01 and I hope we can remove it before the 22.11 release, so we don't carry it around until then. via cc kernel maintainer team
Thanks for the heads-up. I'd be fine with doing the removal right now (considering that it's LTS and having that one removed on stable may be an unpleasant surprise), but FWIW: we usually drop kernel releases when they get EOLed (also from stable branches), otherwise we wouldn't be able to provide non-LTS kernels on any stable branch anyways.
Change:
# Framework search paths aren't added by bintools hook # https://github.com/NixOS/nixpkgs/pull/41914 <del> export NIX_LDFLAGS="$NIX_LDFLAGS -F${CoreFoundation}/Library/Frameworks -F${CoreServices}/Library/Frameworks -F${Foundation}/Library/Frameworks" </del> <ins> export NIX_LDFLAGS+=" -F${CoreFoundation}/Library/Frameworks -F${CoreServices}/Library/Frameworks -F${Foundation}/Library/Frameworks" </ins> # libcxx includes aren't added by libcxx hook # https://github.com/NixOS/nixpkgs/pull/41589 export NIX_CFLAGS_COMPILE="$NIX_CFLAGS_COMPILE -isystem ${libcxx}/include/c++/v1" # don't use system installed Xcode to run clang, use Nix clang instead <del> sed -i -E "s;/usr/bin/xcrun (--sdk macosx )?clang;${stdenv.cc}/bin/clang $NIX_CFLAGS_COMPILE $NIX_LDFLAGS -framework CoreFoundation;g"  </del> <ins> sed -i -E "s;/usr/bin/xcrun (--sdk macosx )?clang;${stdenv.cc}/bin/clang $NIX_CFLAGS_COMPILE $(bazelLinkFlags) -framework CoreFoundation;g"  </ins> scripts/bootstrap/compile.sh  src/tools/xcode/realpath/BUILD  src/tools/xcode/stdredirect/BUILD 

Discussion:
Describe the bug bazel broken on darwin in nixpkgs HEAD () To Reproduce Steps to reproduce the behavior: to build bazel on darwin Expected behavior Able to build bazel on darwin Additional context might be related to Metadata Please run and paste the result. Maintainer information: cc:
The bazel build is passing LDFLAGS flags to the compiler instead of the linker. Those should be prefixed with or moved somewhere else.
Clang used as a frontend should accept linker flags.
Flags were in .
Change:
react-native-debugger = callPackage ../development/tools/react-native-debugger { }; <ins> readarr = callPackage ../servers/readarr { }; </ins> read-edid = callPackage ../os-specific/linux/read-edid { }; readstat = callPackage ../applications/science/math/readstat { };

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:
pythonOlder, pythonRelaxDepsHook, requests, <ins> uvicorn, </ins> }: buildPythonPackage rec { pname = "langsmith"; <del> version = "0.1.45"; </del> <ins> version = "0.1.48"; </ins> pyproject = true; disabled = pythonOlder "3.8";

Discussion:
In this was to the list of . As is linux-only this breaks the build for and all of it's dependencies on other platforms such as The package also seems to build without this dependency (at least on ) -- I hope I didn't overlook something here (also sadly can't check right now). Thank you! Steps to reproduce the behavior: or Add any other context about the problem here. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
hash = "sha256-5g5xdUzH/RTVwu4Vfb5Cb1t0ruG0EXgiXjrogD/+JCU="; }; <ins> patches = [ # https://github.com/ArniDagur/python-adblock/pull/91 (fetchpatch { name = "pep-621-compat.patch"; url = "https://github.com/ArniDagur/python-adblock/commit/2a8716e0723b60390f0aefd0e05f40ba598ac73f.patch"; hash = "sha256-n9+LDs0no66OdNZxw3aU57ngWrAbmm6hx4qIuxXoatM="; }) ]; </ins> cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}";

Discussion:
Ran on at . Was building my system running . While building , the dependency failed to build due to removing support for certain metadata fields in . Fix could be similar to , but I'm not well-versed in Python packaging. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Change:
<ins> { fetchFromGitHub, lib, stdenv }: stdenv.mkDerivation rec { pname = "kitty-themes"; version = "unstable-2022-02-03"; src = fetchFromGitHub { owner = "kovidgoyal"; repo = pname; rev = "337d6fcb3ad7e38544edfb8d0f6447894b7e5f58"; sha256 = "ZP5GrT2QCdXtC5swqI0SXzIlqIcQNsxBlzEplj/hpz4="; }; installPhase = '' mkdir -p $out/themes mv themes.json $out mv themes/*.conf $out/themes ''; meta = with lib; { homepage = "https://github.com/kovidgoyal/kitty-themes"; description = "Themes for the kitty terminal emulator"; license = licenses.gpl3Only; platforms = platforms.all; maintainers = with maintainers; [ nelsonjeppesen ]; }; } </ins>

Discussion:
kitty-themes Themes for the kitty terminal emulator Metadata homepage URL: source URL: license: gpl3 platforms: linux, darwin
Change:
{ lib, bundlerEnv, bundlerUpdateScript, ruby, perl, autoconf }: bundlerEnv { <del> pname = "chef-dk"; version = "4.13.3"; </del> <ins> name = "chef-dk-4.13.3"; # Do not change this to pname & version until underlying issues with Ruby # packaging are resolved ; see https://github.com/NixOS/nixpkgs/issues/70171 </ins> inherit ruby; gemdir = ./.;

Discussion:
Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior: -build -A chefdk ./result/bin/chef ./result/bin/knife Expected behavior The chef executable is there but is broken, the knife executable isn't even present. Additional context broke chef, it worked before that commit. I've bisected it down to that changeset. Problem for me is that I don't know ruby or the ruby ecosystem... This is a problem in 19.09 as well. Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
cc
I also ran into this; I tried to debug and build it myself locally but it never seemed to rebuild when I ran in my local copy of nixpkgs. Even so, showed just the binary and nothing else. Eventually I tried the following diff to force a new build: Which caused to actually rebuild, and for some reason the rest of the binaries showed up in even with no other changes: I'm relatively new to nix, so not sure why bumping the version changes anything.
Interesting find! Just changing to makes it work as well, even without adding a version to the end of it. I tried keeping and adding a separate attribute but no such luck. There's something odd going on with I'd say.
So what seems to happen is that bundlerEnv is two different things depending if you have a or a . Maybe there's a bug in there somewhere: But I made PR's to revert to using instead for now.
Seems like this is still/again a problem ( missing) on NixOS 21.11 since it has been again mass-replaced in
After initial testing this seems to work. Are there any downsides to using here? (except for the fact that we need to list out executables to be exposed)
I don't know the ruby tooling in nix enough to know if there's any downsides or upsides of making that change. however, I'm not sure why version is removed? If you would make a PR of that we could ask someone with more ruby insights.
Sure, I can do that next week. IIRC / changes behaviour depending on existence of param.

If it is missing, it'll be pulled in from relevant gemfiles in anyways.
Sounds good to me, I'm currently running my install from nixos 19.09, because it was the latest release where I found it working :wink: I guess that's the power of Nix, but it's not a good thing to have broken packages like this. So ping me when you have that PR open and I'll test it it and possibly merge it :)
Heyho, any updates on this? :) I finally also migrated my work laptop to NixOS and just ran into this because the binary is missing. I am not at all experienced with neither Nix or NixOS but just renaming to in the appears to fix the problem, the presence of the version variable apparently doesn't have any impact on the result.
Change:
default = if lib.versionOlder config.system.stateVersion "24.05" then "${httpConf.scheme}://${httpConf.host}:${builtins.toString httpConf.port}/media/" else null; <ins> defaultText = literalExpression '' if lib.versionOlder config.system.stateVersion "24.05" then "${httpConf.scheme}://${httpConf.host}:${builtins.toString httpConf.port}/media/" else null; ''; </ins> description = '' Base path for the media proxy. Whilst this can just be set to a subdirectory of the main domain, it is now recommended to use a different subdomain.

Discussion:
Seems like introduced a dependency on inside the default of , which make fail to build with: Steps to reproduce the behavior: to build a based on System builds fine Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> url https://sourceforge.net/projects/firejail/files/firejail/ version_link '[-][0-9.]+[.]tar[.][a-z0-9]+/download$' SF_redirect </del>

Discussion:
Describe the bug Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(user): nixpkgs: Maintainer information:
Seems like updating to 0.9.64.4 is the way to go?
Can be closed?!
Change:
''; }; <del> npm2nix = nodePackages."npm2nix-git://github.com/NixOS/npm2nix.git#5.12.0".override { postInstall = "npm run-script prepublish"; }; </del> pnpm = nodePackages.pnpm.override { nativeBuildInputs = [ pkgs.makeWrapper ];

Discussion:
is unmaintained, superseded by node2nix and should therefore be removed from nixpkgs Please run and paste the results.
seems LGTM. Wanna open a PR ?
Change:
postFixup = '' makeWrapper ${python3.interpreter} $out/bin/sherlock  --add-flags "-m"  <del> --add-flags "sherlock"  </del> <ins> --add-flags "sherlock_project"  </ins> --prefix PYTHONPATH : "$PYTHONPATH:$out/share" '';

Discussion:
Package name: sherlock Latest released version: v0.15.0 <!-- Search your package here: --- Current version on the unstable channel: 0-unstable-2024-06-09 Current version on the stable/release channel: 0-unstable-2024-05-15 <!-- 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. --Some extra info: Current version of sherlock may be broken potentially because it's outdated. The link is broken. Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I'll work on updating this. Current sherlock version is also broken for me.
Change:
super = imported; overrides = { <ins> p4-16-mode = super.p4-16-mode.overrideAttrs { # workaround https://github.com/NixOS/nixpkgs/issues/301795 prePatch = '' mkdir tmp-untar-dir pushd tmp-untar-dir tar --extract --verbose --file=$src content_directory=$(echo p4-16-mode-*) cp --verbose $content_directory/p4-16-mode-pkg.el $content_directory/p4-pkg.el src=$PWD/$content_directory.tar tar --create --verbose --file=$src $content_directory popd ''; }; </ins> }; in super // overrides);

Discussion:
Steps to reproduce the behavior: With : Directly installing this package from within Emacs (using ) does not cause this error. The execution leading to this build error is: in calls ... which calls on the unpacked directory name () ... which parses this name to get the "package name" and append to get the "package description file name" wrongly thinks the "package name" is "p4" instead of "p4-16-mode", and looks for (instead of ), which does not exist. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Most certainly the parser conflates 16 as a version number.
Change:
<ins> { stdenv, lib, fetchurl, fetchFromGitHub, unzip, kernel, utillinux, libdrm, libusb1, makeWrapper }: let arch = if stdenv.system == "x86_64-linux" then "x64" else if stdenv.system == "i686-linux" then "x86" else throw "Unsupported architecture"; libPath = lib.makeLibraryPath [ stdenv.cc.cc utillinux libusb1 ]; in stdenv.mkDerivation rec { name = "displaylink-${version}"; version = "1.1.62"; src = fetchFromGitHub { owner = "DisplayLink"; repo = "evdi"; rev = "fe779940ff9fc7b512019619e24a5b22e4070f6a"; sha256 = "02hw83f6lscms8hssjzf30hl9zly3b28qcxwmxvnqwfhx1q491z9"; }; daemon = fetchurl { name = "displaylink.zip"; url = "http://www.displaylink.com/downloads/file?id=607"; sha256 = "0jky3xk4dfzbzg386qya9l9952i4m8zhf55fdl06pi9r82k2iijx"; }; nativeBuildInputs = [ unzip makeWrapper ]; buildInputs = [ kernel libdrm ]; buildCommand = '' unpackPhase cd $sourceRoot unzip $daemon chmod +x displaylink-driver-${version}.run ./displaylink-driver-${version}.run --target daemon --noexec ( cd module export makeFlags="$makeFlags KVER=${kernel.modDirVersion} KDIR=${kernel.dev}/lib/modules/${kernel.modDirVersion}/build" export hardeningDisable="pic format" buildPhase install -Dm755 evdi.ko $out/lib/modules/${kernel.modDirVersion}/kernel/drivers/gpu/drm/evdi/evdi.ko ) ( cd library buildPhase install -Dm755 libevdi.so $out/lib/libevdi.so ) fixupPhase ( cd daemon install -Dt $out/lib/displaylink *.spkg install -Dm755 ${arch}/DisplayLinkManager $out/bin/DisplayLinkManager patchelf  --set-interpreter $(cat ${stdenv.cc}/nix-support/dynamic-linker)  --set-rpath $out/lib:${libPath}  $out/bin/DisplayLinkManager wrapProgram $out/bin/DisplayLinkManager  --run "cd $out/lib/displaylink" ) ''; meta = with stdenv.lib; { description = "DisplayLink DL-5xxx, DL-41xx and DL-3x00 Driver for Linux"; platforms = [ "x86_64-linux" "i686-linux" ]; license = licenses.unfree; homepage = "http://www.displaylink.com/"; }; } </ins>

Discussion:
DisplayLink, as far as I can tell, seems to be unfortunately emerging as the only choice for connecting external monitors to laptops without display ports (for example, via the ). It would be great if NixOS could support it. I have no idea what is involved in this. There is an Ubuntu driver. DisplayLink the company claims that it should be possible to port (). The says it's difficult to get working.
Do you have hardware for testing this? The driver itself seems fairly straightforward and I could help packaging it.
I do - I have the Dell adapter linked above.
Change:
meta = with lib; { description = "GTK3 Subsonic/Airsonic client"; homepage = "https://sublimemusic.app/"; <ins> changelog = "https://github.com/sublime-music/sublime-music/blob/v${version}/CHANGELOG.rst"; </ins> license = licenses.gpl3Plus; maintainers = with maintainers; [ albakham sumnerevans ]; };

Discussion:
Steps to reproduce the behavior: sublime-music Just the error: Full log: Add any other context about the problem here. Built OK as of rev . I tried bisecting but too many commits required me to build multiple versions of LLVM/GHC/god knows what else. I also tried applying patch from but that didn't change the error. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Change:
PATH="@coreutils_bin@/bin:@gnugrep_bin@/bin" fi <ins> cInclude=0 </ins> source @out@/nix-support/utils.bash # Flirting with a layer violation here.

Discussion:
Describe the bug Building fails with the following error message: To Reproduce Steps to reproduce the behavior: . Expected behavior It enters a nix-shell with the command available. Screenshots None Additional context The build log is available at . Notify maintainers (gnatboot) and (gnat) Metadata system: host os: multi-user?: sandbox: version: channels(omasanori): nixpkgs: Maintainer information:
Might be a regression from cc
Change:
# See # https://github.com/snakemake/snakemake/blob/main/.github/workflows/main.yml#L99 <del> # for the current basic test suite. Tibanna and Tes require extra </del> <ins> # for the current basic test suite. Slurm, Tibanna and Tes require extra </ins> # setup. nativeCheckInputs = with python3.pkgs; [

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: a simple Snakefile such as shown below command fails with (truncated) exception message as shown below The command does not fail with an exception This is a known issue that has been fixed in the recent versions of Snakemake Please run and paste the result.