[mythtv-users] updated Myth, but libraries not updated

[Jerome Yuzyk]

On Sunday 14 October 2007 17:52, Axel Thimm wrote:
> On Sun, Oct 14, 2007 at 05:10:13PM -0600, Jerome Yuzyk wrote:
> > On Sunday 14 October 2007 17:06, Brad DerManouelian wrote:
> > > On Oct 14, 2007, at 4:02 PM, Jerome Yuzyk wrote:
> > > > On Sunday 14 October 2007 14:21, Axel Thimm wrote:
> > > >> On Wed, Oct 10, 2007 at 03:44:06PM -0600, Jerome Yuzyk wrote:
> > > >>> I saw some updates to Myth 0.20.2(-166.fc7) on ATrpms so I used
> > > >>> Yum to
> > > >>> get them. However, I noticed that none of the newer matching libs
> > > >>> (libmyth and others) were pulled. Is this normal?
> > > >>
> > > >> No, did you use the plain-old yum update command for doing the
> > > >> update?
> > > >
> > > > I did a   yum update myth*   which has always worked in the past.
> > > > It pulled
> > > > myth* but none of the libs that I assume they would be needing.
> > > > Everything
> > > > worsk fine though.
> > >
> > > You mean it didn't update stuff like libmyth which does not match the
> > > pattern of myth* that you told it to update?
> >
> > Well, I figured that if there was a myth-123 and a libmyth-123 that
> > updating myth-123 would pull libmyth-123. Yum has always handled those
> > kinds of dependencies automatically.
>
> Actually it never did, and the yum update myth* has been the source of
> 1001 endless bug chasing crusades.

So this implies that Myth libs are optional, and can fall behind the myth* 
packages? Does dependecy-resolution eventually force a catch-up?

> plain-ole yum update is your friend.

... except when non-Myth updates outnumber Myth updates, like for lazybones 
like me that only check every month or so.