From: Jonathan Nieder <jrnieder@gmail.com>
To: Jelmer Vernooij <jelmer@samba.org>
Cc: Gabriel Filion <lelutin@gmail.com>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Jeff King <peff@peff.net>, David Barr <davidbarr@google.com>,
Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [RFC/PATCH git-remote-bzr] Adapt to new semantics of remote-helper "import" command
Date: Sun, 22 Jan 2012 18:12:28 -0600 [thread overview]
Message-ID: <20120123001228.GA1209@burratino> (raw)
In-Reply-To: <4F1C9D4C.6090603@samba.org>
Jelmer Vernooij wrote:
> On 01/22/2012 06:46 AM, Jonathan Nieder wrote:
>> BTW, would you mind if I sent a patch to include git-remote-bzr in
>> git.git under contrib/?
>
> Please note that the bzr-git package, which provides git integration
> for bzr and vice versa, also includes a 'git-remote-bzr' command.
That's good to hear. Then there should be no need for git.git to have
its own helper.
Unfortunately, when I try to clone any repo, at the last step I get
Traceback (most recent call last):map 6/7
File "/usr/lib/git-core/git-remote-bzr", line 220, in <module>
commands[argv[0]](argv, shortname, remote_dir)
File "/usr/lib/git-core/git-remote-bzr", line 89, in cmd_list
for ref, git_sha1 in refs.as_dict().iteritems():
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 196, in as_dict
ret[key] = self[("%s/%s" % (base, key)).strip("/")]
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 267, in __getitem__
_, sha = self._follow(name)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 249, in _follow
contents = self.read_ref(refname)
File "/usr/lib/python2.7/dist-packages/dulwich/repo.py", line 225, in read_ref
contents = self.read_loose_ref(refname)
File "/usr/lib/python2.7/dist-packages/bzrlib/plugins/git/refs.py", line 129, in read_loose_ref
tag_name = ref_to_tag_name(ref)
File "/usr/lib/python2.7/dist-packages/bzrlib/plugins/git/refs.py", line 89, in ref_to_tag_name
raise ValueError("unable to map ref %s back to tag name" % ref)
ValueError: unable to map ref refs/heads back to tag name
Will file a bug.
next prev parent reply other threads:[~2012-01-23 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 5:46 [RFC/PATCH git-remote-bzr] Adapt to new semantics of remote-helper "import" command Jonathan Nieder
2012-01-22 23:35 ` Jelmer Vernooij
2012-01-23 0:12 ` Jonathan Nieder [this message]
2012-02-03 9:43 ` Gabriel Filion
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=20120123001228.GA1209@burratino \
--to=jrnieder@gmail.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=jelmer@samba.org \
--cc=lelutin@gmail.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/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).