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?
Laurentiu
------------------------------------------------------------------------
_______________________________________________
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/
Hi,
The reason why the Software Updates page shows that the system was
successfully updated and in fact it didn't update, is that the page only
displays the installation log(update.output.log) and don't check if
there were any errors on installation process. A solution could be
checking the update.err.log file for any reported errors and inform the
user about that. Also, if there are any installation errors, the servers
shouldn't restart.
In the current situation, the user is confused because although the
update went well(because that's what the UI displayed) the server wasn't
updated at all. He can understand what really happened only after
reading the update logs. Considering the above, I believe we should open
a Jira task for this.
Cosmin.
_______________________________________________
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/
