Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #17178
| From | Andrey Rakhmatullin <wrar@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Debianized upstream source branch name |
| Date | 2025-11-18 21:20 +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> |
| Organization | linux.* mail to news gateway |
[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
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