| Summary: | mozilla-thunderbird-lightning fails to display existing calendar data | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | James Kerr <jim> |
| Component: | RPM Packages | Assignee: | Florian Hubold <doktor5000> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | stormi-mageia |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mozilla-thunderbird-lightning | CVE: | |
| Status comment: | |||
|
Description
James Kerr
2011-06-08 17:33:35 CEST
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) =>
stormi
Anssi Hannula
2011-10-01 13:06:54 CEST
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? ping? If noone responds, i'll close this as old. Closing as OLD. Status:
ASSIGNED =>
RESOLVED |