Closed Bug 1070661 Opened 11 years ago Closed 11 years ago

Error setting access/modification time on application bundle

Categories

(Toolkit :: Application Update, defect)

All
macOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla35
Tracking Status
firefox34 --- fixed
firefox35 --- fixed

People

(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)

References

Details

Attachments

(1 file, 1 obsolete file)

Seen while updating on Oak
Attached patch patch rev1Splinter Review
Attachment #8492680 - Attachment is obsolete: true
Attachment #8492686 - Flags: review?(spohl.mozilla.bugs)
Comment on attachment 8492686 [details] [diff] [review] patch rev1 Review of attachment 8492686 [details] [diff] [review]: ----------------------------------------------------------------- Looks great, just this one question below. r=spohl ::: toolkit/mozapps/update/updater/updater.cpp @@ +2190,5 @@ > #ifdef XP_MACOSX > + // If the update was successful we need to update the timestamp on the > + // top-level Mac OS X bundle directory so that Mac OS X's Launch Services > + // picks up any major changes when the bundle is updated. > + if (!sStagedUpdate && utimes(gInstallDirPath, nullptr) != 0) { Could you walk me through the steps during a staged update? Will the timestamp be updated upon relaunch of Firefox?
Attachment #8492686 - Flags: review?(spohl.mozilla.bugs) → review+
The update is staged by copying the files in the bundle to the staging directory under ~/Library/caches/...etc. So, the stage copy doesn't need the timestamp updated. When an update is applied directly to the bundle is completed or when a replace request is completed that is when the bundle itself is updated and needs the timestamp updated.
Great, it was the replace request that I was wondering about. Thanks for clarifying!
Note: the fix won't be seen except when updating with a build that includes this fix so Sunday's nightly (e.g. on Monday) unless another nightly is generated.
I created an additional nightly yesterday and I verified the patch fixed this bug for the next nightly. No error and the bundle date timestamp had changed.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Landed on aurora in the Mac V2 signing combined patch in bug 1047584
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: