zapper wrote:

Okay so then how often do updates occur on testing? Because I didn't see any updates for a long time on testing even. I am curious if it is because of preparing to switch to libressl. This is why right?
I had tried this before but nothing much happened.

Thanks though for telling me.

For now, both versions are the same since we are preparing our build server to begin Milky Way v0.3 development for Hyperbola GNU/Linux-libre and Hyperbola GNU/Hurd. Then, White Hole will be a testing version again.

Okay, thanks for clarifying why that was happening.

Okay so then how often do updates occur on testing? Because I didn't see any updates for a long time on testing even. I am curious if it is because of preparing to switch to libressl. This is why right?
I had tried this before but nothing much happened.

Thanks though for telling me.

For now, both versions are the same since we are preparing our build server to begin Milky Way v0.3 development for Hyperbola GNU/Linux-libre and Hyperbola GNU/Hurd. Then, White Hole will be a testing version again.

zapper wrote:

I am not entirely sure though how to do that of course. Mostly because I don't know how to activate the white hole repo. heh

You should disable the stable mirrors and enable the testing ones in /etc/pacman.d/mirrorlist, eg:

# Hyperbola GNU/Linux-libre - Last Updated: Fri Nov 24 15:01:10 CET 2017

# Location: Galicia, Spain
# Responsible: Oficina de Software Libre do CIXUG
# Work hours: 24*7
# Server = https://ftp.cixug.es/hyperbola/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Cuenca, Ecuador
# Responsible: Red CEDIA
# Work hours: 24*7
# Server = https://mirror.cedia.org.ec/hyperbola/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Utrecht, Netherlands
# Responsible: Vereniging NLUUG
# Work hours: 24*7
# Server = https://ftp.nluug.nl/os/Linux/distr/hyperbola/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Luke .R
# Work hours: 24*7
# Server = https://whatsgnu.serverpit.com/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Isaac David
# Work hours: 24*7
# Server = https://hyperbola.isacdaavid.info/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Bissen, Luxembourg
# Responsible: Hyperbola Project
# Server = https://repo.hyperbola.info:50012/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Luke .R
# Work hours: 24*7
# Note: Darknet mirror for Tor (requires special settings in pacman.conf, only use if you know what you are doing)
# Server = http://antd4nwolq3tmqsz.onion/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Luke .R
# Work hours: 24*7
# Note: Darknet mirror for I2P (requires special settings in pacman.conf, only use if you know what you are doing)
# Server = http://mp3p7nzaz5zic5qbdmqsrus4uxxumznvg67a7rmpyawj7fps2mva.b32.i2p:8080/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Galicia, Spain
# Responsible: Oficina de Software Libre do CIXUG
# Work hours: 24*7
# Note: Only for development and debugging
 Server = https://ftp.cixug.es/hyperbola/gnu-plus-linux-libre/testing/$repo/os/$arch

# Location: Cuenca, Ecuador
# Responsible: Red CEDIA
# Work hours: 24*7
# Note: Only for development and debugging
 Server = https://mirror.cedia.org.ec/hyperbola/gnu-plus-linux-libre/testing/$repo/os/$arch

# Location: Utrecht, Netherlands
# Responsible: Vereniging NLUUG
# Work hours: 24*7
# Note: Only for development and debugging
 Server = https://ftp.nluug.nl/os/Linux/distr/hyperbola/gnu-plus-linux-libre/testing/$repo/os/$arch

# Location: Bissen, Luxembourg
# Responsible: Hyperbola Project
# Note: Only for development and debugging
 Server = https://repo.hyperbola.info:50011/gnu-plus-linux-libre/testing/$repo/os/$arch

Okay so then how often do updates occur on testing? Because I didn't see any updates for a long time on testing even. I am curious if it is because of preparing to switch to libressl. This is why right?
I had tried this before but nothing much happened.

Thanks though for telling me.

I am not entirely sure though how to do that of course. Mostly because I don't know how to activate the white hole repo. heh

You should disable the stable mirrors and enable the testing ones in /etc/pacman.d/mirrorlist, eg:

# Hyperbola GNU/Linux-libre - Last Updated: Fri Nov 24 15:01:10 CET 2017

# Location: Galicia, Spain
# Responsible: Oficina de Software Libre do CIXUG
# Work hours: 24*7
# Server = https://ftp.cixug.es/hyperbola/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Cuenca, Ecuador
# Responsible: Red CEDIA
# Work hours: 24*7
# Server = https://mirror.cedia.org.ec/hyperbola/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Utrecht, Netherlands
# Responsible: Vereniging NLUUG
# Work hours: 24*7
# Server = https://ftp.nluug.nl/os/Linux/distr/hyperbola/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Luke .R
# Work hours: 24*7
# Server = https://whatsgnu.serverpit.com/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Isaac David
# Work hours: 24*7
# Server = https://hyperbola.isacdaavid.info/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Bissen, Luxembourg
# Responsible: Hyperbola Project
# Server = https://repo.hyperbola.info:50012/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Luke .R
# Work hours: 24*7
# Note: Darknet mirror for Tor (requires special settings in pacman.conf, only use if you know what you are doing)
# Server = http://antd4nwolq3tmqsz.onion/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Amsterdam, Netherlands
# Responsible: Luke .R
# Work hours: 24*7
# Note: Darknet mirror for I2P (requires special settings in pacman.conf, only use if you know what you are doing)
# Server = http://mp3p7nzaz5zic5qbdmqsrus4uxxumznvg67a7rmpyawj7fps2mva.b32.i2p:8080/gnu-plus-linux-libre/stable/$repo/os/$arch

# Location: Galicia, Spain
# Responsible: Oficina de Software Libre do CIXUG
# Work hours: 24*7
# Note: Only for development and debugging
 Server = https://ftp.cixug.es/hyperbola/gnu-plus-linux-libre/testing/$repo/os/$arch

# Location: Cuenca, Ecuador
# Responsible: Red CEDIA
# Work hours: 24*7
# Note: Only for development and debugging
 Server = https://mirror.cedia.org.ec/hyperbola/gnu-plus-linux-libre/testing/$repo/os/$arch

# Location: Utrecht, Netherlands
# Responsible: Vereniging NLUUG
# Work hours: 24*7
# Note: Only for development and debugging
 Server = https://ftp.nluug.nl/os/Linux/distr/hyperbola/gnu-plus-linux-libre/testing/$repo/os/$arch

# Location: Bissen, Luxembourg
# Responsible: Hyperbola Project
# Note: Only for development and debugging
 Server = https://repo.hyperbola.info:50011/gnu-plus-linux-libre/testing/$repo/os/$arch

zapper wrote:

You haven't responded since, is it too dangerous then to even load a white hole iso through qemu even if its not on my actual install?

aka a virtual machine with white hole not the actual install?

Virtual machines are just virtual machines, you could use them for testing, debugging like me. I don't see problems to use White Hole from it, if it is your goal.

That was what my original post was about. I wanted to use testing within a virtual machine.

I am not entirely sure though how to do that of course. Mostly because I don't know how to activate the white hole repo. heh

Because I don't know how to change the virtual system over.  ps, I was going to do this, to report bugs for you.  This really is a unique and awesome distro.

Arch + Debian Packages + Libre Completely! Never seen this happen before you guys made this distro.

I would love to see FSF feature your distro in the free distro area.  Calamares might be the last hurdle to making this distro newbie friendly.

You haven't responded since, is it too dangerous then to even load a white hole iso through qemu even if its not on my actual install?

aka a virtual machine with white hole not the actual install?

Virtual machines are just virtual machines, you could use them for testing, debugging like me. I don't see problems to use White Hole from it, if it is your goal.

aka a virtual machine with white hole not the actual install?

zapper wrote:

I wanted to use qemu to do some testing of the white hole stuff. So, how does one do this?

And what errors should I suspect? just wondering...

White Hole version is adapted to the Hyperbola devs and security team who are doing new revisions of our packages and making testing before release it to Milky Way for a better stability.

While a roadmap doesn't start, both versions (White Hole and Milky Way) are the same, however when a roadmap starts, it could generate instabilities and break your system.

If you paid attention, our Milky Way v0.3 roadmap is about stabilize all [core] repo following our packaging guidelines. It won't generate issues for your system, however we have plans to make the migration from OpenSSL to LibreSSL that could break your system since we need rebuild a lot of packages to be adapted to LibreSSL; so i don't suggest you use it.

Okay, but would it be dangerous if I loaded an iso through qemu within my stable hyperbola distro?

ps, thanks for the warning. I won't change to white hole within my actual distro now that I know this.

Just in a qemu image if needed.

I wanted to use qemu to do some testing of the white hole stuff. So, how does one do this?

And what errors should I suspect? just wondering...

White Hole version is adapted to the Hyperbola devs and security team who are doing new revisions of our packages and making testing before release it to Milky Way for a better stability.

While a roadmap doesn't start, both versions (White Hole and Milky Way) are the same, however when a roadmap starts, it could generate instabilities and break your system.

If you paid attention, our Milky Way v0.3 roadmap is about stabilize all [core] repo following our packaging guidelines. It won't generate issues for your system, however we have plans to make the migration from OpenSSL to LibreSSL that could break your system since we need rebuild a lot of packages to be adapted to LibreSSL; so i don't suggest you use it.

And what errors should I suspect? just wondering...