Wondering how to fix up a category of import failure

[Max Bowsher]

I've come across an "interesting" importer malfunction in some old branches.

Essentially, it appears that:

1. the importer has imported a version

2. this version has then been copied into future series branches by the
process of initializing new distroseries

3. the importer has then re-imported the same version IN A LATER SERIES
ONLY, but with a different dpkg-source -x version or settings with the
effect of adding files such as .gitignore to the imported tree, BUT has
updated its internal meta.db but NOT moved the tag for the version

4. now it complains that its meta.db and the tag are out of sync.


Options:

A) Move the tag to match what the importer expects. Accept that the same
package version tag exists (for example) in the maverick branch pointing
to r8, but in the natty branch pointing to r9, which have slightly
different trees.

B) Push the extra revision back into the earlier branches and move the
tag there too. (Even though the extra revision has a branch nick with a
later series name than the earlier branches)

C) Nuke the entire import, and let the importer do better this time.

D) Something else?


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/20110623/21d5131d/attachment.pgp>