More > JRiver Media Center 33 for Linux
installJRMC - MC installer for Linux
BryanC:
--- Quote from: Awesome Donkey on November 01, 2024, 11:06:35 am ---An idea, an addition to --mcversion to specific a major version of MC, e.g. --mcversion 32 to install the latest/last version of the specified MC on the system (same could work for MC33, MC31, etc.). This would be useful for installing older MC versions on a system... well, as long as it's not installing too old MC versions which may not work on newer Linux distros due to dependency issues.
--- End quote ---
Good idea, only specifying the major version is now implemented in the dev branch, I want to do a little testing on some of the older distros to make sure they don't blow up before releasing it.
--- Code: -----mcversion VERSION
Build or install a specific MC version, ex. "33.0.37" or "33" (default: latest)
--- End code ---
Awesome Donkey:
The one-liner command fails in Ubuntu 24.10 (maybe others as well). It was reported here and I can confirm it just fails with no reason given.
--- Code: ---curl https://git.bryanroessler.com/bryan/installJRMC/raw/master/installJRMC|bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 53666 0 53666 0 0 30273 0 --:--:-- 0:00:01 --:--:-- 30268
Starting installJRMC
To enable debugging output, use --debug or -d
Adding universe repository
[sudo] password for michael:
Installing JRiver Media Center from remote repository
Error: Package update failed!
Error: JRiver Media Center installation from remote repository failed
--- End code ---
Of course it being a one-liner, I don't think adding -d or --debug actually works there which actually makes me wonder something... why isn't the debug (verbose) not the default and the current behavior not behind a -s or --silent switch? I can understand the benefit on not wanting to see all the output during install, but for most new users it may actually be more beneficial to make -d the default as it's more likely they'll run into issues like this and not know what to do about it. Or at least give more information about why it fails? Just thinking out loud. :)
Awesome Donkey:
Oh, and speaking of Ubuntu 24.10, I totally forgot to mention this when Ubuntu 24.10 was released last month and as-is you'd get an error when running sudo apt update in a Terminal...
--- Code: ---Error: The repository 'http://dist.jriver.com/latest/mediacenter oracular Release' does not have a Release file.
--- End code ---
If you dig a little deeper...
--- Code: ---Repositories should provide a clear-signed InRelease file, but none found at http://dist.jriver.com/latest/mediacenter/dists/oracular/InRelease.The repository 'http://dist.jriver.com/latest/mediacenter oracular Release' does not have a Release file.
--- End code ---
This likely affects installing MC manually from the repo too.
EDIT: Okay, I remember what it is now. You can't use a /etc/apt/sources.list.d/jriver.list file anymore (otherwise it'll fail), you have to use a /etc/apt/sources.list.d/jriver.sources file with the following contents...
--- Code: ---Types: deb
URIs: http://dist.jriver.com/latest/mediacenter/
Signed-By: /usr/share/keyrings/jriver-com-archive-keyring.gpg
Suites: noble
Components: main
--- End code ---
The jriver.list file can't be present at all otherwise it'll cause APT to error out. That's very likely why the one-liner is failing on Ubuntu 24.10, the script will probably have to detect Oracular and newer and if a jriver.list file is present it'll have to remove it before replacing it with a jriver.sources file. I actually encountered this on the day Ubuntu 24.10 was released nearly a month ago. I upgraded to 24.10 and when checking for updates via APT encountered this issue but I figured it out, fixed it and forgot all about it until now (including how to fix it). I also totally forgot to even mention it here on the forums too. Oooof, better late than never I guess. :-\
BryanC:
1.3.8 (11/4/2024)
1. Can specify major version number only for --mcversion
2. Added new sources file format support for Ubuntu >= 24.10
Oracular (Ubuntu 24.10) will default to using the noble repo by default until an Oracular repo is made available by JRiver.
Awesome Donkey:
It works fine now for clean installs, however install fails if jriver.list already previously exists, e.g. due to upgrade from an older Ubuntu to Ubuntu 24.10.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version