all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <marius@gnu.org>
Cc: 41840-done@debbugs.gnu.org
Subject: bug#41840: Transmission 3.00
Date: Wed, 15 Jul 2020 15:43:48 -0400	[thread overview]
Message-ID: <20200715194348.GA32625@jasmine.lan> (raw)
In-Reply-To: <87a705d5pr.fsf@gnu.org>

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

On Sun, Jul 12, 2020 at 12:53:04AM +0200, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
> > It works fine when I set, for example:
> >
> > CURL_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt
> 
> This is <https://issues.guix.gnu.org/22138>, right?
> 
> I think setting native-search-paths on Transmission as a workaround is
> OK for now.

I found that it also honors SSL_CERT_DIR and SSL_CERT_FILE.

Since these variables are handled automatically on Guix System and we
suggest in the manual that foreign distro users set them, I pushed the
Transmission update without setting up any search paths.

Guix profile search paths do not effect the environment of systemd
services, so they would not help the majority of people using
Transmission on foreign distros anyway.

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

      reply	other threads:[~2020-07-15 19:45 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
2020-07-15 19:43         ` Leo Famulari [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200715194348.GA32625@jasmine.lan \
    --to=leo@famulari.name \
    --cc=41840-done@debbugs.gnu.org \
    --cc=marius@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.