Package Details: czkawka-cli 12.0.0-1

Git Clone URL: https://aur.archlinux.org/czkawka.git (read-only, click to copy)
Package Base: czkawka
Description: Multi functional app to find duplicates, empty folders, similar images etc. (CLI)
Upstream URL: https://github.com/qarmin/czkawka
Licenses: LicenseRef-MIT
Submitter: fabiscafe
Maintainer: fabiscafe
Last Packager: fabiscafe
Votes: 47
Popularity: 1.61
First Submitted: 2021-08-09 09:49 (UTC)
Last Updated: 2026-06-28 18:36 (UTC)

Pinned Comments

fabiscafe commented on 2024-02-20 20:54 (UTC) (edited on 2026-06-28 18:24 (UTC) by fabiscafe)

Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!
Looking for a new maintainer!

fabiscafe commented on 2023-06-11 14:41 (UTC) (edited on 2026-06-28 18:24 (UTC) by fabiscafe)

Key Import

This PKGBUILD uses signed commits. If not done you need to import GitHubs (web-flow) public pgp key.

curl -sS https://github.com/web-flow.gpg | gpg --import -
Build Instructions
$ curl -sS https://github.com/web-flow.gpg | gpg --import -
# pacman -S git devtools --needed
$ git clone https://aur.archlinux.org/czkawka.git
$ cd czkawka
$ pkgctl build .

Latest Comments

1 2 3 4 5 Next › Last »

fabiscafe commented on 2026-07-05 10:04 (UTC)

hi @j1simon, as long as czkawka-gui builds, I don't see any reason to not build it. This is a source package. For this reason we don't have to care what upstream provides in binary form. :)

I've already set it to deprecated in https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=czkawka#n85

For the request, I'll email you.

j1simon commented on 2026-07-05 07:33 (UTC) (edited on 2026-07-05 07:33 (UTC) by j1simon)

fabiscafe, I can take care of the package.
One thing, though—there's no point in continuing to compile czkawka-gui; this package is being discontinued in version 12: "Version 12.0 is the last released version - no new binaries will be provided. New users and existing users are encouraged to switch to Krokiet."
What I'm not sure about is the czkawka-cli package.

fabiscafe commented on 2026-02-18 21:24 (UTC)

@gbr good find, thanks!. It was added just recently, and I missed it completely: https://github.com/qarmin/czkawka/tree/8bd6fb84702b483a49f1dd36686cabd5fc1d6ef4/data

I'll work on it (hopefully) this weekend. (If someone wants to write a patch, I'd be happy :D it's essentially the same as for the other "flavors")

gbr commented on 2026-02-17 11:30 (UTC) (edited on 2026-02-17 11:30 (UTC) by gbr)

Why there's no desktop file for Krokiet?

fabiscafe commented on 2025-06-12 12:12 (UTC)

@Segel sounds like something was wrong on your end. Please try in a clean build environment. I sadly cant recreate it.

Segel commented on 2025-06-12 11:26 (UTC) (edited on 2025-06-12 11:26 (UTC) by Segel)

/usr/sbin/xvfb-run: line 185: kill: (179373) - No such process
A connection to the bus can't be made
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: czkawka-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
czkawka-gui - exit status 4

The error is non critical and can be ignored but check() is failing.

fabiscafe commented on 2024-03-04 15:59 (UTC)

Hi @dc46and2 I suggest you to use the czkawka-*-bin to avoid build times.

Of course you also have the options to:


My PKGBUILD here always follows the purpose of providing a release ready, close-to-upstream setup that works in an Arch build environment. That comes this time sadly with this bug of a much to long build time. :(

dc46and2 commented on 2024-03-03 17:52 (UTC)

Thanks for the very useful software. I just want to build/install czkawka-gui, but I'm waiting a long time for krokiet to build. Would it be better to have a separate PKGBUILD for krokiet? Or is there another way to avoid building the unwanted packages?

fabiscafe commented on 2024-03-01 08:58 (UTC)

schnedan You can remove the --release flag and build it as "development" snapshot. This should shrink down build time by up to 90%

See the pinned bugreport.

For the build problem I have no idea. It works for me in a clean build environment.