Opened 8 years ago
Closed 8 years ago
#12898 closed Bug Report - General (Fixed)
mythtv-frontend wont install
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | 0.28.1 |
Component: | MythTV - General | Version: | 0.28.0 |
Severity: | medium | Keywords: | mythtv-frontend mythtv-common |
Cc: | Ticket locked: | no |
Description
okay, so i have been using myth for years. now i am running mythbuntu for about 4 years and it has worked great until apparently this weekend. i did some myth updates and then got a message that some programs no longer used would be uninstalled. i think that is where this happened.
apprently i took off myth frontend and even worse is it will not re-install on mythbuntu 16.04. i get the error that says it needs mythtv-common but that will not be installed. well, of course it wont, it is already installed.
so i decided to try removing the backend and then putting it all back on and myth-frontend will not install with whatever version of myth-common that is on there even though they have the same version number. so i can get the backend on and running but the frontend will not install because of some issue with mythtv-common.
[code] # apt policy mythtv-frontend mythtv-frontend:
Installed: (none) Candidate: 2:0.28.0+fixes.20161010.7c91ab6-0ubuntu0mythbuntu2 Version table:
2:0.28.0+fixes.20161010.7c91ab6-0ubuntu0mythbuntu2 500
500 http://ppa.launchpad.net/mythbuntu/0.28/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status
2:0.28.0+fixes.20160413.15cf421-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages
# apt policy mythtv-common mythtv-common:
Installed: 2:0.28.0+fixes.20161010.7c91ab6-0ubuntu0mythbuntu2 Candidate: 2:0.28.0+fixes.20161010.7c91ab6-0ubuntu0mythbuntu2 Version table:
* 2:0.28.0+fixes.20161010.7c91ab6-0ubuntu0mythbuntu2 500
500 http://ppa.launchpad.net/mythbuntu/0.28/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status
2:0.28.0+fixes.20160413.15cf421-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu xenial/multiverse amd64 Packages
# apt-get install mythtv-frontend Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies:
mythtv-frontend : Depends: mythtv-common but it is not going to be installed
E: Unable to correct problems, you have held broken packages. code
...but again, mythtv-common is already installed and the latest version.
Change History (4)
comment:1 Changed 8 years ago by
Milestone: | unknown → 0.28.1 |
---|
comment:2 Changed 8 years ago by
Trying to install mythtv-frontend
on a clean Ubuntu 16.10 install, I am seeing the following.
$ sudo apt-get install mythtv-frontend Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. mythtv-frontend : Depends: transcode but it is not installable Recommends: python-imaging but it is not going to be installed E: Unable to correct problems, you have held broken packages.
It appears that the transcode
package is no longer available in the Ubuntu package repositories for 16.10:
$ apt-cache policy transcode transcode: Installed: (none) Candidate: (none) Version table:
comment:3 Changed 8 years ago by
I'm not on a *buntu box at present but I doubt that this is a real dependency. ISTR that it was used years ago, for requantisation, by mytharchive.
comment:4 Changed 8 years ago by
Resolution: | → Fixed |
---|---|
Status: | new → closed |
This was resolved with commit 8b156cce61a111f505dabfb7ecfdf1b4dfedeb33
A new version was built last night which should resolve this. Ironically it was building about when you created this ticket :-/
https://launchpad.net/~mythbuntu/+archive/ubuntu/fixes-building/+build/11017767
Regards Stuart