media-plugins/mythplugins-0.27.6_p20160318 depends on dev-qt/qtwebkit:4 which is ancient and will never see any security updates. I see that there's 0.28 which is ported but has been masked for a long time. Maybe it's time to drop the mask and remove old?
Richard, it has been masked for over a year, was it tested extensively enough? ;)
I haven't touched it in a year. I suspect it is fine, but I am no longer maintaining MythTV. Unfortunately I lost my main Myth frontend and decided to dismantle things. I don't mind contributing what I know, but I'm not in much of a position to test. The biggest issue was with the main client, not the plugins. The client/backend themselves were basically fine but I'm not sure the init.d scripts and systemd units were in an ideal state, with all the changes to the logging/etc. It is probably safe to unmask to testing and solicit feedback and fixes from users. Between config options and command line options there are multiple ways to get the logging to work (separate daemon vs built-in), and upstream has changed direction on this more than once. I'm pretty sure the systemd units were usable but didn't get a chance to test on openrc. Whether the default suits an individual user is probably a matter of personal taste.
Considering the maintainer-needed state and unresolved other bugs with 0.27, maybe this old version should be dropped without stabilising newer if no other maintainer steps up during the next few weeks.
(In reply to Andreas Sturmlechner from comment #3) > Considering the maintainer-needed state and unresolved other bugs with 0.27, > maybe this old version should be dropped without stabilising newer if no > other maintainer steps up during the next few weeks. I think that is a good plan. 0.28 was working fairly well when I last had it running not long after it was introduced. The QT issues are a good reason to retire the older versions. The main issues with 0.28 are probably around the init.d scripts and logging/etc (they keep changing how logging works and there are a few ways it can be configured). I suspect users will step up with patches if they're needed, and if they're not stepping up it probably is working well enough for them. Of course, sooner or later 0.28 will run into issues...
Rich0: Do you think 0.28 is ready to be finally unmasked?
(In reply to Pacho Ramos from comment #5) > Rich0: Do you think 0.28 is ready to be finally unmasked? 0.28 was working fairly well when I last had it running not long after it was introduced. The QT issues are a good reason to retire the older versions. The main issues with 0.28 are probably around the init.d scripts and logging/etc (they keep changing how logging works and there are a few ways it can be configured). I suspect users will step up with patches if they're needed, and if they're not stepping up it probably is working well enough for them. :)
Nice, then, I guess we could unmask it finally as, otherwise, people will get a bit upset if we force them to use a hardmasked version (while forcing them to move to "testing" looks probably more reasonable)
(In reply to Pacho Ramos from comment #7) > Nice, then, I guess we could unmask it finally as, otherwise, people will > get a bit upset if we force them to use a hardmasked version (while forcing > them to move to "testing" looks probably more reasonable) Agree. It is "testing" after all, and I suspect most could figure out how to tweak it and we'll get a bug report with useful feedback. The practical alternatives aren't going to make people any happier.
(In reply to Pacho Ramos from comment #5) > Rich0: Do you think 0.28 is ready to be finally unmasked? That was already done together with a 0.28.1 version bump.
Nice, thanks
It's been almost 3 weeks, can we drop 0.27?
(In reply to Andreas Sturmlechner from comment #11) > It's been almost 3 weeks, can we drop 0.27? Keep in mind this package isn't maintained, so nobody really exists to give permission for this. IMO you can go ahead - we generally don't let unmaintained packages hold up progress and users have an upgrade path.
Thanks, 0.27 removed from tree.
