I made a clean install, keeping my home partition. My existing Calendar data was not displayed. The calendar was empty. This could be because I had been using the version 1.0b3pre, packaged by Mandriva (and also, I believe by Fedora) and the version packaged for Mageia is 1.0b2. (Installing the 1.0b2 xpi file from Mozilla produces the same empty calendar.) I removed the Mageia lightning package and installed the latest Mandriva package and all of my Calendar data is now properly displayed. (I thought that I had tested this during development, but it's possible that I overlooked testing with my own data.)
I couldn't find 1.0b3pre anywhere; I looked at the Fedora spec and they 1.0b3pre actually comes from the thunderbird tarball itself, upstream lightning don't seem to release a separate tarball.... I think Fedora are doing the right thing, not building lightning from the thunderbird src.rpm, but from a separate thunderbird-lihgtning src.rpm (using the same tarball); only caveat is 1.0b3pre doesn't have any localisation, only en_US AFAICS. The options are: - provide 1.0b3pre with not localisation - stick with 1.0beta2 until 1.0b3* gets localisation packages (.jar)
Source RPM: (none) => mozilla-thunderbird-lightning
FWIW, I asked on IRC, it seemed to work fine for one guy there...
I'm satisfied with my present set-up, but would prefer not to use an "alien" package. (I have been unable to find an xpi file for 1.0b3pre.) I'll do some tests on my backup system (could be a week or two, before I get round to it) in case there's something I've missed. If no-one else has had this problem, then there may be something odd about my set-up.
Yes, the xpi file for 1.0b3pre can only be built from the thunderbird tarball itself (lightning upstream didn't release a new tarball...).
Assigning to maintainer now that our maintainers database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me.
CC: (none) => stormiAssignee: bugsquad => anssi.hannula
Assignee: anssi.hannula => doktor5000
As we want localisations, the only option i see so far would be to try with 1.0b5, as for 1.0b3 there is no source or .xpi file for the localisations available and for 1.0b4 no source is available. Will investigate.
Status: NEW => ASSIGNED
Do you have something to reproduce the behavior you described in your report?
ping?
ping? If noone responds, i'll close this as old.
Closing as OLD.
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD