More > JRiver Media Center 22 for Linux
[How-To] Add the APT Repository for Media Center 22
Awesome Donkey:
With the beta release of Media Center 22, the APT Repository has been updated and changed for Media Center 22. What does this mean? If you're already using the APT Repository for Media Center 20 or Media Center 21 and you're going to replace it with Media Center 22, you'll need to update your sources. Otherwise if you're doing a clean install of Media Center 22 you can skip step 0!
Step 0 - Replacing Media Center 20/21 with Media Center 22:
First make a backup of your Media Center 20/21 library and save it to a place where you can find it, e.g. desktop. This is VERY important!
Now we've got to remove the old mediacenter20.list and/or mediacenter21.list file from the /etc/apt/sources.list.d/ directory. Open a Terminal (by either pressing CTRL+ALT+T or by searching for the Terminal in your desktop environment) and either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
For Media Center 20:
--- Code: ---sudo rm /etc/apt/sources.list.d/mediacenter20.list
--- End code ---
For Media Center 21:
--- Code: ---sudo rm /etc/apt/sources.list.d/mediacenter21.list
--- End code ---
Now assuming you made a backup of your library, lets remove Media Center 20/21 completely. With a Terminal open (by either pressing CTRL+ALT+T or by searching for the Terminal in your desktop environment) and either type the following commands one-by-one or copy and paste the commands in one-by-one and press Enter (you *may* be prompted for your password);
For Media Center 20:
--- Code: ---sudo apt-get remove mediacenter20
--- End code ---
For Media Center 21:
--- Code: ---sudo apt-get remove mediacenter21
--- End code ---
Then...
For Media Center 20:
--- Code: ---sudo rm -rf '/usr/lib/jriver/Media Center 20'
--- End code ---
For Media Center 21:
--- Code: ---sudo rm -rf '/usr/lib/jriver/Media Center 21'
--- End code ---
And finally...
For Media Center 20:
--- Code: ---sudo rm -rf '~/.jriver/Media Center 20'
--- End code ---
For Media Center 21:
--- Code: ---sudo rm -rf '~/.jriver/Media Center 21'
--- End code ---
This will completely remove Media Center 20/21 - now you're ready to install Media Center 22!
Step 1 - Adding the JRiver Media Center 22 APT Repository:
The APT repository is required to install Media Center 22 and keep Media Center 22 updated with every new release. There's three available repositories; Stable, Latest and Beta. Decide for yourself which one you want to use - descriptions of each are below.
NOTE: You can run the beta repo alongside either the latest or stable repos if desired (for beta testing, etc.). Don't try to use both the latest and stable repos at the same time - only choose and use one of them!
First, open a Terminal (by either pressing CTRL+ALT+T or by searching for the Terminal in your desktop environment) and either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
--- Code: ---wget -q "http://dist.jriver.com/mediacenter@jriver.com.gpg.key" -O- | sudo apt-key add -
--- End code ---
Next, with the Terminal still open, we need to download and add the correct mediacenter.list file to /etc/apt/sources.list.d/ depending if you're using 32-bit or 64-bit. Also, you can pick which repository you want to use (Stable, Latest or Beta - choose only one!) so either type one the following commands or copy and paste the command in and press Enter;
Media Center 22 (Stable) Repository:
This repository is using the latest stable release of Media Center 22 and is currently the default repository that should be used. It may be out-of-date compared to the Latest repository, however these builds have been thoroughly tested and are considered stable.
If you're using 64-bit Debian Jessie (or any derivatives like Ubuntu, Linux Mint, etc.):
--- Code: ---sudo wget http://dist.jriver.com/stable/mediacenter/mediacenter22jessie.list -O /etc/apt/sources.list.d/mediacenter22.list
--- End code ---
Or...
If you're using 32-bit Debian Wheezy (or any derivatives like Ubuntu, Linux Mint, etc.):
--- Code: ---sudo wget http://dist.jriver.com/stable/mediacenter/mediacenter22.list -O /etc/apt/sources.list.d/mediacenter22.list
--- End code ---
Or...
If you're using an ARM device (like a Raspberry Pi) and distro like Raspbian:
--- Code: ---sudo wget http://dist.jriver.com/stable/mediacenter/mediacenter22native.list -O /etc/apt/sources.list.d/mediacenter22.list
--- End code ---
Media Center 22 (Latest) Repository:
This repository is using the latest up-to-date release of Media Center 22. There *may* be instability issues!
If you're using 64-bit Debian Jessie (or any derivatives like Ubuntu, Linux Mint, etc.):
--- Code: ---sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter22jessie.list -O /etc/apt/sources.list.d/mediacenter22.list
--- End code ---
Or...
If you're using 32-bit Debian Wheezy (or any derivatives like Ubuntu, Linux Mint, etc.):
--- Code: ---sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter22.list -O /etc/apt/sources.list.d/mediacenter22.list
--- End code ---
Or...
If you're using an ARM device (like a Raspberry Pi) and distro like Raspbian:
--- Code: ---sudo wget http://dist.jriver.com/latest/mediacenter/mediacenter22native.list -O /etc/apt/sources.list.d/mediacenter22.list
--- End code ---
Media Center 22 (Beta) Repository:
This repository is for beta builds - not intended for users who prefer stability! These builds are likely buggy, may crash, etc.
If you're using 64-bit Debian Jessie (or any derivatives like Ubuntu, Linux Mint, etc.):
--- Code: ---sudo wget http://dist.jriver.com/beta/mediacenter/mediacenter22jessie.list -O /etc/apt/sources.list.d/mediacenter22beta.list
--- End code ---
Or...
If you're using 32-bit Debian Wheezy (or any derivatives like Ubuntu, Linux Mint, etc.):
--- Code: ---sudo wget http://dist.jriver.com/beta/mediacenter/mediacenter22.list -O /etc/apt/sources.list.d/mediacenter22beta.list
--- End code ---
Or...
If you're using an ARM device (like a Raspberry Pi) and distro like Raspbian:
--- Code: ---sudo wget http://dist.jriver.com/beta/mediacenter/mediacenter22native.list -O /etc/apt/sources.list.d/mediacenter22beta.list
--- End code ---
Finally, we need to reload the packages list, so with the Terminal still open either type the following command or copy and paste the command in and press Enter;
--- Code: ---sudo apt-get update
--- End code ---
That's it! Now we can install Media Center 22...
Step 2 - Installing Media Center 22:
You can now install Media Center 22 by opening a Terminal (by either pressing CTRL+ALT+T or by searching for the terminal in your desktop environment) or re-use the Terminal from the previous step. Next either type the following command or copy and paste the command in and press Enter (you *may* be prompted for your password);
--- Code: ---sudo apt-get install mediacenter22
--- End code ---
And that's it, Media Center 22 should be installed now. Hope this helps people getting the Media Center 22 APT repository added and working on Debian, Ubuntu, Linux Mint, etc.
mwillems:
Two quick suggestions about step 0:
1) I would advise adding a step suggesting users create a backup of their cover art directory before removing the whole JRiver 20 or 21 directory. The library backup won't capture any cover art stored in that directory, and even if you store art in the file tags/sidecars certain art will always be stored in the Cover Art directory (e.g. TV series and season art). So maybe add a step to back that up, or recommend that users move it over before blowing away their old settings? Ditto for skins, they'd lose any custom skins.
2) In any case it might make sense to move the "remove prior version completely" step farther down (after they've finished the new installation and tested that everything works as expected). This is especially true as the default library backup save location may be in the directory that you're recommending they delete in the next step. You suggest saving the library backup to the desktop, but you don't make it clear that saving in the default location will result in a lost library if you follow the rest of the steps. An astute reader would catch it (like this one ;D ), but someone mechanically following the steps might not.
Thanks for writing this up!
skifastbadly:
Excellent overview, thanks a lot.
However, after I performed the update from MC21 to MC22, the app doesn't know about my MC master license. Is there something I've missed? Shouldn't it 'know' about the master license?
Thanks
Ski
bob:
--- Quote from: skifastbadly on October 08, 2016, 05:01:09 pm ---Excellent overview, thanks a lot.
However, after I performed the update from MC21 to MC22, the app doesn't know about my MC master license. Is there something I've missed? Shouldn't it 'know' about the master license?
Thanks
Ski
--- End quote ---
You entered a MC 22 master license into MC 22 linux and it didn't work?
skifastbadly:
No. I guess I didn't account for the fact that changing revisions would require an updated license. But it started working. Weird. I will update the license just to be sure. This stuff can be confusing.
Navigation
[0] Message Index
[#] Next page
Go to full version