It works for me, and has no (real) outstanding bugs.
I have no issue with this either - even though it is the development branch and 0.4.x is the stable branch.
Wouldn't it be better to stick to upstream regarding "stableness" decision? Are there some amazing features in 0.5.x for which it would be good to jump ahead of upstream? 0.4 works for me nicely.
I couldn't get 0.4 to connect to one of the access points I use, but that was a while ago and I haven't retried recently.
I've always had issues with wpa_supplicant past 0.3.9 actually, It never really worked for me. Course that's probably my own thing, if one of the at's works their magic with it and its fine I don't have an objection. However Uberload, its really up to you what you want to do as the maintainer.
(In reply to comment #2) > Are there some amazing features in 0.5.x for which it would be good to jump > ahead of upstream? 0.4 works for me nicely. Features for the end user? no. However, 0.5.x is more reliable than 0.4.x for some AP configurations. I would recommend 0.5.4 being marked stable at this time, but we'll keep the 0.4.x branch in the tree too. Mark em stable boys!
0.5.4 works over here nicely, marked stable on x86
builds fine, marked stable on amd64
Marked ppc stable.
Guess it's fixed then