Arch Linux User Repository

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 .

Packaging Bugtracker

https://gitlab.archlinux.org/fabiscafe/czkawka_aur

@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")

Why there's no desktop file for Krokiet?

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

/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.

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

Of course you also have the options to:

• Speedup the build process (up to -90% time) of krokiet, by removing the --release flag

• Remove Krokiet and -cli completely from the PKGBUILD (To long to explain it in here, so thats for users who can write PKGBUILDs themself

• Use the pre-build binary directly from upstream git -> https://github.com/qarmin/czkawka/releases/tag/7.0.0

• Use czkawka from flathub

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. :(

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?

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.

I can confirm the buildtime problem... 37min on a AMD Ryzen2 8Core / 16Thread 4Ghz machine...

Also Build stops after error:

test connect_things::connect_selection_of_directories::test_remove_ending_slashes ... ok
test help_functions::test::test_change_dimension_to_krotka ... ok
test help_functions::test::test_file_name_shortener ... ok
test help_functions::test::test_pixbuf_from_dynamic_image ... ok
ERROR: ICD associated with VkPhysicalDevice does not support GetPhysicalDeviceCalibrateableTimeDomainsKHR
error: test failed, to rerun pass -p czkawka_gui --bin czkawka_gui

Caused by:
process didn't exit successfully: /tmp/trizen-username/czkawka/src/czkawka/target/release/deps/czkawka_gui-5c6a72e4dfa901a4 (signal: 6, SIGABRT: process abort signal)