jiebi/CodeConvo huggingface dataset:
Change:
{ lib , mkDerivation , variant ? "standalone" <del> , fetchFromGitHub </del> <ins> , fetchzip , fetchpatch </ins> , cmake , pkg-config , ninja

Discussion:
We broke gmic-qt during the bump. After contacting upstream, it seems like the cmake build is not maintained anymore: They migrated to . We should align with them and rewrite a qmake derivation for gmic-qt. Edit: jtojnar advise not to migrate to qmake but instead fix the cmake issue.
Any idea what I can do so I can build my system while this is a WIP?
Install the build from an older version of nixpkgs where the package you want still builds properly. The version in branch should be building properly. For Flakes: For Non-Flake:
Thank you so much!! That section of the wiki described exactly what I was trying to do!
I just posted an upstream PR to fix this:
I've opened with a proper fix if anyone here would like to do some testing (it works for me now)

Steps to reproduce the behavior: Full log: Package built successfully in . Package failed in . I assume package failed to built somewhere in between these two pull request. Please run and paste the result.
Possibly needs update like
tried but had a compilation issue: Error:
Change:
name = "lua-arch.patch"; }; <ins> CVE_2019_6706 = fetchpatch { url = "https://gitlab.alpinelinux.org/alpine/aports/raw/7ad58d2fec12ba6086e2774460d4bfe9e91471a9/main/lua5.3/CVE-2019-6706-use-after-free-lua_upvaluejoin.patch"; sha256 = "11pqpwiydaw2nyjj30rn3k61apy6c4f4f5ahnnk69a9mmxig1nnc"; name = "CVE-2019-6706.patch"; }; </ins> in rec { lua5_3 = callPackage ./interpreter.nix { sourceVersion = { major = "5"; minor = "3"; patch = "5"; }; hash = "0c2eed3f960446e1a3e4b9a1ca2f3ff893b6ce41942cf54d5dd59ab4b3b058ac"; <del> patches = lib.optionals stdenv.isDarwin [ ./5.2.darwin.patch ] ; </del> <ins> patches = lib.optionals stdenv.isDarwin [ ./5.2.darwin.patch ] ++ [ CVE_2019_6706 ]; </ins> postConfigure = lib.optionalString (!stdenv.isDarwin) '' cat ${./lua-5.3-dso.make} >> src/Makefile sed -e 's/ALL_T *= */& $(LUA_SO)/' -i src/Makefile

Discussion:
, (nixos-unstable) Scanned versions: nixos-unstable: . May contain false positives.
Still no new release from upstream. Looks like the discussion sort of fizzled out: Ubuntu and RHEL apply a patch for this, see for example:
Should be backported as well.
Looks like the patch was applied to unstable and backported to 19.09. Can we close this issue?
Change:
) machine.succeed(f"ipfs cat /ipfs/{ipfs_hash.strip()} | grep fnord") <ins> ipfs_hash = machine.succeed( "echo fnord2 | ipfs --api /unix/run/ipfs.sock add | awk '{ print $2 }'" ) machine.succeed( f"ipfs --api /unix/run/ipfs.sock cat /ipfs/{ipfs_hash.strip()} | grep fnord2" ) </ins> ''; })

Discussion:
Describe the bug IPFS module should use upstream systemd files for socket-based activation. Right now we have a custom service file that is different from the one in ipfs-go 0.5.0. This is something quickly I can do. /cc
Change:
libkate libtiger libv4l samba libssh2 liboggz libass libdvbpsi libva xorg.xlibsWrapper xorg.libXv xorg.libXvMC xorg.libXpm xorg.xcbutilkeysyms libdc1394 libraw1394 libopus libebml libmatroska libvdpau libsamplerate <del> fluidsynth wayland wayland-protocols </del> <ins> fluidsynth wayland wayland-protocols ncurses </ins> ] ++ optional (!stdenv.hostPlatform.isAarch64) live555 ++ optionals withQt5    [ qtbase qtsvg qtx11extras ] ++ optionals skins2Support (with xorg; [ libXpm freetype libXext libXinerama ])

Discussion:
Looks like the package doesn't provide ?
Wasn't this fixed by ?
Er, yes, I thought "resolving " would automatically close it. Guess not.
Change:
buildInputs = [ sane-backends #for libsane.so.1 <del> jdk11 </del> ] ++ extraBuildInputs; nativeBuildInputs = [

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: pdfstudio name: pdfstudioviewer <!-- 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: 2021.2.0 desired version: 2022.x.x <!-- 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.
Just purchased license for this product but can't use it as it's a 2022 license. Thanks for your help!
Change:
zlib lmdb curl <ins> sqlite </ins> wxGTK32 ];

Discussion:
Package name: tqsl Latest released version: 2.7.2 <!-- Search your package here: --- Current version on the unstable channel: 2.6.5 Current version on the stable/release channel: 2.6.5 <!-- 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! --- I belive this could also be changed to pull from the SourceForge git repo for TQSL rather than pulling the compressed tarball from the ARRL site. This should then allow automatic updates based on the "vX.Y.Z" semver tags in the repo. 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:
meta = with lib; { homepage = "https://www.cockroachlabs.com"; description = "Scalable, survivable, strongly-consistent SQL database"; <del> license = licenses.bsl11; </del> <ins> license = with licenses; [ bsl11 mit cockroachdb-community-license ]; </ins> platforms = [ "aarch64-linux" "x86_64-linux" ]; maintainers = with maintainers; [ rushmorem thoughtpolice ]; };

Discussion:
Cockroachdb releases 23.1 and newer will stop using BSL and instead use the proprietary CockroachDB licenses. Please update to reflect that.
IIUC BSL is not replaced but CockroachDB license is now on top.
Change:
, fetchFromGitHub , rustPlatform , installShellFiles <del> , fetchpatch </del> , tinycc , libiconv , libobjc

Discussion:
Deno no longer working on darwin due to tinycc being broken. error: Package ‘tcc-0.9.27+date=2022-01-11’ in /nix/store/4la4fc5wfn4p0784i12h0a046yqzln16- is marked as broken, refusing to evaluate. It works. Looks like this happened with the move to Deno 1.23.4: Issue related to tinycc being broken: deno: tinycc:
Thanks for raising this. I shouldn't have missed this. I'll try fix tinycc and if we can't Mac might be able to fall back to the same non-tinycc method (even if it has some performance penalties) until they migrate to asm
Thanks for being on this
if you could try out that'd be helpful
i'm on it!
succeeded for me on x86_64-darwin
Nice, it worked for me in my x8664-darwin vm but it's always good to get it checked on real hardware. Would be nice to have someone try it on aarch64-darwin As a note if you want to do a "full" test of the FFI features (the one that requires tcc now) git clone /tmp/deno cd /tmp/deno mkdir -p ./target/result cp /location/of/the/nixpkgs/result/bin/deno ./target/result/ target/release/deno bench --allow-ffi --allow-read --unstable
Ran it on my aarch64-darwin machine:
fantastic thanks
also worked for me on aarch64 (i used an EC2 m1 macos instance). Unfortunately running the FFI tests requires a to be in the directory, which I noticed is output when running outside of nix. However, on aarch64, I can't get a direct to succeed...
sorry I missed a step there try if you still have the instance
cool, that worked.

the benchmarks ran without error...
Reopening as does not resolve this issue
That PR does resolve the issue, see the comments towards the bottom to pull in the fix early The unstable channel hasn't progressed for and not in scope for this issue ~I will open a backport ticket for 22.05 though~ actually is on which is unaffected by this issue
Yes, this is confirmed by ofborg.
OMG Sorry that I didn't follow the PR correctly. Not only I missed the part you fixed on the derivation of deno, but I saw the tinycc's derivation flagged as and mistook that it is the same on deno's. The old message of the beginning of the PR ("tinycc darwin issues were a pain, there's no point holding up this update since it's already broken") also made me confused and gave an idea that this issue was closed by mistake. Sorry for confusing everyone here, and thank you very much for fixing the problem!
I'd pretty much given up on trying to make tinycc build properly on darwin but as a last-ditch effort I tried just building the static lib on it's own and to my surprise it worked just fine
Change:
<ins> { lib , boost , fetchFromGitHub , libsodium , nix , pkg-config , rustPlatform }: rustPlatform.buildRustPackage rec { pname = "harmonia"; version = "0.2.0"; src = fetchFromGitHub { owner = "helsinki-systems"; repo = pname; rev = "refs/tags/${pname}-v${version}"; hash = "sha256-deqF6xDz3oCA1W8X8U1FD1gPYfxinZzpSuRKyaPDN/Y="; }; cargoHash = "sha256-eur3tg2w2WTA+JkOwTLwQzDZX7QN2xV4K0FIn7JN/rM="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ boost libsodium nix ]; meta = with lib; { description = "Nix binary cache"; homepage = "https://github.com/helsinki-systems/harmonia"; license = licenses.mit; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
Project description Metadata homepage URL: source URL: license: mit platforms: linux
I no longer request this package because I figured out that my nix-serve-ng issue was not caused by nix-serve-ng but rather nix-serve's in combination with instead of the correct
Change:
stdenv.mkDerivation (finalAttrs: { pname = "mdds"; <del> version = "2.1.0"; </del> <ins> version = "2.0.3"; </ins> src = fetchFromGitLab { owner = "mdds"; repo = "mdds"; rev = finalAttrs.version; <del> hash = "sha256-RZ2wGwle4raWlogc5X+VEeriPGS0Nqs7CWGENFEotvs="; </del> <ins> hash = "sha256-Y9uBJKM34UTEj/3c1w69QHhvwFcMNlAohEco0O0B+xI="; </ins> }; nativeBuildInputs = [ autoreconfHook ];

Discussion:
Steps to reproduce the behavior: libreoffice-fresh off master 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.
Is this issue closed because it is solved? It's still happening to me: If I include in my config, fails with the message . If I exclude from my config, rebuilding succeeds. I'm using the channel.
Yes, it's just that the commit hasn't arrived yet at nixos-unstable, see .
Change:
buildPythonPackage rec { pname = "smartdc"; <del> version = "0.1.12"; </del> <ins> version = "0.2.0"; </ins> src = fetchPypi { inherit pname version; <del> sha256 = "36206f4fddecae080c66faf756712537e650936b879abb23a8c428731d2415fe"; </del> <ins> sha256 = "6ffd866fb98386324e189e24d4f7532f66c1b20eece35ca1a6cb4b2a2639fc85"; </ins> }; propagatedBuildInputs = [ requests http_signature ];

Discussion:
Ran . For some reason there are pylint tests running for ~8 minutes that eventually end up in a failure. <details<summaryPyLint test failures</summary</detailson pylint (indirectly?); running for ~10 minutes as part of package installation process.
This will need to be backported to 18.09 as the latest version released by Hydra is broken too
The tests still fails even after the above patch applied. <details<summaryHere is the log</summary</detailsHere is the patch I used: Edit: the original patch is working on the python-unstable branch so I guess it's OK
I pushed a fix to the branch: . The fix for is currently in the branch: .
Change:
<ins> { lib , btrfs-progs , buildGoModule , fetchFromGitHub , lvm2 , pkg-config }: buildGoModule rec { pname = "kubeclarity"; version = "2.18.0"; src = fetchFromGitHub { owner = "openclarity"; repo = pname; rev = "refs/tags/v${version}"; hash = "sha256-qXBD3JurBU7RBemj+gr/tBGpfqKhwk5VPBKaTuM4URg="; }; vendorHash = "sha256-L7g48EH3cuhgSZ87JoMVvv5nGDzjUpOufsikINCdhao="; nativeBuildInputs = [ pkg-config ]; buildInputs = [ btrfs-progs lvm2 ]; sourceRoot = "${src.name}/cli"; ldflags = [ "-s" "-w" ]; postInstall = '' mv $out/bin/cli $out/bin/kubeclarity ''; meta = with lib; { description = "Kubernetes runtime scanner"; longDescription = '' KubeClarity is a vulnerabilities scanning and CIS Docker benchmark tool that allows users to get an accurate and immediate risk assessment of their kubernetes clusters. Kubei scans all images that are being used in a Kubernetes cluster, including images of application pods and system pods. ''; homepage = "https://github.com/openclarity/kubeclarity"; changelog = "https://github.com/openclarity/kubeclarity/releases/tag/v${version}"; license = with licenses; [ asl20 ]; maintainers = with maintainers; [ fab ]; }; } </ins>

Discussion:
<!-- Note that these are hard requirements --<!-- You can use the "Go to file" functionality on GitHub to find the package Then you can go to the history for this package Find the latest "packagename: oldversion -newversion" commit The "newversion" is the current version of the package --- <!-- Type the name of your package and try to find an open pull request for the package If you find an open pull request, you can review it! There's a high chance that you'll have the new version right away while helping the community! --- name: kubei <!-- 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.0.12 desired version: 2.9.0 <!-- Search your package here: If no maintainer is listed for your package, tag the person that last updated the package --maintainers: Please tag this issue in your PR.
Change:
function gitea_setup { cp -f ${configFile} ${runConfig} <del> if [ ! -e ${secretKey} ]; then </del> <ins> if [ ! -s ${secretKey} ]; then </ins> ${gitea}/bin/gitea generate secret SECRET_KEY > ${secretKey} fi # Migrate LFS_JWT_SECRET filename <del> if [[ -e ${oldLfsJwtSecret} && ! -e ${lfsJwtSecret} ]]; then </del> <ins> if [[ -s ${oldLfsJwtSecret} && ! -s ${lfsJwtSecret} ]]; then </ins> mv ${oldLfsJwtSecret} ${lfsJwtSecret} fi <del> if [ ! -e ${oauth2JwtSecret} ]; then </del> <ins> if [ ! -s ${oauth2JwtSecret} ]; then </ins> ${gitea}/bin/gitea generate secret JWT_SECRET > ${oauth2JwtSecret} fi <del> if [ ! -e ${lfsJwtSecret} ]; then </del> <ins> if [ ! -s ${lfsJwtSecret} ]; then </ins> ${gitea}/bin/gitea generate secret LFS_JWT_SECRET > ${lfsJwtSecret} fi <del> if [ ! -e ${internalToken} ]; then </del> <ins> if [ ! -s ${internalToken} ]; then </ins> ${gitea}/bin/gitea generate secret INTERNAL_TOKEN > ${internalToken} fi

Discussion:
I setup the server quite a while ago. I recognized that the service is not running. As I normally do auto update I saw that the process failed as the configuration changed. After rebuild + switch the service fails to start: Steps to reproduce the behavior: Service be able to start. I tried to 1) chmod +w -still fails and permissions are somehow adjusted 2) delete -file is created, startup still fails
Digged a little bit deeper: The error is thrown by the pre-start script. It seems that my installation is missing the which causes some gitea command to generate it and write it into . Which fails as the file is set to non writable by the pre-start script.
Change:
meta = with lib; { description = "ElectronMail is an Electron-based unofficial desktop client for ProtonMail"; homepage = "https://github.com/vladimiry/ElectronMail"; <del> license = licenses.mit; </del> <ins> license = licenses.gpl3; </ins> maintainers = [ maintainers.princemachiavelli ]; platforms = [ "x86_64-linux" ]; };

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: electron-mail <!-- 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: 4.14.0 desired version: 5.0.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.
Change:
<del> { appimageTools , lib , fetchurl }: let pname = "nuclear"; version = "0.6.30"; src = fetchurl { url = "https://github.com/nukeop/nuclear/releases/download/v${version}/${pname}-v${version}.AppImage"; hash = "sha256-he1uGC1M/nFcKpMM9JKY4oeexJcnzV0ZRxhTjtJz6xw="; }; appimageContents = appimageTools.extract { inherit pname version src; }; in appimageTools.wrapType2 { inherit pname version src; extraInstallCommands = '' install -m 444 -D ${appimageContents}/${pname}.desktop -t $out/share/applications substituteInPlace $out/share/applications/${pname}.desktop  --replace 'Exec=AppRun' 'Exec=${pname}' cp -r ${appimageContents}/usr/share/icons $out/share ''; meta = with lib; { description = "Streaming music player that finds free music for you"; homepage = "https://nuclear.js.org/"; license = licenses.agpl3Plus; maintainers = [ maintainers.NotAShelf ]; platforms = [ "x86_64-linux" ]; mainProgram = "nuclear"; }; } </del>

Discussion:
Package name: nuclear Latest released version: 0.6.31 Current version on the unstable channel: 0.6.30 Current version on the stable/release channel: 0.6.30 <!-- 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]:
Made a PR, would appreciate it if you tested it - I don't use nuclear very often at the moment.
Change:
final Uri entryUri = _fileSystem.path.toUri(asset); result.add(_Asset( -          baseDir: _fileSystem.path.join(Cache.flutterRoot!, 'bin', 'cache', 'artifacts', 'material_fonts'), <del> +          baseDir: _fileSystem.path.join(globals.fsUtils.homeDirPath!, 'bin', 'cache', 'artifacts', 'material_fonts'), </del> <ins> +          baseDir: _fileSystem.path.join(globals.fsUtils.homeDirPath!, '.cache', 'flutter', 'artifacts', 'material_fonts'), </ins> relativeUri: Uri(path: entryUri.pathSegments.last), entryUri: entryUri, package: null,

Discussion:
Running fails with the following error: The issue is here: Before the 2.8.0 update, this line used to say So, flutter copied the cache to , which was fine. Now, however, it tries to copy the cache to , which doesn't exist, so flutter throws an error. Steps to reproduce the behavior: do any flutter project `flutter run Flutter builds the app and runs it on the device Please run and paste the result. I cannot run it because I use flakes, so it just says .
My bad, it should be fixed by
thanks!
Change:
sha256 = "sha256-YNAfHmohMqGGF8N/VdndJJ32PF/GMBoNtjo/t2lt6HA="; }; buildInputs = [ zlib openssl ]; <ins> nativeBuildInputs = [ cmake ]; </ins> makeFlags = [ "USE_ZLIB=1" "USE_OPENSSL=1" "PREFIX=$(out)" ] ++ lib.optional (stdenv.cc.cc != null) "SYSROOT_ALT=${stdenv.cc.cc}" ++ lib.optional (stdenv.cc.libc != null) "SYSROOT=${lib.getDev stdenv.cc.libc}" ; <ins> enableParallelBuilding = true; </ins> meta = { description = "A library for real-time communications with async IO support and a complete SIP stack"; homepage = "https://github.com/baresip/re";

Discussion:
Baresip fails to build after because the baresip no longer finds librem through pkg-config. Building baresip with Cmake resolves this, but then there is a new build failure: Steps to reproduce the behavior: baresip
Sorry! I think fixes this. I developed and tested them together but wanted to take more time to be sure baresip was finding all of its dependencies. I didn't realize that merging one without the other would break things. We can either merge or else revert and
Waiting for is fine by me.
Change:
url = "https://github.com/mobile-shell/mosh/commit/e5f8a826ef9ff5da4cfce3bb8151f9526ec19db0.patch"; sha256 = "15518rb0r5w1zn4s6981bf1sz6ins6gpn2saizfzhmr13hw4gmhm"; }) <ins> # Fix build with bash-completion 2.10 ./bash_completion_datadir.patch </ins> ]; postPatch = '' substituteInPlace scripts/mosh.pl 

Discussion:
Describe the bug A clear and concise description of what the bug is. The package fails to build. It errors out during the installation of bash completions with "Permissions denied". To Reproduce Steps to reproduce the behavior: -build -A mosh Expected behavior Successful build Notify maintainers Metadata on Maintainer information:
The breaking commit is the bash-completion update from 2.9 to 2.10: . Any idea how to resolve this?
I think you meant to link . Seems to be a regression from incorrectly dropping by ( in ). The "wrong" prefix comes from . A possible alternative would be to drop the dependency on for (if there's a correct fallback - since we don't actually the prefix from anyway).
I think removing this patch was correct, as the functionality introduced in that patch was to 2.10, however a program needs to define instead of when reading variable, which may necessitate patches (which could be upstreamed). It's unfortunate that the upstream decided on different approach than what was done previously, but trying to preserve the old behaviour would cause more issues in long-term. Let's not overcomplicate things when some of upstream projects already have code that uses when using = 2.10. I imagine this is the line that needs changing:
sorry, my assumption about the patch was wrong then :o And thanks for the fix :) Edit: And I agree that we should follow upstream then.
Change:
nativeBuildInputs = lib.optionals enableQt [ wrapQtAppsHook ]; buildInputs = lib.optional (stdenv.isLinux && enableQt) qtwayland; <del> propagatedBuildInputs = with python3.pkgs; [ </del> <ins> propagatedBuildInputs = with python.pkgs; [ </ins> aiohttp aiohttp-socks aiorpcx

Discussion:
Cannot use hardware wallet with electrum from nixos-unstable channel Steps to reproduce the behavior: to use hardware wallet with electrum (either via creating wallet or loading a wallet) :x: on "Choose Hardware Device" screen, be presented with debug error A list of connected hardware wallets when at least one is connected ! Issue is not present in package from nixos-23.11 channel hardware wallet used: Ledger Nano X Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]: