unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 41840@debbugs.gnu.org
Subject: [bug#41840] Transmission 3.00
Date: Sun, 12 Jul 2020 00:53:04 +0200	[thread overview]
Message-ID: <87a705d5pr.fsf@gnu.org> (raw)
In-Reply-To: <20200709205027.GA31779@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 841 bytes --]

Leo Famulari <leo@famulari.name> writes:

> On Wed, Jun 17, 2020 at 01:31:31AM -0400, Leo Famulari wrote:
>> I haven't updated the package yet because it doesn't work reliably for
>> me — sometimes it can connect to trackers, and sometimes it can't. I
>> don't know why yet.
>
> For some reason, this new version of Transmission fails to find the
> X.509 certificate bundle in its default location while using curl.
>
> It works fine when I set, for example:
>
> CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt
>
> I wonder, what's the best way for us to handle this? Our curl package
> has a CURL_CA_BUNDLE search path. And some other packages have bits to
> make things work.

This is <https://issues.guix.gnu.org/22138>, right?

I think setting native-search-paths on Transmission as a workaround is
OK for now.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-07-11 22:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 21:13 [bug#41840] Transmission 3.00 Leo Famulari
2020-06-13 21:16 ` [bug#41840] [PATCH 1/2] gnu: Transmission: Update to 3.0.0 Leo Famulari
2020-06-13 21:16   ` [bug#41840] [PATCH 2/2] gnu: tremc: Update to 0.9.2 Leo Famulari
2020-06-14 18:18 ` [bug#41840] Transmission 3.00 Maxim Cournoyer
2020-06-17  5:31   ` Leo Famulari
2020-07-09 20:50     ` Leo Famulari
2020-07-11 22:53       ` Marius Bakke [this message]
2020-07-15 19:43         ` bug#41840: " Leo Famulari

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=87a705d5pr.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=41840@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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).