Package Details: ros-indigo-vision-opencv 1.11.12-1

Git Clone URL: (read-only, click to copy)
Package Base: ros-indigo-vision-opencv
Description: ROS - Packages for interfacing ROS with OpenCV, a library of programming functions for real time computer vision.
Upstream URL:
Licenses: BSD
Submitter: bchretien
Maintainer: None
Last Packager: bchretien
Votes: 1
Popularity: 0.000000
First Submitted: 2014-06-07 17:14
Last Updated: 2016-03-24 02:49

Latest Comments

tsirif commented on 2016-02-15 03:27

@bchretien: I keep most recent source tarballs and repos of things i've installed from aur under the same directory. I use pacaur as a manager.

Thank you for your consideration

bchretien commented on 2016-02-15 00:48

@tsirif: thanks for the recommendation. For that kind of general issue, you can post it on the metaproject that generates the PKGBUILDs:

Is that because your AUR manager downloads all the sources in the same common directory? I'm using yaourt, and tarballs are downloaded to /tmp/yaourt-tmp-${USER}/aur-${pkgname}, so I don't really see how such clashes could happen.

tsirif commented on 2016-02-14 18:44

Hello there! In the last update to 1.11.11-0 of vision_opencv, opencv-apps, image-geometry, cv-bridge indigo source packages are all being downloaded as 1.11.11-0.tar.gz, so aur manager cannot differentiate between them and sha256sums are also different. Could you add '"${_dir}.tar.gz":: ' before the url string of source package in PKGBUILDs? (_dir is the var that you define at the line above)

Same thing happens in ros-indigo-pr2_description.

deepsoul commented on 2014-12-16 09:14

Thanks for your reply, bchretien. I was fooled by the fact that the upstream repo contains cv-bridge and image-geometry too, but these are separate AUR packages. And I was unsure who controls the github/ros-gbp/... repo used in the PKGBUILD.

bchretien commented on 2014-12-15 18:28

@deepsoul: note that here we only deal with packaging, the content of these packages depends on what they do upstream. For vision_opencv, if you check the source (, you'll see that this is merely a metapackage, so there should not be any content in there.

bchretien commented on 2014-12-15 17:33

@deepsoul: there was a release yesterday, so I'll update desktop_full (including this package) ASAP.

deepsoul commented on 2014-12-15 17:28

This builds an almost-empty package, because the github repository used removes everything except the metadata from the upstream version. Would it be possible to use the latest release from the upstream repository ?