-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[debian] Fatal Python error: UNREF invalid object #779
Comments
Here the backtrace
|
This is strange it seems to be openssl related. |
Maybe you can try Python3 to build the documentation? |
On Sat, 03 Feb 2018 04:21:35 -0800 picca ***@***.***> wrote:
Hello,
while preparing the official Debian packages, I get this error message on a stretch machine.
```
I: pybuild base:184: cd doc && PYTHONPATH=/home/picca/Debian/pyfai/pyfai/.pybuild/pythonX.Y-dbg_2.7/build http_proxy='127.0.0.1:9' python2.7-dbg -m sphinx -N -bhtml source build/html
Running Sphinx v1.4.9
Fatal Python error: UNREF invalid object
Aborted
E: pybuild pybuild:283: build: plugin custom failed with: exit code=134: cd doc && PYTHONPATH=/home/picca/Debian/pyfai/pyfai/.pybuild/pythonX.Y-dbg_2.7/build http_proxy='127.0.0.1:9' python2.7-dbg -m sphinx -N -bhtml source build/html
dh_auto_build: pybuild --build -i python{version}-dbg -p 2.7 returned exit code 13
debian/rules:45 : la recette pour la cible « override_dh_sphinxdoc » a échouée
make[1]: *** [override_dh_sphinxdoc] Erreur 25
```
???
I don't understand why the doc is built using the python-dbg version ... I have never tested.
On debian9 we stopped building the dbg packages, instead we use the
"symbols-packages" provided: it speeds-up the build and is enough to
debug with GDB. Is there still a valid reson to build in full debug mode ?
|
I build the doc with all version of the python available, it allows to catch more errors during the build, process. |
On Tue, 06 Feb 2018 23:47:34 -0800 picca ***@***.***> wrote:
I build the doc with all version of the python available, it allows to catch more errors during the build, process.
The build and test matrix is already wide and complicated. Adding a
different set of compiler options for every single library make it even
more complicated.
Moreover the -dbgsym package is enough for using gdb for most of out debugging.
I removed dbg packaging since debian9 in our tools.
Do you really consider it is of prime importance to build the doc with the python-dbg ?
Cheers,
…--
Jérôme Kieffer
tel +33 476 882 445
|
Hello,
while preparing the official Debian packages, I get this error message on a stretch machine.
???
The text was updated successfully, but these errors were encountered: