Testing package imports locally

[James Westby]

Some updates since I sent the mail last time.

On Wed, 17 Feb 2010 12:02:48 +1100, Robert Collins <robertc at robertcollins.net> wrote:
> 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.)

There is now also

  --no-existing

to do a fresh import ignoring what is on LP already. I've found that
most of the "<foo> is not found in <bar>" type errors that suggest
repository corruption don't reproduce on a fresh import, suggesting that
they are bugs fixed in newer bzr, or are caused by the act of pushing to
LP.

There is also

  --check

to run check on the repository as it finishes. However, this just puts
the info in the log as the check_dwim API doesn't tell you if any
problems were detected as far as I could see.

> 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.

You may need to create ./logs/diffs and ./logs/merges as well, I don't
think I made it create those if they didn't exist.

> Current failures are at
> 
>   http://package-import.ubuntu.com/failures/.bzr/failures/

As stated elsewhere this is now

  http://package-import.ubuntu.com/status/


Thanks,

James