• Sequoia and duplicate files

    From TimS@21:1/5 to All on Mon May 5 08:14:48 2025
    A user of some of my software, trying to copy a big folder with lots of files in it, thinks that Sequoia is behaving perhaps differently to Sonoma or indeed all other versions of the Finder:

    "Then, while experimenting, I think I’ve run into an Apple OS problem (which I
    think is Sequoia). When I try to copy the folder to anywhere it aborts partway through complaining that a file of name (invoice.pdf) already exists and then refuses to process further."

    Does this sound familiar in any way? IME with Sonoma and all previous, if the Finder copying a file would create a duplicate (same name), it asks you what you want to do.

    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan B@21:1/5 to TimS on Mon May 5 08:36:09 2025
    On 2025-05-05, TimS <tim@streater.me.uk> wrote:
    A user of some of my software, trying to copy a big folder with lots of files in it, thinks that Sequoia is behaving perhaps differently to Sonoma or indeed
    all other versions of the Finder:

    "Then, while experimenting, I think I’ve run into an Apple OS problem (which I
    think is Sequoia). When I try to copy the folder to anywhere it aborts partway
    through complaining that a file of name (invoice.pdf) already exists and then refuses to process further."

    Does this sound familiar in any way? IME with Sonoma and all previous, if the Finder copying a file would create a duplicate (same name), it asks you what you want to do.

    I've not seen this problem on Sequoia or other versions. Are you copying the folder
    to somewhere in the same volume or to another? How are you actually performing the
    copying? I usually right click (2 finder press on the keypad) and select copy then
    use right click & paste where I want the folder to be copied. I do the same for files.
    If the folder (or file) exists at the destination then I get asked what I want to do.

    --
    Cheers, Alan

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Tobin@21:1/5 to tim@streater.me.uk on Mon May 5 09:58:19 2025
    In article <m7raboFqf79U1@mid.individual.net>,
    TimS <tim@streater.me.uk> wrote:

    Does this sound familiar in any way? IME with Sonoma and all previous, if the >Finder copying a file would create a duplicate (same name), it asks you what >you want to do.

    This should not normally arise when copying a folder - how could there
    be a duplicate in the new copy when there wasn't in the original?

    It can happen however if copying from a case-sensitive filesystem
    to a case-insensitive one - for example if the original contained
    both invoice.pdf and Invoice.pdf.

    -- Richard

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From TimS@21:1/5 to All on Mon May 5 11:34:06 2025
    On 5 May 2025 at 09:36:09 BST, "Alan B" <alanrichardbarker@gmail.com.invalid> wrote:

    On 2025-05-05, TimS <tim@streater.me.uk> wrote:
    A user of some of my software, trying to copy a big folder with lots of files
    in it, thinks that Sequoia is behaving perhaps differently to Sonoma or indeed
    all other versions of the Finder:

    "Then, while experimenting, I think I’ve run into an Apple OS problem (which I
    think is Sequoia). When I try to copy the folder to anywhere it aborts partway
    through complaining that a file of name (invoice.pdf) already exists and then
    refuses to process further."

    Does this sound familiar in any way? IME with Sonoma and all previous, if the
    Finder copying a file would create a duplicate (same name), it asks you what >> you want to do.

    I've not seen this problem on Sequoia or other versions. Are you copying the folder
    to somewhere in the same volume or to another? How are you actually performing
    the
    copying? I usually right click (2 finder press on the keypad) and select copy then
    use right click & paste where I want the folder to be copied. I do the same for files.
    If the folder (or file) exists at the destination then I get asked what I want
    to do.

    Well I'm not doing the copying, the user is. So it's a little hard to tell. I have asked him whether the usual Cancel/Skip/Keep Both kind of panel is displayed. I think he's copying from an internal disk to an external SSD.

    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan B@21:1/5 to TimS on Mon May 5 12:17:40 2025
    TimS <tim@streater.me.uk> wrote:
    On 5 May 2025 at 09:36:09 BST, "Alan B" <alanrichardbarker@gmail.com.invalid> wrote:

    On 2025-05-05, TimS <tim@streater.me.uk> wrote:
    A user of some of my software, trying to copy a big folder with lots of files
    in it, thinks that Sequoia is behaving perhaps differently to Sonoma or indeed
    all other versions of the Finder:

    "Then, while experimenting, I think I’ve run into an Apple OS problem (which I
    think is Sequoia). When I try to copy the folder to anywhere it aborts partway
    through complaining that a file of name (invoice.pdf) already exists and then
    refuses to process further."

    Does this sound familiar in any way? IME with Sonoma and all previous, if the
    Finder copying a file would create a duplicate (same name), it asks you what
    you want to do.

    I've not seen this problem on Sequoia or other versions. Are you copying the >> folder
    to somewhere in the same volume or to another? How are you actually performing
    the
    copying? I usually right click (2 finder press on the keypad) and select copy
    then
    use right click & paste where I want the folder to be copied. I do the same >> for files.
    If the folder (or file) exists at the destination then I get asked what I want
    to do.

    Well I'm not doing the copying, the user is. So it's a little hard to tell.

    Sorry my mistake!

    I have asked him whether the usual Cancel/Skip/Keep Both kind of panel is displayed. I think he's copying from an internal disk to an external SSD.

    Drag and drop should be OK from one volume to another and get the usual question if there’s a duplicate, unless it’s read only or ownership issue on the destination volume.

    --
    Cheers, Alan

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Ridd@21:1/5 to Alan B on Mon May 5 17:10:30 2025
    On 05/05/2025 13:17, Alan B wrote:
    Drag and drop should be OK from one volume to another and get the usual question if there’s a duplicate, unless it’s read only or ownership issue on the destination volume.

    The filesystem on the destination volume would be useful to know.

    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From TimS@21:1/5 to Chris Ridd on Mon May 5 16:19:10 2025
    On 5 May 2025 at 17:10:30 BST, "Chris Ridd" <chrisridd@mac.com> wrote:

    On 05/05/2025 13:17, Alan B wrote:
    Drag and drop should be OK from one volume to another and get the usual
    question if there’s a duplicate, unless it’s read only or ownership issue
    on the destination volume.

    The filesystem on the destination volume would be useful to know.

    I shall enquire. It could be that the user did not format the SSD before starting to use it, so it could be FAT or whatever these things come with by default.

    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From TimS@21:1/5 to Chris Ridd on Mon May 5 19:33:58 2025
    On 5 May 2025 at 17:10:30 BST, "Chris Ridd" <chrisridd@mac.com> wrote:

    On 05/05/2025 13:17, Alan B wrote:
    Drag and drop should be OK from one volume to another and get the usual
    question if there’s a duplicate, unless it’s read only or ownership issue
    on the destination volume.

    The filesystem on the destination volume would be useful to know.

    Another report from the user:

    "To answer your earlier question: No, it basically says it can't write another file with that name and when I click the OK buttion the entire process stops
    at that point (partially copied too)."

    I've asked for a screenshot. If he can get me one, I can't post it here but will put it somewhere and post a link.

    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From TimS@21:1/5 to Chris Ridd on Mon May 5 19:29:54 2025
    On 5 May 2025 at 17:10:30 BST, "Chris Ridd" <chrisridd@mac.com> wrote:

    On 05/05/2025 13:17, Alan B wrote:
    Drag and drop should be OK from one volume to another and get the usual
    question if there’s a duplicate, unless it’s read only or ownership issue
    on the destination volume.

    The filesystem on the destination volume would be useful to know.

    APFS, it would seem.


    --
    Tim

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Chris Ridd@21:1/5 to TimS on Mon May 5 21:16:31 2025
    On 05/05/2025 20:29, TimS wrote:
    On 5 May 2025 at 17:10:30 BST, "Chris Ridd" <chrisridd@mac.com> wrote:

    On 05/05/2025 13:17, Alan B wrote:
    Drag and drop should be OK from one volume to another and get the usual
    question if there’s a duplicate, unless it’s read only or ownership issue
    on the destination volume.

    The filesystem on the destination volume would be useful to know.

    APFS, it would seem.

    APFS (case sensitive) or just APFS? Apple will let you choose which one
    when you format the disk.

    --
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Tobin@21:1/5 to tim@streater.me.uk on Mon May 5 21:33:35 2025
    In article <m7shtiF239aU1@mid.individual.net>,
    TimS <tim@streater.me.uk> wrote:

    The filesystem on the destination volume would be useful to know.

    APFS, it would seem.

    The interesting case would be if the *source* volume was
    case-sensitive, and contained two files with names differing only in
    case.

    -- Richard

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bruce@21:1/5 to Richard Tobin on Tue May 6 23:35:40 2025
    On 05/05/2025 10:58, Richard Tobin wrote:
    In article <m7raboFqf79U1@mid.individual.net>,
    TimS <tim@streater.me.uk> wrote:

    Does this sound familiar in any way? IME with Sonoma and all previous, if the
    Finder copying a file would create a duplicate (same name), it asks you what >> you want to do.

    This should not normally arise when copying a folder - how could there
    be a duplicate in the new copy when there wasn't in the original?

    It can happen however if copying from a case-sensitive filesystem
    to a case-insensitive one - for example if the original contained
    both invoice.pdf and Invoice.pdf.

    -- Richard

    And just to add if it isn't obvious: those two versions of invoice.pdf
    would have to be in the same directory to cause the error, which might
    help with tracking them down using Finder or spotlight searches.

    It could be Invoice.pdf/invoice.pdf as Richard suggests but also
    Invoice.pdf / Invoice.PDF is quite likely.

    Regards,
    --
    Bruce Horrocks
    Hampshire, England

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)