bzr-fast-export problem with mysql-6.0

Bug #304943 reported by Martin Kögler
2
Affects Status Importance Assigned to Milestone
Bazaar Fast Import
Triaged
Low
Unassigned

Bug Description

bzr-fast-export has a problem with the mysql-6.0 repository (https://code.launchpad.net/~mysql/mysql-server/mysql-6.0):

Importing the dump into git fails with:
fatal: Path mysql-test/suite/rpl/r/rpl_colSize.result not in branch

The parent commit of the failing commit are:
                revno: 2599.34.8
                committer: Georgi Kodinov <email address hidden>
                branch nick: merge-6.0-5.1.29-rc
                timestamp: Fri 2008-09-05 11:16:04 +0300
                message:
                  merged 6.0-main to 6.0-5.1.29
and
                    revno: 2497.397.8
                    committer: Mats Kindahl <email address hidden>
                    branch nick: b32709-5.1-5.1.29-rc
                    timestamp: Wed 2008-09-03 22:52:54 +0200
                    message:
                      BUG#32709: Assertion failed: trx_data->empty(), file log.cc

                      Incremental fixes: updating a comment and fixing a result file.

So the failing commit must be:
                revno: 2599.34.9
                committer: Mats Kindahl <email address hidden>
                branch nick: merge-6.0-5.1.29-rc
                timestamp: Fri 2008-09-05 15:39:08 +0200
                message:
                  Merging 5.1-5.1.29-rc into 6.0-5.1.29-rc

At my option, the real culprit is this change:
bzr diff -r 2522.43.4..2522.43.5
=== renamed file 'mysql-test/r/rpl_colSize.result' => 'mysql-test/suite/rpl/r/rpl_colSize.result'
=== removed file 'mysql-test/suite/rpl/r/rpl_colSize.result'
--- mysql-test/suite/rpl/r/rpl_colSize.result 2007-07-29 22:10:42 +0000
+++ mysql-test/suite/rpl/r/rpl_colSize.result 1970-01-01 00:00:00 +0000
[...]

It renames a file and deletes it in one commit.

mfg Martin Kögler

Tags: export
tags: added: export
Changed in bzr-fastimport:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.