-
Notifications
You must be signed in to change notification settings - Fork 45
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
Rebuild hatchling 1.18.0
, Python 3.11.*
, Python-bundle-PyPI-2023.*
to solve setuptools_scm
issue
#546
Rebuild hatchling 1.18.0
, Python 3.11.*
, Python-bundle-PyPI-2023.*
to solve setuptools_scm
issue
#546
Conversation
Instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
New job on instance
|
Something really weird is going on here. Python was reinstalled without any issues, but the installation of hatchling fails due to:
I checked the tarball of the removal step, and this shows that the hatchling versions were removed correctly:
Then I inspected the container resumed from the build step, and it shows:
So it's not there, and it is there... 🤷♂️ |
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
New job on instance
|
Not a fluke, apparently... |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen3 |
New job on instance
|
New job on instance
|
New job on instance
|
I had added user write permissions to the hatchling directories on the Stratum 0, and that did solve the issue for hatchling, but now the same thing is also happening to PYthon-bundle-PyPI. So, Ive done the same for those directories, and will try again. |
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
@bedroge Can you open an issue where you write down some kind of conclusion from this? What you observed, what you tried to work around it, what worked in the end? Did you try doing a recursive |
Yep, I tried that as well (chmod and moving). I'll document it in an issue. |
@bedroge Is this ready to deploy now? |
Manual ingestion procedure:
|
Manual ingestion completed, I've closed the staging PRs. Manual check for just one CPU target:
So, setuptools_scm is now part of Python instead of hatchling, as expected. This PR can be merged. I've also retriggered builds for Bioconductor 3.18 with EB 4.9.1 in #533, which should hopefully succeed now. |
During the installation of R-bundle-Bioconductor with EB 4.9.1 in #533, I ran into the same issue as reported in easybuilders/easybuild-easyconfigs#19849. In order to fix it, we have to apply the changes from easybuilders/easybuild-easyconfigs#19777, which involves a reinstallation of some modules.