Am Dienstag, den 29.09.2009, 20:11 +0200 schrieb Alexander Kurtz: > I've got the very same situation here. I upgraded udev and libudev0 to 146-2 > despite loosing mdadm for a while. But since I didn't want to try > (re-)booting without > mdadm ( / is on a RAID5 ), I didn't reboot (which I probably should have). > And unfortunately just upgrading didn't improve anything (yes I did restart > PA). > > So can somebody whose machine isn't wrecked afterwards please try upgrading > udev > and report back. In the mean time I will convince apt to downgrade udev and > PA back > to 0.141-2/0.9.15. Thanks, friendly stranger!
A new version of mdadm (3.0-3.1) entered unstable today (only amd64 binary is available so far [1]). This version doesn't conflict with the new udev anymore, so I - upgraded mdadm to 3.0-3.1 - upgraded udev/libudev to 146-3 - upgraded pulseaudio to 0.9.18-1 - rebuilt my initramfs - and restarted result: it works, so I suggest something like Depends: udev (>= 146-3) for pulseaudio 0.9.18-1. Cheers Alex [1] http://packages.debian.org/sid/mdadm
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
_______________________________________________ Pkg-pulseaudio-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-pulseaudio-devel
