FS#50153 - [xulrunner] is built against a bad version of libvpx
Attached to Project:
Community Packages
Opened by Thomas Jost (Schnouki) - Tuesday, 26 July 2016, 11:34 GMT
Last edited by Connor Behan (connorbehan) - Thursday, 28 July 2016, 20:31 GMT
Opened by Thomas Jost (Schnouki) - Tuesday, 26 July 2016, 11:34 GMT
Last edited by Connor Behan (connorbehan) - Thursday, 28 July 2016, 20:31 GMT
|
Details
Description:
xulrunner 41.0.2-6 (from [community]) is built against libvpx 1.6.0, which is still in [staging]: $ xulrunner XPCOMGlueLoad error for file /usr/lib/xulrunner-41.0.2/libxul.so: libvpx.so.4: cannot open shared object file: No such file or directory Couldn't load XPCOM. $ pacman -Qi libvpx | grep Version Version : 1.5.0-4 $ pacman -Ql libvpx | grep .so libvpx /usr/lib/libvpx.so libvpx /usr/lib/libvpx.so.3 libvpx /usr/lib/libvpx.so.3.0 libvpx /usr/lib/libvpx.so.3.0.0 Additional info: * xulrunner 41.0.2-6 * libvpx 1.5.0-4 |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Tuesday, 26 July 2016, 14:20 GMT
Comment by
Connor Behan (connorbehan) -
Tuesday, 26 July 2016, 17:33 GMT
Comment by Doug Newgard (Scimmia) -
Wednesday, 27 July 2016, 03:17 GMT
And a useless commit message, so we don't know what the purpose of
-6 is.
Right, I accidentally ran communitypkg instead of
community-stagingpkg. What's the proper way to fix this? Building
-7 against the old libvpx and pushing to [community] and then
building -8 against the new libvpx and pushing to
[community-staging]?
That's the only solution I can think of. Packages can be pulled
from Testing, but not from Community AFAIK.