jiebi/CodeConvo huggingface dataset:
Change:
passthru = { inherit <del> # The wrapper consults luaEnv and lua.version luaEnv lua # In the wrapper, we want to reference vapoursynth which has the `python3` # passthru attribute (which has the `sitePrefix` attribute). This way we'll # be sure that in the wrapper we'll use the same python3.sitePrefix used to # build vapoursynth. vapoursynthSupport vapoursynth ; </del> <ins> # The wrapper consults luaEnv and lua.version luaEnv lua # In the wrapper, we want to reference vapoursynth which has the `python3` # passthru attribute (which has the `sitePrefix` attribute). This way we'll # be sure that in the wrapper we'll use the same python3.sitePrefix used to # build vapoursynth. vapoursynthSupport vapoursynth ; wrapper = callPackage ./wrapper.nix { }; scripts = callPackage ./scripts { }; </ins> }; meta = {

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. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Yeeessaah!
Change:
<del> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE fontconfig SYSTEM "urn:fontconfig:fonts.dtd"> <fontconfig> <!-- This configuation is intentionally left empty in order to override any other font package that may wish to set up an alias for the Microsoft @fontname@ font. If you actually do want to have the alias then please change the priority of that package; see the Nix manual page for nix-env for details. --> </fontconfig> </del>

Discussion:
Steps to reproduce the behavior: corefonts This package fails to build because all of the sourceforge mirrors all return "429 Too Many Requests" after making a certain number of requests. I'm not sure if the package needs to add a delay, find a different download host, or something else entirely. <!-- 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:
xnd = callPackage ../development/python-modules/xnd { }; <ins> xonsh = toPythonModule (pkgs.xonsh.override { python3Packages = self; }); </ins> xpath-expressions = callPackage ../development/python-modules/xpath-expressions { }; xpybutil = callPackage ../development/python-modules/xpybutil { };

Discussion:
Xonsh because of However, in unstable the is using
cc as maintainer
I am waiting for someone hit the button here: P.S.: I am not waiting anymore.
Upstream has unpinned prompt-toolkit after

Upstream issue: Since the issue seems to be specific to NixOS, let's track it here. The two commands above should only print "True". If applicable, add screenshots to help explain your problem. Tested on xonsh 0.13.3 and 0.13.4 system: host os: multi-user?: sandbox: version: nixpkgs:
Upstream fix:
Change:
{ stdenv , lib , fetchFromGitLab , gettext , meson , ninja , pkg-config <del> , python3 </del> , rustPlatform , wrapGAppsHook4 , appstream-glib , desktop-file-utils , glib , gtk4 <ins> , gdk-pixbuf </ins> , libadwaita , Foundation }: stdenv.mkDerivation rec { pname = "gnome-obfuscate"; <del> version = "0.0.7"; </del> <ins> version = "0.0.9"; </ins> src = fetchFromGitLab { domain = "gitlab.gnome.org"; owner = "World"; repo = "Obfuscate"; rev = version; <del> sha256 = "sha256-jEMOg2yHi6K57XhA/7hkwwvedmikoB8pGV3ka+jixq8="; </del> <ins> hash = "sha256-aUhzact437V/bSsG2Ddu2mC03LbyXFg+hJiuGy5NQfQ="; </ins> }; cargoDeps = rustPlatform.fetchCargoTarball { inherit src; name = "${pname}-${version}"; <del> sha256 = "sha256-P04BeidLXouPLzT/vsa4VC5AOENF0W4gqXqzdmRFhmE="; </del> <ins> hash = "sha256-HUQvdCmzjdmuJGDLtC/86yzbRimLzx+XbW29f+Ua48w="; </ins> }; nativeBuildInputs = [ gettext <del> glib </del> meson ninja pkg-config <del> python3 </del> rustPlatform.cargoSetupHook rustPlatform.rust.cargo rustPlatform.rust.rustc wrapGAppsHook4 <ins> appstream-glib desktop-file-utils </ins> ]; buildInputs = [ <del> appstream-glib desktop-file-utils </del> glib gtk4 <ins> gdk-pixbuf </ins> libadwaita ] ++ lib.optionals stdenv.isDarwin [ Foundation ]; <del> postPatch = '' patchShebangs build-aux/meson_post_install.py ''; </del> meta = with lib; { description = "Censor private information"; homepage = "https://gitlab.gnome.org/World/obfuscate"; license = licenses.gpl3Plus; <del> maintainers = with maintainers; [ fgaz ]; </del> platforms = platforms.all; <ins> mainProgram = "obfuscate"; maintainers = with maintainers; [ fgaz ]; </ins> }; }

Discussion:
Package name: gnome-obfuscate Latest released version: 0.0.9 <!-- Search your package here: --- Current version on the unstable channel: 0.0.7 Current version on the stable/release channel: 0.0.7 <!-- 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:
, disableDocs ? false , CoreFoundation , gsettings-desktop-schemas <ins> , wrapGAppsHook </ins> }: let

Discussion:
Operations like File -Open crashes DrRacket with the error EDIT: I installed from unstable Install Start Presssystem: host os: multi-user?: sandbox: version: channels(root): channels(simendsjo): nixpkgs:
I strongly suspect it needs . I can take a quick look.
Change:
<ins> { backports-functools-lru-cache , wcwidth }: wcwidth.overridePythonAttrs(oldAttrs: { propagatedBuildInputs = oldAttrs.propagatedBuildInputs ++ [ backports-functools-lru-cache ]; }) </ins>

Discussion:
Steps to reproduce the behavior: I am able to build using July 27's , but not with the more recent s.
I believe this is related to Henceforth, all python2 builds will be broken. I am trying to pin nixpkgs before this commit, and I will report back how it goes.
hey, do you mind giving a try?
I can confirm that pinning python2 to the parent of works for me. I am actually not using fahclient but another python2 package (), but the error message is identical so I didn't bother to open a new issue. Maybe can check?
Change:
qcsxcad = libsForQt5.qcsxcad;  # added 2020-11-05 qmk_firmware = throw "qmk_firmware has been removed because it was broken"; # added 2021-04-02 qr-filetransfer = throw ''"qr-filetransfer" has been renamed to "qrcp"''; # added 2020-12-02 <ins> qt5ct = libsForQt5.qt5ct; # added 2021-12-27 </ins> quake3game = ioquake3; # added 2016-01-14 quilter = throw "quilter has been removed from nixpkgs, as it was unmaintained."; # added 2021-08-03 qvim = throw "qvim has been removed."; # added 2020-08-31

Discussion:
qt5ct is not a part of libsForQt5, what means it's not built for other Qt versions (like 5.14) and apps using these Qt versions (e.g. virtualbox) aren't themed Steps to reproduce the behavior: virtualbox and run it VirtualBox is themed ! Maintainer information:
I don't have enough familiarity with the Qt infrastructure to fix this myself.
looks like all you need is to just move qt5ct from all- to qt5-, it will become libsForQt5.qt5ct
Change:
libressl ] ++ lib.optionals stdenv.isDarwin [ curl Security ]; <ins> # Needed to get openssl-sys to use pkg-config. OPENSSL_NO_VENDOR = 1; </ins> # Most tests rely on external resources and build artifacts. # Disabling check here to work with build sandboxing. doCheck = false;

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: wasm-pack <!-- The current version can be found easily with the same process than above for checking the master branch If an open PR is present for the package, take this version as the current one and link to the PR --current version: 0.9.1 desired version: 0.10.1 <!-- 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.
I've just updated this to request 0.10.1 instead 0f 0.10.0. Is there any chance this will be looked at soon? I've tried packaging 0.10 but ran into trouble, so right now I'm stuck on an old version as a result.
tagging you as well because you've been active on recent wasm-pack pull requests (sorry to bother you, but from looking at PRs it seems like hasn't been active on this kind of thing for a while).
Change:
ffmpegVariant = "full"; }; <ins> ffmpeg_6 = callPackage ../development/libraries/ffmpeg/6.nix { inherit (darwin.apple_sdk.frameworks) Cocoa CoreServices CoreAudio CoreMedia AVFoundation MediaToolbox VideoDecodeAcceleration VideoToolbox; }; ffmpeg_6-headless = ffmpeg_6.override { ffmpegVariant = "headless"; }; ffmpeg_6-full = ffmpeg_6.override { ffmpegVariant = "full"; }; </ins> # Aliases # Please make sure this is updated to the latest version on the next major # update to ffmpeg

