Beep security update
Does GPL say anything about distributing source via git repositories? I mean, it talks about &quot;preferred form of the work for making modifications&quot;. But when I click through to the Debian PTS page for Beep at <a href="https:&#x2F;&#x2F;tracker.debian.org&#x2F;pkg&#x2F;beep" rel="nofollow">https:&#x2F;&#x2F;tracker.debian.org&#x2F;pkg&#x2F;beep</a> it shows a git link to <a href="http:&#x2F;&#x2F;git.deb.at&#x2F;w&#x2F;pkg&#x2F;beep.git" rel="nofollow">http:&#x2F;&#x2F;git.deb.at&#x2F;w&#x2F;pkg&#x2F;beep.git</a> which was last modified 23 months ago, so obviously does not contain this security fix. How is the GPL upheld if security fixes aren&#x27;t available together with the main git repository?<p>I don&#x27;t mean to cause drama,  because I think the Debian security team does an awesome job of keeping an eye on patching everything in the distribution. But I&#x27;m really curious about how one would go about with further development on a package like this when the git commits aren&#x27;t available? There&#x27;s probably a source tarball for the .debs in the apt repos (hard to tell from a mobile web browser) but is that good enough if it doesn&#x27;t contain git commits?<p>Also I really just wanted to read this security patch source diff on the go :)