When using portable and nomtime on tar.c, set date to something other than 0

[isaacs]

npm/osenv#16

Apparently there are architectures that don't like files with modified dates of the Unix epoch.

Always put SOME value in there, perhaps?

cc: @zkat @iarna

[isaacs]

Ah! It looks like this only happens when the file is created with noMtime, but not unpacked with noMtime. So the issue is that new versions of npm are creating packages that old versions of npm unpack badly.

Not actually a tar issue, I guess. This is working as intended.