Skip to content
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

specified easyblock for extension is not taken into account #3710

Closed
arielzn opened this issue May 28, 2021 · 0 comments · Fixed by #3762
Closed

specified easyblock for extension is not taken into account #3710

arielzn opened this issue May 28, 2021 · 0 comments · Fixed by #3762
Milestone

Comments

@arielzn
Copy link

arielzn commented May 28, 2021

If we specify e.g. in a PythonBundle easyconfig , to install an extension that has the same name of an existing EasyBlock , easybuild will try to use that easyblock for it.

A check should be added to honor an easyblock: definition on the extension dict as e.g. :

    ('tbb', '2021.2.0', {
        'easyblock': 'PythonPackage',
        'source_tmpl': 'tbb-%(version)s-py2.py3-none-manylinux1_x86_64.whl',
        'unpack_sources': False,
        'checksums': ['bf54992d1b5d6135620d5f3f2649bf331e2c412a4af00effd35481a9ecb98ee6'],
    }),
@boegel boegel added this to the next release (4.4.1) milestone Jun 9, 2021
@boegel boegel changed the title on easyconfigs with extensions there are no checks for easyblocks specified on the extension dict specified easyblock for extension is not taken into account Jun 9, 2021
boegel added a commit to boegel/easybuild-framework that referenced this issue Jul 3, 2021
boegel added a commit to boegel/easybuild-framework that referenced this issue Jul 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants