This adds a non-interactive mode that prints out the list and exists,
triggered by running the script outside of a terminal.
This also adds a new type, 'misplaced', indicating recordings that were
found, but on a backend other than that listed in the backend. This
is informative only, and does not support any actions being performed on
the recordings in question.
This adds another type of recording for find_orphans.py to handle. If a
recording is in the process of deletion when the backend is terminated,
the file and database entry will still exist, but MythTV will ignore any
pre-existing entries with the 'deletepending' flag set. This now deletes
any such recordings over a certain age.
This alteres the metadata selection strategy in mythvidexport.py
following the availability of more complete metadata with the
`mythmetadatalookup` utility. If inetref has been set on the recording,
it will now pull the metadata directly from the recording, rather than
interfacing with the external grabber scripts. The previously disabled
--listingonly option now works again, forcing this behavior.
WARNING:
The pull of metadata from the recording is performed using the
exportMetadata method from the python bindings, which is currently
incomplete. Exports of recordings that have been updated using
`mythmetadatalookup` performed using the --listingonly option WILL NOT
WORK until that method has been updated.
The objects for handling markup data in Video objects are created when
the video entry is pushed to the database. The metadata import routines
require a database entry to operate against, while the filename
generator requires the import routine to be run before a filename can be
specified. This in turn requires a dummy entry be created with a blank
filename, which results in a broken markup handler.
This fix manually corrects the markup handler object after a filename
has been chosen, to map it to the correct video.
Fix from CiaranG
Adds two options (--safe and --really-safe) to be used to confirm a
correct export of the source material. --safe just checks resultant
filesize, while --really-safe performance a (lengthy) SHA1 comparison of
source and destination. The --delete option enforces the use of at least
--safe.
Ciaran Gultnieks
Raymond Wagner