Path: csiph.com!newsfeed.xs4all.nl!newsfeed7.news.xs4all.nl!bofh.it!news.nic.it!robomod
From: Dave Jones <dave@waveform.org.uk>
Newsgroups: linux.debian.bugs.dist,linux.debian.maint.python
Subject: Bug#924643: RFS: colorzero/2.0-1 [ITP] -- Construct, convert, and manipulate colors in a Pythonic manner.
Date: Mon, 21 Jun 2021 21:20:01 +0200
Message-ID: <CsxCF-8qr-1@gated-at.bofh.it>
References: <CrHXr-1pL-7@gated-at.bofh.it> <CrR0J-88D-3@gated-at.bofh.it> <CssMF-5AH-1@gated-at.bofh.it> <xBTcd-5Zy-5@gated-at.bofh.it> <Csv7P-6Qx-5@gated-at.bofh.it> <xBTcd-5Zy-5@gated-at.bofh.it> <Csv7P-6Qx-5@gated-at.bofh.it>
X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org  Mon Jun 21 19:18:08 2021
Old-Return-Path: <debbugs@buxtehude.debian.org>
X-Spam-Flag: NO
X-Spam-Score: -3.751
Reply-To: Dave Jones <dave@waveform.org.uk>, 924643@bugs.debian.org
Resent-To: debian-bugs-dist@lists.debian.org
Resent-Cc: wnpp@debian.org
X-Debian-Pr-Message: followup 924643
X-Debian-Pr-Package: wnpp
X-Gm-Message-State: AOAM531az9sCflKZCcKmNgRsGME4fYgiqW7hC/6np0fs14QGMWz7Xaof pJv1v4p9vRnotQhGw6upu8bAoQ==
X-Google-SMTP-Source: ABdhPJzHN7Orx1sXGjs5C1xl0MAO0gfqVHy1P/nGNckAVemeehv89K3g/JivTbVhzjsCL/vx+8FAWw==
X-Received: by 2002:a05:600c:22cf:: with SMTP id 15mr29657599wmg.144.1624302903848; Mon, 21 Jun 2021 12:15:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
User-Agent: NeoMutt/20191207
X-Debian-Message: from BTS
X-Mailing-List: <debian-bugs-dist@lists.debian.org> archive/latest/1668483
List-ID: <debian-bugs-dist.lists.debian.org>
List-URL: <https://lists.debian.org/debian-bugs-dist/>
Approved: robomod@news.nic.it
Lines: 46
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Cc: Peter Green <plugwash@debian.org>, Debian Python <debian-python@lists.debian.org>
X-Original-Date: Mon, 21 Jun 2021 20:15:02 +0100
X-Original-Message-ID: <20210621191502.f4gd53ikn2ptkhcd@amaterasu>
X-Original-References: <d8b8995b-aaec-9a0f-08c8-e47088caba6a@debian.org> <8ebdb0c9-773f-f96c-7aef-360dd4bfe2a6@yaerobi.com> <20210621140626.b6wafvt3wdmr7mdf@amaterasu> <155264876356.22584.10802410818036635153.reportbug@spider> <d3c74662-01dd-5673-5391-2ad27b7b8143@yaerobi.com> <155264876356.22584.10802410818036635153.reportbug@spider> <d3c74662-01dd-5673-5391-2ad27b7b8143@yaerobi.com>
Xref: csiph.com linux.debian.bugs.dist:1062686 linux.debian.maint.python:13432

Hi Emmanuel,

On Mon, Jun 21, 2021 at 01:33:11PM -0300, Emmanuel Arias wrote:
>On 6/21/21 11:06 AM, Dave Jones wrote:
>> On Sat, Jun 19, 2021 at 06:40:58PM -0300, Emmanuel Arias wrote:
>>> Also, you can try to follow DEP-14 (although is mark as candidate)
>>> and add debian/master as default branch.
>>
>> Ah, this was something that confused me a bit when initially working
>> on this. I'd read through DEP-14, but then figured a simple way to
>> start would be to grab my existing packaging for Raspbian and use gbp
>> import-dsc on it. This set up the repo with a "master" branch rather
>> than "debian/master" and I then wondered if I'd mis-interpreted
>> DEP-14's prescription to use "debian/master", and whether it meant one
>> should use "debian" branch or alternatively a "master" branch.
>I think that I don't understand you, sorry :(. But DEP-14 recommend the
>use of <vendor>/* for name the branchs, so for debian the branch should
>be debian/*, for ubuntu ubuntu/*, etc.

Ah, sorry -- I'll attempt to elaborate my (rather silly) leap of 
"logic". Having read [PY-GIT] and [DEP-14], and knowing that gbp was 
specifically made for Debian packaging, after using "gbp import-dsc" I 
was slightly surprised to wind up on a "master" branch rather than 
"debian/master". I generally assume that tooling made specifically for a 
purpose (like Debian packaging) probably knows what it's doing better 
than I do, and hence I wondered whether I had missed something and 
whether (yes, it seems silly in hindsight, but still) the recommendation 
to use "debian/master" was to be interpreted as "debian or master" 
rather than a literal "debian/master" string.

Anyway, that's why I initially pushed a "master" branch rather than 
"debian/master" (under the assumption that gbp's defaults are probably a 
better bet than me trying to second guess the interpretation of 
standards :).

[PY-GIT] https://wiki.debian.org/Python/GitPackaging#Git_Branch_Names
[DEP-14] https://dep-team.pages.debian.net/deps/dep14/

In any case, I've fixed up the branches in the repo now and I *think* 
I've got the CI configuration in the right place, though it doesn't seem 
to have triggered a run yet. I've probably missed something in the repo 
config -- will dig into that in a mo.

Thanks for all the advice!

Dave.