Re: BUGREPORT: Modified files on a fresh clone on M2 MacBook Pro

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Mar 22, 2023, 18:22 UTC
Message-ID: <73af529d-e918-445d-b0ee-9506e28188af@app.fastmail.com>
In-Reply-To: <3FC6072C-5856-437F-9B4F-BC182921426D@mac.com>

On Wed, Mar 22, 2023, at 18:29, Sjur Moshagen wrote:

Show 20 quoted lines

> [snip]
>
> Yes, of course :)
>
> It only happens with binary files (.docx and .pdf files), which got me 
> suspicious. It turned out that updating the .gitattributes file fixed 
> the issue, cf
>
> https://github.com/giellalt/lang-sma/commit/fb5b56fa9fa7f25be1a1d7190bbb4d12b5a908fd#diff-618cd5b83d62060ba3d027e314a21ceaf75d36067ff820db126642944145393e
>
> What is still a mystery to me is that there has been no issues with 
> cloning files on Intel Macs (git version 2.39.2), or on Linux (git 
> version 2.34.1), even with the old .gitattributes file - ie the cloned 
> repos were clean on these systems. Only on M2 (possibly also M1) Macs 
> did this issue pop up.
>
> Please tell me if there is more I can do to help.
>
> Regards,
> Sjur

I still get a dirty working repository after a fresh clone (on Linux, git version 2.40.0) on your commit 6425cb09a8d0 (Apply changes 127, 2023-03-22):

    $ git status
    On branch main
    Your branch is up to date with 'origin/main'.

    Changes not staged for commit:
      (use "git add <file>..." to update what will be committed)
      (use "git restore <file>..." to discard changes in working directory)
            modified:   "corp/SN\303\205SNINGEN 2014/43 uke/N\303\246ringsliv.doc"
            modified:   "corp/SN\303\205SNINGEN 2015/26 uke/\303\230lsamling.doc"
            modified:   "corp/SN\303\205SNINGEN 2015/38 uke /SAK1 -s\303\270rsamisk.doc"
            modified:   "corp/SN\303\205SNINGEN 2015/38 uke /SAK1.doc"
            modified:   "corp/Sn\303\245sningen 2012/20 uke/Artig med animasjon - samisk.doc"
            modified:   "corp/Sn\303\245sningen 2012/20 uke/Artig med animasjon.doc"
            modified:   "corp/Sn\303\245sningen 2012/4. uke/Mange vil l\303\246re s\303\270rs/Mange vil l\303\246re s\303\270rsamisk - saemien.doc"
            modified:   "corp/Sn\303\245sningen 2012/4. uke/Mange vil l\303\246re s\303\270rs/Mange vil l\303\246re s\303\270rsamisk.doc"
            modified:   "corp/Sn\303\245sningen 2012/4. uke/P\303\245 sameskolen/Det er p\303\245 sameskolen jeg f\303\270ler meg hjemme - samisk.doc"
            modified:   "corp/Sn\303\245sningen 2012/4. uke/P\303\245 sameskolen/Det er p\303\245 sameskolen jeg f\303\270ler meg hjemme.doc"
            modified:   "corp/Sn\303\245sningen 2013/50 uke/Dramatikk og kj\303\246rlighet - S\303\270rsamisk.doc"

    no changes added to commit (use "git add" and/or "git commit -a")

Note that this `doc` extension was not covered by your update.

But it becomes clean if I remove this line:

    $ git diff
    diff --git a/.gitattributes b/.gitattributes
    index bbd8c0db810d..3959fefadfc1 100644
    --- a/.gitattributes
    +++ b/.gitattributes
    @@ -2,7 +2,6 @@
     # DO NOT EDIT - the file is updated via the template system.

     # Some defaults:
    -* text   eol=lf
     *.png    binary
     *.jpg    binary
     *.jpeg   binary

-- 
Kristoffer Haugsbakk