Local symlinks not resolved when copying to remote location
Bug #1590594 reported by
Robert Tari
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| caja (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I am not sure whether to classify this as a bug or a feature request:
When transferring files to a remote location, e.g. an FTP host, symlinks are copied as symlinks - instead of the local file they are pointing to. I cannot think of a scenario where this should be the desired behaviour, but in case Caja would prefer to do it this way - I would suggest a setting that should determine whether copying/moving over the network should resolve symlinks or not.
The reverse case works as expected: copying a symlinked remote file pulls the remote target.
Revision history for this message
| Norbert (nrbrtx) wrote | #1 |
| Changed in caja (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Robert Tari (robert-tari) wrote | #2 |
| Changed in caja (Ubuntu): | |
| status: | Incomplete → Confirmed |
| tags: | added: bionic focal groovy xenial |
| tags: |
added: hirsute impish removed: groovy |
To post a comment you must log in.
Can you reproduce this bug with newer version of Ubuntu MATE?