ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

bloom; RuntimeError: Two packages have different version numbers (but it is false) [closed]

asked 2016-06-16 05:09:03 -0500

cvillar gravatar image

I'm trying to release a meta package using boom with the following command:

bloom-release --rosdistro indigo --track indigo summit_xl_common

And after a lot of questions it gives me the following error:

==> git-bloom-import-upstream /tmp/tmpUJpJvY/upstream-indigo-1.0.0.tar.gz  --release-version 1.0.0 --replace
Creating upstream branch.
Importing archive into upstream branch...
Traceback (most recent call last):
  File "/usr/bin/git-bloom-import-upstream", line 9, in <module>
    load_entry_point('bloom==0.5.21', 'console_scripts', 'git-bloom-import-upstream')()
  File "/usr/lib/python2.7/dist-packages/bloom/commands/git/", line 391, in main
  File "/usr/lib/python2.7/dist-packages/bloom/commands/git/", line 324, in import_upstream
    _, actual_version, _ = get_package_data('upstream')
  File "/usr/lib/python2.7/dist-packages/bloom/", line 91, in get_package_data
    version = verify_equal_package_versions(packages.values())
  File "/usr/lib/python2.7/dist-packages/catkin_pkg/", line 127, in verify_equal_package_versions
    raise RuntimeError('Two packages have different version numbers (%s != %s):\n- %s\n- %s' % (package.version, version, package.filename, packages[0].filename))
RuntimeError: Two packages have different version numbers (0.0.3 != 1.0.0):
- /tmp/tmp7NakeJ/summit_xl_localization/package.xml
- /tmp/tmp7NakeJ/summit_xl_common/package.xml

<== Error running command '['/usr/bin/git-bloom-import-upstream', '/tmp/tmpUJpJvY/upstream-indigo-1.0.0.tar.gz', '--release-version', '1.0.0', '--replace']'
Release failed, exiting.

It says that summit_xl_common and summit_xl_localization have different version numbers, but it is false, you can check here that it is version 1.0.0 (same as summit_xl_common).

Why does it occur? How should I fix it?


edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by cvillar
close date 2016-06-17 02:30:28.143356


Can you please post the full log, maybe in a The logs are stored in ~/.bloom_logs.

William gravatar image William  ( 2016-06-16 16:27:35 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2016-06-17 02:30:04 -0500

cvillar gravatar image

I've finally managed to publish the release, it was a problem with the package.xml version pushed with that tag, I deleted it and creted it again and it works.


edit flag offensive delete link more

answered 2016-06-16 15:58:21 -0500

tfoote gravatar image

I'm not sure exactly why the error is occurring but I do notice that you're using a non-standard version tag, indigo-1.0.0. The standard tag would be 1.0.0 It is bad practices and will break a lot of tools' assumptions to have different content with the same version number. Different distros should have different versions series.

edit flag offensive delete link more

Question Tools



Asked: 2016-06-16 05:09:03 -0500

Seen: 178 times

Last updated: Jun 17 '16