Depdencies contained inside ffmpeg_image_transport.repos are always fetched at master.

[Tantenfisch]

The file ffmpeg_image_transport.repos that is used to fetch the dependencies that need to be built along side ffmpeg_image_transport always fetches the dependencies at master.

So if you fetch an older tag of ffmpeg_image_transport (e.g. 2.0.3) and install from source, a non matching (the latest) version of the dependencies will be used when building. This leads to incompatibilities during build or runtime.

[berndpfrommer]

True. Is there a way to automatically update the repos file such that version corresponds with the current one? I don't actually generate the tags, somehow bloom does that during release, but release happens later, so when I commit the repos file, I'd somehow need to know what the tag version will be. Of course I have control over the version number, but it's another step that I can/will mess up occasionally. So maybe it would be better to go by the current commit rather than the version.