jiebi/CodeConvo huggingface dataset:
Change:
owner = "Phosh"; repo = pname; rev = "v${version}"; <del> sha256 = "sha256-qd1ZETM2/AjU5nKQIqh0Q+SboLNr+NncvSHgLv2S3KI="; </del> <ins> sha256 = "sha256-oUZtJzclVRSbLG3flF3ryLuvp1kPUtYNsmCG0csSC2A="; </ins> }; nativeBuildInputs = [

Discussion:
We've temporarily introduced as part of to avoid breaking some reverse dependencies. The affected attributes should switch to when possible (usually a new upstream release). There's no hurry but let's use this issue to track the current progress. : [x] phoc [x] cage (): [x] hikari ( and ): [x] waybox (): [x] wayfire (supported since ): [x] wio (, turns out the pending patches on the ML should fix the build with wlroots 0.13): [x] cagebreak ( and additional commits): () : [x] sway: [x] hikari (downstream patches: ): [x] wio (, send via git-send-email to ):
cage: was just merged, do we want to: until a next release it using the now-merged patch the latest version from master
I think waiting for the next release is the best option for now (we're in no hurry). For some other packages that are already based on commits instead of releases there's no need to wait if the package maintainers deem a newer version stable (in that case I'd leave it up to the package maintainers).
(though I hope that doesn't have the same problems as cage)
(kinda flew under the radar for me, but it happened!)
Don't we want to split this issue up per version? It seems like we're always gonna have a handful of wlroots versions around, would be nice if we could close those issues individually instead of having one perpetually open issue
I thought about that too but I was hoping we can close this before the next wlroots release. is the main blocker, should be fairly easy to drop (I'm waiting for patches and, if necessary, I might be able to patch again but I might also mark it as broken instead (until there's a maintained fork) as I don't intend to do that every release).
I have merely made a new fork for wio outside SourceHut, but me myself do not plan to maintain it alone.
in that case we should eventually drop it from Nixpkgs, at least IMO. I had some time yesterday so I've sent you a patch for wlroots 0.14 (, tested with ).
I have patched it on my particular fork
Phoc 0.11.0 was released targeting wlroots 0.14.0 (), so this can finally be closed.
Change:
description = "Web-Scale Blockchain for fast, secure, scalable, decentralized apps and marketplaces. "; homepage = "https://solana.com"; license = licenses.asl20; <del> maintainers = with maintainers; [ netfox happysalada ]; </del> <ins> maintainers = with maintainers; [ netfox happysalada aikooo7 ]; </ins> platforms = platforms.unix; };

Discussion:
Package name: solana-cli Latest released version: 1.16.27 <!-- Search your package here: --- Current version on the unstable channel: 1.14.23 Current version on the stable/release channel: 1.14.23 <!-- 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]:
Hello I was able make the building script work so solana-cli is updated to 1.16.27 expect solana has bug in a which doesn't let me compile. The issue was already reported back back in 22 november 2023: solana-labs/solana So until is fixed I can't do anything more, as soon as it is fixed I will post my pr
Thanks , did you manage to build it for the current version? () On the master of nixpkgs I couldn't even build the existing version of Solana due a rocksdb issue I also found this commit on homebrew PRs. Seems like they patched this part in order to make the build work:
Hello I didn't test it and I don't think I need since I made it able to compile 1.16.27 I appreciate the citation, with the patch used by them I was able to fix it, appreciate your help
Change:
<ins> diff --git a/scripts/msmtpq/msmtpq b/scripts/msmtpq/msmtpq index bcb384e..9622e47 100755 --- a/scripts/msmtpq/msmtpq +++ b/scripts/msmtpq/msmtpq @@ -60,8 +60,6 @@ err() { dsp '' "$@" '' ; exit 1 ; } ##   export the location of the msmtp executable before running this script  (no quotes !!) ##   e.g. ( export MSMTP=/path/to/msmtp ) MSMTP="${MSMTP:-msmtp}" -"$MSMTP" --version >/dev/null 2>&1 ||  -  log_later -e 1 "msmtpq : can't run the msmtp executable [ $MSMTP ]"   # if not found - complain ; quit ## ## set the queue var to the location of the msmtp queue directory ##   if the queue dir doesn't yet exist, create it (0700) </ins>

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: msmtp <!-- 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.8.22 desired version: 1.8.23 <!-- 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:
''; meta = with stdenv.lib; { <del> homepage = https://github.com/alejandrogomez/turses; </del> <ins> homepage = https://github.com/louipc/turses; </ins> description = "A Twitter client for the console"; license = licenses.gpl3; maintainers = with maintainers; [ garbas ];

Discussion:
If you start without a config file, then it starts fine. But when later you exit it and start again, then it crashes with: This error was fixed in but it's not part of tool official releases. (Note that the original upstream repo no longer exists; so we should switch to fork of it. -env -f . -i python3.6-turses it with "q". Please run and paste the results.
Change:
<ins> { lib , stdenvNoCC , fetchurl , libnotify , nss , gtk3 , fetchFromGitHub , makeDesktopItem , itch-setup , runtimeShell }: stdenvNoCC.mkDerivation rec{ pname = "itch"; version = "25.5.1"; src = fetchFromGitHub { owner = "itchio"; repo = pname; rev = "v${version}"; hash = "sha256-Pi3l3uK4kr+N3p7fGQuqckYIzycRqJHDVX00reoSbp4="; }; desktopItems = [ (makeDesktopItem { name = pname; exec = pname; icon = pname; desktopName = pname; mimeType = "x-scheme-handler/itchio;x-scheme-handler/itch"; comment = "Install and play itch.io games easily"; extraDesktopEntries = { TryExec = "itch %U"; Categories = "Game;"; }; }) ]; itchBin = '' #!${runtimeShell} exec ${itch-setup}/bin/itch-setup --prefer-launch -- "$@" ''; passAsFile = [ "itchBin" ]; # as taken from https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=itch installPhase = '' install -Dm0777 $itchBinPath $out/bin/itch for icon in release/images/itch-icons/icon*.png do iconsize="''${icon#release/images/itch-icons/icon}" iconsize="''${iconsize%.png}" icondir="$out/share/icons/hicolor/''${iconsize}x''${iconsize}/apps/" install -Dm644 "$icon" "$icondir/itch.png" done ''; meta = with lib; { description = "The best way to play itch.io games"; homepage = "https://github.com/itchio/itch"; license = licenses.mit; platforms = platforms.linux; maintainers = with maintainers; [ pasqui23 ]; }; } </ins>

Discussion:
Project description The app is a client for the indie game store Metadata homepage URL: source URL: license: mit platforms: linux, darwin
Maybe helpful: Also pinging since he worked on that if i remember right.
I think that one just downloads a precompiled release from My first attempt of packaging this was by following and just add to . That did not work however because the app does not exist on npmjs as far as I can see. According to it should just be installed by a and . But I cannot find any documentation about what the nixpkgs approach would be for this.
Correct, it's basically just two games along with that fetches releases, so it's unrelated to this packaging request.
I marked this as stale due to inactivity. &rarr;
Having the itch game launcher on nix would be a huge win, hope this thread gets more attention. As the package is currently marked as broken :(
Change:
{ stdenv, fetchurl, autoreconfHook, pkgconfig, libzen, libmediainfo, zlib }: stdenv.mkDerivation rec { <del> version = "20.08"; </del> <ins> version = "20.09"; </ins> pname = "mediainfo"; src = fetchurl { url = "https://mediaarea.net/download/source/mediainfo/${version}/mediainfo_${version}.tar.xz"; <del> sha256 = "1baf2dj5s3g1x4ssqli1b2r1203syk42m09zhp36qcinmfixv11l"; </del> <ins> sha256 = "0rqg9z7s5bk7vlvjrs4gackzg7ib05a0dffi2ihsjf5a7kw7wcir"; </ins> }; nativeBuildInputs = [ autoreconfHook pkgconfig ];

Discussion:
, CVSSv3=7.8 (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives. Cc
Remediated - thus closing.
Change:
# Secure the services defaultServiceConfig = { <del> TemporaryFileSystem = "/:ro"; BindReadOnlyPaths = [ "/nix/store" "-/etc/resolv.conf" "-/etc/nsswitch.conf" "-/etc/hosts" "-/etc/localtime" "-/etc/ssl/certs" "-/etc/static/ssl/certs" "-/run/postgresql" ] ++ (optional enableRedis redisServer.unixSocket); BindPaths = [ </del> <ins> ReadWritePaths = [ </ins> cfg.consumptionDir cfg.dataDir cfg.mediaDir

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:
${python.interpreter} setup.py install --skip-build --prefix=$out ''; <del> passthru = { inherit wxGTK; }; </del> <ins> passthru = { wxWidgets = if stdenv.isDarwin then wxmac else wxGTK; }; </ins> meta = {

Discussion:
Describe the bug wxPython40, , does not build there likely because it uses wxGTK rather than this prevents kicad from being built on darwin To Reproduce Steps to reproduce the behavior: darwin, Expected behavior wxPython40 to build on darwin and be usable by kicad there Additional context i maintain the kicad package and Notify maintainers while there are no listed maintainers for this package it was initially contributed by (if you already investigated after the kicad PR ping, nothing relevant changed since) and has a fair amount of contributions by Maintainer information:
Hi I don't have/use mac but happy to answer any wxPython questions as I can
I'm experiencing the same issue with Linux, using .
likely a different issue. Stacktrace? What nixpkgs version / commit?
The as of this writing. Here's the output I'm seeing. <details<summarybuild log</summary</detailsIt looks like pkg-config is giving an old version of GTK+?
please use your failure seems the same as which i closed because it's fixed in the branch by and i can confirm at least starts building there (it's still going...) i'm not sure when this fix will get to ...
nice! didn't know about the details tag. Ok yeah that looks like my issue, thanks for pointing me in that direction.
I can reproduce this on 10.14.6. My best take so far was to use and adapt other Darwin requirements. <details<summarydiff against master</summary</detailsUnfortunately it does not build with the same errors as for the .
Bumped to 3.0.5.1, to its , and it builds! was set, but no dependency specified. That's what caused the missing symbols. <details<summaryworking diff</summary</detailsI'm not even sure why this works at all. claims they build from a submodule, but obviously in this setup we take whatever is supplied through . To be pedantic, 4.0.7 is supposed use some specific instead of a release, as you can . That commit is after* 3.0.4 and shortly before 3.0.5. I only skimmed the , but it sounds and looks like backwards-compatible bug fixes. Opinions on how to proceed?

If we follow upstream and choose the intermediate revision, what to specify as the package version?
i've kinda given up on stuff, at least until the next release which i hope will either be built based on a release or be compatible with the latest release (i have no reason to believe this would be the case though) if you have a diff that fixes a package, i recommend you make a PR 4.0.7 seems to work with the 3.0.4, it seems reasonable to assume the same would be true for 3.0.4
Change:
in rustPlatform.buildRustPackage rec { pname = "rio"; <del> version = "0.0.18"; </del> <ins> version = "0.0.19"; </ins> src = fetchFromGitHub { owner = "raphamorim"; repo = "rio"; rev = "v${version}"; <del> hash = "sha256-/zqJQQLpwYil4BBZJDMMC8JRAEG0vGeG0dCDzLzPk/o="; </del> <ins> hash = "sha256-N7eHIyp2imkMUVwiOCameOROoaDJ7g+zNKdIB2aGZy0="; </ins> }; <del> cargoHash = "sha256-jev4fMwCygVzvrkI1nSE5tx59nGqNKQUHCNHvkr9R90="; </del> <ins> cargoHash = "sha256-XD+/DaaJEJ9jHZITTUma/wfsbduPUTc/SralPOx46Yo="; </ins> nativeBuildInputs = [ autoPatchelfHook

Discussion:
Package name: Rio Latest released version: v0.0.19 <!-- Search your package here: --- Current version on the unstable channel: v0.018 Current version on the stable/release channel: N/A <!-- 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:
sourceVersion = { major = "3"; minor = "12"; <del> patch = "2"; </del> <ins> patch = "3"; </ins> suffix = ""; }; <del> hash = "sha256-vigRLayBPSBTVFwUvxOhZAGiGHfxpp626l2ExKDz2HA="; </del> <ins> hash = "sha256-Vr/vH9/BIhzmcg5DpmHj60F4XdkUzplpjYx4lq9L2qE="; </ins> inherit (darwin) configd; inherit passthruFun; };

Discussion:
Package name: python3, python312 Latest released version: 3.11.9, 3.12.3 <!-- Search your package here: --- Current version on the unstable channel: 3.11.8, 3.12.2 Current version on the stable/release channel: 3.11.8, 3.12.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]:
You could have found the PR for 3.11.9.
I assume python3 and python3.12 updated at same time because updated at same time. Thank you for your message, I'll check two time when I create issue.
fixed issue
Change:
owner = "darrenldl"; repo = "docfd"; rev = version; <del> hash = "sha256-pJ5LlOfC+9NRfY7ng9LAxEnjr+mtJmhRNTo9Im6Lkbo="; </del> <ins> hash = "sha256-fgwUXRZ6k5i3XLxXpjbrl0TJZMT+NkGXf7KNwRgi+q8="; </ins> }; <del> nativeBuildInputs = [ python3 dune_3 ]; </del> <ins> nativeBuildInputs = [ python3 dune_3 makeWrapper ]; </ins> buildInputs = with ocamlPackages; [ cmdliner containers-data

Discussion:
Steps to reproduce the behavior: on x8664-darwin Package is a dependency of . Builds fine on linux and aarch64-darwin, just fails on x86_64-darwin. <!-- 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 submit a patch, I will review it, but I don’t own any Darwin hardware to test…
Pinging to see if anyone can help on this issue as it's outside my area of expertise. Otherwise will mark which depends on this as broken for darwin x86_64. Many thanks!
Can test later, but it looks like there is a workaround for this exact error at
Thanks. I tried that flag earlier, which turns the error into a warning and allows to build (with warnings). But then when I try and build which depends on this I get linker errors,
and were in 11.0. It should use to override the stdenv to use the 11.0 SDK with an 11.0 deployment target. Edit: It uses , so probably something like (untested):
Many thanks, that worked! Much appreciated.

nix shell nixpkgs#docfd Wanted to try out but it failed to build. I noticed the package is not on the . Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi thanks for the report. I currently have a PR for version 4.0.0, but this same build error occurs there too, so it's unrelated to version. Strangely docfd builds fine on aarch64-darwin. The problem is with x8664-darwin, and specifically with the ocaml dependency which fails to build as your error message shows. I'm going to open an issue for that an ping the maintainer.
Change:
python3.pkgs.buildPythonApplication rec { pname = "calibre-web"; <del> version = "0.6.17"; </del> <ins> version = "0.6.18"; </ins> src = fetchFromGitHub { owner = "janeczku"; repo = "calibre-web"; rev = version; <del> sha256 = "sha256-K2va9as+z00txpg/0fR89+kpMzpQSiSSIV489NDs8Bs="; </del> <ins> sha256 = "sha256-KjmpFetNhNM5tL34e/Pn1i3hc86JZglubSMsHZWu198="; </ins> }; propagatedBuildInputs = with python3Packages; [ <ins> advocate </ins> backports_abc flask-babel flask_login

Discussion:
, CVSSv3=9.8 (nixos-21.11) CVSSv3=9.8 (nixos-21.11) CVSSv3=8.8 (nixos-21.11) CVSSv3=6.5 (nixos-21.11) CVSSv3=6.1 (nixos-21.11) CVSSv3=5.4 (nixos-21.11) calibre-web is vulnerable to Business Logic Errors Server-Side Request Forgery (SSRF) in Pypi calibreweb prior to 0.6.16. calibre-web is vulnerable to Cross-Site Request Forgery (CSRF) Improper Access Control in Pypi calibreweb prior to 0.6.16. Cross-site Scripting (XSS) - Reflected in Pypi calibreweb prior to 0.6.16. calibre-web is vulnerable to Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') Scanned versions: nixos-21.11: . Cc
Fixed in
Change:
}; nativeBuildInputs = [ <del> (python39.withPackages (pp: with pp; [ </del> <ins> (python3.withPackages (pp: with pp; [ </ins> fontforge ])) ]; <ins> patches = [ # port to python 3 (fetchpatch { url = "https://salsa.debian.org/fonts-team/fonts-monoid/-/raw/master/debian/patches/0002-fontbuilder.py-Fix-FTBFS-with-non-int-bearing-value.patch"; hash = "sha256-IG3KXvOFZfi8dhVuKDYo0onl6ruEe24aFHBgSoMKf9c="; }) ]; </ins> buildPhase = '' local _d="" local _l=""

Discussion:
Steps to reproduce the behavior: nixos from flake on with the current unstable commit with steam enabled () Sorry I can't figure out a better way to pair this down since the standard nix-build command for this seems to still work fine. full log The previous head of unstable that I can find () has this failure happen as well. Previous commit seems to be the most recent one where my systems seems to continue to build. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Hi, thanks for the report. Adding the specific commits helped a lot. I'm able to reproduce by building the attribute, which is required by the Monoid font. Every other configuration of fontforge seems to be unaffected. Monoid seems to be unable to build with a more recent Python version, pinging the maintainer:
Is it possible that you have the Monoid font installed manually? I can't find any other reference to it in Nixpkgs. I'll likely have to restrict Fontforge to not build with Python 3.9, which is just going to break that font and similar packages.
This insight is great! How you were able to estimate that the installation of monoid might the problem here? I was stuck since weeks to not be able to upgrade on flake based rolling release against unstable, since everytime i failed in the python312Packages.fontforge package to build. Removing monoid from requested fonts did solve the topic here, thanks a lot!
Happy to be of help :) I noticed it as a reverse dependency in the build log posted and then saw that it directly depended on fontforge.
Change:
<del> { stdenv, fetchurl, pkgconfig , wafHook, python3, readline , libxslt, docbook_xsl, docbook_xml_dtd_45 </del> <ins> { stdenv , fetchurl , pkg-config , wafHook , python3 , readline , libxslt , docbook-xsl-nons , docbook_xml_dtd_45 </ins> }: stdenv.mkDerivation rec { <del> name = "tdb-1.4.3"; </del> <ins> pname = "tdb"; version = "1.4.3"; </ins> src = fetchurl { <del> url = "mirror://samba/tdb/${name}.tar.gz"; </del> <ins> url = "mirror://samba/tdb/${pname}-${version}.tar.gz"; </ins> sha256 = "06waz0k50c7v3chd08mzp2rv7w4k4q9isbxx3vhlfpx1vy9q61f8"; }; nativeBuildInputs = [ <del> pkgconfig wafHook libxslt docbook_xsl docbook_xml_dtd_45 </del> <ins> pkg-config wafHook libxslt docbook-xsl-nons docbook_xml_dtd_45 </ins> ]; buildInputs = [ <del> python3 readline </del> <ins> python3 readline # required to build python </ins> ]; wafPath = "buildtools/bin/waf";

Discussion:
Describe the bug build of failed. To Reproduce Metadata system: host os: multi-user?: sandbox: version: channels(root): channels(gtgteq): nixpkgs: Maintainer information:
Looks like regression in . We need to build talloc with Python 3 too.
It might also need
Change:
SERVER_MODE = true; } // (optionalAttrs cfg.openFirewall { DEFAULT_SERVER = mkDefault "::"; <ins> }) // (optionalAttrs cfg.emailServer.enable { MAIL_SERVER = cfg.emailServer.address; MAIL_PORT = cfg.emailServer.port; MAIL_USE_SSL = cfg.emailServer.useSSL; MAIL_USE_TLS = cfg.emailServer.useTLS; MAIL_USERNAME = cfg.emailServer.username; SECURITY_EMAIL_SENDER = cfg.emailServer.sender; </ins> }); systemd.services.pgadmin = {

Discussion:
Steps to reproduce the behavior: pgadmin.service Add any other context about the problem here. Please run and paste the result.
I know. The PR needs to be merged.
seems like it might be some time before this gets fixed. In the meantime, is there a way I could force my system to use an older version of pgadmin? I'm using flakes for my system config.
The way I do it, is to maintain my own fork of and cherry-pick PR's like that. An older version will not work, because they will run into similar errors. You could only run an older version of . This is a problem due to updated dependencies in nixpkgs. I re-requested an review from and/or maybe someone else has time to review/commit the PR.
OK I got it working for now by changing my as follows: Please let me know if that's a terrible idea in your opinion ...
No, not really. I use my branch which I regularly update, which includes my cherry-picked commits. The commit you picked reflects the status of at the time of the commit of pgadmin (and obviously the changes to pgadmin) You just need to be aware that due to the pinning, a will not update currently and should probably be reverted once the PR got merged.
thanks that's what I'll do!
I'm a little fuzzy on what happens next here. Am I seeing correctly that this problem is still not resolved?
The PR needs to be merged. AFAIK everything is done with the PR
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Got it working using in my flake.