hg import does not import all revisions in tip.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Hg Plugin |
Triaged
|
Medium
|
Unassigned | ||
Launchpad itself |
Won't Fix
|
High
|
Unassigned |
Bug Description
I have created a request for an externa (Google code)l mercurial repository (default branch) import. It seemed to work, according to the log all changeset are retrieved (see http://
We do use (a lot) branches in the external repository, but I read that the default branch should be imported completely.
When I look at the avilable branches (only relevant onces shown):
$ hg heads
changeset: 611:30e76f027936
tag: tip
user: Maarten Bezemer
date: Sat Aug 06 20:04:21 2011 +0200
summary: Copied code formatter/
changeset: 2:25bf1f28b048
user: Dmitry Barashev
date: Wed Jun 16 04:25:59 2010 +0400
summary: test branch
The 2nd branch is imported (changeset 2:25bf1f28b048) instead of the tip (changeset: 611:30e76f027936).
So, am I doing something wrong here, do I need to specicify somehow that the default (tip) branch needs to be imported?
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in bzr-hg: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: bzr-hg |
Changed in launchpad: | |
status: | Triaged → Won't Fix |
It looks like our repository contains 2 heads in the default branch (although the commit message of changeset 2 might be a bit distracting). Unfortunately the Bazaar HG Plugin (randomly?) picks the wrong one.
A solution would be to select the tip head if there are multiple heads within the default branch (or simply select the head with the highest revision number).
Another solution (although more a feature request) would be to let the user choose which branch/head should be imported.
For now, I think I'll just remove/close the unwanted head in order to be able to continue working on my project.