Re: Bug#936613: ginac: Python2 removal in sid/bullseye

2019-09-10 Thread Matthias Klose
On 10.09.19 20:31, Richard B. Kreckel wrote: On 10.09.19 11:29, Matthias Klose wrote: Please read the instructions, they mention to check dependencies, build dependencies, and test dependencies ... I have read https://wiki.debian.org/Python/2Removal and the linked pages. Are there any other

Re: Streamlining the use of Salsa CI on team packages

2019-09-10 Thread Hans-Christoph Steiner
Gregor Riepl: > >> I am not a fan of pointing to a moving target with the "include" statement: >> >> include: >> - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml >> - >> https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml >> >> "master"

RFS: fortran-language-server 1.10.2-1

2019-09-10 Thread Denis Danilov
Hi team, I've created fortran-language-server in PAPT https://salsa.debian.org/python-team/applications/fortran-language-server to address ITP Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936075 Could spend some time to review and upload the package? Thanks, Denis

Re: pybuild mysteriously does not copy all testfiles

2019-09-10 Thread Ole Streicher
Hi IOhannes, I have basically the same problem, funnily with almost the same subject: https://lists.debian.org/debian-python/2019/09/msg00040.html The difference is, that the "external" subdirectory is not copied. So, it seems to be a bug in dh-python. Cheers Ole "IOhannes m zmölnig

pybuild mysteriously does not copy all testfiles

2019-09-10 Thread Debian/GNU
updating one of my packages (python-can), the test-suite started to fail, with an error-code 5, indicating that "no tests have been run". since there *are* tests to be run, i investigated and - after scratching my head - found that 'pybuild' did not fully copy the test-directory from the

Re: 2to3 adds '.' in front dir of "from dir import ..." statements (Was: [MoM] lefse migration to python 3])

2019-09-10 Thread Ghislain Vaillant
It results from the ambiguity between absolute and relative imports in Python 2. Here 2to3 considers your imports being relative, hence the added dot. I believe no dots would be added should a `from __future__ import absolute_import` be found in the preamble of the module. Hope this helps. Ghis