<div dir="ltr"><div><div><div><div><div><div>Yes that looks like the answer.<br><br>This page succinctly describes the problem:<br><a href="http://www.lysium.de/blog/index.php?/archives/2-rpmbuild-disable-automatic-dependency-analysis.html">http://www.lysium.de/blog/index.php?/archives/2-rpmbuild-disable-automatic-dependency-analysis.html</a><br>
<br></div>I solved the problem by using "AutoReqProv: no" in the header.<br><br></div>This may not be optimal but it works for now.<br><br></div>Ideally, EditShare (Lightworks developers) will release an RPM soon (in addition to current DEB), or even the source (as promised).<br>
<br></div>Either way, I think Lightworks is important enough for a bit of faffing about. It is a viable competitor for Final Cut Pro, Premiere, Sony Vegas etc.<br></div><br></div><a href="http://www.lwks.com">www.lwks.com</a><br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 5, 2013 at 3:59 AM, T.C. Hollingsworth <span dir="ltr"><<a href="mailto:tchollingsworth@gmail.com" target="_blank">tchollingsworth@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, May 3, 2013 at 8:06 PM, Michael Hall <<a href="mailto:mike@mjhall.org">mike@mjhall.org</a>> wrote:<br>
> I am attempting to repackage a DEB version of the Lightworks video editor as<br>
> an RPM for Fedora 18 (x86_64).<br>
> I have unpacked the DEB file and copied the contents of data.tar.gz (/usr<br>
> and subdirectories) to my BUILDROOT directory.<br>
> Then I created a spec file which basically just specifies package info and<br>
> the %files section.<br>
> The RPM builds OK but does not install due to dependency errors.<br>
> The dependencies are all actually in the RPM itself, as the Lightworks DEB<br>
> package includes its own versions of needed libraries in<br>
> /usr/lib/lightworks.<br>
> Obviously, the RPM doesn't know about this.<br>
<br>
</div>Wait, the libraries in question are provided along with the lightworks<br>
package? If so, these private libraries should probably *not* go into<br>
the system path, and in fact this probably won't even work because the<br>
program most likely hardcodes the location of the libraries instead of<br>
checking the system path.<br>
<br>
If I understand you correctly, your only problem is RPM's dependency<br>
generator writes out some bogus requires from these private libraries.<br>
That's easy to fix:<br>
<a href="https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering" target="_blank">https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering</a><br>
<div class="im HOEnZb"><br>
> Apparently Debian doesn't use the /usr/lib64 location for 64 bit libraries.<br>
> The problem may have something to do with this, or ldconfig or similar.<br>
> Adding /sbin/ldconfig to a %post section has made no difference.<br>
> Putting the libraries in either /usr/lib or /usr/lib64 in the RPM also<br>
> hasn't fixed the issue<br>
> Any suggestions on how I can resolve this?<br>
<br>
</div><span class="HOEnZb"><font color="#888888">-T.C.<br>
</font></span><div class="HOEnZb"><div class="h5">--<br>
packaging mailing list<br>
<a href="mailto:packaging@lists.fedoraproject.org">packaging@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/packaging" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/packaging</a></div></div></blockquote></div><br></div>