Re: Debianized upstream source branch name

Andrey Rakhmatullin <[email protected]> Tue, 18 Nov 2025 16:20:01 +0500

Newsgroups	gmane.linux.debian.devel.python
Message-ID	<[email protected]>

On Tue, Nov 18, 2025 at 11:13:42AM +0000, Nick Morrott wrote:
>> >If in doubt, always check to see if debian/gbp.conf exists and what
>> >debian-branch is set to.
>>
>> And in which branch would you look for this file?
>
>I generally check the default gbp clone branch first! 

In most cases this already answers the question.
It doesn't only when the maintainer forgot (or most likely didn't know 
how/didn't know they need it) to change it on salsa when changing the 
debian-branch from one to another.

>For each of those 3 repos, I seemingly end up on the default branch
>(which is different for each repo), which seems to be what the OP
>wants. 

> That's the branch I would look in for a d/gbp.conf file.

As I said, this step is unnecessary because you alreadu have the answer. 
Also, it will always contain the name of current branch or none (or be 
incorrect).

>Additionally, the OP could also:
>
>i) inspect the repo on the salsa web interface and see which branch is
>marked as default
>ii) download the debian source package and inspect the gbp.conf file if present
>iii) check Peter's remote interrogation solution

True.
Though it depends on the problem being solved.

-- 
WBR, wRAR

signature.asc (application/pgp-signature, 894 B)