Comments (6)
I do not understand enough to know what is requested. If someone can explain again, or take action, this would be great.
Package managers that can build from source (e.g., Homebrew, Spack, Portage...) save for each package release the hash of its source tarball. When building the software, the hash of the downloaded tarball is compared against the known hash and if it does not match, the build is immediately aborted for security reasons and an error message is shown to the user. To update the hash, the build error must be reported, the maintainers of the package manager will want to find out why the hash changed, and then they need to patch their own software if the hash changed for benign reasons.
Two suggested approaches for the future are...
- Do not re-release with the same version number.
- Do not silently re-release with the same version number and leave a note for package manager maintainers why the hash changed.
from lapack.
Hi @chenrui333. Yes it got retagged, and I just did it again, like a minute ago, we had an error in our "thanks". This is corrected now. Sorry about this. Thanks for checking. Julien.
from lapack.
no worries, thanks for confirming it, it would be nice to push a new version in either case. Thanks! :)
from lapack.
It might be a good idea to mention any such re-tagging on the Releases page if incrementing the version number is not desired. (And as I have learned, ideally download and re-upload the github-generated archives together with their checksums - sometimes github changes something in their toolchain that leads to re-generation of the automatically created archives with a new checksum). Some people, and especially the distribution packagers, use the archive checksum to ensure an official source package has not been tampered with - silent re-releases like this are likely to set off alarm bells somewhere.
from lapack.
I am not sure any longer that we are speaking about the same thing. I edited the release page, but I do not think any longer that this impacts the checksum. Yes, we might have changed the retagged / changed the checksum on Friday when we released. We realized that some documentation were not correctly updated. So I think we released and erased the release and released a second time. If something needs to happen, like releasing with a new version number (3.12.1), this is OK. I do not understand enough to know what is requested. If someone can explain again, or take action, this would be great.
from lapack.
Hi @christoph-conrads and @martin-frbg, thanks for explaining. We'll try to be better next time. Julien.
from lapack.
Related Issues (20)
- Overwriting `CMAKE_INSTALL_RPATH` in CMakeLists.txt HOT 1
- vectorization of lapack routines. HOT 7
- Allow installing binaries to subdirectory while keeping CMake package scripts in the same place HOT 1
- xORMQR and xLARFB discrepancy with documentation HOT 17
- ?hbmv and ?hpmv and the documentation notes seem to be inconsistent
- lapack_sgeev routine not going to all routines shown in the call graph while debugging. HOT 17
- poor accuracy with dsterf
- in-place (scaled) matrix transposition: imatcopy HOT 6
- xGETC2 order of loops in finding max element of submatrix HOT 3
- Uninitialized variables in BLAS test HOT 4
- Less accuracy due to FMAs HOT 8
- cblas_dgbmv: Result of row-major is not consistent to column-major HOT 6
- [Documentation] Wrong description of array A in LAPACK ?tfsm routines HOT 2
- SCNRM2 and DZNRM2 fail on master HOT 1
- Xerbla_array, Xerbla and lsame in BLAS or LAPACK? HOT 1
- LAPACK master does not compile with CMake 3.9
- Highly scale-dependent efficiency of ZHEEVR and DSYEVR HOT 3
- BDSQR workspace does not take into account fallback into LASQ1 HOT 1
- *syevr eigenvalues depend on whether eigenvectors are computed or not HOT 11
- xSTEMR: are zero eigenvalues sufficiently accurate?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lapack.