Closed
Bug 617188
Opened 14 years ago
Closed 14 years ago
updater parameters in update_verify should be changed according to the new syntax
Categories
(Release Engineering :: General, defect, P1)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: rail)
References
Details
Attachments
(3 files, 3 obsolete files)
3.32 KB,
patch
|
nthomas
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
3.05 KB,
patch
|
nthomas
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
2.79 KB,
patch
|
nthomas
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
bug 600777 changed command line parameters of updater(.exe) and added a mandatory apply-to-dir parameter. Full syntax is:
Usage: updater update-dir apply-to-dir [wait-pid [callback-working-dir callback-path args...]]
At the moment we call updater as
../../update/updater ../../update 0
It tries to chdir to "0" and fails.
Assignee | ||
Comment 1•14 years ago
|
||
Attachment #495705 -
Flags: review?(nrthomas)
Assignee | ||
Comment 2•14 years ago
|
||
Attachment #495706 -
Flags: review?(nrthomas)
Assignee | ||
Comment 3•14 years ago
|
||
Attachment #495707 -
Flags: review?(nrthomas)
Assignee | ||
Comment 4•14 years ago
|
||
Testing the patches in staging. So far verify.sh runs good.
Comment 5•14 years ago
|
||
I think I would have set it up as use_old_updater so that you can set the global 'use_new_updater': True, with False on 1.9.1 and 1.9.2, and we don't have to pass --new-updater for future releases. Do we have time to do that ?
Assignee | ||
Comment 6•14 years ago
|
||
(In reply to comment #5)
> I think I would have set it up as use_old_updater so that you can set the
> global 'use_new_updater': True, with False on 1.9.1 and 1.9.2, and we don't
> have to pass --new-updater for future releases. Do we have time to do that ?
Sure. I'll update the patches today.
Assignee | ||
Comment 7•14 years ago
|
||
Attachment #495705 -
Attachment is obsolete: true
Attachment #495808 -
Flags: review?(nrthomas)
Attachment #495705 -
Flags: review?(nrthomas)
Assignee | ||
Comment 8•14 years ago
|
||
Attachment #495706 -
Attachment is obsolete: true
Attachment #495809 -
Flags: review?(nrthomas)
Attachment #495706 -
Flags: review?(nrthomas)
Assignee | ||
Comment 9•14 years ago
|
||
Attachment #495707 -
Attachment is obsolete: true
Attachment #495810 -
Flags: review?(nrthomas)
Attachment #495707 -
Flags: review?(nrthomas)
Updated•14 years ago
|
Attachment #495808 -
Flags: review?(nrthomas) → review+
Updated•14 years ago
|
Attachment #495809 -
Flags: review?(nrthomas) → review+
Comment 10•14 years ago
|
||
Comment on attachment 495810 [details] [diff] [review]
configs
>diff --git a/mozilla/config.py b/mozilla/config.py
>+ # Bug 617188
>+ 'use_old_updater': False,
Nit: The comment isn't necessary.
Please let the Thunderbird and SeaMonkey guys know about this change in case they're using the 0.8.0 automation and/or it will also be landing on the 0.7 branch.
Attachment #495810 -
Flags: review?(nrthomas) → review+
Assignee | ||
Comment 11•14 years ago
|
||
Comment on attachment 495808 [details] [diff] [review]
verify.sh: add --old-updater parameter
http://hg.mozilla.org/build/tools/rev/89131c300c1c
Attachment #495808 -
Flags: checked-in+
Assignee | ||
Comment 12•14 years ago
|
||
Comment on attachment 495809 [details] [diff] [review]
update UpdateVerifyFactory
http://hg.mozilla.org/build/buildbotcustom/rev/4febe8d47e48
Attachment #495809 -
Flags: checked-in+
Assignee | ||
Comment 13•14 years ago
|
||
Comment on attachment 495810 [details] [diff] [review]
configs
http://hg.mozilla.org/build/buildbot-configs/rev/8ebfd26e4a5e
Attachment #495810 -
Flags: checked-in+
Assignee | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•