unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: marinus.savoritias@disroot.org, 43184@debbugs.gnu.org
Subject: bug#43184: Qbittorent Search Doesnt work.
Date: Thu, 29 Sep 2022 23:10:57 -0400	[thread overview]
Message-ID: <87a66hmu9q.fsf@gmail.com> (raw)
In-Reply-To: <61eac918-d873-97d7-fa92-15c22cf2127c@telenet.be> (Maxime Devos's message of "Thu, 29 Sep 2022 14:30:01 +0200")

Hello,

Maxime Devos <maximedevos@telenet.be> writes:

> reopen 43184
> merge 43184 53334
> thanks
>
> On 29-09-2022 02:23, Maxim Cournoyer wrote:
>> Hello,
>> Marinus Savoritias <marinus.savoritias@disroot.org> writes:
>> 
>>> When I try to open the search engine in Qbittorent it comes up with
>>> this error:
>>> "Python is required to use the search engine but it does not seem to
>>> be installed."
>>>
>>> Maybe it needs Python as one of the inputs or it is not being
>>> mentioned explicity?
>>>
>>> MSavoritias
>> Testing it with 'guix shell qbittorrent -- qbittorrent', the search
>> seems to work; even though I have no torrent file loaded.
>> Closing, please reopen if something is amiss!
>
> You probably have a 'python' sitting in the environment.  I can
> reproduce with 'guix shell --pure qbittorrent -- qbittorrent' (note:
> you have to use 'View > Search engine', not 'Filter torrent names').
>
> There is a patch available at <https://issues.guix.gnu.org/53334#2>
> for baking in a reference to Python.

Ah yes, silly me, I should have used --pure.  Thanks for reopening!

-- 
Maxim




      reply	other threads:[~2022-09-30  3:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 17:19 bug#43184: Qbittorent Search Doesnt work Marinus Savoritias
2022-09-29  0:23 ` Maxim Cournoyer
2022-09-29 12:30   ` Maxime Devos
2022-09-30  3:10     ` Maxim Cournoyer [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

  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=87a66hmu9q.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=43184@debbugs.gnu.org \
    --cc=marinus.savoritias@disroot.org \
    --cc=maximedevos@telenet.be \
    /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).