Manual upgrade of Sonarr 3

[Dirk]

3.0.10.1567 was released to solve an sqlight issue but no package is available (I believe Radarr is also in the same boat)

Can someone point me at info on how/where to get the new version installed? PKG upgrade results in many files to be installed except Sonarr and that's how I got in trouble the first time.

Thanks in advance

 

[Patrick M. Hausen]

Your version is the current one for FreeBSD:

FreshPorts -- net-p2p/sonarr: PVR for Usenet and BitTorrent users

Sonarr is a PVR for Usenet and BitTorrent users.

www.freshports.org

You need to switch from the "quarterly" to the "latest" package repository:

Code:

mkdir -p /usr/local/etc/pkg/repos
echo 'FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest" }' >/usr/local/etc/pkg/repos/FreeBSD.conf

 

[Dirk]

Your version is the current one for FreeBSD:

FreshPorts -- net-p2p/sonarr: PVR for Usenet and BitTorrent users

Sonarr is a PVR for Usenet and BitTorrent users.

www.freshports.org

You need to switch from the "quarterly" to the "latest" package repository:

Code:

mkdir -p /usr/local/etc/pkg/repos
echo 'FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest" }' >/usr/local/etc/pkg/repos/FreeBSD.conf

Thanks Patrick. That version is the one I'm trying to get to.
I implemented your suggestion but it had no effect. I then looked into the original FreeBSD.conf and found it was set.to...

Code:

FreeBSD: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest",
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

A pkg upgrade does not list sonarr, but a "pkg search sonarr" does show that version.

Not sure where to go unless doing

 

[Dirk]

Code:

root@sonarr:~ # pkg install sonarr-3.0.10.1567
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
pkg: No packages available to install matching 'sonarr-3.0.10.1567' have been found in the repositories
root@sonarr:~ # pkg search sonarr
sonarr-3.0.10.1567             PVR for Usenet and BitTorrent users

 

[Patrick M. Hausen]

What is your jails's freebsd-version?

 

[Dirk]

Three jails on that machine. For some reason (possibly initial install?) Emby and SAB are 13.1 P7 and Sonarr is 13.0 P13. But that may have been deliberate with the MONO chaos back when.

 

[Patrick M. Hausen]

13.0 is EOL and does not receive package updates, anymore. Upgrade the jail to a supported version. I'd recommend 13.2, because 13.1 will probably be EOL by end of July.

 

[Dirk]

I keeping with common sense, I've tried to upgrade Truenas itself FIRST but my only choice is the 13.0 train. Do I also need to switch the main OS to latest?
Thanks

 

[Patrick M. Hausen]

No, no, no. The only way to update the TN itself is through the iXsystems provided releases. The 13.0 number on TN does not mean FreeBSD 13.0. Just upgrade your jails. All the way up to 13.2 should work fine for all, 14.0 of course won't.

 

[Dirk]

Understood.
The jail was upgraded to 13.2 successfully However, it still does not find sonar either bt pkg upgrade, or pkg upgrade sonarr.

The output from pocking around.....

Code:

root@sonarr:~ # pkg info sonarr
sonarr-3.0.9.1549
Name           : sonarr
Version        : 3.0.9.1549
Installed on   : Fri Nov  4 16:09:04 2022 PDT
Origin         : net-p2p/sonarr
Architecture   : FreeBSD:13:*
Prefix         : /usr/local
Categories     : net-p2p
Licenses       : GPLv3
Maintainer     : michiel@vanbaak.eu
WWW            : https://sonarr.tv
Comment        : PVR for Usenet and BitTorrent users
Options        :
        X11            : off
Annotations    :
        repo_type      : binary
        repository     : FreeBSD
Flat size      : 34.0MiB
Description    :
Sonarr is a PVR for Usenet and BitTorrent users.


WWW: https://sonarr.tv
root@sonarr:~ # pkg upgrade sonarr
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
root@sonarr:~ # pkg search sonarr
sonarr-3.0.10.1567             PVR for Usenet and BitTorrent users
root@sonarr:~ #

 

[Patrick M. Hausen]

Have you verified with freebsd-version inside the jail? Also you might want to try pkg upgrade -f sonarr.

 

[winnielinnie]

Did you "lock" any package or dependency at any point in the past?

If so, you need to use "pkg unlock <packagename>" to allow it to upgrade.

 

[Dirk]

Did you "lock" any package or dependency at any point in the past?

If so, you need to use "pkg unlock <packagename>" to allow it to upgrade.

Thanks. I'l look into that. I did have to lock Mono in the past because and upgrade of sonarr wanted to downgrade Mono.

 

[Dirk]

I was going by the TN GUI which said 13.2. the request from the CLI returned the same version.

Have you verified with freebsd-version inside the jail? Also you might want to try pkg upgrade -f sonarr[/IC [/QUOTE]

 

[winnielinnie]

Thanks. I'l look into that. I did have to lock Mono in the past because and upgrade of sonarr wanted to downgrade Mono.

This is likely why.

If you're going to lock packages and dependencies, it can cause strange results in the future when you try to upgrade.

Not familiar with the Mono issue, but I'd recommend:

1. Creating a snapshot of poolname/iocage/jails/sonarr/root (Which can be easily reverted if something breaks)
2. List all locked packages ( pkg lock -l )
3. Unlock any locked packages ( pkg unlock <packagename> )
4. Then try doing a full upgrade again

 

[Dirk]

Ladies and gentlemen! We have a winner! Sonarr was locked. I find it a bit interesting because in my past experience freebsd/truenas would object to trying to upgrade a locked package. Perhaps that should be a consideration? "Are any installed packages locked?" the fact that it would not even list it or error, left the user blind. IMO listing all packages even locked ones (installed ones of course) would be a benefit.

In any event thank you both, especially Patrick for your time. Live and learn.

 

[Dirk]

This is likely why.

If you're going to lock packages and dependencies, it can cause strange results in the future when you try to upgrade.

Not familiar with the Mono issue, but I'd recommend:

1. Creating a snapshot of poolname/iocage/jails/sonarr/root (Which can be easily reverted if something breaks)
2. List all locked packages ( pkg lock -l )
3. Unlock any locked packages ( pkg unlock <packagename> )
4. Then try doing a full upgrade again

Working from memory, sonarr was upgraded using a new mono, but the sonarr package didn't bring in that dependency. It got sporked and nobody could find the newer mono or how to install. If/when you did get mono 6.8 installed the soanarr package wanted to revert it.

Thanks again!