Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Aeliton Silva Newsgroups: linux.debian.maint.python Subject: Re: Debianized upstream source branch name Date: Tue, 18 Nov 2025 18:30:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Tue Nov 18 17:23:46 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-1.762 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, MIME_QP_LONG_LINE=0.001, RCVD_IN_SBL_CSS=3.335, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001] autolearn=no autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -3.5 Content-Type: multipart/alternative; boundary=Apple-Mail-4A833614-B272-4FB0-ACD8-6452DD1490B1 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 (1.0) X-Mailer: iPhone Mail (22G100) X-From-Rewrite: unmodified, already matched X-Get-Message-Sender-Via: esja.orangewebsite.com: authenticated_id: aeliton@aeliton.com X-Authenticated-Sender: esja.orangewebsite.com: aeliton@aeliton.com X-Originating-IP: 82.221.129.44 X-Spamexperts-Domain: esja.orangewebsite.com X-Spamexperts-Username: 82.221.129.44 Authentication-Results: ice-networks.com; auth=pass smtp.auth=82.221.129.44@esja.orangewebsite.com X-Spamexperts-Outgoing-Class: ham X-Spamexperts-Outgoing-Evidence: Combined (0.15) X-Recommended-Action: accept X-Filter-ID: 9kzQTOBWQUFZTohSKvQbgI7ZDo5ubYELi59AwcWUnuWsJ5TQDMA0H2TNYeesRdXDc2HyHh9/ak7b V97B6HQZWiu2SmbhJN1U9FKs8X3+Nt0X+OmySRy5m8XU2TBBZd4sh7E6ioikvQnMsfdLux5zw4JL M0i5ZAms0EHrvcCaVIP0edpVxSrbA/BehZwb2OTYGnT3EFAinyrilm9zau/FuzkQt9Nb4Ml7QXdk EetczWBwpXy0XHspphdZQYvd/p0QeB7itP8hgjDRserKv4bhb045GZEcMu7Cmce9RZWUwaz0yvyP 5m3h8sXTblXeTwt0on0MzSTdZlEzzrvB3glmyJk5mH/X3pSH/ENJb2CQDctYptuo6nUi3mq0kk1S CcjSkTlM0XgkvBKSodCLfS9uSUvNep7ohNLeaRujC1xnM6F5KB1kV1jO3BXL+OePRM0w+qSSZH9r PpLCu68SAXfCPqWFX3vB9pl/sZ+GcI6S5lycDSHy1aiHYhGH4uVbmL5XGL7fPKjYhHLan24CGgyQ vG0S731kaX83MCoiLh1IvWA93SsS4aMXJmiJ2G0eb5ahVJ6jkcnrJ9/hg9+g0Vr4KnA6vHexqZqH zGeEiMM430NtV1w91ummwAJgSfp95IB5KumLerNJaitFnP2ausrj+xM74OqDymuB/totiLbH5Lhy EYUeNDqrX3Sju+Zod+VzkQn3LrJ4EhaXa9s1NBItcgfILneBruSXVJFMTtbeU7NoqEt7BnqWgGpX 3717t3U1wBHDXskUQEIFlsr08TzOInZD4NQheMp9Ba84Jdxq5iWXb/diL22Sh7Sj27Ks5PlkHTwY nMvwT8P3rU7heFsyDpLbnUglTfDYDpdjoa8GxiGeRArt8zAuv1CL1PnX7j1uAoWOT269rCq62YYB RYsduvT/u39Lnury1zo6ar+iDA3luPQUNCv2ATEieO1jJZHHA00TI/RL72f8V8nY4xdM+JfVL8XV LsYYMtVIBO5VpqNe6PgGYqUho23uG5w4Hdn+WF3v5neiES6puHDYgaIr0ARE5pef8bx1JcyDJayF HTavhpRXuQXfEGeNxrjfuR2hW0gOlPzxMSICdeCXRZ3aLcGU8V3CtXVQ6mF3jmI5IBh+RPBrHjaC SPJOudTvd6VD0wYx69VUo2KTAtDR+r8U64S4S1nZiLbg3wWLKRRpevJlsencvO2nbIruNjqlj2yG X-Report-Abuse-To: spam@email-filter1.ice-networks.com X-Mailing-List: archive/latest/23389 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/6FB70745-F4A8-4AD4-BE26-77D9D9E8EE8A@aeliton.com Approved: robomod@news.nic.it Lines: 92 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Tue, 18 Nov 2025 14:23:12 -0300 X-Original-Message-ID: <6FB70745-F4A8-4AD4-BE26-77D9D9E8EE8A@aeliton.com> X-Original-References: X-Original-X-Complaints-To: abuse@email-filter1.ice-networks.com Xref: csiph.com linux.debian.maint.python:17174 --Apple-Mail-4A833614-B272-4FB0-ACD8-6452DD1490B1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Aeliton G. Silva > On 18 Nov 2025, at 13:46, Andrey Rakhmatullin wrote: >=20 > =EF=BB=BFOn Tue, Nov 18, 2025 at 01:33:16PM -0300, Aeliton G. Silva wrote:= >> Thanks Thomas, This shed some light on what I read at [1](see NOTE >> under "For development releases"), quoting it here: >>=20 >> "NOTE: If the Git repository listed in debian/control's Vcs-Git field >> does not indicate an explicit branch (with the -b suffix) then >> it should have its HEAD point to the branch where new upstream versions >> are being packaged (that is one of the branches associated to a >> development release)..." >>=20 >> So the complete answer to me >=20 > To what question, again? Your initial email asks about a disrepancy in two= documents, but it, again, doesn't describe what you actually want to know. >=20 Apologies for not being clear. The question is how to identify which branch s= hould be considered the debianized upstream branch for a given project. >> right now would be: >> 1) The branch stated in debian/control Vcs-Git; or >> 2) If branch not stated, >> 2.1. Check the default branch in salsa; or >> 2.2. use 'git ls-remote --symref HEAD', as it should be >> pointing to the branch desired branch (as Peter suggested). >>=20 >> Is this the correct understanding? >=20 > Probably, depends on the problem you are solving. >=20 > -- > WBR, wRAR > --Apple-Mail-4A833614-B272-4FB0-ACD8-6452DD1490B1 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
=
Aeliton G. Silva

On 18 Nov 2025, at 13:46, A= ndrey Rakhmatullin <wrar@debian.org> wrote:

=
=EF=BB=BFOn Tue, Nov 18, 20= 25 at 01:33:16PM -0300, Aeliton G. Silva wrote:
Thanks Thomas, This shed some light on what I read at [1](see N= OTE
under "For develo= pment releases"), quoting it here:

"NOTE: I= f the Git repository listed in debian/control's Vcs-Git field
does not indicate an explicit branc= h (with the -b <branch> suffix) then
it should have its HEAD point to the branch where new u= pstream versions
are b= eing packaged (that is one of the branches associated to a
development release)..."

So the complete answer to me
<= span>
To what question, again? Your initial email asks about= a disrepancy in two documents, but it, again, doesn't describe what you act= ually want to know.


<= /div>Apologies for not being clear. The question is how to identify which br= anch should be considered the debianized upstream branch for a given project= .

right now would be:
1) The branch stated in debian/control Vcs-Git; or
2) If branch not stated,
   2.1. Check the defau= lt branch in salsa; or
   2.2. use 'git ls-remote --symref <repo> HEAD', as it s= hould be
pointing to t= he branch desired branch (as Peter suggested).

= Is this the correct understanding?

Probably, depends on the problem you are solving.

--
WBR, wRAR
<signature= .asc>
= --Apple-Mail-4A833614-B272-4FB0-ACD8-6452DD1490B1--