@disappear: No need to thank me (though I do appreciate it). I enjoy doing things that actually help other people, and this is something I can actually do to help.

- In related news -

Aircrack-NG 1.1-maemo9 is now in Extras-Testing. Rejoice, those who have -testing enabled, but not -devel.

Test, or if you've already tested, vote here, so that the masses with only Extras enabled may have aircrack-ng goodness too:
http://maemo.org/packages/package_in...ng/1.1-maemo9/
(It's not the most intuitive system - you need to log in with your maemo.org account, which is separate from your talk.maemo.org account, AND, you press the thumbs up/thumbs down icons to vote. So press the up thumb to vote for, press the down thumb to vote against.)

Here's the list of blockers which you should diligently check for before voting (I don't believe that this version violates any of them, as it has been optified, has a bugtracker link, and is otherwise awesome, but, if you genuinely believe aircrack-ng violates any of these, say so in here, so that I may look into fixing it):
http://wiki.maemo.org/Extras-testing...klist#Blockers

Also, the repository is being really weird. Last I looked, -devel armel was at 1.1-maemo9, as was -testing armel, BUT -devel i386 is still stuck on 1.1-maemo8, so there's nothing in -testing i386 for aircrack-ng.

This doesn't actually effect usability on the N900, because we see/use the armel versions on our devices, and the i386 version is just there...for some odd reason. But I'm worried that this is a symptom of some greater server-side issue.