Re: Problems with unrecognized headers in git bundles
On Wed, Feb 22, 2012 at 9:25 PM, Øyvind A. Holm <sunny@sunbase.org> wrote:
Show 30 quoted lines
> On 22 February 2012 17:05, Jannis Pohlmann wrote:
>> Hi,
>>
>> creating bundles from some repositories seems to lead to bundles with
>> incorrectly formatted headers, at least with git >= 1.7.2. When
>> cloning from such bundles, git prints the following error/warning:
>>
>> $ git clone perl-clone.bundle perl-clone
>> Cloning into 'perl-clone'...
>> warning: unrecognized header: --work around mangled archname on...
>>
>> This can be reproduced easily with git from any version >= 1.7.2 or
>> from master, using the following steps:
>>
>> git clone git://perl5.git.perl.org/perl.git perl
>> GIT_DIR=perl/.git git bundle create perl-clone.bundle --all
>> git clone perl-clone.bundle perl-clone
>>
>> The content of the bundle is:
>>
>> # v2 git bundle
>> -- work around mangled archname on win32 while finding...
>> 39ec54a59ce332fc44e553f4e5eeceef88e8369e refs/heads/blead
>> 39ec54a59ce332fc44e553f4e5eeceef88e8369e refs/remotes/origin/HEAD
>
> Have researched this a bit, and I've found that all git versions back to
> when git-bundle was introduced (around v1.5.4) produces the same invalid
> line. The culprit is commit 3e8148feadabd0d0b1869fcc4d218a6475a5b0bc in
> perl.git, branch 'maint-5.005'. The log message of that commit contains
> email headers, maybe that's the reason git bundle gets confused?
For the lazy, the commit can be found here:
http://perl5.git.perl.org/perl.git/commit/3e8148feadabd0d0b1869fcc4d218a6475a5b0bc
Erik Faye-Lund <kusmabite@gmail.com>