On Fri, Mar 16, 2012 at 7:09 PM, Clayton Gooding
<clayton.good...@gmail.com> wrote:
> Ok great, thank you.  I will see if I can schedule a backup and maintenance
> window in order to apply the update and see if that corrects it.  I guess
> our update must have been done prior to the last major maintenance window we
> did.  Could you explain how you were able to determine the build date from
> the files below?  Can it be found by searching the wiki or forums or is this
> just tribal knowledge?
>

Sure, from sipxconfig-4.4.0-326.gd0202 you take the last part -gd0202
- and remove g, so you have d0202. This would be the beginning of the
last commit hash included in that rpm, so if you go to the 4.4 commits
(https://github.com/dhubler/sipxecs/commits/release-4.4) and search
for d0202 you will find it on the 2nd page:
https://github.com/dhubler/sipxecs/commits/release-4.4?page=2

commit:
https://github.com/dhubler/sipxecs/commit/d020291c532cc40aa193c21ae92a4d0bb288fbab

George

George
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to