`make clone` and `make dev` complain about clock skew due to clamping logic

[eloquence]

When building the RPM, we're setting all files to a date in the future:

securedrop-workstation/scripts/build-rpm.sh

Line 14 in 3ff2eb9

find . -type f -exec touch -m -d "+1 day" {} \;

This makes sense to satisfy RPM's build logic, which will use whichever time is older (time from RPM changelog vs. file on disk). So if we don't do this, older files will make the file non-reproducible. See #1114.

However, it leaves the files on disk 1 day in the future, which has side effects. :-) In particular, make clone will tar them up and ship them into dom0, and tar will complain about the time drift; similarly, make has clock skew detection and will also complain about it when you run make dev.

Since clock skew issues can be pretty gnarly to track down in Qubes, this seems desirable to fix to avoid hunting down issues that aren't issues.

A simple fix may be to just set every file to the current time after the RPM is built (maybe on a trap clause?).