Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From: Andrey Rakhmatullin <wrar@debian.org>
Newsgroups: linux.debian.maint.python
Subject: Re: Debianized upstream source branch name
Date: Tue, 18 Nov 2025 17:50:01 +0100
Message-ID: <LSx3X-dVrw-7@gated-at.bofh.it>
References: <LSoWJ-dQ0N-7@gated-at.bofh.it> <LSx3X-dVrw-9@gated-at.bofh.it> <LSx3X-dVrw-11@gated-at.bofh.it>
X-Mailbox-Line: From debian-python-request@lists.debian.org  Tue Nov 18 16:45:50 2025
Old-Return-Path: <wrar@debian.org>
X-Amavis-Spam-Status: No, score=-11.898 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FOURLA=0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate: -3.5
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ILWMUYedspJGiWT1"
Content-Disposition: inline
X-Mailing-List: <debian-python@lists.debian.org> archive/latest/23388
List-ID: <debian-python.lists.debian.org>
List-URL: <https://lists.debian.org/debian-python/>
List-Archive: https://lists.debian.org/msgid-search/aRyirJXSPS6OfnsG@belkar.wrar.name
Approved: robomod@news.nic.it
Lines: 58
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Tue, 18 Nov 2025 21:45:32 +0500
X-Original-Message-ID: <aRyirJXSPS6OfnsG@belkar.wrar.name>
X-Original-References: <978d76a9087f2eecfc59addf45f4cc8be8139966.camel@aeliton.com> <041fe649-355d-4135-8e72-96d41b67b0c3@debian.org> <53665a4c1e6a5ab6335d5ef095f0910665723882.camel@aeliton.com>
Xref: csiph.com linux.debian.maint.python:17173


--ILWMUYedspJGiWT1
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 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:
>
>"NOTE: If the Git repository listed in debian/control's Vcs-Git field
>does not indicate an explicit branch (with the -b <branch> 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)..."
>
>So the complete answer to me=20

To what question, again? Your initial email asks about a disrepancy in two=
=20
documents, but it, again, doesn't describe what you actually want to know.

>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 <repo> HEAD', as it should be
>pointing to the branch desired branch (as Peter suggested).
>
>Is this the correct understanding?

Probably, depends on the problem you are solving.

--=20
WBR, wRAR

--ILWMUYedspJGiWT1
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmkcoqwtFIAAAAAAFQAP
cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh
b8YP/Au0w76H/ulYMa92iMnThyLAhMz8h90ICOJMpZ8nRHGm5zHHJsUJ1+iEu6E5
jc7G0pEB9jRqJveZbaf5nBfu19KCN2ygR9wM9vGyHxLXLfJZo3WxFGBbEVRvUeqd
c6im58LaWYAsB3Ia3Xu8faHufe+z95WyR2Zkt9WBFzzn5Zj6AwGQJH4LMFT4vhN8
aMLtp2p9Duq9NWTjM9ViBPvxknbUkC2n0dzfQ8qZkQ8jmScwA9cYgUBYHntzdhWZ
Cr/K8sIvXEpnNnmEUv0E3Avwvsd5J2o+0BAw1Ny8GIAX39O1Q/hEtKqztOdu/5O2
5B6nEmBdhGWkKaNn2qxnpeNiYsc/iPQKJlKx5iVnr9EdBYPosXvhu3l/MEXYQe3/
iNobYo0Rs1f1RHNDGbb+Odj1+QaI0GeVK/rhR97Sc63NzHVnqz5M+Fz/be2ahaM9
NVzpCXh5/aL+LkbEov5eBpSzAIP9YlOmn93qw/lV/TYSOF3b194uTABqJ1E8AEWA
yvyQDPd+/52hcPV9z7afc2clmNAvgtapqNM8N10NmW5U69Xk9eFUWRP5LCTHh9Q0
mLzorI08FcAT/PBZvW7AbEn6SDgvIw05ZCHeSb7N5vm1BY9hUdTBOzYhN7/CVrIV
aHN1wmj2dT3tFdjJKzFyTzI43yB4aS49vfuaCOF5SrEwRYhQ
=Fkdg
-----END PGP SIGNATURE-----

--ILWMUYedspJGiWT1--