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

fix(node_modules): remove duplicated file #3591

Merged
merged 1 commit into from
Jul 28, 2021

Conversation

wraithgar
Copy link
Member

Case sensitivity on filesystems is tricky

@wraithgar wraithgar requested a review from a team as a code owner July 28, 2021 17:36
@wraithgar
Copy link
Member Author

@wraithgar wraithgar force-pushed the gar/fix-case-sensitive-snafu branch 2 times, most recently from fdb28bd to f24fd6b Compare July 28, 2021 17:49
@wraithgar
Copy link
Member Author

What had happened was: socks originally had this file as containing an upper case, as evidenced by the fact that it's still upper case in their git repo: https://github.com/JoshGlazebrook/socks/tree/master/typings/common

It was published lower case in the tarball:

-rw-r--r--  0 0      0         314 Oct 26  1985 package/typings/common/receivebuffer.d.ts

And because git is case insensitive, but os/x isn't things went sideways.

@wraithgar wraithgar force-pushed the gar/fix-case-sensitive-snafu branch from f24fd6b to f6efc44 Compare July 28, 2021 18:05
@wraithgar wraithgar changed the base branch from release-next to latest July 28, 2021 18:07
@wraithgar wraithgar changed the base branch from latest to release-next July 28, 2021 18:07
@wraithgar
Copy link
Member Author

Not sure why it thinks it's also changing the npm version to what it already is but it doesn't do that locally for me in git.

@wraithgar wraithgar force-pushed the gar/fix-case-sensitive-snafu branch from f6efc44 to e197165 Compare July 28, 2021 20:14
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 this pull request may close these issues.

2 participants