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

[Michael Tokarev]

03.04.2022 15:32, Mathieu Parent wrote:
> 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).

Well, that's what I know about the security team, I was especially
asking about samba team preferences :)

[...]
> 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.

Okay.  I just don't see why it is being useful, besides extra
complexity and confusion in the repository. You'll have to syncronise/
merge the two branches all the time (the history in d/changelog should
be linear too).

> Also Salvatore Bonaccorso, from the security team has done uploads in
> the past (because I was too busy).

Please note: debian/2%4.13.13+dfsg-1_deb11u2 import reverts all
locally applied patches (from d/patches) in git. I don't know if
this is the right thing or not.  Maybe you just forgot to
add `git am $(sed .. d/patches/series) step before comiting?
If yes, maybe you can perform this step and re-tag the result?
Or maybe it is really better to keep them unapplied, since this
makes managing the package more difficult - more, I for one don't
really understand how it is supposed to work to start with.

Thank you!

/mjt