Yes, there is no real port available and right away we cannot afford doing that. Also to note that it looks not good for mumble and umurmur for the moment: Those projects are set direct on top of Google's protocol-buffers and there is no way around it.

That was already taken care of. Problem stays for the moment protobuf. But so far on the current state we will also remove:

mumble
umurmur

Those packages are not possible to build without protobuf. We have therefore checked possible ways, but all of them rely back onwards on the only implementation from Google. As already noted: Hyperbola does not support corporate open-source! It is not a point about trust in the first place, but about depending only on one essential project without having any other choice in the end. Therefore the removed packages will be part of the the correspondng thread in the forums.

Current listing:

bleachbit
bleachbit-gtk
fbida
adobe-source-code-pro-fonts
adobe-source-sans-pro-fonts
dwm-bin (new package dwm)
dwm-src
t1lib
mosh
mumble
umurmur
protobuf
protobuf-c
python-protobuf
protozero
cdw

We don't forbid anything and no one is restricted through those removals. It is just that we will no longer include those packages in our repositories. Everyone is free compiling them and share the corresponding packaging-scripts here as long as they at minimum follow a free and permissive license. But a free and permissive license does not make let alone a free and libre package as there is more: Depending on those packages won't end up good. And speaking about mumble: There is no decentralization within as you will again need to use a server. That's not technical emancipation in the first place. I understand that this decision will make people left with questions. But imagine just this: Where is the real emancipation when you just change the package-names being without alternatives? We have done so much for avoiding dbus, avahi, gtk-doc and many more. Why should we then accept again "corporate open-source"? Just because we have no choice? Though we have that and that's the removal as hard it seems for the moment. If you nevertheless want to use the removed packages: Feel free doing so.

Next to be removed:

redis
hiredis

No worries about the depending packages though: All was tested and there will be nothing missed out. The reasoning is here also the same as before: Free and permissive licensed, but not the whole way as company behind is emulating only freedom. We will nevertheless provide another alternative to key-value-storage fitting on the essentials of Hyperbola, lightweight packaging.

And last but not least also a note about keeping up the support for Hyperbola GNU/Linux-libre and packaging: Yes, we know that HyperbolaBSD is making people curious. But to underline again that also the version 0.4.x is already going at the point where we see HyperbolaBSD in the near future. So it is not only the point that Hyperbola in a whole is in some way transitioning or reforming only into HyperbolaBSD. The whole project is important, the whole team and its work, including the whole community. It is complete false and a just too simplified perspective stating that "only HyperbolaBSD is important". Packaging and porting is also really needed. If you think that software is magically transforming into a package, you are surely going into the wrong way. It is not only depending on the maintaining upstream. Also the people doing the packging-work are needed. Yes, it seems easy to oversee them. But we here at Hyperbola won't and don't do this. So the friendly reminder is also called out for the community not following those wrong perspectives around.

Yes, GCC 8 is not the newest version. Others the same. Nevertheless our packages are also individual made and we are standing behind the decisions done. If people don't want to value that and the work behind this, we would kind ask those people to get in contact with us and state their criticism. Perhaps there are misunderstandings to clear up? Also to repeat again: Hyperbola is NOT Arch GNU/Linux and also NOT Parabola. Since the initial release of version 0.4 there is no further snapshot of packages and the whole system is complete independent made from scratch. And do us a favor: Please stop claiming that the system is making a "transitioning towards BSD and so has old or weird decisions for the moment". We can read this in some commentary on issues elsewhere. If you don't like the version of GCC, so upgrade it on your own. If you miss some package, add it and port it on your own. Hyperbola is free software, you are free to decide on your own. We are not the ones stopping anyone, but we ask for sharing help and not sharing commentary elsewhere.

Thank you!

Agent Carmen and Agent Francis entered the room, the only thing they found was this one symbol. Carmen stated to Francis: "Well, seems we should try this out. But please, darling, staying silent about that, will you?" Francis reacted only with grumbling.

Done in Inkscape!

That is like a Pink Floyd album... Nice. For me it is like the officers and the zepelin are running away!

Wallpapers are now there for everyone to check and review: https://git.hyperbola.info:50100/~team/ … apers.git/

There is an autojump port for NetBSD.

I have noticed that the "iceweasel-uxp-ematrix" package for iceweasel-uxp will automatically fetch and enable proprietary hosts files under non-commercial restrictions whenever the user profile is reset, maybe we should blacklist it or try to patch it (I'm not sure how trivial patching it would be)

Well, when I first installed the EMatrix package, no hosts files were being listed in EMatrix's configuration interface (chrome://ematrix/content/dashboard.html#hosts-files), but then at one point 4 hosts files decided to pop up for whatever reason and they enabled themselves automatically. I was able to disable them, but when I reset my Iceweasel-UXP to factory defaults they were automatically reenabled again and they updated themselves. The hosts files are the following:

*URLhaus blocklist (the only libre one, under public domain). Stored locally in chrome://ematrix/content/asset-viewer.html?url=urlhaus

*Peter Lowes Ad and tracking server list (under custom non-free license that forbids ALL commercial use (see https://pgl.yoyo.org/license/)). Stored locally in chrome://ematrix/content/asset-viewer.html?url=plowe-0

*Dan Pollocks hosts file (non-free, probihits commercial use). Stored locally in chrome://ematrix/content/asset-viewer.html?url=dpollock-0

*MVPS HOSTS (under proprietary "Creative Commons" NC license); chrome://ematrix/content/asset-viewer.html?url=mvps-0

This problem is not exclusive to EMatrix, I am aware that UMatrix also fetches (or used to fetch) non-free hosts files. If you want to test this, try to temporarily delete your ~/.hyperbola/iceweasel-uxp in order to reset EMatrix to its default state, and then check chrome://ematrix/content/dashboard.html to see if EMatrix is trying to fetch non-free files in your setup too