Bug#1036502: amp: please add autopkgtests (to add coverage for python3-matplotlib)

2023-05-21 Thread Sandro Tosi
Source: amp
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-matplotlib

Dear maintainer,
amp has a package relationship with python3-matplotlib (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1036499: rickslab-gpu-utils: please add autopkgtests (to add coverage for python3-matplotlib)

2023-05-21 Thread Sandro Tosi
Source: rickslab-gpu-utils
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-matplotlib

Dear maintainer,
rickslab-gpu-utils has a package relationship with python3-matplotlib (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1036493: python-pyclustering: please add autopkgtests (to add coverage for python3-matplotlib)

2023-05-21 Thread Sandro Tosi
Source: python-pyclustering
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-matplotlib

Dear maintainer,
python-pyclustering has a package relationship with python3-matplotlib (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1036492: bornagain: please add autopkgtests (to add coverage for python3-matplotlib)

2023-05-21 Thread Sandro Tosi
Source: bornagain
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-matplotlib

Dear maintainer,
bornagain has a package relationship with python3-matplotlib (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1036490: arpys: please add autopkgtests (to add coverage for python3-matplotlib)

2023-05-21 Thread Sandro Tosi
Source: arpys
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-matplotlib

Dear maintainer,
arpys has a package relationship with python3-matplotlib (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1036483: ompl: please add autopkgtests (to add coverage for python3-matplotlib)

2023-05-21 Thread Sandro Tosi
Source: ompl
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-matplotlib

Dear maintainer,
ompl has a package relationship with python3-matplotlib (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035270: taurus: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: taurus
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
taurus has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035267: vitables: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: vitables
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
vitables has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035266: yp-svipc: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: yp-svipc
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
yp-svipc has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035265: guiqwt: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: guiqwt
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
guiqwt has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035264: morse-simulator: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: morse-simulator
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
morse-simulator has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035244: syrthes: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: syrthes
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
syrthes has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035245: sardana: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: sardana
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
sardana has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035234: ros-laser-geometry: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: ros-laser-geometry
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
ros-laser-geometry has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035226: python-escript: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: python-escript
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
python-escript has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035220: python-pyclustering: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: python-pyclustering
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
python-pyclustering has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035217: python-pyqtgraph: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: python-pyqtgraph
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
python-pyqtgraph has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035216: python-pyorick: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: python-pyorick
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
python-pyorick has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035202: pyimagetool: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: pyimagetool
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
pyimagetool has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035197: fasttext: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: fasttext
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
fasttext has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035186: mpi4py-fft: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: mpi4py-fft
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
mpi4py-fft has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035185: mlpack: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: mlpack
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
mlpack has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035174: mathgl: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: mathgl
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
mathgl has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035173: guidata: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: guidata
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
guidata has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035169: amp: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: amp
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
amp has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035168: arpys: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: arpys
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
arpys has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035160: libpysal: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: libpysal
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
libpysal has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035161: libvigraimpex: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: libvigraimpex
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
libvigraimpex has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035148: harp: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: harp
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
harp has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035141: bornagain: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: bornagain
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
bornagain has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035120: apriltag: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: apriltag
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
apriltag has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1035122: denss: please add autopkgtests (to add coverage for python3-numpy)

2023-04-29 Thread Sandro Tosi
Source: denss
Severity: normal
User: debian-pyt...@lists.debian.org
Usertags: missing-adt-python3-numpy

Dear maintainer,
denss has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

  
https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027250: keras: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: keras
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027248: sasview: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: sasview
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027245: symfit: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: symfit
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027241: pysph: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: pysph
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027236: pyemd: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: pyemd
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027231: numcodecs: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: numcodecs
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027230: python-dmsh: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: python-dmsh
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027229: mlpy: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: mlpy
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027226: lmfit-py: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: lmfit-py
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027218: pyswarms: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: pyswarms
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027217: python-pymbar: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: python-pymbar
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027215: theano: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: theano
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027212: python-dtcwt: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: python-dtcwt
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027210: vedo: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: vedo
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027208: scikit-learn: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: scikit-learn
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027206: qiskit-aer: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: qiskit-aer
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027205: tpot: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: tpot
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027203: qiskit-terra: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: qiskit-terra
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027195: fiat: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: fiat
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#1027190: dolfin: autopkgtest fail with numpy/1.24.1

2022-12-28 Thread Sandro Tosi
Source: dolfin
Severity: important
User: debian-pyt...@lists.debian.org
Usertags: numpy1.24

Hello,
recently numpy/1.24.1 has been uploaded to experimental, and this package
autopkgtest fail when running against it.

An overview of the upstream changes in the 1.24.x series is available at:

  https://numpy.org/doc/stable/release/1.24.0-notes.html

Several of the errors are in the form of:

AttributeError: module 'numpy' has no attribute 'X'

with X in [float, int, bool, object, ...]. This is because, numpy upstream in
1.24.0, finally decided to expire

  
https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases

some deprecations introduced in 1.20.0

  
https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated

(released almost 2 years ago).

All of those are quite straightforward to fix, since often it's just necessary
to stop importing them from numpy and use the python native types.

Other changes may requires a bit more rework to be addressed.

Currently numpy/1.24.x is in experimental, but given the possible longer support
that it'll receive from upstream, we're hopeful to include this in bookworm, so
your help is necessary to address this bug ASAP.

Regards,
Sandro

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#994304: libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm

2021-11-11 Thread Sandro Tosi
> (Immediate uploading _not_ recommended: it still needs a workaround for
> #997908.)

any idea when that will be addressed? i would like to remove numpy-dbg
sooner rather than later -- thanks!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Re: pynfft: Removal of the python3-*-dbg packages in sid/bookworm

2021-11-10 Thread Sandro Tosi
control: severity -1 serious

On Wed, 15 Sep 2021 10:37:58 + Matthias Klose  wrote:
> Package: src:pynfft
> Version: 1.3.2-3
> Severity: serious
> Tags: sid bookworm
> User: debian-pyt...@lists.debian.org
> Usertags: pydbg-removal
>
> Python 3.8 upstream now has a common ABI for normal and debug
> extension builds, so we can drop the python3-*-dbg packages.
> Details at
> https://lists.debian.org/debian-python/2021/09/msg4.html
>
> Stop building the python3-*-dbg package, but be careful
> that all the reverse dependencies are also removed.

please remove python3-pynfft-dbg it's now a leaf package and it's
blocking the removal of python3-numpy-dbg

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Re: libgpuarray: Removal of the python3-*-dbg packages in sid/bookworm

2021-11-10 Thread Sandro Tosi
control: severity -1 serious

On Wed, 15 Sep 2021 10:37:26 + Matthias Klose  wrote:
> Package: src:libgpuarray
> Version: 0.7.6-6
> Severity: serious
> Tags: sid bookworm
> User: debian-pyt...@lists.debian.org
> Usertags: pydbg-removal
>
> Python 3.8 upstream now has a common ABI for normal and debug
> extension builds, so we can drop the python3-*-dbg packages.
> Details at
> https://lists.debian.org/debian-python/2021/09/msg4.html
>
> Stop building the python3-*-dbg package, but be careful
> that all the reverse dependencies are also removed.

please do remove python3-pygpu-dbg, it is now a leaf package and it's
blocking the removal of python3-numpy-dbg

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers


Bug#981810: python-fabio: regression in autopkgtest tests

2021-02-03 Thread Sandro Tosi
Source: python-fabio
Version: 0.11.0+dfsg-1
Severity: serious

Hello,
autopkgtests are failing, please check the logs at:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fabio/10229362/log.gz

The same tests are not executed during build time, and that's why the package
builds fine (i verify that just now) but then autopkgtests fail.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#978452: python3-opencv: missing dependency on libcharls2

2020-12-27 Thread Sandro Tosi
Package: python3-opencv
Version: 4.5.1+dfsg-1
Severity: grave

Hello,
i've just upgraded to opencv 4.5.1 and when importing the python module, i got
this error:

Traceback (most recent call last):
  File "tool", line 10, in 
import cv2
ImportError: libcharls.so.2: cannot open shared object file: No such file or 
directory

which is provided by libcharls2, and after installing it, i can import cv2 fine.

set to RC level because if i cant even import the module, that's a broken enough
package that's unusable.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-opencv depends on:
ii  libc6   2.30-2
ii  libgcc-s1   10.2.1-3
ii  libopencv-calib3d4.54.5.1+dfsg-1
ii  libopencv-contrib4.54.5.1+dfsg-1
ii  libopencv-core4.5   4.5.1+dfsg-1
ii  libopencv-dnn4.54.5.1+dfsg-1
ii  libopencv-features2d4.5 4.5.1+dfsg-1
ii  libopencv-flann4.5  4.5.1+dfsg-1
ii  libopencv-highgui4.54.5.1+dfsg-1
ii  libopencv-imgcodecs4.5  4.5.1+dfsg-1
ii  libopencv-imgproc4.54.5.1+dfsg-1
ii  libopencv-ml4.5 4.5.1+dfsg-1
ii  libopencv-objdetect4.5  4.5.1+dfsg-1
ii  libopencv-photo4.5  4.5.1+dfsg-1
ii  libopencv-shape4.5  4.5.1+dfsg-1
ii  libopencv-stitching4.5  4.5.1+dfsg-1
ii  libopencv-superres4.5   4.5.1+dfsg-1
ii  libopencv-video4.5  4.5.1+dfsg-1
ii  libopencv-videoio4.54.5.1+dfsg-1
ii  libopencv-videostab4.5  4.5.1+dfsg-1
ii  libopencv-viz4.54.5.1+dfsg-1
ii  libstdc++6  10.2.1-3
ii  python3 3.9.1-1
ii  python3-numpy [python3-numpy-abi9]  1:1.19.4-1+b1

python3-opencv recommends no packages.

python3-opencv suggests no packages.

-- no debconf information

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#959991: joblib: build and install documentation

2020-11-30 Thread Sandro Tosi
> I don't have any particular interest in this package,

then maybe let the maintainer take care of it?

> but if you
> supply a patch, I am happy to apply it and do a team upload.

no thanks

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#970899: libflame: add hypothesis to numpy autopkgtests dependencies

2020-09-24 Thread Sandro Tosi
Source: libflame
Severity: serious

Hello,
please add hypothesis to the autopkgtests dependencies when testing numpy;

autopkgtest [03:28:25]: test numpy-with-default: python3 -c "import numpy as 
np; np.test('full', verbose=3)"
autopkgtest [03:28:25]: test numpy-with-default: [---
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/numpy/_pytesttester.py", line 129, in 
__call__
import hypothesis
ModuleNotFoundError: No module named 'hypothesis'
autopkgtest [03:28:26]: test numpy-with-default: ---]
autopkgtest [03:28:26]: test numpy-with-default:  - - - - - - - - - - results - 
- - - - - - - - -


autopkgtest [03:55:13]: test numpy-with-libflame: python3 -c "import numpy as 
np; np.test('full', verbose=3)"
autopkgtest [03:55:13]: test numpy-with-libflame: [---
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/numpy/_pytesttester.py", line 129, in 
__call__
import hypothesis
ModuleNotFoundError: No module named 'hypothesis'
autopkgtest [03:55:13]: test numpy-with-libflame: ---]
autopkgtest [03:55:14]: test numpy-with-libflame:  - - - - - - - - - - results 
- - - - - - - - - -
numpy-with-libflame  FAIL non-zero exit status 1


it's not appropriate to add hypothesis to python3-numpy Depends since running
numpy tests is beyond the general use of the library, so at best it could be a
Suggests, which wont solve the failure of the autopkgtest.

RC severity since it's blocking the migration of numpy.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#959991: joblib: build and install documentation

2020-05-07 Thread Sandro Tosi
Source: joblib
Severity: normal

Hello,
the upstream tarball contains the doc dir, so please build it and ship it in a
-doc package.  sphinx-gallery will benefit from it since it uses joblib
intersphinx data for its tests.

Thanks!

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#959990: joblib: update Homepage field

2020-05-07 Thread Sandro Tosi
Source: joblib
Severity: normal

Hello,
Homepage points to http://packages.python.org/joblib/ but that's 404ing right
now. debian/copyright already points to https://github.com/joblib/joblib so
maybe update Homepage to the gh project?

thanks

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#936727: ignition-math4: Python2 removal in sid/bullseye - reopen 936727

2020-04-09 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:ignition-math4)Build-Depends->python

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#943135: numba: Python2 removal in sid/bullseye - reopen 943135

2020-04-09 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:numba)Testsuite-Triggers->python-all-dev
(source:numba)Testsuite-Triggers->python-funcsigs
(source:numba)Testsuite-Triggers->python-numba
(source:numba)Testsuite-Triggers->python-singledispatch
(binary:numba-doc)Recommends->python-numba

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#943706: Issue with building opencv prevents fixing psychopy (Re: Bug#937330: psychopy: Python2 removal in sid/bullseye - reopen 937330)

2020-03-11 Thread Sandro Tosi
> > (binary:psychopy)Recommends->ipython
> >
> > Re-opening, so that they can be taken care of.
>
> I've fixed this in Git.

i dont think you pushed your changes to salsa :(

> However, the package currently does not build
> due to
>
>python3-opencv : Depends: python3 (< 3.8) but 3.8.2-1 is to be installed

as other said, opencv was tangled in the python3.8 transition, but as
of a couple of hours ago it has been built on all release architecture
(the amd64 binnmu already hit the archive and mirrors) so please do
retry to upload psychopy and see how that goes.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: Processed: Gallery generation broken with sphinx-gallery 0.2.0

2020-03-06 Thread Sandro Tosi
i've just uploaded sphinx-gallery_0.5.0-1 which should fix this issue,
can you give it a nother try when it reaches the archive? thanks!

On Fri, Mar 6, 2020 at 3:21 AM Debian Bug Tracking System
 wrote:
>
> Processing control commands:
>
> > reassign -1 python3-sphinx-gallery 0.2.0-3
> Bug #951768 [src:skimage] skimage documentation build fails with python 3.8
> Bug reassigned from package 'src:skimage' to 'python3-sphinx-gallery'.
> No longer marked as found in versions skimage/0.16.2-2.
> Ignoring request to alter fixed versions of bug #951768 to the same values 
> previously set
> Bug #951768 [python3-sphinx-gallery] skimage documentation build fails with 
> python 3.8
> Marked as found in versions sphinx-gallery/0.2.0-3.
>
> --
> 951768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951768
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: debian-science: Python2 removal in sid/bullseye - reopen 935927

2020-03-05 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:science-numericalcomputation)Recommends->ipython

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#936740: ipe-tools: Python2 removal in sid/bullseye - reopen 936740

2020-02-21 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:svgtoipe)Recommends->python-pil

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#937214: openturns: Python2 removal in sid/bullseye - reopen 937214

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:openturns-examples)Depends->python

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#943226: python-xarray: Python2 removal in sid/bullseye - reopen 943226

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:python-xarray)Build-Depends->python-pip

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#938426: sagemath: Python2 removal in sid/bullseye - reopen 938426

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:sagemath)Build-Depends->cython
(source:sagemath)Build-Depends->cython-dbg
(binary:sagemath)Depends->cython

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#937396: pybtex: Python2 removal in sid/bullseye - reopen 937396

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:pybtex)Testsuite-Triggers->python-all
(source:pybtex)Testsuite-Triggers->python-nose
(source:pybtex)Testsuite-Triggers->python-pybtex

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#938743: ufo-core: Python2 removal in sid/bullseye - reopen 938743

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:libufo-bin)Depends->python:any

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: debian-science: Python2 removal in sid/bullseye - reopen 935927

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:science-engineering)Recommends->pythoncad

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#936924: libsvm: Python2 removal in sid/bullseye - reopen 936924

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(binary:libsvm-tools)Depends->python:any

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#936740: ipe-tools: Python2 removal in sid/bullseye - reopen 936740

2020-01-18 Thread Sandro Tosi
Control: reopen -1

This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:

(source:ipe-tools)Build-Depends->python
(binary:svgtoipe)Depends->python
(binary:svgtoipe)Depends->python:any
(binary:svgtoipe)Recommends->python-pil

Re-opening, so that they can be taken care of.
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#948700: scikit-learn: re-enable build and installation of -doc package

2020-01-11 Thread Sandro Tosi
Source: scikit-learn
Version: 0.22.1+dfsg-1
Severity: important

Hello,
in order to package 0.22.1, we had to disable the build of the documentation via
sphinx, as that's requires sphinx 2.* while debian currently only ships 1.8.5

Refer to:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944913
https://github.com/scikit-learn/scikit-learn/issues/16087#issuecomment-573092993

Please re-enable as soon as #944913 is addressed.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#936238: brial: diff for NMU version 1.2.5-2.1

2020-01-10 Thread Sandro Tosi
Control: tags 936238 + patch


Dear maintainer,

I've prepared an NMU for brial (versioned as 1.2.5-2.1). The diff
is attached to this message.

Regards.

diff -Nru brial-1.2.5/debian/changelog brial-1.2.5/debian/changelog
--- brial-1.2.5/debian/changelog	2019-11-10 15:15:02.0 -0500
+++ brial-1.2.5/debian/changelog	2020-01-10 14:06:12.0 -0500
@@ -1,3 +1,10 @@
+brial (1.2.5-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936238
+
+ -- Sandro Tosi   Fri, 10 Jan 2020 14:06:12 -0500
+
 brial (1.2.5-2) unstable; urgency=medium
 
   * Rebuild with gcc-9 (required to fix segfaults in sagemath).
diff -Nru brial-1.2.5/debian/control brial-1.2.5/debian/control
--- brial-1.2.5/debian/control	2019-11-10 15:14:55.0 -0500
+++ brial-1.2.5/debian/control	2020-01-10 14:05:50.0 -0500
@@ -10,7 +10,6 @@
libboost-python-dev,
libboost-test-dev,
libm4ri-dev (>= 20120613),
-   python-all-dev,
python3-all-dev,
libgd-dev,
libjpeg-dev,
@@ -21,30 +20,6 @@
 Vcs-Browser: https://salsa.debian.org/science-team/brial
 Homepage: https://github.com/BRiAl
 
-Package: python-brial
-Architecture: any
-Section: python
-Replaces: python-polybori (<< 0.8.5)
-Breaks: python-polybori (<< 0.8.5), sagemath (<< 8.1~)
-Depends: ${shlibs:Depends},
- ${misc:Depends},
- libbrial3 (= ${binary:Version}),
- libbrial-groebner3 (= ${binary:Version}),
- ${python:Depends}
-Description: polynomials over Boolean Rings, Python 2 module
- The core of BRiAl is a C++ library, which provides high-level data
- types for Boolean polynomials and monomials, exponent vectors, as
- well as for the underlying polynomial rings and subsets of the
- powerset of the Boolean variables. As a unique approach, binary
- decision diagrams are used as internal storage type for polynomial
- structures. On top of this C++-library a Python interface
- is provided. This allows parsing of complex polynomial systems, as well
- as sophisticated and extendable strategies for Groebner base
- computation. BRiAl features a powerful reference implementation
- for Groebner basis computation.
- .
- This package contains the BRiAl Python 2 module.
-
 Package: python3-brial
 Architecture: any
 Section: python
diff -Nru brial-1.2.5/debian/python-brial.install brial-1.2.5/debian/python-brial.install
--- brial-1.2.5/debian/python-brial.install	2019-09-01 04:03:40.0 -0400
+++ brial-1.2.5/debian/python-brial.install	1969-12-31 19:00:00.0 -0500
@@ -1,2 +0,0 @@
-usr/lib/python2.*/
-
diff -Nru brial-1.2.5/debian/rules brial-1.2.5/debian/rules
--- brial-1.2.5/debian/rules	2019-09-01 04:03:40.0 -0400
+++ brial-1.2.5/debian/rules	2020-01-10 14:06:05.0 -0500
@@ -5,7 +5,7 @@
 export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 
 %:
-	dh $@ --with python2,python3
+	dh $@ --with python3
 
 override_dh_auto_build:
 	dh_auto_build
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#933366: scikit-learn: Please upgrade to 0.21.0 or later

2020-01-08 Thread Sandro Tosi
Package: src:scikit-learn
Followup-For: Bug #933366

Hello,
i was trying to rebuild 0.20.3+dfsg-0.1 to disable the python2 autopkgtests but
now that version FTBFS; i believe it's becaues it's rather old (March 2019) and
a lot of other packages have been upgraded recently (namely scipy and numpy,
probably more anyway).

so i'm gonna start working on packaging 0.22.1 which has just been released,
hopefully i'll complete this work soon.

FTR the failure is:

```
=== FAILURES ===
___ test_scale_and_stability ___

def test_scale_and_stability():
# We test scale=True parameter
# This allows to check numerical stability over platforms as well

d = load_linnerud()
X1 = d.data
Y1 = d.target
# causes X[:, -1].std() to be zero
X1[:, -1] = 1.0

# From bug #2821
# Test with X2, T2 s.t. clf.x_score[:, 1] == 0, clf.y_score[:, 1] == 0
# This test robustness of algorithm when dealing with value close to 0
X2 = np.array([[0., 0., 1.],
   [1., 0., 0.],
   [2., 2., 2.],
   [3., 5., 4.]])
Y2 = np.array([[0.1, -0.2],
   [0.9, 1.1],
   [6.2, 5.9],
   [11.9, 12.3]])

for (X, Y) in [(X1, Y1), (X2, Y2)]:
X_std = X.std(axis=0, ddof=1)
X_std[X_std == 0] = 1
Y_std = Y.std(axis=0, ddof=1)
Y_std[Y_std == 0] = 1

X_s = (X - X.mean(axis=0)) / X_std
Y_s = (Y - Y.mean(axis=0)) / Y_std

for clf in [CCA(), pls_.PLSCanonical(), pls_.PLSRegression(),
pls_.PLSSVD()]:
clf.set_params(scale=True)
X_score, Y_score = clf.fit_transform(X, Y)
clf.set_params(scale=False)
X_s_score, Y_s_score = clf.fit_transform(X_s, Y_s)
>   assert_array_almost_equal(X_s_score, X_score)
E   AssertionError: 
E   Arrays are not almost equal to 6 decimals
E   
E   Mismatch: 50%
E   Max absolute difference: 5.15227746e-06
E   Max relative difference: 0.00011717
Ex: array([[-1.337317, -0.041709],
E  [-1.108472,  0.098156],
E  [ 0.407632, -0.10308 ],
E  [ 2.038158,  0.046633]])
Ey: array([[-1.337317, -0.041713],
E  [-1.108472,  0.098159],
E  [ 0.407632, -0.103075],
E  [ 2.038158,  0.04663 ]])

sklearn/cross_decomposition/tests/test_pls.py:360: AssertionError
 test_unsorted_indices _

def test_unsorted_indices():
# test that the result with sorted and unsorted indices in csr is the 
same
# we use a subset of digits as iris, blobs or make_classification didn't
# show the problem
digits = load_digits()
X, y = digits.data[:50], digits.target[:50]
X_test = sparse.csr_matrix(digits.data[50:100])

X_sparse = sparse.csr_matrix(X)
coef_dense = svm.SVC(kernel='linear', probability=True,
 random_state=0).fit(X, y).coef_
sparse_svc = svm.SVC(kernel='linear', probability=True,
 random_state=0).fit(X_sparse, y)
coef_sorted = sparse_svc.coef_
# make sure dense and sparse SVM give the same result
assert_array_almost_equal(coef_dense, coef_sorted.toarray())

X_sparse_unsorted = X_sparse[np.arange(X.shape[0])]
X_test_unsorted = X_test[np.arange(X_test.shape[0])]

# make sure we scramble the indices
>   assert_false(X_sparse_unsorted.has_sorted_indices)

sklearn/svm/tests/test_sparse.py:118: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , expr = 1
msg = '1 is not false'

def assertFalse(self, expr, msg=None):
"""Check that the expression is false."""
if expr:
msg = self._formatMessage(msg, "%s is not false" % safe_repr(expr))
>   raise self.failureException(msg)
E   AssertionError: 1 is not false

/usr/lib/python3.8/unittest/case.py:759: AssertionError
=== short test summary info 
SKIPPED [1] /usr/lib/python3/dist-packages/_pytest/nose.py:32: This test is 
failing on the buildbot, but cannot reproduce. Temporarily disabling it until 
it can be reproduced and  fixed.
SKIPPED [3] /usr/lib/python3/dist-packages/_pytest/nose.py:32: Download 20 
newsgroups to run this test
SKIPPED [1] /usr/lib/python3/dist-packages/_pytest/nose.py:32: California 
housing dataset can not be loaded.
SKIPPED [1] /usr/lib/python3/dist-packages/_pytest/nose.py:32: Covertype 

Bug#947757: pysparse: should this package be removed?

2019-12-29 Thread Sandro Tosi
Source: pysparse
Severity: serious

Hello,
it seeems to me there are several issues with this package:

* python2 only, and there's already another `python3-sparse` from another src
* no upstream commits since 2013, 
https://sourceforge.net/p/pysparse/git/commit_browser
* no upstream releases since 2010

If i dont hear back within a week with a good reason to keep this package in
Debian, i'll file for its removal.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#946926: pysparse: should this package be removed?

2019-12-17 Thread Sandro Tosi
Source: pysparse
Severity: serious

Hello,
it looks like pysparse is no longer fit to remain in debian:

* python2 only
* no upstream release in 8+ years
* python3-sparse exists, as a possible alternative?

If i dont hear back within a week with a good reason to keep this package, i
will file for its removal.

Regards,
Sandro

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#937214: openturns: Python2 removal in sid/bullseye

2019-12-17 Thread Sandro Tosi
tests are failing when building the updated package in git,
https://github.com/openturns/openturns/issues/1346

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#945686: petsc4py: Python2 removal in sid/bullseye

2019-11-27 Thread Sandro Tosi
Source: petsc4py
Version: 3.11.0-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#945678: ompl: Python2 removal in sid/bullseye

2019-11-27 Thread Sandro Tosi
Source: ompl
Version: 1.4.2+ds1-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#945643: giella-core: Python2 removal in sid/bullseye

2019-11-27 Thread Sandro Tosi
Source: giella-core
Version: 0.1.1~r129227+svn121148-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#945621: slepc4py: rename python-slepc4py-docs to python-slepc4py-doc

2019-11-27 Thread Sandro Tosi
Source: slepc4py
Severity: important

Python doc packages should have -doc suffix, not -docs. please rename

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#945620: petsc4py: rename python-petsc4py-docs to python-petsc4py-doc

2019-11-27 Thread Sandro Tosi
Source: petsc4py
Severity: important

Python doc package should have a -doc suffix, not -docs, please rename

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#943217: pplpy: diff for NMU version 0.8.4-3

2019-10-27 Thread Sandro Tosi
Control: tags 943217 + patch


Dear maintainer,

I've prepared an NMU for pplpy (versioned as 0.8.4-3). The diff
is attached to this message.

apparently master is protected on git and i cant push to it..

Regards.

diff -Nru pplpy-0.8.4/debian/changelog pplpy-0.8.4/debian/changelog
--- pplpy-0.8.4/debian/changelog	2019-09-03 07:54:50.0 -0400
+++ pplpy-0.8.4/debian/changelog	2019-10-26 16:39:43.0 -0400
@@ -1,3 +1,10 @@
+pplpy (0.8.4-3) unstable; urgency=medium
+
+  * Team upload.
+  * Drop python2 support; Closes: #943217
+
+ -- Sandro Tosi   Sat, 26 Oct 2019 16:39:43 -0400
+
 pplpy (0.8.4-2) unstable; urgency=medium
 
   * Add upstream patch to fix doctests on 32 bit architectures.
diff -Nru pplpy-0.8.4/debian/control pplpy-0.8.4/debian/control
--- pplpy-0.8.4/debian/control	2019-09-03 07:54:24.0 -0400
+++ pplpy-0.8.4/debian/control	2019-10-26 16:23:58.0 -0400
@@ -6,7 +6,6 @@
 Build-Depends:
  debhelper (>= 11),
  dh-python (>= 3.20180313),
- cython (>= 0.26),
  cython3 (>= 0.26),
  libgmp-dev,
  libmpfr-dev,
@@ -14,15 +13,10 @@
  libppl-dev,
  libpari-dev,
  libjs-mathjax,
- python-all-dev,
  python3-all-dev,
- python-cysignals-pari (>= 1.8.1),
  python3-cysignals-pari (>= 1.8.1),
- python-gmpy2,
  python3-gmpy2,
- python-setuptools,
  python3-setuptools,
- python-sphinx,
  python3-sphinx,
 Standards-Version: 4.4.0
 X-Python3-Version: >= 3.7
@@ -30,16 +24,6 @@
 Vcs-Git: https://salsa.debian.org/science-team/pplpy.git
 Vcs-Browser: https://salsa.debian.org/science-team/pplpy
 
-Package: python-ppl
-Architecture: any
-Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}, python-cysignals-pari
-Description: Python interface to PPL -- Python 2
- A Python interface to the C++ Parma Polyhedra Library (PPL),
- which allows computations with polyhedra and grids, like mixed
- integer linear programming.
- .
- This package installs the library for Python 2.
-
 Package: python3-ppl
 Architecture: any
 Depends: ${python3:Depends}, ${shlibs:Depends}, ${misc:Depends}, python3-cysignals-pari
diff -Nru pplpy-0.8.4/debian/rules pplpy-0.8.4/debian/rules
--- pplpy-0.8.4/debian/rules	2019-09-03 07:54:24.0 -0400
+++ pplpy-0.8.4/debian/rules	2019-10-26 16:24:28.0 -0400
@@ -4,7 +4,7 @@
 export PYBUILD_NAME = ppl
 
 %:
-	dh $@ --with autoreconf --with python2,python3,sphinxdoc  --buildsystem=pybuild
+	dh $@ --with autoreconf --with python3,sphinxdoc  --buildsystem=pybuild
 
 override_dh_auto_build: export http_proxy=127.0.0.1:9
 override_dh_auto_build: export https_proxy=127.0.0.1:9
@@ -14,10 +14,6 @@
 
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS) $(DEB_BUILD_PROFILES)))
 override_dh_auto_test:
-	export PYTHONPATH=$(CURDIR)/.pybuild/cpython2_2.7_ppl/build && python2 tests/runtests.py
-	export PYTHONPATH=$(CURDIR)/.pybuild/cpython2_2.7_ppl/build && cd tests && python2 setup.py build_ext --inplace
-	export PYTHONPATH=$(CURDIR)/.pybuild/cpython2_2.7_ppl/build && cd tests && python2 setup2.py build_ext --inplace
-	export PYTHONPATH=$(CURDIR)/.pybuild/cpython2_2.7_ppl/build && cd tests && python2 -c "import testpplpy; testpplpy.test(); testpplpy.example(); import testpplpy2; testpplpy2.test(); testpplpy2.example()"
 	export PYTHONPATH=$(CURDIR)/.pybuild/cpython3_3.7_ppl/build && python3 tests/runtests.py
 	export PYTHONPATH=$(CURDIR)/.pybuild/cpython3_3.7_ppl/build && cd tests && python3 setup.py build_ext --inplace
 	export PYTHONPATH=$(CURDIR)/.pybuild/cpython3_3.7_ppl/build && cd tests && python3 setup2.py build_ext --inplace
diff -Nru pplpy-0.8.4/debian/tests/control pplpy-0.8.4/debian/tests/control
--- pplpy-0.8.4/debian/tests/control	2019-07-19 09:34:24.0 -0400
+++ pplpy-0.8.4/debian/tests/control	2019-10-26 16:24:40.0 -0400
@@ -1,7 +1,3 @@
-Tests: upstreamtestsuite2
-Depends: python-ppl
-Restrictions: allow-stderr
-
 Tests: upstreamtestsuite3
 Depends: python3-ppl
 Restrictions: allow-stderr
diff -Nru pplpy-0.8.4/debian/tests/upstreamtestsuite2 pplpy-0.8.4/debian/tests/upstreamtestsuite2
--- pplpy-0.8.4/debian/tests/upstreamtestsuite2	2019-07-19 09:34:24.0 -0400
+++ pplpy-0.8.4/debian/tests/upstreamtestsuite2	1969-12-31 19:00:00.0 -0500
@@ -1,3 +0,0 @@
-#!/bin/sh
-set -e
-python2 tests/runtests.py
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#943663: pyviennacl: should this package be removed?

2019-10-27 Thread Sandro Tosi
Source: pyviennacl
Severity: serious

Hello,
this package has 2 RC bugs un-addressed since more 3 and 4 years respectively!
Due to this, it is not in stable. There were only ever been 2 uploads of this
package, 5 years ago.  should we just remove it from debian?

if i dont hear back within a week with a good reason to keep this package, i'll
file for it's removal (it also has no rdeps)


-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: upcoming Robot OS uploads to drop python2 support

2019-10-24 Thread Sandro Tosi
> thanks for the offer but there is no need to. I have worked on new
> Python 3 only packages, finished the last tests yesterday and started
> uploading already. I will continue to upload them in a non breaking way
> full time starting today.

Fantastic, thanks a lot Jochen! let me know if i can help

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

upcoming Robot OS uploads to drop python2 support

2019-10-24 Thread Sandro Tosi
Hello folks,
in the next couple of days i will go thru all ROS packages to drop
their python2 packages; none of them has reverse dependencies in
Debian, and it will help greatly the effort described at
https://wiki.debian.org/Python/2Removal .

I'll commit my changes to their git repos but i'd like to upload
directly to unstable; please let me know if that's not ok and i'll
have you review the changes (which are usually very minimal and only
in debian/{control,rules}).

I know it's short notice, so apologies for that.

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#937556: pytango: diff for NMU version 9.3.0-1.1

2019-10-17 Thread Sandro Tosi
Control: tags 937556 + patch
Control: tags 937556 + pending


Dear maintainer,

I've prepared an NMU for pytango (versioned as 9.3.0-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru pytango-9.3.0/debian/changelog pytango-9.3.0/debian/changelog
--- pytango-9.3.0/debian/changelog	2019-09-28 14:18:02.0 -0400
+++ pytango-9.3.0/debian/changelog	2019-10-17 19:00:57.0 -0400
@@ -1,3 +1,10 @@
+pytango (9.3.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937556
+
+ -- Sandro Tosi   Thu, 17 Oct 2019 19:00:57 -0400
+
 pytango (9.3.0-1) unstable; urgency=medium
 
   [ Picca Frédéric-Emmanuel ]
diff -Nru pytango-9.3.0/debian/control pytango-9.3.0/debian/control
--- pytango-9.3.0/debian/control	2019-09-28 14:18:02.0 -0400
+++ pytango-9.3.0/debian/control	2019-10-17 19:00:24.0 -0400
@@ -10,16 +10,6 @@
libboost-python-dev,
libtango-dev,
pkg-config,
-   python-all-dev,
-   python-concurrent.futures ,
-   python-enum34,
-   python-gevent ,
-   python-mock ,
-   python-numpy,
-   python-setuptools,
-   python-six,
-   python-sphinx ,
-   python-sphinx-rtd-theme ,
python3-all-dev,
python3-gevent ,
python3-mock ,
@@ -35,23 +25,6 @@
 Homepage: http://www.tango-controls.org/static/PyTango/latest/doc/html/
 Rules-Requires-Root: no
 
-Package: python-tango
-Architecture: any
-Section: python
-Depends: ${misc:Depends},
- ${python:Depends},
- ${shlibs:Depends},
- python-enum34
-Provides: ${python:Provides}
-Description: API for the TANGO control system (Python 2)
- TANGO is an object oriented distributed control system using CORBA,
- mainly developed by the Controls Section of the ALBA Synchrotron.
- PyTango provides bindings for its client- and server-side C++ APIs.
- With PyTango, you can write TANGO device servers and TANGO applications
- (scripts, CLIs, GUIs) that access TANGO device servers in pure Python.
- .
- This is the Python 2 version of the package.
-
 Package: python3-tango
 Architecture: any
 Section: python
diff -Nru pytango-9.3.0/debian/python-tango.pydist pytango-9.3.0/debian/python-tango.pydist
--- pytango-9.3.0/debian/python-tango.pydist	2019-09-28 14:18:02.0 -0400
+++ pytango-9.3.0/debian/python-tango.pydist	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-pytango python-tango; PEP386
diff -Nru pytango-9.3.0/debian/rules pytango-9.3.0/debian/rules
--- pytango-9.3.0/debian/rules	2019-09-28 14:18:02.0 -0400
+++ pytango-9.3.0/debian/rules	2019-10-17 19:00:45.0 -0400
@@ -1,10 +1,10 @@
 #!/usr/bin/make -f
 
 export PYBUILD_NAME=tango
-export PYBUILD_AFTER_INSTALL=dh_numpy ; dh_numpy3
+export PYBUILD_AFTER_INSTALL=dh_numpy3
 
 %:
-	dh $@ --with python2,python3,sphinxdoc --buildsystem=pybuild
+	dh $@ --with python3,sphinxdoc --buildsystem=pybuild
 
 
 override_dh_auto_clean:
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: guiqwt: Python2 removal in sid/bullseye

2019-10-08 Thread Sandro Tosi
Version: 3.0.3-4

https://tracker.debian.org/news/1070228/accepted-guiqwt-303-4-source-into-unstable/

Debian Science team,
please remember to properly close bugs in the changelog; this is not
the first bug i have to close by hand for pkgs maintained in this team
:)

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: Suggests instead of comment of Python2 only packages? (Was: debian-science: migrate all python dependencies to their python3 variant)

2019-10-02 Thread Sandro Tosi
> BTW, I've checked debian-med tasks for replacable python-* packages was
> successfully for some but some others remaining.  If you feel an urgent
> need also for debian-med metapackages I can do the same as for Debian
> Science there.

thanks Andreas! that would be really helpful indeed! i'd take the same
approach as debian-science: replace py2 with py3 where available,
comment out package py2-only, remove where packages are no longer
available in debian

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#932683: Bug#932679: python-gdal dropped from gdal (3.0.1+dfsg-1~exp3)

2019-10-01 Thread Sandro Tosi
On Tue, Oct 1, 2019 at 1:21 PM Sebastiaan Couwenberg  wrote:
>
> On 8/30/19 10:20 AM, Sebastiaan Couwenberg wrote:
> > gdal (3.0.1+dfsg-1~exp3) dropped support for Python 2 and no longer
> > builds python-gdal.
>
> The next upload of GDAL 2.4.x will also drop support for Python 2 and no
> longer build python-gdal.

why?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: Suggests instead of comment of Python2 only packages? (Was: debian-science: migrate all python dependencies to their python3 variant)

2019-10-01 Thread Sandro Tosi
> Just uploaded.

thanks!!!

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: Suggests instead of comment of Python2 only packages? (Was: debian-science: migrate all python dependencies to their python3 variant)

2019-09-27 Thread Sandro Tosi
Hey Andreas and others

On Fri, Sep 27, 2019 at 5:51 AM Andreas Tille  wrote:
> Regarding your change:
>
> Switch every python dependency to Python3 (removing packages no longer
> available, commenting out python2-only packages); Closes: #935927
>
> I'm wondering whether it would not be better to rather
>
> Suggests: python2-only
>
> packages.

i'm not very familiar on how people uses this tasks packages, but if
(say) 90% of the python modules are python3-only, how can you use that
10% that's python2 only? you cant write code unless it's very
specialized to that specific module and uses *none* of the py3k-only
packages; most likely that module will get removed if there is no py3k
support or if there is, we're gonna remove the py2 package anyway.

the reason i left them as comment is for the science team to
"remember" they used to be there and decide at a later time what to
do: is the package still in Debian and been ported to py3k? add it
back. was it removed? remove the commented line.

>  If the packages are commented out they become absolutely
> invisible while per policy suggested packages do not need to exist and
> thus the metapackages would not block a removal of the packages
> themselves.

the way we're tracking the removal (via
http://sandrotosi.me/debian/py2removal/index.html) considers also the
Suggests fields as a rdeps. Also i dont see anything about not being
avaible as a valid state in
https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends
for suggests

> Since you felt a need to change this in Git I guess you are interested
> in a soonish upload.

indeed i am :)

>  So if we have some consensus about the item above
> I'll upload to get the changes applied.

i gave you my opinion, but i'm happy with whatever the team comes up
about it, if that means we can upload soon :)

Cheers,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Re: Bug#935927: debian-science: migrate all python dependencies to their python3 variant

2019-09-26 Thread Sandro Tosi
On Mon, Sep 16, 2019 at 9:54 PM Sandro Tosi  wrote:
>
> On Mon, Sep 16, 2019 at 9:33 PM David Bremner  wrote:
> >
> > Sandro Tosi  writes:
> >
> > >
> > > any update here? if i dont hear anything within a week, i will raise
> > > the severity of this bug to serious.
> >
> > That seems a little ahead of the curve. I'm pretty sure we're months (if
> > not years) away from removing python2.
>
> not necessarily (and the sooner we start the sooner we finish). do you
> see any blockers in moving the dependencies of debian-science to
> python3?

Ive just pushed 8db1e2eae137d103ef9df5b4512d05f9ebcdb2ba to address this bug:

- every module with a py3k bin package, has been migrated to it
- if the module is python2-only, it's still in the tasks file but commented out
- if the module is not in debian anymore/yet, it has been removed.

It'd be great if someone with more knowledge than me on blends
packaging could give it a look and possibly upload the package.

I'll set a reminder to myself in a week to `make` and upload
debian-science if nobody comments/does so before.

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#932683: Bug#932679: python-gdal dropped from gdal (3.0.1+dfsg-1~exp3)

2019-09-16 Thread Sandro Tosi
thanks for the heads up, but please note python-networkx has still
planty of reverse-dependencies, so we cannot drop that package yet.
please dont drop python-gdal from unstable until it has no rev-deps.
thanks!

On Fri, Aug 30, 2019 at 4:55 AM Sebastiaan Couwenberg
 wrote:
>
> gdal (3.0.1+dfsg-1~exp3) dropped support for Python 2 and no longer
> builds python-gdal.
>
> Your package will break when the transition to gdal 3.x starts.
>
> Kind Regards,
>
> Bas
>
> --
>  GPG Key ID: 4096R/6750F10AE88D4AF1
> Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: debian-science: migrate all python dependencies to their python3 variant

2019-09-16 Thread Sandro Tosi
On Mon, Sep 16, 2019 at 9:33 PM David Bremner  wrote:
>
> Sandro Tosi  writes:
>
> >
> > any update here? if i dont hear anything within a week, i will raise
> > the severity of this bug to serious.
>
> That seems a little ahead of the curve. I'm pretty sure we're months (if
> not years) away from removing python2.

not necessarily (and the sooner we start the sooner we finish). do you
see any blockers in moving the dependencies of debian-science to
python3?

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#935927: debian-science: migrate all python dependencies to their python3 variant

2019-09-16 Thread Sandro Tosi
> Source: debian-science
> Severity: important
>
> Hello,
> many of the packages on this set refer to python packages.  Theres an effort
> on-going to remove Python 2 for Bullseye,
> https://wiki.debian.org/Python/2Removal .
>
> It would be great if you could migrate all the python dependencies here into
> their python3 correspondent ones.
>
> This will "free" packages from being reverse dependencies of debian-science 
> deps
> packages, hence they could ideally be removed (once we figure out the
> remaining rdeps).
>
> Given the high number of python deps from debian-science, it would be awesome 
> if
> you could tackle this sooner rather than later.
>
> Let me know if i could help (ideally porting some of the deps to python3).

any update here? if i dont hear anything within a week, i will raise
the severity of this bug to serious.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

  1   2   >