Processing of netcdf-parallel_4.6.1-1_amd64.changes
Bas Couwenberg
sebastic at xs4all.nl
Tue Jul 10 09:40:18 BST 2018
On 2018-07-10 10:30, Alastair McKinstry wrote:
> On 10/07/2018 09:18, Bas Couwenberg wrote:
>> Remove pkg-grass-devel at lists.alioth.debian.org from the
>> netcdf-parallel package, the Maintainer and Uploaders of the netcdf
>> source package must not be associated with your fork.
>>
>> Having the Debian GIS team associated with the netcdf-parallel package
>> is especially problematic because there is no public VCS (on Salsa)
>> for your fork. Not having a public VCS is unacceptable for any package
>> in this team.
>
> Ok, I will remove the team from Maintainers / Uploaders.
>
> I am maintaining a public VCS on Salsa , though: the dev-coinstallable
> branch on the netcdf repo.
> I'd rather not maintain a totally separate VCS as I plan to keep the
> fork as close as possible to the main VCS.
A separate source package should have a separate git repository.
You can add the netcdf repository as a second remote to pull changes
from.
My expectation for your fork is that it will live much longer than you
think, hence the need for a clear separation.
I will not be involved in the fork, and do not wish to be even remotely
thought responsible for the netcdf-parallel package.
The changes required upstream are quite invasive, so it will take quite
some time to get them adopted.
Kind Regards,
Bas
More information about the Pkg-grass-devel
mailing list