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 Newsgroups: linux.debian.maint.python Subject: Re: Debianized upstream source branch name Date: Tue, 18 Nov 2025 21:20:02 +0100 Message-ID: References: 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: 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: archive/latest/23394 List-ID: List-URL: 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: X-Original-References: <6FB70745-F4A8-4AD4-BE26-77D9D9E8EE8A@aeliton.com> Xref: csiph.com linux.debian.maint.python:17178 --DXmQysWC9TwJJj0J Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=20 either has only one packaging branch or it's obvious which one of the sever= al=20 present packaging branches is the uptodate one, or it's not possible to=20 determine automatically. --=20 WBR, wRAR --DXmQysWC9TwJJj0J Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmkc0wwtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh VG4QAJmjFwwsU+ymhQqKxO4zoHSa661jE2Ds8sLE+evqg3i6Rb+c52/6vSbJ317X rVTWLCSxnXi5BqBTC+N9w6g9k+v7dVYJtXbFBPE7UR9oPg4kaexZ+omYz+uX40XS p3QjChbe5mwtnEeWpbxn61XIIhYOk44IV/pfuDV1Zk1okhAesjWhvr+XiWCyoxbG OKnAE83wASzUtT4c0KZ78esHD5bdA/eFxXDW1noB6SuUYJ/aHgPz0FwiZZ6JNYuk 5dF9Lt+wLD33PG8SmaHJBsjjbSK4GCzwuZfJYTQKVYvokQsrQxQDZuHX/LJO+5xH keyQRtfzvGXLS8F04N9S79j/9P089N7Eg0PR+BbsnPsJgLAS6G6bLdaqwNo83BUV 0AKX8fbZOhc4O2b4wi1PpcsN//wG9pcjIdxL9wrI87sYY+B6kfTKAPxQdf1n5KIG V4iNMQfCdOh3CdAg7/fbknMhJas20jYVrvdKKCfoMa6Qp7Xtzldw1wUsh50TojK1 wF7X+uuAexAY/KLwe71muLu7mTocAeSt3suUDZmNDoweMMFnmTlhMi7+uylDHJW0 rYGmU1hFO5kVXsOCZ3UxPRr2wt5egBrcsLZGYbGsvTqtISwwhQ+HR3WI+hH7nCZK NJ9EQKTJUgKoK9gkO34GYwcDvz6WFXCM0ya2GZ0D4igt7MQy =JHWc -----END PGP SIGNATURE----- --DXmQysWC9TwJJj0J--