[mythtv-users] FC4: 0.18 ---> 0.19

[Axel Thimm]

On Wed, Feb 22, 2006 at 02:00:45PM -0500, Boleslaw Ciesielski wrote:
> Axel Thimm wrote:
> >> Sorry for the misinformation.  Shouldn't yum resolve the dependencies 
> >> though?
> > 
> > No, it would only do so for missing packages (e.g. a new dependency
> > introduced by the latest mythtv package), not for such that exist, but
> > are outdated.
> 
> Is this really true? Someone mentioned using:
> 
> yum upgrade myth\* --enablerepo=atrpms
> 
> This command *will* update libmyth if one of the new myth* packages 
> requires the new version. And if it doesn't then it means that the new 
> myth* rpms do not specify the dependency on the new libmyth, which may 
> be the real issue here.

No, the real issue is using a depsolver to cut parts of a repo away,
it's not only myth* and libmyth but the other 40-50 dependencies that
stem from other src.rpms.

Having a partial repo config like the line above is not a supported
configuration by neither a 3rd party repo, nor any vendor
repos. Suggesting static dependencies as a workaround is an
unmaintainable task, and every upgrade of libfoo would require bumping
up the versioned dependency in all dependent packages and a forced
mass rebuild.

> For example:
> 
> $ rpm -q --requires mythtv-backend
> [...]
> libmythtv-0.19.so.0
> [...]

> which does not list
> 
> libmyth = 0.19-121.rhfc4.at

It effectively lists libmyth = 0.19.

And it also doesn't list glibc = 2.3.5-10.3, qt = 3.3.4-15.4,
libraw1394 = 1.2.0-1_6.rhfc4.at and so on.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-users/attachments/20060222/ff1ea589/attachment.pgp