Bug #4334
closed
Technique "Download From A Shared Folder": copy files to directory destination doesn't work
Added by Nicolas PERRON almost 11 years ago.
Updated over 7 years ago.
Description
With Download From A Shared Folder, #3646 lead to have a file with name of a directory instead of placing the file in the destination directory.
What is more unfortunate here is that if we copy a file in a path requiring a directory with the same name than a file it will not work.
Example 1:
- /tmp/foo is a directory
- we want to copy file1 in /tmp/foo with "/tmp/foo/" in destination in the Directive
- result: /tmp/foo will be replaced by the content of file1 (cf #3646)
Example 2:
- /tmp/foo is a file
- file2 is another file
- we want to copy file2 in /tmp/foo/bar/baz
- result: the folder /tmp/foo will not be able to be created since a file with the same name already exist
Now, imagine that you made the first mistake, you will have to delete the wrong file (/tmp/foo) before to apply the second example without error.
I suppose we should propose to enforce or not a file/directory during the copy ?
- Description updated (diff)
- Target version changed from 2.4.13 to 2.6.11
Since version 2.4 is not maintained anymore, retargeting to branch 2.6
- Target version changed from 2.6.11 to 2.6.12
- Target version changed from 2.6.12 to 2.6.13
- Target version changed from 2.6.13 to 2.6.14
- Target version changed from 2.6.14 to 2.6.16
- Target version changed from 2.6.16 to 2.6.17
- Target version changed from 2.6.17 to 2.6.18
- Target version changed from 2.6.18 to 2.6.19
- Target version changed from 2.6.19 to 2.6.20
- Target version changed from 2.6.20 to 2.10.10
- Target version changed from 2.10.10 to 2.10.11
- Target version changed from 2.10.11 to 2.10.12
- Project changed from 24 to Rudder
- Category set to Techniques
- Target version changed from 2.10.12 to 2.10.13
- Target version changed from 2.10.13 to 2.10.14
- Target version changed from 2.10.14 to 2.10.15
- Target version changed from 2.10.15 to 2.10.16
- Target version changed from 2.10.16 to 2.10.17
- Target version changed from 2.10.17 to 2.10.18
- Target version changed from 2.10.18 to 2.10.19
- Target version changed from 2.10.19 to 2.10.20
- Target version changed from 2.10.20 to 2.11.18
- Target version changed from 2.11.18 to 2.11.19
- Target version changed from 2.11.19 to 2.11.20
- Target version changed from 2.11.20 to 2.11.21
- Target version changed from 2.11.21 to 2.11.22
- Target version changed from 2.11.22 to 2.11.23
- Target version changed from 2.11.23 to 2.11.24
- Target version changed from 2.11.24 to 308
- Target version changed from 308 to 3.1.14
- Target version changed from 3.1.14 to 3.1.15
- Target version changed from 3.1.15 to 3.1.16
- Target version changed from 3.1.16 to 3.1.17
- Target version changed from 3.1.17 to 3.1.18
- Target version changed from 3.1.18 to 3.1.19
- Subject changed from Technique "Download From A Shared Folder": Copy a file with same name than a directory will replace it by the file but copying a file with a path requiring a directory with the same name than a file will not work to Technique "Download From A Shared Folder": copy files to directory destination doesn't work
- Status changed from New to Rejected
- Priority set to 0
It is a duplicate of #10312, so I'm closing it.
- Is duplicate of Bug #10312: "Download files from the shared folder" behaving badly? added
Also available in: Atom
PDF