Forums

Resolved
1 votes
Hi,
Serviio version 2.1 is now available for ClearOS 7. If you want to update your existing serviio version you will have to do it manually from command line:

yum update --enablerepo=clearos-contribs-testing serviio


NOTE: Any "Pro licence" that you may have for Serviio 1.x will NOT work with Serviio 2.x , so if you update and still want the Pro-features, then you need to go to http://serviio.org and purchase a new licence.

Release Notes

Since the 2.1 version will make any 1.0 licence unusable, I am planning to keep Serviio 2.1 in contribs-testing and not release it into the normal contribs repo (because then the update will be forced upon everyone that has auto-update on).

/Fred
Sunday, June 07 2020, 08:02 PM
Like
1
Share this post:
Responses (11)
  • Accepted Answer

    Saturday, November 26 2022, 12:42 PM - #Permalink
    Resolved
    0 votes
    John,
    Since ClearOS is a ghost ship at the moment there is no way for me, as an outsider, to release an updated Serviio package since I need someone on the inside to get the build environment up and running and also to release the package into the ClearOS repos. So you are on your own.

    If you want you can build a new rpm package yourself. I do not think there are any major changes in the serviio source files, so most of it will likely compile OK without to many changes (you might need to adjust one or two of the patch files). If you have never done this it will probably take you a few hours. Below follows a brief instruction (from the top of my head, which means that I might have forgotten something...) of what is needed:

    1. I suggest you create a virtual machine on your normal PC to use as your development environment (VirtualBox is one alternative if you are using a Windows PC). Create a Linux 64 bit machine. (set the "network card" to run in bridge mode (not NAT), so that you can connect to it from a ssh terminal on your LAN). Download the ClearOS 7 DVD iso file to install ClearOS as the operating system on your virtual machine.
    2. When your ClearOS virtual machine is up and running, use ssh from your PC to connect to it (puTTy is a very good program)
    3. Follow the instructions here to "upgrade your virtual ClearOS machine so that it has all needed files to build rpms":
    https://www.clearos.com/clearfoundation/development/clearos/content:en_us:dev_development_environment
    If you have not used vim before for text editing, you can skip that part and maybe use nano instead, which I think is easier.
    4. Now you should have a folder called "rpm" in your home directory for your normal user (do NOT build stuff logged in as root).
    5. In your home directory create a folder called serviio. download the old source-rpm file:
    wget http://mirror1-newyork.clearos.com/clearos/7/contribs/SRPMS/serviio-2.2.1-1.v7.src.rpm

    6. Unpack the source rpm:
    rpm2cpio serviio-2.2.1-1.v7.src.rpm[ | cpio -idmv
    You should now have 2 folders:
    SPECS
    here your serviio.spec file should be

    SOURCES
    here the rest of the files should be

    7. You will likely need to download a few more files: The files listed in "sources.download" should be downloaded and put in the SOURCES folder. (use nano to open the sources.download file, there is one file on each row (ignore the sha256 checksum in the beginning of each line, but look at the url to the right). The file "sources.download" is not needed in the building process.
    8. edit the serviio.spec file in the SPECS folder with your favorite text editor. change the release version etc so that it matches the new serviio release rpm name/version. Save the file
    9. Copy both the SOURCES and SPECS folders with its content to the rpm folder
    10. go to the SPECS folder and try to build
    rpmbuild -ba serviio

    11. You might be missing a few packages, in such case you will get an error stating what is missing. Using your root account install the missing packages
    yum install <your missing package>
    . Repeat step 10-11 until it starts building.
    12. You might also get an error that one of the patch files could not be applied. In that case the upstream (serviio) source files have changed so much so that the patch files needs to be adjusted. Google to find out how to create/modify patch files (tip: create two folders "org" and "mod", unpack the files to be patched from the serviio rpm and put them (with the correct folder tree) under the "org" folder. Copy the content of the "org" folder to the "mod" folder, edit the files under the "mod" folder (according to what you can see in the old patch files). Then use something like this
    diff -Naur org/subfolder1/subfolder2/myserviio.file  mod/subfolder1/subfolder2/myserviio.file > myserviio.file.patch
    . Then try to build again.
    13. After a successful buld, copy the rpm file (found under rpm/rpms/...) to your machine where you want to install serviio. You can try in your virtual development machine first if you like.
    yum localinstall serviio-x-y-z.rpm


    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    John
    John
    Offline
    Saturday, November 26 2022, 08:14 AM - #Permalink
    Resolved
    0 votes
    Hi Fred,

    Serviio Pro 2.3 is released and I was wondering if an update can still be made available, even when ClearOS is EOL.

    Thanks in advance.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 20 2021, 08:02 PM - #Permalink
    Resolved
    0 votes
    John,
    Maybe I get some time during the weekend to look at this. If the changes are minor, which it says in the release notes, then I think I can put it in contribs-testing within a week after some testing first..

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    John
    John
    Offline
    Tuesday, October 19 2021, 04:38 PM - #Permalink
    Resolved
    0 votes
    Hi all,

    Can anyone explain to me how I upgrade Serviio Pro from 2.1 to 2.2 on a COS box, with all the required dependencies (FFmpeg, dcraw & Java 8) and without braking it ... ?!?

    https://www.serviio.org/download

    Thanks in advance,

    John
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 10 2020, 03:19 PM - #Permalink
    Resolved
    1 votes
    Eddy,
    Not sure if I am the right guy to try to answer your question(s). But to maybe better understand how things work I will try to describe below a bit more detailed than you asked for... ;)

    I develop/maintain the "wrapper" that installs Serviio using the ClearOS marketplace. It is called "app-serviio" and I update it if/when Serviio (or ClearOS) changes so installations and controlling (enable/disable the serviio service from the ClearOS webconfig page) is still possible. For the last few releases Serviio has not changed its behaviour so there has not been any reason for me to make any update of app-serviio. The app-serviio version number is NOT the same as the version number of the actual serviio program. The Serviio Pro license is connected to Serviio, not to app-serviio.

    The serviio program itself, and its roadmap is entirely done upstream. I do however, package it into a serviio.rpm package for ClearOS whenever upstream releases a new version. Now, a bit more than a year ago, upstream decided to go for a Serviio 2.0 release. With it came also the requirement to buy a new Pro license as the old from "1.x" is not valid for "2.x". I did what I normally do: packaged the new serviio-2.0.rpm but faced a problem that is a bit problematic: The way ClearOS is setup (for most users) is that there will be automatic updates whenever a newer package is available in the ClearOS repos, and there is "no way back". IF I would have requested the ClearOS team to put the new serviio 2.0 package in the normal contribs repo (and subsequently contribs-verified later on), that would have forced anyone with a Pro licence on a ClearOS platform to having to buy a new license even if they were happy to stay where they were.

    My solution at the time, and this is still the situation, was to "just" build serviio-2.0.rpm and leave it sitting in the contribs-testing repo (from which no one should do automatic installations from). In that way, anyone who really wanted the 2.0 (and now 2.1) version could manually upgrade if they wanted to, but it would be a very active decision from their point of view. And yes, it does require a bit of command line. Regarding the stability, I have not tested it personally on a Home (or business) system so I can not make a firm promise. But I do not see any problem as the serviio package itself is pretty stand-alone from the rest of the system.

    Now, I did have a discussion with Nick a month or two ago, if it is about time to "force" the Serviio 2.x upon all the ClearOS users by moving it to the contribs repo. We never really finished that discussion, and maybe it is time to take an active decision.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Eddy Winko
    Eddy Winko
    Offline
    Monday, August 10 2020, 11:00 AM - #Permalink
    Resolved
    0 votes
    Not sure if you can help, or if I am in the right place, but if there a road map for when this release of Serviio will be added to the marketplace for the paid Home Edition of ClearOS? I was fooled by the version number of 1.8 and went ahead and purchased a Pro license so that I could connect my Android TV box to my Serviio server only to discover that it is version 1.x and not compatible with the android app. Am I able to install the update as you describe above without affecting the stability of Clearos Home Edition? If you think that is possible can you point me to a guide on how to install software from a command line as I don't normally get involved in the workings of these things :) Thanks in advance for any help\advice.
    The reply is currently minimized Show
  • Accepted Answer

    grubs
    grubs
    Offline
    Wednesday, July 29 2020, 03:31 PM - #Permalink
    Resolved
    0 votes
    I had a similar experience John.

    The corrupt symbols on the screen appears to be a caching issue that was fixed by your reboot. I saw this too.

    I ended up uninstalling Serviio because the media server is now incompatible with windows media player (Windows 10) and my smart TV also could not find any files in the libraries despite serviio rebuilding them.. so I gave up. I tried some of the inbuilt configurations for different clients but just could not get the right glue to hold it all together.
    The reply is currently minimized Show
  • Accepted Answer

    John
    John
    Offline
    Wednesday, July 29 2020, 12:17 PM - #Permalink
    Resolved
    0 votes
    Hi all,

    After successfully installing Serviio 1.8 from the marketplace, I decided too update it to version 2.1.
    With version 1.8 everything was working like to be expected, but after the update I was unable to find the files from the library and parts of the Serviio console got messed up.

    I initially stopped the Serviio service on the web interface of my ClearOS box.
    Then I updated it with the following results:
    # yum update --enablerepo=clearos-contribs-testing serviio
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Loading mirror speeds from cached hostfile
    * clearos: mirror2-amsterdam.clearos.com
    * clearos-centos: download4.clearsdn.com
    * clearos-centos-sclo-rh: download4.clearsdn.com
    * clearos-centos-updates: download4.clearsdn.com
    * clearos-contribs: mirror2-amsterdam.clearos.com
    * clearos-contribs-paid: mirror2-amsterdam.clearos.com
    * clearos-contribs-testing: mirror2-amsterdam.clearos.com
    * clearos-epel: download4.clearsdn.com
    * clearos-fast-updates: download4.clearsdn.com
    * clearos-infra: mirror2-amsterdam.clearos.com
    * clearos-paid: mirror2-amsterdam.clearos.com
    * clearos-updates: mirror2-amsterdam.clearos.com
    * nux-dextop: li.nux.ro
    * private-clearcenter-dnsthingy: download2.clearsdn.com:80
    * private-clearcenter-plex: download1.clearsdn.com:80
    clearos | 3.7 kB 00:00
    clearos-centos | 3.6 kB 00:00
    clearos-centos-sclo-rh | 3.0 kB 00:00
    clearos-centos-updates | 2.9 kB 00:00
    clearos-contribs | 3.5 kB 00:00
    clearos-contribs-testing | 3.5 kB 00:00
    clearos-epel | 2.9 kB 00:00
    clearos-fast-updates | 3.0 kB 00:00
    clearos-infra | 3.5 kB 00:00
    clearos-updates | 3.5 kB 00:00
    nux-dextop | 2.9 kB 00:00
    (1/17): clearos/7/group_gz | 1.6 kB 00:00
    (2/17): clearos/7/primary_db | 1.0 MB 00:00
    (3/17): clearos-centos/x86_64/group_gz | 153 kB 00:00
    (4/17): clearos-contribs/7/updateinfo | 96 B 00:00
    (5/17): clearos-contribs-testing/7/updateinfo | 96 B 00:00
    (6/17): clearos-contribs-testing/7/primary_db | 71 kB 00:00
    (7/17): clearos-contribs/7/primary_db | 66 kB 00:00
    (8/17): clearos-fast-updates/x86_64/primary_db | 10 kB 00:00
    (9/17): clearos-infra/7/updateinfo | 96 B 00:00
    (10/17): clearos-centos-updates/x86_64/primary_db | 2.8 MB 00:01
    (11/17): clearos-infra/7/primary_db | 11 kB 00:00
    (12/17): clearos-updates/7/primary_db | 178 kB 00:00
    (13/17): clearos-centos-sclo-rh/x86_64/primary_db | 2.8 MB 00:02
    (14/17): clearos-updates/7/updateinfo | 96 B 00:00
    (15/17): nux-dextop/x86_64/primary_db | 1.8 MB 00:00
    (16/17): clearos-centos/x86_64/primary_db | 6.1 MB 00:04
    (17/17): clearos-epel/7/x86_64/primary_db | 11 MB 00:05
    clearos-contribs-paid | 3.5 kB 00:00
    clearos-paid | 3.5 kB 00:00
    private-clearcenter-dnsthingy | 3.0 kB 00:00
    private-clearcenter-plex | 3.0 kB 00:00
    Resolving Dependencies
    --> Running transaction check
    ---> Package serviio.noarch 0:1.10.1-1.v7 will be updated
    ---> Package serviio.noarch 0:2.1-1.v7 will be an update
    --> Finished Dependency Resolution

    Dependencies Resolved

    ================================================================================
    Package Arch Version Repository Size
    ================================================================================
    Updating:
    serviio noarch 2.1-1.v7 clearos-contribs-testing 27 M

    Transaction Summary
    ================================================================================
    Upgrade 1 Package

    Total download size: 27 M
    Is this ok [y/d/N]: y
    Downloading packages:
    Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
    serviio-2.1-1.v7.noarch.rpm | 27 MB 00:05
    Running transaction check
    Running transaction test
    Transaction test succeeded
    Running transaction
    Updating : serviio-2.1-1.v7.noarch 1/2
    Cleanup : serviio-1.10.1-1.v7.noarch 2/2
    Verifying : serviio-2.1-1.v7.noarch 1/2
    Verifying : serviio-1.10.1-1.v7.noarch 2/2

    Updated:
    serviio.noarch 0:2.1-1.v7

    Complete!

    I had to create new accounts, before I was able to login to Serviio again, but I think that this is an improvement.
    I attempted to "Force refresh" the library, but without result.
    Also the "Status" tab of the Serviio console is currently messed up with all sorts of variables on the screen.

    Should I attempt to uninstall Serviio from the ClearOS web interface and start using version 1.8 again ... ?!?

    Can someone please help me with making Serviio work again ... ?!?
    Please assist,

    John

    Ps. After rebooting my ClearOS box, the "Status" tab of the Serviio console was without errors, but even after starting the service on the Servio "Status" tab, I can still not see any of the videos I previously added to the Flexshare.
    After adding a new video, all the other videos showed up again.
    Sorry for the misunderstanding, but I do not delete this post, because others might get the same problems.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, June 22 2020, 11:30 AM - #Permalink
    Resolved
    0 votes
    grubs,
    The ClearOS Serviio "webconfig-app" is just a shell to start/stop and control Serviio in the ClearOS environment. Since there is no API-change in Serviio 2.x from the 1.x versions, this shell did not need any update, so it is still version 1.8 (its versioning is not really connected to serviio releases).

    So everything is as it is meant to be.

    /Fred
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, June 16 2020, 01:59 PM - #Permalink
    Resolved
    0 votes
    Don't worry about the mirror error. It is a third party mirror not controlled by ClearCenter, and yum did its job and fell over to a working mirror.
    The reply is currently minimized Show
  • Accepted Answer

    grubs
    grubs
    Offline
    Tuesday, June 16 2020, 01:00 PM - #Permalink
    Resolved
    0 votes
    Thanks Fredrik. I just installed into a new community v7.7 install and got the v1.8 from the marketplace and was a bit surprised when the serviio console said update to 2.1 was available and that led me to git where I saw activity so I came here :D

    I installed 2.1 using your instructions - seemed to have worked fine and the serviio interface reports v2.1

    Note however the ClearOS webconfig interface still reports "App Version 1.8" in the app info box on the right side of the screen where the start/stop button is.
    I found the version 1.8 is coded in two places in /usr/clearos/apps/serviio/deploy/info.php


    During install I got

    a mirror that couldn't be accessed.. assume temporary but reporting it here for you in case it means something

    [root@gateway ~]# yum update --enablerepo=clearos-contribs-testing serviio
    Loaded plugins: clearcenter-marketplace, fastestmirror
    ClearCenter Marketplace: fetching repositories...
    Loading mirror speeds from cached hostfile
    * clearos: clearos.uberglobalmirror.com
    * clearos-centos: download2.clearsdn.com
    * clearos-centos-sclo-rh: download2.clearsdn.com
    * clearos-centos-updates: download2.clearsdn.com
    * clearos-contribs: clearos.uberglobalmirror.com
    * clearos-contribs-testing: clearos.uberglobalmirror.com
    * clearos-epel: download2.clearsdn.com
    * clearos-fast-updates: download2.clearsdn.com
    * clearos-infra: clearos.uberglobalmirror.com
    * clearos-paid: mirror1-singapore.clearos.com
    * clearos-updates: clearos.uberglobalmirror.com
    http://clearos.uberglobalmirror.com/7/contribs-testing/x86_64/repodata/repomd.xml" target="_blank">http://clearos.uberglobalmirror.com/7/contribs-testing/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://clearos.uberglobalmirror.com/7/contribs-testing/
    x86_64/repodata/repomd.xml: (28, 'Connection timed out after 30000 milliseconds')
    Trying other mirror.
    clearos-contribs-testing | 3.5 kB 00:00:00
    (1/2): clearos-contribs-testing/7/primary_db | 75 kB 00:00:00
    clearos-contribs-testing/7/upd FAILED
    http://clearos.uberglobalmirror.com/7/contribs-testing/x86_64/repodata/bac1f19c5dfca742f393716e4a466cf35b259a6512741309eae58f87cee54df4-updateinfo.xml.xz: [Errn
    o 12] Timeout on http://clearos.uberglobalmirror.com/7/contribs-testing/x86_64/repodata/bac1f19c5dfca742f393716e4a466cf35b259a6512741309eae58f87cee54df4-updatei
    nfo.xml.xz: (28, 'Connection timed out after 30001 milliseconds')
    Trying other mirror.
    (2/2): clearos-contribs-testing/7/updateinfo | 96 B 00:00:00
    Resolving Dependencies
    --> Running transaction check
    ---> Package serviio.noarch 0:1.10.1-1.v7 will be updated
    ---> Package serviio.noarch 0:2.1-1.v7 will be an update
    --> Finished Dependency Resolution
    The reply is currently minimized Show
Your Reply