From: "Raghav Gururajan" <rvgn@disroot.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34861@debbugs.gnu.org
Subject: bug#34861: TLS Error with Flatpak
Date: Mon, 18 Mar 2019 17:31:54 +0000 [thread overview]
Message-ID: <e15ac30a9925c47e77f0dcff5b63eeb0@disroot.org> (raw)
In-Reply-To: <87imwgpl5e.fsf@gnu.org>
Hello Ludovic!
Yes, I did them. Still did not work.
I did the following to set env variables:
$ guix package -i nss-certs
$ export SSL_CERT_DIR="$HOME/.guix-profile/etc/ssl/certs"
$ export SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt"
$ export GIT_SSL_CAINFO="$SSL_CERT_FILE"
Regards,
RG.
March 18, 2019 9:49 AM, "Ludovic Courtès" <ludo@gnu.org> wrote:
> Hello,
>
> "Raghav Gururajan" <rvgn@disroot.org> skribis:
>
>> Whenever I try "flatpak remote-add --if-not-exists flathub
>> https://flathub.org/repo/flathub.flatpakrepo"; I keep getting the error "Can't load uri
>> https://flathub.org/repo/flathub.flatpakrepo: TLS support is not available".
>>
>> I even tried following steps mentioned at
>> https://www.gnu.org/software/guix/manual/en/guix.html#index-TLS. Still not working.
>
> To be more specific, did you install ‘nss-certs’?
>
> If you did is it installed system-wide in /etc/ssl/certs, or per-user?
>
> Did you set ‘SSL_CERT_DIR’, ‘SSL_CERT_FILE’, or related environment
> variables?
>
> Thanks,
> Ludo’.
next prev parent reply other threads:[~2019-03-18 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 20:36 bug#34861: TLS Error with Flatpak Raghav Gururajan
2019-03-18 9:49 ` Ludovic Courtès
2019-03-18 17:31 ` Raghav Gururajan [this message]
2019-03-18 21:24 ` Ricardo Wurmus
2019-03-18 23:10 ` Raghav Gururajan
2019-03-19 0:21 ` Ricardo Wurmus
2019-03-19 0:43 ` Raghav Gururajan
2019-03-22 21:00 ` Ludovic Courtès
2019-03-23 4:02 ` Raghav Gururajan
2019-03-23 8:05 ` Ricardo Wurmus
2019-03-24 6:48 ` Raghav Gururajan
2019-03-24 22:13 ` Ludovic Courtès
2019-03-24 22:13 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e15ac30a9925c47e77f0dcff5b63eeb0@disroot.org \
--to=rvgn@disroot.org \
--cc=34861@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).