Re: Maintaining a package across several debian codenames

Hi Andrey,

It’s odd, for the document in https://www.debian.org/doc/debian-policy/ch-controlfields.html#special-version-conventions indicates ~bpoNuX unless I missed something…

Kind regards.

—-

Robin

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 policy

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 ..."
It's "3.0.0-1~bpo11+1", see https://backports.debian.org/Contribute/

Should I decide to setup a private repository on top to speed up things
, I could add a new branch to my git repository:
Branch debian/bullseye
File debian/changelog would show "... (3.0.0-1~deb11u1) ..."
The versioning scheme for private repos is up to you, as long as it
doesn't clash with schemes used by Debian repos.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply to: