From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0000318]: alsaconf: -bash: syntax error in conditional expression
Date: Fri, 8 Jul 2005 10:34:58 +0200 [thread overview]
Message-ID: <f46b1aa14701e20dcf73bbefbbcac7b0@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=318>
======================================================================
Reported By: Toralf Förster
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 318
Category: alsaconf
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 05-31-2004 12:25 CEST
Last Modified: 07-08-2005 10:34 CEST
======================================================================
Summary: alsaconf: -bash: syntax error in conditional
expression
Description:
The error above results from lines like:
elif [ -f /etc/redhat-release -a `grep -c "Red Hat" /etc/redhat-release
2>/dev/null` -ne 0 ]; then
instead it should be
elif [[ -f /etc/redhat-release && `grep -c "Red Hat" /etc/redhat-release
2>/dev/null` -ne 0 ]; then
notice the doubled '[[' and ']]' and '&&' instead of '-a', isn't it ?
======================================================================
----------------------------------------------------------------------
jdthood - 02-18-05 22:04
----------------------------------------------------------------------
This should be fixed.
----------------------------------------------------------------------
tiwai - 02-22-05 18:05
----------------------------------------------------------------------
Fixed on CVS.
Issue History
Date Modified Username Field Change
======================================================================
05-31-04 12:25 Toralf Förster New Issue
01-19-05 15:36 jdthood Note Added: 0003288
01-19-05 16:44 tiwai Note Added: 0003292
01-19-05 17:00 Toralf Förster Note Added: 0003299
02-18-05 22:04 jdthood Note Added: 0003666
02-22-05 18:05 tiwai Status new => resolved
02-22-05 18:05 tiwai Resolution open => fixed
02-22-05 18:05 tiwai Assigned To => tiwai
02-22-05 18:05 tiwai Note Added: 0003706
02-22-05 18:05 tiwai Assigned To tiwai =>
07-08-05 10:34 perex Status resolved => closed
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
next reply other threads:[~2005-07-08 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 8:34 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-22 17:05 [ALSA - utils 0000318]: alsaconf: -bash: syntax error in conditional expression bugtrack
2005-02-18 21:04 bugtrack
2005-01-19 16:00 bugtrack
2005-01-19 15:44 bugtrack
2005-01-19 14:36 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f46b1aa14701e20dcf73bbefbbcac7b0@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.