Package Details: sonarr-develop-bin 4.0.11.2793-1

Git Clone URL: https://aur.archlinux.org/sonarr-develop-bin.git (read-only, click to copy)
Package Base: sonarr-develop-bin
Description: Smart PVR for newsgroup and torrent users (develop branch)
Upstream URL: https://sonarr.tv
Licenses: GPL-3.0-or-later
Groups: servarr-develop-bin
Conflicts: sonarr
Provides: sonarr
Submitter: txtsd
Maintainer: txtsd (fryfrog)
Last Packager: txtsd
Votes: 10
Popularity: 0.24
First Submitted: 2024-10-16 04:59 (UTC)
Last Updated: 2024-12-23 09:36 (UTC)

Dependencies (20)

Required by (17)

Sources (8)

Pinned Comments

mkomko commented on 2024-11-15 07:00 (UTC)

PSA: If you receive exceptions like "System.IO.IOException: Read-only file system" when Sonarr is importing files after updating to 4.0.10.2544, and you use your home directory for downloaded files (which is advised against), you can either move file management out of your home directory or do something like the following:

$ sudo systemctl edit sonarr

[Service]
# Allow home directory path to be writable again
ReadWritePaths=/home/user/media

txtsd commented on 2024-10-21 03:59 (UTC) (edited on 2024-10-30 12:52 (UTC) by txtsd)

Alternate versions

sonarr (source version)
sonarr-bin (binary version)
sonarr-develop (source version of this package)

Latest Comments

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

SAKUJ0 commented on 2015-05-22 11:01 (UTC)

I suppose the version in the AUR title, 2.0.0.2597-1, is out of date and will be most of the time. Right now this package links to 2.0.0.3159. Is there a way people like me can update the title to reflect that?

SAKUJ0 commented on 2015-04-13 12:24 (UTC)

@manoeldacosta and to anyone following his bullet lists. It is not recommended to give unprivileged users write permissions on anything inside /usr (except for maybe the src directory as many people use this as a scratchpad for all their system sources) The recommended way would be to set up Sonarr inside /opt/sonarr if you really want the auto-update functionality in a production environment. Using a package manager is usually a good idea, though. If something goes wrong when fiddling around with write permissions, theoretically quotas could be exceeded (not going to happen here) and you have no control over what code automatically gets introduced without a second layer of audit (and frankly the audit on Arch's site is next to non-existent).

justin8 commented on 2015-02-25 01:10 (UTC)

If you have an AUR manager like yaourt/aura/etc you can just tell it to rebuild your *-git packages and it would update to the latest one and record proper versioning information in your pacman database.

manoeldacosta commented on 2015-02-24 17:11 (UTC)

In answer to my own question: instructions on how to get Sonarr updated to the latest development version without having to reinstall this package: [Ref. http://dominicm.com/install-nzbdrone-sonarr-on-arch-linux/] 1. Stop Sonarr's service: $ sudo systemctl stop sonarr.service 2. Make user 'sonarr' the owner of its Startup and AppData directories: $ sudo chown -R sonarr:sonarr /usr/lib/sonarr $ sudo chown -R sonarr:sonarr /var/lib/sonarr 3. Edit /var/lib/sonarr/config.xml and change "<Branch>master</Branch>" to "<Branch>develop</Branch>" (I couldn't do this using the app's web interface: it wouldn't keep the new setting). 4. Edit file /etc/systemd/system/multi-user.target.wants/sonarr.service according to the replacement systemd script available in the above-referenced post [Alternative source: http://pastebin.com/3TqLacNr/]. 5. Start Sonarr: $ sudo systemctl start sonarr.service 6. Enter the web interface, go to 'System' and then 'Updates'. Click the 'Install' button alongside the latest development version listed. 7. Wait for the update to complete, and then restart using the built-in restart button. (If you restart through systemctl instead, the version number shown under 'System', 'Status' will remain unchanged.)

manoeldacosta commented on 2015-02-24 14:53 (UTC)

Thank you for maintaining this package, justin8. Do you know a way to automatically keep it in sync with the daily development updates? Maybe a custom update script or something similar?

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