Wondering how to fix up a category of import failure
John Arbash Meinel
john at arbash-meinel.com
Thu Jun 23 08:48:05 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
> 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?
I personally like C when reasonable. However reasonable means that
nobody else has started working on the project (since creating new
revisions will break their existing changes). Otherwise, I would go for
B. branch-nick doesn't mean all that much.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the ubuntu-distributed-devel