Package Details: aurutils 1.3.3-1

Git Clone URL: https://aur.archlinux.org/aurutils.git (read-only)
Package Base: aurutils
Description: helper tools for the arch user repository
Upstream URL: https://github.com/AladW/aurutils
Licenses: ISC
Submitter: Alad
Maintainer: Alad (runical)
Last Packager: Alad
Votes: 20
Popularity: 5.155882
First Submitted: 2016-03-26 19:17
Last Updated: 2016-09-11 13:06

Dependencies (12)

Required by (0)

Sources (1)

Latest Comments

Alad commented on 2016-05-16 00:03

0.9.1 was released. There are some significant changes from 0.8.5, so please read the release notes and the new man page, aurutils(7).

https://github.com/AladW/aurutils/releases/tag/0.9.0
https://github.com/AladW/aurutils/releases/tag/0.9.1

Alad commented on 2016-04-25 10:18

Done, thanks for the report

runical commented on 2016-04-25 10:12

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

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

No problem. Thanks for the update!

Alad commented on 2016-03-28 14:50

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

runical commented on 2016-03-28 14:30

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

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

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

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.