Building in clean chroot fails using devtools 20221002-1

[YHNdnzj]

Affected Version

paru v1.11.1 +git - libalpm v13.0.1

Description

After updating to the latest devtools (20221002-1, currently in testing), building in chroot fails during pkgver() for i3status-rust-git. It seems that the source dir doesn't exist. Downgrading devtools to 20220621-1 fixes the issue for me. I'm not sure if paru is to blame, though.

Output

paru.conf

# i3status-rust-git-0.30.0.r2917.g51fd9e5d-1-x86_64-pkgver.log
/startdir/PKGBUILD: line 28: cd: i3status-rust: No such file or directory

[hexchain]

The issue can be reproduced with a simple stub PKGBUILD:

pkgname=testpkg
pkgver=1.0
pkgrel=1
pkgdesc="Test package"

prepare() {
    cd "$srcdir"
    touch a
    ls -lR
}

build() {
    cd "$srcdir"
    ls -l a
}

package() {
    cd "$srcdir"
    ls -l a
}

Running paru -U on the PKGBUILD will fail at build step due to the missing file a.

[YHNdnzj]

After some bisecting, archlinux/devtools@1e23bbc seems to be the first bad commit.

[Morganamilo]

I don't see how that commit could break it :/

[Morganamilo]

Actually I guess if it can only match one case at a time then -eA would cause only A to get detected... Whoops

[alex19EP]

I see that paru execs makepkg like this:
makechrootpkg -r /var/lib/aurbuild/x86_64 -D /var/lib/aur -d /var/cache/pacman/pkg/ -d /var/lib/aur/ -- -feA --noconfirm --holdver

for me problematic option is -e with out -e in -feA all works fine.

[YHNdnzj]

Possible fix at devtools#117

[justinkb]

@Morganamilo want me to submit some simple workaround PRs for this (for master and backported for 1.11.1?) unsure whether devtools maintainer wants to roll a new release for this on short notice

[SamLukeYes]

devtools#117 was merged and they've tagged a new release.

[YHNdnzj]

archlinux/svntogit-packages@e34688a

Closing, just wait for it to enter [extra] :)