We discussed IRL the handling of backport and -v versions.
There are *two* things we are trying to do with the previous version
informatiion:
* Calculate the -v option to pass to dpkg-parsechangelog.
(With a normal upload this is the version currently present in the
target suite.)
* Perform the overwrkte check: we normally insist (with
--trust-changelog eg in t2u) that the version currently present
in the target suite, is mentioned in *this* upload's changelog.
Backports may be based on the previous backport (merge workflow) or
may be re-created afresh from the parent suite (restart workflow).
We think this can be supported with the following behavioural change
in dgit:
* Backports suites are special (and known via the configuration).
* When uploading to backports, check our changelog (of the thing
we're uploading) for *either*
- the current version in the parent suite
- the current version in the backport suite
* Whichever of these exists and is most recent in our changelog,
should be used for dpkg-parsechangelog -v. It should appear
because otherwise we'll be failing the --trust-changelog check.
* With --overwrite=SPECIFIC-VERSION, it is ok to specify either of
those versions as SPECIFIC-VERSION. We might the user (who isn't
using t2u) to specify -v.
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
