[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: Bug#958047: RFS: mercantile/1.0-1 [ITP] -- python3-mercantile - Web mercator XYZ tile utilities



On 4/21/20 9:16 PM, Sebastiaan Couwenberg wrote:
> On 4/21/20 9:04 PM, Joachim Langenbach wrote:
>> Hi Bas,
>>
>> I created a salsa repository at https://salsa.debian.org/jlaba/mercantile[1] with github 
>> upstream source in upstream, the debian folder in master and a tag for the 1.1.3-2 
>> release, where I adapted the package to the Debian Gis Policy.
> 
> There is not pristine-tar branch, why not?
> 
> Relevant team policy section:
> 
>  https://debian-gis-team.pages.debian.net/policy/repositories.html#git-repository
> 
>> The 1.1.3-2 release could be 
>> also found on debian mentors at https://mentors.debian.net/package/mercantile. [2]
>>
>> It would be nice, if you have a look at it, if everything is fine.
>>
>> But what did you mean with "maintained properly within the team"? Should the repository 
>> be owned by the debian gis team?
> 
> Have a look at the Vcs-* fields in d/control, that's where the repo
> should be, but it currently is not, it's at [1].
> 
> Packages that are properly maintained within the GIS have their repo
> under the debian-gis-team namespace, to get commit access there you need
> to join the team on Salsa, as documented in the team policy:
> 
>  https://debian-gis-team.pages.debian.net/policy/index.html#membership
You've been added to the team, welcome!

Because there were issues pushing to an empty repo before, your repo has
been imported at:

 https://salsa.debian.org/debian-gis-team/mercantile

And configured with salsa-configure-repositories.pl:

 $ ../scripts/salsa-configure-repositories.pl -vp mercantile
 Getting projects for namespace: 2052 (page: 1)
 Getting projects for namespace: 2052 (page: 2)
 Getting projects for namespace: 2052 (page: 3)

 Project: mercantile (46625)
 Issues already disabled.
 Setting merge method for: mercantile (46625)
 Set merge method for project: mercantile (46625)
 Disabling merge request link when pushing from the command line for:
mercantile (46625)
 Disabled merge request link when pushing from the command line for
project: mercantile (46625)
 Setting CI config path 'debian/.gitlab-ci.yml' for: mercantile (46625)
 Set CI config path for project: mercantile (46625)
 Activating Emails on push for: mercantile (46625)
 Activated Emails on push service for project: mercantile (46625)
 Irker service already deactivated for project: mercantile (46625)
 Adding KGB webhook for: mercantile (46625)
 Added KGB webhook for project: mercantile (46625)

> The information on the homepage is relevant too:
> 
>  https://debian-gis-team.pages.debian.net/
> 
> Especially the mailinglists members should subscribe to.
> 
>> Regards,
>>
>> Joachim
>>
>> Am Sonntag, 19. April 2020, 20:46:31 CEST schrieben Sie:
>>> On 4/19/20 8:25 PM, Joachim Langenbach wrote:
>>>> Helllo Bas,
>>>>
>>>> just to make sure, I understand your point correctly:
>>>>
>>>> The debian Gis team might sponsor the package, if I
>>>> 1. register a salsa gis account
>>>> 2. create a git repository at salsa for the package
>>>> 3. follow the gis packaging guideline to create it
>>>>
>>>> Got it correct?
>>>
>>> Mostly. If you want me to sponsor GIS packages, they need to be
>>> maintained properly within the team.
>>>
>>> When a package is properly maintained with the team, it's part of the
>>> GIS blend, which makes SoB also an option for sponsoring when I or other
>>> DDs in the team are not available:
>>>
>>>  https://wiki.debian.org/DebianPureBlends/SoB
>>>
>>> As documented in the policy:
>>>
>>>  https://debian-gis-team.pages.debian.net/policy/packaging.html#sponsorship
>>>
>>>> Am Samstag, 18. April 2020, 13:15:39 CEST schrieb Sebastiaan Couwenberg:
>>>>> On 4/18/20 12:29 PM, Joachim Langenbach wrote:
>>>>>> Team is interested in sponsoring the package?
>>>>>
>>>>> If it's maintained within the team:
>>>>>  https://debian-gis-team.pages.debian.net/policy/
> 
> Kind Regards,
> 
> Bas
> 


-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


Reply to: