<div dir="ltr">On Wed, Nov 6, 2013 at 10:32 AM, Stuart Morgan <span dir="ltr"><<a href="mailto:stuart@tase.co.uk" target="_blank">stuart@tase.co.uk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wednesday 06 Nov 2013 10:05:08 Richard Shaw wrote:<br>
> Ok, looks like it's not my fault. I went back through the spec file and saw<br>
> the same thing, the vers_string was set correctly...<br>
<br>
</div>If you're using an exported copy of the source but then applying patches on<br>
top of that you need to remove the EXPORTED_VERSION file.<br>
<br>
When I added that I didn't anticipate that packagers would thwart me by<br>
downloading the tarball for the 0.27 tag then diffing that against 0.27-fixes, to<br>
create a patch which then gets applied to the 0.27 source.</blockquote><div><br></div><div>I should be in sync with what Chris is doing with the RPM spec file on Github so it's not just RPM Fusion that's affected by this. Why did this just show up for 0.27? It worked fine for 0.26. The tag/diff process has been in play since Jarod maintained the RPM Fusion packages.</div>
<div><br></div><div><br></div><div>Thanks,</div><div>Richard </div></div></div></div>