Skip to content
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

FIle collision on case sensitive file systems after recent release. #325

Closed
KristofferC opened this issue Apr 28, 2021 · 0 comments · Fixed by #326
Closed

FIle collision on case sensitive file systems after recent release. #325

KristofferC opened this issue Apr 28, 2021 · 0 comments · Fixed by #326

Comments

@KristofferC
Copy link
Member

KristofferC commented Apr 28, 2021

#323 added some test files that have collisions one case insensitive file systems.

In particular, the two files 'test/files/doxy.MID' and 'test/files/doxy.mid' only differ in the casing.

This causes the following problem:

base ❯ git clone https://github.com/JuliaIO/FileIO.jlCloning into 'FileIO.jl'...
...
warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:

  'test/files/doxy.MID'
  'test/files/doxy.mid'

This also confuses some Pkg tree hash routine so whenever someone installs FileIO they now get:

┌ Warning: tarball content does not match git-tree-sha1, for package downloaded from https://pkg.julialang.org/package/5789e2e9-d7fb-5bc7-8068-2c6fae9b9549/b647ed22f176a4f12eabe2afd90d19a95af2e8ca, expected b647ed22f176a4f12eabe2afd90d19a95af2e8ca got 8dad1c042a8fadf62c5ea801a93abf54d00eeecb

The solution is to rename one of the files and make a new release.

cc @johnnychen94, @VasanthManiVasi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant