On Sun, Nov 03, 2013 at 10:07:36AM -0000, Harald Sitter wrote:
> Making this non-fatal (on launchpad) would be rather helpful since as of
> a couple of days ago this is blocking KDE Frameworks 5 building [1].
> Upstream is less than thrilled.
>
> [1] https://code.launchpad.net/~neon/kde-workspace/master
>
> ** Attachment added: "raw commit data of affected commit in kde-workspace"
> https://bugs.launchpad.net/ubuntu/+source/bzr-git/+bug/1084403/+attachment/3899038/+files/commit
Unfortunately just ignoring these tags is not possible without
fundamentally breaking various assumptions in bzr-git.
bzr-git does a lossless conversion from git to bzr, so it can later
regenerate the exact same git objects. This is necessary since objects
sent by the server can be sent as deltas against fulltexts that the
server knows the client has.
If these tags are ignored, then bzr-git will be unable to reproduce
git commit objects with the exact same contents, and break.
On Sun, Nov 03, 2013 at 10:07:36AM -0000, Harald Sitter wrote: /code.launchpad .net/~neon/ kde-workspace/ master /bugs.launchpad .net/ubuntu/ +source/ bzr-git/ +bug/1084403/ +attachment/ 3899038/ +files/ commit
> Making this non-fatal (on launchpad) would be rather helpful since as of
> a couple of days ago this is blocking KDE Frameworks 5 building [1].
> Upstream is less than thrilled.
>
> [1] https:/
>
> ** Attachment added: "raw commit data of affected commit in kde-workspace"
> https:/
Unfortunately just ignoring these tags is not possible without
fundamentally breaking various assumptions in bzr-git.
bzr-git does a lossless conversion from git to bzr, so it can later
regenerate the exact same git objects. This is necessary since objects
sent by the server can be sent as deltas against fulltexts that the
server knows the client has.
If these tags are ignored, then bzr-git will be unable to reproduce
git commit objects with the exact same contents, and break.
Jelmer