Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[David Sydney]

I am relatively new to Linux and enjoying the learning experience... I started off with Ubuntu but have settled on using Manjaro for last 6 months. I have installed JRiver through the Arch USer Repository and migrated my library sucessfully over Mind you all the media files are sitting in the same place and are accessed by MC Linux, MC Windows and iTunes until I empty the account of $.

The question I have is that through the AUR I am getting JRiver 30.0.45 which is significantly behind. I am guessing this is out control of JRiver right - is it the Arch community who have not updated on the AUR yet. On AUR is version 24, 25 and 30 so several went AWOL. I'd prefer not load stuff outside the package manager at this stage. I have already had to rebuild the system 3 times after I have stuffed things up or not quite fully understood the implications of how Windows bullies other OS off the PC (dual boot)

Just trying to understand the version control through other package managers?

[mattkhan]

From the arch wiki

Warning: AUR packages are user-produced content. These PKGBUILDs are completely unofficial and have not been thoroughly vetted. Any use of the provided files is at your own risk.

Which means some user has published those old versions as you guessed

JRiver themselves just publish deb packages for one to install and there is a user provided install script as mentioned on https://wiki.jriver.com/index.php/Linux_Installation_%26_Removal which looks like it supports manjaro so would be the semi official way to install it

[Awesome Donkey]

AUR is community driven by volunteers which are called maintainers. You can update the PKGBUILD yourself and it does indeed work (I did this manually all the time) but it may require a bit of text editing and whatnot. However, if you make an account on the AUR, you can flag the package out-of-date and post a link to the topic of the newest release and that'll help the package maintainer and the users.

I used to flag it every time a new build came out, but I stopped doing so after I switched from Arch Linux to Fedora as my main distro. I went ahead and flagged it and posted a link to the 30.0.87 topic, but I highly suggest someone actively using Arch Linux or Manjaro to do so in the future.

[David Sydney]

Thanks guys... err. When I figure our what you are talkin about and how...beyond just the concept. I will certainly do that??!! Meanwhile I notice that the version 30.0.87 came through AUR so thanks for that!

[Awesome Donkey]

It's probably easier to go to https://aur.archlinux.org/ then click on Register to create an account. Once created in the future you can use Login instead and log into the account, then go to https://aur.archlinux.org/packages/jriver-media-center and on the right side under Package Actions there's a option called Flag package out-of-date. Click that and you'll be able to add a comment - I highly suggest saying what the full build number is (e.g. 30.0.87) and add a link to the release topic for it, e.g. https://yabb.jriver.com/interact/index.php/topic,135525.0.html and hit the Flag button.