bzr cannot handle filenames with newlines

Bug #826671 reported by James Gregory-Monk on 2011-08-15
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Undecided
Unassigned

Bug Description

I am trying to migrate from a git repository to a bzr repository. I've tried many different routes, and have finally been pointed in the direction of bzr-git and bzr git-import command.

Unfortunately, there is a documented issue with this repository - for some reason, one of the revisions involves a filename that has code pasted into it (don't ask me how it happened!)

This particular post (in relation to git-fast-export) details the particular commit that is causing problems:
http://marc.info/?l=git&m=131253807500855&w=2

When I do bzr git-import, the following error is thrown:

bzr: ERROR: The key 'spec/blueprints/sjt__blueprint.rb
_s_slead__in
_s_sscenario
_s_sanswers_s_s_s_s_s{_sSham.answers__object_s}
_s_sjustification__selected
_s_sjustification__unselected
_s_smark__scheme_s{_sSham.single__mark__scheme__object_s}
end
mcq__blueprint.rb' is not a valid key.

Obviously it is in relation to this particular commit. Is this a bzr issue, or a problem with the git-import command not dealing with the filename properly?

Jelmer Vernooij (jelmer) on 2011-08-15
summary: - bzr git-import cannot handle 'dodgy' filenames
+ bzr cannot handle filenames with newlines
affects: bzr-git → bzr
Martin Pool (mbp) wrote :

the bzr bug is 649250.

As a workaround I think there are tools to filter the fastexport stream which could let you cut out this file.

James Gregory-Monk (jamgregory) wrote :

Hi Martin,

Thanks for your comments. Wouldn't cutting the file out of the stream break the migration process, considering that I'm trying to migrate the (as exact as possible) history from git to bzr?

On 16 August 2011 19:20, James Gregory <email address hidden> wrote:
> Hi Martin,
>
> Thanks for your comments. Wouldn't cutting the file out of the stream
> break the migration process, considering that I'm trying to migrate the
> (as exact as possible) history from git to bzr?

It will mean you don't get the exact history across. If this file was
created in error and has garbage perhaps you don't want to keep it?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers