| Summary: | Incorrect Date shown on Akregator articles - Year 2106 | ||
|---|---|---|---|
| Product: | [Applications] akregator | Reporter: | Marshalleq <atoms> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | dariopnc, osterfeld, zahl |
| Priority: | NOR | ||
| Version First Reported In: | SVN | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Marshalleq
2008-07-14 08:04:33 UTC
this error occurs if time zone in pubDate is missing 13 Jul 2008 10:00 +0000 = correct 13 Jul 2008 10:00 = error in article.cpp : Article::Article::Private :
const time_t datePublished = article->datePublished();
article->datePublished() for RFC incorret date returns -1 (==2^32-1),
but from parseRFCDate:
time_t parseRFCDate(const QString& str)
{
time_t res = KDateTime::fromString(str, KDateTime::RFCDate).toTime_t();
return res != -1 ? res : 0;
}
it should not return -1 value
I've searched around this bug and (for now) found this : parseRFCDate checks result for time_t(-1)=64bit (at least on my computer), but KDateTime... returned uint32_t(-1), so result is: return res != 4294967295 ? res : 0; Conclusion: it's not akregator's bug, it's kdepim's bug *** Bug 156370 has been marked as a duplicate of this bug. *** Seems related to bug #150648. Is the above the beginnings of a patch? :) If you submit one to the mailing list, I'm sure they'd love it. Thanks! I've already filled kdepimlib's bug with patch - 166721 So courtesy of bug #166721, this can be closed? Thanks! And bug #150648? *** This bug has been marked as a duplicate of bug 166721 *** |