We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello :)
I'm getting errors i didn't have a few days/weeks ago, i've tried a few (a lot 😁) other mirror with the same result.
Tested using ./arch-bootstrap.sh -a x86_64 /chroot on a debian 10 but i got the same from a ubuntu system:
./arch-bootstrap.sh -a x86_64 /chroot
(...) --- configure DNS and pacman --- install packages: acl archlinux-keyring attr brotli bzip2 curl expat glibc gpgme libarchive libassuan libgpg-error libnghttp2 libnghttp3 libssh2 lzo openssl pacman pacman-mirrorlist xz zlib krb5 e2fsprogs keyutils libidn2 libunistring gcc-libs lz4 libpsl icu libunistring zstd filesystem base coreutils bash grep gawk file tar gzip systemd sed :: Synchronizing package databases... error: failed to synchronize all databases (unexpected error)
Using pacman's --debug, i get these errors
--debug
"/var/lib/pacman/sync/core.db" is not readable: No such file or directory
Any idea of what changed to cause this ?
Full debug log:
--- install packages: acl archlinux-keyring attr brotli bzip2 curl expat glibc gpgme libarchive libassuan libgpg-error libnghttp2 libnghttp3 libssh2 lzo openssl pacman pacman-mirrorlist xz zlib krb5 e2fsprogs keyutils libidn2 libunistring gcc-libs lz4 libpsl icu libunistring zstd filesystem base coreutils bash grep gawk file tar gzip systemd sed debug: config: arch: x86_64 debug: pacman v7.0.0 - libalpm v15.0.0 debug: config: new section 'options' debug: config: HoldPkg: pacman debug: config: HoldPkg: glibc debug: config: Architecture: auto debug: config: arch: x86_64 debug: config: sandboxuser: alpm debug: config: SigLevel: Never debug: config: LocalFileSigLevel: Optional debug: config: new section 'core' debug: config file /etc/pacman.conf, line 78: including /etc/pacman.d/mirrorlist debug: config: new section 'extra' debug: config file /etc/pacman.conf, line 84: including /etc/pacman.d/mirrorlist debug: config: finished parsing /etc/pacman.conf debug: setup_libalpm called debug: option 'logfile' = /var/log/pacman.log debug: option 'gpgdir' = /etc/pacman.d/gnupg/ debug: option 'hookdir' = /etc/pacman.d/hooks/ debug: option 'cachedir' = /var/cache/pacman/pkg/ debug: registering sync database 'core' debug: database path for tree core set to /var/lib/pacman/sync/core.db debug: "/var/lib/pacman/sync/core.db" is not readable: No such file or directory debug: setting usage of 15 for core repository debug: adding new server URL to database 'core': http://mirrors.kernel.org/archlinux/core/os/x86_64 debug: registering sync database 'extra' debug: database path for tree extra set to /var/lib/pacman/sync/extra.db debug: "/var/lib/pacman/sync/extra.db" is not readable: No such file or directory debug: setting usage of 15 for extra repository debug: adding new server URL to database 'extra': http://mirrors.kernel.org/archlinux/extra/os/x86_64 debug: option 'sandboxuser' = alpm :: Synchronizing package databases... error: failed to synchronize all databases (unexpected error) debug: unregistering database 'local' debug: unregistering database 'core' debug: unregistering database 'extra'
The text was updated successfully, but these errors were encountered:
This commit from ruanformigoni's fork fixed it for me: ruanformigoni@d6ce39c
(thanks @ruanformigoni !)
Sorry, something went wrong.
No problem! I thought it was only happening in my fork 😵💫
No branches or pull requests
Hello :)
I'm getting errors i didn't have a few days/weeks ago, i've tried a few (a lot 😁) other mirror with the same result.
Tested using
./arch-bootstrap.sh -a x86_64 /chroot
on a debian 10 but i got the same from a ubuntu system:Using pacman's
--debug
, i get these errorsAny idea of what changed to cause this ?
Full debug log:
The text was updated successfully, but these errors were encountered: