Rebuild hatchling 1.18.0, Python 3.11.*, Python-bundle-PyPI-2023.* to solve setuptools_scm issue
#546
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
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? |
boegel
added
the
bot:deploy
bedroge
added
ready-to-deploy
|
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. |
boegel
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.