jiebi/CodeConvo huggingface dataset:
Change:
gv = callPackage ../applications/misc/gv { }; <ins> gvisor = callPackage ../applications/virtualization/gvisor { }; gvisor-containerd-shim = callPackage ../applications/virtualization/gvisor/containerd-shim.nix { }; </ins> guvcview = callPackage ../os-specific/linux/guvcview { }; gxmessage = callPackage ../applications/misc/gxmessage { };

Discussion:
"Sandboxed container runtime" Bonus points for NixOS option for docker support :P. But just having it to poke at would be neat, i think!
I've looked quickly at this, and it seems like the main limitation in implementing this is . I think we either have to patch Bazel in NixOS or any Bazel package that compiles Go to fix this...
Change:
rustPlatform.buildRustPackage rec { pname = "helvum"; <del> version = "0.2.1"; </del> <ins> version = "0.3.0"; </ins> src = fetchFromGitLab { domain = "gitlab.freedesktop.org"; owner = "ryuukyu"; repo = pname; rev = version; <del> sha256 = "sha256-ZnpdGXK8N8c/s4qC2NXcn0Pdqrqr47iOWvVwXD9pn1A="; </del> <ins> sha256 = "sha256-AlHCK4pWaoNjR0eflxHBsuVaaily/RvCbgJv/ByQZK4="; </ins> }; <del> cargoSha256 = "sha256-2v2L20rUWftXdhhuE3wiRrDIuSg6VFxfpWYMRaMUyTU="; </del> <ins> cargoSha256 = "sha256-mAhh12rGvQjs2xtm+OrtVv0fgG6qni/QM/oRYoFR7U8="; </ins> nativeBuildInputs = [ clang copyDesktopItems pkg-config ]; buildInputs = [ glib gtk4 pipewire ];

Discussion:
Helvum build is broken on unstable Steps to reproduce the behavior: master helvum Build suceeds. Since it's pipewire-sys crate that fails, I suspect it was a pipewire upgrade that broke it Maintainer information:
Trying to build latest helvum master, as it's now been updated to use pipewire from Will post updates.
Alright, it fails even with the latest master, so I assume it's a pipewire error. is the maintainer of the PipeWire package and the leader of the PipeWire efforts on Nix/OS so they may know more about this. In the meantime, helvum will remain broken :(
Is it the same error? Could be that the bindings need an upgrade to support the newer version of pipewire because of changed APIs. Then that would be a bug in the pipewire-sys crate.
Yes, it's exactly the same error. You're right, I'll look into pipewire-related issues on GitLab to try and see what's going on.
I found , which means we have to wait a bit until that gets merged.
The issue links to this pull request: Not sure how it's with crates, but the dependency could be patched using this patch: (This is the alternative to waiting until that's resolved)
Sure, I'll get to work then.
Strictly speaking I'm not officially maintaining the pipewire package, but I guess I've effectively become the de facto maintainer anyway.
Sorry for mispinging you then!
No problem. I originally just wanted to get some progress and organization in the messy packaging situation. I hope that the official maintainers and autoupdate bot can take over again once upstream stabilizes more. I'm not actually sure who exactly the official maintainers would be, though. The package just says "freedesktop maintainers". EDIT: and I did end up following upstream development pretty closely so pinging me was a very reasonable guess.
as it currently stands, I don't think it's possible to override the dependency with a nix-built one. Though I have made a nix derivation for it, there's no way to propagate it to using . In turn, I'll wait and see what Ryuukyu does upstream.
I've fixed pipewire-rs and helvum and made a new release, so it should now build again once you update the package.
! Can confirm it works. Thanks
Change:
# Please dont edit it manually, your changes might get overwritten! { fetchNuGet }: [ <del> (fetchNuGet { pname = "AAXClean"; version = "1.1.1"; sha256 = "025mwa4hlxi8mg4g5pqf2wpm3w6i2v6zv23s815cs0rbc259f1c2"; }) (fetchNuGet { pname = "AAXClean.Codecs"; version = "1.1.1"; sha256 = "1hqyfxssjk5qz2ig4ldmzs9ji58vpmpyramzj191c75s9fylysgh"; }) (fetchNuGet { pname = "AudibleApi"; version = "8.5.0.1"; sha256 = "0d0rdcsw8pfwym6rwrpyvlzciqxrq6gbb2csjg4zssca5mf0yz7h"; }) </del> <ins> (fetchNuGet { pname = "AAXClean"; version = "1.1.2"; sha256 = "0hxn1giq99rcd6z43ar79awlzyv0mnxpvmarsl2ypi52d3dizf01"; }) (fetchNuGet { pname = "AAXClean.Codecs"; version = "1.1.3"; sha256 = "0hqj9hslscl110h2mr7mf0lb0s7dczx73mplkpgx1gpshyfg5xj8"; }) (fetchNuGet { pname = "AudibleApi"; version = "9.0.0.1"; sha256 = "1j6bigvvldg4m82vb7ry8y06sh3a0q4mdshlsrppq6bivwsalazc"; }) </ins> (fetchNuGet { pname = "Avalonia"; version = "11.0.5"; sha256 = "1l8vpw7dmkgll197i42r98ikkl0g08469wkl1kxkcv8f0allgah6"; }) (fetchNuGet { pname = "Avalonia.Angle.Windows.Natives"; version = "2.1.0.2023020321"; sha256 = "1az4s1g22ipak9a3xfh55z2h3rm6lpqh7svbpw6ag4ysrgsjjsjd"; }) (fetchNuGet { pname = "Avalonia.BuildServices"; version = "0.0.29"; sha256 = "05mm7f0jssih3gbzqfgjnfq5cnqa85ihsg0z1897ciihv8qd3waq"; })

