Scott Lawrence wrote:
On Mon, 2010-04-26 at 11:25 +0300, Laurentiu Ceausescu wrote:
Hi all,
I'm working on http://track.sipfoundry.org/browse/XX-8179 "Wiki user
article: using a local RPM repository for Software Update".
In order to test and validate this article I installed sipX 4.2 from
ISO (4.2.0-018575), I made a set of new RPM packages from the latest
sources (4.2.1-018692)
and I created a local repository with those RPMs.
After that, using System/Software Updates page from the UI, I tried
to upgrade the system.
Although the Software Updates page looks like that sipX has been
updated correctly, after the system was restarted,
I saw that the upgrade process didn't work.
Looking in update.err.log (from /var/log/sipxpbx/update.err.log
directory), I found the cause:
*Error: Missing Dependency: sipxecs-doc >= 4.2.1 is needed by package
sipxecs*
*Error: Missing Dependency: sipxcommserverlib-doc = 4.2.0 is needed
by package sipxecs-doc*
Should I open a jira issue for that? Or we can suppose that the RPMs
are made correctly?
The RPMs were not made correctly - almost certainly because the system
you built them on did not have docbook installed; the configure script
detected that, and removed some build targets accordingly, but those
targets create rpms that you then did not have at installation time.
The fact that the UI did not detect that the upgrade was not
successful is a Critical bug.
I raised http://track.sipfoundry.org/browse/XX-8273 issue.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
