jiebi/CodeConvo huggingface dataset:
Change:
sha256 = "1764ikgj24jjq46s50apwkydqvy5a13adb2nbszk8kbci6df0v27"; }; <ins> patches = [ (substituteAll { src = ./clipboard-make-which-substitutable.patch; which = "${which}/bin/which"; })]; </ins> propagatedBuildInputs = [ curtsies greenlet pygments requests urwid ]; postInstall = ''

Discussion:
09.
We should patch the call of in using . cc maintainer
it also tries to also call out to at least xclip (on Linux), pbcopy (on Darwin), and less - should we patch these in, too?
I don't think so as bpython shouldn't depend on X.
On Linux it should have in its dependencies. Otherwise is still going to fail. The whole point of being able to run something via is that all dependencies are in, and if you have to know about random run-time dependencies that are not obvious, some advantages are nullified.
However, the whole point of bpython calling which is to make the dependency on xclip optional. It will hence not fail without it.
Fair point, but I prefer to have programs that are fully featured by default. People that run on limited platforms can make a more complicated expression optimized for their use cases.
If you do the PR, I won't reject patching in the path to xclip.
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 .
I prefered not dragging in and all its dependencies by default and opened On systems with in , this should do the right thing - PTAL.
Change:
--replace "/bin/kill" "${coreutils}/bin/kill" ''; <ins> passthru.tests.nixos = nixosTests.maddy; </ins> meta = with lib; { description = "Composable all-in-one mail server"; homepage = "https://maddy.email";

Discussion:
Maddy, a small and compact mail server written in Go, was merged as a package with by . Having a NixOS module to enable and configure it would be really great! If someone is interested in creating a PR, I will be happy to help and test it :+1: Best regards Jonas
Hi, I dont have any sort of way to properly test this within the actual nixos repo but I've got a personal working module/service you can try
I did something very similar to the above, but based my serviceConfig on the example . It contains quite a bit more of the systemd security features, so if you want to make something to include in nixpkgs I think all these things should be on! I also hooked it up to Dovecot, hence the waiting script, not sure if that's the best way of doing it.
How about this: Nice and simple.
Have you tried this? Somehow it doesn't work for me:
- it looks like the units aren't included in the nixpkgs package :man_shrugging:, but I created a PR to fix this in Please review, test, and approve PR. I have never used so I wouldn't want to merge that PR without you (or someone else) testing. Thanks!
Change:
<del> { lib , rustPlatform , fetchFromGitHub , pkg-config , protobuf , bzip2 , openssl , sqlite , zstd , stdenv , darwin , nix-update-script , nixosTests , rocksdb_8_3 }: let version = "0.6.0"; rocksdb = rocksdb_8_3; in rustPlatform.buildRustPackage { pname = "stalwart-mail"; inherit version; src = fetchFromGitHub { owner = "stalwartlabs"; repo = "mail-server"; rev = "v${version}"; hash = "sha256-OHwUWSUW6ovLQTxnuUrolQGhxbhp4YqKSH+ZTpe2WXc="; fetchSubmodules = true; }; cargoLock = { lockFile = ./Cargo.lock; }; nativeBuildInputs = [ pkg-config protobuf rustPlatform.bindgenHook ]; buildInputs = [ bzip2 openssl sqlite zstd ] ++ lib.optionals stdenv.isDarwin [ darwin.apple_sdk.frameworks.CoreFoundation darwin.apple_sdk.frameworks.Security darwin.apple_sdk.frameworks.SystemConfiguration ]; env = { OPENSSL_NO_VENDOR = true; ZSTD_SYS_USE_PKG_CONFIG = true; ROCKSDB_INCLUDE_DIR = "${rocksdb}/include"; ROCKSDB_LIB_DIR = "${rocksdb}/lib"; }; # Tests require reading to /etc/resolv.conf doCheck = false; passthru = { update-script = nix-update-script { }; tests.stalwart-mail = nixosTests.stalwart-mail; }; meta = with lib; { description = "Secure & Modern All-in-One Mail Server (IMAP, JMAP, SMTP)"; homepage = "https://github.com/stalwartlabs/mail-server"; changelog = "https://github.com/stalwartlabs/mail-server/blob/${version}/CHANGELOG"; license = licenses.agpl3Only; maintainers = with maintainers; [ happysalada ]; }; } </del>

Discussion:
The new version of stalwart mail (0.7.0), has changed a lot and the module needs a rewrite for a while now, for example: I have forked nixpkgs, to remove the standard settings, to allow me to make a more complex setting. issues I see. No way to disable the default options, in: . WebUI is not currently supported The package imports the entire . <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
If you want to make a contribution, even a small one, im happy to help you get it merged !
I can take a look, as I have written quite extensive configuration for my Stalwart instance. I can check it out to make it available as a NixOS module
That would be amazing ! There is an open pr from the bot for the 0.7 upgrade, you can take over that one or make the update in a new pr. Thank you !
WIP module. I haven't tested it out yet. I will probably do so this evening:
Not yet entirely fixed, module and test need some work to support = 0.7.0
By the way, since migrating to stalwart = 0.7 requires some manual migration in any case, would it be worth setting the default database type to rocksdb instead of sqlite in the module?
In my opinion yes, for the love of Linux or just make it undefined. Do you have a git repo, where I can track your progress and when I have time, give improvements?
Change:
<ins> { lib, fetchurl, appimageTools }: let pname = "buttercup-desktop"; version = "2.13.0"; name = "${pname}-${version}"; src = fetchurl { url = "https://github.com/buttercup/buttercup-desktop/releases/download/v${version}/Buttercup-linux-x86_64.AppImage"; sha256 = "sha256-JXXJZyd/fp2463WyxIB+pKcNzGUFfCouPE6iTx2lhME="; }; appimageContents = appimageTools.extractType2 { inherit name src; }; in appimageTools.wrapType2 { inherit name src; extraPkgs = pkgs: (appimageTools.defaultFhsEnvArgs.multiPkgs pkgs) ++ [ pkgs.libsecret ]; extraInstallCommands = '' mv $out/bin/${name} $out/bin/buttercup-desktop install -m 444 -D ${appimageContents}/buttercup.desktop -t $out/share/applications substituteInPlace $out/share/applications/buttercup.desktop  --replace 'Exec=AppRun' 'Exec=buttercup-desktop' cp -r ${appimageContents}/usr/share/icons $out/share ''; meta = with lib; { description = "Cross-Platform Passwords & Secrets Vault"; homepage = "https://buttercup.pw"; license = licenses.gpl3Only; maintainers = with maintainers; [ wolfangaukang ]; platforms = [ "x86_64-linux" ]; }; } </ins>

Discussion:
Project description From : They currently provide an AppImage, but I'm having trouble getting it to run with . I think packaging this separately (i.e. build from source) would be best, but I'm not sure how to proceed. I'm new to Nix and NixOS, so help wrt this issue is appreciated! Metadata homepage URL: source URL: license: GPL3 platforms: linux, darwin, windows
Update: got it to run with by overriding to include .
try packaging it yourself use ripgrep to search nixpkgs for npm commands that are run in the aur pkgbuild read the comments too for example to build the use
Change:
pytestFlagsArray = [ "-W ignore::FutureWarning" <ins> "-W ignore::DeprecationWarning" </ins> ]; disabledTestPaths = [

Discussion:
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 tag: -
Not sure why these DeprecationWarning's are turning into errors, but oh well
Change:
, libGL , libGLU , libjpeg <ins> , ncurses </ins> , libpng, libtool, mpfr, openssl, pango, poppler , readline, sqlite , disableDocs ? false

Discussion:
Project description Racket on Chez Scheme (Racket CS) may become the default Racket implementation in the next release [1] [1] Metadata homepage URL: https://racket- source URL: license: MIT or Apache 2.0 platforms: unix
Released:
Just a note. Reading stumbled upon the following (emphasis mine): This probably needs to be worked-around...
I thought I'd have a stab at a pull request for bumping to 8.0. It's still compiling, but right now it's looking good. I just had to bump the version number, correct the checksum and fix some hardcoded paths and their like. I'll report back when I know more! Update: There were no further problems. Upstream took care of everything :-) I confirm that I got a working drracket 8.0. Test for yourself here:
Change:
''; in buildPythonApplication rec { pname = "xpra"; <del> version = "4.4.6"; </del> <ins> version = "5.0.9"; </ins> <del> src = fetchurl { url = "https://xpra.org/src/${pname}-${version}.tar.xz"; hash = "sha256-BWf3nypfSrYCzpJ0OfBkecoHGbG1lEgu5jLZhfkIejQ="; </del> <ins> src = fetchFromGitHub { owner = "Xpra-org"; repo = "xpra"; rev = "v${version}"; hash = "sha256-gwo5plCAryGC8/BKVEqyMkgB+3FM8HXG6sESomDOtNM="; </ins> }; patches = [

Discussion:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: Current version on the stable/release channel: <!-- 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. Priorities Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I've got a branch that would close this issue and update xpra to 5.0.3, the UI currently works as expected and a connection over SSH is possible however I've encountered an issue running and . The error output is similar to what can be found in some other python applications. I'll look into patching this and see if I can push this further.
Change:
, systemd # Loaded at runtime. <del> , libexif </del> <ins> , libexif, pciutils </ins> # Additional dependencies according to other distros. ## Ubuntu

Discussion:
GPU acceleration: is required to avoid (which results in a software fallback and bad performance). SwiftShader seems to perform fine (and chrome://gpu even displays "Hardware accelerated") but SwiftShader should actually use the CPU instead of the GPU. Unfortunately the Wayland support is completely broken (crashes on startup) but it was basically already broken before: . It's still a regression that makes it worse though. Google Chrome lacks a dedicated maintainer so these issues will unfortunately persist for now. Edit: This was with Mesa's driver btw (Radeon HD 6950 GPU) but it also affects at least the proprietary Nvidia drivers: .
Change:
<del> { mkDerivation, lib, fetchFromGitHub, qmake, qtbase }: </del> <ins> { lib , mkDerivation , fetchFromGitHub , qmake , qtbase , qtimageformats , qtsvg }: </ins> mkDerivation rec { pname = "qview";

Discussion:
qview support a list of images format, including webp: However, if you try opening a webp image in nixos, you get "unsupported image format". This format is listed as "optional", so it might just be a matter of activating it somehow. Steps to reproduce the behavior: qview with nex "qview " error message Image should be opened. Not needed Add any other context about the problem here.
I wonder if this is something we’d need to add in the nix Qt build itself.
Change:
*/ (enableFeature withAlsa "alsa") # FIXME: see if jellyfin-ffmpeg is already on a version >= 6.1 to use enableFeature <del> (optionalString withAribcaption "--enable-libaribcaption") </del> <ins> (optionalString (withAribcaption && lib.versionAtLeast finalAttrs.version "6.1") "--enable-libaribcaption") </ins> (enableFeature withBzlib "bzlib") (enableFeature withCelt "libcelt") (enableFeature withCuda "cuda")

Discussion:
Jellyfin-ffmpeg overrides in a way that passes one version value () to the outer scope and a different value to the derivation scope (). As a result is set and the build fails with . A rough fix looks like: Looks like also may change things in this area. Steps to reproduce the behavior: fails with Jellyfin-ffmpeg builds bumped ffmpeg in several places. It uses the existing pattern for guarding against version inconsistencies: This doesn't work as the value referenced is from the outer function scope passed in when creating not the library value set later in Building from current master Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Wouldn't something like this fix it?
that should do it. Should also be possible to send that to master as it should mean no rebuild for most other things.
Yeah I think it's better than having more stuff on the jellyfin-ffmpeg side. Also, this will fix it for any weird override.
Also, shouldn't that have broken ffmpeg <6 too?
I don't think so, if jellyfin-ffmpeg would override ffmpeg-5 or -4 it would pass the version of the ffmpeg package, which is lower than 6.1. The problem seems to be that the override of the version is not affecting the scope of the current check, so it uses 6.1.
sadly my fix doesn't seem to work. I'm not sure why but I think we'll need to override withAribcaption in jellyfin-ffmpeg.
can you test this? I think the problem is because a 3-parts version is being used with a 2-parts one.
The in that part of the code comes from ffmpeg_6-full. It's also not the issue:
So the only option is to add the override to jellyfin-ffmpeg.
Change:
homepage = "https://github.com/neovim/pynvim"; changelog = "https://github.com/neovim/pynvim/releases/tag/${version}"; license = licenses.asl20; <del> maintainers = with maintainers; [ ]; </del> <ins> maintainers = with maintainers; [ figsoda ]; </ins> }; }

Discussion:
A clear and concise description of what the bug is. Steps to reproduce the behavior: neovim 0.9.1 from unstable (/nix/store/v777qfyiinf796rgghiidn5fswgv3jyy-neovim-0.9.1/bin/nvim) neovim with healthcheck section "Python 3 provider (optional)" There should be no error shown I'll post the text output of the section, should be better than a screenshot. Add any other context about the problem here. Please run and paste the result.
seems to be broken by , opened to fix it
Change:
let pname = "heroic"; <del> version = "2.2.1"; </del> <ins> version = "2.2.6"; </ins> name = "${pname}-${version}"; src = fetchurl { url = "https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/releases/download/v${version}/Heroic-${version}.AppImage"; <del> sha256 = "sha256-zzxf3eM1fUWTVtzzABcwlmptNuCVQafvotnbOiCzu0c="; </del> <ins> sha256 = "sha256-kL30/G4DpDPwGN7PvbWest7TcgL4Rd1c2OM4nRCT3bg="; </ins> }; appimageContents = appimageTools.extractType2 { inherit name src; };

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: <!-- 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: 2.2.1 desired version: 2.2.6 <!-- 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:
(fetchNuGet { pname = "System.Globalization"; version = "4.3.0"; sha256 = "1cp68vv683n6ic2zqh2s1fn4c2sd87g5hpp6l4d4nj4536jz98ki"; }) (fetchNuGet { pname = "System.Globalization.Calendars"; version = "4.0.1"; sha256 = "0bv0alrm2ck2zk3rz25lfyk9h42f3ywq77mx1syl6vvyncnpg4qh"; }) (fetchNuGet { pname = "System.Globalization.Extensions"; version = "4.0.1"; sha256 = "0hjhdb5ri8z9l93bw04s7ynwrjrhx2n0p34sf33a9hl9phz69fyc"; }) <del> (fetchNuGet { pname = "System.IdentityModel.Tokens.Jwt"; version = "6.29.0"; sha256 = "09bpj7gginq25fiyq3za5i8wm482qbnx6qhm4dxb95jrl3mmb126"; }) </del> <ins> (fetchNuGet { pname = "System.IdentityModel.Tokens.Jwt"; version = "6.30.1"; sha256 = "1f4x5sw9wpkk485lchl0nzdzkcy83s9b119c7g187x0qvkcvdpc2"; }) </ins> (fetchNuGet { pname = "System.IO"; version = "4.1.0"; sha256 = "1g0yb8p11vfd0kbkyzlfsbsp5z44lwsvyc0h3dpw6vqnbi035ajp"; }) (fetchNuGet { pname = "System.IO"; version = "4.3.0"; sha256 = "05l9qdrzhm4s5dixmx68kxwif4l99ll5gqmh7rqgw554fx0agv5f"; }) (fetchNuGet { pname = "System.IO.Compression"; version = "4.1.0"; sha256 = "0iym7s3jkl8n0vzm3jd6xqg9zjjjqni05x45dwxyjr2dy88hlgji"; })

Discussion:
Package name: ryujinx Latest released version: 1.1.747 <!-- Search your package here: --- Current version on the unstable channel: 1.1.743 Current version on the stable/release channel: 1.1.327 Notify maintainers Note for maintainers: Please tag this issue in your PR. Finally, for anyone who stumbles upon this issues, and wants an overlay to get them to 1.1.747 without waiting for the package to be updated:
An update to this package will require updating using the script (a process I'm unfamiliar with) and changing the testProjectFile attribute because all of the source was moved into the src/ directory. Other than that and updating the source, no other changes to the derivation should be necessary
Updating a package with an update script (if it's written correctly) should be as simple as: Thanks for detailing the testProjectFile change, that's super helpful. I'm in the process of updating now.
Change:
<del> { stdenv, fetchurl, lib, darwin }: </del> <ins> { stdenv, fetchurl, lib, darwin, openssl }: </ins> # Based on https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD stdenv.mkDerivation rec { pname = "live555"; <del> version = "2019.11.22"; </del> <ins> version = "2022.01.21"; </ins> src = fetchurl { # the upstream doesn't provide a stable URL urls = [ "mirror://sourceforge/slackbuildsdirectlinks/live.${version}.tar.gz" "https://download.videolan.org/contrib/live555/live.${version}.tar.gz" ]; <del> sha256 = "144y2wsfpaclkj7srx85f3y3parzn7vbjmzc2afc62wdsb9gn46d"; </del> <ins> sha256 = "03m9wgw06vs93nbd55yq8qjpm92mcg9j7cih8j6blfnv8b0pj9bn"; </ins> }; postPatch = '' sed 's,/bin/rm,rm,g' -i genMakefiles <ins> substituteInPlace config.macosx-catalina  --replace '/usr/lib/libssl.46.dylib' "${openssl.out}/lib/libssl.dylib"  --replace '/usr/lib/libcrypto.44.dylib' "${openssl.out}/lib/libcrypto.dylib" </ins> sed  -e 's/$(INCLUDES) -I. -O2 -DSOCKLEN_T/$(INCLUDES) -I. -O2 -I. -fPIC -DRTSPCLIENT_SYNCHRONOUS_INTERFACE=1 -DSOCKLEN_T/g'  -i config.linux

Discussion:
, CVSSv3=7.5 (nixos-21.05, nixos-unstable) CVSSv3=6.5 (nixos-21.05, nixos-unstable) CVSSv3=6.5 (nixos-21.05, nixos-unstable) Live555 through 1.08 mishandles huge requests for the same MP3 stream, leading to recursion and s stack-based buffer over-read. An attacker can leverage this to launch a DoS attack. Live555 through 1.08 does not handle MPEG-1 or 2 files properly. Sending two successive RTSP SETUP commands for the same track causes a Use-After-Free and daemon crash. Live555 through 1.08 does not handle Matroska and Ogg files properly. Sending two successive RTSP SETUP commands for the same track causes a Use-After-Free and daemon crash. Scanned versions: nixos-21.05: ; nixos-unstable: .
Change:
cmakeFlags = [ "-Wno-dev" # dev warnings are only needed for upstream development <del> "-DWL_INSTALL_BASEDIR=${placeholder "out"}" "-DWL_INSTALL_DATADIR=${placeholder "out"}/share/widelands" "-DWL_INSTALL_BINARY=${placeholder "out"}/bin" </del> <ins> "-DWL_INSTALL_BASEDIR=${placeholder "out"}/share/widelands" # for COPYING, Changelog, etc. "-DWL_INSTALL_DATADIR=${placeholder "out"}/share/widelands" # for game data "-DWL_INSTALL_BINDIR=${placeholder "out"}/bin" </ins> ]; <del> nativeBuildInputs = [ cmake doxygen gettext graphviz installShellFiles ]; </del> <ins> nativeBuildInputs = [ cmake doxygen gettext graphviz installShellFiles pkg-config ]; enableParallelBuilding = true; </ins> buildInputs = [ SDL2

Discussion:
name: widelands current version: 1.0 desired version: 1.1 maintainers: The widelands devs sent us an email about the release. I think this is a first for me.
I'm working on a PR for this (and once I figure out the github UI, I'll assign it to myself)..
Closing since fixes this. Please reopen if I'm wrong.
Change:
settings = mkOption { type = with types; attrsOf (oneOf [ bool int str (listOf str) ]); <del> default = {}; </del> <ins> default = { }; </ins> description = '' ClamAV configuration. Refer to <link xlink:href="https://linux.die.net/man/5/clamd.conf"/>, for details on supported values.

Discussion:
When enabling the services and and the system is relying on wifi managed by networkmanager, freshclam will fails to get the database signature and then clamav will refuse to start because freshclam is in failed state. When using ethernet connection, internet connection is working at boot time, before an user log in and freshclam doesn't fail. I suspect if you configure wifi without networkmanager it would also work fine because there would be no delay for connecting. Steps to reproduce the behavior: if I restart freshclam and then clamav, both services work fine until reboot. clamav and freshclam service should be running, or at least try to restart automatically. Please run and paste the result.
Looks like we didn't follow the upstream units enough:
Change:
example = "demo.wireguard.io:12913"; type = with types; nullOr str; description = ''Endpoint IP or hostname of the peer, followed by a colon, <del> and then a port number of the peer.''; </del> <ins> and then a port number of the peer. Warning for endpoints with changing IPs: The WireGuard kernel side cannot perform DNS resolution. Thus DNS resolution is done once by the <literal>wg</literal> userspace utility, when setting up WireGuard. Consequently, if the IP address behind the name changes, WireGuard will not notice. This is especially common for dynamic-DNS setups, but also applies to any other DNS-based setup. If you do not use IP endpoints, you likely want to set <option>networking.wireguard.dynamicEndpointRefreshSeconds</option> to refresh the IPs periodically. ''; }; dynamicEndpointRefreshSeconds = mkOption { default = 0; example = 5; type = with types; int; description = '' Periodically re-execute the <literal>wg</literal> utility every this many seconds in order to let WireGuard notice DNS / hostname changes. Setting this to <literal>0</literal> disables periodic reexecution. ''; </ins> }; persistentKeepalive = mkOption {

Discussion:
On NixOS 20.09, steps to reproduce the behavior: setting up wireguard, change to another port still shows the old port:
This seems to be fixed by my PR
Change:
with import common/ec2.nix { inherit makeTest pkgs; }; let <del> image = </del> <ins> imageCfg = </ins> (import ../lib/eval-config.nix { inherit system; modules = [

Discussion:
Describe the bug On current master (), the ec2 tests don't work: Expected behavior They should work in order to be portable to python, see CCing contributors who wrote/touched this code: