<stenur>
Heh. Lots of mouths to feed. And can be over so fast and terribly, one friend slained to death by falling branch in the heavy storms we had last night.
<stenur>
So better spending each second for the ones we love.
<ppetrov^>
that's terrible. Sorry to hear
<stenur>
Ah wait. The friend had four legs.
<stenur>
It does not really make it better for me though, thank you. ;)
groovy3shoes has quit [Remote host closed the connection]
groovy3shoes has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
Guest35 has joined #crux
ppetrov^ has quit [Quit: Leaving]
Guest35 has quit [Quit: Client closed]
groovy3shoes is now known as groovy2shoes
Guest35 has joined #crux
<Guest35>
hello, my pulseaudio says cannot connect to D-Bus
<stenur>
is dbus running?
<stenur>
note dbus is broken
<stenur>
eh. at least on 3.7
<Guest35>
yes, dbus running.
<stenur>
really?
<stenur>
I had to add " [ -d /run/dbus ] || mkdir -p /run/dbus" to /etc/rc.d/dbus.
<stenur>
Well if it did ran already i do not know; otherwise /etc/dbus-1/* may be of interest, but to me this is crypto.
farkuhar has joined #crux
<farkuhar>
so 3.7 changed /var/run to be a symlink to /run, but the startup script for dbus wasn't changed to match?
<stenur>
That is what happened i think.
<stenur>
I mean, /run is volatile storage (as it should be) and the daemon startup has to ensure itself that the stuff exists.
<stenur>
^ what really happened
<Guest35>
i also saw my pulseaudio post-script fails
<farkuhar>
Were they worried about committing a change that might accidentally get installed on a 3.6 filesystem? It should be possible to make the git commit only for the 3.7 branch.
<stenur>
I have no idea. I would not say "they" in that case, anyway.
<farkuhar>
If it were #crux-devel I might say "we", but this is #crux so I went with "they"
ocb has quit [Remote host closed the connection]
ocb has joined #crux
<stenur>
I meant the particular git commit iirc. I mentioned that on -devel already i think.
<farkuhar>
Guest35: what pulseaudio post-script? The post-install script that came with the port?
<Guest35>
yes, that came with the port
<stenur>
Merde i hate that XML stuff everywhere. Especially in configs like /etc/dbus-1; and no documentation for this, how can this be secure?
<stenur>
And - did the post-install script of glib succeed once you'd compiled _that_?
<farkuhar>
Guest35: the script would fail if the file mentioned in the first command doesn't exist, which is certainly possible given the optional dependencies of pulseaudio.
<Guest35>
the only glib post-install script line is /sbin/telinit U
<Guest35>
it seems to work.
<stenur>
? I have 'glib-compile-schemas /usr/share/glib-2.0/schemas
<farkuhar>
In any case, it's recommended that you inspect each post-install script yourself to see what it intends to do. Some of them aren't written in an idempotent manner, and will fail if you do a prt-get update with runscripts=YES.