On Wed, 22 Aug 2007, Ernie Schroder wrote:
> On Wednesday 22 August 2007, a tiny voice compelled Bo ?rsted Andresen to
> write:
> > On Thursday 23 August 2007 00:47:23 Ernie Schroder wrote:
> > > [blocks B ? ? ] >media-video/ffmpeg-0.4.9_p20070525 (is blocking
> > > media-video/kino-1.0.0)
> > >
> > > Like you said, kino wants a later vervion than -0.4.9_p20070525 so it
> > > tries to pull ffmpeg-0.4.9_p20070616-r but the block persists.
> >
> > Mmm.. nope.. That's neither correct nor is it what Neil said. Kino 1.1.0
> > wants an earlier version of ffmpeg and hence later versions block it. To be
> > exact it needs a version between 0.4.9_p20061016 and 0.4.9_p20070525 (both
> > included).
> >
> 1.1.0???? OK I'll assume that you mean, in this case 1.0.0 What you say makes
> a certain amount of sense, but emerging 1.0.0 WANTS ffmpeg-0.4.9_p20070616-r
> and it appears to me that portage thinks 0.4.9_p20070525 is installed. If my
> perception is wrong here, one would think that portage would give the right
> info rather than trying to emerge an even later version than it needs for
> kino-1.0.0
The [B] line specifies what is not allowed, not what is wanted. Any
version later than 20070525 blocks kino 1.0.0, and such a version is being
chosen by emerge to satisfy kino's need for some version at least
20061016.
Portage doesn't think that ffmpeg-0.4.9_p20070525 *is* installed. It
thinks a later version *will be* installed, which is true, because it's in
the list of things which will be installed first. You should be able to
fix it by copying the blocking line into /etc/portage/package.mask, at
which point emerge will choose from the versions that don't conflict with
the verison of kino you want. (Alternatively, I think you could remove the
testing keyword from ffmpeg; you're getting a testing version of ffmpeg
and a non-testing version of kino, and they don't play well together, and
the ebuilds aren't being clever about it).
-Daniel
*This .sig left intentionally blank*
