daniel huhardeaux wrote:
Package: wpasupplicant
Version: 0.4.8-2
Severity: minor
In the ifupdown script the VERBOSITY variable is not initialized.
A good feature would be to have a wpa-verbosity (0,no=default/1,yes) in
interfaces file to play with.
What is wrong with ifup --verbose ?
Daniel Huhardeaux wrote:
Kel Modderman wrote:
daniel huhardeaux wrote:
Package: wpasupplicant
Version: 0.4.8-2
Severity: minor
In the ifupdown script the VERBOSITY variable is not initialized.
A good feature would be to have a wpa-verbosity (0,no=default/1,yes) in
interfaces file to play
The embedded VERBOSITY echo's were designed to debug interfaces
stanza'a, nothing more.
Are you thinking of something like verbose logging to syslog of the
running wpa_supplicant daemon or so?
syslog or dmesg. Something like wpa-verbose yes in interfaces file
would allow to log in
Robert Edmonds wrote:
Package: wpasupplicant
Version: 0.5.2-2
Severity: normal
Suggests: libengine-pkcs11-openssl, dhcp3-client | dchp-client
There is no dchp-client package.
This also affects the version in unstable (0.4.8-2). Thanks for spotting
the typo.
Thanks, Kel.
daniel huhardeaux wrote:
Package: wpasupplicant
Version: 0.4.8-2
Severity: normal
Using wpa-conf /path/to/wpasupplicant.conf in interfaces and having options
there is working. Putting each option in interfaces file failed for 3 of them.
Here are outputs from ifupdown.sh script in verbosity
Reinhard Tartler wrote:
I have no problems with shipping the old init script (or an improved
one) in /usr/share/doc/wpasupplicant/examples. The local administrator
would have to install and activate it himself.
I'm not happy in installing it again in /etc/init.d per default. IMO
using
Joerg Platte wrote:
Package: wpasupplicant
Version: 0.4.8-1
Severity: wishlist
Hi!
I'm using wpa_supplicant and ifplugd. Each time, wpa_supplicant is able to
associate with one of my preconfigured networks, ifplugd detects this and
invokes
ifup interface. In /etc/network/interfaces I'm using
Mau wrote:
Kel,
Here is the log.
Mau, it does not look like the full log to me, only the last bit which
has no indication of what went wrong, just the the module cannot be found.
Sorry, I thought that this issue was easily reproducible: it seems that
some major change in 2.6.16 kernel
Mau wrote:
Package: spca5xx-source
Version: 20060301-1
Severity: important
m-a build fails silently and complains that it can't find spca5xx.ko,
which actually hasn't been built.
All needed headers' packages has been installed.
Thanks - Mau
Does m-a prompt you to view the log to see
Reinhard Tartler wrote:
This is http://bugs.debian.org/295445
This bug is solved in ubuntu at an different place: in ifupdown.
Ifupdown in ubuntu installs a /etc/udev/rules.d/85-ifupdown.rules, which
ifup's the interface which was hotplugged. I like this idea, and think
this should be handled
Aurelien Jarno wrote:
On Fri, Mar 24, 2006 at 05:59:14PM +, Thiemo Seufer wrote:
On Fri, Mar 24, 2006 at 06:41:32PM +0100, Aurelien Jarno wrote:
[snip]
Hmm, you select the hal.o file accordingly? Won't mips1-le-elf work
on both R1 and R2? Checking for R1/R2 doesn't seem ideal to
Lars Wirzenius wrote:
Package: spca5xx-modules-2.6.15-1-486
Version: 20060301+1
When I test this package with piuparts, I get the following error:
0m5.5s ERROR: Package purging left files on system:
/lib/modules/2.6.15-1-486
owned by: spca5xx-modules-2.6.15-1-486
The packaing of this
Ludovic Rousseau wrote:
Le Thursday 02 March 2006 à 16:47:31, Kel Modderman a écrit:
Package: wnpp
Severity: wishlist
Owner: Kel Modderman [EMAIL PROTECTED]
* Package name: acerhk
Version : 0.5.32
Upstream Author : Olaf Tauber [EMAIL PROTECTED]
* URL : http
Julien Valroff wrote:
As 2 build methods are clearly supported and explained in README.Debian, I
think madwifi-source
should only recommend module-assistant (and not depend).
As an alternative, the package could depend on m-a OR kernel-package.
Cheers,
Julien
This is wrong, and the
Hi,
The version of madwifi in debian is *not* madwifi-ng, it is from the
madwifi-old branch. It is totally working correctly with the
wpasupplicant package in debian.
Since the old driver is not supported anymore, is less stable than
the new one, lacks some features and does not work with
Package: wnpp
Severity: wishlist
Owner: Kel Modderman [EMAIL PROTECTED]
* Package name: acerhk
Version : 0.5.32
Upstream Author : Olaf Tauber [EMAIL PROTECTED]
* URL : http://www.informatik.hu-berlin.de/~tauber/acerhk/
* License : GPL
Description : Acer
Package: sl-modem-source
Version: 2.9.9d+e-pre2-2
|Severity: grave
+sl-modem (2.9.9d+e-pre2-1) unstable; urgency=low
+
+ * New upstream pre-release (closes: #327588)
+ * added sv.po from Daniel Nylander (closes: #330436)
+ * slmodemd.1 manpage from Erik Schanze (closes: #335369)
+ * defining
Eduard Bloch wrote:
#include hallo.h
* Kel Modderman [Fri, Feb 24 2006, 11:05:37PM]:
Package: sl-modem-source
Version: 2.9.9d+e-pre2-2
|Severity: grave
+sl-modem (2.9.9d+e-pre2-1) unstable; urgency=low
+
+ * New upstream pre-release (closes: #327588)
+ * added sv.po from Daniel Nylander
Eduard Bloch wrote:
#include hallo.h
* Kel Modderman [Sat, Feb 25 2006, 12:46:42AM]:
Eduard Bloch wrote:
I though I have written that above.
Can you please clarify at all? What makes a license clone an
interchangeable license, especially since you are the one
Hi,
I maintain the external module pool for the Kanotix project.
qc-usb-messenger-source is one of them.
If it can be used in Debian too, i would gladly help maintain this
package based on what I have already developed.
http://kanotix.com/files/debian/pool/main/q/qc-usb-messenger/
Note
Julien Valroff wrote:
Le jeudi 23 février 2006 à 07:04 +1000, Kel Modderman a écrit :
Kel Modderman wrote:
Julien Valroff wrote:
Package: madwifi-source
Version: 0.svn20060207
Severity: wishlist
As 2 build methods are clearly supported and explained in
README.Debian, I
Julien Valroff wrote:
[...]
Le jeudi 23 février 2006 à 19:15 +1000, Kel Modderman a écrit :
90% of the time i also use kernel-package, not m-a, but that is not the
point. I believe m-a lays the best framework for the average user to
easily install a module.
I totally agree, but I
Julien Valroff wrote:
Package: madwifi-source
Version: 0.svn20060207
Severity: wishlist
As 2 build methods are clearly supported and explained in README.Debian, I
think madwifi-source
should only recommend module-assistant (and not depend).
As an alternative, the package could depend on m-a
Kel Modderman wrote:
Julien Valroff wrote:
Package: madwifi-source
Version: 0.svn20060207
Severity: wishlist
As 2 build methods are clearly supported and explained in
README.Debian, I think madwifi-source
should only recommend module-assistant (and not depend).
As an alternative
Reinhard Tartler wrote:
Thank you very much for your bugreport and your patch.
We are currently preparing an upload for 0.4.7-4, you can look at our
current process here:
http://svn.debian.org/wsvn/pkg-wpa/trunk/wpasupplicant/?rev=0sc=0
Parts of your patch are already included there, I will
Hi,
Arjan Oosting wrote:
I am using the madwifi drivers (from madwifi-source) and I guess the
change
from madwifi to madwifi-ng headers is the cause of this failure
* Update madwifi headers to madwifi-ng, rev1390.
As (joint) maintainer of madwifi in debian (and madwifi-ng *out* of
debian)
-rcd-params option when creating the
+wpasupplicant.postinst script.
+ * Remove code duplicated by dh_installinit in wpasupplicant.postinst,
+invoke-rc.d is added automatically.
+ * Install upstream changelog with correct name.
+ * Add watch file.
+
+ -- Kel Modderman [EMAIL PROTECTED
Reinhard Tartler wrote:
Thank you very much for your bugreport and your patch.
We are currently preparing an upload for 0.4.7-4, you can look at our
current process here:
http://svn.debian.org/wsvn/pkg-wpa/trunk/wpasupplicant/?rev=0sc=0
Parts of your patch are already included there, I will
Stéphane Rosi wrote:
Package: spca5xx-modules-2.6-686
Version: 20060101+1
Severity: wishlist
Hi,
Just to tell that version 20060202 of the driver is now available. It
supports a lot of new webcams, included mine! ;)
Could update the package? Thanks!
The new upstream is packaged and
Gerfried Fuchs wrote:
* Kel Modderman [EMAIL PROTECTED] [2006-02-07 06:15]:
Gerfried Fuchs wrote:
Furthermore, a mailinglist -request address as maintainer address is a
*very* bad idea, I seriously hope you consider changing that, too.
I did not see this in our sources anywhere
Gerfried Fuchs wrote:
Package: spca5xx-modules-2.6.15-1-686
Version: 20060101+1
Severity: serious
Justification: Policy 7.2
Hi!
The modules packages slipped into testing because they don't depend on
their corresponding kernel images they are built against. They don't
make any sense
michel Xhaard wrote:
Le Vendredi 13 Janvier 2006 05:35, Brad Sawatzky a écrit :
Strange my original spca5xx-20051212 include linux/version.h on top of the
spca50x.h file ?
#ifdef __KERNEL__
#include asm/uaccess.h
#include linux/videodev.h
#include linux/smp_lock.h
#include linux/usb.h
Jean-Marc Ranger wrote:
Hi Kel,
Due to a recently arrived ipw2200, I'm loosing some interest in
continuing to package the adm8211 code for Debian. Are you interessed
in taking the ownership of the ITP bug in Debian ?
Jean-Marc
The in-kernel wireless code is too turbulent right now,
Graham wrote:
Hi Kel,
Thank you for the links.
Well, in my experience these gui apps for configuring wireless on linux
really cause more trouble than they are worth.
Maybe, but:
1. You and I are fine with console based configuration tools, but many
people, including the owner of
Graham wrote:
It may be related to the inability of this module to do background
scanning, or it could just be a plain old bug in the code. Try using the
basic wireless-tools and refrain from using the graphical apps, and see
if you can reproduce this instability.
Hi Kel,
I'm just
Graham wrote:
Package: madwifi-source
Version: 2005
I've built the module against the Debian official kernel
2.6.14-2-686 (version 2.6.14-7).
I have a ThinkPad A22p and an Enterasys Networks PCMCIA a/b/g card. I
will attach the output of lspci -vvv.
When I click scan for networks in
Nate Bargmann wrote:
Package: madwifi-source
Version: 0.svn20051110-1
Severity: wishlist
I decided to try the madwifi-source this evening and am at a bit of a
loss on how to proceed. I followed the instructions I've used in the
past at http://www.marlow.dk/site.php/tech/madwifi and
Bill Wohler wrote:
Package: madwifi-source
Version: 0.svn20051110-1
Severity: normal
Thanks for packaging madwifi.
/usr/share/doc/madwifi-source/README.Debian is missing a step. If I
create an /etc/network/interfaces stanza of
iface eth1 inet dhcp
wireless_essid my-SSID
Bill Wohler wrote:
Kel Modderman [EMAIL PROTECTED] wrote:
The README would better use ath0 as an example instead of eth1.
Yes, that would clear things up a lot. I thought perhaps I was missing
something. I have been using ath0.
ifrename; install it, read up on it.
Thanks
Hi,
http://kanotix.com/files/debian/acerhk/
That package was made by your's truly for the Kanotix project.
Although I am not officially involved with debian, I currently
co-maintain some other module packages (spca5xx and madwifi) on alioth.
If a developer would like to sponsor and
Hi,
Package for these drivers are here:-
http://kanotix.com/files/debian/pool/main/a/adm8211/
I also track the experimental new version that depends on the common
ieee80211 stack (=2.6.14) here:-
ftp://debian.tu-bs.de/project/kanotix/experimental/pool/main/a/adm8211/
If you would like to
Package: wnpp
Severity: wishlist
Hi,
http://kanotix.com/files/debian/pool/main/r/rt2570/
Above are packages I developed as part of the Kanotix project.
If there is any interest in them to be in debian (alongside the existing rt2400
rt2500 packages), feel free to contact me concerning these
Jean-Marc Ranger wrote:
Hi Kel,
I'll definitely have a look at what you did. I'm fairly new at Debian
packaging, so I sure can learn from what you did.
My version of the 20050620 driver is available at
http://web.ncf.ca/jmranger/adm8211/ if you're interessed to have a
look. It was
Paul Brossier wrote:
for info, i tried earlier versions of spca5xx from
http://mxhaard.free.fr/spca50x/Download/?M=D and found out that the last
version compiling on -powerpc64 is spca5xx-20050601
[EMAIL PROTECTED]:~/spca5xx-20050601$ make
Building SPCA5XX driver for 2.5/2.6 kernel.
/debian/changelog2005-09-25
20:20:18.0 +1000
@@ -1,3 +1,11 @@
+spca5xx (20050906.1-2) UNRELEASED; urgency=low
+
+ [Kel Modderman]
+ * Move staging area for module source from current dir to
+debian/tmp and remove clean target rule in debian/rules.
+
+ -- Kel Modderman [EMAIL PROTECTED
Hey Otavio,
Otavio Salvador wrote:
Kel Modderman [EMAIL PROTECTED] writes:
Otavio, I did some more thinking about the recent revamp of the rules,
and i'd like to propose a small optimisation.
I agree with all this patch. Only one optimisation: you don't need to
use clean target since
Hi,
By the time I saw this, there were a volley of replies to this first
attempt at contact.
Stephen Birch wrote:
Hi Kel and Itay
One of the packages I have been planning for Debian is the spca5xx
package for which I filed a ITP some time back. Since I believed my
NM application was shortly
701 - 747 of 747 matches
Mail list logo
