This error comes up when you don't have the ca-certificates up to date. Likely you can work around this by adding the ca-certificates package as a dependency or by disabling strict checking as Dirk mentions. I think on the other platforms you must be getting luck that the certificates are being pulled in by transitive dependencies. However it is a build dependency and as such should be listed. Tully On Sat, Apr 12, 2014 at 10:20 AM, Dirk Thomas wrote: > Hi Isaac, > > the error message could either be related to the reason you described > (which is less likely since the used git seems to be newer) or it could be > the case that the cert can not be verified. > For the second reason you could try to call git with GIT_SSL_NO_VERIFY / > http.sslVerify being disabled. > > This is just a guess though. > It is not likely that we will look into the problem more since your > package is trying to fetch external resources during the configure phase. > > Despite that I might repeat myself: this is highly unrecommended behavior > (as mentioned to you several times before). > You might seriously reconsider your workflow - a package following the > recommendations will not have the problem in the first place. > > - Dirk > > > On Sat, Apr 12, 2014 at 6:14 AM, Isaac Isao Saito < > iisaito@opensource-robotics.tokyo.jp> wrote: > >> Hello releasers, >> >> I need a help. A package I'm maintaining (hrpsys_ros_bridge) has been >> failing to build since 2 weeks ago ONLY ON Groovy-Quantal (other >> combination seems to be fine in G, H). >> >> # And I think the failure of this is blocking the next Groovy sync batch). >> >> >> http://jenkins.ros.org/view/GbinQ64/job/ros-groovy-hrpsys-ros-bridge_binarydeb_quantal_amd64/119/consoleFull >> >> -- catkin 0.5.86 >> -- Using these message generators: gencpp;genlisp;genpy >> error: Problem with the SSL CA cert (path? access rights?) while >> accessing https://github.com/PR2/pr2_controllers.git/info/refs >> fatal: HTTP request failed >> >> Tracking down the link in the error message, ultimately I get the >> following link that was posted in 2011 and says version of git is the >> problem. >> >> https://github.com/blog/809-git-dumb-http-transport-to-be-turned-off-in-90-days >> >> However, git is new enough in the error log from the buildfarm. >> >> Setting up git (1:1.7.10.4-1ubuntu1) ... >> >> Any idea is appreciated. >> Isaac >> >> -- >> !Happy opensource robotics! >> >> Isaac Isao Saito (齋藤功) >> Co-founder, Software Engineer >> TORK (Tokyo Opensource Robotics Kyokai Association, 東京オープンソースロボティクス協会) >> http://opensource-robotics.tokyo.jp >> _______________________________________________ >> ros-release mailing list >> ros-release@code.ros.org >> http://lists.ros.org/mailman/listinfo/ros-release >> > > > _______________________________________________ > ros-release mailing list > ros-release@code.ros.org > http://lists.ros.org/mailman/listinfo/ros-release > >