[ros-release] Releasing when Fedora rosdep key is not available?
mfergs7 at gmail.com
Fri Mar 6 20:24:18 UTC 2015
William, the messages are probably fine -- to be honest, I felt kind of
stupid for posting here before actually trying to see if would continue
with a "No" answer. Thanks for all the new features going into the tool.
Jack, I concur, I have found that the new "precheck" is a huge time saver
as I've been releasing into Jade.
On Fri, Mar 6, 2015 at 12:15 PM, Jack O'Quin <jack.oquin at gmail.com> wrote:
> On Fri, Mar 6, 2015 at 1:29 PM, William Woodall <william at osrfoundation.org
> > wrote:
>> 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.
> ros-release mailing list
> ros-release at lists.ros.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ros-release