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

Cannot clone repo due to bad timezone error #3805

Closed
nyuszika7h opened this Issue Jan 10, 2017 · 8 comments

Comments

Projects
None yet
3 participants
@nyuszika7h

nyuszika7h commented Jan 10, 2017

nyuszika7h@cadoth ~/src > git clone https://github.com/kennethreitz/requests.git
Cloning into 'requests'...
remote: Counting objects: 18867, done.
remote: Compressing objects: 100% (11/11), done.
error: object 5e6ecdad9f69b1ff789a17733b8edc6fd7091bd8: badTimezone: invalid author/committer line - bad time zone
fatal: Error in object
fatal: index-pack failed
@Lukasa

This comment has been minimized.

Member

Lukasa commented Jan 10, 2017

Thanks for raising this issue! In future, please search the issue history before opening new issues on projects, as you'll often find that your issue has been reported before. In this case, this is a duplicate of #3088, #3008, and #2690.

@Lukasa Lukasa closed this Jan 10, 2017

@nyuszika7h

This comment has been minimized.

nyuszika7h commented Jan 10, 2017

Sorry. I did search, but didn't get the right terms.

@Lukasa

This comment has been minimized.

Member

Lukasa commented Jan 10, 2017

If you have an error message, it's usually sufficient just to try to search for that. In this case, I searched for "fatal: index-pack failed" and #3088 popped right up.

@nyuszika7h

This comment has been minimized.

nyuszika7h commented Jan 10, 2017

Yeah, well, I searched for "timezone" because I didn't realize there's a space in it in the error message. (Also, it's strange, I don't remember enabling fsck, but I found it in my git config.)

@Lukasa

This comment has been minimized.

Member

Lukasa commented Jan 10, 2017

fsck is on-by-default on new installs of git, so unless you're persisting a gitconfig from an older version of git you'll always find it on. =)

@nyuszika7h

This comment has been minimized.

nyuszika7h commented Jan 10, 2017

I do have a custom gitconfig, so that's strange. This kind of issue could have been avoided if they enabled fsck by default in the first place, but oh well. You can't rewrite 6 years of history now, that would just mess things up even more. I do wonder how that weird timezone ended up in a commit though.

@Lukasa

This comment has been minimized.

Member

Lukasa commented Jan 10, 2017

Yeah, it's really annoying because it causes legitimate problems for lots of people, especially those who use git in automated scripts, but we really can't do anything about it now. =(

@melvinvermeeren

This comment has been minimized.

melvinvermeeren commented Sep 20, 2018

Even though it hurts to do this, you may want to consider rewriting the history to fix this problem once and for all. For Breathe I ended up doing this and I added a notice to the top of the README, in the biggest heading possible, for a while.

Projects using this as a submodule will have to update the SHA once. But currently many setups encounter a clone failure meaning existing submodules will not work at all and cloning this repo directly won't either.

Ref: michaeljones/breathe#340 (comment)

@requests requests locked as resolved and limited conversation to collaborators Sep 21, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.