Remove limit from 1256 DB update.

The limit, coupled with a post-0.24 DB upgrade, could cause a key
binding collision on exactly one host (and not more than one host) in
the MythTV system when upgrading from a 0.23 schema version to post 0.24
schema version.  The collision could only occur in a multi-host MythTV
system, could not occur on the host performing the DB upgrade(s), and
could only occur on a host that had been used as a frontend with 0.23
but never ran either mythfrontend or mythtv-setup from 0.24.

More specifically, you would have had to have a schema version from
before May 10, 2010 on master (such as a 0.23 schema version) and
upgraded to a schema version from after July 21, 2011 on master (not in
any released version, but will be in 0.25) without ever running a
version of mythtv from between those 2 dates.  Even then, the collision
is unlikely to occur because of how the data is returned.

For users running master, any affected host's mythfrontend or
mythtv-setup will show the warning:

2012-03-06 09:08:55.862679 W  Key Esc is bound to multiple actions in
context Main Menu.

The collision can be fixed by manually removing or changing the binding
on the action you don't want in mythfrontend's Utilities/Setup|Edit Keys
in the Main Menu context on the affected host.

For users running 0.24 versions, there is no collision, and simply
running mythfrontend (or mythtv-setup, but no need to run both) from
0.24-fixes on your frontend hosts will prevent one from occurring when
you upgrade to 0.25, so you have nothing to worry about/nothing to fix.

Refs #10403.
Prompt on exit if configuration is ambiguous.

Make EXITPROMPT take precedence on systems where it is mapped to the
same key as EXIT.

Fixes #10403.
Use MythDownloadManger for downloading icons in mythfilldatabase. HttpComms doesn't support SSL.
Revert to using Any address.

This bypasses the startup IP address selector in ServerPool, instead
listening on Any and AnyIPv6.  This leaves the ServerPool itself in
place to handle systems with the bindv6only sysctl set.  The behavior is
being reverted over concerns with systems that may have not completed
network configuration by the time MythTV starts, or would otherwise
change network behavior during normal operation.
Fix sub-folder node not displaying artwork of the first child in the tree view. This was working in all the other views but not in the tree view.
Revert "Revert to using Any address."

This reverts commit 23f3e6ff07fc80d4c4f95729c3f782707a326eb7.

It seems when net.ipv6.bindv6only is disabled, you cannot listen on both
QHostAddress::Any and QHostAddress::AnyIPv6 without the second failing,
meaning we would have to check to see if that flag is set and act
accordingly, putting us right back where we were a month ago.
MythMusic: Add the nodetype statetype to the default 4:3 playlist tree
Fix some DB locking issues on MySQL 5.5

affecting DB upgrades.
Require a reasonably current DB version on upgrade

This removes support for upgrading the database from very old versions
of MythTV (prior to 0.22).  We haven't made such updates for several
versions, but as the old upgrade code is affected by changes outside our
control (both changes to Qt framework/Qt-MySQL drivers and changes to
MySQL, itself), and because this ancient code is seldom tested with
current versions of external code/programs, we need to limit supported
upgrades to relatively recent upgrades that are testable/supportable.

Users using older versions of MythTV can attempt to upgrade their
existing databases by using intermediate versions of MythTV and attempt
to work through any issues they encounter (even posting questions to the
mythtv-users list).  However, they should understand that upgrading from
very old versions may not work due to things that have changed in the
years since the upgrade code was written and tested.
Add log messages missing from a couple of DB upgrades

Add log messages to those upgrades that used UpdateDBVersionNumber()
without explicitly providing a log message so that logs are more
accurate and users don't wonder why some numbers are skipped in upgrade.

(Note that these are not automatically output by UpdateDBVersionNumber()
because UpdateDBVersionNumber() is called after the update succeeds and
the log message should be output before it has started.)
Remove unnecessary comment.

We haven't historically deleted settings values that are no longer used
in code, and doing so isn't necessary, so remove this comment.
If the downloadable themes cache dir doesn't exist, force redownload.

This should fix an issue with the Theme Chooser sometimes showing
only locally installed themes by default forcing the user to manually
refresh the downloadable themes list via the popup menu.  If the
downloadable themes cache dir does not exist, we trigger a download
attempt automatically when entering the Theme Chooser.
Fix a couple of incorrect dtors

if (!m_blah)
    delete m_blah;

Not likely to do what you wanted, more likely to core dump when m_blah is NULL,
and leak the rest of the time.
Update python installer to properly remove installed scripts.
Correct --inversecut handling in mythtranscode.

This makes use of the boolean --inversecut option pull an external
cutlist of out --honorcutlist, rather than try to convert itself to a
string.
Fix RTP IPTV with multiple IPTV interfaces. 1ed419ad applied a fix for udp IPTV where more than one interface was available, it didn't apply the fix for rtp which uses the same socket code. Fixes #8767, Refs #3873
Add more detail to syslog logging

As a fair number of users are likely to be using syslog rather than file
logging, it has been requested by several people that the thread/file/line
type of detail be added to the syslog output as well.  Since this helps a lot
for debugging issues (when combined with the version string which identifies
the git checkout), I've added it now, as I'd forgotten several times in the
past.
Always default to focusing the 'Cancel' button in confirmation dialogs, confirmation dialogs are used when we want to prevent the user making a mistake which is still too easy to do if 'OK' is selected by default.
Revert de7acc4ef now that we no longer focus 'OK' but default in the delete confirmation dialog.
Change delete dialog text to read 'permanently delete'. Just to avoid any doubt.