-
Notifications
You must be signed in to change notification settings - Fork 0
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
Install problem #5
Comments
The link to the sqlite file is no longer valid. Please install the latest version of JASPAR2022 either from the Bioconductor development branch or directly from this repo. |
I thought the Biocmagner one was the lastest version. |
You could try like this: In case this doesn't work, then installing from GitHub will certainly work: |
Thanks they work ! |
other attached packages:
[1] TFBSTools_1.40.0 BiocManager_1.30.22 JASPAR2020_0.99.10 igraph_2.0.1.1
[5] GenomicRanges_1.54.1 GenomeInfoDb_1.38.6 IRanges_2.36.0 S4Vectors_0.40.2
[9] BiocGenerics_0.48.1
I faced the error below when i installed JASPAR2022 using BiocManager::install("JASPAR2022").
Do you happen to know what had happened?
Error:
** testing if installed package can be loaded from temporary location
adding rname 'https://jaspar.genereg.net/download/database/JASPAR2022.sqlite'
Warning: download failed
web resource path: ‘https://jaspar.genereg.net/download/database/JASPAR2022.sqlite’
local file path: ‘/home/ybae/.cache/R/BiocFileCache/1fdbc528e4fdc3_JASPAR2022.sqlite’
reason: Not Found (HTTP 404).
Warning: bfcadd() failed; resource removed
rid: BFC7
fpath: ‘https://jaspar.genereg.net/download/database/JASPAR2022.sqlite’
reason: download failed
Warning in value[3L] :
trying to add rname 'https://jaspar.genereg.net/download/database/JASPAR2022.sqlite' produced error:
bfcadd() failed; see warnings()
Error: package or namespace load failed for ‘JASPAR2022’:
.onLoad failed in loadNamespace() for 'JASPAR2022', details:
call: bfcrpath(BiocFileCache(), url)
error: not all 'rnames' found or unique.
Error: loading failed
Execution halted
The text was updated successfully, but these errors were encountered: