Ask Your Question
0

"Failed to clone repository" error on first-time bloom releasing for svn devel repo.

asked 2013-08-04 18:56:17 -0500

130s gravatar image

updated 2013-08-04 19:08:26 -0500

Following bloom's Releasing a Package for the First Time tutorial with my svn upstream repo and git release repo with source version of bloom(to avoid this problem), I get this error:

ros-giantsquid@calamari:~/ROS/hydro_precise/catkinws/src/openrtm_common$ ~/ROS/ros-infrastructure/bloom/scripts/bloom-release --rosdistro hydro --track hydro openrtm_common --edit
/home/ros-giantsquid/ROS/ros-infrastructure/bloom/bloom/__init__.py:2: UserWarning: Module bloom was already imported from /home/ros-giantsquid/ROS/ros-infrastructure/bloom/bloom/__init__.pyc, but /usr/lib/pymodules/python2.7 is being added to sys.path
  import pkg_resources
/home/ros-giantsquid/ROS/ros-infrastructure/bloom/bloom/__init__.py:2: UserWarning: Module bloom was already imported from /home/ros-giantsquid/ROS/ros-infrastructure/bloom/bloom/__init__.pyc, but /usr/lib/pymodules/python2.7 is being added to sys.path
  import pkg_resources
Specified repository 'openrtm_common' is not in the release file located at 'https://raw.github.com/ros/rosdistro/master/hydro/release.yaml'
Did you mean one of these: 'pr2_common', 'cob_common', 'clearpath_common'?
Could not determine release repository url for repository 'openrtm_common' of distro 'hydro'
You can continue the release process by manually specifying the location of the RELEASE repository.
To be clear this is the url of the RELEASE repository not the upstream repository.
Release repository url [press enter to abort]: <a href="https://github.com/start-jsk/openrtm_common-release.git">https://github.com/start-jsk/openrtm_common-release.git</a>
==> Fetching 'openrtm_common' repository from 'https://github.com/start-jsk/openrtm_common-release.git'
Cloning into '/tmp/tmpKb0aIo'...
warning: You appear to have cloned an empty repository.
WARNING [vcstools] Command failed: 'git log -1 --format='%H''
 run at: '/tmp/tmpKb0aIo'
 errcode: 128:
fatal: bad default revision 'HEAD'
[/vcstools]
WARNING [vcstools] Command failed: 'git log -1 --format='%H''
 run at: '/tmp/tmpKb0aIo'
 errcode: 128:
fatal: bad default revision 'HEAD'
[/vcstools]
WARNING [vcstools] Command failed: 'git checkout master'
 run at: '/tmp/tmpKb0aIo'
 errcode: 1:
error: pathspec 'master' did not match any file(s) known to git.
[/vcstools]
Creating 'master' branch.
Creating track 'hydro'...
Repository Name:
  upstream
    Default value, leave this as upstream if you are unsure
  <name>
    Name of the repository (used in the archive name)
  ['upstream']: 
Upstream Repository URI:
  <uri>
    Any valid URI. This variable can be templated, for example an svn url
    can be templated as such: "https://svn.foo.com/foo/tags/foo-:{version}"
    where the :{version} token will be replaced with the version for this release.
  [None]: <a href="https://rtm-ros-robotics.googlecode.com/svn/tags/:%7Bversion%7D">https://rtm-ros-robotics.googlecode.com/svn/tags/:{version}</a>
Upstream VCS Type:
  svn
    Upstream URI is a svn repository
  git
    Upstream URI is a git repository
  hg
    Upstream URI is a hg repository
  tar
    Upstream URI is a tarball
  ['git']: svn
Version:
  :{ask}
    This means that the user will be prompted for the version each release.
    This also means that the upstream devel will be ignored.
  :{auto}
    This means the version will be guessed from the devel branch.
    This means that the devel branch must be set, the devel branch must exist,
    and there must be a valid package.xml in the upstream devel branch ...
(more)
edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted
0

answered 2013-08-05 14:12:59 -0500

130s gravatar image

updated 2013-08-05 14:14:44 -0500

My collaborator @Kei Okada suggested to set Release Tag as :{none}, which let bloom move forward.

The release repository must have been already initialized with README.

edit flag offensive delete link more
1

answered 2013-08-04 19:55:28 -0500

William gravatar image

The release repository has to be initialized first, from the tutorial:

"Note: When creating your github.com repository, check the box Initialize this repository with a README, this way it starts out as a valid git repo."

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2013-08-04 18:56:17 -0500

Seen: 1,627 times

Last updated: Aug 05 '13