Fixed in 1.3.3: * If-Modified-Since handling was broken * Updated documentation for customising hard-coded searches in page.html * Updated Windows installation docs (thanks Bo Berglund) * Handle rounding of seconds generating invalid date values * Handle 8-bit untranslateable messages from database properties * Fix scripts/roundup-reminder date calculation (sf bug 1649979) * Improved due_date and timelog customisation docs (sf bug 1625124)
I can confirm that just bumping the ebuild works fine. I did notice that the ebuild uses one ewarn line and only additional ewarn lines. I believe they should all be ewarn lines because the ewarn line is part of the whole message. As it is currently implemented I only get the ewarn line in the mail, which looks a bit odd and has no meaning. It may also be useful to add some USE flags such as mysql and sqlite to pull in the specific python packages so that roundup can make use of it.
In cvs. I also changed the einfo calls to ewarn. Thanks for the note. Actually the instructions are not really optimal. I ran into several problem when I tried to install it. I lack the time to fix the db dependencies or rewrite the instructions though. Might happen the next time I look at that ebuild.
