Your message dated Tue, 7 Mar 2006 10:42:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line wpa_gui is not for 'normal' users
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wpagui
Version: 0.4.7-2
Severity: minor
wpagui can be used by users to control the wpa_supplicant daemon. Because
of that reason /usr/bin seems to be a better location of for binary.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-fairlight
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages wpagui depends on:
ii libc6 2.3.5-12 GNU C Library: Shared libraries an
ii libgcc1 1:4.0.2-8 GCC support library
ii libqt4-core 4.1.0-3 Qt 4 core non-GUI functionality ru
ii libqt4-gui 4.1.0-3 Qt 4 core GUI functionality runtim
ii libqt4-qt3support 4.1.0-3 Qt 3 compatibility library for Qt
ii libstdc++6 4.0.2-8 The GNU Standard C++ Library v3
ii wpasupplicant 0.4.7-2 Client support for WPA and WPA2 (I
wpagui recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
wpa_gui is a graphical application which allows priviledged users to
control a running wpasupplicant daemon. The user needs to be priviledged
in some way, either by being root, or having root configured the system
so that he can access the control socket in some way.
This is why I think that section 8 is the right place for this manpage.
Otherwise we would have to move wpa_cli(8) as well to section 1.
Feel free to reopen this bug with a better rationale.
regards,
Reinhard
--- End Message ---
