Revision history [back]

There is a chicken-egg problem here. bloom-release clones the release repository (gbp) for you by looking in the rosdistro file for the release repository url. If you haven't released into hydro before, there will be no entry for your repository yet.

When we "forked" the hydro files from the groovy ones we simply set the version for each entry to null, this way the build farm would skip it and so that bloom can still find the release repository for things released into groovy before the fork.

Since your repository does not have an entry in the hydro.yaml rosdistro file bloom does not know where to find it. You can resolve this by adding a rosdistro entry with a version set to null.

The nice thing for bloom to do here would be to have you specify the location of the gbp, so it could continue and then edit the rosdistro file for you at the end, adding your repository's entry using the gbp you specified at the beginning.

There is a chicken-egg problem here. bloom-release clones the release repository (gbp) for you by looking in the rosdistro file for the release repository url. If you haven't released into hydro before, there will be no entry for your repository yet.

When we "forked" the hydro files from the groovy ones we simply set the version for each entry to null, this way the build farm would skip it and so that bloom can still find the release repository for things released into groovy before the fork.

Since your repository does not have an entry in the hydro.yaml rosdistro file bloom does not know where to find it. You can resolve this by adding a rosdistro entry with a version set to null.

The nice thing for bloom to do here would be to have you specify the location of the gbp, so it could continue and then edit the rosdistro file for you at the end, adding your repository's entry using the gbp you specified at the beginning.

There is a chicken-egg problem here. bloom-release clones the release repository (gbp) for you by looking in the rosdistro file for the release repository url. If you haven't released into hydro before, there will be no entry for your repository yet.

When we "forked" the hydro files from the groovy ones we simply set the version for each entry to null, this way the build farm would skip it and so that bloom can still find the release repository for things released into groovy before the fork.

Since your repository does not have an entry in the hydro.yaml rosdistro file bloom does not know where to find it. You can resolve this by adding a rosdistro entry with a version set to null.

The nice thing for bloom to do here would be to have you specify the location of the gbp, so it could continue and then edit the rosdistro file for you at the end, adding your repository's entry using the gbp you specified at the beginning.

UPDATE: I have added a note the wiki tutorial here:

http://ros.org/wiki/bloom/Tutorials/ReleasingForANewROSDistro