Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#37866 - xfce4 orage archive date is wrong
Attached to Project:
Arch Linux
Opened by JW Purple (wakep) - Thursday, 21 November 2013, 17:40 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 30 November 2013, 18:30 GMT
Opened by JW Purple (wakep) - Thursday, 21 November 2013, 17:40 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Saturday, 30 November 2013, 18:30 GMT
|
DetailsDescription:
xfce4's orage calendar archive function constructs the date wrong, making archiving useless. Additional info: * package version(s) 4.8.4-2 * config and/or log files etc. From ~/.xsession-errors: 11:23:57 ** Message: Orage **: Archiving threshold: 2 month(s) 11:23:57 ** Message: Orage **: Archiving events, which are older than: 0113-10-21 The orage version 4.8.4 code (ical-archive.c) shows tm_year += 1900; but it's not being done judging from the log output. Has the correct source been used in the build? Steps to reproduce: Run archive function. Check .xsession-errors and observe empty ~/.local/share/orage/orage_archive.ics. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Saturday, 30 November 2013, 18:30 GMT
Reason for closing: Upstream
Saturday, 30 November 2013, 18:30 GMT
Reason for closing: Upstream
Comment by Jelle van der Waa (jelly) -
Saturday, 23 November 2013, 13:11 GMT
Please report the bug upstream, this package is also orphan. Btw you could build it from source and check if the bug still exists.
Comment by JW Purple (wakep) -
Wednesday, 27 November 2013, 21:31 GMT
I built it from source, and it still has the problem. I'll submit the bug upstream.