jiebi/CodeConvo huggingface dataset:
Change:
''; }; <del> syncPasswordsByPam = mkOption { type = types.bool; default = false; description = '' Enabling this will add a line directly after pam_unix.so. Whenever a password is changed the samba password will be updated as well. However, you still have to add the samba password once, using smbpasswd -a user. If you don't want to maintain an extra password database, you still can send plain text passwords which is not secure. ''; }; </del> invalidUsers = mkOption { type = types.listOf types.str; default = [ "root" ];

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

Discussion:
Package name: albert Latest released version: 0.23.0 Current version on the unstable channel: 0.22.17 Current version on the stable/release channel: 0.22.17 Notify maintainers Note for maintainers: Please tag this issue in your PR. I'm pretty new to Nix, so I hope this is the right way to request an update. The latest release can be found here:
Thank you for working on this. Unfortunately I still don't know how to get the new version. When will it be available in nixpkgs?
Depending on which channel you use: if you use unstable, as soon as unstable gets updated and includes the merged patch if you use stable, after the next stable release (24.05 afaik)
Thank you very much for explaning!
Change:
six = callPackage ../applications/video/kodi/addons/six { }; <ins> sponsorblock = callPackage ../applications/video/kodi/addons/sponsorblock { }; </ins> urllib3 = callPackage ../applications/video/kodi/addons/urllib3 { }; websocket = callPackage ../applications/video/kodi/addons/websocket { };

Discussion:
Project description Kodi sponsorblork addon for youtube. . This 3rd party port is also mentioned in . <!-- Describe the project a little: --Description This is an unofficial port of the browser extension. It works as an extension to the . Once installed, the add-on will automatically skip sponsor segments in all YouTube and Invidious videos you watch. 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]:
Change:
src = fetchurl { url = "mirror://kernel/linux/kernel/v6.x/linux-${kversion}.tar.xz"; <del> sha256 = "15m228bllks2p8gpsmvplx08yxzp7bij9fnmnafqszylrk7ppxpm"; </del> <ins> sha256 = "09sfrq2l8f777mx2n9mhb6bgz1064bl04921byqnmk87si31w653"; </ins> }; kernelPatches = let rt-patch = { name = "rt"; patch = fetchurl { url = "mirror://kernel/linux/kernel/projects/rt/${branch}/older/patch-${version}.patch.xz"; <del> sha256 = "0mrpsy175iz0b51hwgqbj15w83lm3m57il3gqwb489gln7mpzy17"; </del> <ins> sha256 = "0ihdid1ihg26kjini66j87vh4220gl8xm9dai7zignha2zh238kh"; </ins> }; }; in [ rt-patch ] ++ kernelPatches;

Discussion:
Mounting NFS volumes stopped working without configuration change other than updates. Steps to reproduce the behavior: updated system as of 2023-09-18 from stable to mount a nfs volume Get the error The volume to be mounted Please run and paste the result.
I am having the same issue, with very similar messages: I am running: It happened between ..., the only suspicious changes are kernel changes. In particular, both 6.5.2-6.5.3 and 6.1.52-6.1.53 include the patch "vfs, security: Fix automount superblock LSM init problem, preventing NFS sb sharing" which I think seems suspicious, but I don't know enough to dig any further. Any help would be appreciated.
Gentoo . In that bug, someone bisected the kernel and identified the patch that mentioned as the culprit. This link to a kernel patch that fixes the issue was also posted and verified to work:
I hit this as well, hoping it gets fixed promptly. For now I've worked around it by using an older stable kernel on affected clients:
I am guessing it will be fixed in upstream soonish, will it be fixed in NixOS like the gentoo folks did? For now, I have confirmed the above patch works on my configuration: nevivurn/nixos-config
The patch worked for me, didn't know it was that easy to apply one
cc
This patch works great! This issue still appears in , but the patch still seems to works if applied to that version.
Change:
lib.warn "getLicenseFromSpdxId: No license matches the given SPDX ID: ${licstr}" { shortName = licstr; } ); <ins> /* Get the path to the main program of a derivation with either meta.mainProgram or pname or name Type: getExe :: derivation -> string Example: getExe pkgs.hello => "/nix/store/g124820p9hlv4lj8qplzxw1c44dxaw1k-hello-2.12/bin/hello" getExe pkgs.mustache-go => "/nix/store/am9ml4f4ywvivxnkiaqwr0hyxka1xjsf-mustache-go-1.3.0/bin/mustache" */ getExe = x: "${lib.getBin x}/bin/${x.meta.mainProgram or (lib.getName x)}"; </ins> }

Discussion:
There are a couple of different ways this is determined: use or splits the derivation name  uses It would be nice if there were a helper to get this value in a consistent way, and perhaps also a way to directly get an absolute path to it.
The absolute path can be as simple as after or similar.
Change:
<ins> From 1e000ca711886055176a2f90197a383d09de0e67 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Miguel=20=C3=81ngel=20Arruga=20Vivas?= <rosen644835@gmail.com> Date: Fri, 18 Dec 2020 14:19:36 +0100 Subject: [PATCH] msginit: Do not use POT-Creation-Date. * gettext-tools/src/msginit.c (po_revision_date): Do not use POT-Creation-Date when the file is automatically generated. --- gettext-tools/src/msginit.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gettext-tools/src/msginit.c b/gettext-tools/src/msginit.c index 8ca9a3b77..06e0e7195 100644 --- a/gettext-tools/src/msginit.c +++ b/gettext-tools/src/msginit.c @@ -1075,9 +1075,9 @@ static const char * po_revision_date (const char *header) { if (no_translator) -    /* Because the PO file is automatically generated, we use the -       POT-Creation-Date, not the current time.  */ -    return get_field (header, "POT-Creation-Date"); +    /* Because the PO file is automatically generated, we don't +       generate PO-Revision-Date field.  */ +    return NULL; else { /* Assume the translator will modify the PO file now.  */ -- 2.29.2 </ins>

Discussion:
Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible- . Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems. You can use to analyze the differences in the output of the two builds. To view the build log of the build that produced the artifact in the binary cache: possibly related:
I think we haven't hit this problem before (with 2.06) because the files are usually distributed along with the source tarball. Now (with 2.12-rc1) that we've switched to a git checkout the derivation is building the files itself, and I suspect we're either not doing it right, or we're missing part of the process.
(Fixing gettext's reproducibility is also likely an acceptable solution - but I suspect there's a more targeted and less controversial fix we could just apply to grub2 directly.)
should be fixed with on staging - if we can do something to grub2 to fix it 'more targeted and less controversial' that's still fine, but might not be needed
Change:
] ++ gstDeps; propagatedBuildInputs = [ <del> evdev distro pyyaml pygobject3 requests pillow dbus-python keyring </del> <ins> evdev distro lxml pyyaml pygobject3 requests pillow dbus-python keyring python_magic </ins> ]; # avoid double wrapping

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 --- name: lutris <!-- 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.5.7.1 desired version: 0.5.8.3 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: As there is no maintainer listed, was the last to update the package. Please tag this issue in your PR. Just bumping the version didn't seem to work. You have to add python magic as a dependency, but then, all the tests were failing. I don't recall why tho (tried it a few days ago)
Change:
gdb man emacs ]; <ins> # Expects there to always be a thread with ID # thread:0000000000000009, but notmuch new is non-deterministic so # this isn't always the case.  Upstream bug report: # https://nmbug.notmuchmail.org/nmweb/show/871reno6g7.fsf%40alyssa.is NOTMUCH_SKIP_TESTS = "lib-thread"; </ins> installTargets = [ "install" "install-man" "install-info" ]; postInstall = stdenv.lib.optionalString withEmacs ''

