<p>Hi Stephane, </p>
<p>We gate pushing into the main repo for quality purposes.  (If an improper release is made and it breaks half the packages in the repository we don't want to push the repo public with half the packages missing).  We also do it to prevent significant churn on downloads for our users. (A full release requires each computer updating to download over a GB of data.  It's not bad on our local network, but it is a significant burden when you consider that there are thousands of computers updating from the repo regularly. ) </p>


<p>Your issue with gps_umd is not related to manual syncing, as far as I can tell it's well up to date.  Up through the shadow repository all debs are automatically synced when built into our testing repo (ros-shadow-fixed if you're looking at the names)   It looks like gps_umd is not compiling on precise. <a href="http://www.ros.org/debbuild/fuerte.html" target="_blank">http://www.ros.org/debbuild/fuerte.html</a> Note that there are two zeros in the box.  Saying that there's not a version in shadow-fixed or public from the last sync.  And with it red now, I expect that the build is broken. (It's likely that it needs an update for rosdeps) </p>

<p>Yes, so looking it up, in the last ALL build gps_umd is failing: <a href="http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-amd64/306/consoleText">http://build.willowgarage.com/job/debbuild-build-debs-fuerte-precise-amd64/306/consoleText</a> </p>


<p>Tully</p>
<div class="gmail_quote">Build failure exerpt: </div><div class="gmail_quote"><br></div><div class="gmail_quote"><pre style="word-wrap:break-word;white-space:pre-wrap">{-------------------------------------------------------------------------------
  make[2]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client'
  mkdir -p bin
  cd build && cmake -Wdev -DCMAKE_TOOLCHAIN_FILE=`rospack find rosbuild`/rostoolchain.cmake  ..
  -- The C compiler identification is GNU
  -- The CXX compiler identification is GNU
  -- Check for working C compiler: /usr/bin/gcc
  -- Check for working C compiler: /usr/bin/gcc -- works
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working CXX compiler: /usr/bin/c++
  -- Check for working CXX compiler: /usr/bin/c++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Found PythonInterp: /usr/bin/python (found version "2.7.3")
  [rosbuild] Building package gpsd_client
  [rosbuild] Cached build flags older than manifests; calling rospack to get flags
  [rosbuild] Including /opt/ros/fuerte/share/rospy/rosbuild/rospy.cmake
  [rosbuild] Including /opt/ros/fuerte/share/roslisp/rosbuild/roslisp.cmake
  [rosbuild] Including /opt/ros/fuerte/share/roscpp/rosbuild/roscpp.cmake
  -- Configuring done
  -- Generating done
  -- Build files have been written to: /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build
  cd build && make -l16
  make[3]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  make[4]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  make[5]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  Scanning dependencies of target rospack_genmsg_libexe
  make[5]: Leaving directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  [  0%] Built target rospack_genmsg_libexe
  make[5]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  Scanning dependencies of target rosbuild_precompile
  make[5]: Leaving directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  [  0%] Built target rosbuild_precompile
  make[5]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  Scanning dependencies of target gpsd_client
  make[5]: Leaving directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  make[5]: Entering directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  [100%] Building CXX object CMakeFiles/gpsd_client.dir/src/client.o
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp:38:2: error: #error "gpsd_client only supports gpsd API versions 3 and 4"
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp: In constructor 'GPSDClient::GPSDClient()':
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp:13:32: error: no matching function for call to 'gpsmm::gpsmm()'
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp:13:32: note: candidates are:
  /usr/include/libgpsmm.h:29:3: note: gpsmm::gpsmm(const char*, const char*)
  /usr/include/libgpsmm.h:29:3: note:   candidate expects 2 arguments, 0 provided
  /usr/include/libgpsmm.h:15:7: note: gpsmm::gpsmm(const gpsmm&)
  /usr/include/libgpsmm.h:15:7: note:   candidate expects 1 argument, 0 provided
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp: In member function 'bool GPSDClient::start()':
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp:27:30: error: 'class gpsmm' has no member named 'open'
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp: In member function 'void GPSDClient::step()':
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp:46:27: error: 'class gpsmm' has no member named 'poll'
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp: In member function 'void GPSDClient::process_data_gps(gps_data_t*)':
  /tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/src/client.cpp:95:35: error: 'SATS_VISIBLE' was not declared in this scope
  make[5]: *** [CMakeFiles/gpsd_client.dir/src/client.o] Error 1
  make[5]: Leaving directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  make[4]: *** [CMakeFiles/gpsd_client.dir/all] Error 2
  make[4]: Leaving directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  make[3]: *** [all] Error 2
  make[3]: Leaving directory `/tmp/buildd/ros-fuerte-gps-umd-0.1.2/debian/ros-fuerte-gps-umd/opt/ros/fuerte/stacks/gps_umd/gpsd_client/build'
  make[2]: *** [all] Error 2
-------------------------------------------------------------------------------}</pre></div><div class="gmail_quote"><br></div><div class="gmail_quote">On May 14, 2012 11:42 AM, "Stéphane Magnenat" <<a href="mailto:stephane.magnenat@mavt.ethz.ch" target="_blank">stephane.magnenat@mavt.ethz.ch</a>> wrote:<br type="attribution">

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Hello,<br>
<br>
As far as I have understood, the current build process puts deb files into a shadow repository and requires a manual operation to make these files available to everyone in the main repository. I do not understand the rationale of this, as it slows down the release process considerably. For instance, we wish to release our new ethzasl_xsens_driver stack that depends on gps_umd, whose debs have not been published yet on some fuerte targets.<br>




<br>
Do you have any plan to streamline this process or advise on how to efficiently work around this bottleneck?<br>
<br>
Thank you, kind regards,<br>
<br>
Stéphane<br>
<br>
-- <br>
Dr Stéphane Magnenat<br>
<a href="http://stephane.magnenat.net" target="_blank">http://stephane.magnenat.net</a><br>
______________________________<u></u>_________________<br>
Ros-release mailing list<br>
<a href="mailto:Ros-release@code.ros.org" target="_blank">Ros-release@code.ros.org</a><br>
<a href="https://code.ros.org/mailman/listinfo/ros-release" target="_blank">https://code.ros.org/mailman/<u></u>listinfo/ros-release</a><br>
</blockquote></div>