bloom-generate Rosdep can't resolve key
I have been poking around with bloom-generate to generate rosdebian packages of a few custom packages and I came across a situation that has been asked here several times, but I seem to find no solution:
I have a workspace with two packages, my_package and my_package_msgs.
Executing bloom-generate rosdebian on my_package will yield the following result:
==> Generating debs for ubuntu:xenial for package(s) ['my_package']
No homepage set, defaulting to ''
Could not resolve rosdep key 'my_package_msgs'
Try to resolve the problem with rosdep and then continue.
Continue [Y/n]?
What bugs me is that according to Dirk's answer on this question: https://answers.ros.org/question/5019... newer versions of bloom should consider all packages from the same workspace to be "ok". And I don't know if I dreamt it or what, but I would swear that it worked in one of my early tests (unfortunately those tests where on a docker container that no longer exists)
I have created a toy repo with instructions to test the situation: https://github.com/MartinPeris/ros-bl...
Anyone could give me any pointers?
Hello, just chiming in cause I'm seeing the same problem currently but I still have not found a solution. Did you manage to fix your issue somehow? Perhaps through the use of buildfarm?
Hey there, just encountered this issue as well. Any ideas two + years later?
Nope, let me know if you find something out. I ended up creating a custom rosdep.yaml with something like this: for i in
catkin list -u; do echo -e "$$i:\n ubuntu: [ros-kinetic-echo $$i | sed 's/_/-/g']\n" >> rosdep.yaml; done'catkin list -u' gives you the list of packages in your workspace in "dependency order". So then I iterated over the package list in order, bloomed each package and installed in in the system (I work on a docker container, so it wouldn't interfere with my host machine).
Very drity and I don't recommend it.