Closed
Bug 127358
Opened 23 years ago
Closed 23 years ago
fast-update fails forever if error occurs in security
Categories
(SeaMonkey :: Build Config, defect, P2)
SeaMonkey
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0
People
(Reporter: jesup, Assigned: netscape)
Details
Attachments
(1 file)
595 bytes,
patch
|
netscape
:
review+
|
Details | Diff | Splinter Review |
If an error occurs in a fast-update of security, the file
.fast_update-failed.tmp is created in the directory _above_ mozilla. Since this
isn't deleted, from then on fast-update will fail when doing security.
Solution: delete the file in both directories, or when doing security use
"mozilla/.fast_update-failed.tmp" as the error file (so there's only one file).
Patch to be attached for the second variation (one file in the mozilla directory).
Reporter | ||
Comment 1•23 years ago
|
||
Trivial patch to correct this. Didn't look at Windows makefiles; it's possible
they have a similar problem.
Reporter | ||
Comment 2•23 years ago
|
||
Very trivial patch, very safe. Tested. I'd suggest 0.9.9, but there's no need
to have the patch, it's merely a would-be-nice (I'd been unable to use
fast-update for months on one system and finally decided to find out why).
Keywords: mozilla1.0,
patch
Assignee | ||
Updated•23 years ago
|
Priority: -- → P2
Target Milestone: --- → mozilla1.0
Reporter | ||
Comment 4•23 years ago
|
||
seawood - I can check this is if you like. (We seem to have an a= without r/sr,
though)
Assignee | ||
Comment 5•23 years ago
|
||
Comment on attachment 71010 [details] [diff] [review]
client.mk patch
r=cls
Attachment #71010 -
Flags: review+
Assignee | ||
Comment 6•23 years ago
|
||
Patch checked in.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•