jiebi/CodeConvo huggingface dataset:
Code change:
dotnet-sdk_7 = dotnetCorePackages.sdk_7_0; dotnet-runtime_3 = dotnetCorePackages.runtime_3_1; <del> dotnet-runtime_5 = dotnetCorePackages.runtime_5_0; </del> dotnet-runtime_6 = dotnetCorePackages.runtime_6_0; dotnet-runtime_7 = dotnetCorePackages.runtime_7_0; dotnet-aspnetcore_3 = dotnetCorePackages.aspnetcore_3_1; <del> dotnet-aspnetcore_5 = dotnetCorePackages.aspnetcore_5_0; </del> dotnet-aspnetcore_6 = dotnetCorePackages.aspnetcore_6_0; dotnet-aspnetcore_7 = dotnetCorePackages.aspnetcore_7_0;

Related discussion:
text: Since May 10, .NET 5.0 is EOL (End Of Life), and should not be used. Should it be marked as EOF similar to dotnet 2.2 and 3.0? See All packages using dotnet 5.0 should be updated to use a newer, supported version. These packages still need updating: [x] - [x] - [x] - [x] pkgs/development/tools/build- - [x] -
There is at least one package, which currently uses dotnet 5 sdk - . So we will need to update it beforehand. Btw, I'm not sure if we have any policy regarding packages removal, for nixpkgs in general or specifically for it's dotnet part. , what do you think?
The package is also using .NET 5: . But this is because I made the PR upstream updating it from .NET 4 to 5. I suspect that the transition to 6 will be similarly easy.
I think we should just mark it as depricated, as many projects do still use it upstream. Dotnet version 3 is also still commonly used, so I dont expect it would be realistic to remove version 5 any time soon. also uses dotnet 5 by default, I'll go ahead and switch that over now. See . That doesnt mark dotnet 5 as deprecated or change anything from a SDK perspective, just some preperation work.
See as well, it adds a warning whenever dotnet version 5 is used. Not using a throw for now since a few packages depend on it and I dont have the time to clean that all up at the moment.
Can you provide a list of packages that need updating?
Based on a quick grep: pkgs/development/tools/build-
I believe that after all the above PRs are merged, we should be able to safely remove .NET 5 from nixpkgs :)
Code change:
environment.etc = mapAttrsToList (n: v: makePAMService v) config.security.pam.services; <del> systemd.tmpfiles.rules = optionals (any (s: s.updateWtmp) (attrValues config.security.pam.services)) [ "f /var/log/wtmp" "f /var/log/lastlog" ]; </del> security.pam.services = { other.text = ''

Related discussion:
text: Describe the bug /dev/fuse isn't user read/writable To Reproduce Expected behavior Additional context I've been testing with and : Metadata Please run and paste the result. system: host os: multi-user?: sandbox: version: channels(root): nixpkgs: Maintainer information:
After further testing, I found that reverting fixes the issue. I'm guessing that this new file needs to be installed somewhere. CCing maintainers of systemd:
There are even more tmpfiles configs that we're not using. I'll check what applies to us and prepare a PR.
It would be cool if there was a test for the permissions.
I have the same issue with /dev/fuse for can't mount remote sshfs as user only as root la /dev/fuse 10.6s crw------- 1 root root 10, 229 Sep 23 14:36 /dev/fuse ~sshfs user ~/sshfs/ fuse: failed to open /dev/fuse: Permission denied Any fix we can expect soon?
Seems permissions is associated with systemd /etc/static/systemd/system/kmod-static-nodes.service
apparently that broke permissions for me, which are needed for
Strangely, on my 19.09 system does have 666 permission, despite containing a line .
I think the permission is automatically set to 666 by udev rules when the fuse module is loaded.
In my system on 19.09pre channel I have this issue manifesting in kbfsmount failing with a permission error. crw------- 1 root root 10, 229 Sep 23 21:48 /dev/fuse
Code change:
export PERLPATH ''; <del> configureFlags = [ "--sysconfdir=/etc" "--localstatedir=/var" "--with-openldap" "--with-db" "--with-db-inc=${db.dev}/include" "--with-db-lib=${db.out}/lib" "--with-sasl=${cyrus_sasl.dev}" "--with-netsnmp=yes" "--with-netsnmp-inc=${lib.getDev net-snmp}/include" "--with-netsnmp-lib=${lib.getLib net-snmp}/lib" ]; </del> <ins> configureFlags = let mkEnable = cond: name: if cond then "--enable-${name}" else "--disable-${name}"; in [ "--enable-cmocka" "--localstatedir=/var" "--sysconfdir=/etc" "--with-db-inc=${db.dev}/include" "--with-db-lib=${db.out}/lib" "--with-db=yes" "--with-netsnmp-inc=${lib.getDev net-snmp}/include" "--with-netsnmp-lib=${lib.getLib net-snmp}/lib" "--with-netsnmp=yes" "--with-openldap" "${mkEnable enableCockpit "cockpit"}" "${mkEnable enablePamPassthru "pam-passthru"}" "${mkEnable enableDna "dna"}" "${mkEnable enableLdapi "ldapi"}" "${mkEnable enableAutobind "autobind"}" "${mkEnable enableAutoDnSuffix "auto-dn-suffix"}" "${mkEnable enableBitwise "bitwise"}" "${mkEnable enableAcctPolicy "acctpolicy"}" "${mkEnable enablePosixWinsync "posix-winsync"}" ]; </ins> enableParallelBuilding = true; <ins> doCheck = true; </ins> installFlags = [ "sysconfdir=${placeholder "out"}/etc" "localstatedir=${placeholder "TMPDIR"}"

Related discussion:
text: Project description Upgrade 389-ds-base Apparenty its new 1.4.4.4 release is a bit different. Metadata homepage URL: source URL:
I marked this as stale due to inactivity. &rarr;
Code change:
<del> { stdenv, fetchurl, autoconf, vala_0_32, pkgconfig, glib, gobjectIntrospection, gnome3 }: </del> <ins> { stdenv, fetchurl, autoconf, vala, pkgconfig, glib, gobjectIntrospection, gnome3 }: </ins> let <del> ver_maj = "0.18"; </del> <ins> ver_maj = "0.20"; </ins> ver_min = "0"; in stdenv.mkDerivation rec {

Related discussion:
text: Geary and are . I suppose updating might remove its dependency on the insecure . (I think i remember having seen somewhere in an issue tracker that this dependency was removed in Geary source code, but i cannot find now where i saw it.)
By the way, I do not really understand these GTK and WebKitGTK issues and versions, but, just for reference, there is an open issue about previous versions of Geary using GTK2 instead of GTK3: .
In Geary 0.12 there are some fresh bugs (for example, ). It looks like version 0.12.1 is in the beginning of November.
Running shows gtk2 as a transitive dependency from webkitgtk (which depends on both GTK 2 and GTK 3) and gnome-themes-standard. I do not think the latter is necessary for GTK 3 applications since Adwaita is built into GTK 3.
Code change:
--offline ) <del> local -r tmpDir="$(mktemp -d yarnInstallHook.XXXXXX)" </del> <ins> local -r tmpDir="$(mktemp -d)" </ins> # yarn pack does not work at all with bundleDependencies. # Since we are imediately unpacking, we can just remove them from package.json

Related discussion:
text: is currently using this command creates the temporary directory inside the current working directory instead of in . This can cause the generated directory to be included in the final package, as I'm assuming accidentally picked it up. I encountered this while working on and The temporary directory is not included in the output use use (output is of the format ) note: this isn't really used across nixpkgs use something else <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
{ lib, stdenv, fetchFromGitHub, cmake, makeWrapper, perlPackages, <del> libminc, EBTKS }: </del> <ins> libminc, ebtks }: </ins> stdenv.mkDerivation rec { pname = "N3";

Related discussion:
text: For x8664-darwin, aarch64-darwin: build .#EBTKS x8664-darwin: aarch64-darwin:
Code change:
propagatedBuildInputs = [ ncurses zlib ]; <ins> patches = [ # Force a test to evaluate the saved benchmark for a CPU for which LLVM has # an execution model. See NixOS/nixpkgs#119673. ../../exegesis-force-bdver2.patch ]; </ins> postPatch = optionalString stdenv.isDarwin '' substituteInPlace cmake/modules/AddLLVM.cmake  --replace 'set(_install_name_dir INSTALL_NAME_DIR "@rpath")' "set(_install_name_dir)" 

Related discussion:
text: Describe the bug wendy, one of the big-parallel build hosts used by , cannot successfully build This blocks advancing nixos-unstable. To Reproduce Steps to reproduce the behavior: wendy to build Observe :( or, more realistically: the attached CMOV16rm-, and run (a reduced commandline that produces the same assertion failure is ) Expected behavior A clear and concise description of what you expected to happen. Additional context The assertion that's tripped by this YAML file is: 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:
is the CMOV16rm- (can't upload it here because it's not a supported GitHub filetype, apparently). To be more precise, the test that is failing is this one:
This has primarily become apparent because the configuration was changed in NixOS/nixos-org-configurations to make wendy only build big-parallel jobs. Since llvm is big-parallel, this means that wendy will now usually get selected for building llvm, since the load is otherwise pretty low. Previous successful builds of have been using one of the packet builders instead, which are using a newer CPU for which LLVM has a scheduling machine model.
FWIW, this probably affects other LLVM versions as well, but they have current versions in the cache. If wendy rebuilds the other packages (e.g. stdenv bump or something), they'll likely start failing as well.
If you spin up a VM using the CPU profile that at least virt-manager calls "OpteronG1", then you can reproduce this using the LLVM tests. That's not quite the same as the CPU reported on wendy (OpteronG1: k8-sse3; wendy: amdfam10), but it exhibits the same problem.
I don't know why, but wendy as disabled now.
it's probably late for you (I hope I didn't confuse names), but you this issue some time ago.
uh, same full name but this GitHub name is in .
Filed upstream for this.
Code change:
# this also disables necessary patches contained in `ollama/llm/patches/` # those patches are applied in `postPatch` ./disable-git.patch <ins> # we provide our own deps at runtime ./skip-rocm-cp.patch </ins> ]; postPatch = ''

Related discussion:
text: Steps to reproduce the behavior: Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hydra can reproduce:
I tracked down the potential source of this failure, and am working on a fix. These builds take 30 minutes for me though, so it's slow going.
Please see for a fix. Testing appreciated.
Thanks for the quick patch. EDIT: My way of installing to profile didn't pull the fix, I'll see if I can figure out a way to do it properly using the pr review package
Builds and runs... seg faults as soon as I load a model, but that's an AMD driver thing (whole WM crashes)... Ship it :laughing:
I did see some segfaults, but was able to restart and get it to load on my 6700xt. “Glad” to know it’s known and common.
Nice! Thanks for this - excited to see it roll into unstable soon. Ollama seems to always have some issue - is there a "working group" that has some focus on this program and nix? Anyway, thanks again!
The problems with crashing aren't nix problems, they're crappy amd driver issues. It doesn't crash if you don't load models close to the max vram available... obviously it shouldn't crash if you do, but amd... so yeah
Code change:
<del> { config, lib, stdenv, fetchFromGitHub, runCommand, ncurses, pkg-config </del> <ins> { config, lib, stdenv, fetchFromGitHub, fetchpatch, ncurses, pkg-config </ins> , libiconv, CoreAudio, AudioUnit, VideoToolbox , alsaSupport ? stdenv.isLinux, alsa-lib ? null

Related discussion:
text: Steps to reproduce the behavior: cmus on current (). Full logs: I haven't updated in a while, so I'm not sure where this failure starts. Nothing has changed in the cmus package; it must be a change in dependencies. system: host os: multi-user?: sandbox: version: channels(root): channels(jamesw): nixpkgs:
cmus started failing somewhere between (good) and (bad). I don't have the hundreds of gigabytes of RAM that would allow me to do a bisection between those, so I'll leave that to someone else.
Manually going through it suggests as a possible culprit. I have no idea what that commit does, though, yet.
the issue is bump of ffmpeg to 6, i am about to push a fix
Code change:
, fetchurl , autoPatchelfHook , dpkg <del> , makeBinaryWrapper </del> <ins> , makeShellWrapper </ins> , wrapGAppsHook3 , alsa-lib , at-spi2-atk

Related discussion:
text: ArmCord's wrapper seems unable to launch under Wayland, always chooses to launch under Steps to reproduce the behavior: sure and are properly set: Armcord: . ... 's on XWayland (as shown by ). I expect it to launch with Wayland instead of XWayland. Custom wrapper: Test case: Log output: <!-- 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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
probably need makeShellWrapper instead of makeBinaryWrapper in the package
Thanks for jumping on a PR will review this evening.
Code change:
<ins> { lib, buildGoModule, fetchFromGitHub }: buildGoModule rec { pname = "devspace"; version = "5.18.4"; src = fetchFromGitHub { owner = "loft-sh"; repo = "devspace"; rev = "v${version}"; sha256 = "0s5117cgxgrxfki5drvg6d22dvrjffa03bi644zdl1p631r599r1"; }; vendorSha256 = null; ldflags = [ "-s" "-w" "-X main.version=${version}" ]; # Check are disable since they requiered a working K8S cluster # TODO: add a nixosTest to be able to perform the package check doCheck = false; meta = with lib; { description = "DevSpace is an open-source developer tool for Kubernetes that lets you develop and deploy cloud-native software faster"; homepage = "https://devspace.sh/"; changelog = "https://github.com/loft-sh/devspace/releases/tag/v${version}"; license = licenses.asl20; maintainers = with maintainers; [ darkonion0 ]; }; } </ins>

Related discussion:
text: Project description DevSpace is an open-source developer tool for Kubernetes that lets you develop and deploy cloud-native software faster. Metadata homepage URL: source URL: license: apache2 platforms: linux, darwin
Code change:
./services/web-apps/cryptpad.nix ./services/web-apps/documize.nix ./services/web-apps/frab.nix <ins> ./services/web-apps/gotify-server.nix </ins> ./services/web-apps/icingaweb2/icingaweb2.nix ./services/web-apps/icingaweb2/module-monitoring.nix ./services/web-apps/limesurvey.nix

Related discussion:
text: Project description A simple server for sending and receiving messages in real-time per WebSocket. Includes a web UI, also has an Android client for receiving notifications and an optional CLI program (distributed separately) for sending notifications. Metadata homepage URL: source URL: license: MIT platforms: anything Go runs on
I started an attempt locally, however it failed due to some timeouts while fetching Go dependencies... will retry during this week :)
I think the main difficulty is the UI, which needs to be compiled with NPM. In essence, I think the build is three-staged: fetch UI dependencies, fetch Go dependencies, do the actual build.
You may want to take a look at .
Code change:
buildPythonPackage rec { pname = "flax"; <del> version = "0.6.0"; </del> <ins> version = "0.6.1"; </ins> src = fetchFromGitHub { owner = "google"; repo = pname; rev = "refs/tags/v${version}"; <del> sha256 = "sha256-egTYYFZxhE/Kk7jXRi1HmjCjyFia2LoRigH042isDu0="; </del> <ins> sha256 = "sha256-fZiODo+izOwGjCCTvi11GvUG/VQL1DV9bNXKjvIIw4A="; </ins> }; <del> patches = [ # Bump rich dependency, should be fixed in releases after 0.6.0 # https://github.com/google/flax/pull/2407 (fetchpatch { url = "https://github.com/google/flax/commit/72189153f9779022b97858ae747c23fbaf571e3d.patch"; sha256 = "sha256-hKOn/M7qpBM6R1RIJpnXpRoZgIHqkwQZApN4L0fBzIE="; name = "bump_rich_dependency.patch"; }) ]; </del> buildInputs = [ jaxlib ]; propagatedBuildInputs = [

Related discussion:
text: Build of failed on x86_64-linux as of . This is currently breaking . maintainers cc: maintainers cc: Other cc: n/a nixpkgs at commit This issue was automatically generated by . that created this issue. Internal tags: - -
Code change:
lib.fakeSha256; inherit url change state channel; <ins> impureEnvVars = lib.fetchers.proxyImpureEnvVars; </ins> } )

Related discussion:
text: The pijul fetcher throws a certificate error when used, for example with the following command: Related: Steps to reproduce the behavior: fetchpijul (for example like in the command above) fails with above error Repository gets fetched successfully Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Oh my, thanks for notifying, I'll make a PR to fix that ASAP!
Code change:
ninja pkg-config python3 <ins> rustPlatform.cargoSetupHook rustc </ins> wrapGAppsHook ];

Related discussion:
text: Describe the bug fails to compile with Additional context See for a possible cause. Notify maintainers cc (sorry for notifying you here and in the PR!)
Gonna try to just switch it to . We should probably update gnome docs for Rust+Gnome packages
Yeah, I think that would be best. The idea of the hooks is that is not necessary anymore in mixed projects. I will also do a PR for cargoBuildHook, since it should not be used when is set explicitly.
Code change:
qdarkstyle ]; <del> preBuild = '' </del> <ins> postPatch = '' # make compatible with protobuf4 by easing dependencies ... substituteInPlace ./contrib/requirements/requirements.txt  --replace "protobuf>=3.12,<4" "protobuf>=3.12" # ... and regenerating the paymentrequest_pb2.py file protoc --python_out=. electrum/paymentrequest.proto </ins> substituteInPlace ./electrum/ecc_fast.py  --replace ${libsecp256k1_name} ${secp256k1}/lib/libsecp256k1${stdenv.hostPlatform.extensions.sharedLibrary} '' + (if enableQt then ''

Related discussion:
text: Steps to reproduce the behavior: nixpkgs electrum was recently updated 4.3.1 -4.3.2: previously built fine on nixpkgs 2022-09-28 () <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --<!-- attempting ti bisect, but on a slow machine, and it looks like there's miscellaneous failures over this duration so not sure it'll bisect cleanly: --
bisected to: good: bad: that's the staging-next merge though, so a lot of surface area. however, we appear to address a very similar build failure over in pkgs/development/python- by doing: i'm not sure how to test this same patch on electrum since it doesn't have any file.
oh just kidding, Electrum just places its in a different location. the patch below fixes the build when applied to master, and the application starts but i didn't test any functionality that i know touches protobuf. not sure how concerned i should be about overriding a pinned dep (i'm not a python dev):
Fix in
Code change:
<ins> { config , lib , pkgs , ... }: let cfg = config.services.realm; configFormat = pkgs.formats.json { }; configFile = configFormat.generate "config.json" cfg.config; inherit (lib) mkEnableOption mkPackageOption mkOption mkIf types getExe; in { meta.maintainers = with lib.maintainers; [ ocfox ]; options = { services.realm = { enable = mkEnableOption "A simple, high performance relay server written in rust"; package = mkPackageOption pkgs "realm" { }; config = mkOption { type = types.submodule { freeformType = configFormat.type; }; default = { }; description = '' The realm configuration, see <https://github.com/zhboner/realm#overview> for documentation. ''; }; }; }; config = mkIf cfg.enable { systemd.services.realm = { serviceConfig = { DynamicUser = true; MemoryDenyWriteExecute = true; PrivateDevices = true; ProtectClock = true; ProtectKernelLogs = true; ProtectKernelModules = true; ProtectProc = "invisible"; ProtectKernelTunables = true; ExecStart = "${getExe cfg.package} --config ${configFile}"; AmbientCapabilities = [ "CAP_NET_ADMIN" "CAP_NET_BIND_SERVICE" ]; }; wantedBy = [ "multi-user.target" ]; }; }; } </ins>

Related discussion:
text: Project description A simple, high performance relay server written in rust. Metadata homepage URL: source URL: license: mit platforms: Linux, darwin Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Code change:
# there is at least one "privileged" account that has a # password or an SSH authorized key. Privileged accounts are # root and users in the wheel group. <del> assertion = !cfg.mutableUsers -> any id ((mapAttrsToList (_: cfg: (cfg.name == "root" </del> <ins> # The check does not apply when users.disableLoginPossibilityAssertion # The check does not apply when users.mutableUsers assertion = !cfg.mutableUsers -> !cfg.allowNoPasswordLogin -> any id (mapAttrsToList (name: cfg: (name == "root" </ins> || cfg.group == "wheel" || elem "wheel" cfg.extraGroups) &&

Related discussion:
text: Describe the bug There are reasons to want a system, that has no user that can log in by SSH or with their password, for example in a declarative container To Reproduce Steps to reproduce the behavior: up a minimal declarative container asserts that I will be locked out from the system and refuses to build the configuration with Expected behavior nix generates me a container that I can log in with , or maybe I don't want to log into it at all (because it's a disposable VM or something of the like). I think there should be a check whether the generated system is a container and an additional "I know what I'm doing" override for other cases. I'll create a PR once we agreed on what's best. Maintainer information: Code causing the problem: mentioning since you the check.
Is it an option to set a randomly-generated (the hash itself would be generated, not obtained by honestly hashing a password)? Recovering the password from such a hash is probably harder than a lot of other attack vectors. But an override «doLockOutEveryone» sounds fine.
Setting a password would certainly be a possibility, but somewhat (for lack of a better word) really lame. Having slept a night over it, I propose , that disables all the assertions at the bottom. I can see scenarios where two users with the same uid could be wanted. I want my unixoid to always give me enough rope to shoot myself in the leg.
What about not enabling ssh and disabling the getty? It should completely lock anyone out, unless I am missing something. Take a look at the profile.
In case of a nixos declaratively defined nixos container, you are not logged out because the root system(d) can generate a root shell without any authentication, which is why I consider this a bug. Having to "fool" the assertion to actually lock oneself out is another matter, I could live with that but I don't think it's nice behavior.
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.
Code change:
# there is at least one "privileged" account that has a # password or an SSH authorized key. Privileged accounts are # root and users in the wheel group. <del> assertion = !cfg.mutableUsers -> any id ((mapAttrsToList (_: cfg: (cfg.name == "root" </del> <ins> # The check does not apply when users.disableLoginPossibilityAssertion # The check does not apply when users.mutableUsers assertion = !cfg.mutableUsers -> !cfg.allowNoPasswordLogin -> any id (mapAttrsToList (name: cfg: (name == "root" </ins> || cfg.group == "wheel" || elem "wheel" cfg.extraGroups) &&

Related discussion:
text: 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 . 3. Ask on the on .
This is still an issue.
I marked this as stale due to inactivity. &rarr;
Fixed via