-
Notifications
You must be signed in to change notification settings - Fork 16
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
Handle longer dev.eessi.io
prefix in ingestion
#203
Conversation
I've tested it on the tarball from EESSI/dev.eessi.io-example#7 / https://github.com/EESSI/staging/pull/2175, but now the problem shifts to the next parameter:
|
Ah dang and I merged the staging pr... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this on the tarballs from EESSI/dev.eessi.io-example#7, and works like a charm. Thanks @Neves-P!
This PR addresses an issue when ingesting a tarball with an installation in a non-standard prefix coming from
dev.eessi.io
. This currently fails as spotted by @bedroge when merging https://github.com/EESSI/staging/pull/2176.The call to
ingest_${tar_contents_type_dir}_tarball()
should only point toingest_init_tarball()
,ingest_scritps_tarball()
,ingest_compat_tarball()
oringest_software_tarball()
. This fails, because when ingesting indev.eessi.io
${tar_contents_type_dir}
will instead be$EESSI_DEV_PROJECT
(as currently defined here, to be changed to something not hard-coded soon.) Here I add a condition to look for the type of tarball to be ingested differently indev.eessi.io
builds.