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

add shebang line in setup_custom_pythonpath.sh.in template #91

Merged
merged 1 commit into from
Jul 18, 2017

Conversation

mikaelarguedas
Copy link
Member

@mikaelarguedas mikaelarguedas commented Jul 11, 2017

connects to #69

@joshughes
Copy link

@mikaelarguedas this solves the issue I was seeing

@mikaelarguedas
Copy link
Member Author

@ros-pull-request-builder retest this please

@mikaelarguedas mikaelarguedas merged commit 88ba5ef into master Jul 18, 2017
@mikaelarguedas mikaelarguedas deleted the add_shebang_line branch July 18, 2017 17:29
@joshughes
Copy link

@mikaelarguedas sorry to bother you but was curious how we might know when this fix is available upstream

Now that its merged will a new package be generated right away or does the ROS team have a release cadence they adhere to

Currently we pull from http://packages.ros.org/ros/ubuntu/pool/main/r/ros-kinetic-rqt-reconfigure/

@mikaelarguedas
Copy link
Member Author

TL:DR I'd say about 3 weeks from now

The process for getting a package available:

  • making a release
  • the ROS buildfam will build the package and make it available in the testing repository
  • every few weeks (usually 2 weeks but sometimes a bit more) we sync the testing repository to the main repository (the one you are using).

For packages that low in the stack we try to synchronize the releases because it results in rebuild almost the entire ROS eco-system. I expect us to make a new release of ros "core" packages around the beginning of next week, we will then leave them in testing for ~2weeks to track and address possible regressions before making them available on the main repository.

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

Successfully merging this pull request may close these issues.

None yet

2 participants