Closed
Bug 642723
Opened 14 years ago
Closed 14 years ago
Upgrade hg on Windows Slaves to hg 1.7.5
Categories
(SeaMonkey :: Release Engineering, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: Callek)
References
Details
This is to track upgrading Hg on windows slaves to 1.7.5
At the same time I will be enabling the share and purge extensions (though not enabling the use of them yet)
Assignee | ||
Comment 1•14 years ago
|
||
I remembered how to log into stage without needing to be on the seabld user, so doing this all from Administrator.
In MozillaBuild Shell:
* cd ~/../seabld
* scp -i .ssh/seabld_dsa seabld@stage-old.mozilla.org:packages/merc* ./
Following from windows cmd prompt in same dir:
* D:/mozilla-build/hg/unins000.exe /silent
* D:/mercurial/unins000.exe /silent
* msiexec /i "mercurial-1.7.5-x86.msi" /passive /log hg_install.log INSTALLDIR="D:\\mozilla-build\\hg"
* rm mercurial-1.7.5-x86.msi
* Manually create (overwrite if existing) .hgrc in "C:\Documents and Settings\seabld" with the file at http://hg.mozilla.org/build/opsi-package-sources/file/ebd7fd619599/mercurial-hgrc/CLIENT_DATA/hgrc
On all builders (probably due to not having actually _stopped_ the builds) I got "Some files cannot be removed..." for the mozilla-build unins000.exe run (manually deleted said files from the directory)
Done on cb-sea-win32-tbox cb-seamonkey-win32-{01,02,03}
Waiting to finish the DX install on cn-sea-qm-win2k3-01 to do this there (it has a slow connection to stage, so the DX pull is taking a while)
Assignee | ||
Comment 2•14 years ago
|
||
All slaves done
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•14 years ago
|
||
Whops... I accidentally saved (in notepad) as unicode, which added a BOM to the .hgrc I installed. And caused it to fail.
I also noticed, going through some of the slaves, that 2 out of the 5 slaves didn't save hgrc right (saved as .hgrc.txt due to me forgetting quotes in the save-as dialog) I fixed that, slaves should be green again.
You need to log in
before you can comment on or make changes to this bug.
Description
•