Re: Debianized upstream source branch name
On Tue, 18 Nov 2025 at 08:39, Andrey Rakhmatullin <wrar@debian.org> wrote:
>
> On Tue, Nov 18, 2025 at 08:30:55AM +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! (apologies for
the useless comment above...)
My experience with using "gbp clone" just now was as follows:
----
$ gbp clone https://salsa.debian.org/python-team/packages/test-stages.git
gbp:info: Cloning from
'https://salsa.debian.org/python-team/packages/test-stages.git'
nick on krusty in ~/d/s/g/debian-packaging
$ cd test-stages
nick on krusty in ~/d/s/g/d/test-stages (debian/unstable )
----
$ gbp clone https://salsa.debian.org/python-team/packages/python-lsp-server.git
gbp:info: Cloning from
'https://salsa.debian.org/python-team/packages/python-lsp-server.git'
nick on krusty in ~/d/s/g/debian-packaging
$ cd python-lsp-server
nick on krusty in ~/d/s/g/d/python-lsp-server (debian/master )
----
$ gbp clone https://salsa.debian.org/python-team/packages/babelfish.git
gbp:info: Cloning from
'https://salsa.debian.org/python-team/packages/babelfish.git'
nick on krusty in ~/d/s/g/debian-packaging
$ cd babelfish
nick on krusty in ~/d/s/g/d/babelfish (master )
----
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.
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
Cheers,
Nick
Reply to: