Package Details: aurutils 20.5.8-1

Git Clone URL: https://aur.archlinux.org/aurutils.git (read-only, click to copy)
Package Base: aurutils
Description: helper tools for the arch user repository
Upstream URL: https://github.com/AladW/aurutils
Keywords: aur aur-helper helper
Licenses: ISC
Submitter: Alad
Maintainer: Alad (zoorat, Pulec)
Last Packager: Pulec
Votes: 301
Popularity: 2.28
First Submitted: 2016-03-26 19:17 (UTC)
Last Updated: 2026-02-24 15:21 (UTC)

Dependencies (15)

Sources (1)

Pinned Comments

Alad commented on 2026-02-24 22:13 (UTC)

If you updated to gawk 5.4.0 before aurutils 20.5.8, you'll need to build the package manually (aur-build/makepkg) or append --no-graph to your aur-sync command.

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15

runical commented on 2016-04-25 10:12 (UTC)

Seems like the checksum update went wrong. Only the .SRCINFO was updated according to the log. Could you update the checksum once more as it is still incorrect?

Alad commented on 2016-04-04 22:14 (UTC) (edited on 2016-04-04 22:15 (UTC) by Alad)

Please note that with 0.4.0., aurchain and aursift now print and check pkgname respectively, instead of pkgbase. https://github.com/AladW/aurutils/issues/84 There are also two new command-line switches: "aursync -u" to find outdated packages in a given repository and build them, and "aursearch -b" to search the AUR pkgbase list.

runical commented on 2016-03-28 15:00 (UTC)

No problem. Thanks for the update!

Alad commented on 2016-03-28 14:50 (UTC)

Sorry guys, I still had an old source directory around. Updated the checksums.

runical commented on 2016-03-28 14:30 (UTC) (edited on 2016-03-28 14:34 (UTC) by runical)

The new package builds, but only after updating the md5 to 'e7530dcf300b13a2a34754e43ce0395d'. I did get a cd error before this update.

prettyvanilla commented on 2016-03-28 13:58 (UTC)

I've got the same problem, downloading the 0.2.1 release tarball I consistently get 'e7530dcf300b13a2a34754e43ce0395d' for the md5sum, not 'fa27a[...]'.

Alad commented on 2016-03-28 13:42 (UTC)

Hm, the checksums were correct for me, but the cd was wrong. Could you try again with a new snapshot?

runical commented on 2016-03-28 10:25 (UTC)

I think you forgot to update the checksum for 2.1. Builds fail because 0.2.1.tar.gz does not pass the validity check.