 |
VOOZH | about |
| Git Clone URL: | https://aur.archlinux.org/sonarr-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | sonarr-bin |
| Description: | Smart PVR for newsgroup and torrent users |
| Upstream URL: | https://sonarr.tv |
| Licenses: | GPL-3.0-or-later |
| Groups: | servarr-bin |
| Conflicts: | sonarr |
| Provides: | sonarr |
| Submitter: | txtsd |
| Maintainer: | txtsd (fryfrog) |
| Last Packager: | txtsd |
| Votes: | 106 |
| Popularity: | 0.063196 |
| First Submitted: | 2024-10-13 20:06 (UTC) |
| Last Updated: | 2026-06-26 18:24 (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
Alternate versions
sonarr (source version of this package)
sonarr-develop (develop branch)
sonarr-develop-bin (binary version of the develop branch)
I think it's missing some dependencies for a fresh install (base-devel & binutils maybe ?)
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
@Sveske-Juice I've pushed a fix. Could you try re-installing now, and let me know how it goes?
EDIT: Actually, since you've already created that dir, don't worry about it.
@kidfrostbite Thank you!
@txtsd Gotcha, good to know. Appreciate the work you're doing maintaining so many packages.
@kidfrostbite Arch built packages are generally hardened the same amount because of consistent build settings. Binaries built elsewhere generally aren't hardened as much as Arch's are.
@txtsd I see, I didn't realize that was the case. ffmpeg's immediate dependencies are 110 packages, I wonder if all of those are all hardened, or if those dependencies' dependencies are. Anyway, I'm not complaining, thanks for the clarification.
Was that the first time you installed sonarr?
@Sveske-Juice It's strange that's happening on your system. I test my packages in clean chroots, and they build perfectly, so I suspect something is up with your system. Like /var/log should exist because many packages use it.
λ pacman -Qo /var/log
/var/log/ is owned by apache 2.4.62-1
/var/log/ is owned by cups 2:2.4.11-1
/var/log/ is owned by filesystem 2024.04.07-1
/var/log/ is owned by gssproxy 0.9.2-1
/var/log/ is owned by libvirt 1:10.8.0-1
/var/log/ is owned by lxd 6.1-2
/var/log/ is owned by nginx-mainline 1.27.2-1
/var/log/ is owned by samba 2:4.21.1-1
/var/log/ is owned by systemd 256.7-1
Looks like there is a bug. I'm not quite sure if this is a upstream bug. But after running:
yay -S sonarr-bin &&
systemctl start sonarr
The following outputs from journalctl:
(Sonarr)[147659]: sonarr.service: Failed to set up special execution directory in /var/log: No such file or directory
(Sonarr)[147659]: sonarr.service: Failed at step LOGS_DIRECTORY spawning /usr/lib/sonarr/bin/Sonarr: No such file or directory
A workaround is to create an empty directory at /var/lib/sonarr/logs:
mkdir /var/lib/sonarr/logs
edit: this is also the case with radarr-bin