jiebi/CodeConvo huggingface dataset:
Change:
, libicns , jq , moreutils <ins> , cacert </ins> , nodePackages }: stdenv.mkDerivation (finalAttrs: {

Discussion:
Steps to reproduce the behavior: vesktop Log had some escape codes for color so I removed them to make it more readable Got this error while I was trying to update my flake to
Can confirm. Git bisect shows that caused this on master. Yet if you build that PR's branch it works fine. So something broke between when that PR was opened and when it got merged Edit: also fails in Hydra:
Can these changes be reverted until at least hydra builds properly?
I just reverted in my local checkout of master and ran which resulted in the same errors. So this has nothing to do with the PR above
having the same error when compiling a yarn package ()
Found the culprit:
So do we need to add the certificates ourselves now?
I opened a PR at fixing this. It includes cacert in the build, which in-turn adds to the environment
I'm sorry, but what about other cases with using pnpm? It throws this error in dev shell when installing/upgrading. I found in .npmrc fixes the issue, but is this correct behaviour?
Perhaps this should be tracked in a new issue. Not sure what'd be the best way forward
Change:
<ins> diff --git a/shell/source/unix/exec/shellexec.cxx b/shell/source/unix/exec/shellexec.cxx --- a/shell/source/unix/exec/shellexec.cxx +++ b/shell/source/unix/exec/shellexec.cxx @@ -150,7 +150,7 @@ void SAL_CALL ShellExec::execute( const OUString& aCommand, const OUString& aPar if (std::getenv("LIBO_FLATPAK") != nullptr) { aBuffer.append("/app/bin/xdg-open"); } else { -            aBuffer.append("/usr/bin/xdg-open"); +            aBuffer.append("xdg-open"); } #endif aBuffer.append(" "); diff --git a/shell/source/unix/misc/senddoc.sh b/shell/source/unix/misc/senddoc.sh index 4519e01f26e2..8985711a2c01 100755 --- a/shell/source/unix/misc/senddoc.sh +++ b/shell/source/unix/misc/senddoc.sh @@ -393,6 +393,8 @@ case `basename "$MAILER" | sed 's/-.*$//'` in MAILER=/usr/bin/kde-open elif [ -x /usr/bin/xdg-open ] ; then MAILER=/usr/bin/xdg-open +        elif type -p xdg-open >/dev/null 2>&1 ; then +            MAILER="$(type -p xdg-open)" else echo "Unsupported mail client: `basename $MAILER | sed 's/-.*^//'`" exit 2 </ins>

Discussion:
When user control-clicks on link embedded in cell nothing happens, and gets printed in console. Create a cell with web link in libre office calc and try to open the link. System: 17.03.1152. Nix version: 1.11.8 Nixpkgs version: 17.03.1152. Sandboxing enabled: false
This patch for libreoffice core may help
Change:
, callPackage, ghostscript_headless, harfbuzz , makeWrapper, installShellFiles , python3, ruby, perl, tk, jdk, bash, snobol4 <del> , coreutils, findutils, gawk, getopt, gnugrep, gnumake, gnupg, gnused, gzip, ncurses, zip </del> <ins> , coreutils, findutils, gawk, getopt, gnugrep, gnumake, gnupg, gnused, gzip, html-tidy, ncurses, zip </ins> , libfaketime, asymptote, biber-ms, makeFontsConf , useFixedHashes ? true , recurseIntoAttrs

Discussion:
I'm trying to produce html and epub files from a LaTeX document with the ht tools and it looks like they don't work properly. Given the following simple input, with a PDF file , the commands and give the following errors In both cases the output is produced, but the image is missing. <!-- 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.
How did you install TeXLive / which version of TeXLive do you have installed? It looks like you have 2 commands missing: and . I ran the same commands (on your test file) and only got the second error which was easily fixed for me by installing the package from the repos (seems to be an optional dependency, so not part of TeXLive per se). seems to be part of all the current unstable TeXLive packages, but none of the 23.05 TeXLive packages.
Indeed I'm on the 20.05 channel. I installed with the following in my NixOS is not a problem, as you mentioned. It's just that causes the problem. The TeXLive version is (in nixpkgs). I see the following in the store .
Ok thanks. Just to confirm, are you on or did you mean to say ?
Yes, sorry. I'm on .
cc this must have been fixed by the recent changes to scripts packaging? Is this is a wontfix for 23.05?
The script should work now on unstable, I see listed among the binaries on However is most likely an external dependency that must be to the path via .
PS: I'll try slip an extra link in the 23.05 , since 23.11 is still some time away. (It should be enough to add to the loop that reads from – not in directly as it would cause a useless rebuild – so if somebody has a moment to do it before me, go ahead!)
Thanks for the rapid fix!
Change:
bypassCache = true; reconstructLock = true; }; <ins> localtunnel = nodeEnv.buildNodePackage { name = "localtunnel"; packageName = "localtunnel"; version = "2.0.2"; src = fetchurl { url = "https://registry.npmjs.org/localtunnel/-/localtunnel-2.0.2.tgz"; sha512 = "n418Cn5ynvJd7m/N1d9WVJISLJF/ellZnfsLnx8WBWGzxv/ntNcFkJ1o6se5quUhCplfLGBNL5tYHiq5WF3Nug=="; }; dependencies = [ sources."ansi-regex-5.0.1" sources."ansi-styles-4.3.0" sources."axios-0.21.4" sources."cliui-7.0.4" sources."color-convert-2.0.1" sources."color-name-1.1.4" sources."debug-4.3.2" sources."emoji-regex-8.0.0" sources."escalade-3.1.1" sources."follow-redirects-1.15.2" sources."get-caller-file-2.0.5" sources."is-fullwidth-code-point-3.0.0" sources."ms-2.1.2" sources."openurl-1.1.1" sources."require-directory-2.1.1" sources."string-width-4.2.3" sources."strip-ansi-6.0.1" sources."wrap-ansi-7.0.0" sources."y18n-5.0.8" sources."yargs-17.1.1" sources."yargs-parser-20.2.9" ]; buildInputs = globalBuildInputs; meta = { description = "Expose localhost to the world"; homepage = "https://github.com/localtunnel/localtunnel#readme"; license = "MIT"; }; production = true; bypassCache = true; reconstructLock = true; }; </ins> lodash = nodeEnv.buildNodePackage { name = "lodash"; packageName = "lodash";

Discussion:
Project description Localtunnel allows you to easily share a web service on your local development machine without messing with DNS and firewall settings. Metadata homepage URL: source URL: license: mit platforms: unix, linux, darwin, nodejs
Change:
<ins> { lib , python3Packages , fetchFromGitHub }: python3Packages.buildPythonPackage rec { pname = "lib4sbom"; version = "0.7.1"; format = "setuptools"; src = fetchFromGitHub { owner = "anthonyharrison"; repo = pname; rev = "v${version}"; hash = "sha256-UQZZYTRDbUqSH6F8hjhp9L70025cRO3zXQ8Aoznotg4="; }; propagatedBuildInputs = with python3Packages; [ pyyaml semantic-version defusedxml ]; nativeCheckInputs = with python3Packages; [ pytestCheckHook ]; disabledTests = [ # stub tests that always fail "TestCycloneDXGenerator" "TestCcycloneDX_parser" "TestGenerator" "TestOutput" "TestParser" "TestSPDX_Generator" "TestSPDX_Parser" # tests with missing getters "test_set_downloadlocation" "test_set_homepage" "test_set_checksum" "test_set_externalreference" # checks for invalid return type "test_set_type" # wrong capilatization "test_set_supplier" "test_set_originator" ]; pythonImportsCheck = [ "lib4sbom" ]; meta = with lib; { description = "Library to ingest and generate SBOMs"; homepage = "https://github.com/anthonyharrison/lib4sbom"; license = licenses.asl20; maintainers = with maintainers; [ teatwig ]; }; } </ins>

Discussion:
Project description A Python library to create SBOM files in several formats including SPDX and CycloneDX. Metadata homepage URL: source URL: license: Apache-2.0 platforms: Python
The expression for this can probably be automatically generated with a tool like nix-init, would you be down to maintain this package if I add it to nixpkgs?
Here's a generated expression, I can't get the test to pass though.
Change:
<ins> diff --git a/Cargo.lock b/Cargo.lock index a52b978..092bc1d 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -2788,7 +2788,7 @@ checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3" [[package]] name = "std_detect" version = "0.1.5" -source = "git+https://github.com/tensorchord/stdarch.git?branch=avx512fp16#db0cdbc9b02074bfddabfd23a4a681f21640eada" +source = "git+https://github.com/rust-lang/stdarch.git?branch=master#d2b1a070afc72d9ba4df80e055109ede5fc0a81f" dependencies = [ "cfg-if", "libc", diff --git a/crates/detect/Cargo.toml b/crates/detect/Cargo.toml index b3ac782..c671c6a 100644 --- a/crates/detect/Cargo.toml +++ b/crates/detect/Cargo.toml @@ -4,6 +4,6 @@ version.workspace = true edition.workspace = true [dependencies] -std_detect = { git = "https://github.com/tensorchord/stdarch.git", branch = "avx512fp16" } +std_detect = { git = "https://github.com/rust-lang/stdarch.git", branch = "master" } ctor = "0.2.6" rustix.workspace = true </ins>

Discussion:
I was attempting to build 0.2.1 which relies on , and hit a build failure on (nixos-unstable via flakes). I add to my system flake . Steps to reproduce the behavior: into a rust compilation failure of the crate while building , which relies on. <details<summaryClick to view logs</summary</detailsI was able to build 0.2.1 successfully in the past, and there hasn't been an update to or recently, so I'm not sure why this is failing now. Perhaps I was relying on the build cache's copy of , and now I'm not? The error looks to be due to using an unstable rust library feature () while not using a nightly rust compiler. Did the default rust compiler used to build packages change recently? cargo-pgrx maintainers: pgvecto-rs maintainers: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Its most likely a version issue. Cargo pgrx is very version sensitive. Every minor upgrade is breaking. Ive been waiting for 1.0 to try to make the upgrade in nixpkgs otherwise we have to add and maitain every minor version. You cam try with a different version is you want and that might solve your problem. Sorry for not having a better solution than this unfortunately.
This seems to have been caused by an upgrade of rustc to 1.78 (from 1.77.2). I'll see if it can be patched in (or pgrx if that's the case).
Some more information I found: pgvecto-rs uses a fork of rust's crate (under the repo), which only has a single commit (): This commit has since been merged upstream The build is failing because of (you can see the devs trying to fix all the build failures in the commit history ) I think the easiest fix here would be to patch pgvecto-rs to use Rust's crate instead of the fork, which should work fine. I'll still have to investigate whether there were any other changes to the crate that could cause problems, but it seems to be a fairly small crate, so fingers crossed it doesn't.

Can you try my branch in PR It's based on commit , so it should be a drop-in replacement for nixos-unstable. Let me know on the PR if it works fine with Immich (perhaps backup first, but I don't think it should have problems).
Change:
''; postFixup = '' <del> makeWrapper ${electron_5}/bin/electron $out/bin/typora  </del> <ins> makeWrapper ${electron_8}/bin/electron $out/bin/typora  </ins> --add-flags $out/share/typora  "''${gappsWrapperArgs[@]}"  ${lib.optionalString withPandoc ''--prefix PATH : "${lib.makeBinPath [ pandoc ]}"''} 

Discussion:
Describe the Bug The Typora pkg cannot work: To Reproduce During the package installation, This message will occur: The URL cannot be reached.
anyone can solve the problem?

Describe the bug Current version 0.9.73 is broken (download link at least). To Reproduce Steps to reproduce the behaviour: -env -i typora ... ... Expected behaviour Typora installed successfully. Screenshots ! Additional context Maybe we should replace the deb package: ${version} by Notify maintainers Metadata /nix/store/5k0id2x2sqj9k7kb9f1jzf382mpn6b2r-nix-info copying path '/nix/store/5k0id2x2sqj9k7kb9f1jzf382mpn6b2r-nix-info' from ''... system: host os: multi-user?: sandbox: version: channels(root): channels(vutaliy): nixpkgs:
The version referenced is simply outdated and not available any more from upstream. Switching to the is no solution, as the contents may change without being visible through the file name, leading to a hash mismatch and breaking the build.
I tried updating to 0.9.89 with sha256 but the .deb has setuid for the chrome sandbox and with it builds, but crashes at startup.

Describe the bug Typora have released version 0.9.80 To Reproduce Steps to reproduce the behavior: -env -i typora old version compared to the latest version in their website :( Expected behavior The latest version should be installed Screenshots If applicable, add screenshots to help explain your problem. Additional context Add any other context about the problem here. Metadata Please run and paste the result. Maintainer information:
Can do :+1:
Hey, I just noticed that the current version 0.9.73 is broken (download link at least), I'll update it to 0.9.9.33.2. Edit: I just noticed that the url using the version is now broken all versions. We should replace the deb package: ${version} by Do you have a better idea?
Change:
dftfit = callPackage ../development/python-modules/dftfit { }; <ins> diagrams = callPackage ../development/python-modules/diagrams { }; </ins> diceware = callPackage ../development/python-modules/diceware { }; dicom2nifti = callPackage ../development/python-modules/dicom2nifti { };

Discussion:
Project description Generate architecture diagrams with python code. Allows for rapid iteration. Metadata homepage URL: source URL: license: mit platforms: linux, darwin This library requires graphviz (both native and the python library).
Change:
buildPythonPackage rec { pname = "pip-tools"; version = "6.12.1"; <del> format = "setuptools"; </del> <ins> format = "pyproject"; </ins> disabled = pythonOlder "3.7";

Discussion:
Steps to reproduce the behavior: <!-- Please @ people who are in the list of the offending package or module. If in doubt, check for whoever last touched something. -- (last updated the package in ) Please run and paste the result. Also relevant for .
Change:
<ins> diff --git a/bin/internal/shared.sh b/bin/internal/shared.sh index 75d9d3013e..657ad3cb78 100644 --- a/bin/internal/shared.sh +++ b/bin/internal/shared.sh @@ -245,7 +245,7 @@ function shared::execute() { # and will corrupt each others' downloads. # # SHARED_NAME itself is prepared by the caller script. -  upgrade_flutter 7< "$SHARED_NAME" +  # upgrade_flutter 7< "$SHARED_NAME" BIN_NAME="$(basename "$PROG_NAME")" case "$BIN_NAME" in </ins>

Discussion:
Package name: Flutter Latest released version: 3.19.0 <!-- Search your package here: --- Current version on the unstable channel: 3.16.7 Current version on the stable/release channel: 3.13.8 <!-- 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]:
Change:
runHook postCheck ''; <ins> dontWrapGApps = true; preFixup = '' makeWrapperArgs+=("''${gappsWrapperArgs[@]}") ''; </ins> meta = with lib; { homepage = "https://thetimelineproj.sourceforge.net/"; changelog = "https://thetimelineproj.sourceforge.net/changelog.html";

Discussion:
re , the package crashes with when a file dialog is opened (eg. file -open). The rest of the program seems to work. I tried adding wrapGAppsHook, gsettings-desktop-schemas, and glib, but none of those fixed it. I'm running awesome wm, nixos 21.11 cc
Some resources i found related to the error message: timeline sources does not have schemas files. maybe is not set correctly on your system do you know how to fix this issue?
That might be a issue (since it defaults to true for ). See similar issue with
other gnome stuff seems to work though
You need to use . Global intentionally will not contain schemas.
I did try wrapGAppsHook, but that didn't fix it. maybe I did it wrong?
As mentioned above, for Python packages, you might also need to disable .
I tried using and , and it still errors out
Change:
# This includes the complete source so the per-script derivations can run the tests. core = stdenv.mkDerivation rec { pname   = "bat-extras"; <del> version = "2024.02.12"; </del> <ins> version = "2024.07.10"; </ins> src = fetchFromGitHub { owner  = "eth-p"; repo   = "bat-extras"; rev    = "v${version}"; <del> hash   = "sha256-EPDGQkwwxYFTJPJtwSkVrpBf27+VlMd/nqEkJupHlyA="; </del> <ins> hash   = "sha256-6IRAKSy5f/WcQZBcJKVSweTjHLznzdxhsyx074bXnUQ="; </ins> fetchSubmodules = true; };

Discussion:
Steps to reproduce the behavior: bat-extras.batdiff error: builder for '/nix/store/5khnbkiiys0kr98zb11m5apy7vixk930-batdiff-' failed with exit code 2; last 10 log lines:
For full logs, run 'nix log /nix/store/5khnbkiiys0kr98zb11m5apy7vixk930-batdiff-'. $ nix log /nix/store/5khnbkiiys0kr98zb11m5apy7vixk930-batdiff- warning: The interpretation of store paths arguments ending in recently changed. If this command is now failing try again with '/nix/store/5khnbkiiys0kr98zb11m5apy7vixk930-batdiff-^*' Running phase: unpackPhase { "action": "setPhase", "phase": "unpackPhase" } unpacking source archive /nix/store/k43djnn6wrc88hkdn51l8hg48bngxqyi-bat-extras-2024.02.12 source root is bat-extras-2024.02.12 Running phase: patchPhase { "action": "setPhase", "phase": "patchPhase" } patching script interpreter paths in bin/batdiff bin/batdiff: interpreter directive changed from "#!/usr/bin/env bash" to "/nix/store/4bj2kxdm1462fzccRunning phase: updateAutotoolsGnuConfigScriptsPhase { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" } Running phase: checkPhase { "action": "setPhase", "phase": "checkPhase" }
[FAIL] version :: Mismatched STDERR snapshot. Totals: PASS: 0 / 1 FAIL: 1 / 1 console $ nix-shell -p nix-info --run "nix-info -m" system: host os: multi-user?: sandbox: version: nixpkgs: Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Related
Please test

Package name: bat-extras Latest released version: 2024-07-10 <!-- Search your package here: --- Current version on the unstable channel: 2024.02.12 Current version on the stable/release channel: 2024.02.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 <!-- 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]:
Change:
<ins> { lib, fetchFromGitHub, buildGoModule }: buildGoModule rec { pname = "goss"; version = "0.3.16"; src = fetchFromGitHub { owner = "aelsabbahy"; repo = pname; rev = "v${version}"; sha256 = "1m5w5vwmc9knvaihk61848rlq7qgdyylzpcwi64z84rkw8qdnj6p"; }; vendorSha256 = "1lyqjkwj8hybj5swyrv6357hs8sxmf4wim0c8yhfb9mv7fsxhrv7"; CGO_ENABLED = 0; preBuild = '' buildFlagsArray+=("-ldflags" "-s -w -X main.version=v${version}") ''; meta = with lib; { homepage = "https://github.com/aelsabbahy/goss/"; changelog = "https://github.com/aelsabbahy/goss/releases/tag/v${version}"; description = "Quick and easy server validation"; longDescription = '' Goss is a YAML based serverspec alternative tool for validating a server’s configuration. It eases the process of writing tests by allowing the user to generate tests from the current system state. Once the test suite is written they can be executed, waited-on, or served as a health endpoint. ''; license = licenses.asl20; platforms = platforms.linux; maintainers = with maintainers; [ hyzual jk ]; }; } </ins>

Discussion:
Project description is a server validation tool. It lets you write assertions in YAML format and runs them really fast to ensure your server matches them, for example it lets you assert some binary is present in path or some command gives an expected result, or that some port is open, etc. I personally use it a lot to test docker images through its sub-project , for which I'll submit another request. Metadata homepage URL: source URL: license: Apache License 2.0 platforms: linux. Darwin and windows support is alpha (see the )
Per request I am bringing up the question here from : should we split into a separate package ? I assumed that since they are different binaries, they would need different packages. Both and are built and released together in the same github repository. depends on , but may be used without it.
Change:
<del> { mkDerivation, lib, fetchFromGitHub, pkg-config, cmake, qtbase, qttools , seafile-shared, jansson, libsearpc , withShibboleth ? true, qtwebengine }: </del> <ins> { lib , stdenv , fetchFromGitHub , pkg-config , cmake , qtbase , qttools , libuuid , seafile-shared , jansson , libsearpc , withShibboleth ? true , qtwebengine , wrapQtAppsHook }: </ins> <del> mkDerivation rec { </del> <ins> stdenv.mkDerivation rec { </ins> pname = "seafile-client"; <del> version = "8.0.7"; </del> <ins> version = "9.0.2"; </ins> src = fetchFromGitHub { owner = "haiwen"; repo = "seafile-client"; <del> # Tag v8.0.7 used to point to this commit, but was re-tagged later to a state # that fails to link properly rev = "8b96abf64e6aa19e3beeff6b322bcd6d28120bdd"; sha256 = "00wfr7dvbyl7pg1xgssgz8a94c7c4n5r9266lhy9qcbz456hdcgj"; </del> <ins> rev = "v${version}"; sha256 = "sha256-6AsvqlXDmTr3yBvYlV/0qjH+KnZ03S5TU7yzGt0MqiI="; </ins> }; <del> nativeBuildInputs = [ pkg-config cmake ]; buildInputs = [ qtbase qttools seafile-shared jansson libsearpc ] ++ lib.optional withShibboleth qtwebengine; </del> <ins> nativeBuildInputs = [ libuuid pkg-config cmake wrapQtAppsHook qttools ]; buildInputs = [ seafile-shared jansson libsearpc ] ++ lib.optional withShibboleth qtwebengine; </ins> <del> cmakeFlags = [ "-DCMAKE_BUILD_TYPE=Release" ] ++ lib.optional withShibboleth "-DBUILD_SHIBBOLETH_SUPPORT=ON"; </del> <ins> cmakeFlags = lib.optional withShibboleth "-DBUILD_SHIBBOLETH_SUPPORT=ON"; </ins> qtWrapperArgs = [ "--suffix PATH : ${lib.makeBinPath [ seafile-shared ]}"

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: legacyPackages.x86_64-linux.seafile-client <!-- 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: 8.0.7 desired version: 8.0.10 <!-- 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.