Currently, an empty progress bar may get printed even when download is not actually performed. This happens because the callback responsible for download progress assumes the transferred data will eventually increase. However this is not certain, for example odd servers may cause the curl library to activate the download callback without any byte transfer ever taking place. Also, because the callback may be called multiple times while there is still no transferred data, --noprogressbar may print repeated status messages.

The emty progress bar can be reproduced for example by refreshing pacman repositories from Bintray, which seems to confuse the curl library by returning unexpected HTTP status codes. The repeated status messages can be reproduced by refreshing databases with --noprogressbar. Attached is a patch addressing both issues, along with sample outputs.