public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Cc: John covici <covici@ccs.covici.com>
Subject: [gentoo-user] win32codecs / realcodecs / amd64codecs (and the -real USE flag)  was: Re: How do I fix multiple versions for the same package slot have been pulled
Date: Sun, 9 Nov 2008 05:01:52 +0000	[thread overview]
Message-ID: <244A2EC0-AE4E-4B37-8E91-8595BF26A227@stellar.eclipse.co.uk> (raw)
In-Reply-To: <18710.25193.638469.809440@ccs.covici.com>


On 9 Nov 2008, at 04:09, John covici wrote:

> In my latest update I have received the following message:
> !!! Multiple versions within a single package slot have been pulled
> !!! into the dependency graph, resulting in a slot conflict:
>
> media-libs/win32codecs:0
>
>  ('installed', '/', 'media-libs/win32codecs-20071007-r4', 'nomerge')
>  pulled in by
>    ('installed', '/', 'media-libs/realcodecs-11.0.1.1056', 'nomerge')
>    @world
>
>  ('ebuild', '/', 'media-libs/win32codecs-20071007-r4', 'merge')
>  pulled in by
>    ('ebuild', '/', 'media-video/vlc-0.9.6', 'merge')
>    ('ebuild', '/', 'media-video/mplayer-1.0_rc2_p27725-r1', 'merge')
>    @world
>
>
> ...
> Are they doing some kind of strange reorg or what?  HOw can I fix
> this?

I believe so:
http://forums.gentoo.org/viewtopic-t-713051.html

I'm guessing that it's this that's causing the problems you describe  
above. You mentioned package unmasking, and this is recommended in the  
referenced forums post for those that require Real, but you might just  
try unmerging win32codecs & realcodecs & trying your update again.

I discovered this reorganisation because updating my system showed  
mplayer updating with the real USE flag being forcibly disabled, i.e.:
[ebuild     U ] media-video/mplayer-1.0_rc2_p27725-r1 [1.0_rc2_p26753- 
r1] USE="...  -radio (-real*) -rtc ... " 0 kB
Someone on #gentoo was able to help because they'd experienced the  
issue this morning.

It's not clear to me from this post whether Realplayer & these codecs  
are actually needed by mplayer in order to play .rm & .ram playlists &  
audio files. One would assume so, except for beandog's statement  
"Chances are, you don't need them anyway. The codecs are hardly used  
anymore, and most people will be fine without them."

I have been thinking recently to record Pete Tong & the other Friday /  
Saturday night Radio 1 DJs using cron & mplayer, so I can burn their  
shows to CD-R & listen to them in the car during the week. As a  
consequence later tonight I will be testing mplayer's ability to  
handle http://www.bbc.co.uk/radio1/realaudio/media/r1live.ram without  
these packages installed.

Stroller.



  reply	other threads:[~2008-11-09  5:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-09  4:09 [gentoo-user] How do I fix multiple versions for the same package slot have been pulled John covici
2008-11-09  5:01 ` Stroller [this message]
2008-11-09  7:39   ` [gentoo-user] win32codecs / realcodecs / amd64codecs (and the -real USE flag) was: " John covici
2008-11-09 10:29     ` Neil Bothwick
2008-11-11 16:49   ` Stroller
2008-11-16  5:40   ` jaeyoung lee
2008-11-09 10:41 ` [gentoo-user] " Daniel Pielmeier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=244A2EC0-AE4E-4B37-8E91-8595BF26A227@stellar.eclipse.co.uk \
    --to=stroller@stellar.eclipse.co.uk \
    --cc=covici@ccs.covici.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox