Groups > linux.debian.maint.python > #17178

Re: Debianized upstream source branch name

Path	csiph.com!weretis.net!feeder8.news.weretis.net!news.nntp4.net!news.hispagatos.org!srl.newsdeef.eu!news.corradoroberto.it!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 21:20:02 +0100
Message-ID	<LSAlc-dXLE-7@gated-at.bofh.it> (permalink)
References	<LSx3X-dVrw-7@gated-at.bofh.it> <LSxGF-dVXp-5@gated-at.bofh.it> <LSxQl-dW0O-11@gated-at.bofh.it> <LSAlc-dXLE-9@gated-at.bofh.it>
X-Original-To	debian-python@lists.debian.org
X-Mailbox-Line	From debian-python-request@lists.debian.org Tue Nov 18 20:12:19 2025
Old-Return-Path	<wrar@debian.org>
X-Amavis-Spam-Status	No, score=-11.998 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-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="DXmQysWC9TwJJj0J"
Content-Disposition	inline
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/23394
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/aRzTDDaE8gU4zEHr@belkar.wrar.name
Approved	robomod@news.nic.it
Lines	47
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Wed, 19 Nov 2025 01:11:56 +0500
X-Original-Message-ID	<aRzTDDaE8gU4zEHr@belkar.wrar.name>
X-Original-References	<aRyirJXSPS6OfnsG@belkar.wrar.name> <6FB70745-F4A8-4AD4-BE26-77D9D9E8EE8A@aeliton.com> <aRyt22dGD5Vfv3sF@belkar.wrar.name> <d7a0f2c2b087fd4c15456d86513548247c45fe1f.camel@aeliton.com>
Xref	csiph.com linux.debian.maint.python:17178

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Tue, Nov 18, 2025 at 05:02:10PM -0300, Aeliton G. Silva wrote:
>> > Apologies for not being clear. The question is how to identify
>> > which branch should be considered the debianized upstream branch
>> > for a given project.
>>
>> Is this the whole task or are you solving some real-world problem?
>
>I'm interested in learning the process of updating packages, initially,
>python-lsp-server.

Then you never need to use any sophisticated logic as any given repo 
either has only one packaging branch or it's obvious which one of the several 
present packaging branches is the uptodate one, or it's not possible to 
determine automatically.

-- 
WBR, wRAR

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar

Thread

Re: Debianized upstream source branch name Andrey Rakhmatullin <wrar@debian.org> - 2025-11-18 17:50 +0100
  Re: Debianized upstream source branch name Aeliton Silva <aeliton@aeliton.com> - 2025-11-18 18:30 +0100
    Re: Debianized upstream source branch name Andrey Rakhmatullin <wrar@debian.org> - 2025-11-18 18:40 +0100
      Re: Debianized upstream source branch name Andrey Rakhmatullin <wrar@debian.org> - 2025-11-18 21:20 +0100

csiph-web