jiebi/CodeConvo huggingface dataset:
Change:
- `util-linux` is now supported on Darwin and is no longer an alias to `unixtools`. Use the `unixtools.util-linux` package for access to the Apple variants of the utilities. <ins> - `services.keyd` changed API. Now you can create multiple configuration files. </ins> - `services.ddclient` has been removed on the request of the upstream maintainer because it is unmaintained and has bugs. Please switch to a different software like `inadyn` or `knsupdate`. - The `vlock` program from the `kbd` package has been moved into its own package output and should now be referenced explicitly as `kbd.vlock` or replaced with an alternative such as the standalone `vlock` package or `physlock`.

Discussion:
Currently options of keyd service () allow for creating single configuration file (). I need to apply different configs to different keyboards (which is possible by creating multiple conf files in ). Could NixOS keyd module expose suitable option(s) for this?
I'll look into it. Can you provide an example of what these files should look like? Is it the same as "" but with a different "id" section?
Thanks very much! Exactly. The format of all conf files is the same. Each file specifies different to match different keyboards.
Ok, I will think how I can do it nicely soon
this patch is ready. If you are using unstable nixos, you can update the packages with with a flake switch (do you use flakes?). Can you confirm that the multi-file configuration is working now?
Hello, I am using keyd and NixOS unstable. I updated my to account for the changes related to this issue. I then ran and my built-in laptop keyboard, which I use keyd with, stopped responding to input. I plugged in an external keyboard, which worked fine, and had a look at the systemd logs for keyd.service and the new configuration files. I did not see anything unusual. I then ran and my keyboard started working again. I can consistently reproduce this by rebooting and re-running the above command. If anyone else has this issue and doesn't have an external keyboard handy, I suggest trying the following steps, as these also allowed me to update without disabling my keyboard: out the portion of your NixOS config. NixOS update command e.g. portion and run again As for the new configuration: I have not tested the multi-file configuration properly as I only use it for my laptop keyboard but the new file layout looks correct .
Hi unfortunately I also have this problem from time to time when the home manager restarts many services at once. I have an easier workaround - just press . The keyd docs say this command will stop keyd, but for me it restarts it and everything works like a charm. Also try using or instead of and you should probably run into this situation less often. I think because when you create a lock file from scratch, all services will be restarted, but with the only some of them. I'm not sure though, just a guess.
Change:
sha256 = "sha256-7tptHKWkbdxTn6VIPxXE1K3opKRiUW2zv9r6J05dcS8="; }; <del> nativeBuildInputs = [ extra-cmake-modules cmake file jdk17 ninja wrapQtAppsHook ]; </del> <ins> nativeBuildInputs = [ extra-cmake-modules cmake jdk17 ninja ]; </ins> buildInputs = [ qtbase <del> qtsvg </del> zlib quazip ghc_filesystem tomlplusplus <del> ] ++ lib.optional (lib.versionAtLeast qtbase.version "6") qtwayland ++ lib.optional gamemodeSupport gamemode.dev; </del> <ins> ] ++ lib.optional gamemodeSupport gamemode; hardeningEnable = [ "pie" ]; </ins> <del> cmakeFlags = lib.optionals (msaClientID != "") [ "-DLauncher_MSA_CLIENT_ID=${msaClientID}" ] </del> <ins> cmakeFlags = lib.optionals (msaClientID != null) [ "-DLauncher_MSA_CLIENT_ID=${msaClientID}" ] </ins> ++ lib.optionals (lib.versionAtLeast qtbase.version "6") [ "-DLauncher_QT_VERSION_MAJOR=6" ]; postUnpack = '' rm -rf source/libraries/libnbtplusplus <del> mkdir source/libraries/libnbtplusplus ln -s ${libnbtplusplus}/* source/libraries/libnbtplusplus chmod -R +r+w source/libraries/libnbtplusplus chown -R $USER: source/libraries/libnbtplusplus </del> <ins> ln -s ${libnbtplusplus} source/libraries/libnbtplusplus </ins> ''; <del> qtWrapperArgs = let libpath = with xorg; lib.makeLibraryPath ([ libX11 libXext libXcursor libXrandr libXxf86vm libpulseaudio libGL glfw openal stdenv.cc.cc.lib ] ++ lib.optional gamemodeSupport gamemode.lib); in [ "--set LD_LIBRARY_PATH /run/opengl-driver/lib:${libpath}" "--prefix PRISMLAUNCHER_JAVA_PATHS : ${lib.makeSearchPath "bin/java" jdks}" # xorg.xrandr needed for LWJGL [2.9.2, 3) https://github.com/LWJGL/lwjgl/issues/128 "--prefix PATH : ${lib.makeBinPath [xorg.xrandr]}" ]; </del> <ins> dontWrapQtApps = true; </ins> meta = with lib; { homepage = "https://prismlauncher.org/";

Discussion:
It's common to use custom builds of GLFW with Minecraft, for things like improved Wayland support. At the moment, Prism Launcher is built and wrapped in a . This means that overriding libraries such as GLFW, that aren't actually used in the build process but rather used by prebuilt copies of Minecraft at runtime, result in a binary cache miss - triggering local a rebuild of the entire launcher. I propose that the wrapping pattern is implemented here, building the launch wrapper in a new derivation. This way, runtime dependencies can be changed without changing the hash of the launcher binary derivation.
This sounds like a good idea to me, let's do this
Change:
# "-Dseccomp=enabled" "-Dmanpages=enabled" "-Dconvert-icon=enabled" <del> ] ++ optional synctexSupport "-Dsynctex=enabled"; </del> <ins> "-Dsynctex=enabled" ]; </ins> nativeBuildInputs = [ meson ninja pkgconfig desktop-file-utils python3.pkgs.sphinx

Discussion:
Trying to build zathura on unstable, I get: Additional context I can't really see what might have changed recently (I think it started happening about 2 weeks ago....) for it to no longer find synctex. The texlive package is being included as a build input, which should have synctex Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
I can build zathura on master and the hydra has been doing ok. Am I missing something?
Hm, I'm not sure. I can't seem to get it to build.... "nix-build -A zathura" on master gives me the same error
This also builds for me on master. Only thing i can think of is your branch isn't up to date.
What do you think could be wrong? My sources are up to date:
I notice that I get a different drv on my system (), I think you may not be building from the master. IIRC when you run it will build from which may not point to your git checkout. If you want to build expressions from the current directory you need to do nix also can download a tarball with expressions, for example like this:
If no path is given nix-build will read and If doesn't exist it will fail. So, command is fine.
I just checked on another x86_64-linux NixOS system that evaluates to on . If the command is correct then there must be an override or an overlay in or that affects the derivation.
Oh my god, you're totally right. I had an overlay in my , which I think I had to add to disable synctex at one point when it wasn't working. Removing that and it builds fine. So sorry for wasting your guys' time but thanks for the help! (Although I wonder why it says it can't find synctex when it should have been disabled with the overlay?) Anyways, I'll close this issue, thanks again, it was driving me crazy!
What was the overlay? There may still be a bug here.
The build indeed fails with . I don't have time to open a PR now but the fix is pretty easy: can you reopen the issue?
Sure - it also fails to build with synctexSupport = false, not sure if your fix addresses that as well?
The option was introduced in I think we should just drop variant
Change:
<del> { lib, stdenv, fetchFromGitHub, rustPlatform, cmake, pkg-config, openssl, oniguruma, CoreServices, installShellFiles }: </del> <ins> { lib , stdenv , fetchFromGitHub , rustPlatform , cmake , pkg-config , openssl , oniguruma , CoreServices , installShellFiles , libsass }: </ins> rustPlatform.buildRustPackage rec { pname = "zola";

Discussion:
It doesn't work with nor with a flake. Works fine on my NixOS machine. I don't even know what means. With a flake I suspect that this is related to . I've had so many dynamic linking errors in the past week, especially from Rust stuff, that I no longer have the energy to look into this myself, hence the bug report. Please run and paste the result.
Could you (or anyone with access to aarch64-darwin) try another run against my branch?
$ nix-shell -p zola error: missing bootstrap url for platform aarch64-apple-darwin (use '--show-trace' to show detailed location information) is coming from and since the flake works you should update your channels
I'm trying your commit but it might take a while for things to compile. I'll probably ask about this on Discourse since it's unrelated to this issue but I was hoping that my Darwin machine would run the I install through the flake that makes up my dotfiles. So hopefully taking channels out of the equation, but I think that's not how it works, so I'll look into this, thanks.
that should be possible but uses channels while uses flakes. remove your channels to be sure that you're using flakes instead of channels
works, thanks! If someone needs this fix right now
Thanks Here's another way of applying the fix that doesn't require a overlay, which works for my use case:
Change:
openfire = callPackage ../servers/xmpp/openfire { }; <del> oracleXE = callPackage ../servers/sql/oracle-xe { }; </del> softether_4_25 = callPackage ../servers/softether/4.25.nix { openssl = openssl_1_0_2; }; softether_4_29 = callPackage ../servers/softether/4.29.nix { }; softether = softether_4_29;

Discussion:
I installed oracle-xe but I cannot find the password ! How to find it ?
do you have any capacity to bump the version of this software. Seems like the latest release is ... there must be a ton of CVEs against our version. ping in case you still have to manage and stuff these days (though I'm guessing not). does help at all?
Unfortunately no, since I never used it and I'd rather opt for removing it entirely if nobody suddenly steps up to maintain it.
I tried that but it doesn't work, it doesn't work at all, at least remove it from the repos
removes .
Change:
patches = [ ./dont-hardcode-ar.patch <ins> # Fix warnings from preprocessor instructions. # https://github.com/NixOS/nixpkgs/issues/59929 ./preprocessor-warnings.patch </ins> ]; doCheck = true;

Discussion:
In and it is described that to get working on a Linux kernel build, you should do: Inside that shell though, to build the kernel breaks with . Removing from the list fixes the issue. Why is that happening? If we can't fix it, we should at least update the wiki and manual. Full repro with and nixpkgs commit :
Seems to be caused by this change in the kernel: With this recent change, the kernel tries to use to find include and library flags for libelf, and fails back to the old behavior of assuming it's available in the default include/library directories. Running within shows something like: . These are flags so the compiler does not treat them like system includes and does not inhibit warnings from these headers. Making available makes the kernel use those flags, so libelf is included normally, leading to the warning and error, presumably because some kernel makefile adds to compiler flags. Without available, the libelf headers are found through include paths automatically by which are flags so warnings from those headers are ignored. I see different ways to fix this: Patch the libelf file to use instead of . Patch libelf headers to not produce those warnings. Patch the kernel to disable those warnings before including libelf (and re-enable). Any opinions?
is it normal for libelf headers to generate these warnings ? isn't that an upstream issue in some way ? I would vote for 2 ("fix libelf headers") since other approaches have their downsides: patching libelf's .pc may hide warnings for normal packages as I sometimes develop on the kernel, the more we patch its sourcecode, the more annoyed I get (pollutes git status etc.)
I'd agree that it's an upstream bug. Ran into this on my Gentoo system earlier, noticed something about those headers, and figured I'd chime in: they should be using instead of Relatively simple change, should fix the problem entirely. Edit: I'll try to send a patch upstream tomorrow or Friday. Uh, that is, today or Friday. It's past midnight. Oops.
Change:
hardeningDisable = [ "format" ]; # https://github.com/joncampbell123/dosbox-x/issues/4436 <ins> # Build optional App Bundle target, which needs at least one arch-suffixed binary postBuild = lib.optionalString stdenv.hostPlatform.isDarwin '' cp src/dosbox-x src/dosbox-x-$(uname -m) make dosbox-x.app ''; </ins> postInstall = lib.optionalString stdenv.hostPlatform.isLinux '' wrapProgram $out/bin/dosbox-x  --prefix PATH : ${lib.makeBinPath [ yad ]} <ins> '' # Install App Bundle, wrap regular binary into bundle's binary to get the icon working + lib.optionalString stdenv.hostPlatform.isDarwin '' mkdir $out/Applications mv dosbox-x.app $out/Applications/ mv $out/bin/dosbox-x $out/Applications/dosbox-x.app/Contents/MacOS/dosbox-x makeWrapper $out/Applications/dosbox-x.app/Contents/MacOS/dosbox-x $out/bin/dosbox-x </ins> ''; passthru.tests.version = testers.testVersion {

Discussion:
An empty icon is displayed in the dock when I launch dosbox-x built with Nix.
Thanks, all good now
Change:
meson ninja gtk3 <del> pkgconfig </del> <ins> pkg-config </ins> check ];

Discussion:
Describe the bug Setting the variable to , as suggested , does nothing. Unsetting results in this error: Expected behavior There are two issues. First, the Enlightenment Foundation Libraries are not complied with Wayland support. Secondly, the variable needs to be set correctly a Wayland environment. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Maintainer information:
PR fixes this issue. Tested terminology with sway. The environment variable should not be set. In my test it was not needed to set . !
Change:
<ins> --- a/configure +++ b/configure @@ -5894,9 +5894,9 @@ else die "ERROR: cannot find soundtouch 1.8.0 or later." fi -if [ $target_os = "linux" ] ; then -    . /etc/os-release -fi +# if [ $target_os = "linux" ] ; then +#     . /etc/os-release +# fi # libudfread if enabled system_libudfread ; then </ins>

Discussion:
MythTV current version 31.0 desired version 32.0 Note to maintainer I tried installing Mythtv 31.0 in the latest version of NixOS and the following error appeared. collect2: error: ld returned 1 exit status For full logs, run 'nix log /nix/store/i7hayl96078skrs46yksjqxjsh31cmfv-mythtv-'. Reading the log displayed error: experimental Nix feature 'nix-command' is disabled; use '--extra-experimental-features nix-command' to override
started working on this, bump for version is , but doesn't build yet on NixOS master branch. first quick look on the error tells something about FFmpeg and impure path (see below). I'll check this later as my first priority is getting it to build and run on NixOS 22.05 the log reading is a bit confusion, you have to append literally (). so your command from the example you provided would be
I am currently building MythTV 32.0 (sha256 = "0i4fs3rbk1jggh62wflpa2l03na9i1ihpz2vsdic9vfahqqjxff1") with two patches. The first is called : The second patch is called . I patched it up , and it looks like my patch has been . Here is that patch: My current derivation is like this: Sorry that was back in April and I didn't propagate my changes to NixOS yet!
it looks like your branch and mine are basically the same except for the . I don't know if it is better to add my patch, or for you to move to a version of MythTV after the pull mentioned above.
I didn't paste my whole , there are also new deps (soundtouch, libzip) which you can see in the branch by
I the patch on top of 's branch . I haven't tried building it yet since my machine is already building my original version of the derivation in the background (due to NixOS upgrade), and it takes hours. That is actually what prompted me to notice this issue :).
I'll try if my issue is gone with your patch now (I also need lots of time for one build).

Going forward I think it's best to use the release version of MythTV 32 and your patch for bumping the version in NixOS. I'll however try the other route with the MythTV version after the merge of your fix as I want to set up a combination of official and my own packages anyway.
I'm happy to confirm that both routes work. for the one with the updated MythTV version I took the commit of the pull request mentioned. would you be so kind and open a pull request for the version bump ?
Change:
<del> diff --git a/CMakeLists.txt b/CMakeLists.txt index 1ea7c1df..b0face0d 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -176,6 +176,10 @@ ELSE() SET (SKIP_COMPONENTS "N-O-N-E") ENDIF() +IF (WITHOUT_CLIENT) +  SET (SKIP_COMPONENTS "Client|ClientPlugins|ManPagesClient") +ENDIF() + OPTION(NOT_FOR_DISTRIBUTION "Allow linking with GPLv2-incompatible system libraries. Only set it you never plan to distribute the resulting binaries" OFF) INCLUDE(check_compiler_flag) </del>

Discussion:
Describe the bug Erorr first init mysql databases if use package builded To Reproduce Steps to reproduce the behavior: this patch command Expected behavior Error running this command Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: cc
Thanks for reporting Any of the , , , options require a client so I'm guessing the best we can do is document this. Any other ideas
is an argument that is only available for the derivation, and is not exposed in - so it's hard people stumble over this by accident. They need to explicitly set a global package override. Also, as error message by itself should already be clear enough, especially when looking at the system configuration. I don't consider this a bug. It works as intended - if you override mysql globally to not contain the client components, you'd have to expect client operations to fail. given you by yourself in , and it doesn't really work properly anyways, what about removing that argument?
When I made this parameter, I did not test database creation on first run. I wanted to split mariadb into components - server and client. Example in another distribution: But due to the different file locations, occur such errors. Is this variant bad? (Not worked witn MySQL 8.0)
If you use then there no reason to split package because you install both anyways. Arch Linux probably doesn't offer option so it makes sense.
What was the initial idea of having a server without the client binaries? Closure size reduction? In that case pulling in the client anyways in a separate derivation doesn't make much sense. I understand we want to have a separate client without pulling in server components (and we have that for mariadb), but I having the server without client isn't much of use. There's usually enough storage space on the database server to also ship the client binaries, and they are needed for most options in the mysql module, as well as for local administration / backups anyways. I'm pretty much for removing the argument. It causes a lot of confusion when uses for arguable benefit.
Change:
{ lib, stdenv, fetchurl, substituteAll <del> , pkg-config </del> <ins> , pkg-config, autoreconfHook </ins> , cups, zlib, libjpeg, libusb1, python3Packages, sane-backends , dbus, file, ghostscript, usbutils , net-snmp, openssl, perl, nettools, avahi

Discussion:
The recent fixes to disable in hplip didn't seem to properly work on , making the whole package fail with a cryptic error. Additionally, due to a dependency failure in PyQt5, the package further refuses to build unless it's disabled. Steps to reproduce the behavior: an aarch64-linux user it fail due to PyQt5 failure that PyQt5 support can be disabled it fail again with -related errors hplip works n/a Current unstable as of writing this is . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --cc as maintainer
cc as PyQt5 maintainer due to dependency failure - should a separate issue be filed for this?
Can reproduce. I ended up moving the print server to a x86-64 machine which was conveniently only a ~meter away from the RPi.
Also got bit by this on a RaspberryPi 4 server upgrade to 22.05. Did a bit of investigation, and came up with an overlay workaround (and hplip upgrade to 3.22.4) using a patch by the Debian crew: The meat of the issue comes down to the HP folks feeling the need to include their non-free x86/-64 'ImageProcessor' in the default build (even when the applicable flag is specified). So the community consensus is hoping that HP will fix/revert this, but until then everyone's just patching it out. Could this patch be to the patch list (and likely update hplip to 3.22.4) ?
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
owner = "OpenMW"; repo = "openmw"; rev = name; <del> sha256 = "0lj8v81hk807dy0wcdhfp0iyn4l5yag53hx1a6xm44gh2dpyil43"; </del> <ins> sha256 = "1nybxwp77qswjayf0g9xayp4x1xxq799681rhjlggch127r07ifi"; </ins> }; enableParallelBuilding = true;

Discussion:
The version claimed to be produced by the openmw derivation is , however once installed it is still version system: host os: multi-user?: sandbox: version: channels(avery): channels(root): nixpkgs:
Change:
}; }; in <del> self </del> <ins> lib.warnIf (withXclip != null || withWlClipboard != null || withWlclip != null) '' The options `withXclip`, `withWlClipboard`, `withWlclip` were removed. If you are seeking for clipboard support, please consider the following packages: - `micro-with-wl-clipboard` - `micro-with-xclip` - `micro-full` '' self </ins>

Discussion:
The current package depends on wayland/x11, making its use in servers unnecessarily cumbersome. This is nothing a simple overlay can't help with, but that requires building the package from source and is yet another thing to learn for newbies (plus, some may not notice the dependencies and inadvertently end up putting wayland on their servers... ask me how I know :wink:). Would a separate (or similar name) package be worth it? (possibly, together with some options?) mantainers: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
We have no explicit policy prohibiting green aliases. I will create something about this. On the other hand I do not see why creating a dedicated NixOS module for it - at least not now. You can merely throw it at environment.systemPackages and the effect will be the same.
concurrent effort ^
/ I would suggest a huge load of modifications in your idea, so here is my implementation:
Change:
radarr = handleTest ./radarr.nix {}; radicale = handleTest ./radicale.nix {}; rasdaemon = handleTest ./rasdaemon.nix {}; <ins> readarr = handleTest ./readarr.nix {}; </ins> redis = handleTest ./redis.nix {}; redmine = handleTest ./redmine.nix {}; restartByActivationScript = handleTest ./restart-by-activation-script.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.