laserjock at ubuntu.com
Sat Feb 7 17:26:01 GMT 2009
2009/2/7 Daniel Glassey <dglassey at gmail.com>:
> On Fri, Feb 6, 2009 at 2:06 PM, Dmitrijs Ledkovs
> <dmitrij.ledkov at gmail.com> wrote:
>> 2009/2/6 Daniel Glassey <dglassey at gmail.com>:
>>> $bzr co lp:~pkgcrosswire/bibledit/main
>>> bzr: ERROR: Unknown branch format: 'Bazaar Branch Format 7 (needs bzr 1.6)\n'
>>> 2 problems with that
>>> (1) My laptop is hardy which is bzr 1.3
>> Enable, update, upgrade
>> deb http://ppa.launchpad.net/bzr/ppa/ubuntu hardy main
>> deb-src http://ppa.launchpad.net/bzr/ppa/ubuntu hardy main
> Hmmm, that repo looks broken at the mo
> $ sudo apt-get install bzrtools bzr bzr-gtk bzr-builddeb
> The following packages have unmet dependencies.
> bzrtools: Depends: bzr (< 1.11~) but 1.11-1~bazaar1~hardy1 is to be installed
> E: Broken packages
> bzrtools is a dep of bzr-builddeb
Yeah, they haven't had a chance to get bzrtools upgraded for the
latest bzr version. I've been poking #bzr about it. Hopefully it
should be working soon.
> I'll try the build from source later
>>> (2) Debian lenny and sid have bzr 1.5
> [building from source]
>> Try this. Hope it works!
> Thanks, I'll try that when I get back but this is only a temporary
> measure until the jaunty deadline. imho It would be very unhelpful,
> maybe even 'inconsiderate' (Ubuntu CoC) for Debian to have to use
> extra steps like that just to get access to the repo.
This is a problem, and not just for Debian. I've discussed this issue
with a Launchpad code hosting developer. I think perhaps Launchpad
needs to be able to specify what versions of bzr a branch will work
with *and* allow people to easily change the branch format to
something more compatible if so desired. The problem right now is that
people are using such a broad range of bzr versions (bzr releases
monthly) that a backwards-incompatible change in branch format, even
if not very often, can really be a pain.
More information about the Pkg-crosswire-devel