Bug 208677 - multimedia/mythtv missing dependents
Summary: multimedia/mythtv missing dependents
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Bernhard Froehlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-10 17:19 UTC by joeb1
Modified: 2016-07-18 15:48 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description joeb1 2016-04-10 17:19:00 UTC
package mythtv-0.25.5.20150616 is missing a lot of dependencies. 
With only mythtv installed on a fresh install of 10.3 the 
"pkg check -d -a" command shows this

mythtv has a missing dependency: lame
mythtv has a missing dependency: p5-xmltv
mythtv has a missing dependency: qt4-network
mythtv has a missing dependency: py27-urlgrabber
mythtv has a missing dependency: p5-LWP-UserAgent-Determined
mythtv has a missing dependency: p5-Net-UPnP
mythtv has a missing dependency: p5-DBD-mysql
mythtv has a missing dependency: qt4-mysql-plugin
mythtv has a missing dependency: qt4-l10n
mythtv has a missing dependency: p5-HTTP-Request-Params
mythtv has a missing dependency: py27-MySQLdb
mythtv has a missing dependency: p5-IO-Socket-INET6
mythtv has a missing dependency: qt4-script
mythtv has a missing dependency: qt4-sql
mythtv has a missing dependency: qt4-imageformats
mythtv has a missing dependency: wget
mythtv is missing a required shared library: libQtWebKit.so.4

This is after I installed xorg-server & mysql56-server which should also be included in the dependent list.

Also Lame does not have a package for it as of 4/10/2016

The mythtv-setup command should work after mythtv package is installed, that is the test to verify if port is good or not.
Comment 1 Bernhard Froehlich freebsd_committer freebsd_triage 2016-04-12 12:28:37 UTC
This is not a problem of the mythtv port. The port clearly lists lame and p5-xmltv and the others as dependencies.

https://svnweb.freebsd.org/ports/head/multimedia/mythtv/Makefile?revision=412348&view=markup

Your system seems to be either messed up or probably there were some issues with pkg.
Comment 2 joeb1 2016-04-12 15:15:43 UTC
On the other hand just looking at the makefile is not enough to say the problem is not reproducible. Did you really issue "pkg install mythtv" command and then issue "pkg check -d -a" command? Did you do this test on a freshly installed 10.3 system? Please explain how you tested for this problem? If it comes down to there is a problem with the "pkg" program then lets identify it as such and issue a bug report on it.
Comment 3 Bernhard Froehlich freebsd_committer freebsd_triage 2016-04-12 15:32:58 UTC
I am not saying that there is no problem. I just say that this is definitely not a mythtv ports issue. It can be a bug in various other places or it could be an issue with the last package set and might resolve itself with the next package set (after ~3 days).

If you want a more precise answer please spend some time to find the real cause. I will remove myself from that bug now since I was assigned to it as mythtv maintainer and leave it open for you to collect further information. Good luck!
Comment 4 John Marino freebsd_committer freebsd_triage 2016-07-18 15:03:40 UTC
Looks like a pkg user error.  A full reinstall of all prime ports would likely have fixed this 2 month-old report.  Closing due to lack of feedback (and lack of real issue).
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2016-07-18 15:31:01 UTC
Leave maintainer assigned
Comment 6 John Marino freebsd_committer freebsd_triage 2016-07-18 15:33:28 UTC
Koobs, decke intentionally removed himself from this PR (see after comment #3).  
Did you not realize that?  I think you should respect his wishes.
Comment 7 Kubilay Kocak freebsd_committer freebsd_triage 2016-07-18 15:43:33 UTC
To clarify last state change:

Issues should have a real assignee on close, in the event the issue is re-opened at a later date. I picked decke@ after checking he remained the current MAINTAINER for the port. Technically John could have also been the final Assignee (closer is responsible, whether fix-by-commit or other), but presumably MAINTAINER would want to be responsible/notified first if the issue is indeed re-opened, in this case after 3 months of no feedback.
Comment 8 John Marino freebsd_committer freebsd_triage 2016-07-18 15:48:16 UTC
Speaking for myself, if I understand that the price for housekeeping (closing obsoletely unclaimed bug reports) is that I become responsible for future comments/reopening of the bug report, I would be much less likely to perform the housecleaning.  It converts the report from a "community problem" to "my problem".

If that's the policy, so be it, but that will definitely curtail my activity even more.