Well, if I succeed you just can take my work as it will hopefully turn out to be much more easier than writing python scripts to do the packaging.
But anyway if the scripts work for you and you are happy with them you can just do it this way of course.
But you should check your packages at least with lintian.
I will try the Makefile method first because I also want to make a Debian package for amd64 and you only seem to provide a package for i386.
I think we should do something related to this. U++ is divided in too many places and that create confusion to some users. They look at sf.net and see no release(nightly builds are in google code) and they think the project is dead or advancing slowly.
I think we should put a notice on sf.net that we're using google code for repository(mirror) and nightly builds and on google code we should specify that we use sf.net for stable releases.
Another confusion is which bug tracker use U++ devs? Both googlecode and sf.net are providing one. I think we don't use one because we got used to get bug reports in forum and that's because bugs are quickly solved.
I see now So, "stables" are going in sf.net and nightly in googlecode. Bug tracking is happening in both(and forum)? I see googlecode bug tracker ignored... bug opened by Christoph Korn is not closed yet. There are also a few bugs left opened in sf.net even if they got solved in upp code.