-
Notifications
You must be signed in to change notification settings - Fork 19
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
warning: couldn't find or create package cache, using /tmp/ instead #88
Comments
That is a pacman message, not anything ccm is generating. Can you try uncommenting |
Yeah, that makes the warning go away. Weird... Thanks, though! |
graysky2
pushed a commit
that referenced
this issue
Sep 19, 2024
If not defining CUSTOM_PACMAN_CONF, the default behavior is to use the system /etc/pacman.conf which is problematic if DownloadUser = alpm is defined causing breakage of creating the buildroot so hack that out when CUSTOM_PACMAN_CONF is null. Fixes #88
Turns out, this is due to pacman 7.0.0, see commit message in 8715a0f User no longer need to point to any particular pacman.conf in v2.229 |
Happy to be of service! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever I use ccm to build packages, I get the above warning when it comes time to download the makedeps. This is not an issue per se - the build works fine - but sometimes, when I tinker with patch series, I am rebuilding the same package several times in a row and the makedeps get re-downloaded every time, because they somehow do not get stored in pacman's cache directory.
What am I doing wrong?
CHROOTPATH64="/opt/chroot"
THREADS=5
#CUSTOM_PACMAN_CONF='/usr/share/devtools/pacman.conf.d/extra-testing.conf'
#CUSTOM_MAKEPKG_CONF='/usr/share/devtools/makepkg.conf.d/x86_64.conf'
REPO="/var/cache/pacman/aur"
REPO_NAME='local_aur'
#NOCHECK=1
PKGEXT=
PACKAGER="Taijian [email protected]"
RUNNAMCAP=
RUNDISTCC=
DISTCC_THREADS=
#DISTCC_HOSTS="localhost/9 foo/8 bar/4"
CCACHE_DIR="/var/cache/ccache"
The text was updated successfully, but these errors were encountered: