Skip to content

Conversation

bluca
Copy link
Member

@bluca bluca commented Aug 19, 2025

It gets stuck on my machine:

==> Generating pacman master key. This may take some time. gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/EB164F6892020464A09A4A6B7E2D4967893A191E.rev' gpg: Done
==> Updating trust database...
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from archlinux.gpg...
==> Appending keys from debian-archive-bookworm-automatic.gpg...
==> Appending keys from debian-archive-bookworm-security-automatic.gpg...
==> Appending keys from debian-archive-bookworm-stable.gpg...
==> Appending keys from debian-archive-bullseye-automatic.gpg...
==> Appending keys from debian-archive-bullseye-security-automatic.gpg...
==> Appending keys from debian-archive-bullseye-stable.gpg...
==> Appending keys from debian-archive-keyring.gpg...
==> Appending keys from debian-archive-removed-keys.gpg...
==> Appending keys from debian-archive-trixie-automatic.gpg...
==> Appending keys from debian-archive-trixie-security-automatic.gpg...
==> Appending keys from debian-archive-trixie-stable.gpg...
==> Appending keys from debian-keyring.gpg...

Avoid calling it when --repository-key-check=no is used, as there's no point anyway, it won't be used

@DaanDeMeyer
Copy link
Contributor

The keyring is cached, so we'd have to make add the value of this option to the cache manifest to make sure the cache is rebuilt when the value of this option is changed, which I'd prefer not to do.

I guess it getting stuck is related to Arch getting DDOSed?

@bluca
Copy link
Member Author

bluca commented Aug 21, 2025

That's possible but don't know for sure, that's all the output I get

It gets stuck on my machine:

==> Generating pacman master key. This may take some time.
gpg: Generating pacman keyring master key...
gpg: directory '/etc/pacman.d/gnupg/openpgp-revocs.d' created
gpg: revocation certificate stored as '/etc/pacman.d/gnupg/openpgp-revocs.d/EB164F6892020464A09A4A6B7E2D4967893A191E.rev'
gpg: Done
==> Updating trust database...
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
==> Appending keys from archlinux.gpg...
==> Appending keys from debian-archive-bookworm-automatic.gpg...
==> Appending keys from debian-archive-bookworm-security-automatic.gpg...
==> Appending keys from debian-archive-bookworm-stable.gpg...
==> Appending keys from debian-archive-bullseye-automatic.gpg...
==> Appending keys from debian-archive-bullseye-security-automatic.gpg...
==> Appending keys from debian-archive-bullseye-stable.gpg...
==> Appending keys from debian-archive-keyring.gpg...
==> Appending keys from debian-archive-removed-keys.gpg...
==> Appending keys from debian-archive-trixie-automatic.gpg...
==> Appending keys from debian-archive-trixie-security-automatic.gpg...
==> Appending keys from debian-archive-trixie-stable.gpg...
==> Appending keys from debian-keyring.gpg...

Avoid calling it when --repository-key-check=no is used, as there's no
point anyway, it won't be used
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants