New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Linux to Windows file copy same name #1976

Closed
Jeeppler opened this Issue May 10, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@Jeeppler

Jeeppler commented May 10, 2016

Qubes OS version (e.g., R3.1): 3.1

Affected TemplateVMs (e.g., fedora-23, if applicable):

  • *inux VM's
  • Windows VM's

Expected behavior:

Renaming of the second file to filename-copy.extension

Actual behavior:

File exists error -> copy process aborts

Steps to reproduce the behavior:

Copy first Document.pdf to Windows VM and then copy document.pdf or the other way around.

General notes:

Windows does not make a difference between lower case and upper case file names. For example document.pdf and Document.pdf is the same file under Windows.
In Linux on the other hand document.pdf and Document.pdf are two different files.

It would be nice if the qubes-copy-to-vm tools could handle this transparently and rename the second file if the copy target VM is a Windows VM to filename-copy.extension. For example rename document.pdf to document-copy.pdf, if Document.pdf is already in the folder.


Relevant labels: Windows, Linux, Copy, Paradigm Problem

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 10, 2016

Member

Duplicate of #1772.

Member

andrewdavidwong commented May 10, 2016

Duplicate of #1772.

@Jeeppler

This comment has been minimized.

Show comment
Hide comment
@Jeeppler

Jeeppler May 10, 2016

@andrewdavidwong: this is not the same as #1772 this is a Linux -> Windows issues. Windows does not differentiate between upper and lower case letters in file names and Linux does. This means even if document.pdf and Document.pdf are two different files on a Linux VM. Windows will complain.

#1772 handles another more general use case if files already exist, but both are not a duplicate.

Jeeppler commented May 10, 2016

@andrewdavidwong: this is not the same as #1772 this is a Linux -> Windows issues. Windows does not differentiate between upper and lower case letters in file names and Linux does. This means even if document.pdf and Document.pdf are two different files on a Linux VM. Windows will complain.

#1772 handles another more general use case if files already exist, but both are not a duplicate.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 10, 2016

Member

From Windows point of view, the issue is the same.

Member

marmarek commented May 10, 2016

From Windows point of view, the issue is the same.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong May 10, 2016

Member

@Jeeppler: It's not a duplicate in the sense that they describe precisely the same issue, but it's a duplicate in the sense that any good solution to #1772 should also solve this issue. There's no reason to implement a Windows-specific solution to this problem when a more general solution for all VM types will work just as well (or better).

Member

andrewdavidwong commented May 10, 2016

@Jeeppler: It's not a duplicate in the sense that they describe precisely the same issue, but it's a duplicate in the sense that any good solution to #1772 should also solve this issue. There's no reason to implement a Windows-specific solution to this problem when a more general solution for all VM types will work just as well (or better).

@Jeeppler

This comment has been minimized.

Show comment
Hide comment

@andrewdavidwong that is true

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment