mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

This boils down to debian library policy or so.  The ABI of the library
is supposed to be in the binary package's name.  This is so a package
can build against a particular library version if both are in the
archive.  It's less important for myth* since everything that links to
it is mythtv or mythplugins, but it's still part of policy.

There shouldn't be any scenarios where both being installed causes a
conflict.  If there are some specifics, we'll need to find out what they
are.

-- 
libmyth causes issues for upgraders
https://bugs.launchpad.net/bugs/675358
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.

Status in Mythbuntu, Ubuntu derivative focused upon MythTV: Opinion

Bug description:
libmyth seems to cause problems in a few different ways.

1) Since the name of the package is libmyth-0.23.0, when users want to upgrade to 0.24, they need to either do a dist-upgrade or remove libmyth-0.23.0 first. Otherwise they get a warning that they can only do a partial upgrade (which isn't entirely true). 

2) In some instances, libmyth-0.23.0 remains installed (I think this may be fixed in newer builds). This causes issues with old stuff still being installed and causes conflicts.


Why is this package named with the 0.23.0 on it unlike any of the other mythtv packages? Why don't we name it simply 'libmyth' and then it won't be a hassle to upgrade to the new version?