jiebi/CodeConvo huggingface dataset:
Code change:
systemd.packages = [ pkgs.tracker ]; <ins> environment.variables = { TRACKER_CLI_SUBCOMMANDS_DIR = let subcommandPackagesTree = pkgs.symlinkJoin { name = "tracker-with-subcommands-${pkgs.tracker.version}"; paths = [ pkgs.tracker ] ++ cfg.subcommandPackages; }; in "${subcommandPackagesTree}/libexec/tracker3"; }; </ins> }; }

Related discussion:
text: Pretty much all commands just show the "usage" output, regardless if the input is correct or not. For example, outputs: Steps to reproduce the behavior: , , , and many other commands incorrect output I expect to see the correct output, for example should show the current status of all miners.
How did you determine the commands? The printed help page does not list any of those as supported.
I got the commands from the Tracker documentation: You are right that they aren't listed in the help page. I do have manuals with usage for all those commands installed though.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Code change:
gtkspell3 libgee pantheon.granite <ins> pcre </ins> sqlite webkitgtk ];

Related discussion:
text: Describe the bug To Reproduce Steps to reproduce the behavior: Expected behavior no fail Additional context it seem to be fixed upstream, but no new release it made yet Notify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Code change:
activitywatch = callPackage ../applications/office/activitywatch/wrapper.nix { }; <ins> aw-watcher-window-wayland = callPackage ../tools/wayland/aw-watcher-window-wayland {  }; </ins> adobe-reader = pkgsi686Linux.callPackage ../applications/misc/adobe-reader { }; adl = callPackage ../applications/video/adl { };

Related discussion:
text: Project description aw-watcher-window-wayland is a part of ActivityWatch needed to have it working in a Wayland compositor. At the present time, without this, the ActivityWatch package is not working on Wayland environments Metadata homepage URL: source URL: license: MPL-2.0 license platforms: linux
Code change:
"['pandas/src/klib', 'pandas/src', '$cpp_sdk']" ''; <del> setupPyBuildFlags = [ </del> <ins> # Parallel Cythonization is broken in Python 3.8 on Darwin. Fixed in the next # release. https://github.com/pandas-dev/pandas/pull/30862 setupPyBuildFlags = optionals (!(isPy38 && isDarwin)) [ </ins> # As suggested by # https://pandas.pydata.org/pandas-docs/stable/development/contributing.html#creating-a-python-environment "--parallel=$NIX_BUILD_CORES"

Related discussion:
text: Describe the bug I cannot make a shell with pandas installed. To Reproduce Expected behavior A shell opens and works. Additional context <details<summaryI get this error message:</summary</detailsNotify maintainers Metadata system: host os: multi-user?: sandbox: version: channels(noah): nixpkgs: Maintainer information:
Code change:
zope_configuration ]; <ins> checkInputs = [ docutils sphinx ]; </ins> patches = [ (fetchpatch { url = "https://gitlab.com/mailman/mailman/-/commit/4b206e2a5267a0e17f345fd7b2d957122ba57566.patch";

Related discussion:
text: Steps to reproduce the behavior: $ nix build --verbose The interesting thing is that I can build the flask-sqlalchemy package just fine: system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Code change:
''; homepage = "https://strlen.com/treesheets/"; <del> maintainers = with maintainers; [ obadz avery ]; </del> <ins> maintainers = with maintainers; [ obadz ]; </ins> platforms = platforms.unix; license = licenses.zlib; };

Related discussion:
text: I became marked as a maintainer on the package many years ago, but since then I have changed careers and have slowly stopped using nixos as much. I don't currently have git installed (and I don't really remember how to use it) Please remove me from the maintainer list I am in the maintainer list as follows:
Code change:
User = cfg.user; Group = cfg.group; PermissionsStartOnly = "true"; <del> ExecStart = "${pkgs.mono}/bin/mono ${pkgs.emby}/bin/MediaBrowser.Server.Mono.exe"; </del> <ins> ExecStart = "${pkgs.emby}/bin/MediaBrowser.Server.Mono"; </ins> Restart = "on-failure"; }; };

Related discussion:
text: Emby uses ffmpeg for transcoding media and for generating thumbnails. Emby fails to find the FFmpeg binary during the setup wizard but can be specified manually if FFmpeg has been installed separately. Add to , browse to , and advance through the wizard. System: 17.03pre92039. (Gorilla) Nix version:nix-env (Nix) 1.11.4 Nixpkgs version: 17.03pre92039.
cc
Funny thing is that I was just watching a movie when I was mentioned on a system without any ffmpeg/ffprobe binary. My system was upgraded from an older version (config was already existing so no check was done by the wizard). I was able to reproduce the issue. Will take a more detailed look at it sometime tomorrow :)
Code change:
buildPythonPackage rec { pname = "msal"; <del> version = "1.29.0"; </del> <ins> version = "1.30.0"; </ins> pyproject = true; disabled = pythonOlder "3.7"; src = fetchPypi { inherit pname version; <del> hash = "sha256-j2cl8Jl1JVP5sv6EEl4qXr5HtJ+S6syjPr7dOp66riU="; </del> <ins> hash = "sha256-tL8AhQCS5GUVfYFO+iShj3iChMmkeUkQJNYpAwheovs="; </ins> }; <del> nativeBuildInputs = [ setuptools ]; </del> <ins> build-system = [ setuptools ]; </ins> <del> propagatedBuildInputs = [ </del> <ins> dependencies = [ </ins> cryptography pyjwt requests

Related discussion:
text: Trying to run an action with azure-cli that requries authentication, az will fail to read the cached authentication token from the token cache: This is due to a version mismatch of . will update the package, I checked that the authentication works afterwards. That's me! Please run and paste the result. ` Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I also experience this issue with , as well as with . Thanks for adding the fix!
Code change:
ctl.!default { type pulse } <ins> ${alsaCfg.extraConfig} </ins> ''); in {

Related discussion:
text: Setting to while setting to any non-empty value will cause a build failure because and both attempt to create The correct result would be for the contents of to be written out at the end of , after the stanzas provided by pulseaudio. Somewhat relatedly, the in and in pulseaudio's generated config doesn't make a whole lot of sense. means "override", currently there is nothing for it to override, and we would like user config to override generated config, not the other way around. However, as long as user config is placed in the file after generated config then I don't think the actually makes any difference.
I am having this issue as well. Easily replicated by setting those two options.
Can you make a pull request?
Should be fixed with . If there still is a problem, please reopen this issue.
Code change:
<ins> { stdenv, fetchurl, bison, m4 }: stdenv.mkDerivation { name = "flex-2.5.35"; src = fetchurl { url = mirror://sourceforge/flex/flex-2.5.35.tar.bz2; sha256 = "0ysff249mwhq0053bw3hxh58djc0gy7vjan2z1krrf9n5d5vvv0b"; }; buildInputs = [ bison ]; propagatedNativeBuildInputs = [ m4 ]; crossAttrs = { preConfigure = '' export ac_cv_func_malloc_0_nonnull=yes export ac_cv_func_realloc_0_nonnull=yes ''; }; meta = { homepage = http://flex.sourceforge.net/; description = "A fast lexical analyser generator"; }; } </ins>

Related discussion:
text: grub fails with nixos-rebuild switch -I nixpkgs=/home/lethal/nixpkgs
The issue title here is highly uninformative, which is why I didn't find this when checking for duplicates. :P
Code change:
{ <ins> # Note: do not use Hydra as a source URL. Ask a member of the # infrastructure team to mirror the job. </ins> busybox = import <nix/fetchurl.nix> { <del> url = https://hydra.nixos.org/build/112609441/download/2/busybox; sha256 = "e6f6aecb675e924a96516f4379445dd2c0ba8b9c438fbfbaa2dc14ccce2802e0"; </del> <ins> # from job: https://hydra.nixos.org/job/nixpkgs/cross-trunk/bootstrapTools.armv6l.dist/latest # from build: https://hydra.nixos.org/build/114202834 url = "http://tarballs.nixos.org/stdenv-linux/armv6l/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/busybox"; # note: the following hash is different than the above hash, due to executable = true sha256 = "1q02537cq56wlaxbz3s3kj5vmh6jbm27jhvga6b4m4jycz5sxxp6"; </ins> executable = true; }; bootstrapTools = import <nix/fetchurl.nix> { <del> url = https://hydra.nixos.org/build/112609441/download/1/bootstrap-tools.tar.xz; sha256 = "7a3f20def1a17ebf0edb5a92c403558429bcc2ac3d931b5e1bd88606cb217778"; </del> <ins> # from job: https://hydra.nixos.org/job/nixpkgs/cross-trunk/bootstrapTools.armv6l.dist/latest # from build: https://hydra.nixos.org/build/114202834 url = "http://tarballs.nixos.org/stdenv-linux/armv6l/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/bootstrap-tools.tar.xz"; sha256 = "0810fe74f8cd09831f177d075bd451a66b71278d3cc8db55b07c5e38ef3fbf3f"; </ins> }; }

Related discussion:
text: Describe the bug doesn't work, either on or . It works on and I have a bisect running at the moment (on some slow hardware, so the results might take some time). It fails with this log: To Reproduce Metadata Maintainer information:
The first bad commit could be any of: jfsutils: fix build with glibc=2.28 ppp: fix build with glibc=2.28 oathToolkit: fix build with glibc=2.28 postfix: fix build w/glibc 2.30 libffi: only run tests on musl targets stdenv: rebuild aarch64 bootstrap files with gcc8 expect: remove hack for aarch64 build expect: fix aarch64 build seasocks: fix build w/glibc-2.30 bzip2: fix aarch64 build xnbd: fix build w/glibc-2.30 glibc: remove outdated patches rr: 5.2.0 -5.3.0, fix build w/glibc-2.30 diod: fix build w/glibc-2.30 libunistring: disable tests distrho: fix build w/glibc-2.30 glibc: depend on libidn2 (and libunistring, transitively) stdenv bootstrap: disable dejagnu tests gcal: fix build w/glibc-2.30 sharutils: fix build with glibc=2.28 drbd: fix build w/glibc-2.30 gnum4: fix build with glibc=2.28 xen48: fix build w/glibc-2.30 gnulib: - mono: fix build w/glibc-2.30 glibc: 2.27 -2.30 foundationdb61: fix build w/glibc-2.30 spaceFM: fix build w/glibc-2.30 cpython: fetch darwin- to nixpkgs xen48-{light,
Code change:
{ <ins> # Note: do not use Hydra as a source URL. Ask a member of the # infrastructure team to mirror the job. </ins> busybox = import <nix/fetchurl.nix> { <del> url = https://hydra.nixos.org/build/112609441/download/2/busybox; sha256 = "e6f6aecb675e924a96516f4379445dd2c0ba8b9c438fbfbaa2dc14ccce2802e0"; </del> <ins> # from job: https://hydra.nixos.org/job/nixpkgs/cross-trunk/bootstrapTools.armv6l.dist/latest # from build: https://hydra.nixos.org/build/114202834 url = "http://tarballs.nixos.org/stdenv-linux/armv6l/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/busybox"; # note: the following hash is different than the above hash, due to executable = true sha256 = "1q02537cq56wlaxbz3s3kj5vmh6jbm27jhvga6b4m4jycz5sxxp6"; </ins> executable = true; }; bootstrapTools = import <nix/fetchurl.nix> { <del> url = https://hydra.nixos.org/build/112609441/download/1/bootstrap-tools.tar.xz; sha256 = "7a3f20def1a17ebf0edb5a92c403558429bcc2ac3d931b5e1bd88606cb217778"; </del> <ins> # from job: https://hydra.nixos.org/job/nixpkgs/cross-trunk/bootstrapTools.armv6l.dist/latest # from build: https://hydra.nixos.org/build/114202834 url = "http://tarballs.nixos.org/stdenv-linux/armv6l/0eb0ddc4dbe3cd5415c6b6e657538eb809fc3778/bootstrap-tools.tar.xz"; sha256 = "0810fe74f8cd09831f177d075bd451a66b71278d3cc8db55b07c5e38ef3fbf3f"; </ins> }; }

Related discussion:
text: slim}: fix build bootstrap-files: bump WIP Merge branch 'staging' into glibc230 Ignoring 'fix build with glibc' commits libffi: only run tests on musl targets stdenv: rebuild aarch64 bootstrap files with gcc8 expect: remove hack for aarch64 build expect: fix aarch64 build bzip2: fix aarch64 build glibc: remove outdated patches libunistring: disable tests glibc: depend on libidn2 (and libunistring, transitively) stdenv bootstrap: disable dejagnu tests gnulib: - glibc: 2.27 -2.30 cpython: fetch darwin- to nixpkgs xen48-{light,slim}: fix build bootstrap-files: bump WIP Merge branch 'staging' into glibc230
stdenv bootstrapping of 32-bit ARMs is (hopefully) being fixed right now:
Thanks for the hard work
Code change:
}) ]; patchFlags = [ "-p3" ]; <del> } { inherit stdenv lib fetchurl fixDarwinDylibNames nativeBuildRoot; } </del> <ins> } { inherit stdenv lib fetchurl fixDarwinDylibNames nativeBuildRoot buildRootOnly; } </ins>

Related discussion:
text: Describe the bug I need to list the out paths of cross compiled packages beforehand which causes an eval error. To Reproduce Steps to reproduce the behavior: Expected behavior List all out paths like `. Additional context I need this feature for nixpkgs-review when cross compiling. 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(user): nixpkgs: Maintainer information:
I think its because of the lack of splicing for perl-packages. Note however, that when that is fixed, other package sets will fail with the same issue. cc
Probably multiple issues. Have seen that problem with building xwayland for aarch64 too. Removing makeWrapper helps but probably breaks it :(. But the deps don't cross-build anyway so never got that far for now. Was thinking about opening an issue but got caught up trying to find the issue -- to no avail. Not currently at my machine, might post it later.
I marked this as stale due to inactivity. &rarr;
still important to me
Fix in
Code change:
system.nssModules = optional (cfg.nssmdns4 || cfg.nssmdns6) pkgs.nssmdns; system.nssDatabases.hosts = let <del> mdnsMinimal = if (cfg.nssmdns4 && cfg.nssmdns6) then "mdns_minimal" </del> <ins> mdns = if (cfg.nssmdns4 && cfg.nssmdns6) then "mdns" </ins> else if (!cfg.nssmdns4 && cfg.nssmdns6) then <del> "mdns6_minimal" </del> <ins> "mdns6" </ins> else if (cfg.nssmdns4 && !cfg.nssmdns6) then <del> "mdns4_minimal" </del> <ins> "mdns4" </ins> else ""; in optionals (cfg.nssmdns4 || cfg.nssmdns6) (mkMerge [ <del> (mkBefore [ "${mdnsMinimal} [NOTFOUND=return]" ]) # before resolve (mkAfter [ "mdns" ]) # after dns </del> <ins> (mkBefore [ "${mdns}_minimal [NOTFOUND=return]" ]) # before resolve (mkAfter [ "${mdns}" ]) # after dns </ins> ]); environment.systemPackages = [ cfg.package ];

Related discussion:
text: Describe the bug When printing to Brother MFC-L2700DW printer (with created from a similar model in nixpkgs), CUPS often (but not always) complains about "Impossible to connect to Name or service not known" even though I followed the and enabled . To Reproduce Steps to reproduce the behavior: Brother MFC-L2700DW printer. NixOS as follows: (full configuration ) something to http://localhost:631/printers/BrotherMFC-L2700DWseries and see the "Impossible to connect to Name or service not known" message. Expected behavior The job is sent to the printer and printed. Additional context When the printer cannot be connected, running usually helps and the stuck job gets to the printer. After my investigation, I think that the cause is long delay in mDNS name resolution. By default NixOS uses NSS module, which tries to resolve both IPv4 and IPv6 addresses sequentially. It seems to start with IPv6, which does not resolve to a valid address so after 5s timeout the resolution continues with IPv4. So the address of the printer is returned after slightly more that 5 seconds (can be verified with ), which seems to be too long for CUPS so it gives up and tries again later and the same repeats, because nscd in NixOS does not cache the results. My current solution to the problem is to switch from NSS to with the following in my : I've also tried but it didn't help. The question is whether to make it easier for others. Possible things that come to my mind: Document this at Wiki Extend to provide e.g. option. Enable caching in nscd Something else? 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. system: host os: multi-user?: sandbox: version: channels(root): channels(wsh): nixpkgs: Maintainer information:
Confirm, I have the same problem (with Xerox WorkCentre). And your workaround fixed it for me too. Thanks!
I wanted to link this issue from the and found that there a comment suggesting that he might have the same problem. does the above workaround make your setup work without restarting cups after booting?
Code change:
system.nssModules = optional (cfg.nssmdns4 || cfg.nssmdns6) pkgs.nssmdns; system.nssDatabases.hosts = let <del> mdnsMinimal = if (cfg.nssmdns4 && cfg.nssmdns6) then "mdns_minimal" </del> <ins> mdns = if (cfg.nssmdns4 && cfg.nssmdns6) then "mdns" </ins> else if (!cfg.nssmdns4 && cfg.nssmdns6) then <del> "mdns6_minimal" </del> <ins> "mdns6" </ins> else if (cfg.nssmdns4 && !cfg.nssmdns6) then <del> "mdns4_minimal" </del> <ins> "mdns4" </ins> else ""; in optionals (cfg.nssmdns4 || cfg.nssmdns6) (mkMerge [ <del> (mkBefore [ "${mdnsMinimal} [NOTFOUND=return]" ]) # before resolve (mkAfter [ "mdns" ]) # after dns </del> <ins> (mkBefore [ "${mdns}_minimal [NOTFOUND=return]" ]) # before resolve (mkAfter [ "${mdns}" ]) # after dns </ins> ]); environment.systemPackages = [ cfg.package ];

Related discussion:
text: If yes, I'd update your comment, because it's not accurate. The is not needed, because it is pulled in by mentioned on the previous line.
Hi, I'm back and I'll test your workaround soon. About , I thought it should have been pulled, but it wasn't at the time. I vaguely remember triple checking and it wasn't there.
Sorry, I can't test it again. My printer is busted.
OK, thanks for letting me know :-)
Ok, my printer has sudently revived and this solves the issue for me as well.
I marked this as stale due to inactivity. &rarr;
Confirming that the issue still exists with current nixos-unstable.
Out of curiosity, is this workaround supposed to break or use outdated softwares? If not, would it make sense to directly apply your workaround by default?
This workaround makes mDNS working only for IPv4. If you are on a IPv6-only network, mDNS won't work for you. On mixed IPv4/IPv6 network, you might not see some devices. That's definitely not what some people want :-) Btw, may be relevant to this problem. I've not read all the comments there, but the keywords seem similar to what I remember when debugging this issue. I think the solution might be to increase or decrease some timeout somewhere, but I'm not sure where. More debugging/analysis is needed.
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Same happening here with a Canon MF643C. I found a workaround, but yours seems better. Mine was to manually add the expected on '/etc/hosts' file. This only works if your printer has a fixed ip (like 10.1.2.3). networking.extraHosts = '' 10.1.2.3 '';
I also hit this issue. Given that (I assume) most people are running ipv4, can we not try the v4 exclusive module first, and still fallback to the one that also works with v6, so that it "just works" for this rather common use case? Given, that will slowdown v6 name resolution, but I guess we could also add a big warning in the option.
Looks like this is closed by
Unfortunately, that commit is not sufficient for me.
Code change:
system.nssModules = optional (cfg.nssmdns4 || cfg.nssmdns6) pkgs.nssmdns; system.nssDatabases.hosts = let <del> mdnsMinimal = if (cfg.nssmdns4 && cfg.nssmdns6) then "mdns_minimal" </del> <ins> mdns = if (cfg.nssmdns4 && cfg.nssmdns6) then "mdns" </ins> else if (!cfg.nssmdns4 && cfg.nssmdns6) then <del> "mdns6_minimal" </del> <ins> "mdns6" </ins> else if (cfg.nssmdns4 && !cfg.nssmdns6) then <del> "mdns4_minimal" </del> <ins> "mdns4" </ins> else ""; in optionals (cfg.nssmdns4 || cfg.nssmdns6) (mkMerge [ <del> (mkBefore [ "${mdnsMinimal} [NOTFOUND=return]" ]) # before resolve (mkAfter [ "mdns" ]) # after dns </del> <ins> (mkBefore [ "${mdns}_minimal [NOTFOUND=return]" ]) # before resolve (mkAfter [ "${mdns}" ]) # after dns </ins> ]); environment.systemPackages = [ cfg.package ];

Related discussion:
text: Current version of CUPS complains with: "No destination host name supplied by cups-browsed for printer "BrotherMFCL2700DWseriesmDNS", is cups-browsed running?" The referenced commit makes my contain the following line: hosts: mymachines mdns4minimal [NOTFOUND=return] files myhostname dns mdns With it, running returns an IPv6 address: fd76:76f3:2dcb:0:3205:5cff:fecb:4509 From the output of it seems that the command first asks for IPv6 address, so the is somehow ignored and the address is returned by at the end of the line. I can ping and connect that address via so I don't know why CUPS cannot print to it. Anyway, if I disable IPv6 in the printer, returns the IPv4 address, but only after the 5 second timeout, which is too long for CUPS. What I need is also at the end of line. I'll ask at and submit a PR to do that if people do not complain.
Please submit a PR.
Uses a direct printer install. Same sort of problems encountered.
Code change:
fastjar = callPackage ../development/tools/java/fastjar { }; <del> jextract = callPackage ../development/tools/java/jextract { }; </del> httpunit = callPackage ../development/libraries/java/httpunit { }; javaCup = callPackage ../development/libraries/java/cup {

Related discussion:
text: Package name: jextract (jextract-unstable) Current version on the unstable channel: 2023-11-27 Current version on the stable/release channel: n/a As of today the current release build is (see ) It would be nice for the nixpkgs version to be based on JDK 22 -- which contains the final non-preview release of Java Foreign Function & Memory API (aka "Panama") There are significant changes to that users will want before building/launching projects that use Panama. See: I am wiling to contribute but before we can do this we'll need to build with JDK 22 (see Issue )
It would be great if we could update to be based on JDK 22 :+1: , and we should also keep the current JDK 21 package as a new name (perhaps ?) at the same time, as some downstreams still depend on it and JDK 21 is a LTS version.
So should the first step be to rename the existing package? And leave as JDK 21-based (with a warning, maybe) and then do a separate PR to upgrade to JDK 21?
Update: There is a PR for JDK 22:
I can open a PR to update jextract after gets merged. Considering the significant API changes between JDK 21 and 22, and the fact that jextract itself produces very differnt code if you have to use JDK21 (see ) , is there really value in keeping a jextract version compatible with JDK21?
Awesome! I'm going to test on macOS/aarch64 this weekend, so that will help get it merged. wrote: as some downstreams still depend on it and JDK 21 is a LTS version. JDK 21 is LTS, but Panama (Foreign Functions & Memory API) is a "preview feature" which makes it really hard to build anything real with it (i.e. publish JARs for use by other projects. I even had problems with a Gradle multi-module build). I migrated my project to 22 a few weeks ago and am not looking back (which meant I had to stop using Nix as a source for temporarily.) But, I don't see any harm in renaming the existing to and starting a new one. And we certainly don't want to unnecessarily break anyone's dependencies.