Discussion:
Package name: libation Latest released version: 11.3.1 <!-- Search your package here: --- Current version on the unstable channel: 11.1.0 Current version on the stable/release channel: 11.1.0 <!-- 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:
{ lib, buildGoModule, fetchFromGitHub, stdenv, pkg-config, rustPlatform, libiconv, fetchpatch, nixosTests }: let <del> libflux_version = "0.188.0"; </del> <ins> libflux_version = "0.194.5"; </ins> <del> # This is copied from influxdb2 with flux version matching the needed by thi </del> <ins> # This is copied from influxdb2 with the required flux version </ins> flux = rustPlatform.buildRustPackage rec { pname = "libflux"; version = "v${libflux_version}";

Discussion:
Steps to reproduce the behavior: There appears to be a cache miss, because starts to be compiled, but it fails. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
the maintainers to tag would be for v2 and and for v1 (all share the same build failure). v2 will be addressed via
Apologies. Thank you.
Change:
testScript = '' machine.wait_for_unit("sockets.target") machine.wait_for_unit("lxd.service") <ins> machine.wait_for_file("/var/lib/lxd/unix.socket") </ins> # It takes additional second for lxd to settle machine.sleep(1)

Discussion:
Please find stable urls for the lxd container tests these fail to download now and are causing test failures: cc
Thanks for pinging - I will fix it later today :-)
Change:
{ lib, stdenv, fetchurl, intltool, gettext, coreutils, gnused, gnome , gnugrep, parted, glib, libuuid, pkg-config, gtkmm3, libxml2 , gpart, hdparm, procps, util-linux, polkit, wrapGAppsHook, substituteAll <ins> , mtools, dosfstools </ins> }: stdenv.mkDerivation rec {

Discussion:
Describe the bug GParted in the installation ISO images cannot create, resize, move and do other operations on many filesystems such as FAT32. This problem is due to absence of related (optional) run-time dependencies such as and (in the case of FAT32). in live session doesn't solve the problem. The supports to filesystems other than ext4 is important especially when you need to operate on the EFI System Partition (ESP), NTFS for Windows, HFS for Mac, and BTRFS used by some other Linux distributions. Possible solution includes: all the run-time dependencies required for GParted to operate on those filesystems in the list in . a new package, , and show it in . Replace with 'gparted-full' in list in . To Reproduce Steps to reproduce the behavior: Go to and download the 64bit Plasma Desktop ISO image, which is the image after burning it to a USB stick or attaching to a virtual machine. sure that there is a FAT32 partition on your machine. Most computers have EFI System Partition, which is usually FAT32. If there isn't any, an USB stick with a FAT32 partition can be attachede GParted and right-click on the FAT32 partition, it can be noticed that some options including are grayed out. -click on an un-allocated space, click , and it can be seen that many options including FAT32 have been grayed out. Expected behavior GParted on the ISO installation image can operate on all or most of the supported file systems. Screenshots If applicable, add screenshots to help explain your problem. Additional context Filesystems supported by GParted: 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 Please run and paste the result. Maintainer information:
I had the same issue now.
Related
Change:
<ins> # Contributing to this documentation {#chap-contributing} The DocBook sources of the Nixpkgs manual are in the [doc](https://github.com/NixOS/nixpkgs/tree/master/doc) subdirectory of the Nixpkgs repository. You can quickly check your edits with `make`: ```ShellSession $ cd /path/to/nixpkgs/doc $ nix-shell [nix-shell]$ make $makeFlags ``` If you experience problems, run `make debug` to help understand the docbook errors. After making modifications to the manual, it's important to build it before committing. You can do that as follows: ```ShellSession $ cd /path/to/nixpkgs/doc $ nix-shell [nix-shell]$ make clean [nix-shell]$ nix-build . ``` If the build succeeds, the manual will be in `./result/share/doc/nixpkgs/manual.html`. </ins>

Discussion:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! here that you intend to work on it. (Please also post if you stop working on it.) a new branch of nixpkgs master. to . the contents from Docbook to CommonMark. Follow . Use existing .md sections for inspiration. from the folder to build the manual. the manual on your computer at after running from doc/ folder: it looks good, submit a PR and reference this issue.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
I am currently working on it :-)
I opened a PR here: Thanks in advance for reviewing :-)
I'll do the section.
Nice! I amended the issue title for correctness sake.
Change:
homepage = "https://gitlab.com/schmiddi-on-mobile/railway"; license = lib.licenses.gpl3Plus; mainProgram = "diebahn"; <del> maintainers = with lib.maintainers; [ dotlambda ]; </del> <ins> maintainers = with lib.maintainers; [ dotlambda lilacious ]; </ins> }; }

Discussion:
how Steps to reproduce the behavior: ... ... ... alias diebahn to railway-travel or vice versa If applicable, add screenshots to help explain your problem. Add any other context about the problem here. you two fight Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
any way for ci to detect double packages perhaps through source? are there more duplicates in nixpkgs?
MB, I did not realize that it was packaged already , it didn't occurred to me to search for the name of the binary instead of the project name. If is fine with it, we could put an alias in place and treat it like a refactoring to pkgs/by-name. Otherwise I will remove my package.
Please remove your package Feel free to add yourself to diebahn's maintainers.
Alright, will do. Should I add an alias for railway-travel that points to diebahn?
You can if you think it helps people find the package in the future.
Change:
stdenv.mkDerivation (finalAttrs: { pname = "qmplay2"; <del> version = "23.08.22"; </del> <ins> version = "23.10.22"; </ins> src = fetchFromGitHub { owner = "zaps166"; repo = "QMPlay2"; rev = finalAttrs.version; fetchSubmodules = true; <del> hash = "sha256-Ug7WAqZ+BxspQUXweL/OnVBGCsU60DOWNexbi0GpDo0="; </del> <ins> hash = "sha256-yDymUXuILgT4AFTt302GniPi/WNwrTCOuOfdUiKOIyk="; </ins> }; nativeBuildInputs = [

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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:
auto-patchelf-hook = callPackage ./auto-patchelf-hook { }; systemd = callPackage ./systemd { }; <ins> substitute = recurseIntoAttrs (callPackage ./substitute { }); </ins> }

Discussion:
Using with , currently does not allow me to replace a string that contains spaces. Steps to reproduce the behavior: the code below: It gives the following error: I tried quoting it, escaping the spaces... but none of them seemed to work. The I did succeeds. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. I posted this in the NixOS matrix room a while ago (but I forgot to submit an issue): !$ People showed me some bash magic I couldn't understand, I think they might be helpful and worth checking out. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (git blame) cc (people in the original conversation) Please run and paste the result. (I'm sorry if I described anything incorrectly, I'm a not a native English speaker and I am still trying to improve my language skills) Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Should be fixed with , please give it a try :)
Wonderful! It worked for me
Change:
rabbitmq-server = callPackage ../servers/amqp/rabbitmq-server { inherit (darwin.apple_sdk.frameworks) AppKit Carbon Cocoa; <ins> elixir = elixir_1_12; </ins> }; radicale1 = callPackage ../servers/radicale/1.x.nix { };

Discussion:
rabbitmq-sever build error caused by rabbitmqctl does not support Elixir 1.13.1 -shell -p rabbitmq-server rabbitmq-sever built and installed on the nix shell. was released in and was updated in but . I am very new to NixOS project, so I am not sure how these conflicts are commonly resolved. I tried to build with and it built it successfully, just replacing with in rabbitmqserver'd .
thanks for reporting! The right way to patch this is to go to , find , and add a line like in its . Do you want to give it a try and open a PR?
Sure, I've just opened the PR , although apart from building the package I don't know how to test the built package. I am very new on this :D.
Change:
<ins> diff -u -r a/src/wl/sys/wl_linux.c b/src/wl/sys/wl_linux.c --- a/src/wl/sys/wl_linux.c	2022-03-23 00:35:42.930416350 +0000 +++ b/src/wl/sys/wl_linux.c	2022-03-23 00:40:12.903771013 +0000 @@ -2980,7 +2980,11 @@ else dev->type = ARPHRD_IEEE80211_RADIOTAP; +#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 17, 0) bcopy(wl->dev->dev_addr, dev->dev_addr, ETHER_ADDR_LEN); +#else +	eth_hw_addr_set(wl->dev, dev->dev_addr); +#endif #if defined(WL_USE_NETDEV_OPS) dev->netdev_ops = &wl_netdev_monitor_ops; @@ -3261,7 +3265,11 @@ static ssize_t wl_proc_read(struct file *filp, char __user *buffer, size_t length, loff_t *offp) { +#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 17, 0) wl_info_t * wl = PDE_DATA(file_inode(filp)); +#else +	wl_info_t * wl = pde_data(file_inode(filp)); +#endif #endif int bcmerror, len; int to_user = 0; @@ -3318,7 +3326,11 @@ static ssize_t wl_proc_write(struct file *filp, const char __user *buff, size_t length, loff_t *offp) { +#if LINUX_VERSION_CODE < KERNEL_VERSION(5, 17, 0) wl_info_t * wl = PDE_DATA(file_inode(filp)); +#else +	wl_info_t * wl = pde_data(file_inode(filp)); +#endif #endif int from_user = 0; int bcmerror; </ins>

Discussion:
fails to build when I tried to execute . Steps to reproduce the behavior: should build successfully. ! There are no maintainers for anymore, so I'll instead mention the last contributors.
Sorry but I no longer have a machine that uses that driver, but it looks like it's broken with linux 5.17. Here is the patch used by Arch:
Likewise I dont have a machine that runs this driver anymore
Same issue for me on 3 machines. The odd thing, the issue still remains after a temp fix of;
Can confirm that this is working with Will try to PR the patch.
Any idea when this issue will be resolved via the patch? I just failed to compile broadcom_sta when attempting to upgrade to kernel 5.17.1 on a Macbook Pro late 2013.
It's unlikely to happen anytime soon, since it looks like no one with merging permission has hardware that uses this driver. Maybe if has some time he could review it since he is already familiar with it, and it seems that the PR is just the patch used by Arch. In the meantime you can try and the made bye X9VoiD.
Change:
"man" ]; <ins> passthru.tests = { version = testers.testVersion { package = afew; }; }; </ins> meta = with lib; { homepage = "https://github.com/afewmail/afew"; description = "An initial tagging script for notmuch mail";

Discussion:
The package seems to be missing in . Something like the following help output: Searching for the error message suggests that is from and overriding the derivation to include in seems to fix the issue. However, I do not have enough experience with Python packaging in NixOS to know whether that is sufficient/the right thing to do. Please run and paste the result.
This probably regressed in - cc
Provided a fix, PTAL.
Change:
{ imports = [ (mkRemovedOptionModule [ "services" "samba" "defaultShare" ] "") <ins> (mkRemovedOptionModule [ "services" "samba" "syncPasswordsByPam" ] "This option has been removed by upstream, see https://bugzilla.samba.org/show_bug.cgi?id=10669#c10") </ins> ]; ###### interface

Discussion:
I tried to enable syncing Unix passwords to Samba via PAM using the option. However, I see a bunch of errors in the logs because the library PAM is looking for, , doesn't exist. Use the following config: Please run and paste the results. system: host os: multi-user?: sandbox: version: channels(USER): channels(root): nixpkgs:
Same issue here. The folder it was searching for () only contains on my system. Additionally, querying for presents no results.
Just experienced exactly same issue on 19.03. Is samba broken in this release?
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly: for maintainers and people that previously touched the related code and @ mention them in a comment. on the . on the on .
It's still relevant now. I noticed this issue in my system logs as well. Samba is not broken, they've just deprecated this feature. See and . Here's a PR for us:
Change:
exec "$APPIMAGE_DEBUG_EXEC" fi <del> exec ./AppRun </del> <ins> exec ./AppRun "$@" </ins> ''; })

Discussion:
I tried to run using . I noticed two things: was missing. Adding it to fixes that issue. Is supposed to be able to run all appimages? Should we add ? command line arguments aren't passed on to the appimage CC
I haven't decided yet. Common libraries currently not available to appimage-run should be to the list, but I think unreasonable libraries that are only used by a single application shouldn't be . Anything in should be okay to add, which would include . Oh right, I noticed that a while ago, and then forgot to fix it.
That is a useful list. I used a bash monster to look for libraries missing in our :
Of those the following are available in nixpkgs:
Change:
more-properties = callPackage ../development/python-modules/more-properties { }; <ins> morecantile = callPackage ../development/python-modules/morecantile { }; </ins> moreorless = callPackage ../development/python-modules/moreorless { }; moretools = callPackage ../development/python-modules/moretools { };

Discussion:
Project description User friendly Rasterio plugin to read raster datasets. Metadata homepage URL: source URL: license: bsd platforms: unix Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Already packaged by in . Should be easy to add to nixpkgs.
Requires morecantile and pystac, that shoud be to nixpkgs as well.
Change:
src = "${src}/cuTENSOR"; <ins> buildInputs = [ cutensor ]; </ins> cmakeFlags = [ "-DCUTENSOR_EXAMPLE_BINARY_INSTALL_DIR=${builtins.placeholder "out"}/bin" ];

Discussion:
From what I could tell this was only mentioned in some comment of a closed PR. This is blocking me from wrapping up a flake for Invoke AI (a Stable Diffusion webui). Any help/advice would be appreciated. This was described on Discourse by :
What commit of nixpkgs are you using? I might have some cycles this weekend to spend on this.
Looks like the cause is an outdated version of cutensor. It appears cupy is the only dependent of that so hopefully an upgrade is simple. I am working on a patch now.
Change:
GTK_PATH = [ "/lib/gtk-2.0" "/lib/gtk-3.0" ]; XDG_CONFIG_DIRS = [ "/etc/xdg" ]; XDG_DATA_DIRS = [ "/share" ]; <ins> XCURSOR_PATH = [ "/share/icons" ]; </ins> MOZ_PLUGIN_PATH = [ "/lib/mozilla/plugins" ]; LIBEXEC_PATH = [ "/lib/libexec" ]; };

Discussion:
In the Xfce "Mouse and Touchpad" settings, in the Theme tab, no cursor themes are shown other than Default. The cursor size option has no effect. Even after installing (a set of cursor themes) via , no cursor themes are available. System: NixOS 16.09
I have the same problem with the Windows Manager Only setup. NO desktop environment. LXappearance did show the mouse themes not after I copy some Cursor themes manually into but still refuse to change the theme. also I am not using XCURSOR_PATH environment variable. if there that is the solution how should i implement it?
This is a serious issue for me, as it's very hard to see the mouse cursor on a retina display with the default size. If there is any temporary workaround to change the size/theme, please let me know, that would be very useful. EDIT: I'm running latest unstable
The workaround is to add these to your (this is what my patch makes the default):
"error: The option value ' is not a string or list of strings."
the error suggests you didn't enter it right, it's environment.profileRelativeEnvVars not environment.variables.profileRelativeEnvVars.
I've made your necessary changes which allowed a rebuild however my mouse cursor still does not adopt a new cursor theme.
Just to say that I got my custom cursor working by following advice, thanks a lot for the help!
My cursor is only custom mousing over some applications. Any of the Xfce system applications launched as user display the old default but qutebrowser and emacs shows my new cursor. Here's my .
Adding in conjunction with two lines has fixed this issue for me.
This has been fixed in . I can't reproduce the issue (tried ): system: host os: multi-user?: sandbox: version: channels(root): channels(chronos): nixpkgs:
Same problem in Gnome. My Icon Themes placed in are listed and defined, but not applied.
Change:
{ stdenv, lib, makeDesktopItem, makeWrapper, lndir, config <del> , replace, fetchurl, zip, unzip, jq </del> <ins> , replace, fetchurl, zip, unzip, jq, xdg_utils </ins> ## various stuff that can be plugged in , flashplayer, hal-flash

Discussion:
Describe the bug "Set browser as default" functionality doesn't work for Firefox and Chromium in Sway. (bspwm and other x11 wms worked) Additional context If I have xdgutils installed globally, it works as expected. Notify maintainers xdgutils & firefox: firefox: Metadata Please run and paste the result.
Chromium seems to be ok now.
Added additional context, which might lead to solving the main issue.
Oh, I forgot that this is also for Firefox.