Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#39122 - Restart download (instead of file resume) when resume is not supported

Attached to Project: Pacman
Opened by Florian Breitwieser (florianbw) - Monday, 03 March 2014, 18:09 GMT
Last edited by Allan McRae (Allan) - Sunday, 29 June 2014, 10:01 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

I'm on a public wireless network, which manages to disable the file resume. Currently, when the download fails, you are stuck with the error

HTTP server doesn't seem to support byte ranges. Cannot resume.

and nothing can be done about it, unless you know you have to delete the .part file in the cache. Even when you restart the command, or try to force it, it fails. There should be either a message notifying the user that the cache has to be cleaned, or rather the part file is automatically ignored when this occurs. [And it is really just the provider you are connecting with: When I tether from my phone, resume works again.]

I've seen the closed issue #34973, which reports the same issue (but proposes a different solution).

Steps to Reproduce:
pacman -S mypackage
## timeout
pacman -S mypackage
## does not work
pacman --force -S mypackage
## also does not work
pacman -S mypackage
## still does not work
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 29 June 2014, 10:01 GMT
Reason for closing:  No response
Comment by Allan McRae (Allan) - Tuesday, 04 March 2014, 00:10 GMT
Can you post a --debug log with this happening?
Comment by Florian Breitwieser (florianbw) - Tuesday, 04 March 2014, 02:42 GMT
Sorry, I can't now. The Access Point is not so near, but I should pass by there in two weeks again. Then I'll provide logs.

Loading...