Package Details: pymedusa 0.4.5-1

Git Clone URL: (read-only, click to copy)
Package Base: pymedusa
Description: Automatic Video Library Manager for TV Shows. It watches for new episodes of your favorite shows, and when they are posted it does its magic.
Upstream URL:
Licenses: GPL
Submitter: blinx
Maintainer: blinx
Last Packager: blinx
Votes: 7
Popularity: 0.000009
First Submitted: 2018-02-26 16:15
Last Updated: 2020-11-16 21:08

Latest Comments

1 2 Next › Last »

yochananmarqos commented on 2019-06-26 13:51

This also requires openssl & libmediainfo per the installation guide.

hexdsl commented on 2019-04-05 15:48


This site can’t be reached is unreachable. ERR_ADDRESS_UNREACHABLE

I get that error every time i try the download. I have tried with VPN, without VP. same error. its really odd.

blinx commented on 2019-04-05 09:22

@hexdsl that's weird, I have no issues to reach the link, git repo and releases. I tried from different locations and I was able to reach.

hexdsl commented on 2019-04-05 09:12

the address is not reachable. I have checked the git repo and if i navigate to the release its not working there either.

Superpiffer commented on 2019-03-18 14:23

Great! I've just updated and it works as expected. The only thing is that maybe there's no need to use the commands in post_install:

  • "systemd-sysusers pymedusa.conf" and "systemd-tmpfiles --create pymedusa.conf" are automatically called during the installation.

  • I think it's cleaner if you set the working folder in tmpfiles file: d /var/lib/pymedusa 0755 pymedusa pymedusa

Right now I'm using pymedusa with a user service located in my home (.config/systemd) but if you want you can put it in /usr/lib/systemd/user with a starting command like this:

ExecStart=/usr/bin/python /usr/lib/pymedusa/ -q --nolaunch --datadir=%h/.config/pymedusa

Thanks for the update! :)

blinx commented on 2019-03-18 13:45

@Superpiffer Thank you, that's a great suggestion. They're applied on the update.

Superpiffer commented on 2019-03-15 10:32

@blinx: I marked the package as out-of-date, version 0.3.0 was released with python3 migration. I want to report that after the upgrade, changing python2.7 to python3 and upgrading the dependencies to python3, I had some "bad magic number" errors. I solved them simply with "find /opt/medusa/ -name \*.pyc -delete".

Also I have some suggestions:

  • Why the working folder is in /opt? IMHO is better to install in /usr/lib and move the working folder in /var/lib/pymedusa for medusa user.

  • Maybe a systemd user service can be useful, in order to run pymedusa as a different user, with working folder in the home of the user.

  • You can migrate the .install file to sysusers.d and tmpfiled.d entries.

Thanks :)

blinx commented on 2019-03-03 10:58

@bobpaul if a new dependency is added the auto-update won't install it.

bobpaul commented on 2019-03-03 04:47

Question: Should we update via this package, via the auto-update within the application, both, or neither? Currently I have this package in my IgnorePkg list and I update via the autoupdate within the app.

blinx commented on 2018-12-27 16:43

@Twiki take a look on the upstream url, there is a setup guide over there..