Re: [Bioc-devel] seqArchR error on build systems

2022-10-28 Thread Sarvesh Nikumbh
Ubuntu and macOS errors are now fixed, but the palomino4/Windows error
is still there (this error is different), says, it needs OpenSSL.
Thanks in advance.

===
Collecting package metadata (current_repodata.json): ...working...
Collecting package metadata (current_repodata.json): ...working...
failed

CondaSSLError: OpenSSL appears to be unavailable on this machine.
OpenSSL is required to
download and install packages.
Exception: HTTPSConnectionPool(host='conda.anaconda.org', port=443):
Max retries exceeded with url:
/conda-forge/win-64/current_repodata.json (Caused by SSLError("Can't
connect to HTTPS URL because the SSL module is not available."))

+ "C:/Users/biocbuild/AppData/Local/r-miniconda/condabin/conda.bat"
"create" "--yes" "--prefix"
"C:/Users/biocbuild/AppData/Local/r-miniconda/envs/r-reticulate"
"python=3.8" "numpy" "--quiet" "-c" "conda-forge"
failed

CondaSSLError: OpenSSL appears to be unavailable on this machine.
OpenSSL is required to
download and install packages.

Exception: HTTPSConnectionPool(host='conda.anaconda.org', port=443):
Max retries exceeded with url:
/conda-forge/win-64/current_repodata.json (Caused by SSLError("Can't
connect to HTTPS URL because the SSL module is not available."))
===


Thanks and best,
  Sarvesh


On Tue, 25 Oct 2022 at 22:05, Hervé Pagès  wrote:
>
> Hi Sarvesh,
>
> It looks like reticulate somehow was using the wrong Python instance on
> nebbiolo2 and lconway, as reported by py_config().
>
> We're now setting RETICULATE_PYTHON on those machines to make sure that
> reticulate will use the correct Python. This change was made after the
> builds started today so it won't be reflected on tomorrow's report. But
> it should be reflected on Thursday's report.
>
> We'll do the same on the other build machines soon.
>
> Best,
>
> H.
>
> On 25/10/2022 08:53, Sarvesh Nikumbh wrote:
> > Hi Bioc-team,
> >
> > seqArchR was building fine, without any errors last week, but I am seeing
> > an error again. This time it is due to the Python module 'sklearn' not
> > available and one another error. The sklearn-related error occurs on
> > nebbiolo2 and Iconway, while palomino4 shows a different error.
> >
> > Maybe something changed on the build systems? Because these system
> > requirements were available before*.*
> >
> > Thanks and best,
> >Sarvesh
> >
> --
> Hervé Pagès
>
> Bioconductor Core Team
> hpages.on.git...@gmail.com
>


-- 

thanks!
-Sarvesh


Q: Why is this email five sentences or less?
A: http://five.sentenc.es

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel


Re: [Bioc-devel] seqArchR error on build systems

2022-10-25 Thread Hervé Pagès

Hi Sarvesh,

It looks like reticulate somehow was using the wrong Python instance on 
nebbiolo2 and lconway, as reported by py_config().


We're now setting RETICULATE_PYTHON on those machines to make sure that 
reticulate will use the correct Python. This change was made after the 
builds started today so it won't be reflected on tomorrow's report. But 
it should be reflected on Thursday's report.


We'll do the same on the other build machines soon.

Best,

H.

On 25/10/2022 08:53, Sarvesh Nikumbh wrote:

Hi Bioc-team,

seqArchR was building fine, without any errors last week, but I am seeing
an error again. This time it is due to the Python module 'sklearn' not
available and one another error. The sklearn-related error occurs on
nebbiolo2 and Iconway, while palomino4 shows a different error.

Maybe something changed on the build systems? Because these system
requirements were available before*.*

Thanks and best,
   Sarvesh


--
Hervé Pagès

Bioconductor Core Team
hpages.on.git...@gmail.com

___
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel