[ros-release] Releasing when Fedora rosdep key is not available?

Jack O'Quin jack.oquin at gmail.com
Fri Mar 6 20:15:02 UTC 2015

On Fri, Mar 6, 2015 at 1:29 PM, William Woodall <william at osrfoundation.org>

> Yeah, the message might could be better. I don't have time to spend on it
> right now, but if you guys open an issue I might look at it next time I'm
> doing bloom stuff.
> I think the reason the message isn't more specific is that the same check
> is used for Debian generation and it will not allow you to skip. So the
> logic to offer the skip comes after failing to get all of the keys. It
> might require a structural change.

I initially found those messages somewhat confusing, but still very
helpful, because bloom kept me from making a mess of releasing to Jade with
some rosdeps not yet defined for Utopic or Vivid.

Once I figured out what was going on, it was great. I left the
bloom-release terminal asking whether to try again, added the missing
rosdeps, then told bloom to retry after they were merged.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20150306/cae2af09/attachment.html>

More information about the ros-release mailing list