Package Details: sonarr 2.0.0.5338-1

Git Clone URL: https://aur.archlinux.org/sonarr.git (read-only, click to copy)
Package Base: sonarr
Description: PVR for newsgroup users
Upstream URL: https://sonarr.tv
Licenses: GPL3
Submitter: justin8
Maintainer: degeberg
Last Packager: degeberg
Votes: 80
Popularity: 0.091276
First Submitted: 2014-11-10 04:45
Last Updated: 2019-08-17 05:50

Dependencies (9)

Required by (6)

Sources (4)

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 Next › Last »

justin8 commented on 2015-04-13 00:40

@shkercuh Your one builds in to /opt so it isn't really an issue. /opt is really the catch-all for things that don't comply with the usual standards. check man file-hierachy for more details. It does state that /usr is not required to be read-only. But working in a corporate Linux environment I would have some words with anyone who tried to make an app write to /usr. (FYI, I'm the maintainer for the sonarr-develop package on the AUR)

@SAKUJ0 the -data/-datadir thing is needed to write the files to the correct place of /var unless we ran the whole application out of /opt. Since it does appear to support working in this manner, are you able to link to those forum posts you said about the developers recommending against using it?

shkercuh commented on 2015-04-13 00:31

@justin8
@SAKUJ0

Is the approach I have taken in https://aur.archlinux.org/packages/sonarr-git correct?

justin8 commented on 2015-04-13 00:29

I feel I should point out that regardless of the developers wishes, no programs at all should be able to write to /usr. It is static data that should be maintained in your package manager and not transient data. That belongs in /var. Having an auto update system within the app instead of using the OS package manager is a windows/OSX thing that is somewhat against the Linux way of managing things. The correct way to update an app is to update it via the package manager. If auto updating is something they want, it should be living in /opt where other non-conformant apps live.

SAKUJ0 commented on 2015-04-12 17:24

Hey, thanks for maintaining the package. A few obvious and not so obvious points the developers of Sonarr pointed out to me when I mentioned the AUR package:

1) It would be really great if /usr/lib/sonarr had write access to the sonarr user. That is a requirement for the desired update functionality to work within Sonarr and update procedures seem to be fine with the way the installation is set up.

2) Currently using -data / -datadir (I don't recall exactly) is not recommended by the Sonarr devs in production environments. The devs pointed me towards the forums as ongoing discussions appear to be there for best ways how to avoid using the launch option.

3) The distro repo for mono can cause SIGSEGV issues. Currently it is recommended to use mono 3.10.0 instead of 3.12.1 or at least the current git version of 3.12.1. That being said, I myself am using the distro version (3.12.1) of mono just fine so I prefer the currently used mono version myself. I just thought I would mention this.

Of course I can supply you with patches but in the spirit of the AUR, which emphasizes collaboration and the learning curve, I thought it would be best to approach you for the reasons of doing things the way they are. Maybe we can handle things more the way the devs of Sonarr would recommend, without going against Arch and AUR conventions. At least making sure the update functionality works (the devs are very conservative with patches) would certainly be a desirable goal.

johannvonperfect commented on 2015-03-17 15:21

Upstream updated to 2.0.0.3004.

johannvonperfect commented on 2015-02-12 15:42

Upstream has gone through a couple of updates and is currently at 2.0.0.2850.

ayounggun commented on 2015-02-11 18:37

Hi degeberg

Thanks for putting together this package.

I'm using it on a raspberry pi 2 currently, and it works really well.

In case you're not aware, I thought I should say that a few users (1) have been having problems with sonarr's auto-update feature. They believe it is due to the archlinux/systemd, as similar problems are not seen with debian.

Also in the logs I see sonarr complaining about not having the correct write permissions.

I'm just looking into these two possibly related things at the moment and wondered whether you had seen this or not.

Cheers

(1) https://forums.sonarr.tv/t/auto-update-fails-on-arch-linux/3798/23

degeberg commented on 2015-01-19 11:12

The new version should work with mono 3.12.

pezz commented on 2015-01-18 15:59

This doesn't work with mono-3.12.0-1 that is now in the normal repos, downgrading to mono-3.10.0-1 and all is well again.

degeberg commented on 2015-01-02 12:49

Not yet. You would have to use the develop branch of sonarr.