[pacman-dev] "pacman --arch=i686 -Syu" results in "error: GPGME error: No data"
# pacman --arch=i686 -Syu This is clearly not a sensible command, but trying it just to see what happened when using the --arch option out resulted in database corruption, then it was impossible to upgrade and pacman would not function: error: GPGME error: No data error: failed to synchronize all databases (unexpected error) until I did: # rm /var/lib/pacman/sync/* # pacman-key --init # pacman-key --populate archlinux artix # pacman -Syy I tried it again and it did the same thing, and thought you might be interested.
On 6/2/21 7:55 PM, stratus--- via pacman-dev wrote:
# pacman --arch=i686 -Syu This is clearly not a sensible command, but trying it just to see what happened when using the --arch option out resulted in database corruption, then it was impossible to upgrade and pacman would not function: error: GPGME error: No data error: failed to synchronize all databases (unexpected error) until I did: # rm /var/lib/pacman/sync/* # pacman-key --init # pacman-key --populate archlinux artix> # pacman -Syy I tried it again and it did the same thing, and thought you might be interested.
This works fine for me, I got lots of 404 errors for the resulting *.db downloads and nothing else occurred. Some people reported on some mirrors that 404 pages were getting erroneously saved to .part files before going to the next mirror. But I would not expect this to affect databases since we don't try to resume downloading a database... I'm not sure how else you could get junk info in the database files. Your report is missing necessary debug information: what are the contents of an example .db and .db.sig which report this error? Also: what's the entire error, rather than 2 snipped out lines? -- Eli Schwartz Bug Wrangler and Trusted User
On 3/6/21 9:55 am, stratus--- via pacman-dev wrote:
# pacman --arch=i686 -Syu This is clearly not a sensible command, but trying it just to see what happened when using the --arch option out resulted in database corruption, then it was impossible to upgrade and pacman would not function: error: GPGME error: No data error: failed to synchronize all databases (unexpected error) until I did: # rm /var/lib/pacman/sync/* # pacman-key --init # pacman-key --populate archlinux artix # pacman -Syy I tried it again and it did the same thing, and thought you might be interested. .
I can not replicate:
pacman --arch=i686 -Syu :: Synchronizing package databases... core.db failed to download extra.db failed to download community.db failed to download error: failed retrieving file 'extra.db' from syd.mirror.rackspace.com : Could not resolve host: syd.mirror.rackspace.com warning: too many errors from syd.mirror.rackspace.com, skipping for the remainder of this transaction error: failed retrieving file 'community.db' from syd.mirror.rackspace.com : Could not resolve host: syd.mirror.rackspace.com error: failed retrieving file 'core.db' from syd.mirror.rackspace.com : Could not resolve host: syd.mirror.rackspace.com error: failed to synchronize all databases (invalid url for server)
Allan
participants (3)
-
Allan McRae
-
Eli Schwartz
-
stratus＠tuta.io