[ros-release] Releasing when Fedora rosdep key is not available?
mfergs7 at gmail.com
Fri Mar 6 19:12:50 UTC 2015
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!
On Fri, Mar 6, 2015 at 11:01 AM, William Woodall <william at osrfoundation.org>
> 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
> 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 <mfergs7 at gmail.com>
>> 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?
>> ros-release mailing list
>> ros-release at lists.ros.org
> William Woodall
> ROS Development Team
> william at osrfoundation.org
> ros-release mailing list
> ros-release at lists.ros.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ros-release