I think Jack's right. It's rejecting the upload with this error: No Description field in /var/www/repos/building/tmp/ros-fuerte-rail-gazebo_0.0.11-s1354602716~lucid_i386.deb's control file! There have been errors! Error: post upload command failed. Tully On Tue, Dec 4, 2012 at 9:13 AM, Jack O'Quin wrote: > Just a guess: might it be complaining about the empty description field in > your stack.xml? > > > On Tue, Dec 4, 2012 at 7:49 AM, Toris, Russell Charles wrote: > >> Good morning all- >> >> The other week we released a whole slew of our ROS stacks as Ubuntu >> packages and one of the packages continues to fail on Jenkins and I can't >> seem to find out what the issue is. Funny enough, the one package that is >> failing is the one that doesn't even build any code; it is our Gazebo stack >> with some models and world files we have developed ( >> http://www.ros.org/wiki/rail_gazebo). I have listed simulator_gazebo as >> a dependency and that is all. From what I can tell from the Jenkins output, >> I see no problem on the ROS end ([ rosmake ] Built 54 packages with 0 >> failures) but rather during the deb package build? It fails right at the >> end. Here is an example output (all architectures fail): >> >> >> http://jenkins.willowgarage.com:8080/job/ros-fuerte-rail-gazebo_binarydeb_lucid_i386/17/consoleFull >> >> The package has no problems at all building on the per-release server. Is >> there something I am overlooking or is there some problem out of my control? >> >> Russell >> >> >> -- >> Russell Toris >> Graduate Student | WPI Department of Computer Science >> rctoris@wpi.edu | http://users.wpi.edu/~rctoris/ >> >> >> _______________________________________________ >> Ros-release mailing list >> Ros-release@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-release >> > > > > -- > joq > > _______________________________________________ > Ros-release mailing list > Ros-release@code.ros.org > https://code.ros.org/mailman/listinfo/ros-release > > -- Tully Foote tfoote@willowgarage.com (650) 475-2827