Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #17173 > unrolled thread

Re: Debianized upstream source branch name

Back to article view | Back to linux.debian.maint.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

#17173 — Re: Debianized upstream source branch name

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

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 

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.

>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.

-- 
WBR, wRAR

[toc] | [next] | [standalone]

#17174

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

Aeliton G. Silva

> On 18 Nov 2025, at 13:46, Andrey Rakhmatullin <wrar@debian.org> wrote:
> 
> 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
> 
> 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.
> 

Apologies for not being clear. The question is how to identify which branch 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 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.
> 
> --
> WBR, wRAR
> <signature.asc>

[toc] | [prev] | [next] | [standalone]

#17175

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

On Tue, Nov 18, 2025 at 02:23:12PM -0300, Aeliton 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?

-- 
WBR, wRAR

[toc] | [prev] | [next] | [standalone]

#17178

[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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web