canmove, Confirmed users
2,850
edits
CIDuty/Reconfigs: Difference between revisions
no edit summary
ChrisCooper (talk | contribs) |
ChrisCooper (talk | contribs) No edit summary |
||
| Line 39: | Line 39: | ||
The script will also attempt to update IRC with reconfig status. To do so, it uses a minimal bash IRC client called [http://tools.suckless.org/ii/ ii]. You can [http://tools.suckless.org/ii/ download ii from their website], or install it via a package manager (e.g. port install ii). Updating irc is non-fatal, but make sure ''ii'' is in your PATH if you want it to work. | The script will also attempt to update IRC with reconfig status. To do so, it uses a minimal bash IRC client called [http://tools.suckless.org/ii/ ii]. You can [http://tools.suckless.org/ii/ download ii from their website], or install it via a package manager (e.g. port install ii). Updating irc is non-fatal, but make sure ''ii'' is in your PATH if you want it to work. | ||
= Help, my reconfig failed! = | |||
Assuming you're using the end_to_end_reconfig.sh script, you can resume after fixing the error. Errors and exit state can be found in the manage_masters-##########.log which is created in /tmp/reconfig by default. | |||
Running the script again will yield the following menu: | |||
* Please select one of the following options: | |||
1) Continue with existing reconfig (e.g. if you have resolved a merge conflict) | |||
2) Delete saved state for existing reconfig, and start from fresh | |||
3) Abort and exit reconfig process | |||
#1 is usually the best option here, especially if the hg operations actually succeeded during the previous attempt. This way the wiki/bugzilla updates will still be properly applied. | |||
= Help, my reconfig is stuck! = | = Help, my reconfig is stuck! = | ||