Chaotic-keyring and chaotic-mirrorlist packages missing

This morning I woke up to see this

:: Searching AUR for updates...
 -> Missing AUR Packages:  chaotic-keyring  chaotic-mirrorlist
 -> Flagged Out Of Date AUR Packages:  libeb

The out of date package libeb is normal but for some reason the chaotic-aur packages are missing. I redid the steps on the chaotic website and it hasn’t fixed it.
Will this be solved in a few days?

Try to reinstall:

sudo pacman -U 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-keyring.pkg.tar.zst' 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-mirrorlist.pkg.tar.zst

edit: That is, if it is active in the pacman.conf file.

Is chaotic-AUR activated? If that is not the case, those packages will be shown as missing.

2 Likes

How to use it?

First, install the primary key - it can then be used to install our keyring and mirrorlist.
$ pacman-key --recv-key FBA220DFC880C036 --keyserver keyserver.ubuntu.com
$ pacman-key --lsign-key FBA220DFC880C036
$ pacman -U 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-keyring.pkg.tar.zst' 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-mirrorlist.pkg.tar.zst'

Append (adding to the end of the file) to /etc/pacman.conf:
[chaotic-aur]
Include = /etc/pacman.d/chaotic-mirrorlist

The commands need to be run with sudo.

$ should have been # in the instructions at https://aur.chaotic.cx/

+1

It looks like the chaotic repo is no longer in your pacman.conf.

1 Like

I normally don’t bother editing pacman.conf. I use octopi, which offers the option to edit your repository list. Easy way to check and edit.

I already said that I followed all the steps on the chaotic aur website, redoing them doesn’t fix it. the chaotic repo is in my pacman.conf and it does appear in the repo list when I Syu

I did try that already. It does reinstall the packages but they’re still Missing when I update

[matt@mpc ~]$ sudo pacman -U 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-keyring.pkg.tar.zst' 'https://cdn-mirror.chaotic.cx/chaotic-aur/chaotic-mirrorlist.pkg.tar.zst'
loading packages...
warning: chaotic-keyring-20210617-2 is up to date -- reinstalling
warning: chaotic-mirrorlist-20211231-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (2)         Old Version  New Version  Net Change

chaotic-keyring     20210617-2   20210617-2     0.00 MiB
chaotic-mirrorlist  20211231-1   20211231-1     0.00 MiB

Total Installed Size:  0.02 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                                                                        [------------------------------------------------------------] 100%
(2/2) checking package integrity                                                                      [------------------------------------------------------------] 100%
(2/2) loading package files                                                                           [------------------------------------------------------------] 100%
(2/2) checking for file conflicts                                                                     [------------------------------------------------------------] 100%
:: Processing package changes...
(1/2) reinstalling chaotic-keyring                                                                    [------------------------------------------------------------] 100%
==> Appending keys from chaotic.gpg...
==> Updating trust database...
gpg: next trustdb check due at 2022-05-06
==> Updating trust database...
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:  11  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  11  signed:  94  trust: 1-, 0q, 0n, 10m, 0f, 0u
gpg: depth: 2  valid:  87  signed:  33  trust: 87-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2022-05-06
(2/2) reinstalling chaotic-mirrorlist                                                                 [------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Checking which packages need to be rebuilt
(3/3) Updating statusbar...

In that case it is probably either an issue with your chaotic mirror or with chaotic-aur itself.

2 Likes

I’ve updated the mirror so it must be with the chaotic aur itself
Could someone else test this?

At least this works:
https://shantitribe.eu/chaotic-aur/x86_64/ (<- Don’t use this.)
Switch to another mirror.

How do I do that?

edit /etc/pacman.d/chaotic-mirrorlist

Nope, it must be a problem with the chaotic aur and not my mirror

You may be right. Something strange:

[xxx@arch tmp]$ rankmirrors -t chaotic-mirrorlist
Querying servers. This may take some time...
   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *   *
 Servers sorted by time (seconds):
https://bg-mirror.chaotic.cx/$repo/$arch : unreachable
https://br-mirror.chaotic.cx/$repo/$arch : unreachable
https://ca-mirror.chaotic.cx/$repo/$arch : unreachable
https://cdn-mirror.chaotic.cx/$repo/$arch : unreachable
https://de-2-mirror.chaotic.cx/$repo/$arch : unreachable
https://de-3-mirror.chaotic.cx/$repo/$arch : unreachable
https://de-4-mirror.chaotic.cx/$repo/$arch : unreachable
https://de-mirror.chaotic.cx/$repo/$arch : unreachable
https://es-2-mirror.chaotic.cx/$repo/$arch : unreachable
https://es-mirror.chaotic.cx/$repo/$arch : unreachable
https://fr-mirror.chaotic.cx/$repo/$arch : unreachable
https://geo-mirror.chaotic.cx/$repo/$arch : unreachable
https://in-2-mirror.chaotic.cx/$repo/$arch : unreachable
https://in-mirror.chaotic.cx/$repo/$arch : unreachable
https://kr-mirror.chaotic.cx/$repo/$arch : unreachable
https://us-ca-mirror.chaotic.cx/$repo/$arch : unreachable
1 Like

odd, it tells me chaotic-mirrorlist doesn’t exist even though it does when I use that command

https://status.chaotic.cx/

2 Likes

Thank you. :grinning:

1 Like

Do I just wait until it’s fixed then?

I guess there is not much we can do now. The issue need to be resolved on their end.

1 Like