Opened 13 years ago

Closed 12 years ago

Last modified 12 years ago

#7410 closed Bug report (fixed)

Renaming local file overrides existing

Reported by: Peter Slivka Owned by: Atul Jha
Priority: normal Component: FileZilla Client
Keywords: rename local file Cc:
Component version: Operating system type: Linux
Operating system version: Ubuntu 12.04

Description

When I try to rename local file to name that already exists, it overrides that file.

Example:
I have 2 files
test
test1
renaming test1 to test replace test file without warning.

Trying the same on remote server throws alert saying filename already exists, what is good.

Attachments (1)

bug_7410.patch (522 bytes ) - added by Atul Jha 12 years ago.
Patch for Bug Number 7410

Download all attachments as: .zip

Change History (7)

comment:2 by Sworddragon, 13 years ago

Component: FileZilla ServerFileZilla Client
Keywords: rename local file added; POOPOPOPOPOPOPOPOPOPO LOL POOP SMELLS LIKE FILEZILLA removed
Operating system type: BSDLinux
Operating system version: POOPOPOPOPOPOPOPOPOPO LOL POOP SMELLS LIKE FILEZILLAUbuntu 10.04
Priority: lowhigh
Resolution: wontfix
Status: closedreopened
Summary: POOPOPOPOPOPOPOPOPOPO LOL POOP SMELLS LIKE FILEZILLARenaming local file overrides existing
Type: Feature requestBug report

comment:3 by Atul Jha, 12 years ago

Owner: set to Atul Jha
Status: newassigned

comment:4 by Atul Jha, 12 years ago

hi,

I am trying to solve this bug. I wanted to know if any other person is working on the same bug.

comment:5 by Atul Jha, 12 years ago

Operating system version: Ubuntu 10.04Ubuntu 12.04
Priority: highnormal

by Atul Jha, 12 years ago

Attachment: bug_7410.patch added

Patch for Bug Number 7410

comment:6 by Atul Jha, 12 years ago

Resolution: Nonefixed
Status: assignedclosed

comment:7 by Alexander Schuch, 12 years ago

@atjha

I do not know the communication you did, so sorry if you all did that already.

The patch itself does not contain a filename so at least I do not know where to apply it. Usually, patches are created using "diff -u" (unified diff format).

This bug report is marked as "fixed" and closed. This means that you submitted the patch and it was accepted and now is part of the FileZilla source code. Is this the case?

Maybe it is a good idea to submit the patch to the patch tracker and create a link to this bug report and from this bug report to the patch tracker item.

As long as the patch is not accepted and part of the official FileZilla repository, I wouldn't mark this bug as fixed and closed.

Note: See TracTickets for help on using tickets.