-
-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building in clean chroot fails using devtools 20221002-1 #859
Comments
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 |
After some bisecting, archlinux/devtools@1e23bbc seems to be the first bad commit. |
I don't see how that commit could break it :/ |
Actually I guess if it can only match one case at a time then -eA would cause only A to get detected... Whoops |
I see that paru execs makepkg like this: for me problematic option is -e with out -e in -feA all works fine. |
This reverts commit 8512f55 See Morganamilo/paru#859
Possible fix at devtools#117 |
@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 |
devtools#117 was merged and they've tagged a new release. |
archlinux/svntogit-packages@e34688a Closing, just wait for it to enter |
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 duringpkgver()
fori3status-rust-git
. It seems that the source dir doesn't exist. Downgradingdevtools
to20220621-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
The text was updated successfully, but these errors were encountered: