A listing of detectable policy problems in the thrift Debian packaging (in contrib/) can be found with a lintian run:
I'll note some of them here for posterity.
The libthrift-dev package should have a versioned dependency on libthrift0, i.e., in debian/control:
You don't need the "build-essential" bit in Build-Depends.
Syntax is a bit off in debian/control for the Description fields; I'll attach a patch.
You need a man page for /usr/bin/thrift.
The python-thrift-dbg package should be in Section: debug.
Debian packages shouldn't be shipping anything in /usr/local; that's supposed to be reserved for the local system admin. There isn't much reason for this anyway; the dirs being shipped by python-thrift-dbg here are empty.
The libthrift-ruby package should be in Section: ruby. Also, according to http://wiki.debian.org/Teams/Ruby/Packaging , it looks like Ruby packages are undergoing a name change in the current Debian testing suite. libthrift-ruby probably needs to become ruby-thrift and switch to using gem2deb.
This will probably be addressed under
This is complaining because the package name of a library package should usually reflect the soname of the included library (see chapter 5 of the Debian Library Packaging Guide for more info). Something is fishy here, though. Did you intend to distribute the c-glib library as "libthrift0"? If so, where is the cpp library supposed to go? I don't think I see it after a quick search through the packages.
See the lintian explanation for detailed info. Basically, you need some extra Sauce to add a dependency to php5-thrift on a PHP with a compatible API version.
libthrift-java should be Section: java
libthrift-cil should be Section: cli-mono
Thrift.dll shouldn't have its executable bit set.
Yeah, installing into /usr/usr/local/lib is kinda wacko. Ought to be /usr/lib.
And as a final note, a lot of the packaging here could be pretty greatly simplified and better future-proofed using the Debhelper 7 command sequencer ("dh").