Bug#823140: RFS: caffe/1.0.0~rc3-1 -- a deep learning framework [ITP]
Hi Lumin, Ghislain
>An update to this, according to
>https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html
>Even if I want to add some testsuite for python-caffe, I don't need
>to add those runtime deps in control, I can add them in tests/control
>instead, by adding "Depends" field that supprted by d/tests/control.
true, I agree
>OpenCV 3.0 can yield python3-opencv package with just a small patch,>which is provided by a user in an opencv debian bug.
>Protobuf might be similar.
that would be awesome
>And I agree, on behalf of the release team I should make python3-*
>packages in the initial upload. I decide to bump python from
>2 to 3. python3-caffe can be built easily with packages outside
>of Debian archive. One of the unapplied patches I removed
>is for python3->python2 downgrade reversal.
>opencv and protobuf is still on the way of 2 to 3, in Debian.
yes, so lets go for python2
(or maybe lets go for no python bindings?)
>CPU version is safe. and
>no need to worry about GCC and CUDA, the source of trouble
>is the compatibility between NVCC and GCC.
>That's exactly why I'm now a maintainer of CUDA ............
>I helped the 6.5->7.0 and 7.0->7.5 bump of CUDA, and the NVCC
>usability got into a better situation, where caffe-cuda
>survived.
wonderful!
>CUDA 8.0 is comming soon, if NVCC 8.x fails to work with GCC-6,
>we just lock build-dep at GCC-5. Safe too.
wonderful
>Actually I guess CUDA 8.5 release date is prior to stretch freeze.
even better
>I'm not familiar with that package, and I think if I'm going
>to help caffe's recursive dependency package maintainers,
>I intend to first have a look at opencv or protobuf.
I can do scikit-image
>Stretch freeze is Q1 2017, I'm afraid whether caffe can
>be uploaded into stretch in time.
>
>* python3-opencv upload
>* python3-protobuf upload
I'll wait for some news from you.
>* python3-skimage NON-DFSG bugs
I'll do it.
Ghislain, do you think we can upload it right now?
even if it doesn't migrate to testing, at least we will have the new
queue trip cleared, and then we can fix bugs on reverse-dependencies.
G.
Reply to: