https://bugs.gpodder.org/show_bug.cgi?id=1186
Thomas Perl <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |CLOSED Resolution| |FIXED AssignedTo|[email protected] |[email protected] Target Milestone|--- |2.10 Severity|feature request |normal --- Comment #1 from Thomas Perl <[email protected]> 2010-10-30 00:13:32 BST --- Thank you for your bug report. I've looked at the feed and was able to reproduce the bug. It happens because gPodder limits the number of episodes per feed (max_episodes_per_feed setting) and the feed lists its entries in chronological order (old episode first), and therefore gPodder did not see new episodes, because they were always cut off. As a temporary workaround, you can set max_episodes_per_feed to a much higher value and update the feed (it might only work after the next update of the feed on the server, because gPodder does not check for new episodes if the feed on the server has not changed). The bug is fixed in the development repository by sorting the entries in the feed descending by their date and only then cutting off excessive episodes via max_episodes_per_feed. The fix will be part of the next gPodder release. Again, thanks for reporting this bug and making gPodder more robust for corner-case feeds :) Related commit: http://gpodder.org/commit/2ccd3f5d -- Configure bugmail: https://bugs.gpodder.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes. _______________________________________________ gPodder-Bugs mailing list [email protected] https://lists.berlios.de/mailman/listinfo/gpodder-bugs
