-
Notifications
You must be signed in to change notification settings - Fork 102
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
Use -o when extracting with tar to give ownership to current user #1408
Conversation
@sebjulliand I gave this change a quick test - however, I wasn't able to recreate the problem: Even using Could you recreated the issue #1405 on your system? And how was your setup? |
Awesome work Seb! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @sebjulliand.
Much like @chrjorgensen, I was not able to recreate this on a 7.3 box I was using, but I really appreciate you sharing the system you recreated it on.
I thought when Barry merged the commit into master I thought when I opened VSCode it would notify me to update the extension but it didn't. As I'm new to this when or how do I see this fix to confirm it is working on my end? |
@rogersonra the merge some not mean it has been released. I am hoping to get a new release (2.0.0) out this weekend. |
@sebjulliand , thank you. I had a chance to test this today and everything is created with my user profile. Good job... |
Awesome, thanks! |
Changes
Fixes #1405
For some reason (?)
tar
would give ownership of the deployed files to QSECOFR (always with/usb/bin
'star
, not on files with/QOpensys
' tar).Using the
-o
flag (i.e.--no-same-owner
) fixes the issue and gives owner of every extracted files to the currently connected user.Checklist