jiebi/CodeConvo huggingface dataset:
Change:
, json-glib , glib , glib-networking <ins> , libhandy </ins> }: stdenv.mkDerivation rec { pname = "tootle"; <del> version = "0.2.0"; </del> <ins> version = "1.0"; </ins> src = fetchFromGitHub { owner = "bleakgrey"; repo = pname; rev = version; <del> sha256 = "1z3wyx316nns6gi7vlvcfmalhvxncmvcmmlgclbv6b6hwl5x2ysi"; </del> <ins> sha256 = "NRM7GiJA8c5z9AvXpGXtMl4ZaYN2GauEIbjBmoY4pdo="; </ins> }; nativeBuildInputs = [

Discussion:
<!-- 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: tootle <!-- 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.2.0 desired version: 1.0 maintainers: Please tag this issue in your PR.
Change:
<del> { stdenv, fetchurl }: </del> <ins> { stdenv, fetchurl, nixosTests }: </ins> stdenv.mkDerivation rec { pname = "wordpress";

Discussion:
, CVSSv3=2.4 (nixos-20.03) Scanned versions: nixos-20.03: . May contain false positives. Cc
See also:
merged - closed.
Change:
''; }; <ins> unifi-poller = { nodeName = "unifi_poller"; exporterConfig.enable = true; exporterConfig.controllers = [ { } ]; exporterTest = '' wait_for_unit("prometheus-unifi-poller-exporter.service") wait_for_open_port(9130) succeed( "curl -sSf localhost:9130/metrics | grep -q 'unifipoller_build_info{.+} 1'" ) ''; }; </ins> varnish = { exporterConfig = { enable = true;

Discussion:
Project description Collect ALL UniFi Controller, Site, Device & Client Data Nixpkg currently has which is not developed anymore. Corresponding NixOS module may have to be updated. Metadata homepage URL: source URL: license: MIT platforms: unix, linux, darwin
Change:
src = fetchPypi { pname = "PyQt5"; inherit version; <del> hash = "sha256-3EHoQBqQ3D4raStBG9VJKrVZrieidCTu1L05FVZOxMA="; </del> <ins> hash = "sha256-1Gt4BLGxCk/5F1P4ET5bVYDStEYvMiYoji2ESXM0iYo="; </ins> }; patches = [

Discussion:
Steps to reproduce the behavior: picard <!-- 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]:
Also happens for . Probably related:
Hey, was "fixed" by switching to Python 3.11 at . Hopefully I'll remember to switch back to Python 3.12 when the picard's maintainers will publish a new release and will be merged to by then.

Steps to reproduce the behavior: git-cola <!-- 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]:
I'm not at a laptop for the coming weeks, so I'm not able to look into it. A segfault inside pytest doesn't sound like something git-cola specific, but not sure. If someone else wants to take a look in the meantime, that would be much appreciated
I've also run into this and have opened builds and runs with the updated PyQt5 version.
I link a few related issues:
I was able to workaround this problem by overriding the python version to be 3.11 instead of 3.12: The proper patch () is already in staging-next (), so it shouldn't be too long before it lands on master and nixpkgs-unstable.
In about a week, probably.
Change:
steam-runtime = callPackage ./runtime.nix { }; steam-runtime-wrapped = callPackage ./runtime-wrapped.nix { }; steam = callPackage ./steam.nix { }; <del> steam-fonts = callPackage ./fonts.nix { }; </del> steam-fhsenv = callPackage ./fhsenv.nix { glxinfo-i686 = pkgsi686Linux.glxinfo; steam-runtime-wrapped-i686 =

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: steam-fonts <!-- 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" desired version: <!-- 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. is no longer available under the given URL. current URL: File could be here:
Change:
}: let <del> inherit (torch) cudaPackages gpuTargetString; </del> <ins> inherit (torch) cudaCapabilities cudaPackages cudaSupport; </ins> inherit (cudaPackages) cudatoolkit cudaFlags cudaVersion; # NOTE: torchvision doesn't use cudnn; torch does!

Discussion:
I discovered today that overriding torchvision with does not work. At least not without making corresponding changes to torch. For example, We should either remove this argument and pull from torch or improve the ergonomics here somehow. cc Checkout nixpkgs at a relatively recent master commit, eg , and then run
can you test if fixes the problem? To be honest, including the argument for was a mistake in the first place -- it should (must?) use whatever was built with, so it should be inherit directly.
Maybe assert torch.cudaSupport is more explicit? Idk
I'm not super comfortable with asserts in the derivation because (afaik) they can't be overridden. Thoughts on me updating to ensure either both are compiled with CUDA, or neither are?
I understand it's a compromise. IIRC if we set here, we'll just exclude the broken package from ofborg and nixpkgs-review, contrary to the purpose.
Why do we need to be asserting or marking things as broken depending on ? shouldn't it build fine either way?
So the question is, should use , or should it accept as an argument and then possibly . I think that silently using may be surprising to people, but then again we're discussing some furnish while the thing is broken xD
ohhh i see, yeah that's tricky. i could envision someone creating a nix-shell with both and and then being very surprised to learn that is not built with CUDA support

From a brief look at the updated cuda section in the manual, it would be logical to take as an argument, rather than the compiled string. And to expose that in via gets even further beyond the scope, so let's skip it Originally posted by in
This issue has been mentioned on NixOS Discourse. There might be relevant details there:
Change:
patches = [ # fix "No/bad main configuration file" error ./fix-datadir.patch <ins> # use the same configure based build for darwin as linux ./0001-no-qtgui-darwin-bundle.patch </ins> ]; nativeBuildInputs = [

Discussion:
Steps to reproduce the behavior: Note: is a recoll dependency that previously didn't build (); graciously fixed it but it currently isn't merged. This reflects their fix: (doesn't build on macOS; builds fine elsewhere) tl;dr is <!-- --Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
I have something that builds and will show a gui but not sure how much else works. can try with:
Change:
''; meta = with lib; { <del> description = "G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc"; </del> <ins> description = "G-code generator for 3D printers (Bambu, Prusa, Voron, VzBot, RatRig, Creality, etc.)"; </ins> homepage = "https://github.com/SoftFever/OrcaSlicer"; license = licenses.agpl3Only; maintainers = with maintainers; [

Discussion:
Package name: orca-slicer Latest released version: 2.1.1 <!-- Search your package here: --- Current version on the unstable channel: 2.0.0 Current version on the stable/release channel: 2.0.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! --- <!-- 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]:
please change update from 2.0.0 to 2.1.1 due to some major bugs in 2.1.0
Change:
hash = "sha256-KtR+qU2Xys4NkEARZBbO8mTPa7EI9JplWvXdtuLt2vE="; }; <del> patches = [ ./time.patch  # TODO: remove when https://github.com/surrealdb/surrealdb/pull/4565 merged </del> <ins> cargoPatches = [ ./time.patch # TODO: remove when https://github.com/surrealdb/surrealdb/pull/4565 merged </ins> ]; cargoHash = "sha256-5qIIPdE6HYov5EIR4do+pMeZ1Lo3at39aKOP9scfMy8=";

Discussion:
Steps to reproduce the behavior: Happens on nixos-unstable, master, and on the commit that was made in the latest surrealdb PR. It consistently produces the same hash as prior to on x86_64-linux and aarch64-linux. <!-- 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]:
Hey so sorry about this, i was sure i had checked ofborg before merging.
Does anyone have bandwidth to make a PR ?
I can make a PR soon (later today) with the other hash, I was just curious how did get that hash.
Change:
mutt-ics = callPackage ../tools/networking/mutt-ics { }; <ins> mw = callPackage ../tools/text/mw { }; </ins> mwic = callPackage ../applications/misc/mwic { pythonPackages = python3Packages; };

Discussion:
A CLI program that renders Markdown timeline as HTML Announced: <!-- Describe the project a little: --Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, ...
Since upstream has a this should be pretty simple using .
Change:
{ mkKdeDerivation, <ins> pkg-config, </ins> shared-mime-info, qtnetworkauth, qtspeech, qtwebengine, cyrus_sasl, lib, <del> libkgapi </del> <ins> libetebase, libkgapi, </ins> }: mkKdeDerivation { pname = "kdepim-runtime"; <del> extraNativeBuildInputs = [shared-mime-info]; # FIXME: libkolabxml, libetebase extraBuildInputs = [qtnetworkauth qtspeech qtwebengine cyrus_sasl]; </del> <ins> extraNativeBuildInputs = [pkg-config shared-mime-info]; # FIXME: libkolabxml extraBuildInputs = [qtnetworkauth qtspeech qtwebengine cyrus_sasl libetebase]; </ins> qtWrapperArgs = [ "--prefix SASL_PATH : ${lib.makeSearchPath "lib/sasl2" [ cyrus_sasl.out libkgapi ]}"

Discussion:
EteSync is a "secure, end-to-end encrypted, and privacy respecting sync for your contacts, calendars, tasks and notes." Since GSoC 2020 KDE supports it. automatically detects if it is installed and builds the appropriate modules. Since last month is packaged for NixOS, cf. What is missing is adjusting the build of to use it. KDE PIM has a "EteSync Groupware Resource". Following sets up sync with etesync. User guide: ("build from source" link points to a site that is gone) Build instructions: <!-- 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]:
Change:
]; execPkgs = lib.concatMap (opt: let isSet = config.serviceConfig ? ${opt}; <del> in lib.optional isSet config.serviceConfig.${opt}) execOpts; </del> <ins> in lib.flatten (lib.optional isSet config.serviceConfig.${opt})) execOpts; </ins> unitAttrs = toplevelConfig.systemd.units."${name}.service"; allPkgs = lib.singleton (builtins.toJSON unitAttrs); unitPkgs = if fullUnit then allPkgs else execPkgs;

Discussion:
Describe the bug Evaluating my system stopped working since the last channel update (Jul 17), because systemd confinement can no longer evaluate package list with ("nixos/nginx: move configuration testing script into reload command") Evaluating it in the repl yields the following: To Reproduce Steps to reproduce the behavior: gives most of the config required to have the breakage but... Expected behavior evaluates to something Additional informations I was able to work around the issue by forcing the value, e.g. So the problem is purely in the way the package list is built that doesn't parse properly complex commands? or intermediate variables I'm not sure... The machine I'm testing this on is way too slow to test comfortably, I'll play around later this week if required. Notify maintainers (and I guess as this concerns nginx) Metadata Maintainer information: (not sure how that works, please adjust if required)
To be confirmed, but I guess that the case where is a list is not handled by :
I confirmed that this is the case with yesterday: forcing value to a single item fixes it, back to a list with trivial values breaks again. So the construction of the package list is not resilient enough to list values - ju1m provided a fix for me to try, which looks good to me but I didn't take time to test yet: one of us will probably open a PR sooner or later
Has this been fixed in the meantime, or a PR filed? I'd assume this will break peoples setups when using the module - having multiple etc. seems pretty common.
Thanks for the reminder, hadn't taken time -- doing this now. FWIW I'm not sure how many people actually use confinement ? But might as well fix for 20.09 :)
Change:
# Zplugin's source files install -dm0755 "$outdir" <del> # Installing also backward compatibility layer install -m0644 z{plugin,init}{,-side,-install,-autoload}.zsh "$outdir" install -m0755 git-process-output.zsh "$outdir" </del> <ins> # Installing backward compatibility layer install -m0644 zinit{,-side,-install,-autoload}.zsh "$outdir" install -m0755 share/git-process-output.zsh "$outdir" </ins> # Zplugin autocompletion installShellCompletion --zsh _zinit

Discussion:
Package name: zinit Latest released version: 3.11.0 <!-- Search your package here: --- Current version on the unstable channel: 3.7 Current version on the stable/release channel: 3.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:
<ins> { stdenv , lib , python3Packages , fetchFromGitHub , ffmpeg , libsForQt5 , testers , corrscope }: python3Packages.buildPythonApplication rec { pname = "corrscope"; version = "0.9.0"; pyproject = true; src = fetchFromGitHub { owner = "corrscope"; repo = "corrscope"; rev = version; hash = "sha256-kOPhVm4epIhBSsgQVKNCoQ7DZcMG/b3sapxwwKo/V+U="; }; pythonRelaxDeps = [ "attrs" "ruamel.yaml" ]; nativeBuildInputs = (with libsForQt5; [ wrapQtAppsHook ]) ++ (with python3Packages; [ poetry-core pythonRelaxDepsHook ]); buildInputs = [ ffmpeg ] ++ (with libsForQt5; [ qtbase ] ++ lib.optionals stdenv.hostPlatform.isLinux [ qtwayland ]); propagatedBuildInputs = with python3Packages; [ appdirs appnope atomicwrites attrs click matplotlib numpy packaging qtpy pyqt5 ruamel-yaml colorspacious ]; dontWrapQtApps = true; preFixup = '' makeWrapperArgs+=( --prefix PATH : ${lib.makeBinPath [ ffmpeg ]} "''${qtWrapperArgs[@]}" ) ''; passthru.tests.version = testers.testVersion { package = corrscope; # Tries writing to # - $HOME/.local/share/corrscope on Linux # - $HOME/Library/Application Support/corrscope on Darwin command = "env HOME=$TMPDIR ${lib.getExe corrscope} --version"; }; meta = with lib; { description = "Render wave files into oscilloscope views, featuring advanced correlation-based triggering algorithm"; longDescription = '' Corrscope renders oscilloscope views of WAV files recorded from chiptune (game music from retro sound chips). Corrscope uses "waveform correlation" to track complex waves (including SNES and Sega Genesis/FM synthesis) which jump around on other oscilloscope programs. ''; homepage = "https://github.com/corrscope/corrscope"; license = licenses.bsd2; maintainers = with maintainers; [ OPNA2608 ]; platforms = platforms.all; mainProgram = "corr"; }; } </ins>

Discussion:
Package name: corrscope Latest released version: 0.9.0 <!-- Search your package here: --- Current version on the unstable channel: 0.8.1 Current version on the stable/release channel:0.8.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. --My apologies for accidentally publishing before i was done with the issue. 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:
wrapProgram $out/bin/mancha ${makeWrapperArgs} ''; <ins> passthru.updateScript = unstableGitUpdater { }; </ins> meta = { description = "Lightweight and featureful terminal web browser"; homepage = "https://sr.ht/~bptato/chawan/";

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:
libxml2 ]; <del> buildInputs = [ gtk4 glib gsettings-desktop-schemas gdk-pixbuf gnome-desktop geocode-glib_2 geoclue2 libgweather libadwaita ]; preFixup = '' gappsWrapperArgs+=( # Fallback sound theme --prefix XDG_DATA_DIRS : "${sound-theme-freedesktop}/share" ) ''; </del> <ins> buildInputs = [ gtk4 glib gsettings-desktop-schemas gdk-pixbuf gnome-desktop geocode-glib_2 geoclue2 libgweather libadwaita ] ++ (with gst_all_1; [ # GStreamer plugins needed for Alarms gstreamer gst-plugins-base gst-plugins-good ]); </ins> doCheck = true;

Discussion:
Gnome clocks fails to play alarm. Emits following error: (): GStreamer-Play-ERROR **: 05:20:00.109: GstPlay: 'playbin' element not found, please check your setup Trace/breakpoint trap (core dumped) Steps to reproduce the behavior: an alarm for 1 min later and wait. the crash I use Hyprland not gnome. If it is expected for clocks to not work in other desktop environments, I am sorry for the noise. <!-- 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]:
Thanks for reporting. Sounds like we forgot to add GStreamer to buildInputs in the previous bump ( in GNOME 45). It works on GNOME Shell because it leaks GStreamer into environment, masking this issue. The sound theme can be removed.
Please test
Change:
{ port = 7979; extraOpts = { <del> url = mkOption { type = types.str; description = '' URL to scrape JSON from. ''; }; </del> configFile = mkOption { type = types.path; description = '' Path to configuration file. ''; }; <del> listenAddress = {}; # not used </del> }; serviceOpts = { serviceConfig = { ExecStart = '' <del> ${pkgs.prometheus-json-exporter}/bin/prometheus-json-exporter  --port ${toString cfg.port}  ${cfg.url} ${escapeShellArg cfg.configFile}  </del> <ins> ${pkgs.prometheus-json-exporter}/bin/json_exporter  --config.file ${escapeShellArg cfg.configFile}  --web.listen-address="${cfg.listenAddress}:${toString cfg.port}"  </ins> ${concatStringsSep " n  " cfg.extraFlags} ''; }; }; <ins> imports = [ (mkRemovedOptionModule [ "url" ] '' This option was removed. The URL of the endpoint serving JSON must now be provided to the exporter by prometheus via the url parameter `target'. In prometheus a scrape URL would look like this: http://some.json-exporter.host:7979/probe?target=https://example.com/some/json/endpoint For more information, take a look at the official documentation (https://github.com/prometheus-community/json_exporter) of the json_exporter. '') ({ options.warnings = options.warnings; options.assertions = options.assertions; }) ]; </ins> }

Discussion:
current version: unstable-2017-10-06 desired version: 0.2.0 maintainers:
An option in the service definition to overwrite the package would be nice, too! :smile:
Why is this needed? -options are usually implemented if modifying the package in question with an overlay is a bad idea because it would mean that a lot of leaf-packages would require a rebuild as well. An example for that would be .
Ah, okay.
could you please update this package?
Oh sure, thank you for the ping :)
Change:
patches = [ ./fix-libcrypto-loading.patch <ins> (fetchpatch { url = "https://github.com/saltstack/salt/commit/6ec8b90e402ff3fa8f27c7da70ece898592416bc.patch"; hash = "sha256-OQCJeG12cp2EZ0BErp6yqsqhv023923rVFDHAFUfF6c="; }) </ins> ]; postPatch = ''

Discussion:
nicely describes the issue and the fix Steps to reproduce the behavior: salt on to run it errors salt working and may be of interest to ;) <!-- 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.
Change:
- `nushell` has been updated to at least version 0.77.0, which includes potential breaking changes in aliases. The old aliases are now available as `old-alias` but it is recommended you migrate to the new format. See [Reworked aliases](https://www.nushell.sh/blog/2023-03-14-nushell_0_77.html#reworked-aliases-breaking-changes-kubouch). <ins> - `gajim` has been updated to version 1.7.3 which has disabled legacy ciphers. See [changelog for version 1.7.0](https://dev.gajim.org/gajim/gajim/-/releases/1.7.0). </ins> - `keepassx` and `keepassx2` have been removed, due to upstream [stopping development](https://www.keepassx.org/index.html%3Fp=636.html). Consider [KeePassXC](https://keepassxc.org) as a maintained alternative. - The [services.kubo.settings](#opt-services.kubo.settings) option is now no longer stateful. If you changed any of the options in [services.kubo.settings](#opt-services.kubo.settings) in the past and then removed them from your NixOS configuration again, those changes are still in your Kubo configuration file but will now be reset to the default. If you're unsure, you may want to make a backup of your configuration file (probably /var/lib/ipfs/config) and compare after the update.

Discussion:
Package name: gajim Latest released version: 1.7.3 <!-- Search your package here: --- Current version on the unstable channel: 1.5.4 Current version on the stable/release channel: 1.6.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 Note for maintainers: Please tag this issue in your PR.
New sha256 hash, but it doesn’t just work with a version bump because they changed something with the build setup.