[Pkg-samba-maint] updating packages on stable?

[Mathieu Parent]

On Sun, Apr 3, 2022 at 11:38 AM Michael Tokarev <mjt at tls.msk.ru> wrote:
>
> Hi!
>
> What's the usual procedure of updating samba packages in stable?
> Do we import new upstream samba-4.13.17 and upload with the new
> source as 2:4.13.17+dfsg-1~deb11u1?

This needs to be discussed with the stable release team (and security
team when relevant).
They usually accept uploading the latest from the same branch (4.13.x).

> (why it is ~deb11 and not +deb11 anyway?)

To avoid having stable >= testing/sid. At that time, bullseye and
testing had the same version.

> Or do we add individual patches and release 2:4.13.13+dfsg-1~deb11u4 ?

Go for the former, if accepted by the release team.

> If that's the former, is it usually okay for the
> release team?

There is no automatic approval from the release team, this may be
discussed however.

> Besides, in git I see branches for debian releases
> (eg buster) and for their security counterparts
> (eg buster-security) - how these are managed, what's
> the difference?

Security releases go thru release-security. We have done point-release
updates too in the past (with a different timeline),in the release
branch, merging the release-security branch. The branches usually
correspond to the release in the changelog.
Also Salvatore Bonaccorso, from the security team has done uploads in
the past (because I was too busy).

> I usually have single branch for each debian release
> (eg buster) and keep both -security and -stable in
> there, releasing either to -stable or to -security,
> there's no forks for -security and -stable, at least
> usually - I can't imagine how one can create a fork
> here.

Yes. This is easier. You can go with this. Also this conforms to [dep14].

[dep14] https://dep-team.pages.debian.net/deps/dep14/

Thanks

-- 
Mathieu