Diff your local .conf with the package .conf.
1 Like
New problem. It builds the new mesa 24.1.5 just fine, buuuut… when I start installing it, I get:
:: Synchronizing package databases...
localrepo 3.7 KiB 1241 KiB/s 00:00 [--------------------------------------------------] 100%
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (12) lib32-libva-mesa-driver-1:24.1.5-1 lib32-mesa-1:24.1.5-1 lib32-mesa-vdpau-1:24.1.5-1 lib32-opencl-rusticl-mesa-1:24.1.5-1
lib32-vulkan-mesa-layers-1:24.1.5-1 lib32-vulkan-radeon-1:24.1.5-1 libva-mesa-driver-1:24.1.5-1 mesa-1:24.1.5-1
mesa-vdpau-1:24.1.5-1 opencl-rusticl-mesa-1:24.1.5-1 vulkan-mesa-layers-1:24.1.5-1 vulkan-radeon-1:24.1.5-1
Total Installed Size: 321.77 MiB
Net Upgrade Size: 2.19 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
lib32-opencl-rusticl-mesa-1:24.1.5-1-x86_64 7.0 MiB 234 MiB/s 00:00 [--------------------------------------------------] 100%
opencl-rusticl-mesa-1:24.1.5-1-x86_64 6.9 MiB 208 MiB/s 00:00 [--------------------------------------------------] 100%
libva-mesa-driver-1:24.1.5-1-x86_64 4.1 MiB 115 MiB/s 00:00 [--------------------------------------------------] 100%
lib32-libva-mesa-driver-1:24.1.5-1-x86_64 3.9 MiB 97.7 MiB/s 00:00 [--------------------------------------------------] 100%
lib32-mesa-vdpau-1:24.1.5-1-x86_64 3.9 MiB 97.0 MiB/s 00:00 [--------------------------------------------------] 100%
mesa-vdpau-1:24.1.5-1-x86_64 3.8 MiB 88.5 MiB/s 00:00 [--------------------------------------------------] 100%
lib32-vulkan-radeon-1:24.1.5-1-x86_64 2.6 MiB 56.0 MiB/s 00:00 [--------------------------------------------------] 100%
vulkan-radeon-1:24.1.5-1-x86_64 2.5 MiB 54.1 MiB/s 00:00 [--------------------------------------------------] 100%
lib32-vulkan-mesa-layers-1:24.1.5-1-x86_64 374.6 KiB 7.95 MiB/s 00:00 [--------------------------------------------------] 100%
vulkan-mesa-layers-1:24.1.5-1-x86_64 360.4 KiB 7.65 MiB/s 00:00 [--------------------------------------------------] 100%
(12/12) checking keys in keyring [--------------------------------------------------] 100%
(12/12) checking package integrity [--------------------------------------------------] 100%
:: File /var/cache/pacman/pkg/mesa-1:24.1.5-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] n
:: File /var/cache/pacman/pkg/lib32-mesa-1:24.1.5-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (checksum)).
Do you want to delete it? [Y/n] n
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.
-> error refreshing databases - exit status 1
EDIT: nvm. it conflicted with philm’s .sig files in /var/cache/pacman/pkg/ with/for the exact same package named packages there.
@pux can I move localrepo out of ~/autogit folder, because apparently pacman 7 doesn’t like it being in my home folder? How?
Anyway, right now as a workaround to pacman 7 issue with the localrepo being in my user folder, I added the line to /etc/fstab
/home/deemon/autogit/localrepo /localrepo none bind,ro
which seems to do the trick for the new pacman 7 (ln -s didn’t work).
Also right now all the files in the folder remain with deemon:deemon ownership… which doesn’t seem to bother pacman 7 … although it was suggested to alter the ownership for some reason to alpm?? seems unnecessary as far the folders are accessible and files readable to alpm.
You can change the whole directory by setting “DIR” on top of “/usr/bin/autogit” to the desired location as noted here.
As a workaround you can unset (disable) DownloadUser in /etc/pacman.conf, then it should work like usual in the /home directory.
#DownloadUser = alpm
So starting to manually alter the “package itself”? and lose this with next update? Sounds like a temporary workaround, I would rather not do.
I thought that there’s probably a good enough reason why they separated this to different user… so instantly disabling it would be like … bad idea?
Although I guess, it’s “better bad solution” (editing some config in /etc), than editing /usr/bin/autogit.
And I still like the read-only bind mount workaround as the “best bad solution” currently.
Could this DIR constant be brought into configuration file in a future update?
I will look into it when I find the time!
@deemon I’ve pushed a new release with a new option to sync repos to a custom location. This should solve any issues with pacman 7.
You may want to give it a try when its pushed to the Manjaro repo. Just be aware that this change will require a config file update, you will be prompted to merge the changes of the new “.conf”.
Happy building!
1 Like