You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
The released tar-balls of version 3.12.1 on GitHub and the official website do not include the commit which updates the versions from 3.12.0 to 3.12.1 and the update of the year in the copyrights in the license file.
Extract tar-ball using e.g. tar -xvzf lapack-3.12.1.tar.gz
Check versions:
CMakeLists.txt LAPACK_PATCH_VERSION is still 0: set(LAPACK_PATCH_VERSION 0)
INSTALL/ilaver.f VERS_PATCH is still 0: VERS_PATCH = 0
LICENSE still references year 2023
Why is this important for us:
We want to use LAPACK as a thirdparty and therefore the "officially" released version including the appropriate LICENSE file.
Checklist
I've included a minimal example to reproduce the issue
I'd be willing to make a PR to solve this issue
The text was updated successfully, but these errors were encountered:
Description
The released tar-balls of version 3.12.1 on GitHub and the official website do not include the commit which updates the versions from 3.12.0 to 3.12.1 and the update of the year in the copyrights in the license file.
Merge of the referenced commit: #1095
Used download link of the Tar-Ball (URL from LAPACK Website in section https://www.netlib.org/lapack/#_lapack_version_3_12_1 points to the same URL for downloading): https://github.com/Reference-LAPACK/lapack/archive/refs/tags/v3.12.1.tar.gz
Steps to reproduce:
tar -xvzf lapack-3.12.1.tar.gz
set(LAPACK_PATCH_VERSION 0)
VERS_PATCH = 0
Why is this important for us:
We want to use LAPACK as a thirdparty and therefore the "officially" released version including the appropriate LICENSE file.
Checklist
The text was updated successfully, but these errors were encountered: