Re: Maintaining a package across several debian codenames

[Robin Gustafsson <robin@rgson.se>]

On Mon, Apr 10, 2023 at 11:30 AM Robin ALEXANDER
<robin.alexander@netplus.ch> wrote:
>
> Hi,
>
> Let's assume I wish to maintain package_A across unstable and bullseye-
> backports. I understand from
> https://dep-team.pages.debian.net/deps/dep14/ that:
>
> 1. I need to create 3 branches in my git repository:
> - upstream/latest
> - debian/latest
> - debian/bullseye-backports
>
> 2. Since I am using git-buildpackage, I presume I would generate 3 tags
> when creating a new package version (ex: v3.0.0)
> - upstream/3.0.0 (when running gbp import-orig)
> - debian/3.0.0-1 (when running gbp buildpackage inside branch
> debian/latest)
> - ??? (when running gbp buildpackage inside branch debian/bullseye-
> backports)
>
> If the above is correct, what should be the name of the last tag (the
> one issued by gbp buildpackage inside branch debian/bullseye-backports
> ?
>
> Thank you for your help.
>
> Robin Alexander

The debian version tag "debian/3.0.0-1" matches the package's version number.

You can find the conventions for backport version numbers documented
in section 5.6.12.2 of the policy. [1]

If your backport version is "3.0.0-1~bpo11+1" then the tag should be
"debian/3.0.0-1_bpo11+1" (as ~ is disallowed in git tags).

As mentioned, `gbp tag` will do it for you though.

[1] https://www.debian.org/doc/debian-policy/ch-controlfields.html#special-version-conventions