is this a test version?above v0.3.1 is not on the download page

You can install v0.4 using v0.3.1 iso. You have to enable testing repo as mentioned at
https://forums.hyperbola.info/viewtopic … 3860#p3860

Well, the packages of v0.3.1 are really old, and few in number. v0.4 is way more functional due to many more packages, but typically if you use a desktop environment(DE), using lumina which is compulsory DE for v0.4 is a step down compared to user experience of plasma, or equivalent DEs. However, you experience the beauty of minimalism.

If you're willing to shift to window managers, v0.4 is definitely amazing and has a lot of options!

Installation instructions are the same as that of v0.3.1

It just means that all keys aren't available on both keyservers. A couple are available here and there.

so everyone has a problem with that now?

v0.4

is this a test version?above v0.3.1 is not on the download page

throgh wrote:

To host an own keyserver is a little bit more complicated. First we need to find a fitting application especially for that. When looking at the development available I get mostly implementations with Rust or Go, which would be not possible or even more complicated (in regards for Go as language).

I'm not suggesting hosting a keyserver. Just having each member's public key as a static page on website like my public key at
https://designman.org/sagar/static/saga … ic_key.txt

Then one can do something like

curl https://designman.org/sagar/static/sagaracharya_public_key.txt | gpg --import 

And perhaps edit a bit of pacman code for importing that way too. It would also improve decentralization of public keys.

Well, there are some parts to be thought of and I'm not sure if this could be done right from the start. Also when editing that part of pacman, we would have even more to modify as the software is no longer compatible with upstream-logic for PGP-verification.

In general: As rachad has written to circumvent that part the configuration-option "SigLevel = Never" can be used for version 0.3.1.

What are you installing? v0.3.1 or v0.4?

v0.3.1

To host an own keyserver is a little bit more complicated. First we need to find a fitting application especially for that. When looking at the development available I get mostly implementations with Rust or Go, which would be not possible or even more complicated (in regards for Go as language).

I'm not suggesting hosting a keyserver. Just having each member's public key as a static page on website like my public key at
https://designman.org/sagar/static/saga … ic_key.txt

Then one can do something like

curl https://designman.org/sagar/static/sagaracharya_public_key.txt | gpg --import 

And perhaps edit a bit of pacman code for importing that way too. It would also improve decentralization of public keys.

@throgh Do you think we should atleast shift all hyperbola signing keys to hyperbola's own servers so we don't trust keyservers anymore? Such problems would vanish for hyperbola's dev public keys.

To host an own keyserver is a little bit more complicated. First we need to find a fitting application especially for that. When looking at the development available I get mostly implementations with Rust or Go, which would be not possible or even more complicated (in regards for Go as language).

What are you installing? v0.3.1 or v0.4?

@throgh Do you think we should atleast shift all hyperbola signing keys to hyperbola's own servers so we don't trust keyservers anymore? Such problems would vanish for hyperbola's dev public keys.

hkp://keyring.debian.org:
pacman-key --refresh-keys
gpg: refreshing 77 keys from hkp://keyring.debian.org
gpg: no valid openPGP data found.
gpg: key 16x1: 101 signature not checked due to a missing keys
gpg: key 16x1: "Felix Yan <felixonmars@archlinux.org>" 2 new missing IDs
gpg: key 16x1: "Felix Yan <felixonmars@archlinux.org>" 103 new signatures
gpg: no valid openPGP data found.
gpg: no valid openPGP data found.
gpg: Total number processed: 1
gpg:           new user IDs: 2
gpg:         new signatures: 103
gpg: key 16x1: no user ID for key signature packet of class 10
gpg: key 16x1: no user ID for key signature packet of class 10
gpg: key 16x1: no user ID for key signature packet of class 10
gpg: key 16x1: no user ID for key signature packet of class 10
gpg: key 16x2: no user ID for key signature packet of class 10
gpg: key 16x2: no user ID for key signature packet of class 10
gpg: key 16x2: no user ID for key signature packet of class 10
gpg: key 16x2: no user ID for key signature packet of class 10
gpg: key 16x2: 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:  62  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1  valid:  62  signed:  5  trust: 0-, 0q, 0n, 62m, 0f, 0u
gpg: next trustdb cheak due at 2022-12-30
==> ERROR: A specified local key could not be updated from a keyserver.