Yes, sorry. I copied the wrong url in the email by mistake, but I put the
right one in the release.yaml.

Is it possible that not having the <export> <metapackage/> tag in the
package.xml of the metapackage was the cause of the problem?


2013/9/25 Jack O'Quin <jack.oquin@gmail.com>

>
> On Wed, Sep 25, 2013 at 6:12 AM, Toni Oliver Duran <
> toliver.shadow@gmail.com> wrote:
>
>> This is a first-time release of a repo containing multiple packages (one
>> of them a metapackage).
>>
>> bloom-release seems to be working well and finding the different
>> packages, but when generating the pull request to hydro/release.yaml it
>> does not create the list of packages automatically.
>>
>> I get
>>
>> sr_ronex:
>>     tags:
>>       release: release/hydro/{package}/{version}
>>     url: git@github.com:shadow-robot/sr-ronex-release.git
>>     version: 0.9.2-0
>>
>>
>> When I expect:
>>
>> sr_ronex:
>>     packages:
>>         sr_ronex:
>>         sr_ronex_controllers:
>>         sr_ronex_drivers:
>>         sr_ronex_examples:
>>         sr_ronex_external_protocol:
>>         sr_ronex_hardware_interface:
>>         sr_ronex_launch:
>>         sr_ronex_msgs:
>>         sr_ronex_transmissions:
>>         sr_ronex_utilities:
>>     tags:
>>       release: release/hydro/{package}/{version}
>>     url: git@github.com:shadow-robot/sr-ronex-release.git
>>     version: 0.9.2-0
>>
>>
>> Is the normal behaviour of bloom-release that the user adds the list of
>> packages manually? Or it means that I did something wrong?
>>
>
> Looking at the release repo, bloom clearly did find all your packages, and
> you have the latest version of bloom.
>
> I think your release URL should be the https address, not the git login
> address. The build farm can't log in as you.
> --
>  joq
>