# upstream commit FILE5_33-59-g4fdbc347 <https://github.com/file/file/commit/FILE5_33-59-g4fdbc347> Control: found 902643 1:5.30-1+deb9u3 Control: fixed 902643 1:5.34-1
Elliott Mitchell wrote...
> Sample invocation of `dump` might be `dump -u0 -f fs_dump.0 /dev/loop0`
> and then `dump -u1 -f fs_dump.1 /dev/loop0`. Examine the output of
> `file fs_dump.0` and `file fs_dump.1`. The dates for the previous dump
> and current dump are swapped (...)
*That* is the information needed to start working on a report. So this
exists in stretch only, I'll try to include it in another point release.
> (for the level 0 is is reporting the epoch,
> "never", "none", or "No previous dump" would be better). Also noticing
> for the level 0 is is reporting "Level zero" instead of "Level 0".
That's arguable. About the timestamp, the program just dumps the value
zero which gets printed as the epoch. The literal "zero" however is
result of an extra rule in libmagic's patterns. Personally, I'd either
have such an extra for either both cases or none at all. Any mix seems
weird.
Christoph
signature.asc
Description: PGP signature
