bzr-hg version 0.2.0~bzr409-1.1 failed to build in oneiric

Bug #831375 reported by Matthias Klose on 2011-08-22
28
This bug affects 4 people
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://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2689756

Details about the rebuild:
http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html

Direct link to the build log: https://launchpad.net/ubuntu/+archive/test-rebuild-20110816/+build/2689756/+files/buildlog_ubuntu-oneiric-i386.bzr-hg_0.2.0%7Ebzr409-1.1_FAILEDTOBUILD.txt.gz

This log snippet might be of interest, since it triggered the matcher 'Source-dependencies not satisfied'.
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/hgrc.d/hgext.rc with new version
Setting up python-central (0.6.17) ...
Setting up python-pkg-resources (0.6.16-1) ...
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

Matthias Klose (doko) on 2011-08-22
Changed in bzr-hg (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Jelmer Vernooij (jelmer) wrote :

This is fixed by the latest bzr-hg in Debian, I'll request a sync.

Changed in bzr-hg (Ubuntu Oneiric):
assignee: nobody → Jelmer Vernooij (jelmer)
status: Confirmed → In Progress
Matthias Klose (doko) wrote :

the synced 0.2.0~bzr511-1 still ftbfs

Matthias Klose (doko) wrote :

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
Jelmer Vernooij (jelmer) on 2011-12-20
Changed in bzr-hg (Ubuntu Oneiric):
assignee: Jelmer Vernooij (jelmer) → nobody
Matthias Klose (doko) wrote :

0.2.0~bzr540-1build1 still ftbfs in precise

tags: added: precise
Jelmer Vernooij (jelmer) wrote :

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 :

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 :

Also, shouldn't this be critical? I mean, you can't even use the package until this bug is fixed...

Jelmer Vernooij (jelmer) wrote :

bzr-hg has been removed from precise. See Debian bug 659931 for the background of the removal (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659931).

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
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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