On Fri, 16 Nov 2007 the mental interface of Alter Ego told: > Well, I did further research about the "solution" suggested by > Elimar. Elimar suggestion is even worse than I initially thought. > As a matter of fact, his instructions do not actually set up > pinning; they'll end up in me upgrading to unstable!
Are you paranoia? Only alsa-utils to version 1.0.15. It isn't migrated to testing yet, because the hppa buildd didn't worked a while. > With the due respect, It's a completely non-sense to ask someone > to change to another version just in order to (eventually) solve a > bug that it shouldn't exist in the first place. > > It's like asking a Windows XP user to upgrade to Vista in order to > solve a Windows bug... This is from a view of a foolish user. I didn't advice you to upgrade to sid. Only one package. > Well, back on track... > > I did find the solution to this bug. It's very simple: > > # cd /etc/modprobe.d > # mv alsa-base alsa-base.bak > # mv alsa-base.dpkg-old alsa-base This isn't a solution to the problem described by you. The files in modprobe.d are managing modules, respective drivers, which are adapted to kernel-space. > At some point of the abobe-mentioned safe-upgrade, aptitude showed > me this message: > > Setting up alsa-base (1.0.15-2) ... > > Configuration file `/etc/modprobe.d/alsa-base' > ==> Modified (by you or by a script) since installation. > ==> Package distributor has shipped an updated version. > What would you like to do about it ? Your options are: > Y or I : install the package maintainer's version > N or O : keep your currently-installed version > D : show the differences between the versions > .... > > I didn't modified /etc/modprobe.d/alsa-base, so I chose the option > "install the package maintainer's version". Hmmmm. Did you have had a view at the diff to find the bug? > And the bug in question resides on the package maintainer's > version. Choosing the option "keep your currently-installed > version" would have avoided the bug. As told before: no! > So, to solve the problem all I needed to do was to put back the > original "alsa-base", hence the command "mv alsa-base.dpkg-old > alsa-base". And now /etc/init.d/alsa-utils finds amixer? modprobe.d files don't influence the behaviour of the initscripts. So you _must_ have tweaked something else. /etc/init.d/alsa-utils and amixer are in user-space and therefore kernel independent. > In the future package developers (and maintainers) should pay more > attention to the contents of file "/etc/modprobe.d/alsa-base", > before introducing new alsa versions. Well, there are thousands of ALSA users out there. No bug was filed against /etc/modprobe.d/alsa-base which is automaticly created out of a maintained driver list. And you are as competent, to tell us what we have to pay attention to? JJCale, first think, then blame ;) In the future you have to file bugs with reportbug. Else I advice you to study the reply function of your Icedove to get a professional threading. And fixed bugs can be closed by [EMAIL PROTECTED], what is done hereby. Elimar -- In most cases the bug resides between the left and the right ear ;) - unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
