INSTALLED_DB error during update

Issues & Assistance
1

About half the packages I have installed seem to be issueing this complaint today. I’ve not seen this one before, but my inclination is to wait and see :wink:
warning: alsa-ucm-conf: unknown key ‘%INSTALLED_DB%’ in local database
warning: archlinux-keyring: unknown key ‘%INSTALLED_DB%’ in local database

2

Whoops, I accidentally let it update…and those messages disappeared afterwards.

3

It shouldn’t be accidental. After every new installation, the first thing to do is update the system.

4

CachyOS is online installation, there usually isn’t any packages to update straight after installation.

5

This isn’t a new installation…this was just a std update.

6

So, I guess no one knows what this error means? I thought perhaps it was some updated pacman configuration causing a one-time error?

7

Hm, could this be because of the differences between Arch pacman and CachyOS pacman?

I found this article

Where it says

ATTENTION: Installing the CachyOS Pacman, will install a forked pacman with features added from CachyOS, like “INSTALLED_FROM” and an automatic architecture check.

So maybe you used the Arch pacman on a CachyOS database, just guessing,

8

Well if so it wasn’t done by manual action (save paru -Syu).

9

What does pacman -Qi pacman say?

For my CachyOS pacman it says:

Installed From  : cachyos
Name            : pacman
Version         : 7.0.0.r3.gf3211df-3.1
Description     : A library-based package manager with dependency support. CachyOS fork.
Architecture    : x86_64
URL             : https://www.archlinux.org/pacman/
Licenses        : GPL-2.0-or-later
[...]

Notice the description.

10

It matches what you have shown, though it also says packager is cachyos.

11

Out of ideas then :smile:

12

I think it was something transient, but I’m trying to understand where it came from (just in case)…thanks for trying Deex!

1 Like