Discussion:
Describe the bug notmuch fails to build in the unstable branch, its test suite fails and reports an error To Reproduce with notmuch somewhere in your environment Additional context Notify maintainers Metadata Maintainer information:
Which CPU are you compiling on? We've found an issue that seems to occur only on an EPYC machine, and under very specific circumstances, so I wonder if this is the same issue.
Minor note:
I have a Xeon E-2288G I can try it on too if needed! Oh yeah duh, thanks, typo corrected!
The compiler gives a warning and the testsuite picks it up -- change makeFlags to . That fixes compilation (only tested with 0.31.3, but presumably works for 0.31 as well).
Hmm, this: doesn't seem to fix it on my end
Ok, I'll see if I can find time to check with the old version. Steps I did: nixpkgs nixos-unstable definition and build with (then you can also see the fails)
and I have been looking into this failure for a few days, since before this issue was opened. We can confidently say that it fails intermittently. We think it might be hardware-dependent, time-dependent, or both.
In a VM I had some issued, but couldn't reproduce on my laptop. Guess your comment explains why...
Change:
}; } </programlisting> <del> <para>At the moment you still have to restart Nginx after the ACME certs arrive.</para> </del> </section> </chapter>

Discussion:
This is a quote from : This looks like a todo item, but I couldn't find an issue for it, so I'm creating that issue here. I also have a question: Does this mean you have to restart Nginx the first time to ACME certs arrive, or every time they renew? And do I understand correctly that this recurring manual task kind of defeats the purpose of using ACME while this issue is still open? (Should we update the manual in the meantime to clarify that the ACME feature isn't really usable yet?)
As far as I'm aware and this includes me using ACME a lot, this no longer is necessary, can you open a PR removing that line?
Sure thing
Thanks for the doc fixes!
I just had had a case where the LE certificate was renewed but the change was not picked up by nginx (until I manually restarted nginx) (few weeks old 17.09). Seems like this is still necessary.
Just to be sure, are you letting Nix generate the relevant nginx config (via setting the option)? I ask because I had that problem for a while because I didn't know you had to do that, and enabling this seems to be what's supposed to cause nginx to reload when certs arrive.
Yup, nginx config is generated with and enableAcme is true for all 3 vhosts. All the acme stuff seems to be working fine and according to the logs nginx was reloaded: (please ignore the unusual formatting as this is extracted from Graylog as the original journal entry was no longer available due to log rotation) I can see no error/warning of any kind. Just a moment after nginx reload is completed the acme unit startup is completed so it looks ok but nginx was still using the old certificates. According to some quick research it should be sufficient to send SIGHUP to nginx which is exactly what is done at so I have no idea why it is not working. This is the 2nd time this has happened to me. I dismissed the first one as I was unsure of the circumstances. It is quite hard to debug as one usually only notices the issue days(weeks) later when the certificate is expired.
Change:
<ins> { lib , stdenv , fetchurl , dpkg , autoPatchelfHook , wrapQtAppsHook , qtbase , qtdeclarative , qtsvg }: stdenv.mkDerivation (finalAttrs: { pname = "texturepacker"; version = "7.1.0"; src = fetchurl { url = "https://www.codeandweb.com/download/texturepacker/${finalAttrs.version}/TexturePacker-${finalAttrs.version}.deb"; hash = "sha256-9HbmdMPTp6qZCEU/lIZv4HbjKUlEtPVval+y0tiYObc="; }; nativeBuildInputs = [ dpkg autoPatchelfHook wrapQtAppsHook ]; buildInputs = [ qtbase qtdeclarative qtsvg ]; installPhase = '' mkdir -p $out/bin $out/lib cp usr/lib/texturepacker/{libGrantlee_Templates.so.5,libHQX.so.1.0.0,libPVRTexLib.so} $out/lib cp usr/lib/texturepacker/TexturePacker $out/bin cp -r usr/share $out ''; meta = { changelog = "https://www.codeandweb.com/texturepacker/download"; description = "Sprite sheet creator and game graphics optimizer"; homepage = "https://www.codeandweb.com/texturepacker"; license = lib.licenses.unfree; mainProgram = "TexturePacker"; maintainers = with lib.maintainers; [ tomasajt ]; platforms = [ "x86_64-linux" ]; }; }) </ins>

Discussion:
Project description TexturePacker - Utility for creating optimized sprite sheets. Metadata homepage URL: source URL: license: unfree platforms: linux Here is what I have so far: CLI works, while GUI segfaults: <details</details
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Change:
preFixup = '' # The following libraries need libtiff.so.5, but nixpkgs provides libtiff.so.6 patchelf --replace-needed libtiff.so.5 libtiff.so $out/opt/kingsoft/wps-office/office6/{libpdfmain.so,libqpdfpaint.so,qt/plugins/imageformats/libqtiff.so} <ins> # dlopen dependency patchelf --add-needed libudev.so.1 $out/opt/kingsoft/wps-office/office6/addons/cef/libcef.so </ins> ''; postFixup = ''

Discussion:
Describe the bug When open any component of wps office, it shows an dialog "An error has occurred in WPS" and crash. No logs found, but it works by using steam-run. To Reproduce Steps to reproduce the behavior: package pkgs.wpsoffice it in terminal or click office logo shows an error dialog, self-restart repeatedly and exit. Screenshots ! Notify maintainers Metadata `` Maintainer information:
Confirmed this error on my nixos
Change:
{ lib, stdenv, fetchurl, substituteAll , pkg-config, autoreconfHook <del> , cups, zlib, libjpeg, libusb1, python3Packages, sane-backends </del> <ins> , cups, zlib, libjpeg, libusb1, python311Packages, sane-backends </ins> , dbus, file, ghostscript, usbutils , net-snmp, openssl, perl, nettools, avahi , bash, util-linux

Discussion:
Steps to reproduce the behavior: build .#hplip Looks like more fallout from Python 3.12. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
}; <del> meta.maintainers = with lib.maintainers; [ minijackson ]; </del> <ins> meta.maintainers = with maintainers; [ minijackson nu-nu-ko ]; </ins> }

Discussion:
I currently run Jellyfin in a Docker container but want to deploy it using an ephemeral NixOS container. However, does not expose a option and runs Jellyfin with where . I understand that this directory will be cleared when the container restarts. I'm not familiar with 's nor the aggressive sandboxing. Need I consider something else when adding the option other than user permissions?
I am experimenting with this, I just some options for defining a and a . It seems to "just work tm", but is there anything I should be aware of? I'll run my own nixpkgs branch on my own machine for a little bit before creating a PR, but so far it seems fine.
I looked a bit into this, and I think bind mounts is what works best with systemd. But I didn't really find a lot of info...
Relevant:
I'm interested in this as well. Currently the Sonarr, Radarr, Jackett, and Ombi services provide . Is the approach they use also usable here?
Change:
, lib , buildPythonPackage , fetchPypi <ins> , fetchpatch </ins> , gfortran, glibcLocales , numpy, scipy, pytest, pillow , cython

Discussion:
Describe the bug Currently the python 3.7 module (the other versions likely too, but I have not tested this yet) fails due to some numeric discrepancy caused by a recent upgrade of . This breaks ~26 downstream packages. I'm filing this to keep track of this for and am currently bisecting to confirm and test some other versions too. This is caused by a singular test failure: Upstream issue: Full hydra log: To Reproduce Steps to reproduce the behavior: on or . fails Expected behavior Tests should pass. Maintainer information:
Fixed by
Change:
githubId = 20176306; name = "jammerful"; }; <ins> janik = { name = "Janik"; email = "janik@aq0.de"; matrix = "@janik0:matrix.org"; github = "Janik-Haag"; githubId = 80165193; }; </ins> jansol = { email = "jan.solanti@paivola.fi"; github = "jansol";

Discussion:
Project description a program for managing several popular DMR hand held radios Metadata homepage URL: source URL: license: gpl3 platforms: linux, macos
Change:
}; http_addr = mkOption { <del> description = lib.mdDoc "Listening address."; default = ""; </del> type = types.str; <ins> default = "127.0.0.1"; description = lib.mdDoc '' Listening address. ::: {.note} This setting intentionally varies from upstream's default to be a bit more secure by default. ::: ''; </ins> }; http_port = mkOption {

Discussion:
changed on which address Grafana listens by default. Previously (under 22.05) it was localhost only and it was necessary to explicitly adjust this if so desired. Now (with 22.11) Grafana is listening on all IPs. Previously: New default is to listen on all IPs: Without enabled (and properly configured) firewall this could result in situations where people are exposing their Grafana installation unintentionally.
but the default settings should suffice to catch this, right? This also matches the upstream grafana default
Yes, I would think so. Therefore not really dramatic in most cases.
Change:
kochi-substitute-naga10 = callPackage ../data/fonts/kochi-substitute-naga10 {}; <del> latinmodern-math = callPackage ../data/fonts/lm-math {}; </del> lato = callPackage ../data/fonts/lato {}; league-of-moveable-type = callPackage ../data/fonts/league-of-moveable-type {};

Discussion:
A grep of : The latest version is 1.959 per I'd say that the texlive and fonts/lm-math versions can stay as they have different paths ( vs ), although ideally just the texlive version would stay, but the others are not helping anything at all.
cc for comments
– has meta, unpacks only the needed files – resides in the same directory with , tries to provide texmf So, perhaps, we should keep the implementation of under the name and make an alias. The satysfi needs to be fixed to use existing packages (also implements a duplicate of ).
Well, for texmf one would presumably use the TexLive package, as it has separated and outputs unlike the other packages. And it auto-updates along with the rest of TexLive. The only issue with using it as the sole package is that it's not a multiple output derivation so using it in the fonts list looks like rather than just . It shouldn't be that hard to set up TexLive to have attributes usable directly, by setting and so forth. Nix doesn't support multiple outputs for fixed-output derivations, so it'd be a bit of a hack.
The "packages" in are set up to be used with . They were not intended to be used in any other way.
Change:
sed -i src/form.c -e '21i#include <stdlib.h>' # there is no point to bring in the whole netpbm package just for this file <del> install -Dm644 ${netpbm}/share/netpbm/misc/rgb.txt $out/share/yad/rgb.txt </del> <ins> install -Dm644 ${netpbm.out}/share/netpbm/misc/rgb.txt $out/share/yad/rgb.txt </ins> ''; postAutoreconf = ''

Discussion:
no $ Add to installPhase
For some reason netpbm is installing the symlink to . Will be fixed by

Describe the bug Netpbm misses TIFF converters, such as . To Reproduce Steps to reproduce the behavior: to find some commands. Expected behavior TIFF converters installed with Netpbm. Additional context libtiff is required to build the following Netpbm programs: , , and (). Indeed is input for the , but TIFF converters are missed. Metadata output:
Change:
meta = { description = "Like neofetch, but much faster because written in C"; homepage = "https://github.com/fastfetch-cli/fastfetch"; <ins> changelog = "https://github.com/fastfetch-cli/fastfetch/releases/tag/${finalAttrs.version}"; </ins> license = lib.licenses.mit; <del> maintainers = with lib.maintainers; [ khaneliman ]; </del> <ins> maintainers = with lib.maintainers; [ luftmensch-luftmensch khaneliman ]; </ins> platforms = lib.platforms.all; mainProgram = "fastfetch"; };

Discussion:
Package name: fastfetch Latest released version: 2.21.0 <!-- Search your package here: --- Current version on the unstable channel: 2.20.0 Current version on the stable/release channel: 2.13.2 <!-- 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]: