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

[BUG] Remove outdated duplicate files to avoid file collission on case-insensitive filesystem #2330

Closed
1 of 2 tasks
martinyde opened this issue Feb 19, 2024 · 1 comment · Fixed by #2517
Closed
1 of 2 tasks

Comments

@martinyde
Copy link

If you have problems with the installation please use our community forum

What set up are you using

  • Cloud Hosted Version
  • Self Hosted

Describe the bug
When cloning this repository into a case-insensitive filesystem there are a few file collisions, mainly in the public/assets/images/Screenshots folder.

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:

  'public/assets/images/Screenshots/Blueprints.png'
  'public/assets/images/Screenshots/blueprints.png'
  'public/assets/images/Screenshots/Calendar.png'
  'public/assets/images/Screenshots/calendar.png'
  'public/assets/images/Screenshots/Docs.png'
  'public/assets/images/Screenshots/docs.png'
  'public/assets/images/Screenshots/Goals.png'
  'public/assets/images/Screenshots/goals.png'
  'public/assets/images/Screenshots/ProjectDashboard.png'
  'public/assets/images/Screenshots/projectDashboard.png'
  'public/assets/lottie/leo/Pirate.json'
  'public/assets/lottie/leo/pirate.json'

To Reproduce
Steps to reproduce the behavior:

  1. Clone the repository into a case-insensitive filesystem

Expected behavior
The repo clones without file collision.

Leantime Version
v3.0.6

@marcelfolaron
Copy link
Contributor

Fixed in 3.1.0-beta

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.

2 participants