<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Macos on rmqa.com</title>
    <link>https://rmqa.com/tags/macos/</link>
    <description>Recent content in Macos on rmqa.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 25 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rmqa.com/tags/macos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Permission Denied After Unzip and How rmqa Spots Lost Executable Bits</title>
      <link>https://rmqa.com/permission-denied-after-unzip-and-how-rmqa-spots-lost-executable-bits/</link>
      <pubDate>Sun, 25 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://rmqa.com/permission-denied-after-unzip-and-how-rmqa-spots-lost-executable-bits/</guid>
      <description>&lt;p&gt;On Linux and macOS, a program runs only if its file is marked executable. The mark travels with the file in a tar archive, as part of each entry&amp;rsquo;s Unix permissions. Lose it, and every user who downloads the release gets the same first experience:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ ./tidy&#xA;bash: ./tidy: Permission denied&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Then a support question, or a quiet uninstall.&lt;/p&gt;&#xA;&lt;h2 id=&#34;two-ways-it-gets-lost&#34;&gt;Two Ways It Gets Lost&lt;/h2&gt;&#xA;&lt;p&gt;&lt;strong&gt;Packing with the wrong mode.&lt;/strong&gt; A script copies the program with a tool or a step that doesn&amp;rsquo;t keep permissions, or builds the tar archive with fixed file modes, and the program goes in as &lt;code&gt;-rw-r--r--&lt;/code&gt;. The archive looks normal, the program is fine, it just won&amp;rsquo;t start.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
