Bug#993622: python3-open3d: Missing dependency on python3-numpy

2021-09-03 Thread Shane Loretz
Package: python3-open3d
Version: 0.9.0+ds-5+b2
Severity: normal
X-Debbugs-Cc: slor...@openrobotics.org

Dear Maintainer,

It appears python3-open3d is missing a dependency on python3-numpy.
The module can't be imported until it's manually installed.

On a fresh bullseye container I installed python3-open3d 

bullseye:root> apt install libopen3d-dev/stable libopen3d0d/stable 
python3-open3d/stable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 
'libopen3d-dev'
Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 
'libopen3d0d'
Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 
'python3-open3d'
...

But I encountered an ImportError:

>>> import open3d
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/open3d/__init__.py", line 3, in 

from .open3d import *
ImportError: ModuleNotFoundError: No module named 'numpy'

So I installed python3-numpy, and afterwards I was able to import
open3d.

>>> import open3d
>>>

Would you be willing to add this dependency to the Debian package?


Cheers,
Shane

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.11.0-27-generic (SMP w/24 CPU threads)
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 not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python3-open3d depends on:
ii  libc62.31-13
ii  libgcc-s110.2.1-6
ii  libopen3d0d  0.9.0+ds-5+b2
ii  libstdc++6   10.2.1-6
ii  python3  3.9.2-3

python3-open3d recommends no packages.

Versions of packages python3-open3d suggests:
pn  open3d-doc  

-- no debconf information



Bug#956254: python3-pykdl: PyKDL crashes Python 3 interpretter (SIGABRT) if any API accepting a str is used

2020-04-17 Thread Shane Loretz
I tested the orocos-kdl 1.4.0-9 sources using debuild/dpkg -i in a Debian
Buster container and can confirm it works for my use case. Thanks again!

On Thu, Apr 9, 2020 at 10:01 AM Jochen Sprickerhof 
wrote:

> Hi Shane,
>
> * Shane Loretz  [2020-04-08 22:19]:
> >Would you be willing to apply that patch and release a new version to
> >Buster and Sid?
>
> I've uploaded a fixed version to sid and proposed an update to the
> release team in #956315. Thanks for opening the bug!
>
> Cheers Jochen
>


Bug#956254: python3-pykdl: PyKDL crashes Python 3 interpretter (SIGABRT) if any API accepting a str is used

2020-04-08 Thread Shane Loretz
Package: python3-pykdl
Version: 1.4.0-7
Severity: important
Tags: patch

Dear Maintainer,


The package python3-pykdl crashes the Python 3 interpretter if any API
accepting a str is used. I've tested this in both Debian Buster and Sid.

$ python3 -c "import PyKDL; PyKDL.Tree('foobar')"
python3: 
/build/orocos-kdl-oHbJfL/orocos-kdl-1.4.0/python_orocos_kdl/PyKDL/std_string.sip:52:
 int convertTo_std_string(PyObject*, void**, int*, PyObject*): Assertion 
