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

makepkg ignores user configs when running under aura #614

Closed
infomaniac50 opened this issue Jun 9, 2020 · 6 comments
Closed

makepkg ignores user configs when running under aura #614

infomaniac50 opened this issue Jun 9, 2020 · 6 comments

Comments

@infomaniac50
Copy link

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.

@fosskers
Copy link
Owner

I've just released 3.1.2 that fixed a big regression. Can you try that version and see if the issue persists?

@infomaniac50
Copy link
Author

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.

@fosskers
Copy link
Owner

Great to hear! Shall we close this?

@infomaniac50
Copy link
Author

I consider the matter solved. I will close the issue.

@ultimatespirit
Copy link

I think this issue may actually persist, or perhaps it's ignoring certain parts of the user makepkg.conf. A relatively recent change to the way makepkg works has it that by default it will create a separate package_name-debug package for all packages and install that automatically.

This behaviour may be removed by changing the OPTIONS=... array to include !debug, for example OPTIONS=(strip docs !libtool !staticlibs emptydirs zipman purge !debug lto) or OPTIONS+=('!debug') should do it.

As far as I can tell aura version 3.2.9 ignores this, as it still creates debug packages.

@fosskers
Copy link
Owner

fosskers commented Jun 3, 2024

Ah interesting. We should consider that a separate issue.

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

3 participants