Package Details: flaresolverr 3.3.19-1

Git Clone URL: https://aur.archlinux.org/flaresolverr.git (read-only, click to copy)
Package Base: flaresolverr
Description: A proxy server to bypass Cloudflare protection
Upstream URL: https://github.com/FlareSolverr/FlareSolverr
Keywords: captcha cloudflare jackett proxy
Licenses: MIT
Submitter: txtsd
Maintainer: txtsd
Last Packager: txtsd
Votes: 6
Popularity: 0.000343
First Submitted: 2023-01-05 11:20 (UTC)
Last Updated: 2024-05-26 18:54 (UTC)

Pinned Comments

txtsd commented on 2023-11-13 09:56 (UTC)

This package use to incorrectly build from source in the past. It now correctly builds from an archive of the source without needing dependencies like git.

Please report any user-agent related errors that stem from running recent versions of Chrome and Chromium upstream.

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

txtsd commented on 2023-01-05 11:24 (UTC) (edited on 2023-01-05 11:25 (UTC) by txtsd)

This package will not be updated until upstream provides binaries. For version 3.0 onward, try flaresolverr or flaresolverr-git instead.

cwegener commented on 2023-01-05 09:27 (UTC) (edited on 2023-01-06 02:04 (UTC) by cwegener)

UPDATE (2023/01/06): The preferred way to install is via AUR, using the new flaresolverr package. The below manual install instructions are left as a reference, until the migration of the upstream to a compliant Python Packaging format is complete.

Anybody who would want to try out the new version without an AUR package could do a manual install via pipx:

  1. Install chromium sudo pacman -S chromium
  2. Install pipx: sudo pacman -S python-pipx
  3. Install flaresolverr from the WIP PR: pipx install --suffix '@git' git+https://github.com/FlareSolverr/FlareSolverr/@refs/pull/651/head
  4. Launch flaresolverr: flaresolverr@git

cwegener commented on 2023-01-05 09:22 (UTC)

I'll work on updating this to flaresolverr 3.0 today. You're correct about needing a package rename now, since there aren't any prebuilt binaries.

I think the lack of PEP-517 support and lack of a published sdist tarball on PyPI are going to be blockers for a proper Python package for now.

Gaspard and myself are currently working through the PEP-517 part in the referenced Github PR.

txtsd commented on 2023-01-05 05:43 (UTC)

I'll work on updating this to flaresolverr 3.0 today. You're correct about needing a package rename now, since there aren't any prebuilt binaries.

HLFH commented on 2023-01-05 02:27 (UTC) (edited on 2023-01-05 02:28 (UTC) by HLFH)

  1. This package flaresolverr-bin is technically not outdated as it tracks the precompiled binaries that are no longer provided in v3.0.0.

  2. The upstream does not comply with the Python package guidelines.

  3. flaresolverr-bin will have to be deleted / renamed to flaresolverr on the AUR.

  4. This PR will have to be merged. https://github.com/FlareSolverr/FlareSolverr/pull/651. And a version 3.0.1 released.

  5. Flaresolverr would need to be published on Pypi. https://pypi.org/

  6. Here is an example for Hatch, I'll have a look at your pyproject.toml file https://github.com/HLFH/automua/blob/master/pyproject.toml

  7. I was not able to make the new release work (yet!) with Prowlarr, I will try with the updated Jackett.

cwegener commented on 2023-01-05 02:18 (UTC)

Yes packaging a good release is difficult.

So, if I understand Diego's message correctly, jackett has a matching change to upgrade its FlareSolverr .NET library to a compatible release as well and both, flaresolverr and jackett would need to upgraded at the same time ...

cwegener commented on 2023-01-05 02:16 (UTC)

Setup.py is crap and obsolete. For pyproject.toml, see

I pushed the PR FWIW .. https://github.com/FlareSolverr/FlareSolverr/pull/651

HLFH commented on 2023-01-05 01:57 (UTC) (edited on 2023-01-05 01:58 (UTC) by HLFH)

Yes packaging a good release is difficult.

No setup.py or pyproject.toml

Setup.py is crap and obsolete. For pyproject.toml, see https://github.com/FlareSolverr/FlareSolverr/issues/650#issuecomment-1371647485.

Chromedriver management is performed by the FlareSolverr code itself for some reason.

Yes, it does not seem to be optimized. See as well https://github.com/FlareSolverr/FlareSolverr/issues/650#issuecomment-1371647485.

Thanks for your comments.

cwegener commented on 2023-01-05 01:48 (UTC)

I'm just looking through the new Python version of FlareSolverr 3.0.0

I must say that the code looks a bit difficult from a packaging perspective:

  1. No setup.py or pyproject.toml
  2. Chromedriver management is performed by the FlareSolverr code itself for some reason

HLFH commented on 2023-01-05 01:45 (UTC) (edited on 2023-01-05 01:45 (UTC) by HLFH)

In the meantime, v3.0.0 is available in git version with flaresolverr-git on the AUR. As co-maintainer, let me look at the update of the flaresolverr-bin package.

« First ‹ Previous 1 2 3 4 5 Next › Last »