Importer requires changelog parent ancestory on upload tags
Bug #1774985 reported by
Robie Basak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| git-ubuntu |
Triaged
|
Undecided
|
Unassigned | ||
Bug Description
Following discussion, we think this needs reconsideration in the spec. We may decide to relax the changelog parent ancestory requirement for adoption of upload tags. In this case, we agree that the lint tool should pick it up (which it should do regardless of the importer algorithm), which is bug 1774735.
Revision history for this message
| Robie Basak (racb) wrote | #1 |
To post a comment you must log in.
Edge cases:
1) After a "reimport" that mutated commit hashes, we probably don't want to accidentally "pull in" the old tree because an uploader is based on a commit from the previous set of imports.
2) Generalized case of 1: it's usually a mistake for an uploader not to base a set of commits on what existed and was published by git-ubuntu previously. And if this is done, then "git log" won't make any sense.
3) The first time a package is imported, there won't be any previous imports so will fail the current test. In this exceptional case ("there are no import tags"), perhaps we should accept the rich history.