`PyUnicode_Check(s)' failed.
Aborted (core dumped)
$ echo $?
134

The following patch resolves the issue on both Buster (1.4.0-7) and Sid
(1.4.0-8)


Index: orocos-kdl-1.4.0/python_orocos_kdl/PyKDL/std_string.sip
===
--- orocos-kdl-1.4.0.orig/python_orocos_kdl/PyKDL/std_string.sip
+++ orocos-kdl-1.4.0/python_orocos_kdl/PyKDL/std_string.sip
@@ -48,9 +48,7 @@
  return 1;
  }
  if (PyUnicode_Check(sipPy)) {
-PyObject* s = PyUnicode_AsEncodedString(sipPy, "UTF-8", "");
-*sipCppPtr = new std::string(PyUnicode_AS_DATA(s));
-Py_DECREF(s);
+*sipCppPtr = new std::string(PyUnicode_AsUTF8(sipPy));
 return 1;
  }
 #if PY_MAJOR_VERSION < 3


Would you be willing to apply that patch and release a new version to
Buster and Sid?


Cheers,
Shane


-- System Information:
Debian Release: 10.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-45-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python3-pykdl depends on:
ii  libc6 2.28-10
ii  libgcc1   1:8.3.0-6
ii  liborocos-kdl1.4  1.4.0-7+b1
ii  libpython3.7  3.7.3-2+deb10u1
ii  libstdc++68.3.0-6
ii  python3   3.7.3-1
ii  python3-sip   4.19.14+dfsg-2

python3-pykdl recommends no packages.

python3-pykdl suggests no packages.

-- no debconf information
Index: orocos-kdl-1.4.0/python_orocos_kdl/PyKDL/std_string.sip
===
--- orocos-kdl-1.4.0.orig/python_orocos_kdl/PyKDL/std_string.sip
+++ orocos-kdl-1.4.0/python_orocos_kdl/PyKDL/std_string.sip
@@ -48,9 +48,7 @@
  return 1;
  }
  if (PyUnicode_Check(sipPy)) {
-PyObject* s = PyUnicode_AsEncodedString(sipPy, "UTF-8", "");
-*sipCppPtr = new std::string(PyUnicode_AS_DATA(s));
-Py_DECREF(s);
+*sipCppPtr = new std::string(PyUnicode_AsUTF8(sipPy));
 return 1;
  }
 #if PY_MAJOR_VERSION < 3


Bug#955149: python3-pydocstyle: pydocstyle.config Deprecation warning during 'from collections import Set'

2020-03-27 Thread Shane Loretz
Package: python3-pydocstyle
Version: 2.1.1-1
Severity: minor
Tags: upstream

Dear Maintainer,

This package emits a DeprecationWarning during an import. The issue is known
upstream and has been fixed in this commit:
https://github.com/PyCQA/pydocstyle/pull/324/commits/5f216c27f09fa95647fa5496d5ed056772e009a5

Would you be willing to apply that commit here?

To reproduce:

python3 -Walways -c 'import pydocstyle.config'

Output:

/usr/lib/python3/dist-packages/pydocstyle/config.py:6: DeprecationWarning:
Using or importing the ABCs from 'collections' instead of from
'collections.abc' is deprecated since Python 3.3, and in 3.9 it will stop
working
  from collections import Set, namedtuple


Cheers,
Shane


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-91-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages python3-pydocstyle depends on:
ii  python3  3.8.2-2
ii  python3-six  1.14.0-2
ii  python3-snowballstemmer  2.0.0-1

python3-pydocstyle recommends no packages.

python3-pydocstyle suggests no packages.

-- no debconf information


Bug#955029: assimp: CMake Warning CMP0012 'if given arguments: "ON"' during 'find_package(assimp)'

2020-03-26 Thread Shane Loretz
Package: libassimp-dev
Version: 5.0.1~ds0-1
Severity: normal
File: assimp
Tags: upstream

Dear Maintainer,

This package emits a CMake warning during `find_package(assimp)`.
The bug is known upstream, and it has been fixed in this commit.
https://github.com/assimp/assimp/commit/6ac8279977c3a54118551e549d77329497116f66

Would you be willing to apply that commit here?

Instructions to reproduce:

mkdir -p /tmp/assimp_bug/build
cd /tmp/assimp_bug
printf "cmake_minimum_required(VERSION
3.0)\nproject(assimp_bug)\nfind_package(assimp)" > CMakeLists.txt
cd build
cmake ..

Output from the above:

-- The C compiler identification is GNU 9.3.0
-- The CXX compiler identification is GNU 9.3.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Warning (dev) at
/usr/lib/x86_64-linux-gnu/cmake/assimp-5.0/assimpTargets.cmake:54 (if):
  if given arguments:

"ON"

  An argument named "ON" appears in a conditional statement.  Policy CMP0012
  is not set: if() recognizes numbers and boolean constants.  Run "cmake
  --help-policy CMP0012" for policy details.  Use the cmake_policy command
to
  set the policy and suppress this warning.
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/assimp-5.0/assimp-config.cmake:1 (include)
  CMakeLists.txt:3 (find_package)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring done
-- Generating done
-- Build files have been written to: /tmp/assimp_bug/build


Cheers,
Shane

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-91-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages libassimp-dev:amd64 depends on:
ii  libassimp5  5.0.1~ds0-1

libassimp-dev:amd64 recommends no packages.

libassimp-dev:amd64 suggests no packages.

-- no debconf information


Bug#908169: libasio-dev: Asio on Linux stalls in epoll

2018-09-06 Thread Shane Loretz
Package: libasio-dev
Version: 1:1.10.8-1
Severity: normal

Dear Maintainer,

The version of libasio-dev in sid can deadlock if used in multiple threads.

https://github.com/chriskohlhoff/asio/issues/180

It looks like the bug is fixed in the version in experimental (1.12.0).
Is there something I can do to help migrate the version in experimental to
unstable?

The issue was also reported downstream.
https://bugs.launchpad.net/ubuntu/+source/asio/+bug/1771903

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-33-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

libasio-dev depends on no packages.

Versions of packages libasio-dev recommends:
ii  libboost-date-time-dev  1.62.0.1
ii  libboost-dev1.62.0.1
ii  libboost-regex-dev  1.62.0.1
ii  libssl-dev  1.1.1~~pre9-1

libasio-dev suggests no packages.

-- no debconf information


Bug#890364: pybind11-dev: Request migration to unstable

2018-02-14 Thread Shane Loretz
Hi Ghis,

Thank you!

What is the likelihood of migration before March 1st (date of ubuntu Bionic
Debian import freeze)?


Cheers,
Shane

On Wed, Feb 14, 2018 at 1:34 AM, Ghislain Vaillant <ghisv...@gmail.com>
wrote:

> Hi Shane, thanks for reaching out,
>
> On Wed, 14 Feb 2018 00:48:14 +0000 Shane Loretz <sloretz@openrobotics.o
> rg> wrote:
> > Would the maintainer be willing to migrate 2.2.1 from experimental to
> unstable? I'm a user of a distribution based on debian unstable. I have
> been using pybind11 from pip previously. The package in experimental
> appears to be working flawlessly for my usecase and has some nice new
> features not in the version currently in unstable.
>
> There are a few rdpends I have got to test first to guarantee a smooth
> upgrade. But yes, I intend to migrate the new version to unstable soon.
>
> Cheers,
> Ghis
>


Bug#890364: pybind11-dev: Request migration to unstable

2018-02-13 Thread Shane Loretz
Package: pybind11-dev
Version: 2.2.1-1
Severity: wishlist

Dear Maintainer,

Would the maintainer be willing to migrate 2.2.1 from experimental to unstable? 
I'm a user of a distribution based on debian unstable. I have been using 
pybind11 from pip previously. The package in experimental appears to be working 
flawlessly for my usecase and has some nice new features not in the version 
currently in unstable.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-26-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

pybind11-dev depends on no packages.

pybind11-dev recommends no packages.

Versions of packages pybind11-dev suggests:
pn  libeigen3-dev  
pn  pybind11-doc   

-- no debconf information