bump JasPer version to latest 2.0.24 for 2020b generation of easyconfigs + remove easyconfigs for ancient JasPer 2.0.1.4 with GCCcore/10.2.0#12277
Conversation
…igs + remove easyconfigs for ancient JasPer 2.0.1.4 with GCCcore/10.2.0
|
@boegelbot please test @ generoso |
|
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 785817867 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
I did a test build, but forgot the upload. I error out with: Which leads me to qt/qtimageformats@704868d |
|
@boegelbot please test @ generoso |
|
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 785855658 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @branfosj |
|
Test report by @boegel |
|
Test report by @boegelbot |
|
Test report by @boegel |
|
Test report by @boegel |
|
Test report by @branfosj |
|
Going in, thanks @boegel! |
While working on OpenCV for
foss/2020b(#12265), I noticed we're (probably by accident) using an ancient version of JasPer for the2020bgeneration of easyconfigs...JasPer 2.0.14 was released Sept'17 (see https://www.ece.uvic.ca/~frodo/jasper/#download), and there are several more recent releases available through https://github.com/jasper-software/jasper/releases . In addition, we already have an easyconfig for JasPer 2.0.24 with
GCCcore/10.2.0(see #12077), so we really should be using that instead.The fact that only old releases are mentioned at https://www.ece.uvic.ca/~frodo/jasper/#download is probably what caused this.
Fallout is relatively limited for now, but it does involve
Qt5, so people who already have it installed will have to rebuild it to avoid running into surprises...