package is once again failing CRAN tests

[corviday]

Explanation provided:

The check problems on the Debian systems are likely caused by attempts
to write to the user library to which all packages get installed before
checking (and which now is remounted read-only for checking).
Having package code which is run as part of the checks and attempts to
write to the user library violates the CRAN Policy's

I don't think this package writes to the user library, but maybe we need better scratch space management or something?

[corviday]

The failing test writes to a file generated by R base function tempfile().

I have reached out to the person who sent me the email to ask if there's something to use instead of tempfile(), but I don't know if or how quickly I will get a response, I'm sure CRAN folks field a lot of questions. I will work on this a couple more days, and if necessary disable that test to resubmit it before the deadline and work on it more at leisure.

[jameshiebert]

I would expect that CRAN tests should provide some minimal temp storage for the tempfile() function. Who have you reached out to and are they in the loop with the folks that set deadlines for CRAN package removal?