Hi,gbp buildpackage (or gbp tag) will create the correct tag name for you.
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
?
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
In a nutshell, if I understood correctly the debian policyIt's "3.0.0-1~bpo11+1", see https://backports.debian.org/Contribute/
Branch debian/latest
File debian/changelog will show "...(3.0.0-1) unstable ..."
Branch debian/bullseye-backports
File debian/changelog will show "... (3.0.0-1~bpo11u1) bullseye ..."
Should I decide to setup a private repository on top to speed up thingsThe versioning scheme for private repos is up to you, as long as it
, I could add a new branch to my git repository:
Branch debian/bullseye
File debian/changelog would show "... (3.0.0-1~deb11u1) ..."
Le 10 avr. 2023 à 20:44, Andrey Rakhmatullin <wrar@wrar.name> a écrit :
On Mon, Apr 10, 2023 at 08:14:39PM +0200, Robin ALEXANDER wrote:
In a nutshell, if I understood correctly the debian policyIt's "3.0.0-1~bpo11+1", see https://backports.debian.org/Contribute/
Branch debian/latest
File debian/changelog will show "...(3.0.0-1) unstable ..."
Branch debian/bullseye-backports
File debian/changelog will show "... (3.0.0-1~bpo11u1) bullseye ..."
Should I decide to setup a private repository on top to speed up thingsThe versioning scheme for private repos is up to you, as long as it
, I could add a new branch to my git repository:
Branch debian/bullseye
File debian/changelog would show "... (3.0.0-1~deb11u1) ..."
doesn't clash with schemes used by Debian repos.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 547 |
Nodes: | 16 (2 / 14) |
Uptime: | 60:16:13 |
Calls: | 10,398 |
Calls today: | 6 |
Files: | 14,067 |
Messages: | 6,417,474 |
Posted today: | 1 |