On Tue, 2010-02-16 at 17:14 -0600, John Arbash Meinel wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I've been wanting to get into handling some of the bugs with the package > importer, such as: > https://bugs.edge.launchpad.net/udd/+bug/508251 > > However, I really don't know a way to run the package importing > manually. I can write unit tests, but without running a real import, I > can't be sure that my assumptions are valid. > > So how does one go about setting up a local package importer. Or can we > set something up somewhere like tungsten/chinstrap/devpad/etc so all of > us have a sandbox that we can go play in.
See the attached message from this list back in december. There is more to the thread :) -Rob
--- Begin Message ---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 -- ubuntu-distributed-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
--- End Message ---
signature.asc
Description: This is a digitally signed message part
-- ubuntu-distributed-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-distributed-devel
