Your message dated Mon, 19 May 2008 20:27:54 +1000
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#481885: Fixed (madwifi-source: can't build with 
linux-image-2.6.25-2-686)
has caused the Debian Bug report #481885,
regarding madwifi-source: can't build with linux-image-2.6.25-2-686
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
481885: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481885
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: madwifi-source
Version: 1:0.9.4~rc2-1
Severity: important
Justification: fails to build from source

m-a a-i madwifi fails. the log in /var/cache/modass/ is basically empty, 
apart from the build log starting line and the date. 



-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages madwifi-source depends on:
ii  bzip2                         1.0.5-0.1  high-quality block-sorting file co
ii  debhelper                     7.0.8      helper programs for debian/rules
ii  module-assistant              0.10.11.0  tool to make module package creati

madwifi-source recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On Monday 19 May 2008 20:14:35 Gijs Hillenius wrote:
> Please ignore this bug report.
> 
> I reported this bug on madwifi-source, because it would not build on
> linux-iamage-2.6.25-2-686. Well, I'm an oof. 

Probably why the modass logs were so "empty" ;-) Closing.

Thanks, Kel.


--- End Message ---

Reply via email to