From: Alex Bennee <kernel-hacker@bennee.com>
To: git@vger.kernel.org, David Reitter <david.reitter@gmail.com>
Subject: Re: bzr to git syncing
Date: Fri, 28 Aug 2009 17:02:22 +0100 [thread overview]
Message-ID: <b2cdc9f30908280902m22d594bam3c70259d4c296e52@mail.gmail.com> (raw)
In-Reply-To: <F84D4C0F-1CEF-4853-84DB-B7927CBE62B3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
2009/6/29 David Reitter <david.reitter@gmail.com>:
> Does anyone have experience syncing a Bzr repository to git?
> I would ideally want two-way syncing, but even the bzr->git route would be a
> start.
I've a sneaking suspicion a breakage has been introduced to either the
git-bzr script or
the bzr fast-import module. I say this as I have successfully pulled
from a bzr repo into
git before but having need to do it today and I get a crash in fast-import.
A few quick questions:
* What versions of git/bzr are you using (me: git 1.6.4, bzr 1.17)?
* Which git-bzr script are you using (me:
http://github.com/mcepl/git-bzr/tree/master)?
I've attached the fast-import crash I'm seeing. Are you seeing the
same sort of failure?
--
Alex, homepage: http://www.bennee.com/~alex/
http://www.half-llama.co.uk
[-- Attachment #2: fast_import_crash_21774 --]
[-- Type: application/octet-stream, Size: 1094 bytes --]
fast-import crash report:
fast-import process: 21774
parent process : 21773
at Fri Aug 28 16:54:14 2009
fatal: Corrupt mode: M 040000 - content
Most Recent Commands Before Crash
---------------------------------
commit refs/heads/bzr/upstream
mark :1
committer Alexander Sack <asac@jwsdot.com> 1181743954 +0200
data 39
M 644 inline build.sh
data 3963
M 644 inline chrome.manifest
data 192
M 644 inline config_build.sh
data 170
* M 040000 - content
Active Branch LRU
-----------------
active_branches = 1 cur, 5 max
pos clock name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1) 0 refs/heads/bzr/upstream
Inactive Branches
-----------------
refs/heads/bzr/upstream:
status : active loaded dirty
tip commit : 0000000000000000000000000000000000000000
old tree : 0000000000000000000000000000000000000000
cur tree : 0000000000000000000000000000000000000000
commit clock: 0
last pack :
Marks
-----
exported to /export/src/debs/cbnlfox.git/.git/bzr-git/upstream-git-map
-------------------
END OF CRASH REPORT
next prev parent reply other threads:[~2009-08-28 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 19:12 bzr to git syncing David Reitter
2009-08-28 16:02 ` Alex Bennee [this message]
2009-08-28 16:19 ` Sverre Rabbelier
2009-08-28 17:47 ` Alex Bennee
2009-08-28 17:49 ` Sverre Rabbelier
2009-08-31 7:49 ` [Vcs-fast-import-devs] " Ian Clatworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b2cdc9f30908280902m22d594bam3c70259d4c296e52@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=david.reitter@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).