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

--no-same-owner --no-same-permissions in tar #375

Closed
Jef239 opened this issue Mar 21, 2024 · 0 comments
Closed

--no-same-owner --no-same-permissions in tar #375

Jef239 opened this issue Mar 21, 2024 · 0 comments

Comments

@Jef239
Copy link

Jef239 commented Mar 21, 2024

I ran create_install.sh on Windows in git-bash and got bundled install. During installation, the files had incorrect user and group names. This can be resolved by adding the --no-same-owner option to the tar. It also makes sense to add the --no-same-permissions switch.

As I understand it, the construction "sudo -u "${RTKBASE_USER}" tail -n+${ARCHIVE} "${0}" | tar xpJv" is first separated by a "|" into two parts, and then only the first part is executed under sudo

Stefal added a commit that referenced this issue Nov 24, 2024
…ng the install.sh script.

before:
If you launch the script as foo, with sudo, extracted files owner is the one who create the archive.
after:
If you launch the script as foo, with sudo, and RTKBASE_USER is basegnss, extracted files owner is basegnss.

Fix #413 and fix #375
@Stefal Stefal closed this as completed Nov 24, 2024
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

2 participants