jiebi/CodeConvo huggingface dataset:
Change:
config = mkIf cfg.enable { security.wrappers.udevil.source = "${lib.getBin pkgs.udevil}/bin/udevil"; <ins> systemd.packages = [ pkgs.udevil ]; systemd.services."devmon@".wantedBy = [ "multi-user.target" ]; </ins> }; }

Discussion:
systemd service isn't referencing the correct binary investigate is devmon requires suidsystem: host os: multi-user?: sandbox: version: channels(root): channels(peter): nixpkgs:
Can you elaborate a bit on what exactly is wrong? Steps to reproduce would be ideal.
udevil at <storepath/lib/systemd/system/devmon.service
I marked this as stale due to inactivity. &rarr;
Although I've self-assigned it, somebody else is very welcome to grab this.
I noticed the same issue yesterday when I tried devmon for automounting. devmon works fine when started manually but doesn't work as a systemd service. I couldn't find devmon service after running and .
Change:
, ghc-boot-th, ghc-check, ghc-paths, ghc-typelits-knownnat, gitrev , haddock-library, hashable, haskell-lsp, haskell-lsp-types , hie-bios, hslogger, lens, lsp-test, mtl, network-uri <del> , opentelemetry, optparse-applicative, prettyprinter , prettyprinter-ansi-terminal, process, QuickCheck , quickcheck-instances, regex-tdfa, rope-utf16-splay, safe , safe-exceptions, shake, sorted-list, stdenv, stm, syb, tasty , tasty-expected-failure, tasty-hunit, tasty-quickcheck , tasty-rerun, text, time, transformers, unix, unordered-containers , utf8-string, yaml </del> <ins> , optparse-applicative, prettyprinter, prettyprinter-ansi-terminal , process, QuickCheck, quickcheck-instances, regex-tdfa , rope-utf16-splay, safe, safe-exceptions, shake, sorted-list , stdenv, stm, syb, tasty, tasty-expected-failure, tasty-hunit , tasty-quickcheck, tasty-rerun, text, time, transformers, unix , unordered-containers, utf8-string, yaml </ins> }: mkDerivation { pname = "ghcide"; <del> version = "0.2.0"; </del> <ins> version = "0.3.0"; </ins> src = fetchgit { url = "https://github.com/haskell/ghcide"; <del> sha256 = "1zq7ngaak8il91a309rl51dghzasnk4m2sm3av6d93cyqyra1hfc"; rev = "078e3d3c0d319f83841ccbcdc60ff5f0e243f6be"; </del> <ins> sha256 = "15v3g3i5v0xbq50lfvl4bv3rx01nixiqx02sddqi5lj2idgmg24g"; rev = "96cf8c53d0bdc16d3d2cd0559b74962593ce6dc5"; </ins> fetchSubmodules = true; }; isLibrary = true;

Discussion:
Describe the bug , a nested dependency, requires < 4.1.14. To Reproduce
Can probably be closed now?
Yes, I thought that would happen automatically.
I just bumped on (something very similar to?) this:
Change:
<ins> { lib , python3 }: python3.pkgs.buildPythonPackage rec { pname = "listparser"; version = "0.18"; src = python3.pkgs.fetchPypi { inherit pname version; sha256 = "0hdqs1mmayw1r8yla43hgb4d9y3zqs5483vgf8j9ygczkd2wrq2b"; }; propagatedBuildInputs = with python3.pkgs; [ requests six ]; checkPhase = '' ${python3.interpreter} lptest.py ''; meta = with lib; { description = "A parser for subscription lists"; homepage = "https://github.com/kurtmckee/listparser"; license = licenses.lgpl3Plus; maintainers = [ maintainers.pbogdan ]; platforms = platforms.linux; }; } </ins>

Discussion:
Project description An RSS/Atom feed reader for GNOME. Metadata homepage URL: source URL: license: GPL v3 platforms: linux, possibly others?
I haven't tested it extensively yet but here's my current expression: The basic at the very least seem to work.
I haven't run into any problems using your expression, are you planning on creating a pull request for this?
Glad you found it useful. And thank you for the reminder, I forgot about this (just stashed it into a local overlay) but will try and prepare a PR in the next couple of days.
Change:
homepage = "https://github.com/grantjenks/py-tree-sitter-languages"; license = licenses.asl20; maintainers = with maintainers; [ doronbehar ]; <ins> # https://github.com/grantjenks/py-tree-sitter-languages/issues/67 broken = versionAtLeast tree-sitter.version "0.22"; </ins> }; }

Discussion:
Steps to reproduce the behavior: Originally found building Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
That's not a build failure, but an evaluation failure. If you want to make not depend on , you need to figure out where does this dependency comes from, and try to remove it. The reason we disabled is documented in the code: Note that although the issue is fixed, we intentionally provide an expression for , so that we can build with it. See also: You can work around this issue by using instead, or try to be creative and make depend on the latest (and not ), by fixing the upstream issue . Good luck!
I'm closing this, as this is an upstream issue. Ideally it would have been possible to declaratively write with Nix why packages are disabled for certain Python implementation, and that would have improved the evaluation failure message you observed. I think I saw discussion about such a feature, but I can't find any links now unfortunately.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
, udev , wayland , xorgproto <ins> , nix-update-script </ins> }: <del> stdenv.mkDerivation (self: { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "louvre"; <del> version = "2.2.0-1"; rev = "v${self.version}"; hash = "sha256-Ds1TTxHFq0Z88djdpAunhtKAipOCTodKIKOh5oxF568="; </del> <ins> version = "2.9.0-1"; </ins> src = fetchFromGitHub { <del> inherit (self) rev hash; </del> owner = "CuarzoSoftware"; repo = "Louvre"; <ins> rev = "v${finalAttrs.version}"; hash = "sha256-0M1Hl5kF8r4iFflkGBb9CWqwzauSZPVKSRNWZKFZC4U="; </ins> }; <ins> sourceRoot = "${finalAttrs.src.name}/src"; postPatch = '' substituteInPlace examples/meson.build  --replace-fail "/usr/local/share/wayland-sessions" "${placeholder "out"}/share/wayland-sessions" ''; </ins> nativeBuildInputs = [ meson ninja

Discussion:
Package name: louvre Latest released version: 2.9.0-1 <!-- Search your package here: --- Current version on the unstable channel: 2.2.0-1 Current version on the stable/release channel: 1.2.1-2 <!-- 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:
roboto-mono = callPackage ../data/fonts/roboto-mono { }; <ins> roboto-serif = callPackage ../data/fonts/roboto-serif { }; </ins> roboto-slab = callPackage ../data/fonts/roboto-slab { }; hasklig = callPackage ../data/fonts/hasklig {};

Discussion:
Project description Metadata homepage URL: source URL: license: SIL Open Font License 1.1 platforms: all
Change:
with open("${pkgs.writeText "tests.json" (builtins.toJSON tests)}") as json_file: tests = json.load(json_file) <ins> # These environments used to run in the opposite order, causing the # following error at openvt startup. # # openvt: Couldn't deallocate console 1 # # This error did not appear in successful runs. # I don't know the exact cause, but I it seems that openvt and X are # fighting over the virtual terminal. This does not appear to be a problem # when the X test runs first. </ins> keymap_environments = { <del> "VT Keymap": "openvt -sw --", </del> "Xorg Keymap": "DISPLAY=:0 xterm -title testterm -class testterm -fullscreen -e", <ins> "VT Keymap": "openvt -sw --", </ins> } machine.wait_for_x()

Discussion:
The dvorak test is failing. Build Copy of the log Dvorak works, test works, channel progresses. If applicable, add screenshots to help explain your problem. Test has no maintainers. Please run and paste the result.
All keymap tests have been flaky for quite a long time. I don't know why. Restarting them helps, e.g. the build linked above succeeded on the second attempt.
Speaking of blockers here's a current one:
You don't happen to know the rough time frame when they became flaky?
No, I can't recall. Practically it became worse because shortly before 22.11 we to standard jobs, so the number of keymap tests doubled.
Yeah, I can see why this gets a lot more annoying. Is the flakiness exclusively for the -tests or the -ones as well?
Tried to reproduce it via the following (mainly for myself as a reference when switching locations) and didn't get a single failure after several runs: I'm guessing that the build nodes were on high load, so need to employ a different strategy...
We might run smaller amount of them; that should be easy. I don't know why it's useful to run it on so many keymaps.
Or a larger amount with more logging so we can find the cause.
Also not all hardware is equal. Maybe keep track of hostnames?
I've found a fix that runs the test dozens of times without issue on a machine that otherwise reproduces the issue fairly reliably.
Change:
# Dolphin bluez ffmpeg gettext portaudio wxGTK30 miniupnpc mbedtls lzo sfml gsm <del> wavpack gnutls-kdh orc nettle gmp pcre vulkan-loader </del> <ins> wavpack orc nettle gmp pcre vulkan-loader </ins> # DOSBox SDL_net SDL_sound

Discussion:
Describe the bug See the ; the relevant issue seems to be here: Most of is online verbatim. To Reproduce Steps to reproduce the behavior: Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(username): nixpkgs:
I confirm I see the same issue here when I run with the channel.
It seems the only package that needs is . Do you need or specifically in your configuration?
i bisect'ed it to
lutris has it as a transitive dependency
I guess it's used by dolphin
to follow up, gnutls-kdh doesn't build with nettle-3.5.1. Seeing as the repo is quite inactive, either we get rid of it, or freeze nettle. I'm personally in favor of getting rid of it
Change:
to  work, the username used to connect to PostgreSQL must match the database name, that is services.invidious.settings.db.user must match services.invidious.settings.db.dbname. This is the default since NixOS 24.05. For older systems, it is normally safe to manually set <del> services.invidious.database.user to "invidious" as the new user will be created with permissions for the existing database. `REASSIGN OWNED BY kemal TO invidious;` may also be needed. </del> <ins> the user to "invidious" as the new user will be created with permissions for the existing database. `REASSIGN OWNED BY kemal TO invidious;` may also be needed, it can be run as `sudo -u postgres env psql --user=postgres --dbname=invidious -c 'reassign OWNED BY kemal to invidious;'`. </ins> ''; } ];

Discussion:
New version of the invidious module gives an error on old system state versions with the following message: Config option doesn’t seem to exist and doesn’t do anything when set. Manually setting gets config to build, but service still doesn’t start with permission error, even after running the suggested reassign command: database seems to be correctly owned by the user: Steps to reproduce the behavior: invidious with local database on system state before 24.05: an error message, try to perform suggested fix. Find out that the suggested setting doesn’t exist and use instead: as suggested by the error message. to start . permission error. Service should successfully start after applying suggested fixes. Error message shouldn’t refer to non-existent options. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
The correct configuration should look like this if your state version is before 24.05: Looks like there is a mistake in the error message ( and are both specified and only the former is correct). Can you please try again with set to ?
Yes, I’ve tried this (steps 2+ of reproduction). I’ve mistakenly wrote in my initial issue, sorry, I’ve tried setting . It gets config to build, but it doesn’t start with the error described in the first post. I’ll amend the issue text now.
Can you show us the output of
Sure! I see the problem now. I’ve tried to run the command without selecting the database first. After running it with database selected, service starts successfully. Thanks!
Super. Can you please look at the PR and tell me if the improved language would have solved your issue?
Yeah, thanks, that would’ve been clear!
Change:
pngquant tesseract python3Packages.weasyprint <ins> ghostscript_headless </ins> ] ++ lib.optional (cfg.environment.INSTALL_BOOK_AND_ADVANCED_HTML_OPS or "false" == "true") calibre;

Discussion:
The Stirling PDF module is missing the Ghostscript (gs) dependency for compression, resulting in an error when trying to compress PDF's. Steps to reproduce the behavior: to compress a PDF via the web client. the error . compression happens. PDF file compression completes successfully. ! Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<ins> { lib, options, ... }: with lib.types; { options.fooDeclarations = lib.mkOption { default = (options.free.type.getSubOptions [])._freeformOptions.foo.declarations; }; options.free = lib.mkOption { type = submodule { config._module.freeformType = lib.mkMerge [ (attrsOf (submodule { options.foo = lib.mkOption {}; })) (attrsOf (submodule { options.bar = lib.mkOption {}; })) ]; }; }; config.free.xxx.foo = 10; config.free.yyy.bar = 10; } </ins>

Discussion:
See the : the options aren't declared by any file (it's actually , but that's stripped at some point). I think this is most likely because they are declared inside a : but I don't know the module system well enough to troubleshoot this. This was causing the unstable channel import to because of an which should be fixed by This is an issue of the module system, so pinging
fixes this, thanks for the report!
Change:
stdenv.mkDerivation rec { pname = "pcsclite"; <del> version = "1.9.4"; </del> <ins> version = "1.9.5"; </ins> outputs = [ "bin" "out" "dev" "doc" "man" ]; src = fetchurl { url = "https://pcsclite.apdu.fr/files/pcsc-lite-${version}.tar.bz2"; <del> sha256 = "sha256:0jqwnpywk9ka3q88b1k93p8s0xhmx1isdpcqa80nd8p04z1am34a"; </del> <ins> sha256 = "sha256:024x0hadn0kc0m9yz3l2pqzc5mdqyza9lmckg0bn4xak6frzkqwy"; </ins> }; patches = [ ./no-dropdir-literals.patch ];

Discussion:
The package installs that contains an unconfigured variable: This results in the following message in system journal: Obviously, not critical, but still this doesn’t sound right. The contains , so it looks like gets replaced by literal , but I am not sure where this happens or why. Steps to reproduce the behavior: There should be no unsubstituted variables in the installed unit. Maintainer information:
Looks like this line was upstream in 1.9.2 and the version in nixpkgs was upgraded from 1.9.1 to 1.9.4 in October ().
Ok, I am not particularly good with Autotools, but it seems to me that it is an upstream bug. The generate does this replacement, but I think it is supposed to happen only in a context in which this will be further expanded, not in plaintext files intended to be simply copied to their final install location.
Yes, it’s definitely an upstream issue. This usage of is explicitly called out as incorrect in Autconf docs:
Reported upstream:
Fixed in 1.9.5 (just released):
Keep in mind that this needs to point at if it is to be used for anything instead of into the nix store.
Can we make an option to allow specific ? I can help to make a PR if you agree : )
Send a PR I guess? Although, I am not sure how useful this option will be, given that, I assume, all other packages have to be linked to the same pcsc that provides the daemon. On the other hand, many other packages have this option, and I don’t know if there is some pattern or policy in NixOS.
The fixes PR is merged, but if a stable user (, etc.) wants to solve these issues, he could be: nix overlays, let = the package from newer channel, this will cause rebuild of all package that depends on it. to override attribute of , which is tedious and error-prone. So I suggest either we add an option to allow specific the package,or backport the changes to stable branch...?
Change:
}; cmp-fish = super.cmp-fish.overrideAttrs { <del> dependencies = with self; [ nvim-cmp fish ]; </del> <ins> dependencies = with self; [ nvim-cmp ]; </ins> }; cmp-fuzzy-buffer = super.cmp-fuzzy-buffer.overrideAttrs {

Discussion:
Many cmp-* plugins have dependencies like curl, fish, tmux etc. But those are not plugins. In result those programs are to nvim runtimepath. Looks like it was introduced by Steps to reproduce the behavior: package e.g. -pack-dir now contains curl and git directories. Binaries should not be linked to runtimepath. Paths to binaries should be replaced in plugin source code or to nvim's PATH (does it work with propagatedBuildInputs?). If applicable, add screenshots to help explain your problem. 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.
Change:
downloadPage  = "http://download.fcitx-im.org/fcitx-mozc/"; license       = licenses.free; platforms     = platforms.linux; <del> maintainers   = [ maintainers.ericsagnes ]; </del> <ins> maintainers   = with maintainers; [ gebner ericsagnes ]; </ins> }; }

Discussion:
Describe the bug I was trying to upgrade my system to latest unstable when I encountered this error: error: --- Error
--------------------- nix-build builder for '/nix/store/4akxpw50h059071m68rm96qi3jmdv7zi-ibus-mozc-' failed with exit code 1; last 10 log lines: File "", line 854, in BuildMain BuildWithNinja(options, targets) File "", line 828, in BuildWithNinja RunOrDie([ninja, '-C', buildarg] + ninjatargets) File "", line 99, in RunOrDie '=========='])) ERROR: ninja -C outlinux/Release ibusmozc mozcemacshelper mozcserver mozctool mozc_renderer
cc: because of .
likewsie fcitx-mozc stopped working. Seems like there is this fork of google-mozc with more recent commits but changing upstream would require more changes:
Change:
gtksourceview5 ]; <ins> postPatch = '' substituteInPlace src/meson.build  --replace "1.2.0" "${libadwaita.version}" ''; </ins> postInstall = '' ln -s $out/bin/io.posidon.Paper $out/bin/paper '';

Discussion:
Steps to reproduce the behavior: in nixos-unstable -note build will failed 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.
You can override paper-note by adding the following section and it should work fine.
Change:
<ins> { lib , stdenv , fetchFromGitHub , glslang , meson , ninja , pkg-config , libX11 , spirv-headers , vulkan-headers , vkbasalt32 }: stdenv.mkDerivation rec { pname = "vkbasalt"; version = "0.3.2.6"; src = fetchFromGitHub { owner = "DadSchoorse"; repo = pname; rev = "v${version}"; sha256 = "sha256-wk/bmbwdE1sBZPlD+EqXfQWDITIfCelTpoFBtNtZV8Q="; }; nativeBuildInputs = [ glslang meson ninja pkg-config ]; buildInputs = [ libX11 spirv-headers vulkan-headers ]; mesonFlags = [ "-Dappend_libdir_vkbasalt=true" ]; postInstall = lib.optionalString (stdenv.hostPlatform.system == "x86_64-linux") '' install -Dm 644 $src/config/vkBasalt.conf $out/share/vkBasalt/vkBasalt.conf # Include 32bit layer in 64bit build ln -s ${vkbasalt32}/share/vulkan/implicit_layer.d/vkBasalt.json  "$out/share/vulkan/implicit_layer.d/vkBasalt32.json" ''; meta = with lib; { description = "A Vulkan post processing layer for Linux"; homepage = "https://github.com/DadSchoorse/vkBasalt"; license = licenses.zlib; maintainers = with maintainers; [ kira-bruneau ]; platforms = platforms.linux; }; } </ins>

Discussion:
error when creating a bottle Steps to reproduce the behavior: bottles to create a new bottle during dxvk installation process with the following error message No error when trying to create a bottle ! I'm pretty new to nixos so it might be a configuration error on my part I apologize in advanced if I tagged the wrong maintainers
It should be fixed in (I don't reproduce it there). (I think it's caused by the fact I )
gotcha. feel free to close if you think it's gonna be fixed in next release. thanks :)
Change:
stateDir = "%S/${systemdDir}"; # %L: Log directory root (usually /var/log); see systemd.unit(5) logsDir = "%L/${systemdDir}"; <ins> # Name of file stored in service state directory currentConfigTokenFilename = ".current-token"; </ins> in { options.services.github-runner = {

Discussion:
After rebooting the machine, the systemd service fails to start due to an "invalid user: ‘github-runner’" Steps to reproduce the behavior: The systemd service enters the state : It does not happen after every reboot. I have not found the circumstances that make the systemd service fail. One workaround to bring the service back to the running state is to manually restart . Please run and paste the result. Maintainer information:
Thanks for raising this. I guess I ran into this as well already but didn't give it too much thought. Now, after reading systemd.service(5) again, I believe we should prefix with instead of : I'm not sure that's really the issue but it seems like the user/group () is not always set up when systemd runs . It appears would make sure they exist. I'm going to open a PR. Regardless of fixing this issue (which I hope it does), it makes sense to use instead of .
Wow, thanks for the quick response! I will check out your PR soon.
Change:
<del> { stdenv, fetchzip, applyPatches, ... }: </del> <ins> { stdenv, fetchzip, applyPatches, lib, ... }: </ins> { url , sha256 <ins> , appName ? null , appVersion ? null , license </ins> , patches ? [ ] <del> , name ? null , version ? null </del> <ins> , description ? null , homepage ? null </ins> }: <del> if name != null || version != null then throw '' `pkgs.fetchNextcloudApp` has been changed to use `fetchzip`. To update, please * remove `name`/`version` * update the hash '' else applyPatches { </del> <ins> applyPatches ({ </ins> inherit patches; src = fetchzip { inherit url sha256;

Discussion:
The nextcloud package set offers apps, that have licensing information attached, but not exposed as part of their meta attribute. Also, there are some apps, like news, where the licensing information says , which requires clarification. This needs to be fixed.
Thank you for opening the draft PR in order to fix my mistakes and broken packages. I'm sorry for the bad communication and the inability to resolve this serious issue. Fixing this for Wordpress packages and themes (wp4nix) and Nextcloud apps (nc4nix) in a foreseeable time exceeds my skills and competence. Therefore I would like to offer to add a flag to these package sets and remove them for the next release 23.11 if it's not resolved by then.
Change:
pkg-config qt6.qttools qt6.wrapQtAppsHook <ins> # GLib-GIO-ERROR: No GSettings schemas are installed on the system wrapGAppsHook3 </ins> ]; buildInputs = [

Discussion:
Package name: PDF4QT Latest released version: 1.4.0 Current version on the unstable channel: 1.3.7 Current version on the stable/release channel: 1.3.7 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]:
Sorry for the ignorance. Repology didn't prompt me to update. I will try to update it tomorrow.
is it possible to backport to 24.05?
Change:
stdenv.mkDerivation rec { pname = "postsrsd"; <del> version = "1.6"; </del> <ins> version = "1.10"; </ins> src = fetchFromGitHub { owner = "roehling"; repo = "postsrsd"; rev = version; <del> sha256 = "1dza22f0zlzsvr2dpnmsg8m8mj9rgdk0pzm1wvxrcfwyi8899ggm"; </del> <ins> sha256 = "sha256-AqOHHOnGqOnIw5hPPiJjUJFiwngTux7gwn8qig0t7hs="; </ins> }; cmakeFlags = [ "-DGENERATE_SRS_SECRET=OFF" "-DINIT_FLAVOR=systemd" ];

Discussion:
, CVSSv3=7.5 (nixos-20.09) Scanned versions: nixos-20.09: . Cc