Summary: | media-tv/plex-media-server-1.10.0 registers its .so files in ldconfig | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | wyvern5 |
Component: | Current packages | Assignee: | Jonathan Vasquez (RETIRED) <fearedbliss> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=646162 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
wyvern5
2018-01-15 21:02:27 UTC
Thanks for reporting this, I'll get to it when I get a chance. If you can submit patches, that would expedite this process. Simply commenting out the LDPATH line (the only line) in /etc/env.d/66plex and running env-update solved the issue for me. With or without that change, revdep-rebuild still thinks that plex-media-server needs to be rebuilt. Can confirm that commenting out LDPATH in /etc/env.d/66plex solves the registration of plex's libraries to the entire system. There one more problem - revdep-rebuild tells that several libraries search for "libdb-4.8.so", and a rebuild doesn't help: * Broken files that require: libdb-4.8.so (64 bits) * /usr/lib64/plexmediaserver/Resources/Python/lib/python2.7/lib-dynload/_bsddb.so * /usr/lib64/plexmediaserver/Resources/Python/lib/python2.7/lib-dynload/dbm.so ldd's output for one of the files: ldd: warning: you do not have execution permission for `/usr/lib64/plexmediaserver/Resources/Python/lib/python2.7/lib-dynload/dbm.so' linux-vdso.so.1 (0x00007ffe80df0000) libdb-4.8.so => not found libpython2.7.so.1.0 => /usr/lib64/libpython2.7.so.1.0 (0x00007fec15a96000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fec15876000) libc.so.6 => /lib64/libc.so.6 (0x00007fec154b4000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fec152b0000) libutil.so.1 => /lib64/libutil.so.1 (0x00007fec150ad000) libm.so.6 => /lib64/libm.so.6 (0x00007fec14d63000) /lib64/ld-linux-x86-64.so.2 (0x00007fec16074000) Those file aren't being linked against the correct library (actually, they aren't being compiled locally, they are just extracted from a DEB package - so that's why a rebuild doesn't help). Hey folks, I've fixed and tested the issue with your fix. Seems good. I pushed it in https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=45282acdcd2bfdb74d8d74ebc712b4cddeadd2e9 That also stabilizes 1.10.1. As for the other issue, you could open another bug report if you want, I am aware of that issue but it hasn't caused any issues with other applications and at this point I consider it cosmetic. It probably would be more complicated to try and split this from being packaged by upstream vs use rebuilding it. Due to this, I don't feel I want to spend time trying to do this, and I would also like to stay close to upstream. Hopefully as we move towards a more containerized future, these issues wouldn't pop up (Since with containers, upstream is free-to & encouraged to package all of their stuff in their own container). - Jonathan |