Yes. I was wrong.
Search inside local and sync. Don’t do anything I wouldn’t.
Don’t do anything I wouldn’t.
I can only try … 
/var/lib/pacman/sync
total 8364
drwxr-xr-x 1 root root 140 Jun 16 19:40 .
drwxr-xr-x 1 root root 18 Jun 16 19:40 ..
-rw-r--r-- 1 root root 45 May 20 2023 community.db
-rw-r--r-- 1 root root 123974 Jun 16 09:51 core.db
-rw-r--r-- 1 root root 7638 Jun 16 19:40 endeavouros.db
-rw-r--r-- 1 root root 7638 Jun 16 19:40 endeavouros.db.sig
-rw-r--r-- 1 root root 8272987 Jun 16 19:11 extra.db
-rw-r--r-- 1 root root 141726 Jun 16 09:06 multilib.db
Is it safe to delete all the .db files here?
I can only guess (from RTFM).
So I did that, refreshed the mirrorlist and ran an update, and got the following error:
error: GPGME error: No data
:: Synchronizing package databases...
endeavouros 15.5 KiB 676 KiB/s 00:00 [---------------------------------------------------------------------------------------] 100%
core 121.1 KiB 117 KiB/s 00:01 [---------------------------------------------------------------------------------------] 100%
extra 7.9 MiB 1024 KiB/s 00:08 [---------------------------------------------------------------------------------------] 100%
community 45.0 B 90.0 B/s 00:01 [---------------------------------------------------------------------------------------] 100%
multilib 138.4 KiB 134 KiB/s 00:01 [---------------------------------------------------------------------------------------] 100%
error: failed retrieving file 'endeavouros.db' from mirror.nimatarlani.com : Failed to connect to mirror.nimatarlani.com port 443 after 10002 ms: Timeout was reached
error: GPGME error: No data
error: failed to synchronize all databases (unexpected error)
Seeing that the nimatarlani mirror has been problematic lately, I deleted it from the endeavouros mirrorlist and ran an update again:
error: GPGME error: No data
:: Synchronizing package databases...
endeavouros 15.5 KiB 83.1 KiB/s 00:00 [---------------------------------------------------------------------------------------] 100%
core 121.1 KiB 119 KiB/s 00:01 [---------------------------------------------------------------------------------------] 100%
extra 7.9 MiB 2.36 MiB/s 00:03 [---------------------------------------------------------------------------------------] 100%
community 45.0 B 86.0 B/s 00:01 [---------------------------------------------------------------------------------------] 100%
multilib 138.4 KiB 137 KiB/s 00:01 [---------------------------------------------------------------------------------------] 100%
error: GPGME error: No data
error: failed to synchronize all databases (unexpected error)
I read a bit of the Arch wiki that @petsam posted, which mentioned that the .db files should be gzip-compressed; when I checked the filetypes, I got the following readout:
file /var/lib/pacman/sync/*
/var/lib/pacman/sync/community.db: gzip compressed data, from Unix, original size modulo 2^32 10240
/var/lib/pacman/sync/core.db: gzip compressed data, from Unix, original size modulo 2^32 593920
/var/lib/pacman/sync/endeavouros.db: XZ compressed data, checksum CRC64
/var/lib/pacman/sync/endeavouros.db.sig: HTML document, ASCII text, with very long lines (4070)
/var/lib/pacman/sync/extra.db: gzip compressed data, from Unix, original size modulo 2^32 32942080
/var/lib/pacman/sync/multilib.db: gzip compressed data, from Unix, original size modulo 2^32 655360
is the issue that the endeavouros.db file is xz compressed?
Your EnOS sync database seems to be “corrupted” / not correctly dowloaded.
Every file in the sync directory should be gzip compressed data.
There have been a few users recently having this issue.
You would need to correct your /etc/pacman.d/endeavouros-mirrorlist.
See for example here:
Also the [community] repo doesn’t exist anymore.
Remove it from /etc/pacman.conf.
2 Likes
Thank you so much!
Removed the [community] repo too
1 Like
You are welcome! Glad your issue is finally resolved!
It was a collective effort from the community.
2 Likes
Please note that command
eos-update --clear-databases
also deletes those db files.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.