Closed Bug 559184 Opened 15 years ago Closed 14 years ago

[MacOSX] 'unify' reports 'chrome.manifest' mismatch

Categories

(Calendar :: Build Config, defect)

Product:
Calendar
Component:
Build Config
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: sgautherie, Unassigned)

References

Details

{ http://tinderbox.mozilla.org/showlog.cgi?log=Calendar1.0/1271186385.1271187239.27476.gz MacOSX 10.5 comm-1.9.1 sunbird build on 2010/04/13 12:19:45 /builds/buildbot/comm-1.9.1-sunbird-macosx/build/mozilla/build/macosx/universal/unify: copyIfIdenticalWhenSorted: compare: while comparing: objdir-tb/ppc/mozilla/dist/sunbird/Calendar.app/Contents/MacOS/extensions/\{972ce4c6-7e08-4474-a285-3208198ce6fd\}/chrome.manifest, objdir-tb/i386/mozilla/dist/sunbird/Calendar.app/Contents/MacOS/extensions/\{972ce4c6-7e08-4474-a285-3208198ce6fd\}/chrome.manifest make[1]: *** [postflight_all] Error 1 }
(In reply to comment #1) Sorry, that's currently irrelevant for Calendar1.0: see bug 526817 comment 13.
Bug 526817 relanded ... but tinderboxes are red atm.
Serge, is this problem resolved?
http://tinderbox.mozilla.org/showlog.cgi?log=Calendar1.0/1286543127.1286544793.20790.gz MacOSX 10.5 comm-1.9.2 lightning build on 2010/10/08 06:05:27 http://tinderbox.mozilla.org/showlog.cgi?log=Calendar1.0/1286618407.1286648357.21714.gz MacOSX 10.5 comm-1.9.2 lightning nightly on 2010/10/09 03:00:07 were already green. http://tinderbox.mozilla.org/showlog.cgi?log=Sunbird/1286544707.1286545685.24675.gz MacOSX 10.5 comm-central lightning build on 2010/10/08 06:31:47 http://tinderbox.mozilla.org/showlog.cgi?log=Sunbird/1286618400.1286659078.29419.gz MacOSX 10.5 comm-central lightning nightly on 2010/10/09 03:00:00 were red (with various errors) until "2010-11-04 19:14:14 +0000": http://hg.mozilla.org/comm-central/rev/67033a790980 Too late to know what/when fixed it.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
(In reply to comment #5) > Too late to know what/when fixed it. PS: I think it should be comment 3, but that was 6,5 months ago...
You need to log in before you can comment on or make changes to this bug.