Jump to content

Upgrading from 4.7.0.40 to 4.7.1.0


Mael
Go to solution Solved by Mael,

Recommended Posts

I'm running 4.7.0.40 manually installed in a truenas jail following the freebsd instructions. I'd like to get off the beta train and back on to the standard release train. The the freebsd instructions are now updated to point to version 4.8. Can you provide an updated version of this command to install 4.7.1 along with any new package dependencies?

pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.8.0.0/emby-server-freebsd13_4.8.0.0_amd64.pkg

I tried browsing github and looking for the right path, but github doesn't allow it. I also don't see the freebsd releases under https://github.com/MediaBrowser/Emby.Releases

Maybe it would make sense to have a set of instructions for FreeBSD that point to the stable release? 

Edited by Mael
Link to comment
Share on other sites

Quote

Maybe it would make sense to have a set of instructions for FreeBSD that point to the stable release? 

Hi, yes that is the FreeBSD ports method of installing. If you want to use the standalone package then you'll have to get it manually in the github release.

Link to comment
Share on other sites

Happy2Play

You would have to wait for 4.7.1.0 to be built out for all platforms or install 4.7.0.60 to switch release branches.  But the beta instructions apply.

Release 4.7.0.60 · MediaBrowser/Emby.Releases (github.com)

22 minutes ago, Mael said:

I tried browsing github and looking for the right path, but github doesn't allow it. I also don't see the freebsd releases under https://github.com/MediaBrowser/Emby.Releases

It does just another layer in.

Releases · MediaBrowser/Emby.Releases (github.com)

  • Like 1
Link to comment
Share on other sites

The reason we don't have equivalent stable instructions is because then we have to support two non-equivalent ways of doing the same thing, so that's why we prefer to direct the stable audience to the FreeBSD ports method.

Link to comment
Share on other sites

Thanks for the help. I ran the following, to install 4.7.0.60 but the version is still 4.7.0.40

pkg upgrade && pkg update
service emby-server stop
pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.7.0.60/emby-server-freebsd13_4.7.0.60_amd64.pkg
service emby-server start

Any idea what I'm doing wrong?

Edited by Mael
Link to comment
Share on other sites

  • Solution

Ok this is weird. I saw that FreeBSD packages were available for 4.7.1. I ran the commands below and I ended up upgrading my instance form  4.7.0.40 to 4.7.0.60. Is something up with the builds where they are one version behind where they're supposed to be?

service emby-server stop
pkg add -f https://github.com/MediaBrowser/Emby.Releases/releases/download/4.7.1.0/emby-server-freebsd13_4.7.1.0_amd64.pkg
service emby-server start

Update - I spun up a fresh jail just to see if something was funky with the build. A fresh install with the same installation commands shows as version 4.7.1. This is very weird.

Update 2 - The output from pkg version shows 4.7.1 is the version installed, but the dashboard was showing 4.7.0.60 until I restarted the jail. After the restart the dashboard shows 4.7.1

Edited by Mael
Link to comment
Share on other sites

raidflex

So is 4.7.1.0 using .NET now? I switched to the beta mainly because it was using .NET instead if mono.

Link to comment
Share on other sites

9 minutes ago, raidflex said:

So is 4.7.1.0 using .NET now? I switched to the beta mainly because it was using .NET instead if mono.

Yes it does.

Link to comment
Share on other sites

I figured it out. I updated my post above. I ended up restarting the jail and poof... it showed 4.7.1 on the dashboard. 

Edited by Mael
  • Thanks 1
Link to comment
Share on other sites

16 minutes ago, Mael said:

I figured it out. I updated my post above. I ended up restarting the jail and poof... it showed 4.7.1 on the dashboard. 

Thanks for following up !

Link to comment
Share on other sites

raidflex
On 5/28/2022 at 3:57 PM, Luke said:

Yes it does.

So I removed the beta version and attempted to install the stable 4.7.1.0 from packages and mono wants to install as a dependency, yet I thought this should be built with .NET?

 

Edit: Well I manually installed the pkg like I did with the beta, not sure why when installing the pkg from the repo it is building with mono though. 

Edited by raidflex
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...