Your message dated Sun, 20 Apr 2008 13:36:06 +0300
with message-id <[EMAIL PROTECTED]>
and subject line setmixer removed
has caused the Debian Bug report #368678,
regarding setmixer: Please don't conflict with alsa-base or aumix
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
368678: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368678
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: setmixer
Severity: normal
setmixer shouldn't conflict with alsa-base or aumix. The CLI tool
works perfectly in conjunction with both of them, the only problem is
the init script. IANADD, but I think the policy forbids to put
alsa-base/aumix in the "Conflicts:" field in such a case.
The correct fix would be to fix the init script to stop if either
aumix or alsa-base is found. (Just as aumix currently does it with
alsa-base).
setmixer is quite a useful tool, but due to the Conflicts line with
alsa-base I am currently unable to use it.
Lennart
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
--- End Message ---
--- Begin Message ---
Setmixer has now been removed from debian. Setting mixer by
default on boottime is not done by alsa-base. Setting mixer
from command line is done with "amixer" command
from alsa-utils.
--
"rm -rf" only sounds scary if you don't have backups
--- End Message ---
