Re: Debianized upstream source branch name

On 11/18/25 2:20 AM, Aeliton G. Silva wrote:
> Hi DPT,
> 
> I've found a small inconsistency in between [1] (section Branch names)
> and [2] (section Git Branch Names).
> 
> The wiki says:
> 
> * "debian/main (formerly debian/master) - The Debianized upstream
> source directory..."
> 
> and the policy.rst says:
> * "debian/master - The Debianized upstream source directory...".
> 
> Which one is correct?
> 
> I was having a look at the python-lsp-server repository and the branch
> debian/main does not exist whilst debian/master does.
> 
> 
> Cheers,
> Aeliton

I'm sorry to say it strait like this, but none of the answers of this 
thread are right.

The *only* source of truth *must* be the VCS URLs as per debian/control. 
So you should, in theory, only look at the Vcs-Git: of a give package, 
and a "debcheckout" call should be pulling the correct package (if your 
source.list contains unstable).

If this isn't the case, you're free to file a bug. The maintainer can 
correct it by either:
- changing the default branch in Salsa

This can be done with a simple curl:

curl ${CURL_OPT} -H "Content-Type: application/json" \
	--header "PRIVATE-TOKEN: ${SALSA_TOKEN}" \
	-X PUT \
	--data '{ "default_branch": "debian/'${NEW_RELEASE}'" }' \
	https://salsa.debian.org/api/v4/projects/${PROJECT_ID}

or with your preferred command line wrapper.

- adding the branch name in the VCS URL

Yes, this is less known, but this can be part of the Vcs-Git field.

As stated above: if it's not the case, feel free to file a bug.

Cheers,

Thomas Goirand (zigo)