A
dspaan wrote:I use standard. Here is the output.
My database server was SVN 3199 but the installer script decided to install 2829 for some reason which i now can see on my database server to so i have already ran the SVN update on the database server again to get it back to 3199.
...
U /usr/src/astguiclient/trunk/UPGRADE
U /usr/src/astguiclient/trunk/install.pl
Updated to revision 2829.
Skipped '>> /var/log/vicibox.log 2>> /var/log/vicibox.log'
Summary of updates:
Updated '/usr/src/astguiclient/trunk' to r2829.
Summary of conflicts:
Skipped paths: 1
....
There's going to be a reason it pulled that svn revision level, likely in the vicibox table somewhere.
How do i now get my dialer updated to SVN3199? Would this be sufficient:
Should work, except we perform each task on its own line to be sure to stop and fix each error if one occurs. While concatenated commands are cool when obfuscating code and while certain of success ... they aren't so cool when trying to be careful.
Also worthy of note: You'll want to include sample conf files in your execution or q/a section in case there have been changes. During any install.pl run, always include them and be prepared to re-edit any that have changed.