Comment 3 for bug 1372149

Hi Jelmer,

Hi Jelmer,

The HG guys are interested in this bug but they think its a bzr-git issue.
Does Dulwich preserve or ignore extra fields?

---------- Forwarded message ----------
From: Siddharth Agarwal <email address hidden>
Date: Tue, Sep 30, 2014 at 12:15 PM
Subject: Re: HG:rename tags not removed by hg-git
To: <email address hidden>, Susan Spencer <email address hidden>
Cc: Siddharth Agarwal <email address hidden>

On 09/30/2014 10:13 AM, Augie Fackler wrote:

> On Tue, Sep 30, 2014 at 10:32 AM, Susan Spencer <email address hidden>
> wrote:
>
>> Should the 'HG:rename' tags be transferred from hg to git?
>> Git doesn't generate an error message from these tags.
>> However, here is my problem with these tags...
>>
>> My project is converted from hg/bitbucket to git/github to bzr/launchpad.
>>
>> bzr returns an error message on the HG:rename tags as:
>>
>> raise UnknownCommitExtra(commit, [item[0] for item in commit.extra])
>> bzrlib.plugins.git.errors.UnknownCommitExtra: Unknown extra fields in
>> <Commit 56ead206c93f1ed9d6f1d46cbfa2a8e79cdad63c>: ['HG:rename',
>> 'HG:rename', 'HG:rename', 'HG:rename', 'HG:rename', 'HG:rename',
>> 'HG:rename', 'HG:rename', 'HG:rename', 'HG:rename', 'HG:rename',
>> 'HG:rename', 'HG:rename', 'HG:rename', 'HG:rename', 'HG:rename'].
>> Import failed
>>
> You're probably doing the conversion using a relatively recent hg-git,
> which just started storing this data in the hidden metadata section of
> git commits. This is (probably) a bzr-git bug wherein they're choking
> on metadata fields they don't understand, rather than just preserving
> or dropping them as appropriate.
>

Yes, please report this to bzr-git. bzr-git isn't matching git's or
Dulwich's behavior of preserving but otherwise ignoring unknown extra
fields.

- Siddharth