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.91
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 .. 7 8 9 10 11 12 13 14 Next › Last »

Alad commented on 2018-03-25 20:17 (UTC)

https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

qdii commented on 2018-03-25 19:43 (UTC)

There is a first stage where makepkg tells me I'm missing dependencies. Then I install them, then running makepkg fails because it cannot find "patch", and then once more with "fakeroot".

Maybe add those to the dependency check at first?

Alad commented on 2018-01-27 13:04 (UTC)

Fixed.

Mel commented on 2018-01-27 12:56 (UTC) (edited on 2018-01-27 12:58 (UTC) by Mel)

1.5.3-7 errors out in prepare():

==> Starting prepare()...

patching file bin/aurbuild

patching file bin/aurbuild

patching file bin/aurbuild

Hunk #1 FAILED at 5.

1 out of 1 hunk FAILED -- saving rejects to file bin/aurbuild.rej

patching file bin/aursync

patching file man1/aursync.1

==> ERROR: A failure occurred in prepare().

    Aborting...

cat aurbuild.rej

--- bin/aurbuild
+++ bin/aurbuild
@@ -5,7 +5,7 @@ readonly PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'
 set -e

 declare -a gpg_args=(--detach-sign --no-armor --verbose --batch)
-declare -a makechrootpkg_args=(-cnu) makepkg_args=(-Lcrs)
+declare -a makechrootpkg_args=(-cnu) makepkg_args=(-crs)
 declare -i chroot=0 sign_pkg=0

 conf_chroot() {

Alad commented on 2018-01-27 02:30 (UTC)

With -6, makepkg -L is now optional.

Alad commented on 2018-01-17 18:41 (UTC) (edited on 2018-01-17 18:42 (UTC) by Alad)

There's a known issue with aurchain and dependency order of some split packages such as gdm-plymouth. Either specify the order manually, or update to the git version until 1.6.0 is released.

air-g4p commented on 2017-12-18 15:49 (UTC)

Alad - very sorry for my latest 'comment' - obviously, wrong URL - but I got hundreds open atm - but still my fault.

Feel free to delete it.

BTW - I'm an avid aurutils user!

Best regards,

air|g4p

air-g4p commented on 2017-12-18 15:45 (UTC)

Hi grayslake,

I am sorry to have to inform you that using: extra-x86_64-build

fails with either linux-ck 4.14.6-3 or with linux-ck 4.14.7-1.

I have pasted the complete failed build runs at:

linux-ck 4.14.6-3 (per your suggestion) lives here: https://bpaste.net/show/cad411ec029a

and also with: linux-ck 4.14.7-1, here:

Despite the 'advice' generated just prior to build failure:

Console input/output is redirected. Run 'make oldconfig' to update configuration.

$ make oldconfig make: *** No rule to make target 'oldconfig'. Stop.

and ofc, this also:

$ sudo make oldconfig [sudo] password for user: make: *** No rule to make target 'oldconfig'. Stop.

Those 'make oldconfig' failures occur irrespective of whether a user is in their correct build directory, or in their chroot directory = /var/lib/archbuild/extra-x86_64/<userid>/build</userid>

Also, carefully note, the build process never stopped, prior to failure, to ask me, which CPU I wanted to build support for. The current linux-ck AURs I have tested above both only auto-select '> 23. Generic-x86-64 (GENERIC_CPU)', then immediately fail.

grayslake - I do appreciate your ongoing support, but I would like to get to the bottom of this issue, sometime 'soon'. If you have specific commands you want me to test, let me know.

All the best,

air|g4p