Re: Moving default branch after project creation

2024-08-13 Thread Alexandru Mihail
Hi, Apologies Carsten, I was not yet subscribed to debian-python and literally missed your big mail when I was not CC'ed. > $ gbp import-orig --verbose --sign-tags ~/Downloads/psrecord- 1.4.tar.gz This is exactly what I ended up doing now, with a gbp.conf, the right way. > For now I suggest to d

Re: Moving default branch after project creation

2024-08-13 Thread Thomas Goirand
On 8/8/24 13:05, Carsten Schoenert wrote: Hi Martin, Am 08.08.24 um 09:49 schrieb Martin: On 2024-08-08 08:42, Carsten Schoenert wrote: $ gbp import-orig --verbose --sign-tags --pristine-tar --upstream-branch=upstream --debian-branch=debian/master ~/Downloads/psrecord-1.4.tar.gz I suggest to

Re: Moving default branch after project creation

2024-08-12 Thread Alexandru Mihail
> The structure of the tree is simply wrong, given you are at the beginning I > suggest to drop the current tree and restart from scratch within your > namespace. > For me it makes no sense to work further on that base. It make things > unnecessary harder. > > Once it's working on your side i

Re: Moving default branch after project creation

2024-08-11 Thread Carsten Schoenert
Am 10.08.24 um 00:01 schrieb Alexandru Mihail: Thanks everyone for chiming in ! Debates around the branch name aside, I still can't find out how to access the Gitlab settings button to change the default to anything. It's a permissions thing I think. When I access a project under my personal name

Re: Moving default branch after project creation

2024-08-08 Thread Carsten Schoenert
Hi Martin, Am 08.08.24 um 09:49 schrieb Martin: On 2024-08-08 08:42, Carsten Schoenert wrote: $ gbp import-orig --verbose --sign-tags --pristine-tar --upstream-branch=upstream --debian-branch=debian/master ~/Downloads/psrecord-1.4.tar.gz I suggest to use `upstream/latest` as upstream branch.

Re: Moving default branch after project creation

2024-08-08 Thread Martin
On 2024-08-08 08:42, Carsten Schoenert wrote: > $ gbp import-orig --verbose --sign-tags --pristine-tar > --upstream-branch=upstream --debian-branch=debian/master > ~/Downloads/psrecord-1.4.tar.gz I suggest to use `upstream/latest` as upstream branch. It spares you separating upstream/latest, upstr

Re: Moving default branch after project creation

2024-08-07 Thread Carsten Schoenert
Am 08.08.24 um 07:54 schrieb Julian Gilbey: The OP specifically said they got it from DEP-14. Thanks also to Nicholas for reminding me of the DEP-14 history! I don't see what makes the difference in the end? There is a DPT policy that enforces to usage of the branch name debian/master for wo

Re: Moving default branch after project creation

2024-08-07 Thread Julian Gilbey
On Thu, Aug 08, 2024 at 05:50:38AM +0200, Carsten Schoenert wrote: > Am 07.08.24 um 22:33 schrieb Julian Gilbey: > > > The candidate DEP-14 (https://dep-team.pages.debian.net/deps/dep14/) > > currently reads: > > > >In Debian this means that uploads to unstable and experimental > >should

Re: Moving default branch after project creation

2024-08-07 Thread Carsten Schoenert
Am 07.08.24 um 22:33 schrieb Julian Gilbey: The candidate DEP-14 (https://dep-team.pages.debian.net/deps/dep14/) currently reads: In Debian this means that uploads to unstable and experimental should be prepared either in the debian/latest branch or respectively in the debian/unstable

Re: Moving default branch after project creation

2024-08-07 Thread Nicholas D Steeves
Julian Gilbey writes: > On Wed, Aug 07, 2024 at 08:27:33PM +0300, Alexandru Mihail wrote: >> Hi, I've recently created >> https://salsa.debian.org/python-team/packages/psrecord following >> previous ITP. The main branch was set to main and I'd like to move it >> to DEP compliant debian/master and

Re: Moving default branch after project creation

2024-08-07 Thread Julian Gilbey
On Wed, Aug 07, 2024 at 08:27:33PM +0300, Alexandru Mihail wrote: > Hi, I've recently created > https://salsa.debian.org/python-team/packages/psrecord following > previous ITP. The main branch was set to main and I'd like to move it > to DEP compliant debian/master and delete the main branch.  The