I'm marking the bug as invalid. Turns out that mytharchive's importing
and exporting is version specific. See comment from mythtv.org below.
To anyone encountering the same problem that I did, I found that
temporarily changing the database recordedmarkup column name from data
to offset, and replacing offset="" entries in the mytharchive .xml files
with offset="NULL", allowed me to import the recordings properly to the
new version.
Regards,
David
This was the reply posted at MythTV:
MythArchive, and MythTV, in general, do not support importing data from
previous DB schema versions. You must import MythArchive native exports
(and restore mythconverg backups) into the same DB schema version from
which they were created. Therefore, exports from 0.21-fixes are not
compatible with 0.22 fixes.
The proper procedure to make sure the exported programs were brought
over after upgrade to 0.22-fixes would have been to import them into
0.21-fixes, then back up the database, then upgrade to 0.22-fixes and
let MythTV's database upgrade convert the data. If you have questions on
proper upgrade procedure, please ask for more information on the mythtv-
users list.
There is hope to one day make a real export format that's not version
specific, but at this point, it's just a feature request/item on some
TODO lists.
** Changed in: mythbuntu
Status: New => Invalid
** Changed in: mythbuntu
Assignee: (unassigned) => DJ Dallas (djdallas)
--
Mytharchive (myth 0.22 karmic) fails to import/export recordedmarkup
https://bugs.launchpad.net/bugs/486233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
