M. Ranganathan wrote: > On Fri, Aug 29, 2008 at 6:23 AM, Kevin Thorley <[EMAIL PROTECTED]> wrote: >> M. Ranganathan wrote: >>> Version is now 1.2.79. Please update the RPM as well. ( Not sure I >>> agree with having both the sipx-commons and RPM -- both with the same >>> jar file). >>> >>> Thanks >>> >>> Ranga >>> >> Ranga, >> After updating my view I am unable to build. I can't seem to get the >> jain-sip RPM through yum. Has this been updated on our updates server? >> Do we need to manually install it from somewhere?
I doubt Ranga is responsible for your problems ;-) The RPMs are here: http://sipxecs.sipfoundry.org/temp/sipXecs/main/FC/8/i386/RPM/ You can check for yourself which version is on the server. What yum error are you getting when trying to install this RPM? > > > No it has not been updated on the server. It needs to be updated; > however in the interim, you can use the older version (sipxconfig does > not rely on the changes from the last version) or manually create a > link to the newer jar version. Damian can update the RPM as I am not > sure how to do that. The bigger question is -- why *both* the RPM and > the sipxcommons directory containing the same jar? > > Ranga sipXconfig is going to use RPM version of sipx-jain I suggest that all other java applications that run on Linux switch to RPM version. Same apply to javadns and other java jars. As I said many times here I consider sipXcommons practice of checking in JARs "a bad thing". See this: http://thread.gmane.org/gmane.comp.voip.sipx.devel/10221 I cannot update jain-sip until build servers are back in order: since otherwise I cannot trigger lib builds. BTW: updating RPM is trivial http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&revision=13180 D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
