Re: Bug#902516: python-matplotlib-venn: FTBFS in buster/sid (failing tests)
On Thursday, 5 July 2018 08:09:50 AEST Andreas Tille wrote: > Control: tags -1 help > > Hi, > > I can confirm this problem in a pbuilder environment. Unfortunately I > have no idea about the cause of the issue nor how to fix it. Any hint > from the Debian Python team? Looks a lot like at least some of the tests are failing with: https://wiki.debian.org/ContinuousIntegration/TriagingTips/numpy-1.14-doctests cheers Stuart -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Re: Anyone interested in Tensorflow packaging? Makefile available now.
Hello Lumin, just my 2 cts. Cmake is usually crossplatform. So it should not be too difficult to adopt it for Linux. It would be much better as a set of hardcoded makefiles which can be a nightmare in a long perspective. > * abseil [missing] I have started to prepare a package of it [1]. But there are a couple of principal questions which need to be discussed with upstream. [1] https://salsa.debian.org/debian/abseil Regards Anton 2018-07-05 16:05 GMT+02:00 Lumin : > Hello d-Science and d-Python team, > > Long time ago, TensorFlow packaging was blocked by bazel, > a google's java-based building system which is hard to harness. > At that time, cmake build was available but it's written for > windows. > > However, by chance I discovered that tensorflow now ships > a set of makefiles[1], which is explicitly saying "support Ubuntu". > That means packaging TensorFlow is now viable, as long as we patch > the build system to prevent it from downloading tarballs. > > If you are looking for things to do, or interested in machine learning > or deep learning applications, you might want to have a look at it. > > However, I'm not working on it because: > 1. I'm a bit overload these days, working on the Julia package. > 2. unfortunately I don't like TensorFlow. I like it's main > competitor -- PyTorch. > But if someone is going to do something about it, I'd be happy to help. > > > Let's have a look at the dependencies: > > * eigen [OK] > * gemmlowp [OK, maintained by me] > * googletest [OK] > * nsync [missing] > * protobuf [OK] > * re2 [OK] > * fft2d [missing] > * abseil [missing] > * cub [missing, NVIDIA's BSD-3-clause software that depends on CUDA] > We don't need this pile of code when compiling CPU-only tensorflow. > > If someone is going to hack the makefiles, I'd suggest that, > try building a CPU-only version first. > > Best, > > > [1] > https://salsa.debian.org/science-team/tensorflow/blob/master/tensorflow/contrib/makefile/build_all_linux.sh > [2] > https://salsa.debian.org/science-team/tensorflow/blob/master/tensorflow/contrib/makefile/download_dependencies.sh >
Anyone interested in Tensorflow packaging? Makefile available now.
Hello d-Science and d-Python team, Long time ago, TensorFlow packaging was blocked by bazel, a google's java-based building system which is hard to harness. At that time, cmake build was available but it's written for windows. However, by chance I discovered that tensorflow now ships a set of makefiles[1], which is explicitly saying "support Ubuntu". That means packaging TensorFlow is now viable, as long as we patch the build system to prevent it from downloading tarballs. If you are looking for things to do, or interested in machine learning or deep learning applications, you might want to have a look at it. However, I'm not working on it because: 1. I'm a bit overload these days, working on the Julia package. 2. unfortunately I don't like TensorFlow. I like it's main competitor -- PyTorch. But if someone is going to do something about it, I'd be happy to help. Let's have a look at the dependencies: * eigen [OK] * gemmlowp [OK, maintained by me] * googletest [OK] * nsync [missing] * protobuf [OK] * re2 [OK] * fft2d [missing] * abseil [missing] * cub [missing, NVIDIA's BSD-3-clause software that depends on CUDA] We don't need this pile of code when compiling CPU-only tensorflow. If someone is going to hack the makefiles, I'd suggest that, try building a CPU-only version first. Best, [1] https://salsa.debian.org/science-team/tensorflow/blob/master/tensorflow/contrib/makefile/build_all_linux.sh [2] https://salsa.debian.org/science-team/tensorflow/blob/master/tensorflow/contrib/makefile/download_dependencies.sh
Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]
Great! thanks for you help! In next updates I will contact you. Thanks Regards El jue., 5 de jul. de 2018 a la(s) 07:33, Dmitry Shachnev < mity...@debian.org> escribió: > On Wed, Jul 04, 2018 at 09:50:51PM -0300, eamanu15 wrote: > > Hello Dmitry, > > > > I just pushed the update the package to Salsa. I pushed the PyGithub_1.40 > > version. > > Thanks! Uploaded after fixing debian/changelog. > > -- > Dmitry Shachnev > -- Arias Emmanuel https://www.linkedin.com/in/emmanuel-arias-437a6a8a http://eamanu.com
Re: Add me to salsa
Hi, ne 1. 7. 2018 v 14:45 odesílatel Bastien ROUCARIES < roucaries.bast...@gmail.com> napsal: > I am the maintainer of python magick that I maintained formally under > alioth > what is your salsa username please? -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Bug#900368: RFS: pygithub/1.40a3-1 [ITP]
On Wed, Jul 04, 2018 at 09:50:51PM -0300, eamanu15 wrote: > Hello Dmitry, > > I just pushed the update the package to Salsa. I pushed the PyGithub_1.40 > version. Thanks! Uploaded after fixing debian/changelog. -- Dmitry Shachnev signature.asc Description: PGP signature
[Help] Re: Bug#902516: python-matplotlib-venn: FTBFS in buster/sid (failing tests)
Control: tags -1 help
Hi,
I can confirm this problem in a pbuilder environment. Unfortunately I
have no idea about the cause of the issue nor how to fix it. Any hint
from the Debian Python team?
Kind regards
Andreas.
On Wed, Jun 27, 2018 at 12:50:32PM +, Santiago Vila wrote:
> Package: src:python-matplotlib-venn
> Version: 0.11.5-4
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster with "dpkg-buildpackage -A"
> but it failed:
>
>
> [...]
> debian/rules build-indep
> dh build-indep --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -i -O--buildsystem=pybuild
>dh_autoreconf -i -O--buildsystem=pybuild
>dh_auto_configure -i -O--buildsystem=pybuild
> pybuild --configure --test-pytest -i python{version} -p 2.7
> I: pybuild base:217: python2.7 setup.py config
> running config
> pybuild --configure --test-pytest -i python{version} -p 3.6
> I: pybuild base:217: python3.6 setup.py config
> running config
>dh_auto_build -i -O--buildsystem=pybuild
> pybuild --build --test-pytest -i python{version} -p 2.7
>
> [... snipped ...]
>
> File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 719, in
> _perform_collect
> self.items.extend(self.genitems(node))
> File "/usr/lib/python2.7/dist-packages/_pytest/main.py", line 860, in
> genitems
> rep = collect_one_node(node)
> File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", line 502, in
> collect_one_node
> rep = ihook.pytest_make_collect_report(collector=collector)
> File "/usr/lib/python2.7/dist-packages/pluggy/__init__.py", line 617, in
> __call__
> return self._hookexec(self, self._nonwrappers + self._wrappers, kwargs)
> File "/usr/lib/python2.7/dist-packages/pluggy/__init__.py", line 222, in
> _hookexec
> return self._inner_hookexec(hook, methods, kwargs)
> File "/usr/lib/python2.7/dist-packages/pluggy/__init__.py", line 216, in
>
> firstresult=hook.spec_opts.get('firstresult'),
> File "/usr/lib/python2.7/dist-packages/pluggy/callers.py", line 180, in
> _multicall
> res = hook_impl.function(*args)
> File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", line 369, in
> pytest_make_collect_report
> 'collect')
> File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", line 189, in
> __init__
> self.result = func()
> File "/usr/lib/python2.7/dist-packages/_pytest/runner.py", line 368, in
>
> lambda: list(collector.collect()),
> File "/usr/lib/python2.7/dist-packages/_pytest/doctest.py", line 217, in
> collect
> module = self.fspath.pyimport()
> File "/usr/lib/python2.7/dist-packages/py/_path/local.py", line 668, in
> pyimport
> __import__(modname)
> File
> "/<>/.pybuild/cpython2_2.7_matplotlib-venn/build/matplotlib_venn/__init__.py",
> line 55, in
> from matplotlib_venn._venn2 import venn2, venn2_circles
> File
> "/<>/.pybuild/cpython2_2.7_matplotlib-venn/build/matplotlib_venn/_venn2.py",
> line 22, in
> from matplotlib.pyplot import gca
> File "/usr/lib/python2.7/dist-packages/matplotlib/pyplot.py", line 71, in
>
> from matplotlib.backends import pylab_setup
> File "/usr/lib/python2.7/dist-packages/matplotlib/backends/__init__.py",
> line 16, in
> line for line in traceback.format_stack()
>
>
> '''
>
> -- Docs: http://doc.pytest.org/en/latest/warnings.html
> === 15 failed, 34 passed, 3 warnings in 0.60 seconds
> ===
> E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: cd
> /<>/.pybuild/cpython2_2.7_matplotlib-venn/build; python2.7 -m
> pytest
> dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
> exit code 13
> debian/rules:10: recipe for target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Error 25
> make[1]: Leaving directory '/<>'
> debian/rules:7: recipe for target 'build-indep' failed
> make: *** [build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
> status 2
>
>
> The above is how the build ends in my autobuilder and it's not
> necessarily the relevant part.
>
> The failure is not, however, related to using dpkg-buildpackage -A,
> as it also fails in reproducible builds:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-matplotlib-venn.html
>
> If this is really a bug in one of the build-depends, please use reassign and
> affects,
> so that this is still visible in the page for this package.
>
> Thanks.
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
>
