Hello Malsasa,

thanks for the feedback onto those issues. For now this would be only my personal assumption but I think the stable ISO has issues with installation as the packages wget and curl were too old and we have upgraded them - without a newer ISO-file. I'll take that assumption and speak with the team, so we see if we can bring a solution towards that problem for installation.

For now I would recommend a dirty workaround and to modify your pacman.conf as follows for the packages:

[core]
SigLevel = Never
Include = /etc/pacman.d/mirrorlist

[extra]
SigLevel = Never
Include = /etc/pacman.d/mirrorlist

[community]
SigLevel = Never
Include = /etc/pacman.d/mirrorlist

[multilib]
SigLevel = Never
Include = /etc/pacman.d/mirrorlist

The reasoning is more or less very simple: We are a very small team and have most of our time invested into our upcoming release 0.4. This does not mean we don't want be aware of problems with the last stable release 0.3.1 for sure. It is just the missing time for everything. So coming to the next problem you are describing: The websearch for the packages only shows the concurrent testing-version, not the stable one. Also here the reasoning: The community needs insights for the packages and the final result in the package-database. So we can also see where is something missing, marked as optional dependency for example. We don't follow a rolling-release model and are oriented towards fixed releases, so we can only provide for now the insight for testing. When we are finished with 0.4 this will be changed again.

Your search local gives you the stable branch of the packages assigned towards 0.3.1 and therefore plasma-desktop, qtcreator or sddm. As mentioned packages have unwanted dependencies we cannot assure and we see as violation towards our social contract they won't be part for 0.4 any longer. More explanation towards that point: Hyperbola has taken one single snapshot of all repositories from "Arch Linux" back in 2017 (https://www.hyperbola.info/news/hyperbo … ally-here/) and removed all unfree packages. From that point we worked part by part towards removal of problematic frameworks and dependencies. So we have removed for example Kodi and Vice for having unfree code and content included. The version 0.4 will be the break as we did a complete rework and built all packages again but now without cloning.

About the mailing list: Yes, that is more or less known. But as mentioned before: We can only focus part by part for now. If you have some further tipps or possible hints we can use for fixing that sooner, please be invited.

I hope you have a great time here.

If you have more questions and / or problems: Just ask. I'm sure we can find a solution for them and eager to help here for further technical emancipation.

I have checked the date and it was correct. The issue still persists even after doing the Verification process you mentioned above. I am still trying now.

I do second this, but I think it should be labelled  at the end with beta, or better yet, release candidate, since it is mega close to being ready.

Of course, that is all up to the lead devs, but yeah...

I recommend this as well especially since 0.4 has become as stable in my opinion as  release candidate,

Either way, I hope all devs reading this thread ponder this!

Hello, Hyperbola Community.

After many times re-evaluating, I can confirm that this issue only happens on a Live System as per image file 'hyperbola-milky-way-v0.3.1-dual.iso' and this issue does not happen or everything is alright on an installed, fully upgraded system. I still don't know what causes this and I suspect what sir Throgh said was true, there was something wrong with the ISO's built-in old key system. Without knowing the cause or finding a solution, I am afraid this will render the iso unusable, and I would fail also to install Hyperbola 0.4 if I should use 0.3 iso, thus the ISO file needs to be updated soon by Hyperbola Team.

Picture of pacman update from the ISO's Live System Installer:

Picture of pacman update from an installed, fully-upgraded Hyperbola:

What do you think?

I'm going to do another test with 0.3.1 within the next days and will play around a little to find out possible solutions especially as I'm interested to keep 0.3.1 for some special appliance active after 0.4 is even released - named one is wine for that and multilib without network at most.

In general: We work hard on the live-system getting it running. Emulatorman and Coadde are doing therefore much in the background. I also hope for doing more work onto virtualization, but no promise yet as libvirt is hard to get into with all its dependencies especially for running the service. I hope to come back with more news about both parts: 0.3.1-installation and also 0.4-insights.