Ask Your Question

Porting visp release to trusty/indigo

asked 2014-04-03 20:55:19 -0600

Fabien Spindler gravatar image

I'm porting visp to indigo. According to it fails for trusty with the followin error (see ):

package ros-indigo-visp does not have dependency [ffmpeg]
Dependencies not satisfied for packages: ['ffmpeg']
Process leaked file descriptors. See for more information
Build step 'Execute shell' marked build as failure
Build step 'Groovy Postbuild' marked build as failure
Build step 'Groovy Postbuild' marked build as failure

In , ffmpeg dependency is now specific for trusty. We have:

     trusty: [libavcodec-dev, libavformat-dev, libavutil-dev, libswscale-dev]

I can't understand wy I get this error "Dependencies not satisfied for packages: ['ffmpeg']". It should not happen as ffmpeg is not a dep for trusty. I'm wrong. Is there a problem with the build farm.

Moreover I'm also surprised with the last lines of the log:

Build step 'Groovy Postbuild' marked build as failure

The build is for indigo. Wy does it mention groovy ?

edit retag flag offensive close merge delete


demmeln gravatar image demmeln  ( 2014-04-04 01:49:43 -0600 )edit
William gravatar image William  ( 2014-04-04 07:27:24 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2014-04-04 08:27:56 -0600

tfoote gravatar image

You need to re bloom the package now that the rosdep rules have been updated. The debian metadata is generated by bloom using the rosdep rules. You can just rerun bloom to generate (no upstream release required) new sourcedeb with the updated rosdep mappings.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2014-04-03 20:55:19 -0600

Seen: 162 times

Last updated: Apr 04 '14