Closed theoryshaw closed 4 years ago
Also, when I do a clean clone to either C: or D: on my machine, and then unlock the repo, I don't have these errors.
I'd rather not go down this route, if I don't have to, as I have a lot of repos i'd have to reclone again.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 0.274 ETH (49.94 USD @ $182.27/ETH) attached to it.
Hi @spacech1mp
rm -f .git/index.lock
I ran that command yesterday, while trying to troubleshoot, and didn't seem to work.
I also tried this... https://www.dropbox.com/s/bpoxo718wtl3usl/mZyYQ7IYEn.mp4?dl=0
The official way to fix this is to lock the repo (or re-clone it) and then unlock. This will refresh the Git config with the new path to git-crypt.exe
. If you don't want to do that, then you can edit .git/config
and replace the C:\
paths with D:\
paths.
Please note that @spaceCh1mp clearly doesn't know what they're talking about.
Hi Guys, In all fairness, I tried both approaches.
@AGWA's approach of changing the paths in the .git/config
file was the one that worked. I did not have to reclone.
Thanks to both of you, however.
@AGWA happy to shoot you the gitcoin bounty, if you jump on and claim.
[filter "git-crypt"] smudge = \"D:\\\\Dropbox\\\\GitHub\\\\Sports Complex\\\\Open\\\\Sports_Complex\\\\git-crypt.exe\" smudge clean = \"D:\\\\Dropbox\\\\GitHub\\\\Sports Complex\\\\Open\\\\Sports_Complex\\\\git-crypt.exe\" clean required = true [diff "git-crypt"] textconv = \"D:\\\\Dropbox\\\\GitHub\\\\Sports Complex\\\\Open\\\\Sports_Complex\\\\git-crypt.exe\" diff
Also fyi, i had to git reset --mixed
to reset things after changing the paths.
As an outside observer who actively uses and understands git-crypt
, I can confirm that what @spaceCh1mp suggested isn't even related to this issue nor does it even indicate an awareness of how smudge/clean work and what might go wrong with a moved repository.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Workers have applied to start work.
These users each claimed they can complete the work by 2 months, 1 week ago. Please review their action plans below:
1) ianlapham has applied to start work _(Funders only: approve worker | reject worker)_.
Hello,
I'd love to take a look at your project. I'm a senior engineer at Uniswap and have a bunch of experience with git and build enviroments.
I'll clone your enviroment and see if i can recreate the issue - if I can I'll work through a couple steps. 2) geceo has applied to start work _(Funders only: approve worker | reject worker)_.
Hi, i the bountie still valid ? If yes, could you, please provide more details regarding what you want us to do ?
Learn more on the Gitcoin Issue Details page.
Not sure how to troubleshoot this one.
I'm syncing my repos to a new machine via dropbox.
when i do
git status
I get the following...https://gist.github.com/theoryshaw/d22d41300037d399553d58eb0b6b11ca
The old machine had a C:/path, the new one D:/ for the repos.
Anyone have any troubleshooting suggestions?
github repo, if curious: https://github.com/OpeningDesign/Sports_Complex