http://bugs.gpodder.org/show_bug.cgi?id=353
--- Comment #3 from Sebastian Krause <[email protected]> 2009-02-20 00:04:30 --- I just used git-biscet to narrow down the bad commit. Here is the result: 2fcbabfadb2207888b77a4dac4111395ba229157 is first bad commit commit 2fcbabfadb2207888b77a4dac4111395ba229157 Author: Romain Janvier <[email protected]> Date: Sat Feb 14 16:31:53 2009 +0100 Avoid problems with wrong timestamps (bug 352) I've search a little and it seems that it comes from podcasts that are on my iPod and that don't have a released date. I've just attached my version of util.py. I've added a try/except, so if the timestamp is not None, but is incorrect, the exception is catched and None is returned. It works for me. :040000 040000 7a7184198c8205837578a0db9e2933bd1627c150 fbf9e903897ec617afd0087c3616a322d5cf1284 M src -- Configure bugmail: http://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
