 |
Forgot to close earlier, but better late than never. |
|
|
Will close this after May 31 when monthly builds are done. (Thanks for testing to make sure all will be good). |
 |
I've tested the package for the local installation and luckily it's running well :) |
|
|
@PhyllisSmith thank you for your efforts! I will test the test package build these days and post whether this package is doing fine. |
|
|
@Andrea_Paz It builds from 2.4 because that build uses the thirdparty directory libraries which we have not updated to 2.5 yet. |
 |
Curiosity: since I compile from source (in Arch), I didn't have any library problems. Does this mean that when I compile CinGG, the newest library in the system is used? |
|
|
Arch was updated on our build computer and a new package was created. We did note that as you stated it now uses: usr/lib/libIlmImf-2_5.so A test package build is at: https://cinelerra-gg.org/download/testing/cin-5.1-20200518-arch-x86_64.pkg.tar.xz If you want to check it out. We did not actually try it due to time constraints here and you will have to do a local package install to install it after un-tarring the downloaded file. Let us know if any further problems. We use Fedora so are not as Arch-savvy as you probably are. |
|
|
@ArchBug Yes, this helps us! As you well know, Arch is continuously updating. But we only create an Arch build once a month based on the Arch O/S as it exists around the 29th or 30th of the month. So when arch updates a library that is being used by cinelerra, we are out of sync and end up with exactly the type of scenario you found. So when we hear of this, gg will update Arch and create a static tar so that is a user does not want to wait until the next Arch build, they can use that temporarily. |
- Anonymous
