Gpgme error arch

I am trying to update my system like so:

But I get the following errors:

error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
:: Synchronising package databases...
 core                                                                974.9 KiB  1134 KiB/s 00:01 [#########################################################] 100%
 extra                                                               974.9 KiB  1547 KiB/s 00:01 [#########################################################] 100%
 community                                                           974.9 KiB  1486 KiB/s 00:01 [#########################################################] 100%
error: GPGME error: No data
error: GPGME error: No data
error: GPGME error: No data
error: failed to synchronize all databases (invalid or corrupted database (PGP signature))

I tried:

sudo rm /var/lib/pacman/db.lck

But it says the file does not exist. Also:

sudo -E pacman -Sy archlinux-keyring

But it does nothing. How can I solve it please?

Update:
I also tried enabling most servers in:

vim /etc/pacman.d/mirrorlist

Update 2:
I also tried:

sudo rm -R /var/lib/pacman/sync

Update 3:
My /etc/pacman.conf

#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

#IgnorePkg   =
#IgnorePkg   =
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#TotalDownload
CheckSpace
#VerbosePkgLists

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Arch Linux
# packagers with `pacman-key --populate archlinux`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The testing repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[testing]
#Include = /etc/pacman.d/mirrorlist

[core]
Include = /etc/pacman.d/mirrorlist

[extra]
Include = /etc/pacman.d/mirrorlist

#[community-testing]
#Include = /etc/pacman.d/mirrorlist

[community]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the multilib repositories as required here.

#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist

#[multilib]
#Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs

Last edited by light9876 (2021-07-19 20:56:40)

Arch Linux

You are not logged in.

#1 2017-06-01 17:34:14

[SOLVED] pacstrap error: GPGME error: No data

I downloaded the latest iso (archlinux-2017.05.01-x86_64) today. When I try to pacstrap I get:

Any ideas? I tried pacman-key —init followed by pacman-key —populate but it didn’t help.

Last edited by tnek (2017-06-01 19:14:00)

#2 2017-06-01 18:07:18

Re: [SOLVED] pacstrap error: GPGME error: No data

Looks like you’re behind a captive portal or something. Open a CLI browser and make sure you can actually access the internet.

Online

#3 2017-06-01 18:21:53

Re: [SOLVED] pacstrap error: GPGME error: No data

Looks like you’re behind a captive portal or something. Open a CLI browser and make sure you can actually access the internet.

It doesn’t seem to be the problem. I did try ping which worked before I ran into the problem. Now I also tried surfing the web using elinks without any problem.

Last edited by tnek (2017-06-01 18:22:17)

#4 2017-06-01 18:24:48

Re: [SOLVED] pacstrap error: GPGME error: No data

Alright, then what does `file /mnt/var/lib/pacman/sync/core.db` tell you?

Online

#5 2017-06-01 18:49:24

Re: [SOLVED] pacstrap error: GPGME error: No data

Alright, then what does `file /mnt/var/lib/pacman/sync/core.db` tell you?

Hm. It seems to be the contents of a web page:

#6 2017-06-01 18:53:44

Re: [SOLVED] pacstrap error: GPGME error: No data

If you change mirrors does that allow the databases to be properly downloaded indicating it is just one mirror that is redirecting to that domain parking site.
If so which mirror was linking to that site?

#7 2017-06-01 19:13:36

Re: [SOLVED] pacstrap error: GPGME error: No data

If you change mirrors does that allow the databases to be properly downloaded indicating it is just one mirror that is redirecting to that domain parking site.
If so which mirror was linking to that site?

It was the following server (which was the first entry):

I commented it out and everything worked fine. Problem solved! Thanks guys!

Last edited by tnek (2017-06-01 19:14:53)

Источник

Arch Linux

You are not logged in.

#1 2014-03-29 21:41:33

[SOLVED] Pacman GPGME error: No data

I recently bought a new computer and, of course, wanted to get away from windows 8 asap. I’ve installed arch several times before, and this time, from the outset, I’ve been plagued with GPGME errors. First was during the installation when I tried to install the base system with pacstrap. I solved that using the method here: https://bbs.archlinux.org/viewtopic.php?id=142798 (essentially delete /var/lib/pacman/sync and then run pacman -Syyu). From there on out, the install proceeded happily. After booting into my system, I attempted to begin downloading and installing things such as openssh, gparted, virt-manager. etc. Now I get the same error that I had before.

As soon as this happened, I attempted to re initialize pacman and the keys with

This ran properly, but I was still unable to sync or update pacman. I then tried deleting /var/lib/pacman/sync and updating with the same result.
Next, I tried commenting out the mirrors, as that was mentioned in several posts while perusing the wiki. This still did not work. The next ting I tried was setting the SigLevel in the pacman.conf to Never, which brought about a whole host of different errors when trying to update (Unrecognized archive format error).

After reinitializing the keys again, deleting the /var/lib/pacman/sync folder and attempting another (unsuccessful) pacman -Syyu, and running pacman-key —refresh-keys, I set the SigLevel back to it’s default, and decided it might be time to post asking for help. Does anyone have any other ideas that I could try? I’ve been working on this unsuccessfully for a few hours now, and I’d like to see it up and running.

Thank you all in advance!

Searching the archwiki, I tried these threads for additional help:
https://bbs.archlinux.org/viewtopic.php … 2#p1111872 — had a problem in pacman conf I do not
https://bbs.archlinux.org/viewtopic.php?id=169225 —commenting out mirrors did not work
https://bbs.archlinux.org/viewtopic.php?id=135310 — did not help with archive errors
. and many many more that were totally unrelated despite similar titles to mine

Last edited by ephreal (2014-03-29 23:28:46)

Источник

Pacman troubleshooting

Содержание

Various issues relating to the download and installation of software packages from the Manjaro repositories are dealt with here.

«Unrecognized archive format» Error

It has ocurred more than once, an update is issuing these messages in a seemingly never ending stream. Pacman could not open file: sync files

The error relates to a mismatch in the information contained in the db files at the mentioned location and the db files at the first mirror in your mirrorlist. Pacman checks a package in the database and sees if the signature file matches the one in the database. If it does not, then pacman will say the package is corrupted.

While it sometimes is possible to fix the issue simply by deleting the files and the running a pacman update it far from every time.

One recipe for fixing this

It is mandatory to ensure that the keyrings is current. By ensuring the keyrings are in shape and then redownloading the databases we reestablish the chain of trust between the keyrings and the packages.

You will have to find the correct names by looking at

Replace yyyymmdd and x with the info found at the above links

Remove your faulty databases

Download the databases and update the system

«Unable to lock database» Error

When downloading and installing software from the repositories, a special database lock file will be created in order to ensure that the current installation process is the only one running at that time. Otherwise, attempting to install multiple files from multiple sources simultaneously may corrupt the downloaded files, cause file conflicts — or worse still — damage your system. Once the installation has been completed, the lock file will then be automatically deleted. This error may therefore occur due to two possible reasons:

• Another installation is still taking place and has not yet finished, or
• A previous installation attempt had not finished properly (e.g. due to being aborted early)

It is therefore wise to first check to ensure that another installation is not (or had not been) in process at the time of the error. When satisfied that this is not the case, then the database lock file can be manually deleted. To do so, open up the terminal and enter the following command:

Once done, you should now be able to successfully re-attempt your intended installation.

Errors about Keys

We all have our own unique signatures which are used to authenticate who we are and to prevent fraudulent or even malicious activities by others. This is also the case with software packages available from the software repositories. They all contain encrypted codes (signature keys) unique to their developers to ensure that they are authentic and not malicious in nature.

During the installation process, once any software packages have been downloaded, your system will first check their signature keys to ensure that they are authentic prior to actually installing them. If a signature key cannot be verified for any reason, then the installation process will be aborted. This problem will usually occur due to:

• one or more signature keys contained in your system’s database being revoked, changed, corrupted, or out of date
• one or more software packages not having been signed off properly when placed in a repository

Where a package has not been signed off properly before being placed in a repository, it will be the responsibility of the developer(s) to correct this. However, as this problem will be more than likely due to a problem with your system’s verification of a signiture key, this can be solved in three easy steps. Working net connection is required. Once you have opened your terminal:

1. Remove old (and possibly broken) keys by entering this command:

2. Reinstall keyrings including the latest keys:

3. Initialize the pacman keyring:

4. Load the signature keys:

5. Refresh and update the signature keys:

6. Clear out the software packages downloaded during the aborted installation (optional):

1. Remove old (and possibly broken) keys by entering this command:

2. Initialize the pacman keyring:

3. Download the packages:

Those running ARM may also need to download archlinuxarm-keyring and manjaro-arm-keyring.

4. Remove the signatures:

5. Install the downloaded packages manually:

6. Clear out the software packages downloaded during the aborted installation (optional):

7. Remove the custom package folder: (optional):

After that try running sudo pacman -Syu to see if the errors were resolved.

Conflicting files — FILENAME exists in filesystem

If you cant can’t install or update a package because of an error like this:

Then the package manager, pacman, has detected an unexpected file that already exists on the disk.

Why is this happening?

By design pacman will not overwrite files that already exist. This is a design feature, not a flaw — package managers are designed to keep track of installed files.

This issue normally happens because you’ve manually added, copied, or created a file. It can also happen when you install software using a downloaded executable, run a make install, or use a third-party package system such as conda. It also occurs when you install an AUR package which installs files that conflict with a repo package.

When using a third-party installer you should always specify an alternative installation location, such as under your home directory, or under /opt or /usr/local/. Never install directly under / or /usr.

How can I fix this?

The first step is to identify which, if any, package owns the file. This can be easily done with:

If this identifies a conflicting package you can decide to remove it with pacman -R. If no package is identified you can delete the file (or move it to a backup location).

Where can I read more?

This post was inspired by (and adapted from):

The above post also has links to further reading.

«Configuration file. not recognized» Error

Manjaro’s package manager — pacman — uses a file called mirrorlist to tell it the internet addresses of the Manjaro servers in order to download updates and software applications from them. This error will therefore occur if one or more server addresses contained in the mirrorlist file have not been listed properly, resulting in pacman being unable to connect to them. Another tell-tale sign is that this problem will also be encountered immediately after:

• Installing Manjaro and editing the mirrorlist file during installation, or
• Editing the mirrorlist file at a later time.

See the Change to a Different Download Server guide for more detailed information on how to correctly select and enable another Manjaro server for downloading.

«GPGME error: No data» Error

The most likely cause of this issue is that an error or corruption has been detected by pacman in one or more software packages being downloaded. Package signatures and checksums are used to verify the validity of downloaded software, and should they fail, the installation attempt will be aborted to protect your system until the matter is resolved.

Option 1: Basic Resolution

To resolve this issue, first follow the basic procedure provided below. If this does not work, then there is a more comprehensive procedure available.

1. Download the package databases and update your system:

2. Clear out the software packages downloaded during the aborted installation by entering the command:

3. Re-attempt the aborted download.

Option 2: Comprehensive Resolution

If the basic proceedure still does not resolve the matter, further steps are available:

1. Resynchronise with the Manjaro servers to ensure that everything is up to date by entering the command:

2. Refresh and update the signature keys by entering the command:

3. Reload the signature keys by entering the command:

4. Clear out the software packages downloaded during the aborted installation by entering the command:

5. Re-attempt the aborted download.

If the error still persists, then it is recommended to Change to a Different Download Server.

Источник

Arch Linux

You are not logged in.

#1 2012-06-06 03:16:23

[Solved] invalid or corrupted database (PGP signature)

When I try to run pacman -Syu, I get this error:

I have invoke the command pacman-key —init and pacman-key —populate archlinux as per instructed in the front page. Due to this problem, I am unable to upgrade any package, not until I set the SigLevel to Never. Here’s my pacman.conf if it’ll be any help.

Thanks in advance.

Last edited by teddypick3r (2012-06-13 21:30:09)

#2 2012-06-06 08:38:25

Re: [Solved] invalid or corrupted database (PGP signature)

Try commenting SigLevel = Optional TrustAll and uncommenting the SigLevel = PackageRequired for the individual repositories. Maybe changing the global SigLevel = PackageRequired also works, but I haven’t tried.
Look in pacman.conf.*new* (not sure about filename, it is created after the recent update) for an example like pacman said.

#3 2012-06-06 08:40:55

Re: [Solved] invalid or corrupted database (PGP signature)

Database signing hasn’t been implemented yet. Simply adding «DatabaseOptional» to your SigLevel line should take care of it.

#4 2012-06-06 09:22:28

Re: [Solved] invalid or corrupted database (PGP signature)

Hi, thanks for the replies.

I tried commenting out the global SigLevel, and also the suggestion of adding DatabaseOptional to my SigLevel, apparently both of them doesn’t solve my problem.

I try deleting the pacman.d/gnupg folder and re-init the pacman-key, the error still persists. any other idea?

#5 2012-06-06 12:35:49

Re: [Solved] invalid or corrupted database (PGP signature)

It would be strange that you still get pgp signature error when you’ve put «SigLevel = Never». Try doing a full database sync again (pacman -Syy).

#6 2012-06-06 13:34:53

Re: [Solved] invalid or corrupted database (PGP signature)

ah, maybe I didn’t explain myself well, sorry for that. What I mean is that the only way I can upgrade my system is by setting SigLevel to Never. I would love to implement package signing too.
What I’ve done is

1) add DatabaseOptional to SigLevel
2) deleted the pacman.d/gnupg and re-invoke pacman-key —init & pacman-key —populate archlinux

but the error still persists whenever I try to implement package signing.

#7 2012-06-06 15:32:48

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

There’s no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

#8 2012-06-06 15:53:22

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

that would be in the first post

#9 2012-06-06 16:34:09

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

that would be in the first post

what version of pacman are you running. One option would be to simply set siglevel to never and update pacman to the latest. Then merge the pacman.conf file with the pacman.conf.pacnew. Then re-run pacman-key —init and pacman-key —populate archlinux

The new version of pacman has signing enabled by default and has siglevel=PackageRequired on all the official repositories. You can still set globally if you want to later.

There’s no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

#10 2012-06-06 17:24:21

Re: [Solved] invalid or corrupted database (PGP signature)

Same problem here.

1) upgraded pacman
2) replaced pacman-conf with pacman.conf.new
3) tried everything from above

For some tasks, the CLI is quicker. That’s not elitism nor arrogance, that’s just a fact of life.

#11 2012-06-06 19:01:00

Re: [Solved] invalid or corrupted database (PGP signature)

Same problem here.

1) upgraded pacman
2) replaced pacman-conf with pacman.conf.new
3) tried everything from above

Vi0L0 is a user, not an Arch dev. To get his key, see his forum signature: https://bbs.archlinux.org/profile.php?id=26754

Edit: The address mentioned in his profile seems down, use http://pgp.mit.edu:11371/pks/lookup?op= … 2d653c3094

Last edited by karol (2012-06-07 00:01:16)

#12 2012-06-07 03:07:03

Re: [Solved] invalid or corrupted database (PGP signature)

show us your pacman.conf

that would be in the first post

what version of pacman are you running. One option would be to simply set siglevel to never and update pacman to the latest. Then merge the pacman.conf file with the pacman.conf.pacnew. Then re-run pacman-key —init and pacman-key —populate archlinux

The new version of pacman has signing enabled by default and has siglevel=PackageRequired on all the official repositories. You can still set globally if you want to later.

I’m using the latest pacman 4.0.3-2. I did merge the pacman.conf.pacnew with the old one. I try re-run pacman-key -init and pacman-key —populate archlinux for quite a few times already yet the error persists.

#13 2012-06-07 19:41:32

Re: [Solved] invalid or corrupted database (PGP signature)

I was having the same problem.

I tried all the steps above but the only thing that helped me was changing mirrors.

I just started commenting them out in mirrorlist and finally it started working.

-ed+
But i should add, the only time it will perform package operations now I’m getting a 550 error:

Last edited by bioe007 (2012-06-07 19:50:44)

#14 2012-06-08 04:56:58

Re: [Solved] invalid or corrupted database (PGP signature)

I did try changing the mirror, yet the problem still persists. is the mirror affect the error? because I thought package signing is implemented on package level..

Last edited by teddypick3r (2012-06-08 05:03:59)

#15 2012-06-10 18:21:36

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

#16 2012-06-10 22:48:17

Re: [Solved] invalid or corrupted database (PGP signature)

the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

#17 2012-06-11 02:18:03

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

I tried, but doesn’t solve the problem for me

#18 2012-06-13 09:56:09

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same problem. It’s fixed now, but I don’t know what worked exactly.
What I did was replace my pacman.conf with one from colleague who did not have this problem. Global SigLevel was commented and repos have had their level set to PackageRequired in his conf file.
After running

with database update in the end

it started working. I have no idea what fixed it, but if you’re out of options you might want to reproduce it the way I did.

The weird thing is running the three commands by themselves was not fixing the issue a couple of days back.

#19 2012-06-13 17:18:05

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

I tried, but doesn’t solve the problem for me

I think the problem You are getting are caused by your custom XferCommand.
It seems pacman will always try to fetch the sig file for the db, even if key signing has not been enabled (BUG?). If your Xfer script leaves something behind when a file on the server is not found, that file will be used as a sig file. It will obviously not be a valid key file.
If you use something like curl in your script, it will create a HTML file when the file on the server is not found.

Check the files in /var/lib/pacman/sync. You shouldnt have any .db.sig files here.
You probably have .db.sig files here containing HTML code.

Make sure your Xfer script do not create .db.sig files.
Also make sure the script exits with a fault code when the file can not be found on the server.

The cake is a lie

#20 2012-06-13 21:29:50

Re: [Solved] invalid or corrupted database (PGP signature)

I had the same issue too. I managed to fix it by ]running the command found under the header «Master Keys» of the pacman-key page: https://wiki.archlinux.org/index.php/Pacman-key

I tried, but doesn’t solve the problem for me

I think the problem You are getting are caused by your custom XferCommand.
It seems pacman will always try to fetch the sig file for the db, even if key signing has not been enabled (BUG?). If your Xfer script leaves something behind when a file on the server is not found, that file will be used as a sig file. It will obviously not be a valid key file.
If you use something like curl in your script, it will create a HTML file when the file on the server is not found.

Check the files in /var/lib/pacman/sync. You shouldnt have any .db.sig files here.
You probably have .db.sig files here containing HTML code.

Make sure your Xfer script do not create .db.sig files.
Also make sure the script exits with a fault code when the file can not be found on the server.

Ah, at last. Thanks for your suggestion. Seems like the custom XferCommand is really the culprit after all. After I commenting it out, the package signing works flawlessly. Marked the thread as solved. Thanks again.

Источник