Local testing of imports

[James Westby]

Hi all,

We have a number of packages failing to import, for a variety of reasons.
It's useful to be able to run the code locally for testing purposes, so
I've just pushed the driver code to

  lp:~james-w/bzr-builddeb/import-scripts

They're not exactly designed to run on an arbitrary system, but you
should be able to get them to work without too much effort.

It requires bzr-builddeb, bzrtools, python-launchpadlib, python-debian
and of course bzr to be installed.

You first have to get some LP credentials:

  python create_creds.py

You should be able to get away with "Read non-private", but may want
to grant more.

You can trigger a run with

  ./import_package.py --no-push <package-name>

(The --no-push ensures that it doesn't try and push to LP if it
 succeeds.)

This will create a number of directories in your cwd. "updates"
is where the work happens, and where the final branches end up.
"revids" is where the audit data is stored. "logs" contains a log
file per-package, you can tail it to watch progress. There are
a few more of lesser importance.

Any improvements are welcome. I know the code isn't very pleasant,
and I am trying to clean up as I change things. Bug fixes are
especially welcome.

In addition, I think it would be useful if we could classify the
list of current failures. Does the LP OOPS system have code to
match tracebacks? Anyone know of anything else to do this? Perhaps
a weekly email here with counts of classified tracebacks would
help us reduce the number?

Current failures are at

  http://package-import.ubuntu.com/failures/.bzr/failures/

Thanks,

James