-
Notifications
You must be signed in to change notification settings - Fork 14
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
problem installing biomaRt on Fedora #42
Comments
Thanks for the report. Can you confirm if you see the same behaviour from the release version here on GitHub: BiocManager::install('grimbough/biomaRt', ref = 'RELEASE_3_12') I suspect it's getting stuck inside a loop executed when the package is loaded, but I can't see why the loop wouldn't terminate. I just want to check the versions in BioC and GitHub behave the same. |
Thanks for coming back to this so quickly.
|
Merge branch 'RELEASE_3_12' into 3_12_testing # Conflicts: # R/zzz.R
I've created a new branch that will BiocManager::install('grimbough/biomaRt', ref = '3_12_testing') |
I did, but unfortunately to no avail... However, after termination I saw tens of notifications that apparently were printed, and I did not observe this earlier. Hopefully these may provide some clues?
|
Ok, I think I understand what's happening now. The code detects that error and tries to modify the HTTP settings to fix it, then tests again. However if the fix doesn't work it will still produce the same error and we'll go round in the loop. It hadn't occurred to me that the fix might not work! I've tested on various flavours of Ubuntu, but maybe something different is required for Fedora. I can probably put a hard stop in the code so that it will at least load the package, but without addressing the root problem I'm not sure you (or maybe all Fedora users) will actually be able to use biomaRt. I'll have a look at what might be required. Thanks a lot for try these diagnostics and reporting back. |
FWIW: Googling with the error message pointed me to this post of you, which in turn mentioned this Github Issue Ensembl/ensembl-rest#427 (comment). In that thread, I saw Herve's post here Ensembl/ensembl-rest#427 (comment), and indeed Fedora reports the same:
Fedora 33 currently uses OpenSSL version 1.1.1i.
... but the fix you described in that thread Ensembl/ensembl-rest#427 (comment) does indeed not work... ??? As was confirmed by the posts above...
|
Cool, thanks for confirming that the fix doesn't work. I guess that |
I am not at all an expert on this, but I found this and this information. In release 33 Fedora apparently also increased its security level (from 1 to 2 ??). Now check this (run on command line and not in R): Default setting thus gives an error!
But after reducing level to "FEDORA32" not anymore!
Idem for "LEGACY"
Thus, this line in R:
doesn't work with Fedora (is Ubuntu/Debian specific?!), but how then to adapt it in order to set the equivalent of LEGACY or FEDORA32. Or maybe I am too naive on this... :) |
Thanks for the links. This looks tricky to fix. I've haven't managed to find something we can pass to I presume if you run Ideally Ensembl would get rid of the outdated certificate that seems to be causing this issue, but that GitHub issue is over a year old and doesn't seem to have got any traction. As a work around for now, I've added a rule that it should only tests for connection problems once, and if the fix doesn't work then stop trying. If you could again trying installing the test branch, I'm hoping that you'll only see the error message once: BiocManager::install('grimbough/biomaRt', ref = '3_12_testing') That doesn't solve the really problem, but at least it should stop the infinite waiting for package installation. Assuming it works I'll push that workaround to Bioconductor. |
It indeed seems a complicated thing to fix, so thanks for spending so much time on this. I can confirm that there is no infinite waiting anymore when installing your latest test release:
Connecting the ENSEMBL site indeed does not work:
It does, however, after 'a system-wide downgrading' of the security level (as expected):
Note that
|
Great. I'll suppress most of the message printing and make that change in the version on Bioconductor so at least other users don't get bitten with a frozen upgrade of the of package. I'll also add something in the vignette about downgrading the crypto level. At least that gets the package working, even if it's not a solution I particularly like. Thanks for being willing to test all the prototypes and giving such informative reports back. If I come across a working solution I'll update here again. |
Version 2.46.3 is now in the Bioconductor repository and should be available in a few days. Hopefully it will install for you, but please let me know if it continues to be a problem. |
Hi Mike, just to let you know that after the update of the certificates at ENSEMBL,
Now in R/Bioconductor:
|
Hi,
BiocManager
indicated an update ofbiomaRt
is available for my system (Fedora 33). Unfortunately I cannot get it installed; the installation procedure stalls at "testing if installed package can be loaded from temporary location". After 1hr I decided to abort the R-session with ctrl-c (indicated by^C
in code below) to be able to continue. Then this error is reported:Any idea on what goes wrong?
Thanks!
Guido
NB: after this, biomaRt version 2.46.0 (which was already installed) still loads fine.
Full output:
The text was updated successfully, but these errors were encountered: