Package Details: flexget 3.11.29-1

Git Clone URL: https://aur.archlinux.org/flexget.git (read-only, click to copy)
Package Base: flexget
Description: Multipurpose automation tool for downloading media content from different sources
Upstream URL: https://github.com/flexget/flexget
Licenses: MIT
Submitter: jonkristian
Maintainer: carsme
Last Packager: carsme
Votes: 76
Popularity: 0.64
First Submitted: 2009-09-11 19:38 (UTC)
Last Updated: 2024-04-22 19:09 (UTC)

Latest Comments

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 24 Next › Last »

rbellamy commented on 2015-05-31 18:22 (UTC)

Nicely done, @sebleblanc. For those who are still hoping for an "Arch" way of managing this package, take a look at the flexget-git package - I've updated it to point to a branch I'm currently synching that allows the Arch packaged SQL Alchemy.

cockatricehunter commented on 2015-05-31 17:07 (UTC)

@sebleblanc Great guide, any idea how I'd get the deluge plugin working through the virtual environment or would I just have to change it to download to a folder instead. Thanks

sebleblanc commented on 2015-05-08 19:16 (UTC)

I wrote a quick guide on how to install the FlexGet package in a virtualenv, this will get around the package's dependencies on the Python system packages. Unfortunately, this means not using this PKGBUILD, but it might do the trick for some people. This guide works for probably all Python packages that you can find on PyPI; just change "flexget" for "<package name>". https://gist.github.com/sebleblanc/f5e4a635d0fc8b953df7 As the FlexGet site recommends, you *could* install it directly on the system using pip, but this has the risk of clashing with system packages. Using a virtualenv is the recommended route, in my opinion.

rbellamy commented on 2015-05-08 18:12 (UTC)

@highway - yeah, that's absolutely an option. One that many people do use. That does take flexget out of the Arch Package management system - so you're using a Framework-based Package Manager (pip) over the OS-based package manager. Like @tomk says - until upstream validates that python2-sqlalchemy-1.0.x will work, an option is to ignore the python2-sqlalchemy upgrade. Another option is to modify the PKGBUILD and REMOVE the python2-sqlalchemy dependency - this will cause the flexget build process to pull in the version of sqlalchemy it requires via pip. I don't recommend this, as now you're going to have two versions of sqlalchemy - one managed by pacman and one managed by pip. This really is an example of the dichotomy and challenge of Package Management. We see this with ruby, python, haskell, node.js or any other framework with a (relatively) mature package management system where packages can be found in either the OS or the Framework repositories.

highway commented on 2015-05-08 03:03 (UTC)

just install the latest via pip as per the instructions on flexget's website. worked easily for me.

willemw commented on 2015-05-04 10:49 (UTC)

Correction on my comment below: downgrade python2-sqlalchemy (to 0.9.9-2), not flexget.

tomk commented on 2015-05-04 10:12 (UTC)

I've posted a request upstream asking them to update flexget for python-sqlalchemy 1.0.x. Until they do that, I'll be ignoring the python2-sqlalchemy upgrade, as suggested below

willemw commented on 2015-05-04 07:24 (UTC)

@highway: downgrade flexget and ignore python2-sqlalchemy during upgrades (https://wiki.archlinux.org/index.php/Downgrading_packages). I use program 'downgrade' to downgrade and add command line option '--ignore python2-sqlalchemy' during upgrades.

rbellamy commented on 2015-04-29 00:53 (UTC)

Of course, over the weekend, my media server died, so wasn't able to get to this like I expected - instead I spent my time getting the machine back up and running so I can test. I appreciate every being patient - I'll have this sussed out shortly.