It's not suppose to be a problem anymore, what version of bloom are you using? See:

"Users can now skip rpm generation if rosdep keys are missing for fedora only."

https://github.com/ros-infrastructure/bloom/blob/master/CHANGELOG.rst#0512-2014-09-24-152816--0700


On Wed, Dec 10, 2014 at 1:00 PM, Austin Hendrix <legotown@aol.com> wrote:
I'm trying to release the diagnostics package, and I'm running into rosdep issues because one of the rosdep keys that I depend on (`libsensors4-dev`) isn't defined for Fedora heisenbug.

I don't have a Fedora machine or much experience with it, so it's difficult for me to attempt to provide a rosdep key. I've tried searching the fedora package database ( https://admin.fedoraproject.org/pkgdb/ ) for `sensor`, `sensors`, `lm-sensors` and `libsensors` without any results.

What is the procedure for releasing a package in this situation? Since diagnostics is a core package and part of the desktop release, I'd rather not release an updated version without fedora support.

Is there someone in the Fedora packaging community who can provide the proper rosdep key?

Thanks,
-Austin
_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release



--
William Woodall
ROS Development Team
william@osrfoundation.org
http://wjwwood.io/