jiebi/CodeConvo huggingface dataset:
Change:
cz-cli = callPackage ../applications/version-management/cz-cli { }; <ins> czkawka-full = czkawka.wrapper.override { extraPackages = [ ffmpeg ]; }; </ins> comma = callPackage ../tools/package-management/comma { }; commitizen = with python3Packages; toPythonApplication commitizen;

Discussion:
The czkawka package is missing ffmpeg as a dependency. If ffmpeg is not found you get this error when trying to compare video files: Ignore the snap part, it throws this error when it can't find ffmpeg, regardless if snap or not. 't have ffmpeg installed on you system. comparing videos in czkawka throws error ffmpeg error. Just works. No error. Just works. First issue I've reported here, hopefully I'm doing this right. <!-- 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]:
Before I propose any changes, let me know a thing or two. When you install both ffmpeg and czkawka, then czkawka finds ffmpeg, correct?
Correct. It finds it no problem.
Change:
# and https://github.com/patjak/bcwc_pcie/blob/5a7083bd98b38ef3bd223f7ee531d58f4fb0fe7c/firmware/extract-firmware.sh # From the Makefile: <del> dmgUrl = "https://support.apple.com/downloads/DL1877/en_US/osxupd10.11.5.dmg"; dmgRange = "205261917-208085450"; # the whole download is 1.3GB, this cuts it down to 2MB </del> <ins> dmgUrl = "https://updates.cdn-apple.com/2019/cert/041-88431-20191011-e7ee7d98-2878-4cd9-bc0a-d98b3a1e24b1/OSXUpd10.11.5.dmg"; dmgRange = "204909802-207733123"; # the whole download is 1.3GB, this cuts it down to 2MB </ins> # Notes: # 1. Be sure to update the sha256 below in the fetch_url # 2. Be sure to update the homepage in the meta

Discussion:
I don't really know why my system configuration for an XPS 13 is pulling this in, either: EDIT: I had set in my system configuration, thus causing me to (fail to) build .
I have the same problem on 3 laptops As mentioned in above post issue is related to enableAllFirmware = true; Chnaging to enableRedistributableFirmware = true; fixed the issue for now another example
cc maintainers:
I think, the new url could be found on this page
I'll try to find time over the weekend to update new offsets and hashes for the new download path. In the meantime, facetimehd users can extract the firmware from their OSX partition with this override: ``
See
Change:
{ config, stdenv, lib, fetchurl, pkgconfig, zlib, expat, openssl, autoconf , libjpeg, libpng, libtiff, freetype, fontconfig, libpaper, jbig2dec <del> , libiconv, ijs </del> <ins> , libiconv, ijs, fetchpatch </ins> , cupsSupport ? config.ghostscript.cups or (!stdenv.isDarwin), cups ? null , x11Support ? cupsSupport, xlibsWrapper ? null # with CUPS, X11 only adds very little }:

Discussion:
, (nixos-unstable, nixos-19.03, nixos-18.09) Scanned versions: nixos-unstable: ; nixos-19.03: ; nixos-18.09: . May contain false positives.

Can't simply apply the upstream commits, unfortunately (AFAICT). This looks pretty serious!
Thank you!! :sparkle:
Change:
# Wait until server accepts connections machine.wait_until_succeeds("curl -fs localhost:28981") <del> with subtest("Document is consumed"): </del> <ins> with subtest("Create web test doc"): machine.succeed( "convert -size 400x40 xc:white -font 'DejaVu-Sans' -pointsize 20 -fill black " "-annotate +5+20 'hello web 16-10-2005' /tmp/webdoc.png" ) machine.wait_until_succeeds("curl -u admin:admin -F document=@/tmp/webdoc.png -fs localhost:28981/api/documents/post_document/") with subtest("Documents are consumed"): </ins> machine.wait_until_succeeds( <del> "(($(curl -u admin:admin -fs localhost:28981/api/documents/ | jq .count) == 1))" </del> <ins> "(($(curl -u admin:admin -fs localhost:28981/api/documents/ | jq .count) == 2))" </ins> ) assert "2005-10-16" in machine.succeed( "curl -u admin:admin -fs localhost:28981/api/documents/ | jq '.results | .[0] | .created'" ) <ins> assert "2005-10-16" in machine.succeed( "curl -u admin:admin -fs localhost:28981/api/documents/ | jq '.results | .[1] | .created'" ) </ins> ''; })

Discussion:
Whenever I try to add a document using the web ui, it uploads and then waits forever to finish processing. Looking at the log in the same UI, I see the following lines: And when doing I see that it fails with . This is clearly due to the in the services, instead we should share between the and services (and potentially the too?). Steps to reproduce the behavior: a document forever The document should upload and finish processing correctly, being readable accross services. Please run and paste the result. Maintainer information:
Change:
handleEvalWarning = { meta, attrs }: { reason , errormsg ? "" }: let remediationMsg = (builtins.getAttr reason remediation) attrs; <del> msg = if inHydra then "Warning while evaluating ${getName attrs}: «${reason}»: ${errormsg}" else "Package ${getName attrs} in ${pos_str meta} ${errormsg}, continuing anyway." </del> <ins> msg = if inHydra then "Warning while evaluating ${getNameWithVersion attrs}: «${reason}»: ${errormsg}" else "Package ${getNameWithVersion attrs} in ${pos_str meta} ${errormsg}, continuing anyway." </ins> + (optionalString (remediationMsg != "") "n${remediationMsg}"); isEnabled = findFirst (x: x == reason) null showWarnings; in if isEnabled != null then builtins.trace msg true else true;

Discussion:
When running it fails due to an insecure package. To resolve this the output of recommends adding to the file (in my case for electron) This is incorrect as the correct line that should be must contain the package name and ver sion instead of just the package name (eg: instead of ) Steps to reproduce the behavior: while having an insecure package the instructions in the output The output must specify instead of in the sample code. This is the current (wrong) full output
Change:
with: # This cache is for the nixpkgs repo checks and should not be trusted or used elsewhere. name: nixpkgs-ci <del> signingKey: '${{ secrets.CACHIX_SIGNING_KEY }}' </del> <ins> authToken: '${{ secrets.CACHIX_AUTH_TOKEN }}' </ins> - name: Building NixOS manual run: NIX_PATH=nixpkgs=$(pwd) nix-build --option restrict-eval true nixos/release.nix -A manual.x86_64-linux

Discussion:
Visit: All build jobs keep failing. Since ~20:00 UTC Yesterday (03.04.2024) Log says: Add any other context about the problem here. Please run and paste the result. Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
IIRC you created this cachix cache and the token for us.
Change:
mod_timestamp = apacheHttpdPackages.mod_timestamp; inherit (callPackages ../servers/mpd { <del> stdenv = if (with stdenv; cc.isClang && isx86_64) then llvmPackages_8.stdenv else stdenv; </del> inherit (darwin.apple_sdk.frameworks) AudioToolbox AudioUnit; }) mpd mpd-small mpdWithFeatures;

Discussion:
mpd is failing to build both for me locally and on hydra: i have an old version of mpd installed, and im running . i see similar output about locally as appears in the hydra build
Change:
immich-cli = callPackage ../tools/misc/immich-cli { }; <del> inherit (callPackages ../tools/networking/ivpn/default.nix {}) ivpn ivpn-service; </del> <ins> inherit (callPackage ../tools/networking/ivpn/default.nix {}) ivpn ivpn-service; </ins> jobber = callPackage ../tools/system/jobber { };

Discussion:
The NixOS tests for netbox are failing to evaluate: It seems like the module tries to override the package to pass in the plugins that are configured in the module, but for some reason it's overriding the function in instead of the one in . The former doesn't have a plugins argument, so that causes this error. You can also replicate this in : I don't really know what changed to cause this to happen, as it doesn't seem like it should. Steps to reproduce the behavior: The system configuration should evaluate. <!-- 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]:
Possibly related issue with an which used to work: Ping
The thing these packages have in common seems to be that they use to pull in a few different versions into . It seems like something changed about recently.
I think you're right, That commit changes to for a bunch of packages, including citrix_workspace and netbox.
Change:
sha256 = "142145a2whvlk92jijrbf3i2bqrzmspwpysj0bfypw0krzi0aa6j"; }; <ins> patches = [ (fetchpatch { url = "https://github.com/pygobject/pycairo/commit/678edd94d8a6dfb5d51f9c3549e6ee8c90a73744.patch"; sha256 = "sha256-HmP69tUGYxZvJ/M9FJHwHTCjb9Kf4aWRyMT4wSymrT0="; }) ]; </ins> nativeBuildInputs = [ meson ninja

Discussion:
Steps to reproduce the behavior: on latest ()
I encountered the exact same failure when building with python2 extensions. I found a that works for me. Please see if that works for you!
Change:
buildPythonPackage rec { pname = "flax"; <del> version = "0.6.3"; </del> <ins> version = "0.6.1"; </ins> src = fetchFromGitHub { owner = "google"; repo = pname; rev = "refs/tags/v${version}"; <del> sha256 = "sha256-4BYfrwEddA2LCMyDO6PBBYdMVTqqDxhzMCZ5JIIml3g="; </del> <ins> sha256 = "sha256-fZiODo+izOwGjCCTvi11GvUG/VQL1DV9bNXKjvIIw4A="; </ins> }; buildInputs = [ jaxlib ];

Discussion:
your commit broke due to Please test your changes with or at least before committing them to master. Can you please issue a fix by reverting your change and downgrading to 0.6.2? There is not currently a fix available upstream.
That commit is from the regular Python batch updates. While we try to fix as many build failures as possible we can't guarantee every package continues to work. I suggest you file a PR reverting that change.
I understand that python-updates is a messy process. But in the case that you do not know or do not test whether a package update will build successfully, please do not update it. There is no need to upgrade flax, and the risks of pushing untested code to master are simply much higher than the reward.
I think it would be a good idea to maintain a list of packages that shouldn't be updated in python-updates. Let's discuss that over at .
I think that's a great idea! will switch over to matrix
Change:
license = licenses.gpl2Plus; maintainers = with maintainers; [ uri-canva ]; platforms = platforms.unix; <del> broken = stdenv.hostPlatform.system == "aarch64-darwin"; </del> }; }

Discussion:
The package is not supported on Apple M1. It gives the following error message Steps to reproduce the behavior: on an Apple M1 Macbook. We should be able to build the package successfully. Add any other context about the problem here. Maintainer information:
Please run and report whether [ ] it builds without error [ ] produces a working binary Then we can simply add M1 to the list of supported platforms.
No. It does not build. It hits error when building . The outputs are
Change:
MODVERSIONS        = whenOlder "4.9" yes; MOUSE_ELAN_I2C_SMBUS = yes; MOUSE_PS2_ELANTECH = yes; # Elantech PS/2 protocol extension <ins> MOUSE_PS2_VMMOUSE  = yes; </ins> MTRR_SANITIZER     = yes; NET_FC             = yes; # Fibre Channel driver support # GPIO on Intel Bay Trail, for some Chromebook internal eMMC disks

Discussion:
In a NixOS 20.09 guest on a VMWare Windows host, with dwm as my window manager, the mouse cursor neither moves nor registers clicks when . To Reproduce Steps to reproduce the behavior: NixOS 20.09 in VMWare Workstation Player 16 VM (from the minimal ISO) xserver and dwm and in as normal user with a minimal can you have a look?
I can reproduce this. It does work if you login as but fails if you log into a normal user account. It also fails in .
Oh boy, even in the grown-up DM. That's bad.
Did this fix the issue for you? ? I'm having issues my self. I also posted in reddit to see if maybe I didn't do something correctly.
try the PR I just linked. My mouse problems went away when I compiled the kernel with CONFIGPS2VMMOUSE.
Thank you it works! This will be great to have. This might be a silly question, but is open-vm-tools 11.3.0 required for this to work? I didn't have time to try 11.2.5 on the stable channel. For anyone reading this the name value is MOUSEPS2VMMOUSE, might save you one failed kernel build before you figure it out. Here's my nix config that I used to allow non-root user to use the mouse in Xorg running on vmware fushion on MacOS - This config was a "get it to work" attempt with no regard to what the ramifications of how I went about it. My next step is to figure out what it all really means and see if I went about it correctly.
Change:
sha256 = "sha256-G1r7uY9sTcrbLirmq5+plLu4wddfT6ltNA+UN65FRAY="; }; <ins> dependencies = [ # setuptools in dependencies is intentional # https://github.com/ronaldoussoren/altgraph/issues/21 setuptools ]; </ins> pythonImportsCheck = [ "altgraph" ]; meta = with lib; {

Discussion:
Project description Freeze (package) Python programs into stand-alone executables. Metadata homepage URL: source URL: license: gpl2 platforms: unix, linux, darwin
I would love to see it packaged too.
So, I did some digging on previous attempts at and found some abandoned PRs: packaged in itself but got abandoned due to complexity. was in partial effort of packaging by packaging one of its dependencies. also as a dependency for another package . Perhaps someone coming to this issue looking for the package can try it themselves using these attempts as a base.
I would also love to figure out how to build pyinstaller projects as a nix derivation
I believe you're looking for ? This issue is requesting to package itself and not packaging projects using .
Change:
headscale = callPackage ../servers/headscale { }; <ins> health = callPackage ../applications/misc/health { }; </ins> healthchecks = callPackage ../servers/web-apps/healthchecks { }; heisenbridge = callPackage ../servers/heisenbridge { };

Discussion:
Project description Health can visualize how many steps you’ve made daily, your weight development over time and your daily activities. Data can be synched from Google Fit or manually entered into Health. Afterwards, it can be viewed and edited in Health. Metadata homepage URL: source URL: license: gpl3 platforms: linux
Change:
<del> { fetchurl, stdenv, pkgs, ... }: </del> <ins> { stdenv, fetchFromGitHub, buildPythonApplication , colorama, decorator, psutil, pyte, six , pytest, pytest-mock }: </ins> <del> pkgs.pythonPackages.buildPythonPackage rec { name = "${pname}-${version}"; </del> <ins> buildPythonApplication rec { </ins> pname = "thefuck"; <del> version = "3.18"; </del> <ins> version = "3.25"; </ins> <del> src = fetchurl { url = "https://github.com/nvbn/${pname}/archive/${version}.tar.gz"; sha256 = "1xsvkqh89rgxq5w03mnlcfkn9y39nfwhb2pjabjspcc2mi2mq5y6"; </del> <ins> src = fetchFromGitHub { owner = "nvbn"; repo = "${pname}"; rev = version; sha256 = "090mg809aac932lgqmjxm4za53lg3bjprj562sp189k47xs4wijv"; </ins> }; <del> propagatedBuildInputs = with pkgs.pythonPackages; [ psutil colorama six decorator pathlib2 ]; </del> <ins> propagatedBuildInputs = [ colorama decorator psutil pyte six ]; checkInputs = [ pytest pytest-mock ]; checkPhase = '' export HOME=$TMPDIR export LANG=en_US.UTF-8 export XDG_CACHE_HOME=$TMPDIR/cache export XDG_CONFIG_HOME=$TMPDIR/config py.test ''; doCheck = false; # The above is only enough for tests to pass outside the sandbox. </ins> meta = with stdenv.lib; { homepage = https://github.com/nvbn/thefuck;

Discussion:
has failing tests. Specifically, the tests seem to be failing because is no longer available. I traced back the issue to an update of , using : output: system: host os: multi-user?: sandbox: version: channels(root): channels(synthetica): nixpkgs:
Change:
, libsForQt5 , libtiff , qt6Packages <ins> , qt6 </ins> , rdma-core , ucx , rsync

Discussion:
Some cuda packages come with vendored copies of libraries that are already available in nixpkgs. These vendored libraries still require patching their Runpaths, their presence reduces determinism, and breaks "deep replacement" (i.e. nixpkgs' feature allowing to ensure that everything in a package set uses the same revision of a dependency). For instance, ships , which otherwise is available as: Cf. Tasks [ ] Look into deleting these vendored libraries and re-linking their reverse dependencies against nixpkgs alternatives
Change:
outputs = [ "out" ] ++ optionals buildUser [ "lib" "dev" ]; <del> passthru.tests = if isUnstable then [ nixosTests.zfs.unstable ] else [ nixosTests.zfs.installer nixosTests.zfs.stable ]; </del> <ins> passthru = { inherit enableMail; tests = if isUnstable then [ nixosTests.zfs.unstable ] else [ nixosTests.zfs.installer nixosTests.zfs.stable ]; }; </ins> meta = { description = "ZFS Filesystem Linux Kernel module";

Discussion:
Describe the bug On a ZFS-enabled 20.03 system: IMHO zed does not need the ability to send email by default. Also mariadb-connector should have a separate -dev output so that its doesn't end up in the system closure.
cc
Hello, I'm a bot and I thank you in the name of the community for opening this issue. To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human. The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it. If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use or on the relevant files to find them. Lastly, you can always ask for help at or at .
Seems still important: And: And:
Adjusted to milestone 21.03. BTW, If someone wants to backport the fix it shouldn't cause any issues.
Took a stab at this in
Change:
clf = callPackage ../development/python-modules/clf { }; <ins> cli-ui = callPackage ../development/python-modules/cli-ui { }; </ins> clip = callPackage ../development/python-modules/clip { }; clip-anytorch = callPackage ../development/python-modules/clip-anytorch { };

Discussion:
Project description Tbump helps you bump the version of your project easily. It is a simple cli. Metadata homepage URL: source URL: license: BSD 3-Clause platforms: Anything that run python Add a :+1: [reaction] to [issues you find important]. [reaction]: [issues you find important]:
Change:
<del> { lib , stdenv , fetchFromGitHub , cmake , asciidoc , pkg-config , libsodium , enableDrafts ? false </del> <ins> { lib, stdenv, fetchFromGitHub, cmake, pkg-config, libsodium, asciidoc, xmlto, enableDrafts ? false, # for passthru.tests azmq, cppzmq, czmq, zmqpp, ffmpeg, python3, </ins> }: <del> stdenv.mkDerivation rec { </del> <ins> stdenv.mkDerivation (finalAttrs: { </ins> pname = "zeromq"; version = "4.3.5"; src = fetchFromGitHub { owner = "zeromq"; repo = "libzmq"; <del> rev = "v${version}"; sha256 = "sha256-q2h5y0Asad+fGB9haO4Vg7a1ffO2JSb7czzlhmT3VmI="; </del> <ins> rev = "v${finalAttrs.version}"; hash = "sha256-q2h5y0Asad+fGB9haO4Vg7a1ffO2JSb7czzlhmT3VmI="; </ins> }; <del> nativeBuildInputs = [ cmake asciidoc pkg-config ]; </del> <ins> nativeBuildInputs = [ cmake pkg-config asciidoc xmlto ]; </ins> buildInputs = [ libsodium ]; doCheck = false; # fails all the tests (ctest) <del> cmakeFlags = lib.optional enableDrafts "-DENABLE_DRAFTS=ON"; </del> <ins> cmakeFlags = [ (lib.cmakeBool "WITH_LIBSODIUM" true) (lib.cmakeBool "ENABLE_CURVE" true) (lib.cmakeBool "ENABLE_DRAFTS" enableDrafts) ]; </ins> postPatch = '' substituteInPlace CMakeLists.txt 

Discussion:
The package providing is missing several features that other distributions enable by default. Some examples: Upstream Debian Packaging: Arch Linux Packaging: Fedora Packaging: Features like and should probably be enabled by default. I was expecting curve support from the package and even saw in the package's inputs, yet I ran into an on . See the unused input: See the ENOTSUP error here: An we should probably provide build options similar to the upstream RHEL packaging. See Most should probably be enabled by default. <!-- 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]:
I can work on this tomorrow, but I'd rather follow what : Certainly we need to enable the flag to use . About CurveZMQ, I'd say the best option is to provide an input flag as that can be overridden by those who prefer it.
Since we depend on anyway I don't think there is any harm in enabling CurveZMQ by default - even without a flag. Are there negative side effects when enabling CurveZMQ?
Sorry, I was confusing the CurveCP protocol, which is supported by enabling , with CurveZMQ, which is a CurveCP implementation but its a whole different library that depends on . There is no flag related to CurveZMQ on ZeroMQ. But we do need to enable the flag to build with CurveCP support. Yes, sure, if the flag doesn't apply to Nix then it will not be considered.
(Why it wasn't closed automatically if it was linked?)
Change:
stdenv.mkDerivation rec { pname = "twemoji-color-font"; <del> version = "12.0.1"; </del> <ins> version = "13.0.1"; </ins> # We fetch the prebuilt font because building it takes 1.5 hours on hydra. # Relevant issue: https://github.com/NixOS/nixpkgs/issues/97871 src = fetchurl { url = "https://github.com/eosrei/twemoji-color-font/releases/download/v${version}/TwitterColorEmoji-SVGinOT-Linux-${version}.tar.gz"; <del> sha256 = "1kdy2k7b1k7sjp2l8g10lp2v000iwk8i3wcwgkhqfbwrrj7dg1kq"; </del> <ins> sha256 = "1mn2cb6a3v0q8i81s9a8bk49nbwxq91n6ki7827i7rhjkncb0mbn"; </ins> }; dontBuild = true;

Discussion:
The package takes a long time to build the individual glyphs using . See also Other distros simply use the release tarball (e.g. AUR ) which already has the resulting 13 MB file prebuilt. Should we do this as well, given that it's a font? CC maintainer:
I'm conflicted: on one hand NixOS is a source based distribution and building from source makes it possible to apply patches and whatnot, but on the other it's just a font without any executable stuff and 1.5 hours is a lot. I guess it depends on how valuable build time is?
It seems quite common for fonts in nixpkgs to use the upstream-release-provided font files; examples I picked randomly by clicking around in : Some fonts are generated by a call to , for example , but there doesn't seem to be a requirement for that. So I propose to make one of the former category.
EDIT: confused with
Ow. Well, that's a good enough reason to switch I guess :) I'll open a pr. edit: or I could Increase the timeout :)
cc
I have a sentiment for source builds but no rational arguments. The above arguments for building from source are reasonable. We also have package for a bitmap version of the font (using build system from Noto). That artefact is not available upstream so we need to build it ourselves, unless we want to depend on Fedora.
Yeah, I'm similar (at least for fonts, outside fonts there's many rational arguments :rofl: ). And I think considering how it times out... It's the best choice for now as there's not a ton of benefit to argue. Though doesn't seem to be incredibly difficult to do :frowning_face.
I think in practice this is still not going to address the root issue that the calling of inkscape is highly inefficient. Hehe, I bet nix being content addressed would make a lot of us much happier with not having to rebuild stuff pointlessly.
I'm sorry, I confused the two packages. It's apparently the other one that's timing out on Hydra:
Even with the 5x speedup I found in it'd still take 20 minutes to build it though. If somebody goes through the effort of fixing it upstream, we may want to consider switching back to fully-from-source.

But there are 1000s of open-source tasks higher than this on my list :)
Can relate. (says ever opensource contributor ever while submitting 10x README PRs in a day :grin: )