#614 closed defect (fixed)
Failed downloading of <reference>s
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | nALFS - Back End (XML Handlers) | Version: | 1.1.7 |
Severity: | normal | Keywords: | |
Cc: |
Description
When file that should be downloaded doesn't exist, it's created anyway (with zero-size) which latter causes problems.
Also, what should be done when transfer is not fully completed? We need to check that and continue the transfer, not try to unpack the broken archive.
Change History (10)
comment:1 by , 21 years ago
qa_contact: | alfs-discuss@linuxfromscratch.org → alfs-log@linuxfromscratch.org |
---|
comment:2 by , 21 years ago
Owner: | changed from | to
---|---|
Version: | CVS → 1.1.7 |
comment:3 by , 21 years ago
comment:4 by , 21 years ago
Owner: | changed from | to
---|
comment:5 by , 21 years ago
Priority: | lowest → low |
---|
comment:6 by , 21 years ago
Priority: | low → normal |
---|
comment:7 by , 21 years ago
dependson: | → 671 |
---|
comment:8 by , 21 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
patch committed to CVS; no attempt was made to handle "continuing" transfers, but I did add logic to try multiple <url>s in a <download> if the first (or more than the first) successfully download but fail the digest check (assuming a digest was supplied)
comment:9 by , 21 years ago
Keywords: | VERIFIED added |
---|
bug 695 now deals with resuming a failed download.
comment:10 by , 21 years ago
Keywords: | VERIFIED removed |
---|
Note:
See TracTickets
for help on using tickets.
I will fix the zero-size file problem this weekend, and will look into the "continuing transfer" issue. The latter should possible be moved into a separate bug, since it's more work and really an enhancement request. Please assign to me.