I've seen changes in the way bloom formats its release repositories. When dealing with the previous layout it seems to upgrade automatically.But, I am trying to release image_common, which has not been released for about four months. Its GBP repo looks strange, it has a copy of the code in "master" and a tracks.yaml file in the "bloom" branch. I know the format has changed since then, but bloom does not seem to be able to find the tracks.Any suggestions for how to get this repo working with the current bloom?joq@vision-4:image_common-release$ git-bloom-config show hydroTrack 'hydro' does not exist.joq@vision-4:image_common-release$ git co bloomSwitched to branch 'bloom'joq@vision-4:image_common-release$ lsbloom.conf tracks.yamljoq@vision-4:image_common-release$ git-bloom-config show hydroTrack 'hydro' does not exist.joq@vision-4:image_common-release$ cat tracks.yamltracks:hydro:actions:- bloom-export-upstream :{vcs_local_uri} :{vcs_type} --tag :{release_tag} --display-uri:{vcs_uri} --name :{name} --output-dir :{archive_dir_path}- git-bloom-import-upstream :{archive_path} :{patches} --release-version :{version}--replace- git-bloom-generate -y rosrelease :{ros_distro} --source upstream -i :{release_inc}- git-bloom-generate -y rosdebian --prefix release/:{ros_distro} :{ros_distro}-i :{release_inc}devel_branch: nulllast_version: 1.10.3name: upstreampatches: nullrelease_inc: '0'release_tag: :{version}ros_distro: hydrovcs_type: gitversion: :{auto}--
joq
_______________________________________________
Ros-release mailing list
Ros-release@code.ros.org
https://code.ros.org/mailman/listinfo/ros-release