jiebi/CodeConvo huggingface dataset:
Change:
</listitem> <listitem> <para> <ins> <link xlink:href="https://maddy.email">maddy</link>, a composable all-in-one mail server. Available as <link xlink:href="options.html#opt-services.maddy.enable">services.maddy</link>. </para> </listitem> <listitem> <para> </ins> <link xlink:href="https://sr.ht">sourcehut</link>, a collection of tools useful for software development. Available as

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:
}; services.postfix.masterConfig = { <del> smtp_inet = { name = "smtp"; type = "inet"; private = false; command = "smtpd"; }; </del> pickup = { private = false; wakeup = 60;

Discussion:
The postfix module keeps adding a smtp entry to even though I have set . I would like to overwrite the default smtp service in , but postfix uses the last entry in the file (which is always the default one). To Reproduce Steps to reproduce the behavior: postfix: smtp : in Expected behavior following line should be excluded from Additional context Here's the resulting file with double entries: Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- it looks like you wrote this part a while ago. Have you heard of this issue? Metadata Maintainer information:
I think, I fixed this a long time ago in my private nixpkgs repository and never upstreamed the change. I'll make a pull request.
Issue seems to be fixed. Thanks for the quick help!
Change:
stdenv.mkDerivation rec { name = "simplenote-${pkgver}"; <del> pkgver = "1.0.6"; </del> <ins> pkgver = "1.1.3"; </ins> src = fetchurl { <del> url = "https://github.com/Automattic/simplenote-electron/releases/download/v${pkgver}/Simplenote-linux-x64.${pkgver}.tar.gz"; sha256 = "18wj880iw92yd57w781dqaj7iv9j3bqhyh2cbikqrl4m5w9xkla8"; </del> <ins> url = "https://github.com/Automattic/simplenote-electron/releases/download/v${pkgver}/Simplenote-linux-${pkgver}.tar.gz"; sha256 = "1z92yyjmg3bgfqfdpnysf98h9hhhnqzdqqigwlmdmn3d7fy49kcf"; </ins> }; buildCommand = let

Discussion:
Unstable () and master ().
() broke spotify cc
Turned out to be easy to fix
Change:
}; nativeBuildInputs = [ qt5.wrapQtAppsHook ]; <del> buildInputs = [ hackrf rtl-sdr airspy limesuite libiio libbladeRF qt5.qtwayland ] ++ lib.optional USRPSupport uhd; </del> <ins> buildInputs = [ hackrf rtl-sdr airspy limesuite libiio libbladeRF ] ++ lib.optional USRPSupport uhd ++ lib.optional stdenv.hostPlatform.isLinux qt5.qtwayland; </ins> propagatedBuildInputs = with python3Packages; [ pyqt5 numpy psutil cython pyzmq pyaudio setuptools

Discussion:
Steps to reproduce the behavior: (from this template), triggering nix-darwin to be rebuilt qtwayland (I assume as part of darwin). Here is the output of : Add any other context about the problem here. <!-- 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]:
qtwayland should not be built on Darwin, whatever package is doing that needs to be fixed.
(Shouldn't you be running into an error about your platform not being marked supported by ?) Your issue is: dependency on without limiting it to Linux. Opened to make it a Linux-only dependency.
We should probably mark qtwayland broken on Darwin explicitly, yeah.
And it has been marked as broken there in on all supported channels.
Ahh - you're right - it is probably the urh package then. I really love how attentive and helpful people are with fixing things in nixpkgs =). It was just confusing because I saw this line in the output: Hence I just assumed it was nix-darwin. But is that a bit of a red herring? (I'm a nix newbie, so always keen to learn) Also - is there any way to manually apply patches/PRs like Or should I just wait for it to get merged, and then pushed out to the Nixpkgs unstable channel? (I was using to give me an idea of when a commit might be available - I get the impression that there is some gap between when it's actually merged, versus available in nixpkgs).
Change:
{ lib, stdenv, fetchgit, curl, gnunet, jansson, libgcrypt, libmicrohttpd , qrencode, libsodium, libtool, libunistring, pkg-config, postgresql <del> , autoreconfHook, python39, recutils, wget, jq, gettext, texinfo </del> <ins> , autoreconfHook, python3, recutils, wget, jq, gettext, texinfo </ins> }: let <del> version = "0.9.3"; </del> <ins> version = "0.10.1"; </ins> taler-wallet-core = fetchgit { url = "https://git.taler.net/wallet-core.git"; rev = "v${version}"; <del> sha256 = "sha256-oL8vi8gxPjKxRpioMs0GLvkzlTkrm1kyvhsXOgrtvVQ="; </del> <ins> hash = "sha256-sgiJd1snN9JDqS7IUeORKL60Gcm7XwL/JCX3sNRDTdY="; </ins> }; taler-exchange = stdenv.mkDerivation {

Discussion:
Package name: gnunet Latest released version: 0.21.0 Current version on the unstable channel: 0.20.0 Current version on the stable/release channel: 0.20.0 Notify maintainers Changelog: Note for maintainers: Please tag this issue in your PR. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
hash = "sha256-o6OaXOXLykTUuF/taKnEhZRV04/3nlU5aNY05ANr1Ko="; }; <del> nativeBuildInputs = [ makeWrapper gobject-introspection ]; </del> <ins> nativeBuildInputs = [ wrapGAppsHook gobject-introspection ]; </ins> buildInputs = [ perl clamav ]; propagatedBuildInputs = with perlPackages; [ Glib LWP LWPProtocolHttps TextCSV JSON LocaleGettext Gtk3 ];

Discussion:
When executing with , it complains that . Maybe the package needs to be wrapped with some environment variables set or patched against hard-coding or something. Steps to reproduce the behavior: ClamTk runs with . ! ]() Add any other context about the problem here. <!-- 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.
I can't seem to reproduce this. Have run both on nixos and nix on another linux. Can you give me some more info? Does the program work and run correctly? Is it missing any icons (screenshot?). What desktop are you running? Many thanks.
It exits with exit status 2 right after the command being invoked inside the terminal emulator and the error message printed out. No window is shown. The desktop environment I use is LxQt, which inherently doesn't come with the KDE breeze icons. The screenshot and the Asciinema cast is updated into the issue description.
I switched my DE over to LxQt and everything worked for me. Basically the error is between the program logic (it shouldn't crash if it can't find icon files) and your DE set-up (it should provide the correct icon files). It's not a packaging error as far as I can tell. So you could try either: 1. messing around with your DE settings, 2. trying another DE and / or 3. filing a bug report upstream to clamtk. !
p.s. I wonder if this could just be fixed by installing some icons? You could try installing and / or on your system and see if that helps.
Change:
sha256 = "fbd92c067c16111174a1286bfb253660f1e564e5146b39eeed1133315cf2c2cf"; }; <del> buildInputs = [ pytest ]; </del> <ins> buildInputs = [ pytest ] ++ stdenv.lib.optionals isPy35 [ async_generator ]; </ins> # No tests in archive doCheck = false;

Discussion:
The derivation is available but cannot be built. I get the following error : I get the original package to work in a nix-shell with the following derivation:
I commented in the PR to address this issue. It is due to a circular dependency that and have on each other for testing. You may run into more similar issues since python 35 it not heavily tested in the community right now. If you can use 36 or 37. 37 will be the default soon.
Thanks!
Change:
<ins> { stdenv, buildGoPackage, fetchurl, fetchFromGitHub, go-bindata }: let version = "1.4.10"; # TODO: must build the extension instead of downloading it. But since it's # literally an asset that is indifferent regardless of the platform, this # might be just enough. webext = fetchurl { url = "https://github.com/browsh-org/browsh/releases/download/v${version}/browsh-${version}-an.fx.xpi"; sha256 = "0rgwzv1qahqy52q7zz4dklnwx7w4x3gj92ka8n0ypgf9fjjnmqas"; }; in buildGoPackage rec { inherit version; name = "browsh-${version}"; goPackagePath = "browsh"; src = fetchFromGitHub { owner = "browsh-org"; repo = "browsh"; rev = "v${version}"; sha256 = "0lvb20zziknlbgy509ccpvlc21sqjc53xar26blmb6sdl6yqkj0w"; }; buildInputs = [ go-bindata ]; # embed the web extension in a go file and place it where it's supposed to # be. See # https://github.com/browsh-org/browsh/blob/9abc3aaa3f575ca6ec9a483408d9fdfcf76300fa/interfacer/contrib/xpi2bin.sh preBuild = '' xpiprefix="$(mktemp -d)" cp "${webext}" "$xpiprefix/browsh.xpi" go-bindata  -prefix "$xpiprefix"  -pkg browsh  -o "$NIX_BUILD_TOP/go/src/${goPackagePath}/interfacer/src/browsh/webextension.go"  "$xpiprefix/browsh.xpi" sed  -e 's:Asset("/browsh.xpi"):Asset("browsh.xpi"):g'  -i "$NIX_BUILD_TOP/go/src/${goPackagePath}/interfacer/src/browsh/firefox.go" ''; postBuild = '' mv "$NIX_BUILD_TOP/go/bin/src" "$NIX_BUILD_TOP/go/bin/browsh" ''; goDeps = ./deps.nix; meta = with stdenv.lib; { description = "A fully-modern text-based browser, rendering to TTY and browsers"; homepage = https://www.brow.sh/; maintainers = [ maintainers.kalbasit ]; license = stdenv.lib.licenses.lgpl21; platforms = stdenv.lib.platforms.linux ++ stdenv.lib.platforms.darwin; }; } </ins>

Discussion:
isn't yet available in Nixpkgs, which is a bummer since I wanted to check it out :). We'll probably need to go the "source" route (preferable anyway) since the "static binary" immediately starts looking for a dynamic linker/loader, here's a quick strace: Suggesting it's an unpacker of dynamically linked executables or something? Haven't investigated beyond the above :). Source looks like it's someone else's cup-of-tea :3.
Bump! I want to push this request!
er, re-bump? I'm interested in this too, would do it myself but I'm no patching ninja :)
You can probably use to build this as a derivation, you do not need to use the binary release. See the package being built in as an example of how to build it. I can probably package it up this weekend if no one has already done that.
I'd love that, largely because I can't find any docs on anywhere
sure I'll work on it today.
please try and let me know if it works for you.
Change:
wayland xcbutilkeysyms xcbutilwm <ins> libsForQt5.qt5.qtbase libsForQt5.qt5.qtwayland </ins> ]; cmakeFlags = [

Discussion:
Add vulkan-tools-lunarg to a devshell and see that the only executable it provides is vkvia. It should also at least build and provice vkconfig Steps to reproduce the behavior: vulkan-tools-lunarg to a devshell to execute vkconfig to debug your vulkan application that it is not found in your path I expected vkconfig to be built and included in the vulkan-tools-lunarg derivation
Change:
configureFlags = drv.configureFlags or [] ++ ["-fembed_data_files"]; buildDepends = drv.buildDepends or [] ++ [haskellPackages.file-embed]; buildTools = (drv.buildTools or []) ++ [ removeReferencesTo ]; <ins> patches = (drv.patches or []) ++ [ # Add xmlns to top-level tags in Docbook, required for nixpkgs manual. # https://github.com/jgm/pandoc/pull/6923 (fetchpatch { url = "https://github.com/jgm/pandoc/commit/6f35600204132c5a0907bb7cccb2e10ffb27506a.patch"; sha256 = "gRUqc4YG4lZdCZn21fPmlcrFyZ3/VlDx71lU8GMuGSs="; }) # Generate admonitions in DocBook, required for nixpkgs manual. # https://github.com/jgm/pandoc/pull/6922 (fetchpatch { url = "https://github.com/jgm/pandoc/commit/dc6856530c2cb6ca58ed82721ab895b86cfe0c1c.patch"; sha256 = "EdsUDlHzsfRscXBR4EP2Z5ZEz+NfrmFHnV7c1hJczio="; }) # Use correct id attributes in DocBook, required for nixpkgs manual. (fetchpatch { url = "https://github.com/jgm/pandoc/commit/16ef87745702f69d5aa948fbe6d2101577dee8f4.patch"; sha256 = "WyWTqrO6hGsMgJ7o7QL1BNvhkm0yIO1XJOcfPBDy6ag="; }) # Allow using admonition titles from Markdown in DocBook. (fetchpatch { url = "https://github.com/jgm/pandoc/commit/70c7c5703afcbd1cbf2a80c2be515e038abcd419.patch"; sha256 = "2kHQ1qy/UdDi/chwCBvMjAPA/XFH42vWFCjR46Jgt6M="; }) ]; </ins> })).overrideAttrs (drv: { # These libraries are still referenced, because they generate

Discussion:
This issue tracks the conversion of from Docbook to CommonMark per . If you intend to work on this conversion, please comment below! in this issue that you intend to work on it. (Please also post if you stop working on it) a new branch of nixpkgs master. : change to . the contents from Docbook to . Follow . Use existing sections for inspiration. the contents from Docbook to . Use existing sections for inspiration. from the folder to build the manual. the manual on your computer at after running from folder: it looks good, submit a PR and reference this issue.
I can try to tackle this, hopefully we will be able to figure out how to make it functionally equivalent, even if semantic equivalence is out.
I want to finish first to avoid conflicts, though.
This was merged now.
Change:
<ins> { buildGoModule, fetchFromGitHub, installShellFiles, lib, nix-update-script, stdenv, steampipe, testers, }: buildGoModule rec { pname = "steampipe"; version = "0.22.1"; src = fetchFromGitHub { owner = "turbot"; repo = "steampipe"; rev = "v${version}"; hash = "sha256-Oz1T9koeXnmHc5oru1apUtmhhvKi/gAtg/Hb7HKkkP0="; }; vendorHash = "sha256-U0BeGCRLjL56ZmVKcKqrrPTCXpShJzJq5/wnXDKax6g="; proxyVendor = true; patchPhase = '' runHook prePatch # Patch test that relies on looking up homedir in user struct to prefer ~ substituteInPlace pkg/steampipeconfig/shared_test.go  --replace 'filehelpers "github.com/turbot/go-kit/files"' ""  --replace 'filepaths.SteampipeDir, _ = filehelpers.Tildefy("~/.steampipe")' 'filepaths.SteampipeDir = "~/.steampipe"'; runHook postPatch ''; nativeBuildInputs = [ installShellFiles ]; ldflags = [ "-s" "-w" ]; # panic: could not create backups directory: mkdir /var/empty/.steampipe: operation not permitted doCheck = !stdenv.isDarwin; postInstall = '' INSTALL_DIR=$(mktemp -d) installShellCompletion --cmd steampipe  --bash <($out/bin/steampipe --install-dir $INSTALL_DIR completion bash)  --fish <($out/bin/steampipe --install-dir $INSTALL_DIR completion fish)  --zsh <($out/bin/steampipe --install-dir $INSTALL_DIR completion zsh) ''; passthru = { tests.version = testers.testVersion { command = "${lib.getExe steampipe} --version"; package = steampipe; version = "v${version}"; }; updateScript = nix-update-script { }; }; meta = with lib; { homepage = "https://steampipe.io/"; description = "select * from cloud;"; license = licenses.agpl3Only; mainProgram = "steampipe"; maintainers = with maintainers; [ hardselius ]; changelog = "https://github.com/turbot/steampipe/blob/v${version}/CHANGELOG.md"; }; } </ins>

Discussion:
Steps to reproduce the behavior: steampipe Occurred after a and a . <!-- 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]:
It seems that the is invalid: I’ll open a PR to fix this.
The same problem happened to the package last week: They merged the r-ryantm auto-update PR for hugo package, and then the build fails on Hydra with an invalid . Explaination: has been updated to (2 weeks ago) targeting the branch: -ryantm opened the auto-update PR for package compiled with : the staging-next PR was merged with as default: the steampipe auto-update PR was merged with an outdated because Go has been upgraded to 1.22 and the being outdated.
My fault, sorry. Just a question for the explanation, Should it then be supposed that a large proportion of Go packages have hash mismatches on master, but are not detected because go-modules are fixed-output derivations?
No problem, thanks for the help :) I'm not sure if this is already the case on master, but what I do know is that this has happened to other packages like , and . All PRs (not just those of the r-ryantm bot), created before this merge on staging-next (for Go 1.21) and merged now without having a updated for Go 1.22 are potentially impacted. Because :
Change:
] ++ lib.optionals (config.overlay.upperdir != null) [ "upperdir=${upperdir}" "workdir=${workdir}" <del> ] ++ (map (s: "x-systemd.requires-mounts-for=${s}") lowerdir); </del> <ins> ]; </ins> }; };

Discussion:
systemd doesn't respect the option for file systems. Usually this is ok because systemd will mount file systems in the correct topological ordering. The option is useful because it allows you to express dependencies on e.g. the file systems that an FS's lower/upper/work directories exist on. This test should hang forever. Instead, it exits cleanly. The service never exits, so is never mounted, and therefore should never be mounted. So the test should hang. This is also a problem for systemd stage 1, but it's worse because we also have to account for the prefix. We can fix this by adding options for every dependency, and prefixing for the systemd stage 1 file systems.
Do we even need the option? I don't think it's particularly useful. The overlay also shouldn't be a concern since anymore.
Well, currently literally only does anything in scripted stage 1. In stage 2 and in systemd stage 1, you have to use , which is what the stuff does. That's fine, but it's an incompatibility between scripted and systemd stage 1. So we need to either deprecate it or implement it, and it's really easy to implement (I just need to fixup ). It's a handy convenience for people I guess, though far from a necessary one.
Change:
<ins> { lib , fetchFromGitHub , rustPlatform }: rustPlatform.buildRustPackage rec { pname = "sad"; version = "0.4.14"; src = fetchFromGitHub { owner = "ms-jpq"; repo = pname; rev = "v${version}"; sha256 = "03b6qxkn8sqv06gs4p6wg02arz0n9llc3z92zhfd5ipz8han83fd"; }; cargoSha256 = "13nkd4354siy8pr2032bxz2z5x8b378mccq6pnm71cpl9dl6w4ad"; meta = with lib; { description = "CLI tool to search and replace"; homepage = "https://github.com/ms-jpq/sad"; license = licenses.mit; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
Project description describe the project a little is a live previewer that shows previews with fzf I've actually never used it but it looks interesting and would like to give it a try Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin
thanks !
Change:
<del> Add the -m option to man's command line to augment the list of paths searched by man. The string "OUT" must be substituted with chawan's $out path after patching. </del> <ins> Add the -m option to man's command line to augment the list of paths searched by man. </ins> The required -m option is only available in the mandoc implementation. <del> --- a/adapter/protocol/man +++ b/adapter/protocol/man @@ -75,7 +75,7 @@ EOF </del> <ins> --- a/adapter/protocol/man.nim +++ b/adapter/protocol/man.nim @@ -264,7 +264,7 @@ proc myOpen(cmd: string): tuple[ofile, efile: File] = </ins> <del> $section =~ s:([^-w200-377.,])::g; $man =~ s:([^-w200-377.,])::g; -  open(F, "GROFF_NO_SGR=1 MAN_KEEP_FORMATTING=1 $MAN $section $man 2> /dev/null |"); +  open(F, "GROFF_NO_SGR=1 MAN_KEEP_FORMATTING=1 $MAN -m OUT/share/man $section $man 2> /dev/null |"); } $ok = 0; </del> <ins> proc doMan(man, keyword, section: string) = let sectionOpt = if section == "": "" else: ' ' & quoteShellPosix(section) let cmd = "MANCOLOR=1 GROFF_NO_SGR=1 MAN_KEEP_FORMATTING=1 " & -    man & sectionOpt & ' ' & quoteShellPosix(keyword) +    man & sectionOpt & " -m @out@ " & quoteShellPosix(keyword) let (ofile, efile) = myOpen(cmd) if ofile == nil: </ins>

Discussion:
Steps to reproduce the behavior: chawan () Related to Add any other context about the problem here. <!-- 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]:
Change:
phonetisaurus = callPackage ../development/libraries/phonetisaurus {}; <del> duti = callPackage ../os-specific/darwin/duti {}; </del> <ins> duti = callPackage ../os-specific/darwin/duti { inherit (darwin.apple_sdk.frameworks) ApplicationServices; }; </ins> dnstracer = callPackage ../tools/networking/dnstracer { inherit (darwin) libresolv;

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.5.4pre (rev ) desired version: 1.5.5pre (needs at least ) maintainers: The current version of duti fails to compile with: <details<summaryCompilation error with current version</summary</detailsNaively upgrading to the version linked above fails too, I believe that's because the SDK is too old (it uses 10.12.16?): <details<summaryCompilation error with new version</summary</details
Should be fixed with
Change:
{ stdenv, lib, fetchFromGitHub, cmake, docbook_xsl, libxslt <del> , openssl, libuuid, libwebsockets, c-ares, libuv </del> <ins> , openssl, libuuid, libwebsockets_3_1, c-ares, libuv </ins> , systemd ? null, withSystemd ? stdenv.isLinux }: stdenv.mkDerivation rec { pname = "mosquitto"; <del> version = "1.6.4"; </del> <ins> version = "1.6.5"; </ins> src = fetchFromGitHub { owner  = "eclipse"; repo   = "mosquitto"; rev    = "v${version}"; <del> sha256 = "1kr1dgc4nzhyg3rzymbv4rka3rpb30rwsy6binb7apnw3n3ff58l"; </del> <ins> sha256 = "0scgsi3rvs9s8vxv4r7d5d9ixbsfg4dwnjcy6zxwdz9dfn8qnngj"; </ins> }; postPatch = ''

Discussion:
libwebsockets 3.2.0 changed its behaviour in a way that breaks all versions of Mosquitto that use websockets, resulting in incoming connections being intermittent and very slow. It is fixed in their repository and will be in the next release presumably, but for now 3.2.0 is no good. If Mosquitto is the only other package using libwebsockets, I would suggest downgrading to 3.1.0, which behaves fine. Mosquitto 1.6.5, which should be released today, will refuse to compile with libwebsockets 3.2.0.
cc
mosquitto 1.6.5 fixes it - just haven't packaged it yet.
Mosquitto 1.6.5 does not fix this. There is a changelog entry which was written prior to this issue that is probably why you think it does have the fix. Sorry about that, I changed the changelog on the website post but not in the repo. The only fix for this is in libwebsockets itself.
it's pretty awesome having upstream providing proactive updates like this - much appreciated!