Package Details: collision 3.4.0-1

Git Clone URL: (read-only, click to copy)
Package Base: collision
Description: Check hashes for your files. A simple GUI tool to generate, compare and verify MD5, SHA1 & SHA256 hashes
Upstream URL:
Licenses: BSD
Conflicts: collision-hashes, hashbrown
Replaces: collision-hashes, hashbrown
Submitter: igor-dyatlov
Maintainer: igor-dyatlov (yochananmarqos)
Last Packager: igor-dyatlov
Votes: 7
Popularity: 0.171464
First Submitted: 2022-06-06 19:42 (UTC)
Last Updated: 2023-01-15 20:13 (UTC)

Latest Comments

1 2 Next › Last »

GregTheHun commented on 2023-03-17 21:37 (UTC) (edited on 2023-03-17 21:37 (UTC) by GregTheHun)

Also got a nice error:

warn - Gtk::BuildableParser padding field - Unknown conversion to crystal for fixed size array.
syntax error in './harf_buzz-0.0/': can't use variable name 'unicodes' inside assignment to variable 'unicodes'
fatal - Error formating generated files at '/home/greg/.cache/paru/clone/collision/src/Collision-3.4.0/lib/gi-crystal/src/auto'.
==> ERROR: A failure occurred in build().
error: failed to build 'collision-3.4.0-1':
error: packages failed to build: collision-3.4.0-1

Alex-Kim commented on 2023-03-06 08:05 (UTC)

Hey! There's a build error:

syntax error in './harf_buzz-0.0/': can't use variable name 'unicodes' inside assignment to variable 'unicodes'
fatal - Error formating generated files at '/home/alex/.cache/yay/collision/src/Collision-3.4.0/lib/gi-crystal/src/auto'.
==> ERROR: A failure occurred in build().
 -> error making: collision

igor-dyatlov commented on 2023-01-15 20:16 (UTC)

@yochananmarqos: Thank you, I've added you to the maintainer list.

yochananmarqos commented on 2023-01-06 00:47 (UTC) (edited on 2023-01-06 00:47 (UTC) by yochananmarqos)

@igor-dyatlov: The optional dependency is python-nautilus, not libnautilus-extension.

@saltedcoffii: Your paste expired, so no one knows what error you had and why only using one job will fix it. FYI, I use MAKEFLAGS="-j$(($(nproc)+1))"

For those who have trouble building due to failing to clone one of the shards randomly, for some reason running the Makefile commands manually works. See my PKGBUILD

kajlao commented on 2022-12-03 17:11 (UTC) (edited on 2022-12-04 19:28 (UTC) by kajlao)

New fix, fixed it.

DodoLeDev commented on 2022-12-03 14:33 (UTC) (edited on 2022-12-03 14:35 (UTC) by DodoLeDev)

Hi! While building the latest version of Collision, I get each time this compilation error:

==> Starting package_collision-nautilus-extension()...
install: unable to create the standard file '/home/dodoledev/.cache/yay/collision/pkg/collision-nautilus-extension/share/nautilus-python/extensions/': Not a folder
==> ERROR: A failure occurred in package_collision-nautilus-extension().

After some investigations, it seems that there is a problem with the PKGBUILD file:

package_collision-nautilus-extension() {
    pkgdesc="GNOME Files extension that adds a (Check Hashes) context menu item"

    cd "$_source-$pkgver"

    mkdir -p "$pkgdir/usr/share/nautilus-python/extensions/"
    install -Dm644 nautilus-extension/ "$pkgdir/share/nautilus-python/extensions/"

The mkdir line creates a folder not used in the install line!

Please update your PKGBUILD file with this instead:

    mkdir -p "$pkgdir/usr/share/nautilus-python/extensions/"
    install -Dm644 nautilus-extension/ "$pkgdir/usr/share/nautilus-python/extensions/"

Hope I helped you!

saltedcoffii commented on 2022-11-17 09:15 (UTC) (edited on 2022-11-17 09:40 (UTC) by saltedcoffii)

I'm getting a build failure:

This occurs even in a clean chroot.

setting MAKEFLAGS to -j1 in /etc/makepkg.conf seems to fix the error. Perhaps set it manually in the PKGBUILD for the time being and report an error upstream?

igor-dyatlov commented on 2022-10-19 15:13 (UTC)

@yochananmarqos: I don't even know how I can reproduce this problem. Try to build with a VPN and on a virtual machine. I tried, the build is successful

Video of the build on a virtual machine in chroot: Ready binary: sha1 54de97e378b5162ab64b3f7f73a7e5a6d95d6dfd

yochananmarqos commented on 2022-10-17 15:36 (UTC)

@kajlao: I still get the Failed to clone error like in @Tio's log below.