I'll try, but uploading pre-builded packages with autobuilder (sounds like and oxy*****, I'm not sure if it's even possible) is out of my scope. i'll check if it's possible via dput and public key. don't blame me if it result in version that eats Your device, though

AFAIK, if You have code and build environment on Your machine, it's all a matter of creating a debian .control file, then autobuilder will swallow it. Unfortunately, I don't have build environment (promising myself, that one day, I'm going to prepare one) , as I'm not coder, which I mentioned many times in the past.

/Estel

// Edit

I think i know how to upload it to extras with less possible hassle included. Can you provide here Debian-compliant (=Maemo-compliant = exactly same You used to build package)...
...? As you've already builded it, you probably know what I'm talking about - heck, most likely, You know it better than me, as I'm actually even pretty unsure, if all mentioned files are mandatory, or only some of them (.tar.gz probably is, <truecrypt_version>.changes is nice to have but not mandatory I think, and .dsc seems to be mandatory also).

then, i'll try to upload them via my garage account. If it succeed, we would only need to make You maintainer of this package, or it won't be able to go out of -devel.