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

superflore-gen-oe-recipes: Wrong path used to calculate ROS_NUM_CACHE_YAML_COMMITS #264

Closed
herb-kuta-lge opened this issue Dec 31, 2019 · 0 comments
Assignees

Comments

@herb-kuta-lge
Copy link
Contributor

The path to cache.yaml used to calculate ROS_NUM_CACHE_YAML_COMMITS wasn't updated for the file's new location in layer version 3. The line to fix is here.

Also, the generated comment here needs correcting as does the pull request title (here and here).

@herb-kuta-lge herb-kuta-lge self-assigned this Dec 31, 2019
@allenh1 allenh1 added the ready label Jan 2, 2020
shr-project added a commit to shr-project/superflore that referenced this issue Mar 20, 2020
* Fix path to cache.yaml in comment and overlay.get_file_revision_logs() call
* Fixes ros-infrastructure#264

Signed-off-by: Martin Jansa <[email protected]>
shr-project added a commit to shr-project/superflore that referenced this issue Mar 20, 2020
* Fix path to cache.yaml in comment and overlay.get_file_revision_logs() call
* Fixes ros-infrastructure#264

Signed-off-by: Martin Jansa <[email protected]>
shr-project added a commit to shr-project/superflore that referenced this issue Mar 20, 2020
* Fix path to cache.yaml in generated comment in
  superflore-ros-distro.inc, overlay.get_file_revision_logs() call, and
  commit summaries.
* Fixes ros-infrastructure#264

Signed-off-by: Martin Jansa <[email protected]>
zffgithub pushed a commit to zffgithub/superflore that referenced this issue Apr 11, 2023
* Fix path to cache.yaml in generated comment in
  superflore-ros-distro.inc, overlay.get_file_revision_logs() call, and
  commit summaries.
* Fixes ros-infrastructure#264

Signed-off-by: Martin Jansa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants