> There still seems to be a problem in the building process of the alsa > module: Installing a self-built alsa-modules package fails with
> # dpkg -i alsa-modules-2.0.36_0.2.0-pre8-2+kreator.2_i386.deb > Selecting previously deselected package alsa-modules-2.0.36. > (Reading database ... 57038 files and directories currently installed.) > Unpacking alsa-modules-2.0.36 (from > alsa-modules-2.0.36_0.2.0-pre8-2+kreator.2_i386.deb)... > dpkg: ../../../dpkg/packages.c:191: process_queue: Assertion `dependtry <= > 4' failed. > Aborted I got this too. In fact I have heard of this problem alot recently, it seems very serious. I was able to fix it on my machine by purging the new alsa-modules package and installing the normal alsa-modules package (ie the one it depends on) and then installing the kernel specific one. Package: alsa-modules-2.0.35 Status: install ok installed Installed-Size: 559 Maintainer: Wichert Akkerman <[EMAIL PROTECTED]> Source: alsadriver (0.2.0-pre8-3) Version: 0.2.0-pre8-3+1.0 Replaces: alsadriver Provides: alsadriver, alsa-modules Depends: alsa-modules Suggests: alsautils Conflicts: alsadriver Package: alsa-modules Status: install ok installed Priority: optional Section: sound Installed-Size: 123 Maintainer: Wichert Akkerman <[EMAIL PROTECTED]> Source: alsadriver Version: 0.2.0-pre8-3 Depends: whiptail, modutils (>= 2.1.85-14) I'm going to bet that the self-provides/self-depends is what is managing to confuse dpkg, remeber it had a similar problem with the apache-ssl package that had a similar structure? Wichert: Should it really provide alsa-modules?? That seems like a bug as alsa-modules has the init script and other things in it. If you fix that you can probably reassign+merg this bug to the dpkg bug regarding apache-ssl. Jason
