|Summary:||dvgrab does not have correct libdv.so.2 link to correct libdv.so.x.x.x file after emerge of kino 0.7.1 ebuild.|
|Product:||Gentoo Linux||Reporter:||William Fischbacher <willzen89>|
|Component:||New packages||Assignee:||media-video herd <media-video>|
|Package list:||Runtime testing required:||---|
Description William Fischbacher 2004-07-16 00:10:44 UTC
The current dvgrab ebuild requires a "libdv.so.2" link to the current libdv.so.x.x.x. After you "ACCEPT_KEYWORDS='~x86' emerge -v kino", the dvgrab program stops due to a new dependent version of libdv ebuild being emerged as well. Reproducible: Always Steps to Reproduce: 1. emerge dvgrab 2. ACCEPT_KEYWORDS='~x86' emerge -v kino 3. run dvgrab from command prompt. Actual Results: dvgrab: error while loading shared libraries: libdv.so.2: cannot open shared object file: No such file or directory Expected Results: Capture Started "": 0.00 MB 0 frames timecode 00:01:47.01 date 2004.07.13 17:32:38 Capture Stopped Not sure if this is a kino ebuild issue, dvgrab ebuild issue, or a libdv ebuild issue.
Comment 1 Peter Jensen 2004-07-16 01:55:11 UTC
Yet another duplicate of bug 1991, it would seem. This is what 'revdep-rebuild' is for. Oh, and ACCEPT_KEYWORDS on the command line is evil. Use /etc/portage/package.keywords instead.
Comment 2 Patrick Dawson (RETIRED) 2004-08-09 23:22:54 UTC
What Peter said. This is unfortunately a limitation of portage, and why the revdep-rebuild tool exists. When in doubt, re-emerge the package that's giving you errors. If you still have problems after another "emerge dvgrab" and/or revdep-rebuild, please reopen this bug. *** This bug has been marked as a duplicate of 1991 ***
Comment 3 Daniel Webert 2005-05-24 09:44:58 UTC