#741: rpm for SuSE 10.1 has dependency problems
----------------------------------+-----------------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone: version 0.9.x -
progressive release candidate phase
Component: madwifi: driver | Version: v0.9.0
Keywords: SuSE 10.1 dependency | Patch_attached: 0
----------------------------------+-----------------------------------------
I loaded SuSE 10.1 from my boxed set. No Atheros drivers as there had
been in 10.0 for my ThinkPAD X31.
Google comes to the rescue, and I find your site. I use the instructions
on how to put the SuSE directory into my installation list. This is
sweet, and as it should be. Too bad SuSE didn't tell me to do this.
I pulled down the tools and the kernel modules. Also sweet, but
MOM&POP(TM) would have had a bit of problems figuring out which kernel
modules to use once they were displayed in YAST.
Fortunately MOM&POP(TM) paid for my college education, and I knew which
kernel module to choose. Everything came up fine.
Then about a day ago I got my "update alarm" go off, telling me there were
updates to some packages. Also sweet! But when it tried to update the
kernel modules, I got this dependency
check:
Unresolved dependencies:
Updating madwifi-kmp-default-0.9.0_2.6.16.13_4.1-1.2.i586 to madwifi-kmp-
default-0.9.1_2.6.16.21_0.8-1.1.i586[20060703-115356]
There are no installable providers of kernel(net_core) == 7a69389625271e0b
for madwifi-kmp-default-0.9.1_2.6.16.21_0.8-1.1.i586[20060703-115356]
Bummer. This had not happened on the previous set of modules. So I tried
doing things like switching over to wired networking and removing the
module then re-installing. Bad thing. Now it won't install at all.
Fortunately MOM&POP(TM) encouraged me to go on to graduate school, so I
went around YAST, went
to your site, selected the rpm that existed before the nasty messages, and
rpmed it into place.
Yes, and this only took a master's degree in computer science and 35 years
in the industry, but
madwifi seems to work again. But now my little "you have to update
madwifi" button is blinking
at me again....sigh.
So I thought I would let you know that not everything is well with your
update of July 6th, and
as more and more people Google and find your site, they won't know that it
is just that one
rpm that is bad.
Keep up the good work, though! It is a heck of a lot easier than having
to code it myself (now
you should hear wild peals of laughter in the background).....no, really,
I can write code! But
my "C" looks a lot like Fortran......
Warmest regards,
maddog
P.S. I filled in the Ticket Properties as best I could. Sorry if I
screwed something up.
--
Ticket URL: <http://madwifi.org/ticket/741>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
