Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 134835 - Re-add mythtv-0.18.1 to CVS
Summary: Re-add mythtv-0.18.1 to CVS
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Other
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 138902 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-05-29 15:22 UTC by David Grant
Modified: 2006-07-02 13:20 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Grant 2006-05-29 15:22:09 UTC
I don't see the reason for removing mythtv-0.18.1 from CVS so soon (or at all). It is still a fairly current release (May 16, 2005) and functionality-wise, 0.19 is not much different from 0.18 anyways (http://www.mythtv.org/wiki/index.php/Release_Notes_-_0.19). I had problems with 0.19 (it worked for a while, then some upgrade of other packages caused it to segfault on start) and it looks like others have had problems with it as well (3 open bugs right now in gentoo).

I don't want to have to rely on a binary package by running quickpkg (but I will anyways) and I don't want to have to fetch stuff out of the CVS Attic (done it before, it's annoying). I don't see what else I can do, to get rid of this error:

emerge: there are no ebuilds to satisfy "=media-tv/mythtv-0.18.1*"

If there is some strong reason why gentoo devs can't maintain it, then just hard-mask it or something. Otherwise, what was the reason for removing it in the first place? Look at the kernels, we have: 2.4.31-r1 2.4.32-r3 2.4.32-r4 still living in the tree. Why two 2.4.32* versions? Why the 2.4.31 version? Who knows, and who really cares? So why not 0.18.1. What is the good reason to NOT have it?

(jakub moc, please don't close this bug. Assign to relevant person please).
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-05-29 15:29:57 UTC
Removed because of security bug, not coming back. See Bug 115760 and Bug 123066.
Comment 2 Harald van Dijk (RETIRED) gentoo-dev 2006-05-29 15:48:59 UTC
From the second bug you referenced:

------- Comment #6 From Doug Goldstein 2006-03-13 21:33 PST  [reply] -------  
Well now that I know what the flaw is... it turns out that MythTV doesn't use
the ffmpeg code in question....
Comment 3 David Grant 2006-05-29 16:34:45 UTC
Great, maybe there's a chance of 0.18 coming back then?
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2006-07-02 12:55:27 UTC
*** Bug 138902 has been marked as a duplicate of this bug. ***
Comment 5 Mark Knecht 2006-07-02 13:20:56 UTC
Actually removing 0.18 is a problem for those of us who run networks for MythTV boxes since 0.18 & 0.19 are not compatible with each other. There's no easy way that I know of to move up other than taking all the 0.18 stuff down, then building and debugging 0.19. Big, big job for a bug that probably cannot happen on my network anyway...

I cannot see where ffmpeg is even at issue on my network but maybe I'm missing something. Here's what I get on the last machine I have which hasn't had the database updated yet:

myth14 ~ # emerge -pve =media-tv/mythtv-0.18.1-r1 | grep mpeg
myth14 ~ #

Anyway, one more vote for bringing it back even though these arbitray 'WONTFIX' designations never seem to resolve in my favor....