jiebi/CodeConvo huggingface dataset:
Code change:
Package name: rio Latest released version: 0.0.27 <!-- Search your package here: --- Current version on the unstable channel: 0.0.19 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.
Seems one of the dependence of depends on which not entered master yet (see ). I'll handle this once it gets ready.
Not sure why it requires it. Maybe removing this requirement?
And it's an critical component that could not be remove.
1.72.1 merged into master
:+1: Looking forward to this as well. Hopefully fixes
Still not merged into master, merged into staging-next though.
1.73 has been merged into master.
I sent the update

Related discussion:
text: postInstall = '' install -D -m 644 misc/rio.desktop -t $out/share/applications <del> install -D -m 644 rio/src/screen/window/resources/images/logo.png  $out/share/icons/hicolor/scalable/apps/rio.png </del> <ins> install -D -m 644 misc/logo.svg  $out/share/icons/hicolor/scalable/apps/rio.svg </ins> install -dm 755 "$terminfo/share/terminfo/r/" tic -xe rio,rio-direct -o "$terminfo/share/terminfo" misc/rio.terminfo
Code change:
Package name: qdigidoc Latest released version: 4.4.0 <!-- Search your package here: --- Current version on the unstable channel: 4.2.12 Current version on the stable/release channel: 4.2.12 <!-- 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 Note for maintainers: Please tag this issue in your PR.

Related discussion:
text: , mkDerivation , fetchurl , cmake <ins> , flatbuffers </ins> , gettext , pkg-config , libdigidocpp
Code change:
Package name: qdigidoc Latest released version: 4.4.0 <!-- Search your package here: --- Current version on the unstable channel: 4.2.12 Current version on the stable/release channel: 4.2.12 <!-- 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 Note for maintainers: Please tag this issue in your PR.

Related discussion:
text: mkDerivation rec { pname = "qdigidoc"; <del> version = "4.2.12"; </del> <ins> version = "4.4.0"; </ins> src = fetchurl { url = "https://github.com/open-eid/DigiDoc4-Client/releases/download/v${version}/qdigidoc4-${version}.tar.gz"; <del> hash = "sha256-6bso1qvhVhbBfrcTq4S+aHtHli7X2A926N4r45ztq4E="; </del> <ins> hash = "sha256-5zo0yoY0wufm9DWRIccxJ5g4DXn75nT4fd2h+5QP4oQ="; </ins> }; tsl = fetchurl {
Code change:
Package name: qdigidoc Latest released version: 4.4.0 <!-- Search your package here: --- Current version on the unstable channel: 4.2.12 Current version on the stable/release channel: 4.2.12 <!-- 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 Note for maintainers: Please tag this issue in your PR.

Related discussion:
text: ''; buildInputs = [ <ins> flatbuffers </ins> libdigidocpp opensc openldap
Code change:
Steps to reproduce the behavior: pyside6 Please run and paste the result. :sweat_smile: I guess it says not found because i have no channels (i use flakes)
This same failure is causing syncplay to fail to install on my system.
yeah thats how i knew lol
To confirm, I can reproduce this issue.
I'm trying to package something which relies on pyside6. Package builds fine on nixos-stable but fails under nixos-unstable due to pyside6 not building.

Related discussion:
text: { lib , stdenv <ins> , fetchpatch2 </ins> , cmake , ninja , python
Code change:
Steps to reproduce the behavior: pyside6 Please run and paste the result. :sweat_smile: I guess it says not found because i have no channels (i use flakes)
This same failure is causing syncplay to fail to install on my system.
yeah thats how i knew lol
To confirm, I can reproduce this issue.
I'm trying to package something which relies on pyside6. Package builds fine on nixos-stable but fails under nixos-unstable due to pyside6 not building.

Related discussion:
text: sourceRoot = "pyside-setup-everywhere-src-${version}/sources/${pname}"; <ins> patches = [ # Needed to build against qt 6.5.3, until pyside 6.5.3 is released (fetchpatch2 { url = "https://code.qt.io/cgit/pyside/pyside-setup.git/patch/sources/pyside6?id=63ef7628091c8827e3d0d688220d3ae165587eb2"; hash = "sha256-TN1xdBkrzZhNontShMC1SKyJK6a8fOk/Di3zX3kv5+I="; stripLen = 2; }) ]; </ins> # FIXME: cmake/Macros/PySideModules.cmake supposes that all Qt frameworks on macOS # reside in the same directory as QtCore.framework, which is not true for Nix. postPatch = lib.optionalString stdenv.isLinux ''
Code change:
The , which . I do not have a short reproducer. However, the issue was observed on in a cgo context. The issue can be resolved by applying the following change to : The error should not have occurred. The code under test used to work, and failed after an update of the nixpkgs revision in use from to . n/a The commit range includes the following two commits that touch on : adds to the strip setup-hook adds to the cc-wrapper for response file handling The latter one seems to be the cause of the issue. Similar issues were described in and <!-- 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.
So the wrapper picks up the binary from the system instead of the one from the store because the environment is not pure? This makes the behavior of this and other wrappers unpredictable. Maybe it would be better to make sure that the tools used in the wrapper are actually from its real runtime dependencies in the store?
Yes, that matches my understanding. Yes, that thought crossed my mind, too. However, I saw that there is an , which is then . And this import and seems to be . I don't know the context or reasoning for all this logic and didn't venture there. But, that may very well also be a good solution.
Ah cool! So it basically already works that way. Setting actually enables the import. Your explanation led me to find where this logic was first introduced. The discussion there is very interesting, afaiu we need to restore to its original value so things like linker scripts will still find the intended executables. I think that the commit that introduced the should have it before the path gets restored.
Oh, I see, thanks! I overlooked one negation. That seems like it could solve the issue, too. Perhaps it's easier to just resolve before the is reset and then still invoke it later, since . I had opened that replaces the invocation by a portable one. That approach was easier to test in my use-case without rebuilding the world.

Related discussion:
text: fi if (( "${NIX_CC_USE_RESPONSE_FILE:-@use_response_file_by_default@}" >= 1 )); then <del> responseFile=$(mktemp --tmpdir cc-params.XXXXXX) </del> <ins> responseFile=$(mktemp "${TMPDIR:-/tmp}/cc-params.XXXXXX") </ins> trap 'rm -f -- "$responseFile"' EXIT printf "%qn"  ${extraBefore+"${extraBefore[@]}"}
Code change:
Steps to reproduce the behavior: as such, so that it builds with Airplay 2 support: Strangest thing is that I have 4.1.1 built and working for a while (probably at ) but following a it does not rebuild anymore, even though and hasn't changed, while the only two subsequent commits are and which I'm not too sure how they could relate. <!-- 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.

Related discussion:
text: # To achieve this, we coerce the output to a string to prevent # mkDerivation's splicing logic from kicking in. "${glib.dev}" <ins> ] ++ optional enableAirplay2 [ unixtools.xxd </ins> ]; makeFlags = [
Code change:
Steps to reproduce the behavior: as such, so that it builds with Airplay 2 support: Strangest thing is that I have 4.1.1 built and working for a while (probably at ) but following a it does not rebuild anymore, even though and hasn't changed, while the only two subsequent commits are and which I'm not too sure how they could relate. <!-- 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.

Related discussion:
text: libgcrypt libuuid ffmpeg <del> unixtools.xxd </del> ] ++ optional stdenv.isLinux glib;
Code change:
I have transmission running inside a Nixos container which has been working without issue until I recently updated the system. It now fails to start inside the container, I have tried deleting the container and all its data but the same issue exists when creating a new one. I have also tried creating the path "" on both the host and container but it doesn't seem to care. Steps to reproduce the behavior: Run transmission inside of a container Transmission service starts and runs without issue Service status Here's where I have the container and transmission defined in my config. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Same here, not sure if it's an upstream or nixpkgs issue
For the time being and since it's inside a container anyway I'm overriding the root dir of the systemd unit:
Thanks your fix is working for me!
The problem is that is listed in : Which got introduced in to The original problem was that was not in the chroot. I'd say mounting all of as read-only is going too far, so a better fix would be to just mount and only if is true. It also seems weird to have this logic be part of Transmission, but whatever. So a workaround is: (And I'm not sure why this wasn't a problem for 3 years)
I've stumbled upon this issue as well, and wondering if there is anything we can do about it regarding the Transmission service. I had to disable the following is well, before it played nicely in my setup.
indeed, adding only was one the alternatives suggested in , so we can try your suggestion. IMHO disabling or should not be the default, we could make them use though, would that be enough for you?
This is actually still an issue and it isn't limited to containers. Adding the params that posted, unfortunately, does not work for me ;/

Related discussion:
text: BindPaths = [ "${cfg.home}/${settingsDir}" cfg.settings.download-dir <ins> # Transmission may need to read in the host's /run (eg. /run/systemd/resolve) # or write in its private /run (eg. /run/host). "/run" </ins> ] ++ optional cfg.settings.incomplete-dir-enabled cfg.settings.incomplete-dir ++
Code change:
I have transmission running inside a Nixos container which has been working without issue until I recently updated the system. It now fails to start inside the container, I have tried deleting the container and all its data but the same issue exists when creating a new one. I have also tried creating the path "" on both the host and container but it doesn't seem to care. Steps to reproduce the behavior: Run transmission inside of a container Transmission service starts and runs without issue Service status Here's where I have the container and transmission defined in my config. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Same here, not sure if it's an upstream or nixpkgs issue
For the time being and since it's inside a container anyway I'm overriding the root dir of the systemd unit:
Thanks your fix is working for me!
The problem is that is listed in : Which got introduced in to The original problem was that was not in the chroot. I'd say mounting all of as read-only is going too far, so a better fix would be to just mount and only if is true. It also seems weird to have this logic be part of Transmission, but whatever. So a workaround is: (And I'm not sure why this wasn't a problem for 3 years)
I've stumbled upon this issue as well, and wondering if there is anything we can do about it regarding the Transmission service. I had to disable the following is well, before it played nicely in my setup.
indeed, adding only was one the alternatives suggested in , so we can try your suggestion. IMHO disabling or should not be the default, we could make them use though, would that be enough for you?
This is actually still an issue and it isn't limited to containers. Adding the params that posted, unfortunately, does not work for me ;/

Related discussion:
text: # an AppArmor profile is provided to get a confinement based upon paths and rights. builtins.storeDir "/etc" <del> "/run" </del> ] ++ optional (cfg.settings.script-torrent-done-enabled && cfg.settings.script-torrent-done-filename != null)
Code change:
I have transmission running inside a Nixos container which has been working without issue until I recently updated the system. It now fails to start inside the container, I have tried deleting the container and all its data but the same issue exists when creating a new one. I have also tried creating the path "" on both the host and container but it doesn't seem to care. Steps to reproduce the behavior: Run transmission inside of a container Transmission service starts and runs without issue Service status Here's where I have the container and transmission defined in my config. <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --
Same here, not sure if it's an upstream or nixpkgs issue
For the time being and since it's inside a container anyway I'm overriding the root dir of the systemd unit:
Thanks your fix is working for me!
The problem is that is listed in : Which got introduced in to The original problem was that was not in the chroot. I'd say mounting all of as read-only is going too far, so a better fix would be to just mount and only if is true. It also seems weird to have this logic be part of Transmission, but whatever. So a workaround is: (And I'm not sure why this wasn't a problem for 3 years)
I've stumbled upon this issue as well, and wondering if there is anything we can do about it regarding the Transmission service. I had to disable the following is well, before it played nicely in my setup.
indeed, adding only was one the alternatives suggested in , so we can try your suggestion. IMHO disabling or should not be the default, we could make them use though, would that be enough for you?
This is actually still an issue and it isn't limited to containers. Adding the params that posted, unfortunately, does not work for me ;/

Related discussion:
text: MemoryDenyWriteExecute = true; NoNewPrivileges = true; PrivateDevices = true; <del> PrivateMounts = true; </del> <ins> PrivateMounts = mkDefault true; </ins> PrivateNetwork = mkDefault false; PrivateTmp = true; <del> PrivateUsers = true; </del> <ins> PrivateUsers = mkDefault true; </ins> ProtectClock = true; ProtectControlGroups = true; # ProtectHome=true would not allow BindPaths= to work across /home,
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: , flit-core , linkify-it-py , markdown <ins> , mdit-py-plugins </ins> , mdurl , mistletoe , mistune
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: passthru.optional-dependencies = { compare = [ commonmark markdown mistletoe mistune panflute ]; linkify = [ linkify-it-py ]; <ins> plugins = [ mdit-py-plugins ]; </ins> rtd = [ attrs myst-parser pyyaml sphinx sphinx-copybutton sphinx-design sphinx-book-theme ]; };
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: { lib <del> , aiohttp </del> , buildPythonPackage <del> , click </del> , fetchFromGitHub , importlib-metadata , jinja2 <del> , linkify-it-py </del> , markdown-it-py <del> , mdit-py-plugins , mkdocs-exclude , msgpack </del> , poetry-core , pytest-aiohttp , pytestCheckHook
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: , rich , syrupy , time-machine <ins> , tree-sitter </ins> , typing-extensions }: buildPythonPackage rec { pname = "textual"; <del> version = "0.37.1"; format = "pyproject"; </del> <ins> version = "0.40.0"; pyproject = true; </ins> disabled = pythonOlder "3.7";
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: owner = "Textualize"; repo = pname; rev = "refs/tags/v${version}"; <del> hash = "sha256-4ehq36j2n2wRMgos5x4LQ0QeELpWAOgpgTxEWjqFLJs="; </del> <ins> hash = "sha256-+3bxc0ryHtbEJkB+EqjJhW+yWJWxMkxlSav4v6D3/gw="; </ins> }; nativeBuildInputs = [
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: ]; propagatedBuildInputs = [ <del> aiohttp click </del> importlib-metadata <del> linkify-it-py </del> markdown-it-py <del> mdit-py-plugins mkdocs-exclude msgpack </del> rich <del> ] ++ lib.optionals (pythonOlder "3.11") [ </del> typing-extensions <del> ]; </del> <ins> ] ++ markdown-it-py.optional-dependencies.plugins ++ markdown-it-py.optional-dependencies.linkify; passthru.optional-dependencies = { syntax = [ tree-sitter # tree-sitter-languages ]; }; </ins> nativeCheckInputs = [ jinja2
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: pytestCheckHook syrupy time-machine <del> ]; </del> <ins> ] ++ passthru.optional-dependencies.syntax; </ins> disabledTestPaths = [ # snapshot tests require syrupy<4
Code change:
Package name: Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 0.37.1 Current version on the stable/release channel: 0.24.1 <!-- 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.

Related discussion:
text: # Assertion issues "test_textual_env_var" "test_softbreak_split_links_rendered_correctly" <ins> # requires tree-sitter-languages which is not packaged in nixpkgs "test_register_language" </ins> ]; pythonImportsCheck = [