Control: severity -1 minor Thanks Hello Wolfgang,
thanks for your quick response!
With your calls, you should not use the '-f' parameter. Without '-f', the timestamp is passed on to date/gdate for parsing, which yields the following for me on Debian Buster x86_64:
That changes the behavior: Without '-f', the called program will see time passing. In my case the call goes to a build process which takes several seconds, and the timestamp that I want to influence is taken at the very end of it. So without the '-f', the "fake clock" would show a non-deterministic, and most likely different, time. That's exactly the thing that I want to avoid.
https://github.com/wolfcw/libfaketime
Thanks! I hoped that it could parse the absolute timestamp anyway, but 4b) is clear enough. Oh well.
I hope that helps a bit.
It does indeed, thank you. Like I already mentioned, in my case git's `iso` makes faketime happy, and makes me brush up my knowledge on bash.
I also agree that "Success" isn't much of a useful error message here. In this case, it's created by a call to the standard perror() system call, which should be considered to be replaced with something more meaningful. I'll put that on the todo list. :-) However, more useful error messages are printed by the wrapper when '-f' is not used.
Sounds good. So in summary: - The parsing is "as intended". - git and faketime have different about "strict ISO date formats". - The bug is actually only the `: Success` part of the output. Therefore, the bug is only minor. Also, I have a manual workaround anyway. Cheers, Ben Wiederhake
