<html>
    <head>
      <base href="https://bugs.llvm.org/">
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Mac OS .tar.xz release tarball hard to unpack on a Mac"
   href="https://bugs.llvm.org/show_bug.cgi?id=34794">34794</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Mac OS .tar.xz release tarball hard to unpack on a Mac
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>Packaging
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>PC
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>enhancement
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>P
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>binary tarballs
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>unassignedbugs@nondot.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>richard-llvm@metafoo.co.uk
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>llvm-bugs@lists.llvm.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Steps to reproduce:

On macOS 10.12, download the release .tar.xz file and try to open it from
Finder. Amazingly, the Mac "Archiver" tool runs and *compresses* the release to
a .tar.xz.cpio file.

As it happens, the Mac OS "tar" utility will automatically uncompress .xz
compression when extracting (whether you ask it to or not)... but even this is
an undocumented feature of the tar program.

Could/should we ship a file format that the tools installed by default on the
system are able to handle properly? .tar.gz files appear to be handled properly
by default.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>