Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".
* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.
* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.
FS#67865 - Download progress not shown when using Cloudflare mirrors
Attached to Project:
Pacman
Opened by Yuval Adam (yuvadm) - Thursday, 10 September 2020, 10:53 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 10 September 2020, 11:10 GMT
Opened by Yuval Adam (yuvadm) - Thursday, 10 September 2020, 10:53 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 10 September 2020, 11:10 GMT
|
DetailsDescription:
Cloudflare have recently launched a new mirror service - https://cloudflaremirrors.com/ To the best of my understanding they simply mirror the existing mirrors and serve them from their CDN. When using their mirror service, pacman doesn't output any package download progress. This is most likely due to missing Content-Length headers in the response. At the very least, it would be better to gracefully degrade and at least show which packages are *currently* being downloaded, even if the specific package progress is missing. Additional info: * pacman 5.2.2 Steps to reproduce: 1. Add Server = https://cloudflaremirrors.com/archlinux/$repo/os/$arch to your mirrorlist 2. pacman -Syu |
This task depends upon
error: failed retrieving file '.......' from cloudflaremirrors.com : HTTP server doesn't seem to support byte ranges. Cannot resume.
pacman 5.2.2 *does* show download progress, but pacman from git doesn't. pacman from git also doesn't emit errors for the failing byte range.
pacman from git will still show this, though:
<foo>-x86_64.pkg.tar.zst downloading...
Then reports the average at the end.
pacman stable merely quietly shows nothing for them.
This is definitely broken somehow. Though, the worst breakage -- the completely silent failure to report anything -- is incidentally fixed due to the parallel download rewrite.