RFC: Minor collisions handling, both manual and automatic

[Max Bowsher]

I just dealt with a requeue/zap-revids for bootchart to get that import
going again.

The importer created various extra and fairly pointless revisions in the
lucid and maverick branches... all to remove a vim backup file which was
included in the human-committed branch but not in the archive.

I think we should do two things to deal with minor collisions like this:

1) Automation
=============

In the collision detection code, we should have heuristics for pathnames
which are safe to disregard and still treat a collision as clean. I'm
thinking of:

.*.swp (vim backup)

.pc
.pc/.version
.pc/.quilt_series
.pc/.quilt_patches

(The creation or removal of an initialized quilt control directory
containing no actual content is pretty harmless)

I'm sure there are more.


2) Manual override
==================

We should have a new tool that can be used to forcible add/update rows
in the importer's meta.db revids table, by package, suite and
revision-id, so that jubany operators can placate the importer about
one-off oddities determined to be harmless on human inspection.


Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-distributed-devel/attachments/20110713/a3dcb32f/attachment.pgp>