summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorEli Schwartz <eschwartz@archlinux.org>2020-06-03 00:16:48 +0200
committerAllan McRae <allan@archlinux.org>2020-06-11 02:53:24 +0200
commit381e11375569fa7588b1297e0e744749bdafe8f5 (patch)
tree5eae898573fb311df2e109580c78b0597d4de536 /doc
parent817f9fb715b4e90d28bc141dfccfc530b9e951dc (diff)
downloadpacman-381e11375569fa7588b1297e0e744749bdafe8f5.tar.gz
pacman-381e11375569fa7588b1297e0e744749bdafe8f5.tar.xz
makepkg: correctly handle missing download clients
This was broken in commit 882e707e40bbade0111cf3bdedbdac4d4b70453b, which changed 'plain()' messages to go to stdout, which was then captured as the download client in question: cmdline=("Aborting..."). The result was a very confusing error message e.g. /usr/share/makepkg/source/file.sh: line 72: $'\E[1m': command not found or with makepkg --nocolor: /usr/share/makepkg/source/file.sh: line 72: Aborting...: command not found The problem here is that we checked to see if an asynchronous subshell, in our case <(...), failed, by checking if its captured stdout is non-empty. Which is terrible, and also a limitation of old bash. But bash 4.4 can use wait $! to retrieve the return value of an asynchronous subshell. Now we target that as our minimum, we can sanely handle errors in such functions. Losing error messages on stdout by capturing them in a variable instead of printing them, continues to be a problem, but this will be fixed systematically in a later commit. Signed-off-by: Eli Schwartz <eschwartz@archlinux.org> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions