Package: whereami
Version: 0.3.28
Severity: normal
The tests/testap script has two inverted string tests for the madwifi
detection. This causes whereami to not bring up the wireless interface
properly. Attached is a patch to correct the two lines.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (700, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages whereami depends on:
ii debconf [debconf-2.0] 1.4.58 Debian configuration management sy
ii dhcp-client 2.0pl5-19.1 DHCP Client
ii iputils-ping 3:20020927-3 Tools to test the reachability of
ii netbase 4.23 Basic TCP/IP networking system
ii perl 5.8.7-7 Larry Wall's Practical Extraction
Versions of packages whereami recommends:
ii iputils-arping 3:20020927-3 Tool to send ICMP echo requests to
ii resolvconf 1.33 nameserver information handler
ii wireless-tools 27+28pre10-1 Tools for manipulating Linux Wirel
-- debconf information:
* whereami/how_to_configure:
--- tests/testap 2005-09-18 06:37:24.000000000 -0400
+++ /usr/share/whereami/tests/testap 2005-11-14 17:45:43.000000000 -0500
@@ -81,7 +81,7 @@
scan_for_ap()
{
MAXATTEMPTS=4
- if [ ! -z "$ISMADWIFI" ] ; then
+ if [ ! -n "$ISMADWIFI" ] ; then
# For reliable scanning, the interface needs to be down, and
# then brought up for (at least) 4 seconds.
# - true as at madwif + kernel 2.6.10, 29 December 2004
@@ -108,7 +108,7 @@
done
- if [ ! -z "$ISMADWIFI" ] ; then
+ if [ ! -n "$ISMADWIFI" ] ; then
# Put the interface back how we found it...
# except we won't do this on the MADWIFI, because the driver
# doesn't seem to support a non-destructive scan anyway :-(
