Hi Dirk,
On 22.04.2015 16:40:18, Dirk Eddelbuettel wrote:
> | > R should work just fine with or without TZ. Most systems seem to have it;
> | > Debian never did and I am not aware of side effects (but we sometimes do
> set
> | > TZ in our (user) analysis scripts).
> |
> | Indeed, it does, see:
> |
> | $ TZ="GMT+1" Rscript -e "system('date')"
> | Mi 22. Apr 19:57:33 GMT 2015
>
> Not a good example (because of system). Try
>
> edd@max:~$ Rscript -e 'print(Sys.time())' ## I am in America/Chicago
> [1] "2015-04-22 16:38:08.484921 CDT"
> edd@max:~$ TZ="UTC" Rscript -e 'print(Sys.time())' ## UTC override
> [1] "2015-04-22 21:38:15.433783 UTC"
> edd@max:~$ Oh yes, this example is much better... > | > ii) contact upstream which I'll will and see what can be done about > makeing > | > the behaviour more robust (as it used to be prior to R 3.1.3 as well, I > | > think) > | Yes, contacting upstream would be great, thanks. > | But I think prior to R 3.1.3 also FTBFS with TZ set, see: > | > | > https://reproducible.debian.net/rbuild/testing/amd64/r-base_3.1.2-3.0~reproducible1.rbuild.log > > That's helpful, and probably also before my patch. Yes, they FTBFS before your patch: r-base 3.1.2-3.0~reproducible1 FTBFS r-base 3.1.2.20150304-1 FTBFS r-base 3.1.2.20150306-1 FTBFS r-base 3.1.3-1 FTBFS r-base 3.1.3.20150409-1 FTBFS r-base 3.1.3.20150410-1 FTBFS r-base 3.1.3.20150413-1 FTBFS r-base 3.2.0-1 FTBFS r-base 3.2.0-2 FTBFS We don't only have data for these versions, but I was told prior versions also FTBFS. > This "smells" like an upstream issue (when TZ gets set) but I'd love for us > to narrow it down. This has been _excellent_ work by you so far. Keep it > coming :) Thanks, I'll try to narrow this down but I will not find time to do this before next week. Best, Philip
signature.asc
Description: Digital signature
