I've identified an issue when using aurutils.rebase
(git-config
option) with any aurutils version >=3.0.0. If this option is set for any package, then aur-fetch
will use the same sync mode for all packages following it. This issue was introduced with https://github.com/AladW/aurutils/commit/f60bfb1c5154e36ccf391a28ae7a9ea516e920da
For example, if aurutils.rebase
is set for foo
, where ~/.cache/aurutils/sync/foo
has a local commit applied on top of HEAD@{upstream}
, then the sync mode will be "none" (i.e. no changes pulled in) and applied to any bar
, baz
... packages following foo
.
tl;dr avoid aurutils.rebase
with aurutils <=9.6, >=3.0. The issue is fixed in aurutils 10.
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
withdevtools
1.0.0, it is recommended to recreate all aurutils chroots and update any pacman configuration in/etc/aurutils/pacman-x86_64.conf
.https://archlinux.org/news/git-migration-completed/