Comment 9 for bug 672389

Jelmer Vernooij <email address hidden>:
> Do you mean the "Technical details about this PPA" box? This seems to be
> working for me at moment, what breaks for you?

Hm. I was getting an error message an hour ago, but now see instructions.
Must have been some transient database glitch.

> The contents of the box are:
>
> This PPA can be added to your system manually by copying the lines below
> and adding them to your system's software sources.
>
> deb http://ppa.launchpad.net/jelmer/bzr-dailies/ubuntu maverick main
> deb-src http://ppa.launchpad.net/jelmer/bzr-dailies/ubuntu maverick main
>
> Signing key: 1024R/EB27448B
> Fingerprint: CA7C60A52494B0FD5CD5292102949186EB27448B

I did this.

root@snark:/etc/apt/sources.list.d# cat jelmer-vernooij-bzr-fastimport.list
deb http://ppa.launchpad.net/jelmer/bzr-dailies/ubuntu maverick main
root@snark:/etc/apt/sources.list.d#

I got an update of your dailies this way, though it complained of
being unable to authenticate. Then, because I like authentication, I
moved the manually-created repo entry to a .save and went
the add-apt-repository route.

root@snark:/etc/apt/sources.list.d# add-apt-repository ppa:rbelem/bzr-fastimport
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyserver keyserver.ubuntu.com --recv 68D4D9D58AB348A98F3C5328BC67161E45243C2D
gpg: requesting key 45243C2D from hkp server keyserver.ubuntu.com
gpg: key 45243C2D: public key "Launchpad rbelem-main" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)

This appeared to succeed, but another attempt at upgrade just to check gave me
this:

Failed to fetch http://ppa.launchpad.net/rbelem/bzr-fastimport/ubuntu/dists/lucid/main/binary-amd64/Packages.gz 404 Not Found
Some index files failed to download, they have been ignored, or old ones used instead.

So I'm guessing there's a glitch in the PPA build chain somewhere. Shouldn't
these packages be arch-independent? Dropping back to your repo pointer from
rebelem's banishes that error but brings back the failure to authenticate.

> Yeah, I'm not aware of any similar tools at the moment. Unfortunately
> the bzr and hg fastimport/fastexport streams are not yet lossless at the
> moment, but things are slowly improving. The vcs-fastimport-devs list
> was originally started to discuss extensions to the fastimport format,
> and some have already made it in.

I'm going to propose two extensions based on my experience.

Now for the good news: with your update, I've done a successful bzr repo
build from a dumpfile. So that's one problem solved.

Now for more bad news.

esr@snark:~/software/bzr-testrepo$ bzr fast-export --plain
bzr: ERROR: command 'fast-export' requires argument SOURCE

What the hack is this "source" argument anyway? The on-line help fails to
explain it. I tried giving it an argument of "." but that crashed the
exporter. So did the dummy argument "FOO" that it was accepting before.

I note, in the on-line-help, this:

 * *commit-properties* - custom metadata per commit that Bazaar stores
   in revision properties (e.g. branch-nick and bugs fixed by this
   change) will be included in the output.

If commit-properties are now officially part of the format, that's
one of my feature requests down - but I can't find any indication of
this in the git docs. What's the actual state of play?
--
  <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>