Well, when i tried to get it into the repos it was not easy (original maintainer not reachable => update of dropn900 in repos not possible). Now this seems to be different, as sixwheeledbeast told me.

However, i'm not sure how to handle the update in the cleanest way. The old dropn900 depends on the package "python-dropbox-client", which was the name for the api provided by dropbox back then.

When i ported dropn900 to the new (SSL only) dropbox api, it was called "dropbox-python-sdk". I made a maemo package back then with version 1.5.1 of the sdk. Version 1.5.1 is the sdk version currently in use by the patched dropn900

I have a working version of the current sdk (2.2.0) on my n900, and it is a bit faster than 1.5.1.
Downside: It needs urllib3 backport for python2.5 (size: 3.4 MB), which i took from modrana.

So, for me the open questions are:
Remove python-dropbox-client dependency from dropn900 and replace by dropbox-python-sdk?
What to do with python-dropbox-client?
What's the best way to update dropbox-python-sdk to 2.2.0?