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

Git repository is broken #38

Open
nevyn opened this issue Jul 26, 2012 · 1 comment
Open

Git repository is broken #38

nevyn opened this issue Jul 26, 2012 · 1 comment

Comments

@nevyn
Copy link

nevyn commented Jul 26, 2012

This repo has been modified by github's web browser editor at a point where it wrote corrupt git objects to the repo.

These trees are broken:

18:52:28 banana:~/Dev/iphone2/vendor/nu nevyn (master)$ git fsck --full
warning in tree 16bfc00c112096d096440f1b6281e8cdfd7d9dbc: contains zero-padded file modes
warning in tree 2698c6c49d55b360bc2fec7ede772da12cb4680f: contains zero-padded file modes
warning in tree 29f760a8f4d2577ed50ba1dab6cb0e214a664151: contains zero-padded file modes
warning in tree 32cbdd8d58c9731c460a1563237c8aeac26877ef: contains zero-padded file modes
warning in tree 3eb4a46becf98642255c9916b2fe0d7fea7b004f: contains zero-padded file modes
warning in tree 4479a800ea37bbc6950126f42bee6d1747efe20c: contains zero-padded file modes
warning in tree 4f8329ae933a3fdb10920d9ca25f7f6f8b144bd4: contains zero-padded file modes
warning in tree 7a2dc8c2ec60756f9c61340875e96862cb34149f: contains zero-padded file modes
warning in tree ddf9dcc2d2a905e9246cc4f2e92af7be44a47241: contains zero-padded file modes
warning in tree e11e24ecde5c6691aa46d95e6ad43f05422ad420: contains zero-padded file modes
warning in tree ee6e690c3dbce7e7678b477cb9b2ebf62cb6121c: contains zero-padded file modes
warning in tree f04f920a90c4db7063cbeed339bff941d82122de: contains zero-padded file modes

This means that the repository can't be pushed to a git server that is less forgiving about errors. (I'm trying to fork all my external dependencies (so we can keep building even if github or bitbucket is down), and failing to push the fork to gerrit).

The only way to fix it is to rewrite the tree, which will be very annoying for all forks with outstanding changes. If you still want to go through with it, instructions can be found in this mailing thread:
http://thread.gmane.org/gmane.comp.version-control.git/143288

@timburks
Copy link
Member

thanks, looking into it

Sent from my iPhone

On Jul 26, 2012, at 9:56 AM, Joachim Bengtsson [email protected] wrote:

This repo has been modified by github's web browser editor at a point where it wrote corrupt git objects to the repo.

These trees are broken:

18:52:28 banana:~/Dev/iphone2/vendor/nu nevyn (master)$ git fsck --full
warning in tree 16bfc00c112096d096440f1b6281e8cdfd7d9dbc: contains zero-padded file modes
warning in tree 2698c6c49d55b360bc2fec7ede772da12cb4680f: contains zero-padded file modes
warning in tree 29f760a8f4d2577ed50ba1dab6cb0e214a664151: contains zero-padded file modes
warning in tree 32cbdd8d58c9731c460a1563237c8aeac26877ef: contains zero-padded file modes
warning in tree 3eb4a46becf98642255c9916b2fe0d7fea7b004f: contains zero-padded file modes
warning in tree 4479a800ea37bbc6950126f42bee6d1747efe20c: contains zero-padded file modes
warning in tree 4f8329ae933a3fdb10920d9ca25f7f6f8b144bd4: contains zero-padded file modes
warning in tree 7a2dc8c2ec60756f9c61340875e96862cb34149f: contains zero-padded file modes
warning in tree ddf9dcc2d2a905e9246cc4f2e92af7be44a47241: contains zero-padded file modes
warning in tree e11e24ecde5c6691aa46d95e6ad43f05422ad420: contains zero-padded file modes
warning in tree ee6e690c3dbce7e7678b477cb9b2ebf62cb6121c: contains zero-padded file modes
warning in tree f04f920a90c4db7063cbeed339bff941d82122de: contains zero-padded file modes

This means that the repository can't be pushed to a git server that is less forgiving about errors. (I'm trying to fork all my external dependencies (so we can keep building even if github or bitbucket is down), and failing to push the fork to gerrit).

The only way to fix it is to rewrite the tree, which will be very annoying for all forks with outstanding changes. If you still want to go through with it, instructions can be found in this mailing thread:
http://thread.gmane.org/gmane.comp.version-control.git/143288


Reply to this email directly or view it on GitHub:
#38

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

No branches or pull requests

2 participants