bzr-hg version 0.2.0~bzr409-1.1 failed to build in oneiric
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| bzr-hg (Ubuntu) |
High
|
Unassigned | ||
| Oneiric |
High
|
Unassigned | ||
| Precise |
High
|
Unassigned |
Bug Description
bzr-hg version 0.2.0~bzr409-1.1 failed to build in oneiric
Link to failed build: https:/
Details about the rebuild:
http://
Direct link to the build log: https:/
This log snippet might be of interest, since it triggered the matcher 'Source-
Excerpt 276 lines into the build log:
Setting up intltool-debian (0.35.0+20060710.1) ...
Setting up po-debconf (1.0.16+nmu1) ...
Setting up debhelper (8.9.0ubuntu1) ...
Setting up mercurial-common (1.9.1-1) ...
Setting up mercurial (1.9.1-1) ...
Creating config file /etc/mercurial/
Setting up python-central (0.6.17) ...
Setting up python-
Setting up python-testtools (0.9.11-1) ...
Processing triggers for python-central ...
Setting up python-bzrlib.tests (2.4.0-0ubuntu2) ...
Setting up python-subunit (0.0.6-3) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Checking correctness of source dependencies...
After installing, the following source dependencies are still unsatisfied:
mercurial(inst 1.9.1-1 ! << wanted 1.9~)
Source-dependencies not satisfied; skipping bzr-hg
Changed in bzr-hg (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Jelmer Vernooij (jelmer) wrote : | #1 |
Changed in bzr-hg (Ubuntu Oneiric): | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
status: | Confirmed → In Progress |
Matthias Klose (doko) wrote : | #2 |
the synced 0.2.0~bzr511-1 still ftbfs
Matthias Klose (doko) wrote : | #3 |
in package set bzr
Changed in bzr-hg (Ubuntu Oneiric): | |
milestone: | none → ubuntu-11.10 |
Changed in bzr-hg (Ubuntu Precise): | |
milestone: | ubuntu-11.10 → none |
Changed in bzr-hg (Ubuntu Oneiric): | |
milestone: | ubuntu-11.10 → none |
status: | In Progress → Won't Fix |
Why is this Won't Fix in Oneiric? Currently bzr-hg cannot be installed from the package repository due to this packaging bug.
tags: | added: packaging |
Changed in bzr-hg (Ubuntu Oneiric): | |
assignee: | Jelmer Vernooij (jelmer) → nobody |
Jelmer Vernooij (jelmer) wrote : | #6 |
I've filed a request to remove bzr-hg from precise.
Changed in bzr-hg (Ubuntu Precise): | |
assignee: | Jelmer Vernooij (jelmer) → nobody |
status: | In Progress → Triaged |
kroq-gar78 (kroq-gar78) wrote : | #7 |
So what's the problem? More specific, what's the '~' mean in the wanted version?
"After installing, the following source dependencies are still unsatisfied:
mercurial(inst 1.9.1-1 ! << wanted 1.9~)"
^^^ Taken from buildlog ^^^
Wondering primarily for my curiosity.
kroq-gar78 (kroq-gar78) wrote : | #8 |
Also, shouldn't this be critical? I mean, you can't even use the package until this bug is fixed...
Jelmer Vernooij (jelmer) wrote : | #9 |
bzr-hg has been removed from precise. See Debian bug 659931 for the background of the removal (http://
Basically, there were several serious issues with bzr-hg that didn't really make it fit for release. Rather than keeping it in (in a broken state) and exposing our users to it, I decided to ask for it to be removed for the time being. Once it is more production-ready, it can be added again.
I'm sorry if this affects you. As a workaround, you can also use hg-fastexport and bzr-fastimport to convert Mercurial repositories to Bazaar.
I'm closing this bug as Invalid, as the package no longer exists.
Changed in bzr-hg (Ubuntu Precise): | |
status: | Triaged → Invalid |
This is fixed by the latest bzr-hg in Debian, I'll request a sync.