-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
Permission Error on AUR git packages #634
Comments
We've seen this before, and part of the issue seems to be that installation via the official packages sets the permissions right, but the "automatic" way that Aura does itself seems flawed. |
So what's the solution? Is there anything I can do to help? |
For now, can you try deleting |
Let me do that manually instead, What are the requirements? |
Actually, now that I look, the Okay, then let's try it this way: can you delete I'll also mention that this sounds related to #615. |
Error still--not sure if it's due to the same permission issue but likely is:
Is that intentional? NOTE (just to be thorough):
|
Thank you for your patience with this. Can you do an |
|
How about the
|
I have a umask of |
Hmm... why are our permissions different... |
In trying to build
And checking permissions:
|
The smoking gun. Why are |
Found the problem: -- | Assuming that we're already in a VCS-based package's build folder,
-- just pull the latest instead of cloning.
pullRepo :: RIO Env (Either Failure ())
pullRepo = do
logDebug "git: Clearing worktree. "
void . runProcess . setStderr closed . setStdout closed $ proc "git" ["reset", "--hard", "HEAD"]
logDebug "git: Pulling repo."
ec <- runProcess . setStderr closed . setStdout closed $ proc "git" ["pull"]
case ec of
ExitFailure _ -> pure . Left . Failure $ FailMsg buildFail_12
ExitSuccess -> pure $ Right () The |
I checked out
And built it.
|
Ah, you will have to delete your
in that folder. |
I deleted the entire Then tried:
Fails again. Incidentally:
It creates NOTE: I have a NOTE 2: if i change ownership manually to However, a user installing |
Hmm... I don't have such a |
If I manually create the I do think this is a PS This issue has crept up but wasn't present in 2.0, etc. Or early versions of 3, as I recall, |
Maybe that should become a part of an automatic migration process? Otherwise an upgrade of aura package would suddenly break users' existing setups. |
I think that having aura create |
I closed this by error, reopened now. As far as As If I login as If i login to root like this |
Alright, I pushed up a new commit. Could you test it after deleting your |
Just tested it and it works. |
Thanks for testing! I had been using |
What about if dir is missing create it with |
Yes exactly. |
Alright, that should do it! |
Hi, for weeks now, I have noticed that aura is unable to update or install git packages from the AUR due to permission errors.
And:
Permissions are set by aura to 600 during build process.
Not sure why it creates this error.
NOTE: this does not occur with non-git packages.
The text was updated successfully, but these errors were encountered: