Bug 156412

Summary: on downloading a file again, kget tells me to rename the file even though I deleted it before?
Product: [Applications] kget Reporter: Marcel Partap <mpartap>
Component: generalAssignee: KGet authors <kget>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Marcel Partap 2008-01-22 22:04:27 UTC
Version:           2.0 (using 4.00.80 (KDE 4.0.80 >= 20080104), Gentoo)
Compiler:          x86_64-pc-linux-gnu-gcc
OS:                Linux (x86_64) release 2.6.24-rc8-git3

well I downloaded drupal-6.x-dev two days ago. Now I wanted to redownload it, deleted the old file before (which is still in the kget list as complished).. but now kget tells me to rename the download - ? Also there's no overwrite option in that dialog?
And btw.. a redownload feature would be nice for this ;)
Comment 1 Lukas Appelhans 2008-01-22 22:51:42 UTC
Hi!
You have to rename the Transfer, cause there can't be 2 transfers with the same name in the transferlist.
Anyway, the next days I will look for the Redownload-feature...

Lukas
Comment 2 Marcel Partap 2008-01-22 23:07:35 UTC
oic it's not the filename but the transfer name...
well I think downloads should be identified by full source URL.. if then a clash occurs it should ask if redownload-> overwrite or rename.. cheers marcel
Comment 3 Lukas Appelhans 2008-05-31 16:37:11 UTC
Well we now have a redownload-feature, but I don't think that identifying the Transfer by the sourceUrl will go into KGet2. Downloading the same file twice also makes no sense ;) I will close this bug instead...

Lukas
Comment 4 Saurabh Asthana 2008-06-20 21:27:51 UTC
I just had this problem. It is not at all intuitive, I think the bug should be reopened. I don't give a crap that there is already something in the "transfer list", all I care about is downloading the file to my drive. If there is no file on the drive, kget should start a new transfer or replace the existing one. Also, it is EXTREMELY confusing that the name of the transfer is the same as the path of the file (if that is indeed the issue).