spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

Age	Commit message (Collapse)	Author	Files	Lines
2022-01-14	Update copyright year to 2022	Todd Gamblin	1	-1/+1

2021-09-08	url stats: add `--show-issues` option (#25792)	Todd Gamblin	1	-1/+1
	* tests: make `spack url [stats\|summary]` work on mock packages Mock packages have historically had mock hashes, but this means they're also invalid as far as Spack's hash detection is concerned. - [x] convert all hashes in mock package to md5 or sha256 - [x] ensure that all mock packages have a URL - [x] ignore some special cases with multiple VCS fetchers * url stats: add `--show-issues` option `spack url stats` tells us how many URLs are using what protocol, type of checksum, etc., but it previously did not tell us which packages and URLs had the issues. This adds a `--show-issues` option to show URLs with insecure (`http`) URLs or `md5` hashes (which are now deprecated by NIST).
2021-01-02	copyrights: update all files with license headers for 2021	Todd Gamblin	1	-1/+1
	- [x] add `concretize.lp`, `spack.yaml`, etc. to licensed files - [x] update all licensed files to say 2013-2021 using `spack license update-copyright-year` - [x] appease mypy with some additions to package.py that needed for oneapi.py
2019-12-30	copyright: update copyright dates for 2020 (#14328)	Todd Gamblin	1	-1/+1

2019-01-01	copyright: update license headers for 2013-2019 copyright.	Todd Gamblin	1	-1/+1

2018-10-17	relicense: replace LGPL headers with Apache-2.0/MIT SPDX headers	Todd Gamblin	1	-23/+4
	- remove the old LGPL license headers from all files in Spack - add SPDX headers to all files - core and most packages are (Apache-2.0 OR MIT) - a very small number of remaining packages are LGPL-2.1-only
2018-03-24	Update copyright on LLNL files for 2018. (#7592)	Todd Gamblin	1	-1/+1

2018-01-28	Cleaned up JUnit report generation on install (#6977)	Massimiliano Culpo	1	-0/+62
	* Cleaned up JUnit report generation on install The generation of a JUnit report was previously part of the install command. This commit factors the logic into its own module, and uses a template for the generation of the report. It also improves report generation, that now can deal with multiple specs installed at once. Finally, extending the list of supported formats is much easier than before, as it entails just writing a new template. * Polished report generation + added tests for failures and errors The generation of a JUnit report has been polished, so that the stacktrace is correctly displayed with Jenkins JUnit plugin. Standard error is still not used. Added unit tests to cover for installation failures and installation errors.