Discussion:
Package name: ffmpeg Latest released version: 6.0 Current version on the unstable channel: 5.1.2 Notify maintainers Related: I think the way to go with such a rename should be to follow the instructions here: Note for maintainers: Please tag this issue in your PR.
Current version is 4.x, this would probably be as an extra package (ffmpeg_6 and variants)
BTW, 5.1 is LTS and should be maintained by upstream for two years, if I got it right.
I wonder if this should be closed, as default remained same. (even 4 on , but 5 soon from )
I think 6 by default is something we should do for 23.11 and keep 5 on 23.05.
ffmpeg defaults to 6 now on master
Change:
''} # Run systemd-nspawn without startup notification (we'll <del> # wait for the container systemd to signal readiness). </del> <ins> # wait for the container systemd to signal readiness) # Kill signal handling means systemd-nspawn will pass a system-halt signal # to the container systemd when it receives SIGTERM for container shutdown; # containerInit and stage2 have to handle this as well. </ins> exec ${config.systemd.package}/bin/systemd-nspawn  --keep-unit  -M "$INSTANCE" -D "$root" $extraFlags  $EXTRA_NSPAWN_FLAGS  --notify-ready=yes  <ins> --kill-signal=SIGRTMIN+3  </ins> --bind-ro=/nix/store  --bind-ro=/nix/var/nix/db  --bind-ro=/nix/var/nix/daemon-socket 

Discussion:
Describe the bug So, I seem to be seeing an issue that more or less exactly matches the description of on nixos today. I have a number of containers hosting websites, and none of them are shut down gracefully when I shut the host down. I must wait for the 90-second systemd timeout, and see them forcibly shut down. The mysql database in one container doesn't seem to enjoy this. If I shut down a container manually, via , it works flawlessly. But somehow this is not triggered when I shut down the host. To Reproduce There are details, but the meat and potatoes is that I have some containers defined in my , and then try to reboot my host with . Additional context My containers reside on ZFS filesystems? That's all I can think of. Notify maintainers <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- Metadata
I have the same issue. Note that I am very new to NixOS, so I might have missed something This is a workaround that works for me:
Change:
<del> import ./make-test.nix ({ pkgs, ... }: { name = "mathics"; meta = with pkgs.stdenv.lib.maintainers; { maintainers = [ benley ]; }; nodes = { machine = { ... }: { services.mathics.enable = true; services.mathics.port = 8888; }; }; testScript = '' startAll; $machine->waitForUnit("mathics.service"); $machine->waitForOpenPort(8888); $machine->succeed("curl http://localhost:8888/"); ''; }) </del>

Discussion:
The mathics test does not work because: /cc (commit history)
I see the same error with on the 20.03 beta channel. I think it also happens on Master. It used to work (maybe a few weeks ago? if I have time I'll bisect).
I removing mathics.
Change:
}; }); <del> ## Upstreamed, awaiting a Hackage release th-desugar = overrideCabal super.th-desugar (drv: { ##     • Could not deduce (MonadIO (DsM q)) ##         arising from the 'deriving' clause of a data type declaration ##       from the context: Quasi q src = pkgs.fetchFromGitHub { owner  = "goldfirere"; repo   = "th-desugar"; rev    = "4ca98c6492015e6ad063d3ad1a2ad6c4f0a56837"; sha256 = "1n3myd3gia9qsgdvrwqa023d3g7wkrhyv0wc8czwzz0lj9xzh7lw"; }; }); </del> <ins> th-desugar = super.th-desugar_1_8; </ins> ## Upstreamed, awaiting a Hackage release websockets = overrideCabal super.websockets (drv: {

Discussion:
doesn't build on unstable. The root cause seems to be that 1.7 requires but ghc-8.4.1 only provides according to . run system: host os: multi-user?: sandbox: version: channels(chisui): channels(root): nixpkgs:
Only the 2.4 version of singletons works with GHC 8.4.1.
Than version should be changed from 2.3.1 to 2.4.
See
Change:
GEM remote: https://rubygems.org/ specs: <del> fusuma (3.1.0) fusuma-plugin-appmatcher (0.6.0) fusuma (~> 3.0) </del> <ins> fusuma (3.3.1) fusuma-plugin-appmatcher (0.6.1) fusuma (>= 3.0) </ins> rexml ruby-dbus <del> fusuma-plugin-keypress (0.8.0) fusuma (~> 2.0) </del> <ins> fusuma-plugin-keypress (0.9.0) fusuma (>= 3.1) </ins> fusuma-plugin-sendkey (0.10.1) <del> fusuma (~> 3.1) </del> <ins> fusuma (>= 3.1) </ins> revdev <del> fusuma-plugin-tap (0.4.2) fusuma (~> 2.0) </del> fusuma-plugin-wmctrl (1.3.1) <del> fusuma (~> 3.1) </del> <ins> fusuma (>= 3.1) </ins> revdev (0.2.1) <del> rexml (3.2.5) ruby-dbus (0.19.0) </del> <ins> rexml (3.2.6) ruby-dbus (0.23.1) </ins> rexml PLATFORMS ruby DEPENDENCIES <del> fusuma </del> <ins> fusuma (>= 3.0.0) </ins> fusuma-plugin-appmatcher fusuma-plugin-keypress fusuma-plugin-sendkey <del> fusuma-plugin-tap </del> fusuma-plugin-wmctrl BUNDLED WITH <del> 2.4.6 </del> <ins> 2.4.22 </ins>

Discussion:
The fusuma program in the package of the same name crashes when trying to run it. The breaking change causing this issue was made somewhere in the last 56 days: That's when I last updated this particular host, after which everything was still working fine. Steps to reproduce the behavior: "fusuma" package to run fusuma I expected fusuma to start running and be available for use. N/A Instead of displaying the expected behavior, the program crashes: In addition, if I clone the repo, then open a and run the cloned project in that nix-shell, that runs successfully unmodified on the same host. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Thanks especially for the celerity of the fix!
Is there supposed to be a delay between this merge and availability updating? I can clearly see this PR is merged, but when I update my system the new version isn't in there.
Yes, see
One month later, I don't see the updated package. How long can this take ?
The update is already on master, but I don't think it's been backported yet. Are you on NixOS 23.11 instead of unstable?
Yes.
Backported in , should take a few days to land.
Many thanks for the commit !
Change:
after = [ "redis-paperless.service" ]; }; <ins> systemd.services.paperless-task-queue = { description = "Paperless Celery Workers"; serviceConfig = defaultServiceConfig // { User = cfg.user; ExecStart = "${pkg}/bin/celery --app paperless worker --loglevel INFO"; Restart = "on-failure"; # The `mbind` syscall is needed for running the classifier. SystemCallFilter = defaultServiceConfig.SystemCallFilter ++ [ "mbind" ]; # Needs to talk to mail server for automated import rules PrivateNetwork = false; }; environment = env; }; </ins> # Reading the user-provided password file requires root access systemd.services.paperless-copy-password = mkIf (cfg.passwordFile != null) { requiredBy = [ "paperless-scheduler.service" ];

Discussion:
Since which updated from 1.9.2 to 1.10.2, the scheduler service can't be started, the error reported in the logs is: Steps to reproduce the behavior: or to see error as above in the logs The service starts succesfully <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. --Module maintainers: Package maintainers: Please run and paste the result.
Probably fixed by
Change:
PrivateTmp              = "yes"; PrivateNetwork          = "yes"; NoNewPrivileges         = "yes"; <del> ReadWriteDirectories    = stateDir; </del> <ins> StateDirectory          = [ "uptimed" ]; </ins> InaccessibleDirectories = "/home"; ExecStart               = "${pkgs.uptimed}/sbin/uptimed -f -p ${stateDir}/pid"; };

