Closed piyushk closed 10 years ago
Yeah, this is because of this line:
git-bloom-generate -y rosdebian --prefix release/hydro hydro -i 0
That matches any existing branches with the release/hydro
prefix, so any previously bloomed packages will get picked up. I should instead pass the explicit white list to the git-bloom-generate rosdebian
command.
I cannot fix this without changing the default actions for a release and without changing the command line options for git-bloom-generate
, so I am going to push this to the next major release 0.5.
I removed one of the packages (segbot_gazebo_plugins) from a multi-package repository. On the next release (0.1.3), bloom still attempt to re-create the debian branch for segbot_gazebo_plugins (0.1.2). The final pull request for updating release.yaml was fine and removed segbot_gazebo_plugins.
...and...
Final pull request: