Package Details: caffe2-cpu 0.8.2.pytorch.0.4.0-4

Git Clone URL: (read-only)
Package Base: caffe2-cpu
Description: A new lightweight, modular, and scalable deep learning framework (cpu only)
Upstream URL:
Keywords: ai artificial intelligence
Licenses: BSD
Conflicts: caffe, caffe-cpu, caffe-cpu-git, caffe-git, caffe2, caffe2-cpu-git, caffe2-git
Submitter: dbermond
Maintainer: dbermond
Last Packager: dbermond
Votes: 0
Popularity: 0.000000
First Submitted: 2017-04-29 16:21
Last Updated: 2018-06-03 15:55

Required by (0)

Sources (26)

Latest Comments

dbermond commented on 2018-04-30 19:27

PyTorch released its first stable version containing Caffe2.

Package updated to caffe2 0.8.2 from pytorch stable 0.4.0. Note that this package does not contain pytorch, but caffe2 only.

dbermond commented on 2018-04-23 18:01

I have backported a patch to enable building with the newest version of 'gcc' from the official repositories (currently gcc7). Package is now building fine with gcc7.

dbermond commented on 2018-01-26 14:25

@ricefan123 Thank you for reporting this. Now fixed.

ricefan123 commented on 2018-01-26 14:06

thirdparty-protobuf-3.1.0.tar.gz check sum failed. Please fix it. Thank you.

dbermond commented on 2017-08-22 20:20

Thank you for reporting this. I can reproduce the issue.
It seems that the caffe2 python dependencies have slightly changed from when I firstly checked it.
I will be updating this package and the other caffe2 packages on the AUR to fix this issue.

wangqr commented on 2017-08-22 08:34

After installed this package I tried to import it, but get the following error:

Python 2.7.13 (default, Jul 21 2017, 03:24:34)
[GCC 7.1.1 20170630] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from caffe2.python import workspace, model_helper
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/caffe2/python/", line 14, i n <module>
from past.builtins import basestring
ImportError: No module named past.builtins

Installing python2-future resolves the issue.