CORE.DB.SIG - extra.db.sig - community.db.sig

amsmts1 · 2021-12-21 17:48:13

- May I ask when are these files created during installation?
- Could they be recreated without rebuilding the system?

I guess I am looking for a better handle on these files. I understand application signatures and keys to verify applications. I tracked down an issue on my system. THESE FILES ARE NON-EXISTENT.

"sudo pacman -Tv --debug" returned

debug: database path for tree core set to /var/lib/pacman/sync/core.db
debug: "/var/lib/pacman/sync/core.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/core.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 593) : missing PGP signature
debug: missing optional signature

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.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/extra.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 593) : missing PGP signature
debug: missing optional signature

debug: registering sync database 'community'
debug: database path for tree community set to /var/lib/pacman/sync/community.db
debug: "/var/lib/pacman/sync/community.db.sig" is not readable: No such file or directory
debug: sig path /var/lib/pacman/sync/community.db.sig could not be opened
debug: got error 43 at _alpm_gpgme_checksig (../lib/libalpm/signing.c: 593) : missing PGP signature
debug: missing optional signature

SEARCHED OUT that the files are not there. Only discovered this via the "Add/Remove Software". The sudo pacman -Syu Completes fine. HOWEVER, using the "Add/Remove Software" menu option in the System menu... In there I get an 'invalid or corrupted database (PGP signature)' when I attempt to refresh the databases..... What did I break?

Last edited by amsmts1 (2021-12-21 18:26:39)

WorMzy · 2021-12-21 18:16:27

Repository DB signatures are used to verify the database you download from the mirror hasn't been tampered with, similar to the package signatures. They are downloaded from the repository mirror when you refresh your sync DBs (i.e. `pacman -Syu`).

The official Arch Linux repository DBs are not currently signed, and by default Arch configures pacman to treat them as optional.

arojas · 2021-12-21 18:34:36

You can't find those sig files because they don't exist. What exactly is "the Add/Remove Software menu option in the System menu"?

amsmts1 · 2021-12-21 18:59:06

What do you mean they don't exit. I know they're not on my machine. Are you saying they never did exist?

GNome Desktop Enviroment
Right-click, Applications, System, Add/Remove Software.....

Last edited by amsmts1 (2021-12-21 19:04:15)

Trilby · 2021-12-21 19:23:41

amsmts1 wrote:

- May I ask when are these files created during installation?

They aren't.

amsmts1 wrote:

- Could they be recreated without rebuilding the system?

Non-sequitor. Creating them has nothing to do with rebuilding your system. The arch devs would need to create them, not you.

amsmts1 wrote:

I tracked down an issue on my system. THESE FILES ARE NON-EXISTENT.

Putting these sentences next to each other implies a connection between them: there isn't one. If you think the problem on your system is due to the absence of these files, you are wrong.

amsmts1 wrote:

What did I break?

Nothing.

amsmts1 wrote:

What do you mean they don't exit. I know they're not on my machine. Are you saying they never did exist?

Yes, they never did exist. They've never been created. They do not exist on any arch system (ok, maybe some devs are testing them on their systems, but if they are that's an exception ... they don't exist on "normal" arch systems).

Read the link you were provided in the very first reply.

Last edited by Trilby (2021-12-21 19:25:49)

amsmts1 · 2021-12-21 19:33:32

Trilby wrote:

amsmts1 wrote:
- May I ask when are these files created during installation?
They aren't.
amsmts1 wrote:
- Could they be recreated without rebuilding the system?
Non-sequitor. Creating them has nothing to do with rebuilding your system. The arch devs would need to create them, not you.
amsmts1 wrote:
I tracked down an issue on my system. THESE FILES ARE NON-EXISTENT.
Putting these sentences next to each other implies a connection between them: there isn't one. If you think the problem on your system is due to the absence of these files, you are wrong.
amsmts1 wrote:
What did I break?
Nothing.
amsmts1 wrote:
What do you mean they don't exit. I know they're not on my machine. Are you saying they never did exist?
Yes, they never did exist. They've never been created. They do not exist on any arch system (ok, maybe some devs are testing them on their systems, but if they are that's an exception ... they don't exist on "normal" arch systems).
Read the link you were provided in the very first reply.

Thank You Very Much.

amsmts1 · 2021-12-21 19:40:25

I did read the link... I also am attempting to find a solution to this Add/Remove Software options error. Alice lead me to a Rabbit hole pointing to areas that didn't make sense. So, with the collected information I attempted to create a question that would lead to a result.

Now that the initial question has been answered. With the tidbits of information I have gathered here. I will clutter up this forum with the rephrased question.

My ignorance has lead to a broader understanding to the unresolved issue... Thank you all for your help...

amsmts1 · 2021-12-21 20:44:12

So, the issue still exists. The FILES NEVER EXISTED, Why is the command 'sudo pacman -Tv --debug' return that it somehow needs them or refers to them in the debug output?

Something seems to have entered a reference to them somewhere. I would now think the 'db' files do that somehow.

I did read the link and it didn't seem to reveal the answer to me thru my thickness......

Trilby · 2021-12-21 20:47:14

amsmts1 wrote:

So, the issue still exists. The FILES NEVER EXISTED, Why is the command 'sudo pacman -Tv --debug' return that it somehow needs them or refers to them in the debug output?

Because it's debug output. As you stated yourself, your normal pacman commands work fine, right? There is no problem with pacman. Apparently you are having some issue with some GUI software that appears to have a setting requiring those files. Check whether the configuration for that software can set the db signatures to optional as pacman does - if there is no such setting, file a bug report with the author of that GUI tool.

Have you installed gnome-software-packagekit-plugin? What's the output from `pacman -Q gnome-software-packagekit-plugin`?

Last edited by Trilby (2021-12-21 20:49:54)

amsmts1 · 2021-12-21 21:05:12

I uninstalled PAMAN and the GUI issue is solved. My initial request was fragmented. PAMAN has nothing to do with the above DEBUG results from the pacman -T command above

Arch Linux

#1 2021-12-21 17:48:13

CORE.DB.SIG - extra.db.sig - community.db.sig

#2 2021-12-21 18:16:27

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#3 2021-12-21 18:34:36

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#4 2021-12-21 18:59:06

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#5 2021-12-21 19:23:41

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#6 2021-12-21 19:33:32

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#7 2021-12-21 19:40:25

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#8 2021-12-21 20:44:12

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#9 2021-12-21 20:47:14

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

#10 2021-12-21 21:05:12

Re: CORE.DB.SIG - extra.db.sig - community.db.sig

Board footer