-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sources for extensions are still downloaded with --module-only
#3849
Comments
This happens because We need those extension instances for the sanity check, but we don't actually need the sources, so we should decouple creating extension instances and downloading sources (so breaking up |
… source/patch files from downloading them (fixes easybuilders#3849) includes deprecating EasyBlock.fetch_extension_sources and replacing it with EasyBlock.collect_exts_file_info
… source/patch files from downloading them (fixes easybuilders#3849) includes deprecating EasyBlock.fetch_extension_sources and replacing it with EasyBlock.collect_exts_file_info
… source/patch files from downloading them (fixes easybuilders#3849) includes deprecating EasyBlock.fetch_extension_sources and replacing it with EasyBlock.collect_exts_file_info
… source/patch files from downloading them (fixes easybuilders#3849) includes deprecating EasyBlock.fetch_extension_sources and replacing it with EasyBlock.collect_exts_file_info
Semi-large refactoring done in #3860 which fixes this... |
I was testing
--module-only
with the EESSI stack to build my module tree and my VM ran out of space. I thought it was the CVMFS cache (which was indeed partially to blame) but actually it turned out that the/tmp
was full and inside I found a sources directory that was populated with lots of extension sources.The text was updated successfully, but these errors were encountered: