hello, i try to update my system and have some problems to update it. one of the problems, which i can't solve are the two versions of ffmpeg (0.10.3 and 0.10.2) which emerge try to install at the same time: [blocks B ] media-video/ffmpeg ("media-video/ffmpeg" is blocking media-video/libav-0.8.4) * Error: The above package list contains packages which cannot be * installed at the same time on the same system. (media-video/libav-0.8.4::gentoo, ebuild scheduled for merge) pulled in by >=media-video/libav-0.8.2[X,encode,jpeg2k,mp3,sdl,-theora,threads,truetype,-vaapi,-vdpau,-x264] required by (virtual/ffmpeg-0.10.2-r1::gentoo, ebuild scheduled for merge) (media-video/ffmpeg-0.10.3::gentoo, installed) pulled in by >=media-video/ffmpeg-0.10.3 required by (media-video/mplayer-1.1-r1::gentoo, ebuild scheduled for merge) media-video/ffmpeg required by @selected media-video/ffmpeg required by (media-plugins/gst-plugins-ffmpeg-0.10.13-r2::gentoo, ebuild scheduled for merge) media-video/ffmpeg required by (media-video/vlc-2.0.3::gentoo, ebuild scheduled for merge) i can install the new libav and ffmpeg, but i don't know, why the old ffmeg also should installed. i think, someone forget to update a package-configuration file. goodby
The component has been changed to Unspecified since the Ebuilds component is meant to add new ebuilds. Since there is no other Component that fits your bug at the moment, we'll first need to evaluate what the actual problem is in order to assign this bug to a component / herd. This will not affect the visibility of your bug in any way. The question "why the old ffmpeg also should installed" is not answered by the part of output that you linked, let's walk through it shorty to see what it really means. [blocks B ] media-video/ffmpeg ("media-video/ffmpeg" is blocking media-video/libav-0.8.4) This means that libav needs ffmpeg but can't emerge because of ffmpeg, why this is the case is explained in the lines below that; I'll place a stripped version here to make it more clear: (libav-0.8.4, scheduled for merge) pulled in by ... required by (ffmpeg-0.10.2-r1, scheduled for merge) (ffmpeg-0.10.3, installed) pulled in by ... required by ... This means that ffmpeg-0.10.2 is scheduled for merge and it needs libav-0.8.4 thus schedules that for merge as well; ffmpeg is already installed and required by packages like mplayer, gst-plugins-ffmpeg and vlc some of which are scheduled for merge. So, what we can see from this is that both ffmpeg ended up in the list to emerge. But since that isn't possible it blocks between ffmpeg and libav. As I said before, it doesn't tell you though why there is a block. For that, we'll need a full outputted format so I'd like to ask you to do these things: 1) Please tell us what emerge command you are using. 2) Post the output of `emerge --info` into a comment, if it's too long for some reason then post it in an attachment. 3) Append the parameters --tree --unordered-display to your emerge command and post the full output in attachment. If you are unable to copy the terminal's contents you can `emerge wgetpaste` and then append the following at the end of your command |& wgetpaste after which you need to go to the URL provided on a computer where you can copy, then click on the raw link and copy the contents into an attachment here. Attachments can be placed by clicking on the "Add an attachment" link above the comment input box. If you have managed to figure it out using the unordered tree display, which gives the packages in a "dependency tree" style then please let us know as well, thanks in advance. Packages that are deeper in the tree are dependencies of those that are less deep in the tree. Good luck!
To clarify, when I said "why there is a block" I meant: I assume two packages are both trying to emerge ffmpeg which causes ffmpeg and libav to block, but since we don't have the dependency tree we can't tell which packages attempt to do this exactly. This information (as well as the command and info) will help us solve this problem...
hello, i found this situation: - some packages need virtual/ffmpeg which is not the actual ffmpeg 0.10.3 - some packages need the actual ffmpeg 0.10.3 - i remove the use flag for ffmpeg, but i always can't install some packages - it seems, that the actual ffmpeg include libav 0.8.4, but some packages need also libav 0.8.4 which can not installed, if ffmpeg is installed i make this: - install libav 0.8.4 - install ffmpeg 0.10.3 - install the needed packages if possible - install the rest with option --nodeps, so i can install for kdenlive this works, but with security this makes problmes if i update the system the next time. i think, this works also with other packages, which need this libs. i hope, somebody change the configuration, so all packages which need libav accept also the actual ffmpeg with the includeded libav. i don't check all files but the libav.a of both packages have the same size, so i think, they are the same version. goodby
> - some packages need virtual/ffmpeg which is not the actual ffmpeg 0.10.3 > - some packages need the actual ffmpeg 0.10.3 > - i remove the use flag for ffmpeg, but i always can't install some packages > - it seems, that the actual ffmpeg include libav 0.8.4, but some packages need also libav 0.8.4 which can not installed, if ffmpeg is installed Each of these sentences contain "some packages". Which packages are you talking about? See the ordered list in my previous comment where we asked these details, it would be handy if we get the full emerge output so we know which packages are bothering you; we can't see what you are emerging or using so it is hard to replicate these block without those details. > - install the rest with option --nodeps, so i can install > for kdenlive this works, but with security this makes problmes if i update the system the next time. > i think, this works also with other packages, which need this libs. These sounds like an unnecessary workaround, this also might cause that you won't be able to reproduce the problematic block you reported in your bug anymore. /var/log/emerge.log and /var/log/portage/elog/summary.log might still have some information about them. > i hope, somebody change the configuration, so all packages which need libav accept also the actual ffmpeg with the includeded libav. This sounds bad, that would mean packages were to depend on ffmpeg to just get the libav file. If they don't need the actual ffmpeg they should just depend on libav instead. Since guessing and working around a problem leads us to a state where we might not be able to fix this bug anymore, please elaborate on the actual block problem if you still can...
hallo, you don't mist change the packages, which need libav to ffmpeg, but if ffmpeg dpn't block libav, it is possible to install both to solve the depencies without workaround. but the depencies must be changed that all packages use the actual packages and not two diffent version. virtual/ffmpeg must be the same version as media-video/ffmpeg. the packages, which make problems on my system are kdenlive, vlc and mlt. with my workaround, i have installed the packages, i need and at the moment i check, which packages i forget and how i must configure xorg for my display-resolution. if somebody change the depencies to ONE version libav and ffmpeg without collision, i will test it. i mußt update some other systems with gentoo in the next time and install my new server with gentoo. so it is no problem, to test it. goodby PS: i wrote some packages, because i don't check all packages, but i think, there are more packages with this problem, which i don't install.
Sorry, it seems that I skipped over your title and didn't note the difference between virtual and media-video each time in your first comment. I didn't realize this mistake even after your second comment. So, ignore what I said earlier where I tried to get a more clear view on what exactly was happening, but it appeared the information provided was already sufficient for that if I only had read it more carefully. Your extra comments were helpful for clarifying that, thank you for that. I have found this to be reported earlier in https://bugs.gentoo.org/show_bug.cgi?id=436166 so I'll be closing this as a duplicate of that, I'd suggest you support to vote for that bug and I'll put you CC there so that you'll receive updates of it it. When virtual/ffmpeg-0.10.3 gets stable due to that bug, you should no longer experience this problem. *** This bug has been marked as a duplicate of bug 436166 ***
