-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
makepkg ignores user configs when running under aura #614
Comments
I've just released |
I upgraded Aura from 3.1.1 to 3.1.4 and the issue has been fixed. I had to leave the global /etc/makepkg.conf change in place for the aura upgrade but I changed it back afterwards. Then I upgraded dropbox to 99.4.501-1 without any problems. |
Great to hear! Shall we close this? |
I consider the matter solved. I will close the issue. |
I think this issue may actually persist, or perhaps it's ignoring certain parts of the user This behaviour may be removed by changing the As far as I can tell |
Ah interesting. We should consider that a separate issue. |
According to
man makepkg.conf
you can set custom configs in your home directory in~/.makepkg.conf
. I removed the xz extension in my user config to stop it from compressing AUR packages. Some of them are huge and take longer than I am willing to wait for. I have plenty of space on my drive so I removed package compression. The system config still uses the default option.When trying to update Angry IP Scanner (ipscan) today, I got the following error message.
error: '/var/cache/pacman/pkg/ipscan-3.7.2-1-x86_64.pkg.tar': could not find or read package
I checked the build directory for the package file and I found it had an xz extension.ipscan-3.7.2-1-x86_64.pkg.tar.xz
I built the package manually and the build succeeded. Then I checked the package file and it did not have the xz extension. Next I edited the system makepkg.conf and set the PKGEXT to .pkg.tar. Then I ran aura again with the new system config and it also succeeded.
Something about AURA Version 3.1.1 is causing makepkg to not pick up the .makepkg.conf file in my home directory. For now, I'll have to edit /etc/makepkg.conf to not include any compression.
The text was updated successfully, but these errors were encountered: