jiebi/CodeConvo huggingface dataset:
Code change:
cp "${sweethome3dItem}/share/applications/"* $out/share/applications <del> # MESA_GL_VERSION_OVERRIDE is needed since the update from MESA 19.3.3 to 20.0.2: # without it a "Profiles [GL4bc, GL3bc, GL2, GLES1] not available on device null" # exception is thrown on startup. # https://discourse.nixos.org/t/glx-not-recognised-after-mesa-update/6753 makeWrapper ${jre8}/bin/java $out/bin/$exec  --set MESA_GL_VERSION_OVERRIDE 2.1  </del> <ins> makeWrapper ${jdk}/bin/java $out/bin/$exec  </ins> --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS:${gtk3.out}/share:${gsettings-desktop-schemas}/share:$out/share:$GSETTINGS_SCHEMAS_PATH"  <ins> --prefix LD_LIBRARY_PATH : "${lib.makeLibraryPath [ libGL ]}"  </ins> --add-flags "-Dsun.java2d.opengl=true -jar $out/share/java/${module}-${version}.jar -cp $out/share/java/Furniture.jar:$out/share/java/Textures.jar:$out/share/java/Help.jar -d${toString stdenv.hostPlatform.parsed.cpu.bits}"

Related discussion:
text: For me, was needed (with patch). I also needed . and didn't seem needed (or give noticable changes).
Code change:
extraArgs = [ "--version-regex" "r(.*)" ]; }; <del> nativeBuildInputs = [ cmake pkg-config ]; </del> <ins> nativeBuildInputs = [ cmake pkg-config ] ++ lib.optional buildAudaciousPlugin gtk3; </ins> <del> buildInputs = [ mpg123 ffmpeg libvorbis libao jansson speex ]; </del> <ins> buildInputs = [ mpg123 ffmpeg libvorbis libao jansson speex ] ++ lib.optional buildAudaciousPlugin (audacious.override { audacious-plugins = null; }); preConfigure = '' substituteInPlace cmake/dependencies/audacious.cmake  --replace "pkg_get_variable(AUDACIOUS_PLUGIN_DIR audacious plugin_dir)" "set(AUDACIOUS_PLUGIN_DIR "$out/lib/audacious")" ''; </ins> cmakeFlags = [ <del> # There's no nice way to build the audacious plugin without a circular dependency "-DBUILD_AUDACIOUS=OFF" </del> # It always tries to download it, no option to use the system one "-DUSE_CELT=OFF" <del> ]; </del> <ins> ] ++ lib.optional (! buildAudaciousPlugin) "-DBUILD_AUDACIOUS=OFF"; </ins> meta = with lib; { description = "A library for playback of various streamed audio formats used in video games";

Related discussion:
text: The audacious package imports audacious-plugins to build most of the common plugins and then link them into the audacious lib path. However, this makes it hard to add more audacious plugins, like vgmstream. The vgmstream package currently has its , because importing the audacious package causes an infinite recursion error. Steps to reproduce the behavior: vgmstream to audacious-plugins buildInputs audacious to vgmstream's buildInputs and comment out the disable configure flag -shell -p audacious-plugins I expected that adding vgmstream to audacious-plugins would enable the plugin. Instead, the build crashes with an infinite recursion. How is it currently working for audacious to import audacious-plugins and audacious-plugins to import audacious? Can this same magic be extended to other plugins? This about how fcitx is packaged shows that fcitx-addons imports fcitx with no reverse import, should the audacious package be refactored to be similar? Should the audacious package gain an extra parameter to take extra plugin derivations, which can be created outside of the audacious-plugins derivation? Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Instead of adding , did you try to add instead? is without as input, and it is used to break the loop.
Thank you for the quick response! That would be elegant, but I don't see any result in my grep of nixpkgs or in the .
Sorry, it is here: Basically you need to do and this should do the trick. Considering that we are going to use this in more than one place it probably makes sense to introduce it as a , but the result is the same regardless.
Oh that's a neat trick! I'll try that approach out next. Thank you so much! I tried out the extra-plugins approach here, seems to work but is not ergonomic:
I , and it's a lot easier to use as a user! If it looks good as an approach, please provide some review feedback and I'll squash it down for a PR :)
Shall I send a PR for a final review?
Code change:
<ins> { lib , stdenv , rustPlatform , fetchFromGitHub }: rustPlatform.buildRustPackage rec { pname = "evebox"; version = "0.17.2"; src = fetchFromGitHub { owner = "jasonish"; repo = "evebox"; rev = version; hash = "sha256-djL5cdudJNPAWLMQPS2Dkcc9H/gouOuu8evcBDdY9wA="; }; cargoLock = { lockFile = ./Cargo.lock; outputHashes = { "libsqlite3-sys-0.25.2" = "sha256-+c7ong6ca4WkEHl7ynCNn3WW68jF3pSYbllRsaNFGLc="; "suricatax-rule-parser-0.1.0" = "sha256-upWgOKSAuj0pYGTeYKANzwutoF/m4AQ7MkzGYXmPbEo="; }; }; meta = { description = "Web Based Event Viewer (GUI) for Suricata EVE Events in Elastic Search"; homepage = "https://evebox.org/"; changelog = "https://github.com/jasonish/evebox/releases/tag/${src.rev}"; license = lib.licenses.mit; maintainers = with lib.maintainers; [ felbinger ]; broken = stdenv.isDarwin; }; } </ins>

Related discussion:
text: Project description EveBox is a Suricata alert and event management tool for the Suricata IDS/NSM Engine. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ... Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
<del> diff --git a/bin/nexus b/bin/nexus index e7ed3fb..8db766b 100755 --- a/bin/nexus +++ b/bin/nexus @@ -440,7 +440,8 @@ add_class_path "$app_home/lib/boot/org.apache.karaf.diagnostic.boot-4.0.9.jar" add_class_path "$app_home/lib/boot/org.apache.karaf.jaas.boot-4.0.9.jar" vmoptions_val="" -read_vmoptions "$prg_dir/$progname.vmoptions" +VM_OPTS=${VM_OPTS_FILE:-"$prg_dir/$progname.vmoptions"} +read_vmoptions "$VM_OPTS" INSTALL4J_ADD_VM_PARAMS="$INSTALL4J_ADD_VM_PARAMS $vmoptions_val" </del>

Related discussion:
text: Package name: nexus Latest released version: 3.69.0 <!-- Search your package here: --- Current version on the unstable channel: 3.68.1-02 Current version on the stable/release channel: 3.68.1-02 <!-- 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]:
Code change:
(mkChangedOptionModule [ "security" "initialRootPassword" ] [ "users" "users" "root" "initialHashedPassword" ] <del> (cfg: if cfg.security.initialHashedPassword == "!" </del> <ins> (cfg: if cfg.security.initialRootPassword == "!" </ins> then null <del> else cfg.security.initialHashedPassword)) </del> <ins> else cfg.security.initialRootPassword)) </ins> ]; ###### interface

Related discussion:
text: Describe the bug A clear and concise description of what the bug is. I am using nixops to manage a number of machines, some of which use nixpkgs-unstable. When deploying a machine with nixpkgs-unstable, I started getting errors stating . These are likely linked to a change in the last week or so, as I've been able to deploy the same machine perfectly fine last week. When run with , I get: After getting this error the first time, I initialHashedPassword to all 2 of my users, as well as root, as follows: This fails with the same error. Deploying with nixpkgs 20.03 works fine. The error seems to originate from , specifically: I also tried adding , which naturally fails as that attribute doesn't exist. It also fails with the same trace when using instead of To Reproduce Steps to reproduce the behavior: to deploy a machine (maybe nixops is required?) with the latest nixpkgs-unstable Expected behavior The machine should deploy normally, even without , as it used to last week Screenshots N/A Additional context I suspect it might be linked to Notify maintainers - Tagging you as your PR was the last one to touch this area Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(raghav): nixpkgs: I'm using nixops release-1.7 Maintainer information:
Yeah, this really smells like .
Argh, I made a stupid typo. I'll fix this ASAP.
Code change:
in stdenv.mkDerivation rec { pname = "mpv"; <del> version = "0.33.1"; </del> <ins> version = "0.34.0"; </ins> <del> outputs = [ "out" "dev" ]; </del> <ins> outputs = [ "out" "dev" "man" ]; </ins> src = fetchFromGitHub { <del> owner  = "mpv-player"; repo   = "mpv"; rev    = "v${version}"; sha256 = "06rw1f55zcsj78ql8w70j9ljp2qb1pv594xj7q9cmq7i92a7hq45"; </del> <ins> owner = "mpv-player"; repo = "mpv"; rev = "v${version}"; sha256 = "sha256-qa6xZV4aLcHBMa2bIqoKjte4+KWEGGZre4L0u1+eDE8="; </ins> }; <del> patches = [ # To make mpv build with libplacebo 3.104.0: (fetchpatch { # vo_gpu: placebo: update for upstream API changes url = "https://github.com/mpv-player/mpv/commit/7c4465cefb27d4e0d07535d368febdf77b579566.patch"; sha256 = "1yfc6220ak5kc5kf7zklmsa944nr9q0qaa27l507pgrmvcyiyzrx"; }) # TOREMOVE when > 0.33.1 # youtube-dl has been abandonned and is now unusable w/ # youtube.com. Mpv migrated to yt-dlp since the 0.33.1 but did not # cut a new release yet. See # https://github.com/mpv-player/mpv/pull/9209 (fetchpatch { url = "https://github.com/mpv-player/mpv/commit/d1c92bfd79ef81ac804fcc20aee2ed24e8d587aa.patch"; sha256 = "1dwxzng3gsrx0gjljm5jmfcjz3pzdss9z2l0n25rmmb4nbcrcx1f"; }) ]; </del> postPatch = '' patchShebangs ./TOOLS/ ''; <del> passthru = { inherit # The wrapper consults luaEnv and lua.version luaEnv lua # In the wrapper, we want to reference vapoursynth which has the # `python3` passthru attribute (which has the `sitePrefix` # attribute). This way we'll be sure that in the wrapper we'll # use the same python3.sitePrefix used to build vapoursynth. vapoursynthSupport vapoursynth ; }; NIX_LDFLAGS = optionalString x11Support "-lX11 -lXext " + optionalString stdenv.isDarwin "-framework CoreFoundation"; </del> <ins> NIX_LDFLAGS = lib.optionalString x11Support "-lX11 -lXext " + lib.optionalString stdenv.isDarwin "-framework CoreFoundation"; </ins> wafConfigureFlags = [ "--enable-libmpv-shared"

Related discussion:
text: <!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on github to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the the current version of the package --- <!-- 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! --- name: mpv <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.33.1 desired version: 0.34.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Code change:
return _fileSystem.directory(_fileSystem.path.join(_rootOverride.path, 'bin', 'cache')); } else { -      return _fileSystem.directory(_fileSystem.path.join(flutterRoot, 'bin', 'cache')); <del> +      return _fileSystem.directory(_fileSystem.path.join(homeDirPath, '.cache', 'flutter')); </del> <ins> +      return _fileSystem.directory(_fileSystem.path.join(globals.fsUtils.homeDirPath, '.cache', 'flutter')); </ins> } }

Related discussion:
text: When trying to install , the build fails with: To reproduce, use the following and run it with : I think this happens because of the symlink of the , which seems to be resolved while running the build and in that case the symlink target does not exist. /cc btw: could you please also add support for the latest beta / dev / stable releases?
Hey it's fixed in the latest commit. Can you try it ?
Works fine, thank you very much for the fast fix!
Code change:
bitwise = callPackage ../tools/misc/bitwise { }; <ins> blanket = callPackage ../applications/audio/blanket { }; </ins> brakeman = callPackage ../development/tools/analysis/brakeman { }; brewtarget = libsForQt514.callPackage ../applications/misc/brewtarget { } ;

Related discussion:
text: Project description ! Metadata homepage URL: source URL: license: gpl3 platforms: linux
FTR: This requires an update of .
I marked this as stale due to inactivity. &rarr;
Code change:
inherit (pkgs) xmlsec; }; <ins> pysatochip = callPackage ../development/python-modules/pysatochip { }; </ins> pysc2 = callPackage ../development/python-modules/pysc2 { }; pyscard = callPackage ../development/python-modules/pyscard {

Related discussion:
text: Describe the bug failed to build on master. To Reproduce Steps to reproduce the behavior: nixpkgs master Expected behavior It builds. 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(oxa): nixpkgs: Maintainer information:
Code change:
enableParallelBuilding = true; postPatch = '' <ins> substituteInPlace contrib/smime_keys  --replace /usr/bin/openssl ${openssl}/bin/openssl </ins> for f in doc/*.{xml,xsl}*  ; do substituteInPlace $f  --replace http://docbook.sourceforge.net/release/xsl/current     ${docbook_xsl}/share/xml/docbook-xsl 

Related discussion:
text: Neomutt's bundled tool is unable to find . We should probably replace that string in the perl script. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs:
Code change:
}; url_preview_ip_range_blacklist = mkOption { type = types.listOf types.str; <del> default = []; </del> <ins> default = [ "127.0.0.0/8" "10.0.0.0/8" "172.16.0.0/12" "192.168.0.0/16" "100.64.0.0/10" "169.254.0.0/16" ]; </ins> description = '' List of IP address CIDR ranges that the URL preview spider is denied from accessing.

Related discussion:
text: default value causes previews to fail. the usual homeserver config Do not configure (so that the default value is used) Post URL into a preview enabled room Find similar error in synapse log: The option defaults to . Were those values intended as default for the option? Excerpt from a working configuration: /cc (as you discussed the security implications in )
Seems like a good bet.
thanks for fixing this, I was just wondering about this earlier today:
Code change:
# If multiple remote sources are enabled, nuget will try them all # concurrently and use the one that responds first. We always use the # first source that has the package. <del> echo "$package $version is available on $url, but was downloaded from ${base_addresses[$used_source]}$package/$version/$package.$version.nupkg" 1>&2 </del> <ins> echo "$package $version is available at $url, but was restored from $used_source" 1>&2 </ins> found=true break else

Related discussion:
text: I'm getting an error /nix/store/jx2hdq8n3fdj0bm58qxgy0psyyl0vd05-nuget-to-nix/bin/nuget-to-nix: line 56: baseaddresses[$usedsource]: unbound variable when trying to generate a lockfile for . Steps to reproduce the behavior: this simple file: to generate the script the error Be able to generate the lockfile. If applicable, add screenshots to help explain your problem. Add any other context about the problem here. I guess was the one to introduce the variable there.
could you give a try?
The problem seems to be that there's a repo in the sdk at , containing only . This is somehow referenced implicitly. I'm not sure if we should do anything more to handle this situation, but the message fix should do for now.
Code change:
, fetchpatch , python3Packages , asciidoc <del> , makeWrapper </del> <ins> , wrapGAppsNoGuiHook </ins> , iw }:

Related discussion:
text: Steps to reproduce the behavior: to NixOS config Successfully start. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
<del> { lib, stdenv, fetchFromGitHub } : </del> <ins> { lib , stdenv , fetchFromGitHub , netpbm }: </ins> stdenv.mkDerivation rec { pname = "fbcat";

Related discussion:
text: Steps to reproduce the behavior: working program Add any other context about the problem here. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
Code change:
<ins> --- a/llm/llama.cpp/examples/server/CMakeLists.txt +++ b/llm/llama.cpp/examples/server/CMakeLists.txt @@ -11,3 +11,4 @@ TARGET_LINK_LIBRARIES(${TARGET} PRIVATE ws2_32) endif() target_compile_features(${TARGET} PRIVATE cxx_std_11) +include (../../../ext_server/CMakeLists.txt) # ollama </ins>

Related discussion:
text: Package name: ollama Latest released version: 0.1.20 <!-- Search your package here: --- Current version on the unstable channel: 0.1.17 Current version on the stable/release channel: 0.1.7 <!-- 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 Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
20 was released.[^1] :tada: Had a quick look into the source changes. Seems that patching is required because of the integration of ROCm. [^1]:
I modified the title :-)
21 is going to be released very soon.
I opened
update: 0.1.22 is the latest version.
Seems update can be problematic. I've tried manually download and executing new ollama and encountered a lot of issues connected with ROCM libraries. After adding I've got it to state where it crushes: But before adding it seems also miss new version of because it was asking for but current unstable version have CPU works fine without mentioned ROCM packages.
This appears to have been resolved by . Reopen if it's not.
Code change:
print("skipping systemd-boot update to %s because of known regression" % available_version) else: print("updating systemd-boot from %s to %s" % (installed_version, available_version)) <del> subprocess.check_call(["@systemd@/bin/bootctl", "--esp-path=@efiSysMountPoint@", "update"]) </del> <ins> subprocess.check_call(["@systemd@/bin/bootctl", "--esp-path=@efiSysMountPoint@"] + bootctl_flags + ["update"]) </ins> mkdir_p("@efiSysMountPoint@/efi/nixos") mkdir_p("@efiSysMountPoint@/loader/entries")

Related discussion:
text: During systemd-boot update step attempts to touch EFI variables, even when is set to . Steps to reproduce the behavior: NixOS 21.05 with systemd-boot and to NixOS 21.11 () switch fails with: An error is just an indication of update trying to touch EFI variables. (I have EFI vars touching disabled on that system because of some unrelated firmware breakage) Manually running properly finishes, further switches work fine. systemd-boot update should not touch EFI variables during upgrade. <!-- 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. Maintainer information:
I had a similar issue which I fixed by running "sudo nixos-rebuild --install-bootloader switch"
The fix for this got reverted in
Code change:
moveToOutput bin/isc-config.sh $dev moveToOutput bin/host $host <del> ln -sf $host/bin/host $bin/bin </del> moveToOutput bin/dig $dnsutils moveToOutput bin/nslookup $dnsutils moveToOutput bin/nsupdate $dnsutils <del> ln -sf $dnsutils/bin/{dig,nslookup,nsupdate} $bin/bin ln -sf $host/bin/host $dnsutils/bin </del> for f in "$lib/lib/"*.la "$dev/bin/"{isc-config.sh,bind*-config}; do sed -i "$f" -e 's|-L${openssl.dev}|-L${openssl.out}|g'

Related discussion:
text: The symlinking between the multiple outputs of seems to prevent it from installing. I was looking to install it to have the dig command available. - System: 17.03pre94050. (Gorilla) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: "17.03pre94050."
11.4 still doesn't contain :-( How could we have that as default in 16.09? I consider it quite an important feature for + multiple outputs. would you be against porting that PR to 1.11.5 and making that default in 16.09 and master?
+1 for a 1.11.5 Nix release in general :)
Since this seems to be an issue for multiple packages, I am raising the severity on here.
Looks like the same kind of issue as So +1 for Nix 1.11.5 on NixOS 16.09, if that's what it takes to fix this.
ping again about nix-1.11.5 (my comment above).
Code change:
librarian-puppet-go = callPackage ../development/tools/librarian-puppet-go { }; <ins> libgcc = stdenv.cc.cc.libgcc or null; </ins> # This is for e.g. LLVM libraries on linux. gccForLibs = if stdenv.targetPlatform == stdenv.hostPlatform && targetPackages.stdenv.cc.isGNU

Related discussion:
text: On or cross-compiled from , breaks: From : You can either run this on another architecture using . or should not crash: This was responsible for failing to replicate datasets to my ARM NAS. The issue does not_ occur for natively compiled builds. It appears to be a cross-compilation issue only.
It is a bug in / derivations. In non-cross cases it gets copied from used to bid into output: But in cross-case used to build does not yet provide as it needs bits of for it (and the library path is slightly incorrect). One of possible workarounds is to try to add to to get it pulled via from expected location.
We don't do the copying to glibc anymore, but this error still occurs as described on current nixpkgs master.
Yup. cross-compilation never propagated to in any form (and does not today).
Could you please try this PR? It should fix the problem.
With that PR, I'm seeing this on both (a Raspberry Pi CM4) and with QEMU on : Log from aarch64 machine: Log from machine with QEMU:
Well it's finding now, so there's clearly some other problem with addition to that. When I run it with I even get line numbers from inside : That line () is the last line in the following snippet of code: ... so is deliberately ing here due to . Grepping through the docs turns up: This is happening because uses . Once you do that, glibc needs to unwind the stack frame of any thread that calls . And unwinders are a giant headache. I'm afraid that's all I've got here. I've removed the closed-by from since it was only part of the problem here.
Ah, I think I know what it is. We can compile a without , but it won't have an unwinder. We need to pass the glibc headers to the build in order to get one of those.
would you please try ? I believe it fixes one of the two problems which caused this issue, and it includes which fixes the other one. It works for me: BTW, this issue (cross-compile , then run it under qemu) is a really valuable test case. We really ought to add it to so Hydra will catch any regressions automatically.
Code change:
librarian-puppet-go = callPackage ../development/tools/librarian-puppet-go { }; <ins> libgcc = stdenv.cc.cc.libgcc or null; </ins> # This is for e.g. LLVM libraries on linux. gccForLibs = if stdenv.targetPlatform == stdenv.hostPlatform && targetPackages.stdenv.cc.isGNU

Related discussion:
text: Especially since the failure mode gives the user no error message to help them troubleshoot the problem! is a great candidate for this since it's one of those very rare non-C++ programs that uses advanced stack-unwinding features from pthreads.
Confirming fixes the issue. Tested with both and on real hardware and with QEMU on x86_64.
~I think this is fixed, and more cleanly,~ by Edit: it is not. :frowning_face: I will keep trying. Test is in Currently building.
Added this to , but commented out since it is not fixed yet.