I had the same response the first time I encountered a missing rosdep key for Fedora. Since there are now two of us that have had this issue, it's probably worth considering a better error message for that scenario; probably something indicating that we can skip rosdep generation for platforms where the rosdep key is missing. -Austin On 03/06/2015 11:12 AM, Michael Ferguson wrote: > My bad -- I didn't bother to hit "N" once I got to the failed rosdep > key -- I expected it would then fail afterwards -- but it gives me the > option to skip Fedora. Huh. Sorry for the noise! > > -Fergs > > On Fri, Mar 6, 2015 at 11:01 AM, William Woodall > > wrote: > > During the release process it should check if all Fedora keys are > available before starting the rpm generation, if they are not it > will skip it. > > If this is not happening for you, then I think it might be a > regression. > > On Thu, Mar 5, 2015 at 11:51 PM, Michael Ferguson > > wrote: > > I'm trying to release a package which depends on ceres-solver, > which is packaged for Ubuntu by way of my PPA, but is not > available on Fedora. What is our standard practice for this? > Is there a way to force bloom to skip Fedora or do I have to > put a fake key into the rosdep? > > Thanks, > -Fergs > > _______________________________________________ > ros-release mailing list > ros-release@lists.ros.org > http://lists.ros.org/mailman/listinfo/ros-release > > > > > -- > William Woodall > ROS Development Team > william@osrfoundation.org > http://wjwwood.io/ > > _______________________________________________ > ros-release mailing list > ros-release@lists.ros.org > http://lists.ros.org/mailman/listinfo/ros-release > > > > > _______________________________________________ > ros-release mailing list > ros-release@lists.ros.org > http://lists.ros.org/mailman/listinfo/ros-release _______________________________________________ ros-release mailing list ros-release@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-release