On Wed, May 25, 2011 at 12:42 PM, Douglas Hubler <[email protected]> wrote:
> On Wed, May 25, 2011 at 12:34 PM, [email protected] <[email protected]> > wrote: > > Well, interesting then because my system didn't get updated to 4.4.0 when > I ran the update, it only updated 4.2.1. > > This is also a departure how sipxecs release eng ran in the past I > think. You have to explicitly install a new sipxecs repository file > in order to jump to the new X.X release. This is so you can actually > apply bug fixes to your stable system when they come out and not > accidentally upgrade the entire system one day just because a new > major release came out. > > Messing w/repo files is probably not the most user friendly so maybe > we should start installing a script that when run will repoint your > local yum repository file to the next release. This is a lot how OS > upgrades work. > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > Now that the sipx repo and the OS repo and no longer joined at the hips from an ISO install, perhaps a: yum upgrade sipxrepo might be in order? if so, +1
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
