[Git][debian-gis-team/mipp][master] 2 commits: Relax tests on metadata

Bas Couwenberg sebastic at xs4all.nl
Tue Jul 17 07:36:46 BST 2018


On 2018-07-17 08:17, Antonio Valentino wrote:
> Il 16/07/2018 09:48, Bas Couwenberg ha scritto:
>> On 2018-07-16 09:19, Antonio Valentino wrote:
>>> Commits:
>>> 787220f5 by Antonio Valentino at 2018-07-16T07:17:00+00:00
>>> Relax tests on metadata
>> 
>> Note that there are still syntax issues, although non-fatal:
>> 
>>  WARNING: autodoc: failed to import module 'mipp.xsar.mda'; the
>> following exception was raised:
>>  Traceback (most recent call last):
>>    File 
>> "/usr/lib/python3/dist-packages/sphinx/ext/autodoc/importer.py",
>> line 152, in import_module
>>      __import__(modname)
>>    File "/build/mipp-1.1.0/mipp/xsar/__init__.py", line 2, in <module>
>>      from mipp.xsar import sat
>>    File "/build/mipp-1.1.0/mipp/xsar/sat.py", line 121
>>      raise IOError, "No such directory: %s" % opt['dir']
>>                  ^
>>  SyntaxError: invalid syntax
>> 
>> A bunch of these are logged.
>> 
>> I've sponsored the upload, but you may want to fix these in -2.
> 
> Thanks Bas, I didn't noticed it.
> 
> The problem is that recently sphinx-build switched to python3 by
> default, while mipp is python2 only.
> It seems that upstream authors are not interested to port mipp to
> python3 (see [1]). They recommend to switch to satpy [2] that provides
> many (but not all) features of mipp and python-mpop.
> 
> I started working on a satpy packaging (I should add open an ITP
> actually), but for the specific problem of mipp I would go with one of
> the following two options:
> 
> 1. simply stop building and distributing sphinx documentation for mipp
>    (please note that mipp doc don't seems to be particularly relevant)
> 2. build-depend on python-sphinx only (non python3-sphinx) to force the
>    use of the python2 version of the sphinx-build script.
>    This option should raise a lintian warning that we could override.
> 
> Do you have any other option to suggest?

Yes, build depend on both, but use the Python 2 version explicitly, see:

  
https://salsa.debian.org/debian-gis-team/fiona/blob/master/debian/rules#L14

python-sphinx will go away at some point, that's why the lintian tag 
exist, but in the mean time we can use this.

satpy will be a good alternative when Python 2 will no longer be 
available in Debian (after Python 2 is removed some time after 2020).

Kind Regards,

Bas



More information about the Pkg-grass-devel mailing list