Re: Git issue clone issue with .gdb , .loz, & .las files
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- May 13, 2022, 01:49 UTC
- Message-ID
- <Yn23d9UWONDFzH7n@camp.crustytoothpaste.net>
- In-Reply-To
- <SA1PR05MB8454906260C1851A39813916ACCB9@SA1PR05MB8454.namprd05.prod.outlook.com>
On 2022-05-12 at 15:36:25, Robert Brown wrote:
> Hi team,
Hey,
> I started a thread in GitHub, but they pointed me to you. We're having a binary comparison problems when cloning a repo in Git on Windows (git version 2.36.1.windows.1), LFS is installed but is not tracking files. > > So far we have noticed .gdb, .las, and .loz files are not even close to the same size and don't open after cloning the repo. Everything else seems to clone fine at the moment, confidence to moving to Git is a problem because of this on the team. I'm looking to figure out a way to make sure we are getting binary matched clones when doing so. We sure would appreciate any help you can give us.
As I mentioned, I think Git LFS is a red herring here. There are no patterns in .gitattributes, so the fact that it's installed is irrelevant, since it's not being used.
To summarize what I said on the Git LFS issue tracker, I think you've seeing a problem with Git on Windows where it doesn't always handle files larger than 4 GiB properly. My guess is that if you created the repository in WSL or on a Linux box, things would work, provided you used a 64-bit binary. Can you try doing that and seeing if cloning to another Linux-based directory works properly for you in that case?
-- brian m. carlson (he/him or they/them) Toronto, Ontario, CA