Discussion:
Despite beeing installed for a few days now: it seems like the uptimed service does not find its database properly and prints just the current uptime. I guess this is because the database file gets recreated every boot. But that's only a shot into the blue guess. System: 17.03pre99626. (Gorilla) Nix version: nix-env (Nix) 1.11.6 Nixpkgs version: "17.03pre99626."
Some logs from the journal: Pinging maintainers of the service (there is no maintainer in the pkg):
Probably a permission problem or the said directory does not exists.
Yep, looks like it,... though I have no time to investigate, so I'll just leave this here and hope it gets fixed.
In the meantime you can use this one instead:
:smile:
Still no love for this?
Still no love for this?
Does the following (untested) code help?
Tried yours and but fails with: tested on System: 18.03pre124015. (Impala) Nix version: nix-env (Nix) 1.11.16 Nixpkgs version: "18.03pre124015." Sandboxing enabled: build-use-sandbox = true (diff applied on )
It seems that it did not saved my updated change (I forgot to prefix first)
I know nothing about , sorry.
close as unresolved?
Closed as unresolved.
The issue is still present under 18.09 and (I presume) as  does not seem to contain any of the changes proposed here. Why is this issue closed?
Because I do not care anymore and nobody else seems to care either. Do you want me to reopen?
I probably do. I have some extra details on the issue: So it seems that the user cannot write to the directory even though it owns it.
It seems that is a workaround. Not sure about its safety though.
So now it works, but in a roundabout way: The next steps are making the directory world-readable and bringing into user scope.
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 .
As people seemed to interested in this and it is a bug: still important to me
Should be made a tmpfiles rule or if possible changed to /var/lib/uptime, in which case we can set .
I marked this as stale due to inactivity. &rarr;
Change:
''; changelog = "https://github.com/zaps166/QMPlay2/releases/tag/${finalAttrs.version}"; license = lib.licenses.lgpl3Plus; <del> maintainers = with lib.maintainers; [ AndersonTorres ]; </del> <ins> maintainers = with lib.maintainers; [ AndersonTorres kashw2 ]; </ins> platforms = lib.platforms.linux; }; })

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.
Change:
img2pdf = with python3Packages; toPythonApplication img2pdf; <del> imgbrd-grabber = qt5.callPackage ../applications/graphics/imgbrd-grabber { }; </del> imgcat = callPackage ../applications/graphics/imgcat { }; img-cat = callPackage ../applications/graphics/img-cat { };

Discussion:
Package name: imgbrd-grabber Latest released version: <!-- Search your package here: --- Current version on the unstable channel: 7.10.0 Current version on the stable/release channel: 7.10.0 <!-- 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:
buildDotnetModule rec { pname = "libation"; <del> version = "11.1.0"; </del> <ins> version = "11.3.1"; </ins> src = fetchFromGitHub { owner = "rmcrackan"; repo = "Libation"; rev = "v${version}"; <del> hash = "sha256-NxG1H8lj+aBpgKj03CDpX/tLT0SxDS3pnZGQ2ultBnQ="; </del> <ins> hash = "sha256-oTqV1pmjjxzLdvEIUmg3cRFhnPG69yHMbSd9ZBv+XVE="; </ins> }; sourceRoot = "${src.name}/Source"; <del> dotnet-sdk = dotnetCorePackages.sdk_7_0; dotnet-runtime = dotnetCorePackages.runtime_7_0; </del> <ins> dotnet-sdk = dotnetCorePackages.sdk_8_0; dotnet-runtime = dotnetCorePackages.runtime_8_0; </ins> nugetDeps = ./deps.nix;

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