Package Details: aurutils 19.4-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: custom:ISC
Submitter: Alad
Maintainer: Alad (rafasc, cgirard, maximbaz, zoorat)
Last Packager: Alad
Votes: 265
Popularity: 1.87
First Submitted: 2016-03-26 19:17 (UTC)
Last Updated: 2024-05-07 14:05 (UTC)

Dependencies (14)

Sources (1)

Pinned Comments

Alad commented on 2023-05-21 12:54 (UTC) (edited on 2023-05-21 12:54 (UTC) by Alad)

After the git migration and introduction of pkgctl with devtools 1.0.0, it is recommended to recreate all aurutils chroots and update any pacman configuration in /etc/aurutils/pacman-x86_64.conf.

rm -rf /var/lib/aurbuild
cp /usr/share/devtools/pacman.conf.d/extra.conf /etc/aurutils/pacman-x86_64.conf
vim /etc/aurutils/pacman-x86_64.conf  # add local repository

https://archlinux.org/news/git-migration-completed/

Latest Comments

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

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.