http://bugs.gpodder.org/show_bug.cgi?id=12


Justin Forest <[EMAIL PROTECTED]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #89 is|0                           |1
           obsolete|                            |




--- Comment #49 from Justin Forest <[EMAIL PROTECTED]>  2008-06-26 21:31:10 ---
Created an attachment (id=90)
 --> (http://bugs.gpodder.org/attachment.cgi?id=90)
updated patch, fixed import/upgrade new status

Thomas, all episodes are new when they are added.  Very simple: new = not
downloaded, not deleted and not played.  So an episode needs to be explicitly
downloaded, deleted or played to be not new.  Or these flags need to be
imported from history.

I updated the channel/episode update code a little.  Tested these scenarios:

1. In a channel with 5 episodes I downloaded one (in the middle).  Deleted
   all episodes using the SQLite console and updated.  Four episodes were
   new, one detected as existing.  OK, because this is a regular update
   and it shows that backdated episodes are detected as new.
2. Deleted the channel completely (left the files) and added it back.  Only
   the two episodes above the downloaded one were new.  This works much
   like the upgrade process does, except that during an upgrade, after
   the channel was added, some _more_ episodes are marked as old, according
   to history-played.txt.  So, OK.
3. Deleted the channel with enclosures.  Added it back.
   One new episode.  OK
4. Deleted the downloaded file from fs, stargted gPodder.  The file is
   back in the list, marked as downloaded+new, there is "Resurrected
   episode {URL}" in the log.

Keep reporting. ;)


-- 
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

Reply via email to