All Void managed mirrors now listen on new primary addresses. The default mirrors have been updated in the xbps package and will take effect on your next system update. If you were manually setting mirrors, please take a few moments to update the hostname you have configured.
Now is also a great time to determine if you’re using the nearest mirror. An up-to-date list of mirrors and locations can be found any time at http://auto.voidlinux.org/?mirrorstats.
Please report issues at https://github.com/void-linux/xbps/issues.
A new XBPS stable version has been released: 0.53. This is a minor release that contains bugfixes and performance improvements:
xbps-rindex(1): fix possible stagedata deadlock. (@Gottox)
xbps-create(1): Allow file paths longer than 128 characters. (@Gottox)
libxbps: share workload more efficient between threads and avoid idling threads. (@Gottox)
xbps-rindex(1): By default xbps-rindex will not check hashes while cleaning. To enable the old behavior the user can supply the –hashcheck flag. (@Gottox)
This version also bumps the ABI version that should’ve happened with 0.52. Sorry for that.
Please report issues at https://github.com/void-linux/xbps/issues.
So we’re finally moving our GitHub Organisation. The new organisation name will be github.com/void-linux.
We will move the organisation on 2018-06-15.
This is a painful but important step in our reorganisation procedure and lays the foundation of expanding our maintainer team.
Beginning from that date, Void will only accept new pull requests for our new org. New pull requests opened on the old organisation will be auto closed. The remaining pull requests on the old organisation will remain open and will be handled, or the author can reopen them on the new org.
We will add a comment to the remaining issues asking for them to be reopened on the new organisation.
During the next few weeks the team will publish updates to point the repositories to voidlinux.org instead of voidlinux.eu. We will publish a dedicated news entry when the domain is ready to be used.
For everyone that manually configured a repository under the voidlinux.eu domain, please change it manually.
The voidlinux.eu domain will continue to work, but we cannot give any promises for how long.
At last we’d like to thank for the awesome support we’re experiencing during our restructuring.
A quick follow-up to yesterday’s post: We have control over the IRC Channels again!
Thank you Freenode support team!
Dear Void Users,
We have a problem. In the last few months people have been complaining about the lack of management capabilities in the Void Core Team. We have been aware of the problem, and it’s time to explain the situation.
The current project leader has disappeared. We have had no contact with him since the end of January, and no meaningful contact for well over a year. This itself would be concerning, on its own but no threat to the project.
The problem is that we currently have no ability to manage some of Void’s central resources. In the past, they were managed exclusively by the former project leader. Namely:
We contacted Github, but they declined any help to regain access to the organisation. This is really really unfortunately as Github grew to a tool for both source and community management. This has led to questions of if Github is still the best option for us, but we are continuing with the platform for the foreseeable future.
We have contacted freenode support. We see hope to regain access to the VoidLinux IRC Channels. IRC is an essential tool for communication of the core team.
We regained partial control over voidlinux.com. But the most used domain, voidlinux.eu, is currently not under our control. It currently works, but as soon as we have to move any IP addresses, it will fail. IP addresses may need to be moved for a variety of reasons, the most obvious being when we upgrade the master build server.
Currently we are in limbo and are trying to get back on track. We see no possibility to regain access to the Github organisation. So for Github, we will move to a new organisation.
We have a similar solution for the domains. We will move to a different domain and continue to support the voidlinux.eu domain as long as possible.
For the IRC Channels, we will try to get in contact with freenode and regain access. We are hoping that freenode support will be open to our request.
We learned our lesson. In future no single person will have exclusive access to Void’s resources.
Furthermore, we’re in contact with a non profit organisation that helps open source projects to manage donations and other resources. We hope that we can announce further details in a few weeks.
For now, just be aware that the engineering work to help mitigate our problems is underway. This engineering work is consuming the full resources of 2 senior contributors, and has unfortunately also led to longer PR review times..
A new XBPS stable version has been released: 0.52. This is a major release that a few new features and bugfixes:
Because many ponies enjoyed the The Advent of Void: Day 25: ponysay post we decided to release a new Void Linux image with all your friends onboard.
Happy eastern to everypony!
Who of you ever wanted a pony for Christmas? Turns out, Void Linux already includes some. Don’t worry, they are just virtual yet just a command away:
# xbps-install ponysay
ponysay features over 400 illustrations of My Little Pony for your terminal. Look at all of them using
% ponysay-tool --browse /usr/share/ponysay/ponies
You even can make the ponies quote themselves using
Lots of fun for everypony! Whee!
cron(8) is a nice tool, but it has some long-standing problems, among them:
A little, but flexible alternative is to use snooze(1), which essentially just waits for a particular time, and then executes a command. To get recurring jobs ala cron, we can use this together with our runit service supervision suite. If we wanted at(1) instead, we can just run snooze once.
The time for snooze is given using the options
-d (for day),
-m (for month),
-w (for weekday),
-D (for day of year),
-W (for ISO week), and
-H (for hour),
-M (for minute),
-S (for second).
Each option of these can be comma-separated list
of values, ranges (with
-) or repetitions (with
The default is daily at midnight,
so if we wanted to run at the next full hour instead, we could run:
% snooze -n -H'*' 2017-12-24T17:00:00+0100 Sun 0d 0h 47m 33s 2017-12-24T18:00:00+0100 Sun 0d 1h 47m 33s 2017-12-24T19:00:00+0100 Sun 0d 2h 47m 33s 2017-12-24T20:00:00+0100 Sun 0d 3h 47m 33s 2017-12-24T21:00:00+0100 Sun 0d 4h 47m 33s
-n option disables the actual execution and shows the next five
matching times instead.
To run every 15 minutes, we’d use
% snooze -n -H'*' -M/15 2017-12-24T16:15:00+0100 Sun 0d 0h 1m 31s 2017-12-24T16:30:00+0100 Sun 0d 0h 16m 31s 2017-12-24T16:45:00+0100 Sun 0d 0h 31m 31s 2017-12-24T17:00:00+0100 Sun 0d 0h 46m 31s 2017-12-24T17:15:00+0100 Sun 0d 1h 1m 31s
More complicated things are possible, for example next Friday the 13th:
% snooze -n -w5 -d13 2018-04-13T00:00:00+0200 Fri 108d 6h 45m 33s 2018-07-13T00:00:00+0200 Fri 199d 6h 45m 33s no satisfying date found within a year.
Note that snooze bails out if it takes more than a year for the event to happen.
By default, snooze will just terminate successfully, but we can give it a command to run instead:
% snooze -H'*' -M'*' -S30 date Sun Dec 24 16:27:30 CET 2017
When snooze receives a SIGALRM, it immediately runs the command.
snooze is quite robust, it checks every 5 minutes the time has progressed as expected, so if you change the system time (or the timezone changes), it is noticed.
For additional robustness, you can use the timefiles option
which ensures a job is not started if its earlier than some
modification time of a file. On success, your job can then touch this
file to unlock the next iteration. Together with the slack option
this can be used for anacron-style invocations that ensure a task is
run, for example, every day at some point.
Day 23, almost the end of the year. You may consider that it’s time to look
back and take stock of your month, or your year. An accounting, if you will.
Fortunately we have a package or two for that:
second one is a rewrite of the first in Haskell, while the first is the one
that sets the spec.
I must apologize in advance: I am not an accountant, so I may confuse the powerful concepts on which accounting depends. Please bear with me, and feel free to let me know of any corrections.
These are accounting tools, with powerful features I never need to use, web interfaces I don’t need (but maybe others in our lives would desire), but are easy to use with text files with a simple format.
To pass a file to ledger (or hledger), just call
path/to/ledger.file, and make sure the file contains entries (or even just
one) of the format:
2017-12-25 My true love gave to me Equity:TrueLove -1 partridge Assets 1 partridge
The notion behind the ledger format is the same as double entry accounting. What goes in must come out, or everything must come from somewhere. If you take $5 from one place, it has to go somewhere else, in that same transaction.
2017-12-26 My true love gave to me and I paid back Tom Equity:TrueLove -2 turtledove Assets 1 turtledove Assets:Tom 1 turtledove
For instance, the following ledger entry will throw an error because nothing matches!
2017-12-27 My true love gave to me Equity:TrueLove -$3 Assets $1 Assets:Tom $1
(I switched to units where I could be certain the double entry mechanisms are checked. They don’t seem to be for french_hens.)
The ledger manual has a lot of information about all the things ledger supports, including inline maths and stock prices.
May your books forever be balanced!