As the moon goes down...
Pardon a brief interruption of the ongoing silence but; Guess what?
Turns out, this place isn't quite dead just yet! :-)
It has been quite a while since I posted around here, or anywhere to be fair, but after some time away from the keyboard here I am again. Now I haven't fully resumed all that I had going "before" and I'll be honest, there are things I haven't dared looking at so far. This means there's no update for anything at the moment, although I do intend to get back to it at some point.
kalu 4.3.0 is out
As I'm sure you have noticed by now, a new version of pacman (5.1) has been released, and with it API changes to ALPM requiring some compatibility changes.
Nothing big, but it needed to be done of course, so here's a new version of kalu with the required changes, a fix to actually be suspend-aware, and a small addition in form of a context menu to the "Mark Watched (AUR)" windows.
kalu 4.2.0 is out, speaks Spanish
About time a new release of kalu was made, so here it is! Apart from a few bugs being fixed, this release sees a couple of command-line options mainly useful for CLI use, and the addition of Spanish to the list of languages supported by kalu thanks to pepecuis!
anopa 0.5.0 released
A new version of anopa - init system/service manager built around s6 supervision suite - has been released. Main changes since 0.4.0 are :
tty: Fix when multiple devices are listed as console. Thanks to linsam.
status: Report "Up; Getting ready..." as needed. Longruns that are up (i.e. not (yet) ready) but do support readiness will be announced as such, making it obvious they support readiness and therefore aren't yet in their "final" state.
enable: Add
--alarm-s6When adding new servicedirs to an active repodir (i.e. its scandir has a running s6-svscan), for new longruns to be properly set/usable we need to "alarm" s6-svscan, so it rescans the scandir.This had to be done manually via
s6-svscanctl -a $REPODIR/.scandirbut can now be done automatically from aa-enable.
StatusNotifier v1.0.0 released !
As long last, a new version of statusnotifier is out! This has been due for a (very) long time, and it's finally arrived. Many thanks to everyone who helped, especially contributors Bradley Xu and Vladimir Perepechin, and apologies it took so long for a release to happen.
As you've no doubt noticed, this is version 1.0.0 -- Two reasons for that: one, it's indeed considered stable; And two, it comes with a soname bump and incompatibility with the previous version.
New version of slicd, a simple lightweight Linux cron daemon
Time for a new release of slicd - a simple lightweight Linux cron daemon - with fixes regarding DST handling and the addition of a new per-job "special DST" mode, amongst other things.
journal-triggerd 0.2.1 released
This is a "minor" bugfix release, mainly affecting building of journal-triggerd;
though there was an important issue since configure was still looking for
libsystemd-journal even though it has been removed & merged into libsystemd
since v230.
kalu 4.1.0 is out, speaks Norwegian
Time for a new release of kalu. Mostly a bugfix release, though thanks to AdmiringWorm kalu now speaks Norwegian Bokmål!
Note that there was a bug in the updater, where /etc/pacmand.d/hooks was not
set as default HookDir if none were specified in pacman.conf - which means
unless you set it there, any custom hooks were not used.
What does it mean when 'alsactl restore' talks invalid sysfs?
alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Found hardware: "HDA-Intel" "Analog Devices AD1989B" "HDA:11d4989b,10438311,00100300" "0x1043" "0x8311"
Hardware is initialized using a generic method
This is what I could read on boot after a recent kernel upgrade (4.4.1-2 ->
4.4.3-1, to be exact), as a result of running alsactl restore Now, the good
thing is my audio didn't stop working, but that's still not right (and my
settings (e.g. volume levels) weren't restored as they should have been).
kalu 4.0.2 released
"Release often" they say, right? Yet another release of kalu, since a stupid mistake on my part led to notifications being empty in 4.0.1, making them much less useful indeed.
This is now fixed; Thanks to adam777 for the report. Hopefully this is the last release for this week :p