Closed
Bug 641422
Opened 14 years ago
Closed 14 years ago
wrong arg passed for current working directory
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
blocking2.0 | --- | Macaw+ |
status2.0 | --- | .1-fixed |
status1.9.2 | --- | unaffected |
status1.9.1 | --- | unaffected |
People
(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)
Details
Attachments
(1 file)
752 bytes,
patch
|
mossop
:
review+
dveditz
:
approval2.0+
|
Details | Diff | Splinter Review |
patch coming up.
![]() |
Assignee | |
Comment 1•14 years ago
|
||
Attachment #519073 -
Flags: review?(dtownsend)
![]() |
Assignee | |
Comment 2•14 years ago
|
||
The tests I am writing in bug 386760 will cover this... the changes are too extensive to reasonably write just a test for this.
Updated•14 years ago
|
Attachment #519073 -
Flags: review?(dtownsend) → review+
![]() |
Assignee | |
Updated•14 years ago
|
blocking2.0: --- → ?
![]() |
Assignee | |
Updated•14 years ago
|
status1.9.1:
--- → unaffected
status1.9.2:
--- → unaffected
Comment 3•14 years ago
|
||
I really hate it when people nominate things for blocking without explanation. Minusing until rationale comes through.
Updated•14 years ago
|
blocking2.0: ? → -
![]() |
Assignee | |
Comment 4•14 years ago
|
||
Sorry about that.
The problem statement is in the summary and is, "wrong arg passed for current working directory". What that means is that the current working directory will be incorrect after an update.
The fix is safe / simple in that the patch changes the code so the correct arg is passed for the current working directory.
blocking2.0: - → ?
![]() |
Assignee | |
Comment 5•14 years ago
|
||
I should also mention that I asked for blocking-2.0 to get .x approval
Comment 6•14 years ago
|
||
Ask for approval, for now that's done using the approval2.0 flag.
blocking2.0: ? → -
![]() |
Assignee | |
Comment 7•14 years ago
|
||
Thanks... just so you know, I did that for bug 635161 and the approval request was removed and the blocking-2.0=.x flag was granted. Might be a good thing to send out a notice to this affect if one hasn't been sent out already.
![]() |
Assignee | |
Updated•14 years ago
|
Attachment #519073 -
Flags: approval2.0?
Comment 8•14 years ago
|
||
Comment on attachment 519073 [details] [diff] [review]
patch rev1
Approved for mozilla2.0 repository, a=dveditz for release-drivers
Attachment #519073 -
Flags: approval2.0? → approval2.0+
Updated•14 years ago
|
![]() |
Assignee | |
Comment 9•14 years ago
|
||
Pushed to mozilla-2.0
http://hg.mozilla.org/releases/mozilla-2.0/rev/8f8f55913fd9
![]() |
Assignee | |
Comment 10•14 years ago
|
||
btw: I'll land this on mozilla-central Monday so leaving open. The tests in bug 386760 also test this bug.
![]() |
Assignee | |
Comment 11•14 years ago
|
||
Pushed to mozilla-central
http://hg.mozilla.org/mozilla-central/rev/3ac2e9681421
This is tested by the tests in bug 386760.
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Flags: in-litmus-
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•