curl works for me now as well.
Glad it's resolved!
-Robert
On Wed, Mar 6, 2024 at 11:13 AM Gábor Csárdi wrote:
> Yes, it started failing about then, so I am pretty sure it is related.
>
> Thanks, Gabor
>
> On Wed, 6 Mar 2024 at 16:39, Mike Smith wrote:
>
> > Maintainer of the
Sure these sections would probably be useful in your situation.
pushing to github and bioconductor
http://contributions.bioconductor.org/git-version-control.html#push-to-github-bioc
And
fixing bugs in release and devel
Dear Lori,
Thanks for your prompt and helpful email.
I think I've managed to make the necessary changes to stop the build
error.
I think it did it quite manually changing my Github, the Bioconductor
dev code and the Bioconductor RELEASE_3_18 for drawProteins.
The way I did it felt
Yes, it started failing about then, so I am pretty sure it is related.
Thanks, Gabor
On Wed, 6 Mar 2024 at 16:39, Mike Smith wrote:
> Maintainer of the code.bioconductor.org site here. Thanks for the
> report.
>
> The certificate is exactly the same as the one used by all other
>
Certificate updated with the full chain. Strike this one down to user
error on my part.
It looks like it's now working with curl from my perspective. Please let
me know if that's not the case, either by replying here or opening an issue
at https://github.com/Bioconductor/code.bioconductor.org
Maintainer of the code.bioconductor.org site here. Thanks for the report.
The certificate is exactly the same as the one used by all other
bioconductor.org sites, however we recently changed (February 21st) how it
is applied to the code.bioconductor.org subdomain. Did you happen to try
this
My strong suspicion is this is because curl does not support AIA via
openSSL on Linux. But browsers will use AIA (hence the reports of Firefox,
etc working).
Here's an old GitHub issue referencing the problem though it's not the most
recent writing on the topic.
Could you please show the commands you are trying along with a
git remote -v
I've check the configuration on our end and everything looks correct. You'll
need to make sure you are pointing to one of the uploaded ssh keys on the
BiocCredentials account (or create a new one if you are on a
Sorry to bother you I feel as if I am asking a very stupid question but I
can't solve it on my own.
I am getting build errors and I worked out why (a failed test) and changed
my code on Github to correct this:
https://github.com/brennanpincardiff/drawProteins
I have checked R CMD Check and it is
That does seem weird.
curl does indeed complain, but both Edge and Firefox running on my Pop!OS
22.04 have no problems with the certificate.
-Robert
On Wed, Mar 6, 2024 at 3:41 AM Gábor Csárdi wrote:
> I can't find any Linux distro that accepts that certificate. Even
> Debian testing fails
I can't find any Linux distro that accepts that certificate. Even
Debian testing fails with a pretty recent certificate bundle, see
below.
Anyway, I can download your cert and add it to my cert bundle, so this
is not a problem for me. It is just a FYI, that currently this site
fails for pretty
This is a curl problem, nothing wrong with the SSL certificate of
code.bioconductor.org
Try installing the ca-certificates package on your ubuntu.
Best regards,
Anestis Gkanogiannis, PhD
-
linkedin.com/in/anestis-gkanogiannis
github.com/gkanogiannis
www.gkanogiannis.com
Anyone know where to report issues with code.bioconductor.org?
This is what I see from a vanilla Ubuntu 22.04 (and also from Fedora
40/41, etc.):
root@6bff5eca88b0:~# curl https://code.bioconductor.org/
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here:
13 matches
Mail list logo
