+
+ This has been reported as conflicting with the POSIX specs. The reason is
+ that offsets and sizes of non-zero data blocks were stored in multiple
+ instances of GNU.sparse.offset/GNU.sparse.numbytes variables. However,
+ POSIX requires the latest occurrence of the variable to override all
+ previous occurrences.
+
+ To avoid this incompatibility new keyword GNU.sparse.map was introduced
+ in tar 1.15.2. Some people might still need the 1.14 way of handling
+ sparse files for the compatibility reasons: it can be achieved by
+ specifying `--pax-option delete=GNU.sparse.map' in the command line.
+
+ See FIXME-1.14-1.15.1-1.20, below.