Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Indigo/Kinetic Release 07-2017 #42

Closed
20 of 21 tasks
floweisshardt opened this issue Jul 17, 2017 · 28 comments
Closed
20 of 21 tasks

Indigo/Kinetic Release 07-2017 #42

floweisshardt opened this issue Jul 17, 2017 · 28 comments

Comments

@floweisshardt
Copy link
Member

floweisshardt commented Jul 17, 2017

Tracking the related PRs to rosdistro:
⚠️ = not dual-distro compatible, i.e. indigo_dev for Indigo and kinetic_dev for Kinetic

@mathias-luedtke
Copy link

mathias-luedtke commented Jul 17, 2017

ros_canopen is released (0.6.7/0.7.5), do you need a newer version?

@fmessmer
Copy link
Member

fmessmer commented Jul 17, 2017

ros_canopen is released (0.6.7/0.7.5), do you need a newer version?

ros_canopen was just mentioned temporarily as we copied the list from last release...we no longer consider ros_canopen to be part of the "cob-release-cycle"... the maintainer take care of it very well 😉

@mathias-luedtke
Copy link

The fix needed for the raws is not yet released for indigo, only for jade+

@fmessmer
Copy link
Member

@ipa-flg-pb @ipa-rmb @ipa-jcl @ipa-fmw
please continue with the release process for the packages assigned so far....cob_robots, cob_simulation, cob_manipulation and care-o-bot are not yet ready for release as we need to clean-up a few things first to make them releasable...
however, they would be released last anyway, as they have the most upstream-dependencies..

once the first PRs to rosdistro have been accepted, please follow debbuild_indigo and debbuild_kinetic

you can tick of the checkbox once indigo and kinetic succeeded, i.e. first two columns are green and last is either blue=OldVersion (indigo) or red=None (kinetic)

post errors from the buildfarm here, if any

@fmessmer
Copy link
Member

@ipa-flg-pb please come see us about how to proceed with ros/rosdistro#15532 (comment)

@fmessmer
Copy link
Member

@ipa-rmb could you please attach the txt-file with the latest release hints and commands to this issue for the sake of completeness and documentation?

@ipa-rmb
Copy link

ipa-rmb commented Jul 18, 2017

These are the current notes on doing releases:

release.txt

@ipa-flg-pb
Copy link

Ther is the following Issue with cob_driver/cob_mimic

Pre-verifying Debian dependency keys...
Running 'rosdep update'...
Key 'python-vlc-pip' resolved to '['python-vlc']' with installer 'pip', which does not match the default installer 'apt'.
Failed to resolve python-vlc-pip on ubuntu:trusty with: Error running generator: The Debian generator does not support dependencies which are installed with the 'pip' installer.
python-vlc-pip is depended on by these packages: ['cob_mimic']
<== Failed
Some of the dependencies for packages in this repository could not be resolved by rosdep.
You can try to address the issues which appear above and try again if you wish.

any idea how to solve this?

@fmessmer
Copy link
Member

@ipa-mdl
Do you know how to deal with python-pip dependencies?
The rosdep key is available here

@mathias-luedtke
Copy link

AFAIR packages with pip-only dependencies cannot be released.
Where is this output from?

@fmessmer
Copy link
Member

fmessmer commented Jul 18, 2017

it's from bloom-release <repository_name> --track <track> --rosdistro <distro>
(@ipa-flg-pb correct me if I'm wrong)

so, we cannot release cob_mimic then?
@ipa-fmw FYI

@mathias-luedtke
Copy link

ros-infrastructure/bloom#412 might be related

@mathias-luedtke
Copy link

so, we cannot release cob_mimic then?

Only if you rewrite it to use libvlc-dev directly ;)

@fmessmer
Copy link
Member

fmessmer commented Jul 18, 2017

currently having this discussion...
--> https://github.com/ipa320/cob_driver/issues/340

@mathias-luedtke
Copy link

The fix needed for the raws is not yet released for indigo, only for jade+

I have made a new release for indigo as well.

@ipa-rmb
Copy link

ipa-rmb commented Jul 20, 2017

Does someone know what causes this error for libconcorde_tsp_solver: http://build.ros.org/job/Kbin_uxhf_uXhf__libconcorde_tsp_solver__ubuntu_xenial_armhf__binary/4/display/redirect

I can find some errors telling it cannot find libqsopt but libqsopt is part of the cob_extern release and there are no errors from the release of libqsopt.

@mathias-luedtke
Copy link

Is it working for the other architectures?
I would guess that the settings needs to be passed to the ExternalProject.

@ipa-rmb
Copy link

ipa-rmb commented Jul 20, 2017

Yes, it works for the other arhcitectures.

The only other which is not working is:
http://build.ros.org/job/Kbin_djv8_dJv8__libconcorde_tsp_solver__debian_jessie_arm64__binary/4/display/redirect

Something was not available for arm, maybe it was libqsopt. However, how does libqsopt then go through smoothly? Or can we turn of arm support?

@mathias-luedtke
Copy link

Or can we turn of arm support?

https://github.com/ros-infrastructure/ros_buildfarm_config/tree/production/kinetic
Please double check for other errors beforehand!

@fmessmer
Copy link
Member

The release blocker for cob_manipulation, i.e. stomp, has been removed in ipa320/cob_manipulation#117 and ipa320/cob_manipulation#119

@ipa-rmb agreed to release the remaining repos cob_manipulation, cob_robots and cob_simulation into both indigo and kinetic 👍

@ipa-flg-pb I consider your job done for the time being...thank you for your help!

@ipa-rmb
Copy link

ipa-rmb commented Aug 2, 2017

I think I figured out how to edit the first message without loosing data:

  1. Refresh page
  2. Click edit comment but cancel editing immediately (if you would have lost data, it now asks you whether you really want to abort and loose your unsaved changes - click yes)
  3. Refresh page
  4. Edit the message and save
  5. Refresh page

@fmessmer
Copy link
Member

fmessmer commented Aug 2, 2017

release of ur_* packages is tracked ros-industrial/universal_robot#240 (comment)

@fmessmer
Copy link
Member

fmessmer commented Aug 4, 2017

@ipa-rmb
Copy link

ipa-rmb commented Aug 9, 2017

Shall we do a release session again or are there some pull requests that we should await first? Do we release care-o-bot as well?

@fmessmer
Copy link
Member

fmessmer commented Aug 9, 2017

Yes, we should release care-o-bot, too

For the next cycle, I think we should wait a bit more as there are a few things pending in cob_robots...new bots, zr300 migration, raw3-1 to canopen...

@ipa-rmb
Copy link

ipa-rmb commented Aug 9, 2017

Ok, so care-o-bot should be released already now, the remainder has to wait for the second cycle later, correct?

@fmessmer
Copy link
Member

fmessmer commented Aug 9, 2017

👍
the next release should also go in a new issue

@fmessmer
Copy link
Member

fmessmer commented Sep 9, 2017

Let's just say care-o-bot missed one release cycle and close this PR!
We'll trigger a new release some time soon anyway? October?

@fmessmer fmessmer closed this as completed Sep 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants