{"thread":{"id":"43388","subject":"Corrupt pack file using older versions of git on a newer repo..","startedAt":"2006-12-20T13:27:40Z","lastAt":"2006-12-20T15:30:52Z","messageCount":2,"participants":["Sean","Nicolas Pitre"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"294585","messageId":"BAYC1-PASMTP11ADF6C984028A9DED853FAECF0@CEZ.ICE","threadId":"43388","inReplyTo":null,"subject":"Corrupt pack file using older versions of git on a newer repo..","fromName":"Sean","fromEmail":"seanlkml@sympatico.ca","sentAt":"2006-12-20T13:27:40Z","receivedAt":"2006-12-20T13:27:40Z","isPatch":false,"sender":{"key":"seanlkml@sympatico.ca","avatar":"https://gravatar.com/avatar/f92923f54fc08c401fc59b71829d4b89e9b8087fbba45ff87c82e6a83aee02ae?d=mp&s=160"},"body":"\nThis is probably expected behavior, but when bisecting another Git\nissue[1], i found that after a fresh clone of the git repository using\n1.4.4.2 I got the following corrupt pack file when accessing that repo\nwith an old version of git:\n\n$ git --version\ngit version 1.4.2\n\n$ git log\nfatal: corrupted pack file .git/objects/pack/pack-d75f6a8307f8d8ce9727fe27107486839c54aef6.pack\n\nWhen reverting to 1.4.3 instead, a git reset triggered the corrupt pack\nerror.  Anyway, just a heads up in case it actually matters.\n\nSean\n\n[1]  The \"Git\" issue turned out not to be Git at all but rather the\nBeagle search daemon which seems to touch file stat information as\nit scans files in a git repo causing strange git status and diff\n"},{"id":"298409","messageId":"Pine.LNX.4.64.0612201024370.18171@xanadu.home","threadId":"43388","inReplyTo":"BAYC1-PASMTP11ADF6C984028A9DED853FAECF0@CEZ.ICE","subject":"Re: Corrupt pack file using older versions of git on a newer repo..","fromName":"Nicolas Pitre","fromEmail":"nico@cam.org","sentAt":"2006-12-20T15:30:52Z","receivedAt":"2006-12-20T15:30:52Z","isPatch":false,"sender":{"key":"nico@fluxnic.net","avatar":"https://avatars.githubusercontent.com/u/702790?v=4"},"body":"On Wed, 20 Dec 2006, Sean wrote:\n\n> \n> This is probably expected behavior, but when bisecting another Git\n> issue[1], i found that after a fresh clone of the git repository using\n> 1.4.4.2 I got the following corrupt pack file when accessing that repo\n> with an old version of git:\n> \n> $ git --version\n> git version 1.4.2\n> \n> $ git log\n> fatal: corrupted pack file .git/objects/pack/pack-d75f6a8307f8d8ce9727fe27107486839c54aef6.pack\n\nTo make that repository accessible with older git versions simply run \ngit-repack -a -d using version 1.4.4.2.\n\nThe clone with version 1.4.4.2 added OBJ_OFS_DELTA objects to the pack \nwhich older git versions don't know about.  Those objects are used for \npack transport when both ends know about them as they take less space.  \nBut the repack doesn't use them by default so a full repack will get rid \nof them automatically.\n\n\n"}]}