New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libtorrent package required #3874
Comments
What do you mean flexget doesn't support the magnet directly? All of our torrent client plugins support them as far as I'm aware. libtorrent is not a pure python component, so it is harder to install. |
I would like Flexget to download from a Jackett gathered RSS, in which torrent direct url has been banned but magnet works. |
What downloader are you using? |
Download Station of Synology. Recently, I give up the test. So plz ignore this post. |
I solved this by allowing the flexget venv to access system libraries. I did by editing It can then access the I do have a vague recollection of fixing this on a previous flexget installation by running pip from within the venv, but couldn't get it to work this time. Also, enabling access to system packages my or may not do horrible things to flexget. But it works for me. |
This issue is stale because it has been open 150 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Jackett offers a lot of Rss(es) for Flexget, but some torrent links are not reachable (banned by China GFW). However, I found the magnet works. Unfortunately, Flexget doesn't accept magnet directly. So I want to convert the magnet(s) into torrent(s). Then I got the below feedback from Flexget
"pip install libtorrent" does not work:
ERROR: Could not find a version that satisfies the requirement libtorrent (from versions: none)
ERROR: No matching distribution found for libtorrent
Expected behaviour:
Plugin convert_magnet converts the magnet it meets
Actual behaviour:
Plugin convert_magnet says:libtorrent package required
Steps to reproduce:
Config:
Log:
(click to expand)
Additional information:
The text was updated successfully, but these errors were encountered: