-
Notifications
You must be signed in to change notification settings - Fork 703
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
R-bundle-CRAN-2023b, Brunsli-0.1 patch, and easyconfigs.py #20756
Conversation
@Micket : I have just came across your PR #20675 which contains an easyconfig for [UPDATE]: I did a |
Test report by @verdurin |
@moravveji - thanks for your contribution and welcome to EasyBuild. Could you resolve the conflicts, please, preferably by removing them from your PR and specifying them as dependencies instead. The build failure I saw was a checksum mismatch. |
To be clear: conflicts here are caused by the merge of #20675 |
…cluded in pr 20675
Thanks @verdurin and @boegel for your comments. I have few questions about some (minor?) issues with this PR:
Thanks in advance |
Looks like an SSL issue. Might be intermediate.
The patch is not required as it is handled in the EC you mentioned: https://github.com/easybuilders/easybuild-easyconfigs/pull/20675/files#diff-0ea948e4665fcb18be3b5d531fc2c022b3124c586df87e5cb05eea1c7f69b268R30 However I think the patch is clearer than the
3 steps:
|
@moravveji I created a PR to resolve the conflicts stopping this from being merged: moravveji#1 Feel free to handle it yourself, just wanted to offer it to get this merged as we like to use it at our site too. So thanks for the effort of updating this monstrous EC |
Thanks @Flamefire for your new branch. I think I already handled the conflicts in my current branch, by updating the For
|
easybuild/easyconfigs/i/ImageMagick/ImageMagick-7.1.1-33-GCCcore-13.2.0.eb
Outdated
Show resolved
Hide resolved
Almost: it must be a tuple, not a list, i.e. "()" instead of "[]" |
This should be easy ;-)
I have tried different ways to get around this (such as using
Can someone plz give an advice? |
Co-authored-by: Alexander Grund <[email protected]>
Well, seems like EB is clever enough to spot the trick, and refuse to accept it. I get this error now:
Makes me think if it is legitimate to make an exception here, and remove the checksums only for this specific extension ( |
The syntax was wrong, my mistake, sorry: moravveji#2 |
'checksums': ('0a604949bae91410a150a22cfa02d954f5b83166cc7a73e5409554d00e0417a7', # older source | ||
'23ff303856ff09734e8ef280cec94556a15cdc702727ae5d02f8cfa4d8f473b7'), # newer source |
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.
'checksums': ('0a604949bae91410a150a22cfa02d954f5b83166cc7a73e5409554d00e0417a7', # older source | |
'23ff303856ff09734e8ef280cec94556a15cdc702727ae5d02f8cfa4d8f473b7'), # newer source | |
'checksums': [ | |
('89cba854167a2b051a58cf3b73ccbf74eeb47c890ac39720611cd41f86b94684', | |
'0a604949bae91410a150a22cfa02d954f5b83166cc7a73e5409554d00e0417a7'), | |
], |
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.
Or this, yes. To me it looks better on 2 lines for the single list element though. I also took the liberty to improve the error message seen here: moravveji#2
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.
I see the many green lights again. So, thanks @Flamefire for the nice fix.
All the necessary adjustments after the recent merges are included here.
So, it this PR ready for testing?
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.
Test report coming up. I don't expect any issues. Just takes a while to install 1115 extensions ;-)
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.
I have seen surprises at test step ... so, I stay tuned. On our machines it took roughly 6 hours to build (including dependencies).
Fix checksum
Test report by @Flamefire |
After #20898 was merged this only partially applies now.
Not sure if it is worth following up on this although I would. Will be a very small PR I guess. |
after the other PR was merged, I got disappointed, and lost interest in this one. So, please feel free to either follow it up or close it. Thanks in advance. |
@Flamefire : Thanks for that. |
In this PR:
Remarks:
Brotli/1.1.0-GCCcore-13.2.0
(compared to v.1.0.9), thelibbrotli*-static.a
are no longer built. As a result of that, buildingBrunsli/0.1-GCCcore-13.2.0
fails. To fix this, a new patch is introduced (Brunsli-0.1-fix-Brotli-static-library-names.patch
)libgeotiff, Brunsli, GEOS, GDAL
, and so does PR {lib}[GCCcore/13.2.0] Brunsli v0.1, GDAL v3.9.0, libgeotiff v1.7.3, ... #20675. So, some care has to be practiced here to avoid duplication