jiebi/CodeConvo huggingface dataset:
Change:
Type = "oneshot"; # Enable internet access PrivateNetwork = false; <del> # Restrict write access BindPaths = []; BindReadOnlyPaths = [ "/nix/store" "-/etc/resolv.conf" "-/etc/nsswitch.conf" "-/etc/ssl/certs" "-/etc/static/ssl/certs" "-/etc/hosts" "-/etc/localtime" ]; </del> ExecStart = let pythonWithNltk = pkg.python.withPackages (ps: [ ps.nltk ]); in '' ${pythonWithNltk}/bin/python -m nltk.downloader -d '${nltkDir}' punkt snowball_data stopwords '';

Discussion:
My paperless-ngx install has been broken for some time; it looks like paperless-scheduler.service fails to start, which means that paperless-consumer.service and paperless-web.service can't run: I don't have any idea at all how to debug this, sorry. Steps to reproduce the behavior: paperless should work! <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --paperless-ngx maintainers: nixos/paperless maintainers: Please run and paste the result.
+1 habe die selbe fehlermeldung
Here's the .
Will try to find this later, or do you want to do that
Probably caused by the latest systemd update and something in the mount-sandboxing does not work as expected anymore.
The more invasive fix is to set . I actually don't know whether this a regression in systemd or intented. Also there's surely a better fix (maybe with the new systemd option ?), so what should we do?
Change:
blivet = callPackage ../development/python-modules/blivet { }; <ins> bluepy = callPackage ../development/python-modules/bluepy { }; </ins> boltons = callPackage ../development/python-modules/boltons { }; bravia-tv = callPackage ../development/python-modules/bravia-tv { };

Discussion:
Project description Python interface to Bluetooth LE on Linux describe the project a little This package seems to be required by mitemp_bt component of home-assistant service. Metadata homepage URL: source URL: license: gpl2+ platforms: linux
So far this is what I got: But it doesn't build because it can't find pkg-config or glib.h .
It's vendoring in a C dependency and compiling it sigh..... we would want to swap that out for one from nixpkgs but I'm not sure how. Given that there aren't any tests I'm not sure we can know if the version from nixpkgs (which might differ from the one vendored in) would even work.
I am also interested in bluepy. It is the only reliable library for BLE on Linux that I've found.
This works for me.
Can you provide an example of how you are using this in your
Change:
./fix-static.patch ]; <ins> makeFlags = [ "PREFIX=${placeholder "out"}" "UDEVLIBDIR=${placeholder "out"}/lib/udev/" ]; </ins> preBuild = '' <del> export makeFlags="$makeFlags PREFIX="$out" UDEVLIBDIR="$out/lib/udev/""; </del> sed -e "s|/bin/sh|${bash}/bin/sh|" -i *.rules '';

Discussion:
This is pulled in unconditionally by and fails during NixOS cross-compilation: I'm also unsure if we still need the / cc cc
I've just opened which fixes the cross compilation. Not sure if it's the most elegant way to fix it though.
Change:
, networkmanager }: stdenv.mkDerivation rec { pname = "tlp"; <del> version = "1.3.1"; </del> <ins> version = "1.4.0"; </ins> src = fetchFromGitHub { owner = "linrunner"; repo = "TLP"; rev = version; <del> sha256 = "14fcnaz9pw534v4d8dddqq4wcvpf1kghr8zlrk62r5lrl46sp1p5"; </del> <ins> sha256 = "sha256-Blwj4cqrrYXohnGyJYe+1NYifxqfS4DoVUHmxFf62i4="; </ins> }; # XXX: See patch files for relevant explanations. <del> patches = [ ./patches/fix-makefile-sed.patch ./patches/tlp-sleep-service.patch ]; </del> <ins> patches = [ ./patches/0001-makefile-correctly-sed-paths.patch ./patches/0002-tlp-sleep.service-reintroduce.patch ]; </ins> buildInputs = [ perl ]; nativeBuildInputs = [ makeWrapper gnused ];

Discussion:
<!-- 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: <!-- 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: 1.3.1 desired version: 1.4.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.
Change:
<ins> --- a/src/lapi.c +++ b/src/lapi.c @@ -1285,14 +1285,14 @@ LUA_API void *lua_upvalueid (lua_State * LUA_API void lua_upvaluejoin (lua_State *L, int fidx1, int n1, int fidx2, int n2) { -  LClosure *f1; -  UpVal **up1 = getupvalref(L, fidx1, n1, &f1); +  UpVal **up1 = getupvalref(L, fidx1, n1, NULL); /* the last parameter not needed */ UpVal **up2 = getupvalref(L, fidx2, n2, NULL); +  if (*up1 == *up2) return; /* Already joined */ +  (*up2)->refcount++; +  if (upisopen(*up2)) (*up2)->u.open.touched = 1; +  luaC_upvalbarrier(L, *up2); luaC_upvdeccount(L, *up1); *up1 = *up2; -  (*up1)->refcount++; -  if (upisopen(*up1)) (*up1)->u.open.touched = 1; -  luaC_upvalbarrier(L, *up1); } </ins>

Discussion:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
Still no new release from upstream. Looks like the discussion sort of fizzled out: Ubuntu and RHEL apply a patch for this, see for example:
Should be backported as well.
Looks like the patch was applied to unstable and backported to 19.09. Can we close this issue?
Change:
SDL2 libusb1 dbus-glib <ins> gsettings-desktop-schemas </ins> ffmpeg libudev0-shim

Discussion:
The steam client (beta) is attempting to access gsettings schemas and fails. Exporting manually as fixes the issue. into the (likely don't have gtk3/gsettings-desktop-schema already addressable on the host, not steam-run, path) steam the following error GSetting should be looking for schema files in BuildFHSEnv moves schemas to XDGDATADIRS in the fhsenv doesn't include is being pulled into the fhsenv via It's possible just adding to the end of the environment variable is the fix. I'm unfamiliar with gsettings. Attempting does not work as in the fhsenv is missing things adds in . Please run and paste the result.
Exporting GSETTINGSSCHEMADIR manually did not work for me. I left beta participation by removing the file:
+1 affected by this. Edit: this results when you participate in Steam-beta. This is from recent update - however recent major update worked perfectly (new sleeker interface and all that), breakage appeared around 24 hours ago and it was pulled by Steam. This breaks for all users in system. Removing beta flag (as in McDread solution above) works, causing Steam to downgrade. Upgrading into Steam-Beta after this will cause Steam to break again.
Setting GSETTINGSSCHEMADIR worked once for me, but no longer after a reboot.
Try setting it in the extraProfile attribute in steam.override like this
I was able to fix this by overriding steam, adding and setting :
This works great! Tested with reboot.
This worked
For me, this was in the location . Removing that file worked.
+1 affected by this. workaround does fix it.
Change:
meta = getMeta "Distributed storage system"; passthru.version = version; <ins> passthru.tests = { inherit (nixosTests) ceph-single-node ceph-multi-node ceph-single-node-bluestore; }; </ins> }; ceph-client = runCommand "ceph-client-${version}" {

Discussion:
Describe the bug Using ceph-volume to create a new bluestore-backed OSD doesn't work. To Reproduce Steps to reproduce the behavior: -volume lvm create --data /dev/sda --bluestore --no-systemd Expected behavior A clear and concise description of what you expected to happen. A new Bluestore OSD (on LVM) is successfully provisioned. Switching RocksDB to the Ceph-bundled copy rather than the OS version makes it work. I note that the Ceph NixOS test uses filestore instead. Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. 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: nixpkgs: Maintainer information:
Change:
lassulus = "Lassulus <lassulus@gmail.com>"; layus = "Guillaume Maudoux <layus.on@gmail.com>"; ldesgoui = "Lucas Desgouilles <ldesgoui@gmail.com>"; <ins> league = "Christopher League <league@contrapunctus.net>"; </ins> lebastr = "Alexander Lebedev <lebastr@gmail.com>"; leenaars = "Michiel Leenaars <ml.software@leenaa.rs>"; leonardoce = "Leonardo Cecchi <leonardo.cecchi@gmail.com>";

Discussion:
I could not access my USB digital camera as a non-root user, due to insufficient permissions. The file in popped up with user and group set to . I'm new to NixOS and I'm not sure of the best way to solve something like this. Below I'll document a workaround that I used in my that solved the problem, in case that's helpful to others. But if a NixOS option along with some facility in the package could solve it, that would be ideal. Plug camera into USB Ensure it shows up in Run At first it died with "unknown error", but if you do you see the "insufficient permissions" message. System: 16.09.1357. (Flounder) Nix version: nix-env (Nix) 1.11.4 Nixpkgs version: 16.09.1357. I these to my : where I copied the file .
Tagging the gphoto2 maintainer thanks.
you can graft a module, which does exactly the steps above to fix this in long term. I did something similar for adb:
I see, thanks. So there's to define the option, and it references which contains the rules, maintained separately from the packages in . I'll aim to put together something similar for gphoto2.
Change:
kube-prompt = callPackage ../development/tools/kube-prompt { }; <del> kubei = callPackage ../tools/security/kubei { }; </del> <ins> kubeclarity = callPackage ../tools/security/kubeclarity { }; </ins> kubemq-community = callPackage ../servers/kubemq-community { };

Discussion:
<!-- 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 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: kubei <!-- The current version can be found easily with the same process as 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: 1.0.12 desired version: 2.9.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.
Change:
<ins> { lib , stdenv , fetchFromGitLab , fetchpatch , meson , ninja , pkg-config , rustPlatform , rustc , cargo , wrapGAppsHook4 , blueprint-compiler , libadwaita , libsecret , tracker , darwin }: stdenv.mkDerivation rec { pname = "health"; version = "0.94.0"; src = fetchFromGitLab { domain = "gitlab.gnome.org"; owner = "World"; repo = pname; rev = version; hash = "sha256-KS0sdCQg2LqQB0K1cUbAjA8VITn5rAb8XCWjOKYbPqM="; }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; patches = [ ./update_gtk4_cargo_deps.patch ]; name = "${pname}-${version}"; hash = "sha256-j0I0vKoGaf2pce2C/xkz+nJYCfLvHB5F6Q9XpJtABMI="; }; patches = [ (fetchpatch { url = "https://aur.archlinux.org/cgit/aur.git/plain/max_size_tightending_thresh_0.94.0.patch?h=health&id=d35d89760964b00ad457eca07855143a1dcbabdf"; hash = "sha256-ndoxyrm+SVGVxfUbc5sQItQwzK75ZtKMSGUOB9mzBmo="; }) (fetchpatch { url = "https://aur.archlinux.org/cgit/aur.git/plain/max_value_0.94.0.patch?h=health&id=d35d89760964b00ad457eca07855143a1dcbabdf"; hash = "sha256-YKVQNtz+RWN6Ydw+kbStCVf0vu0eTrMKGd6kEijFG00="; }) # patch both or it will complain Cargo.lock mismatch ./update_gtk4_cargo_deps.patch ]; nativeBuildInputs = [ meson ninja pkg-config rustPlatform.cargoSetupHook rustc cargo wrapGAppsHook4 blueprint-compiler ]; buildInputs = [ libadwaita libsecret tracker ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.Security darwin.apple_sdk.frameworks.Foundation ]; meta = with lib; { description = "A health tracking app for the GNOME desktop"; homepage = "https://apps.gnome.org/app/dev.Cogitri.Health"; license = licenses.gpl3Plus; mainProgram = "dev.Cogitri.Health"; maintainers = with maintainers; [ aleksana ]; platforms = platforms.unix; }; } </ins>

Discussion:
Project description Health can visualize how many steps you’ve made daily, your weight development over time and your daily activities. Data can be synched from Google Fit or manually entered into Health. Afterwards, it can be viewed and edited in Health. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
config = mkIf cfg.enable { <del> environment.etc."sshguard.conf".text = let args = lib.concatStringsSep " " ([ "-afb" "-p info" "-o cat" "-n1" ] ++ (map (name: "-t ${escapeShellArg name}") cfg.services)); backend = if config.networking.nftables.enable then "sshg-fw-nft-sets" else "sshg-fw-ipset"; in '' BACKEND="${pkgs.sshguard}/libexec/${backend}" LOGREADER="LANG=C ${pkgs.systemd}/bin/journalctl ${args}" ''; </del> <ins> environment.etc."sshguard.conf".source = configFile; </ins> systemd.services.sshguard = { description = "SSHGuard brute-force attacks protection system";

Discussion:
Describe the bug sshguard is not restarted when services.sshguard.services changes, instead the old configuration is used until sshguard is restarted through some non-nixos-rebuild means To Reproduce Steps to reproduce the behavior: services.sshguard with some value for services.sshguard.services services.sshguard.services -rebuild switch Expected behavior sshguard is restarted with the new services list passed to journalctl Screenshots n/a Additional context since the services list only affects the config file (not the systemd service) and the firewall backend does the same, this should also affect changes in the firewall backend. that probably doesn't matter though. 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(root): nixpkgs: Maintainer information:
Change:
enableParallelBuilding = true; meta = with stdenv.lib; { <del> description = "VAAPI tools: Video Acceleration API"; homepage = "http://www.freedesktop.org/wiki/Software/vaapi"; </del> <ins> description = "A collection of utilities and examples for VA-API"; longDescription = '' libva-utils is a collection of utilities and examples to exercise VA-API in accordance with the libva project. ''; homepage = "https://github.com/intel/libva-utils"; changelog = "https://raw.githubusercontent.com/intel/libva-utils/${version}/NEWS"; </ins> license = licenses.mit; <del> maintainers = with maintainers; [ ]; </del> <ins> maintainers = with maintainers; [ primeos ]; </ins> platforms = platforms.unix; }; }

Discussion:
Describe the bug libva tries to find and use instead of like before To Reproduce Steps to reproduce the behavior: nixos-unstable channel vlc on console to see log any video in vlc Expected behavior is used and no vlc crash happens Additional context Add any other context about the problem here. 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(gnidorah): channels(root): nixpkgs: Maintainer information:
Seems to be an upstream issue that affects only X11 (DRI 2): After we update to this should be fixed. As a temporary workaround it should work via (or , depending on which driver you prefer).
I opened a PR for the update: Note: I the regression label as is the new default since Mesa 20 (the previous default driver was ). As a result NixOS shouldn't be affected by this as we stayed on Mesa 19.
Change:
stdenv.mkDerivation rec { name = "${pname}-${version}"; pname = "clingo"; <del> version = "5.2.2"; </del> <ins> version = "5.3.0"; </ins> src = fetchzip { url = "https://github.com/potassco/clingo/archive/v${version}.tar.gz"; <del> sha256 = "04rjwpna37gzm8vxr09z3z6ay8y8cxbjd8lga7xvqfpn2l178zjm"; </del> <ins> sha256 = "01czx26p8gv81ahrh650x208hjhd8bx1kb688fmk1m4pw4yg5bfv"; </ins> }; buildInputs = [];

Discussion:
Currently python packages in propagatedBuildInputs are included into PYTHONPATH and are referenced by a file in the output (propagated-build-native-inputs), which makes them run-time dependencies: For ELF programs nix can figure out the run-time dependencies by scanning the executables, this fails for python as the dependencies are not referenced in any file. DISCUSSION: pth files could include such references and would handle PYTHONPATH manipulation a nix-support/python-build-inputs could list python buildInputs, turning them into run-time dependencies and further they would be used in the above _addToPythonPath
pth files it is
Change:
"-Donnxruntime_BUILD_UNIT_TESTS=ON" "-Donnxruntime_ENABLE_LTO=ON" "-Donnxruntime_USE_FULL_PROTOBUF=OFF" <ins> (lib.cmakeBool "onnxruntime_USE_CUDA" cudaSupport) (lib.cmakeBool "onnxruntime_USE_NCCL" cudaSupport) </ins> ] ++ lib.optionals pythonSupport [ "-Donnxruntime_ENABLE_PYTHON=ON" <ins> ] ++ lib.optionals cudaSupport [ (lib.cmakeFeature "FETCHCONTENT_SOURCE_DIR_CUTLASS" cutlass) (lib.cmakeFeature "onnxruntime_CUDNN_HOME" cudaPackages.cudnn) (lib.cmakeFeature "CMAKE_CUDA_ARCHITECTURES" cudaArchitecturesString) </ins> ]; <del> env = lib.optionalAttrs stdenv.cc.isClang { </del> <ins> env = lib.optionalAttrs effectiveStdenv.cc.isClang { </ins> NIX_CFLAGS_COMPILE = toString [ "-Wno-error=deprecated-declarations" "-Wno-error=unused-but-set-variable" ]; }; <del> doCheck = true; </del> <ins> doCheck = !cudaSupport; requiredSystemFeatures = lib.optionals cudaSupport [ "big-parallel" ]; </ins> postPatch = '' substituteInPlace cmake/libonnxruntime.pc.cmake.in  --replace-fail '$'{prefix}/@CMAKE_INSTALL_ @CMAKE_INSTALL_ <del> '' + lib.optionalString (stdenv.hostPlatform.system == "aarch64-linux") '' </del> <ins> '' + lib.optionalString (effectiveStdenv.hostPlatform.system == "aarch64-linux") '' </ins> # https://github.com/NixOS/nixpkgs/pull/226734#issuecomment-1663028691 rm -v onnxruntime/test/optimizer/nhwc_transformer_test.cc '';

Discussion:
Project description ONNX Runtime: cross-platform, high performance ML inferencing and training accelerator . Onnxruntime is already packaged. I would like to have the version with gpu support to be able to package obs-backgroundremoval with gpu support (). Related: Metadata homepage URL: source URL: license: mit platforms: linux
Obs-backgroundremoval includes tensorrtproviderfactory.h to build
need it, too
Is it possible to add gpu support to the obs-backgroundremoval as this issue is closed?
It may be possible. If anyone wants to open a PR for that, please base it on the current update PR
Change:
inherit (pkgs) gnome-user-docs; # added 2019-11-20 <del> inherit (pkgs) gegl_0_4; # added 2019-10-31 </del> inherit (pkgs) gjs; # added 2019-01-05 inherit (pkgs) yelp-tools; # added 2019-11-20

Discussion:
Describe the bug I get this: It can also be seen on hydra: successful build: (revision ) First unsuccessful build: (revision ) To Reproduce Expected behavior It should build. Notify maintainers Maintainer information:
Considering it's abandonware since there's a new version, not resolving it and just setting it as broken is perhaps best.
Or removing arch from meta.platforms. Though really, nothing should be using such ancient version these days.
See for alternative solution (dropping gegl 0.2 completely)
Change:
opencascade-occt_7_6, openvdb, pcre, <del> qhull, </del> systemd, tbb_2021_11, webkitgtk,

Discussion:
Package name: orca-slicer Latest released version: 2.1.1 <!-- Search your package here: --- Current version on the unstable channel: 2.0.0 Current version on the stable/release channel: 2.0.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! --- <!-- 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]:
please change update from 2.0.0 to 2.1.1 due to some major bugs in 2.1.0
Change:
$out/share/dbus-1/services/net.sf.cdemu.CDEmuDaemon.service  --replace /bin/true ${coreutils}/bin/true ''; <ins> meta = { inherit (meta) description license longDescription maintainers platforms ; homepage = "https://cdemu.sourceforge.io/about/daemon/"; mainProgram = "cdemu-daemon"; }; </ins> }

Discussion:
Steps to reproduce the behavior: cdemu/vhba on latest nixos-unstable Looks like there's a new vhba module version: <!-- 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]:
broken by
Change:
stdenv.mkDerivation rec { pname = "armcord"; <del> version = "3.2.1"; </del> <ins> version = "3.2.3"; </ins> src = let

Discussion:
Package name: ArmCord Latest released version: 3.2.3 <!-- Search your package here: --- Current version on the unstable channel: 3.2.1 Current version on the stable/release channel: 3.2.0 Repository: Website: <!-- 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:
}; xkbOptions = mkOption { <del> type = types.str; </del> <ins> type = types.commas; </ins> default = "terminate:ctrl_alt_bksp"; example = "grp:caps_toggle, grp_led:scroll"; description = ''

Discussion:
I have a dell as my personal latop, and a mac book pro for work, and I want to exchange option/command key only on the mbp. If this nixos option was a list which was then comma-separated, this would be trivial, since the module system would be able to combine for me. I'd make this change myself, but I'm a bit busy ATM.
It does seem like it ought to be a list - but it also seems pretty trivial regardless, since you can use to concat your list together.
There are also options to go even further...
well I mean with a list/object, the module system will transparently combine definitions in different modules, whereas with concatStringSep, one needs to route the data oneself. Good idea going further. I like the second one as a compromise between structure and brevity.
(triage) any progress?
Nope, but I think it would still be good to have (though thankfully I no longer need to use a macos laptop!). It would be nice if we could tag things like this with some sort of "easy" / "first issue" tag, so they can have a positive role for community building, rather than just being yet another old issue needing triaging.