At least a bit.
Yes, I know PulseAudio 0.9.7 was released and almost all the tools updated, I’ll be taking care of that tomorrow, after the meeting with the surgeon that will have to tell me whether I need to undergo surgery or not.
I already have an ebuild ready for PulseAudio 0.9.7, based on 0.9.6-r2, with the new init script. There are three new USE flags: dbus, samplerate and gnome. Obviously, even the old init script, available for baselayout 1 users, will also be supported.
So what’s the problem? The problem is that the —disallow-module-loading parameter we pass by default to the system-wide PulseAudio installation, for security (you don’t want random users in the pulse group to be able to load random modules into PulseAudio, do you?), disallows the whole PulseAudio from starting up.
In theory, the parameter should disallow just module loading after startup, but for some reasons now it disallows module loading even before startup. I’ll make sure to report to Lennart (who might be reading this already 😉 ), but I’ll also investigate to see if I can fix it.
On the other hand, nxhtml is waiting for upstream to respond, although there are other problems that thanks to ulm are now being slowly fixed (I never tried packaging such a complex mode); and I’ll be working on a bump of sharutils, as you’ll see in the next days, as I’ve been busy trying to package it for OpenWRT (Kamikaze 7.09 brcm-2.4), it’s needed for tramp (Emacs) to connect to the remote host, although it doesn’t seem to work now either, more details tomorrow.
And I should take it easy.
