Non-zero epoch handling requires improvement

[Michael B. Trausch]

Seems that AutoPPA does not work with packages that require an epoch. (For various technical reasons, AllTray requires a "1" epoch.)

However, the command line:

autoppa alltray-1:0.7.4dev.200909291200-ppa1

does not upload anything, instead it creates the files and then autoppa builds the file names incorrectly:

== Uploading signed source for alltray ==
Can't open /home/mbt/Projects/Free/AllTray/alltray_1:0.7.4dev.200909291200-ppa1.8.04_source.changes
Can't open /home/mbt/Projects/Free/AllTray/alltray_1:0.7.4dev.200909291200-ppa1.8.10_source.changes
Can't open /home/mbt/Projects/Free/AllTray/alltray_1:0.7.4dev.200909291200-ppa1.9.04_source.changes
Can't open /home/mbt/Projects/Free/AllTray/alltray_1:0.7.4dev.200909291200-ppa1.9.10_source.changes

Because:
mbt@zest:~/Projects/Free/AllTray$ ls *source.changes|grep ppa1
alltray_0.7.4dev.200909291200-ppa1.8.04_source.changes
alltray_0.7.4dev.200909291200-ppa1.8.10_source.changes
alltray_0.7.4dev.200909291200-ppa1.9.04_source.changes
alltray_0.7.4dev.200909291200-ppa1.9.10_source.changes

I can upload manually for the time being, but this should be handled so that non-zero epochs can be used in a fully automatic fashion.

[Michael B. Trausch (mtrausch)]

Specifically, the working directory autoppa creates has the epoch in it; it should not, also, it should expect the generated files from dpkg to not have the epoch number in them. I believe that's the extent of the issue here, but I'm not sure.