Void Linux

Void Linux

Changes to linux-firmware may require manual intervention

To reduce installation size, firmware provided by linux-firmware is now compressed with zstd. Ensure you are running a supported kernel when updating to linux-firmware-20260309_1 or later:

oss-security - backdoor in upstream xz/liblzma leading to ssh server compromise

Void Linux

Void Accepted to Fastly Fast Forward!

Did you know that Void has over 20 mirrors? We have mirrors all over the world, but just having a bunch of servers isn’t enough to effectively deliver package updates to all Void users. A mirror that is nearby can have extremely good performance if you know it’s there and switch to it, but for many people what we would like to offer is just a URL that works anywhere in the world to provide the best download experience available in that location. When you look at what we’re trying to achieve, its

Void Linux

New utility for selecting XBPS mirrors

If you’ve ever had trouble manually updating the mirror XBPS uses, fear no more! You can now use the xmirror(1) utility from the xmirror package to select a mirror, either interactively (by running xmirror with root privileges) or directly using xmirror --set.

Void Linux

US Mirror Issues

The US mirror, repo-us.voidlinux.org, is currently having hardware issues and is no longer syncing with the other mirrors for the time being. Until this is fixed, switching to another mirror is recommended. There are several other mirrors located in the US that are still operational.

Void Linux

New Repo: Fastly CDN

In our last post we showed you how to quickly change your mirror using xmirror. In this post we’ll give you a reason to use it, and talk a little more about how mirrors work and how packages get from our servers, to your computer.

Void Linux

Minor breaking change in service logging for several packages

As of this change in void-packages, all services provided by packages should start to include log sub-services that use vlogger(8) as they are updated, if they did not already. This means that service logs for all services should go to syslog now, where they can be captured by a syslog daemon.

Void Linux

New Images! (October 2022 Edition)

We’re pleased to announce that the 20221001 image set has been promoted to current and is now generally available.

Void Linux

US Mirror Retirement

The alpha.us.repo.voidlinux.org mirror has been retired. Users should switch to https://repo-us.voidlinux.org for continued service out of the central US. As part of the switch the US tier one mirror has gained TLS, and is running on a more reliable host.

Void Linux

Hacktoberfest 2022

Are you ready for Hacktoberfest 2022? Void Linux is! We’re excited to be participating for our 6th year. Contributions that help to address our out-of-date packages queue are especially welcome. This is a great way to dip your feet into the world of Linux distro package management and what happens behind the scenes to provide a wide selection of packages and make sure your system remains up to date.

Void Linux

New Mirror Default

The default mirror has been updated to https://repo-default.voidlinux.org. If you wish to specify a mirror that is nearer to you geographically you can find the full list of currently active mirrors here: https://docs.voidlinux.org/xbps/repositories/mirrors/index.html.

Void Linux

DigitalOcean Renews Sponsorship

Void is pleased to announce that DigitalOcean has renewed their sponsorship of our project as part of the Digital Ocean Open Source program. DigitalOcean provides us with reliable infrastructure on which we run the control plane for our distributed fleet of machines, as well as some assorted monitoring and fleet management services. You can find our full list of sponsors on the Acknowledgements page.

Void Linux

Repository Signing Disruption

We are aware of an ongoing infrastructure issue affecting repository synchronization and package signing. We are working to resolve this disruption, but first must resolve another unrelated infrastructure issue. We have no short term ETA for service restoration, however our worst case resolution timeline is Friday the 23rd of July.