Skip to content
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

aur sync -c does not work #1151

Closed
nl6720 opened this issue Mar 29, 2024 · 5 comments
Closed

aur sync -c does not work #1151

nl6720 opened this issue Mar 29, 2024 · 5 comments

Comments

@nl6720
Copy link
Contributor

nl6720 commented Mar 29, 2024

After upgrading from aurutils 19-1 to aurutils 19.2-1, aur sync -c doesn't work anymore. No output is produced at all.

See attached logs of:

$ AUR_DEBUG=1 aur sync -c aurutils

aurutils-19.2-1-bad.log
aurutils-19-1-good.log

@ardhinata
Copy link

I'm also can reproduce this issue with aur sync -cu. My mitigation right now is downgrading aurutils version 19.2 to 19.1 and add IgnorePkg=aurutils to /etc/pacman.conf to pin aurutils version.

I'm also attaching debug logs for comparison:
aurutils-19.1.log
aurutils-19.2-fail.log

@AladW
Copy link
Member

AladW commented Mar 30, 2024

It makes no sense to me that it would work in 19.1, but not 19.2. The only thing that changed is 6f91817

Does reverting that commit fix the issue?

@nl6720
Copy link
Contributor Author

nl6720 commented Mar 30, 2024

6f91817 is bork while eb664e7 works fine.

@AladW
Copy link
Member

AladW commented Mar 30, 2024

Fixed in 19.3

@AladW
Copy link
Member

AladW commented Mar 30, 2024

Cleared the mystery: type -P prints the command name to standard output, and this resulted in aur chroot --status printing six lines instead of the (expected) three. This in turn leads to a SIGPIPE in wait $!: https://github.com/aurutils/aurutils/blob/master/lib/aur-build#L226

Using hash or command -p as suggested on IRC would help, or just redirect standard output to /dev/null. That said, I think adding these diagnostics - when the required commands can easily be retrieved from say, pacman -F - was premature anyway.

I've added an additional error message to avoid future confusion: db906f3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants