Package: kismet
The new version of kismet came out this week.
Currently I;m debating on releasing the old core update released a few weeks
ago which i've testied and making a new package for newcore or just replacing
the old kismet all together
i'm playing with newcore now and need to reeval
et.conf, I only changed three values (source, logtypes,
> logtemplate). Attached is the file I use.
>
> Thanks,
> -hd
>
>
> - Original Message
> From: Francois Gurin <[EMAIL PROTECTED]>
> To: Huy Duong <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
>
I need more information as kismet_server works i386 and armel
Does kismet_server segfault in all configurations or just when connecting to
the drone?
Does this happen when you run kismet_server on i386 debian and point it at the
drone?
Does this happen when you run kismet_drone from the pac
ound
> Reply-To: Cristian Ionescu-Idbohrn <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED]
> Resent-From: Cristian Ionescu-Idbohrn <[EMAIL PROTECTED]>
> Resent-To: debian-bugs-dist@lists.debian.org
> Resent-CC: Francois Gurin <[EMAIL PROTECTED]>
> Resent-Date:
yup, when xutils has a working imake and the deps are up i'll resolve this
and the other related bugs. didn't realize it would affect the other
architectures so. the installation paths should be fine in 2.7a-2
from the changelog:
* switched to a static Makefile to quickly work around Imake
On Sun, Apr 16, 2006 at 03:35:25PM -0700, Steve Langasek wrote:
> reopen 362931
> thanks
>
> On Sun, Apr 16, 2006 at 11:32:13AM -0700, Francois Gurin wrote:
> >* New upstream release (Closes: #348324).
> >* Rebuild. (Closes: #362931).
>
> Did you bo
in the future, please include your details in the body of the bug report
On Sun, Apr 16, 2006 at 04:57:36PM +0200, Nicolas Regimbal wrote:
>
> Package: xvkbd
> Version: 2.6-2.1
> Severity: grave
> Justification: renders package unusable
>
>
>
> -- System Information:
> Debian Release: testi
> Since this fix is necessary for the big KDE transition to complete
> (connected to it via imagemagick) it should be uploaded really soon,
> i.e. today or tomorrow would be best. Do you have time to do such an
> upload or would it be okay with you to NMU the package for that?
Go ahead and NMU, th
On Tue, Sep 06, 2005 at 12:37:12AM +0200, Cyril Chaboisseau wrote:
> Package: kismet
> Version: 2005.08.R1-1
> Severity: wishlist
>
> kismet compiles and run cleaning under amd64
>
> please, add it to the list of supported architecture
kismet packages have always included "Architecture: any" so
Package: sfs-common
Version: 1:0.8-0+pre20041016.1-1
Severity: grave
Justification: renders package unusable
SFS packages have a dependency on libgmp3 which is not available on sid.
It has been replaced with libgmp3c2.
--francois
-- System Information:
Debian Release: 3.1
APT prefers testin
wep keys can only be 5, 13, or 16 bytes (40, 104, or 128 bits) in length
the next upload of the kismet package will document this clearly
--francois
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> I tried to Install WMlongrun and dock it in KDE`s dockbar. I have a
> Toshiba Libretto L1 laptop, and I cannot make it work. I installed it by
> apt-get as well as built it myself, but still an error occures every
> time I load it, and of course it wont load. My kernel version is 2.6.11.
> When
I too was looking into zoneminder recently. if anyone wants to bash heads and
start work on packaging the beast that'd be cool.
one of the things i noticed was that it is possible to setup defaults to the
perl config script (to be run in non-interactive mode)
which can be seeded with sane
I'm uploading a new version now that applies some of the patches, putting
fsviewer in a state that compiles and mostly works. As a result I will be
closing the other open bugs as they are technically resolved and dropping the
priority of this one to important.
The BadWindow error seems to o
14 matches
Mail list logo
