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

r10k does not write files correctly from git on Windows #1381

Open
benjamin-robertson opened this issue Apr 12, 2024 · 6 comments
Open

r10k does not write files correctly from git on Windows #1381

benjamin-robertson opened this issue Apr 12, 2024 · 6 comments
Assignees
Labels

Comments

@benjamin-robertson
Copy link

benjamin-robertson commented Apr 12, 2024

Describe the Bug

On Windows r10k include carriage return (CRLF) in files when syncing modules from Git.

This occurs when using 'bolt module install'

Expected Behaviour

It should not insert CRLF when installing modules.

Steps to Reproduce

Steps to reproduce the behaviour:

  1. Install a git module on windows.
  2. Run a ruby task on a non-window host.
  3. Will get error when trying to run against a Linux host.
/opt/puppetlabs/puppet/bin/ruby^M: bad interpreter: No such file or directory

Environment

  • Version [r10k 3.16.0, bolt 3.28.0]
  • Platform [Windows 2022, RHEL8 target]

Additional Context

Noticed this issue when troubleshooting cd4peadm module on Windows.

Solution

Need to disable autocrlf in git for on Windows platform.

@benjamin-robertson
Copy link
Author

benjamin-robertson commented Apr 18, 2024

This issue may be fixed in the bolt project itself, in that case this issue can be closed.

The r10k solution will only fix when modules are installed via git to a windows bolt project. If a user creates local tasks\scripts these will still suffer the same issue. Hence why it may be better to correct within bolt. Waiting for engineering decision.

Copy link

This issue has been marked stale because it has had no activity for 60 days. The Puppet Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days.

@github-actions github-actions bot added the stale label Jun 18, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
@benjamin-robertson benjamin-robertson self-assigned this Jun 26, 2024
Copy link

This issue has been marked stale because it has had no activity for 60 days. The Puppet Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days.

@github-actions github-actions bot added the stale label Aug 26, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 2, 2024
@benjamin-robertson
Copy link
Author

yes bot closing the ticket 'fixes' it.

Copy link

github-actions bot commented Nov 8, 2024

This issue has been marked stale because it has had no activity for 60 days. The Puppet Team is actively prioritizing existing bugs and new features, if this issue is still important to you please comment and we will add this to our backlog to complete. Otherwise, it will be closed in 7 days.

@benjamin-robertson
Copy link
Author

...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant