Your message dated Sun, 10 Jan 2010 20:12:27 +0000 (WET)
with message-id <20100110201227.7c6452...@kmos.homeip.net>
and subject line Package rt2500 has been removed from Debian
has caused the Debian Bug report #563384,
regarding rt2500-source fails to build with kernel 2.6.32-trunk
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 ow...@bugs.debian.org
immediately.)
--
563384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rt2500-source
Version: 1:1.1.0-b4+cvs20090424-2
Severity: grave
Justification: renders package unusable
rt2500-source fails to build with kernel 2.6.32-trunk-686.
module-assitant's buildlog:
touch config.mk \
&& /usr/bin/make clean
make[1]: Entering directory `/usr/src/modules/rt2500'
make[1]: Leaving directory `/usr/src/modules/rt2500'
dh_clean
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/rt2500'
touch config.mk \
&& /usr/bin/make clean
make[2]: Entering directory `/usr/src/modules/rt2500'
make[2]: Leaving directory `/usr/src/modules/rt2500'
dh_clean
dh_clean: Compatibility levels before 5 are deprecated.
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.32-trunk-686/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modu sed -e 's/##KVERS##/2.6.32-trunk-
686/g ;s/#KVERS#/2.6.32-trunk-686/g ; s/_KV done
# Install module
dh_installdirs lib/modules/2.6.32-trunk-686/kernel/drivers/net/wireless
dh_installdirs: Compatibility levels before 5 are deprecated.
# Build modules
/usr/bin/make KERNDIR=/lib/modules/2.6.32-trunk-686/build PATCHLEVEL=6
make[2]: Entering directory `/usr/src/modules/rt2500'
make[3]: Entering directory `/usr/src/linux-headers-2.6.32-trunk-686'
Building modules, stage 2.
MODPOST 0 modules
make[3]: Leaving directory `/usr/src/linux-headers-2.6.32-trunk-686'
rt2500.ko failed to build!
make[2]: *** [module] Error 1
make[2]: Leaving directory `/usr/src/modules/rt2500'
make[1]: *** [binary_modules] Error 2
make[1]: Leaving directory `/usr/src/modules/rt2500'
make: *** [kdist_build] Error 2
Unfortunately using the rt2x00 driver (which is in the kernel) is not an option:
it connects with AP, but connection is slow or not usable at all. See:
http://rt2x00.serialmonkey.com/phpBB/viewtopic.php?f=5&t=4579 for more
details.
Gergely
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-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 rt2500-source depends on:
ii bzip2 1.0.5-3 high-quality block-sorting file co
ii debhelper 7.4.11 helper programs for debian/rules
ii module-assistant 0.11.1 tool to make module package creati
Versions of packages rt2500-source recommends:
ii wireless-tools 30~pre9-3 Tools for manipulating Linux Wirel
Versions of packages rt2500-source suggests:
ii rutilt 0.16-2 Configuration tool for rt2x00 wire
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:1.1.0-b4+cvs20090424-2+rm
You filled the bug http://bugs.debian.org/563384 in Debian BTS
against the package rt2500. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/563429. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
--- End Message ---
