Bug#511044: clean-patched depends on configure-stamp

[Sven Mueller]

Unfortunately, as far as I recall, simply dropping configure-stamp from
the clean-patched target was basically prohibiting the (policy mandated)
ability to run "debian/rules clean" to get back from any state of the
build tree to one which was equivalent to the pristine unpacked source
(i.e. unpacked of orig.tar.gz and patch from with diff.gz applied),
basically giving you the option to build twice in a row without first
unpacking the source again.

Anyway, this might get fixed with the removal of our huge patch of the
upstream build system (basically running autotools in preparation of a
sourceful upload instead of running them during the build process).

Duncan: This is for you to keep in mind while doing the 2.3 stuff:
Since you already removed the autoconf patch and are running the
autotools instead during build, please check wether you can actually do
a "debian/rules clean" and get back to a state where no modifications
are left in the build tree except for the removal of autogenerated files.

Regards,
Sven