Open BennyAJ opened 7 years ago
Thanks for the feedback.
Indeed. Updating a package doesn't cause this problem. If there is nothing to add to the gist, the diff
returns true
and doesn't go to the following wrong expression that causes "Failed to update" if the command passes. You come across this case by adding or removing a non-AUR package.
I fixed it. I'll update the package.
The script runs for 15-20 seconds before outputting that it failed, so maybe it's getting stuck somewhere?
Nevertheless, I don't know why it's so slow.
Every time I install or remove a package, the script says "Failed to update" and pacman outputs "error: command failed to execute correctly." The gist is still updating correctly, so this is mostly a minor annoyance. The script runs for 15-20 seconds before outputting that it failed, so maybe it's getting stuck somewhere? Updating a package doesn't cause this problem. AUR packages also don't cause it.