Comment 62 for bug 727487
Revision history for this message
|
|
#62 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
(In reply to comment #31)
> (In reply to comment #30)
> > i'm guessing this can be RESOLVED INVALID (or RESOLVED DOWNSTREAM, if that
> > exists) since it's a downstream issue, right?
>
> How can it be a downstream issue if it's also present in Arch? AFAIK Arch uses
> vanilla KDE source code to build its packages, so this must be a KDE bug. I
> haven't tried in other distros since I've recently given up on kontact all
> together, but I can give it a shot in openSUSE 11.4 and report back.
Check in ABS if Arch's PKGBUILDs are building libgcal and akonadi-googledata against different sets of SSL libraries, just like Ubuntu is doing. Maybe it's a downstream issue in Arch also. I suggested originally the fix and I've always installed Akonadi Googledata that way; I supposed that to be normal.