From <http://forums.mozillazine.org/viewtopic.php?p=12954197#p12954197> > I just updated my thunder to 23.0 and lightning to 2.5 and lightning died. > just updated the lines in libical.manifest about the binary component to look like the ones in components.manifest > On linux it would look like this > --- libical.manifest.bak 2013-07-02 16:35:23.000000000 -0300 > +++ libical.manifest 2013-07-04 17:51:35.423682575 -0300 > @@ -1,2 +1,3 @@ > -binary-component libcalbasecomps.so > +binary-component Linux_x86-gcc3/libcalbasecomps.so abi=Linux_x86-gcc3 > +binary-component Linux_x86_64-gcc3/libcalbasecomps.so abi=Linux_x86_64-gcc3 > interfaces caldatetime_libical.xpt
Huh? A problem with the recent patch or was it maybe not taken into account? Looks like I will have to do a b2 for this.
Maybe there is a separate build script that creates the unified beta or release builds? The Linux nightly builds are not unified but a separate 32-bit build and 64-bit build is created and uploaded to ftp.mozilla.org.
Oh right, sorry. Indeed there is a manual script that does this, looks like I either forgot to call it on the final xpi or its not updated to the libical manifest. Should be easy to do a b2 in that case.
Is the manual build script located in the calendar repository? Is yes: where? If no: why not?
Created attachment 772000 [details] fix_linux_xpi.sh (In reply to Stefan Sitter from comment #4) > Is the manual build script located in the calendar repository? Is yes: > where? If no: why not? Its not in the calendar repository, as it was rather a quick hack to make it work. The ideal soultion would be to turn this into a buildbot step which the tb infra could trigger once both linux builds are done. I've attached the script for convenience with slight modifications which *should* make it work for libical.manifest.
Created attachment 772003 [details] Lightning 2.5b2 linux Do you have a linux box at hand to test this? Here is a fixed version, repackaged as 2.5b2.
Assignee: nobody → philipp
Status: NEW → ASSIGNED
Attachment #772003 - Flags: feedback?(ssitter)
The attached xpi seems to work fine (with admittedly light testing) on Ubuntu 12.04 64bit with a recent tbird daily: 24.0a1 (2013-06-18).
Comment on attachment 772003 [details] Lightning 2.5b2 linux f=jcv, thanks for testing. Will upload these to amo now.
Attachment #772003 - Flags: feedback?(ssitter) → feedback+
Uploaded to amo now, marking as FIXED https://addons.mozilla.org/en-US/developers/addon/lightning/versions/1472540
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.5
(In reply to John C. Vernaleo from comment #7) This should not be possible. Lightning 2.5 Beta requires Thunderbird 23 Beta and doesn't support Thunderbird 24 or Thunderbird 25.
(In reply to Stefan Sitter from comment #10) > (In reply to John C. Vernaleo from comment #7) > > This should not be possible. Lightning 2.5 Beta requires Thunderbird 23 Beta > and doesn't support Thunderbird 24 or Thunderbird 25. I just tried it again and it definitely lets me install from file and then after I restart tbird, I can open the calendar tab. I didn't try anything beyond that since I don't currenly have any calendars in my test profile (so it entirely possible that things don't work completely).
Hmm I just read the "works" bit, missed the version info. Possible that the builds are binary compatible by coincidence. John, it would be nice if you could test again with the beta build from the beta channel at http://www.mozilla.org/en-US/thunderbird/channel/ ?
I tried the attached xpi (2.5b2 linux) on my 32bit linux machine (ubuntu 12.04) using thunderbird from the beta channel (23.0) and it works. I tried moving around in the calendar, creating events, and a bunch of other little things and all seem good. I cannot try on my 64bit box since the binary in the beta channel does not work on 64bit (and I did not try to fool around with any of the 32bit compat libs).
Thanks, that should be fine. I'll consider this fixed until someone complains that its not working.
You need to log in before you can comment on or make changes to this bug.