We are using the CentOS-6 that is part of the Rivendell Broadcast Appliance system from Paravel Systems. We have a paid-up support contract. It’s really great, and we love it a lot! Thanks for all the wonderful features!
Now the problem: The Rivendell 2.15.3-1 update appears along with more than 300 other updates from Centos when we run “yum check-update”. Some of those CentOS updates are important security fixes. So far as I know, there are no security issues with the Rivendell 2.15.3-1 package. However, if we hold off installing the Rivendell 2.15.3-1 update because we don’t want to deal with the bug in the attached mail from Fred Gleason, discovered by Ryan Williams, we are also holding off on installing all the security (and other) fixes from CentOS. We have two alternatives, as I see it. 1) What we’re doing now: hold off on any updates until the attached bug is fixed by Paravel Systems. or 2) Disable the Paravel Systems repo in the yum configuration files, thereby preventing the Rivendell 2.15.3-1 update from being applied — along with everything else from Paravel. We’ve never done this before (never needed to!) and we don’t know what it might break if we try it. If it breaks something in the Rivendell system, that will take us off the air, which we don’t want to do. So… Please fix the attached bug! Thanks! Rick Thomas SysAdmin, KPTZ 91.9 FM, Port Townsend, WA On May 16, 2017, at 1:26 PM, Scott Spillers <sco...@paravelsystems.com> wrote: > Rick, > We do not have any influence over development of the CentOS Linux > distribution, only the Rivendell code. What version of CentOS are you using? > CentOS 5 has reached end of life and is no longer updated. You may want to > consider updating to CentOS 7 if your version of the distro is no longer > supported. > > Scott Spillers > sco...@paravelsystems.com > > On May 16, 2017 12:10 PM, "Rick Thomas" <r...@kptz.org> wrote: > Dear Rivendell developers, > > We’ve been holding off installing the Rivendell2.15.3-1 update, hoping to see > a fix for this bug. > > But with all the activity over the NSA zero-day exploits released a few > months ago, it’s becoming imperative that we get the security updates from > CentOS that this is blocking. > > Please bump up the priority on this one… > > Thanks, > Rick Thomas, > SysAdmin KPTZ, 91.9 FM Port Townsend, WA > > > > ---------- Forwarded message --------- > > From: Fred Gleason <fr...@paravelsystems.com> > > Date: Tue, Mar 28, 2017 at 8:05 AM > > Subject: Re: [RDD] Rivendell v2.15.3 > > To: User discussion about the Rivendell Radio Automation System > > <rivendell-dev@lists.rivendellaudio.org> > > > > On Mar 28, 2017, at 10:57, Ryan Williams <rya...@gmail.com> wrote: > >> I'm having an regression with the most recent release. If I open RDLogEdit > >> and try to add to a log's description it does not save. We use the field > >> field to add "READY" to the end of the description when the log is cleared > >> for air, so this one is going to sting a lot. > > Partially confirmed here. If you use the ‘Save’ button, the updated > > Description is indeed lost. However, clicking ‘OK’ (without clicking > > ‘Save’ first) appears to work normally. > > > > Cheers! > > > > |----------------------------------------------------------------------| > > | Frederick F. Gleason, Jr. | Chief Developer | > > | | Paravel Systems | > > |----------------------------------------------------------------------| > > | A room without books is like a body without a soul. | > > | -- Cicero | > > |----------------------------------------------------------------------| > > > > _______________________________________________ > > Rivendell-dev mailing list > > Rivendell-dev@lists.rivendellaudio.org > > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
