automate DO NOT MERGE | changes required in CS components to build automate via LTS channel

DO NOT MERGE | changes required in CS components to build automate via LTS channel

Open talktovikas opened this issue 10 months ago • 2 comments

:nut_and_bolt: Description: What code changed, and why?

While building Automate components in chef-server pipeline these changes were required. the problem during testing: Lets say the package: core/coreutils/8.32/20240105213308 that is https://bldr.habitat.sh/#/pkgs/core/coreutils/8.32/20240105213308 is not in LTS and apart from that since we are using Fallback_channel as 'dev' to tackle the problem of chef-scaffolding not in LTS, this version of coreutils would be installed. Now this package have common dependencies with other packages which are from LTS, for example glibc. This will cause having same package with different versions during build and hence due to circular direct or transitive dependency build won't happen.

:chains: Related Resources

:+1: Definition of Done

:athletic_shoe: How to Build and Test the Change

:white_check_mark: Checklist

All PRs must tick these:

[ ] I have read the CONTRIBUTING document.
[ ] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate: