Convert 64bit DEB to RPM - dependency errors

[Michael Hall]

I am attempting to repackage a DEB version of the Lightworks video editor
as an RPM for Fedora 18 (x86_64).
I have unpacked the DEB file and copied the contents of data.tar.gz (/usr
and subdirectories) to my BUILDROOT directory.
Then I created a spec file which basically just specifies package info and
the %files section.
The RPM builds OK but does not install due to dependency errors.
The dependencies are all actually in the RPM itself, as the Lightworks DEB
package includes its own versions of needed libraries in
/usr/lib/lightworks.
Obviously, the RPM doesn't know about this.
Apparently Debian doesn't use the /usr/lib64 location for 64 bit libraries.
The problem may have something to do with this, or ldconfig or similar.
Adding /sbin/ldconfig to a %post section has made no difference.
Putting the libraries in either /usr/lib or /usr/lib64 in the RPM also
hasn't fixed the issue
Any suggestions on how I can resolve this?

[Ralf Corsepius]

On 05/04/2013 05:06 AM, Michael Hall wrote:
>  I am attempting to repackage a DEB version of the Lightworks video
>  editor as an RPM for Fedora 18 (x86_64).
>  I have unpacked the DEB file and copied the contents of data.tar.gz
>  (/usr and subdirectories) to my BUILDROOT directory.
>  Then I created a spec file which basically just specifies package info
>  and the %files section.
>  The RPM builds OK but does not install due to dependency errors.
>  The dependencies are all actually in the RPM itself, as the Lightworks
>  DEB package includes its own versions of needed libraries in
>  /usr/lib/lightworks.
>  Obviously, the RPM doesn't know about this.
>  Apparently Debian doesn't use the /usr/lib64 location for 64 bit libraries.
Correct. Unless the Debian-packaging is broken, the trick during 
repackaging x86_64/amd64 binariers would be to move these */lib/* libs 
into */lib64 for Fedora and *not* to copy them into */lib.

>  The problem may have something to do with this, or ldconfig or
> similar.
>  Adding /sbin/ldconfig to a %post section has made no difference.
>  Putting the libraries in either /usr/lib or /usr/lib64 in the RPM also
>  hasn't fixed the issue
>  Any suggestions on how I can resolve this? 
Insufficient information, please provide more details. There are many 
details which can go wrong in such kind of attempts.

However, as you seem to be referring to a commercial closed source 
package, the better question would be why these folks don't package 
their package to install to somewhere under /opt/.

Ralf

[Michael Hall]

Yes Lightworks is closed source, but important for professional Linux
multimedia users as it has been used to edit many major Hollywood movies.
Good point about /opt.

I'm collecting some info on a Google Sites page and will post again when it
is ready ...


On Sat, May 4, 2013 at 1:22 PM, Ralf Corsepius <rc040203(a)freenet.de&gt; wrote:

>  On 05/04/2013 05:06 AM, Michael Hall wrote:
>
> > I am attempting to repackage a DEB version of the Lightworks video
> > editor as an RPM for Fedora 18 (x86_64).
> > I have unpacked the DEB file and copied the contents of data.tar.gz
> > (/usr and subdirectories) to my BUILDROOT directory.
> > Then I created a spec file which basically just specifies package info
> > and the %files section.
> > The RPM builds OK but does not install due to dependency errors.
> > The dependencies are all actually in the RPM itself, as the Lightworks
> > DEB package includes its own versions of needed libraries in
> > /usr/lib/lightworks.
> > Obviously, the RPM doesn't know about this.
> > Apparently Debian doesn't use the /usr/lib64 location for 64 bit
> > libraries.
> >
>  Correct. Unless the Debian-packaging is broken, the trick during
>  repackaging x86_64/amd64 binariers would be to move these */lib/* libs into
>  */lib64 for Fedora and *not* to copy them into */lib.
>
>
>   The problem may have something to do with this, or ldconfig or similar.
> > Adding /sbin/ldconfig to a %post section has made no difference.
> > Putting the libraries in either /usr/lib or /usr/lib64 in the RPM also
> > hasn't fixed the issue
> > Any suggestions on how I can resolve this?
> >
>
>  Insufficient information, please provide more details. There are many
>  details which can go wrong in such kind of attempts.
>
>  However, as you seem to be referring to a commercial closed source
>  package, the better question would be why these folks don't package their
>  package to install to somewhere under /opt/.
>
>  Ralf
>
>
>  --
>  packaging mailing list
>  packaging(a)lists.fedoraproject.**org <packaging(a)lists.fedoraproject.org&gt;
>
> https://admin.fedoraproject.**org/mailman/listinfo/packaging<https://a...

[Michael Schwendt]

On Sat, 4 May 2013 12:36:32 +0930, Michael Hall wrote:

>  Apparently Debian doesn't use the /usr/lib64 location for 64 bit
> libraries.
>  The problem may have something to do with this, or ldconfig or similar.
>  Adding /sbin/ldconfig to a %post section has made no difference. 
ldconfig has nothing to do with build-time library dependencies. Unless
you specify special options to make it create some symlinks, which usually is
done by either Makefiles or the RPM spec file already (and not ldconfig).
Primary use of ldconfig is for the run-time linker's cache.

Make sure the libs included in the RPM package are executable.
Watch the rpmbuild output carefully to see what it does during the
late "Provides/Requires" dependency generation steps.

-- 
Fedora release 19 (Schrödinger’s Cat) - Linux 3.9.0-301.fc19.x86_64
loadavg: 0.06 0.14 0.13

[T.C. Hollingsworth]

On Fri, May 3, 2013 at 8:06 PM, Michael Hall <mike(a)mjhall.org&gt; wrote:
>  I am attempting to repackage a DEB version of the Lightworks video
> editor as
>  an RPM for Fedora 18 (x86_64).
>  I have unpacked the DEB file and copied the contents of data.tar.gz (/usr
>  and subdirectories) to my BUILDROOT directory.
>  Then I created a spec file which basically just specifies package info and
>  the %files section.
>  The RPM builds OK but does not install due to dependency errors.
>  The dependencies are all actually in the RPM itself, as the Lightworks DEB
>  package includes its own versions of needed libraries in
>  /usr/lib/lightworks.
>  Obviously, the RPM doesn't know about this. 
Wait, the libraries in question are provided along with the lightworks
package?  If so, these private libraries should probably *not* go into
the system path, and in fact this probably won't even work because the
program most likely hardcodes the location of the libraries instead of
checking the system path.

If I understand you correctly, your only problem is RPM's dependency
generator writes out some bogus requires from these private libraries.
 That's easy to fix:
https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering

>  Apparently Debian doesn't use the /usr/lib64 location for 64 bit
> libraries.
>  The problem may have something to do with this, or ldconfig or similar.
>  Adding /sbin/ldconfig to a %post section has made no difference.
>  Putting the libraries in either /usr/lib or /usr/lib64 in the RPM also
>  hasn't fixed the issue
>  Any suggestions on how I can resolve this? 
-T.C.

[Michael Hall]

Yes that looks like the answer.

This page succinctly describes the problem:
http://www.lysium.de/blog/index.php?/archives/2-rpmbuild-disable-automati...

I solved the problem by using "AutoReqProv: no" in the header.

This may not be optimal but it works for now.

Ideally, EditShare (Lightworks developers) will release an RPM soon (in
addition to current DEB), or even the source (as promised).

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.

www.lwks.com


On Sun, May 5, 2013 at 3:59 AM, T.C. Hollingsworth <
tchollingsworth(a)gmail.com&gt; wrote:

>  On Fri, May 3, 2013 at 8:06 PM, Michael Hall <mike(a)mjhall.org&gt;
> wrote:
>  > I am attempting to repackage a DEB version of the Lightworks video
>  editor as
>  > an RPM for Fedora 18 (x86_64).
>  > I have unpacked the DEB file and copied the contents of data.tar.gz (/usr
>  > and subdirectories) to my BUILDROOT directory.
>  > Then I created a spec file which basically just specifies package info
>  and
>  > the %files section.
>  > The RPM builds OK but does not install due to dependency errors.
>  > The dependencies are all actually in the RPM itself, as the Lightworks
>  DEB
>  > package includes its own versions of needed libraries in
>  > /usr/lib/lightworks.
>  > Obviously, the RPM doesn't know about this.
>
>  Wait, the libraries in question are provided along with the lightworks
>  package?  If so, these private libraries should probably *not* go into
>  the system path, and in fact this probably won't even work because the
>  program most likely hardcodes the location of the libraries instead of
>  checking the system path.
>
>  If I understand you correctly, your only problem is RPM's dependency
>  generator writes out some bogus requires from these private libraries.
>   That's easy to fix:
>  https://fedoraproject.org/wiki/Packaging:AutoProvidesAndRequiresFiltering
>
>  > Apparently Debian doesn't use the /usr/lib64 location for 64 bit
>  libraries.
>  > The problem may have something to do with this, or ldconfig or similar.
>  > Adding /sbin/ldconfig to a %post section has made no difference.
>  > Putting the libraries in either /usr/lib or /usr/lib64 in the RPM also
>  > hasn't fixed the issue
>  > Any suggestions on how I can resolve this?
>
>  -T.C.
>  --
>  packaging mailing list
>  packaging(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/packaging
>