Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, 16 May 2015 08:57:15 -0400, Rich Freeman wrote: > > Does that include the several lines of comments, often repeated, that > > portage includes in the auto-unmask output? I just checked two systems > > for abi_x86_32 and got around 130 lines in one and 220 in the other. > > Yes, it does. The number of actual configuration lines is much > smaller of course - probably 1/5th of the total. > > My point wasn't so much that this was an inordinate number of 32-bit > packages, given my list of installed packages. It was more about the > fact that on a system that I'm trying to keep fairly minimal other > than my explicit preferences I end up with a huge config file that > tends to mix my preferences with a lot of stuff that exists solely to > satisfy the depgraph. It would be like sticking every package I > install in my world set. Oh, I agree. If portage needs this stuff set, it should keep it separate from my choices, somewhere like /var/lib/portage/package.use. > There are some ways around this which I'll probably get around to on a > rainy day: > > 1. Take better advantage of the fact that package.use can be a > directory and have several files. The 32-bit flags would go in their > own file. Yes, that's how I do it. I usually group entries according to the program that I use, so a flag for a dependency goes in with the settings for the program requiring that dependency. That way, if I remove the program I can simply remove the single file for package.use. For the abi_x86 flags, though, I keep them in their own file, so those settings are not mixed in with my settings, although they really shouldn't be in the same directory. > Autounmask goes in a separate file with a z at the start of > the name and the intent is that lines in this file get moved to the > appropriate files. That one through me for a while, until I bothered to RTFM, portage always adds auto-unmasked entries to the last file in the directory. > 2. What I'd really like to get to is a point where all my systems are > defined by ansible configs or the like. I've already started > container-izing many of my services to cut down on interactions - this > way when I do random package updates I'm not dealing with mysql > breaking or apache or whatever. However, this increases the amount of > updating I have to do, and I'd like to bring that back down using a > tool like ansible. That sounds an interesting approach. -- Neil Bothwick I used to have a handle on life, then it broke. pgpCDpaSWMI2K.pgp Description: OpenPGP digital signature
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 17:12 GMT+03:00 Rich Freeman : > On Sat, May 16, 2015 at 8:53 AM, gevisz wrote: >> >> I am inattentive today. :( >> >> Some blockers remained but I hope it will not broke the system. >>... >> [blocks b ] > (">... >> Would you like to merge these packages? [Yes/No] y >> > > This is pretty normal for a qt upgrade. You haven't updated this > system recently, so you have a couple of relatively large updates that > are all getting mashed together in your emerge output - they're easier > to follow individually. My last update was on only a week ago, on May 9. I think that the "large updates" are caused by switching to global abi_x86_32 from doing it on per package base. > Blockers with a lower-case b are ones that portage can handle on its > own. Blockers with a capital B are ones it needs help from you with. > A clue is the fact that portage went ahead with asking you whether to > proceed, which indicates that it thinks it knows what it is doing. > You should be fine answering Y. Ok, thank you for explanation. P.S. I am still compiling.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, May 16, 2015 at 8:53 AM, gevisz wrote: > > I am inattentive today. :( > > Some blockers remained but I hope it will not broke the system. >... > [blocks b ] ("... > Would you like to merge these packages? [Yes/No] y > This is pretty normal for a qt upgrade. You haven't updated this system recently, so you have a couple of relatively large updates that are all getting mashed together in your emerge output - they're easier to follow individually. Blockers with a lower-case b are ones that portage can handle on its own. Blockers with a capital B are ones it needs help from you with. A clue is the fact that portage went ahead with asking you whether to proceed, which indicates that it thinks it knows what it is doing. You should be fine answering Y. -- Rich
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 15:50 GMT+03:00 Alan McKinnon : > On 16/05/2015 09:51, gevisz wrote: >> 2015-05-16 9:44 GMT+03:00 Alan McKinnon : >>> On 16/05/2015 07:52, gevisz wrote: 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : > On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: >> >> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury >> wrote: >> >>> I had a similar problem with some packages wanting virtual/ffmpeg and >>> it wouldn't take the -libav USE flag without adding a keyword for >>> ~amd64 on the virtual. >>> (yes, I am going the opposite way from you, but the cause seem the >>> same -- various USE flags are not yet adjusted in the stable >>> branches.) >>> >>> Perhaps we need to request "stabilization" for some of the newer >>> packages to solve this. >> >> Thank you for confirming that libav USE flag do not work not only for me. >> >> However, it would be interesting to hear what the Gentoo devs think about >> this issue. > > Portage news item No 19 has the answer you're looking for. No, it has not. As I have already written, I have libav USE flag in my /etc/portage/make.conf and still portage wants to merge media-video/ffmpeg >> eselect news read 19 >> 2015-04-16-ffmpeg-default >> Title FFmpeg default >> AuthorBen de Groot >> Posted2015-04-16 >> Revision 1 >> >> Since the choice between ffmpeg and libav has been made more >> explicit, there has been a lot of discussion about what the >> default implementation should be. It can be concluded that >> media-video/ffmpeg has wider support, and would be somewhat >> more convenient for most end-users. >> >> For this reason the default implementation has been switched >> back from media-video/libav to media-video/ffmpeg by removing >> the libav useflag from the base profile. >> >> If the libav useflag is already globally enabled or disabled >> in /etc/portage/make.conf, then no further action is required. >> >> Users who implicitly relied on libav being enabled in their >> profile, and who wish to continue using libav, should enable >> USE=libav in their /etc/portage/make.conf file. P.S. Trying to find out which packages currently depend on ffmpeg, I get the following: $ equery depends ffmpeg * These packages depend on ffmpeg: app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) media-plugins/alsa-plugins-1.0.28 (ffmpeg ? virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? > =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? > =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) (!libav ? >=media-video/ffmpeg-1.2:0) (!libav ? media-video/ffmpeg:0[vaapi]) virtual/ffmpeg-9-r1 (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) Interestingly enouth, when I try to find out why the tracker package needs ffmpeg, I get the following: $ equery uses tracker [ Legend : U - final flag setting for installation] [: I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-misc/tracker-1.2.5: U I - - cue : Enable cue sheet parsing + + exif : Add support for reading EXIF headers from JPEG and TIFF images - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support - - firefox-bookmarks : Install bookmark data miner plugin for www-client/firefox and www-client/firefox-bin + + flac : Add support for FLAC: Free Lossless Audio Codec + + gif : Add GIF image support - - gsf : Enable gnome-extra/libgsf based data extractor and for ODT. + + gstreamer
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, May 16, 2015 at 7:50 AM, Neil Bothwick wrote: > On Sat, 16 May 2015 07:16:58 -0400, Rich Freeman wrote: >> >> Well, it can be a lot more than two screens of text. I have 1300 >> lines of package.use, almost all of it for abi_x86_32. I suspect that >> this the result of stuff like steam, wine, android-sdk-update-manager, >> and eternal-lands - all packages that involve graphics libraries and >> toolkits with huge dependency trees. > > Does that include the several lines of comments, often repeated, that > portage includes in the auto-unmask output? I just checked two systems > for abi_x86_32 and got around 130 lines in one and 220 in the other. Yes, it does. The number of actual configuration lines is much smaller of course - probably 1/5th of the total. My point wasn't so much that this was an inordinate number of 32-bit packages, given my list of installed packages. It was more about the fact that on a system that I'm trying to keep fairly minimal other than my explicit preferences I end up with a huge config file that tends to mix my preferences with a lot of stuff that exists solely to satisfy the depgraph. It would be like sticking every package I install in my world set. There are some ways around this which I'll probably get around to on a rainy day: 1. Take better advantage of the fact that package.use can be a directory and have several files. The 32-bit flags would go in their own file. Autounmask goes in a separate file with a z at the start of the name and the intent is that lines in this file get moved to the appropriate files. Then from time to time the 32-bit flags can be deleted and re-created to keep them minimal as installed packages change. 2. What I'd really like to get to is a point where all my systems are defined by ansible configs or the like. I've already started container-izing many of my services to cut down on interactions - this way when I do random package updates I'm not dealing with mysql breaking or apache or whatever. However, this increases the amount of updating I have to do, and I'd like to bring that back down using a tool like ansible. -- Rich
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 11:26 GMT+03:00 gevisz : > 2015-05-16 10:51 GMT+03:00 gevisz : >> 2015-05-16 9:44 GMT+03:00 Alan McKinnon : >>> On 16/05/2015 07:52, gevisz wrote: 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : > On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: >> >> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury >> wrote: >> >>> I had a similar problem with some packages wanting virtual/ffmpeg and >>> it wouldn't take the -libav USE flag without adding a keyword for >>> ~amd64 on the virtual. >>> (yes, I am going the opposite way from you, but the cause seem the >>> same -- various USE flags are not yet adjusted in the stable >>> branches.) >>> >>> Perhaps we need to request "stabilization" for some of the newer >>> packages to solve this. >> >> Thank you for confirming that libav USE flag do not work not only for me. >> >> However, it would be interesting to hear what the Gentoo devs think about >> this issue. > > Portage news item No 19 has the answer you're looking for. No, it has not. As I have already written, I have libav USE flag in my /etc/portage/make.conf and still portage wants to merge media-video/ffmpeg >> eselect news read 19 >> 2015-04-16-ffmpeg-default >> Title FFmpeg default >> AuthorBen de Groot >> Posted2015-04-16 >> Revision 1 >> >> Since the choice between ffmpeg and libav has been made more >> explicit, there has been a lot of discussion about what the >> default implementation should be. It can be concluded that >> media-video/ffmpeg has wider support, and would be somewhat >> more convenient for most end-users. >> >> For this reason the default implementation has been switched >> back from media-video/libav to media-video/ffmpeg by removing >> the libav useflag from the base profile. >> >> If the libav useflag is already globally enabled or disabled >> in /etc/portage/make.conf, then no further action is required. >> >> Users who implicitly relied on libav being enabled in their >> profile, and who wish to continue using libav, should enable >> USE=libav in their /etc/portage/make.conf file. P.S. Trying to find out which packages currently depend on ffmpeg, I get the following: $ equery depends ffmpeg * These packages depend on ffmpeg: app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) media-plugins/alsa-plugins-1.0.28 (ffmpeg ? virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? > =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? > =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) (!libav ? >=media-video/ffmpeg-1.2:0) (!libav ? media-video/ffmpeg:0[vaapi]) virtual/ffmpeg-9-r1 (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) Interestingly enouth, when I try to find out why the tracker package needs ffmpeg, I get the following: $ equery uses tracker [ Legend : U - final flag setting for installation] [: I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-misc/tracker-1.2.5: U I - - cue : Enable cue sheet parsing + + exif : Add support for reading EXIF headers from JPEG and TIFF images - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support - - firefox-bookmarks : Install bookmark data miner plugin for www-client/firefox and www-client/firefox-bin + + flac : Add support for FLAC: Free Lossless Audio Codec + + gif : Add GIF image support - - gsf : Enable gnome-extra/libgsf based data extractor and for ODT. + + gstreamer : Ad
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On 16/05/2015 09:51, gevisz wrote: > 2015-05-16 9:44 GMT+03:00 Alan McKinnon : >> On 16/05/2015 07:52, gevisz wrote: >>> 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: > > On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury > wrote: > >> I had a similar problem with some packages wanting virtual/ffmpeg and >> it wouldn't take the -libav USE flag without adding a keyword for >> ~amd64 on the virtual. >> (yes, I am going the opposite way from you, but the cause seem the >> same -- various USE flags are not yet adjusted in the stable >> branches.) >> >> Perhaps we need to request "stabilization" for some of the newer >> packages to solve this. > > Thank you for confirming that libav USE flag do not work not only for me. > > However, it would be interesting to hear what the Gentoo devs think about > this issue. Portage news item No 19 has the answer you're looking for. >>> >>> No, it has not. >>> >>> As I have already written, I have libav USE flag in my >>> /etc/portage/make.conf >>> and still portage wants to merge media-video/ffmpeg >>> > eselect news read 19 > 2015-04-16-ffmpeg-default > Title FFmpeg default > AuthorBen de Groot > Posted2015-04-16 > Revision 1 > > Since the choice between ffmpeg and libav has been made more > explicit, there has been a lot of discussion about what the > default implementation should be. It can be concluded that > media-video/ffmpeg has wider support, and would be somewhat > more convenient for most end-users. > > For this reason the default implementation has been switched > back from media-video/libav to media-video/ffmpeg by removing > the libav useflag from the base profile. > > If the libav useflag is already globally enabled or disabled > in /etc/portage/make.conf, then no further action is required. > > Users who implicitly relied on libav being enabled in their > profile, and who wish to continue using libav, should enable > USE=libav in their /etc/portage/make.conf file. >>> >>> P.S. Trying to find out which packages currently depend on ffmpeg, >>>I get the following: >>> >>> $ equery depends ffmpeg >>> * These packages depend on ffmpeg: >>> app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) >>> media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) >>> media-plugins/alsa-plugins-1.0.28 (ffmpeg ? >>> virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >>> media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >>> media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >>> media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) >>> media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) >>> (!libav ? >=media-video/ffmpeg-1.2:0) >>> (!libav ? media-video/ffmpeg:0[vaapi]) >>> virtual/ffmpeg-9-r1 >>> (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) >>> >>> Interestingly enouth, when I try to find out why the tracker package >>> needs ffmpeg, >>> I get the following: >>> >>> $ equery uses tracker >>> [ Legend : U - final flag setting for installation] >>> [: I - package is installed with flag ] >>> [ Colors : set, unset ] >>> * Found these USE flags for app-misc/tracker-1.2.5: >>> U I >>> - - cue : Enable cue sheet parsing >>> + + exif : Add support for reading EXIF headers from >>> JPEG and TIFF images >>> - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support >>> - - firefox-bookmarks : Install bookmark data miner plugin for >>> www-client/firefox and www-client/firefox-bin >>> + + flac : Add support for FLAC: Free Lossless Audio Codec >>> + + gif : Add GIF image support >>> - - gsf : Enable gnome-extra/libgsf based data >>> extractor and for ODT. >>> + + gstreamer : Add support for media-libs/gstreamer (Streaming >>> media) >>> + + gtk : Add support for x11-libs/gtk+ (The GIMP Toolkit) >>>
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, 16 May 2015 07:16:58 -0400, Rich Freeman wrote: > > Unless your screen is IMAX-sized, two screens of text is a lot more > > lightfooted than add extra libraries to nearly 200 packages - and most > > of that text is comments anyway. > > > > Well, it can be a lot more than two screens of text. I have 1300 > lines of package.use, almost all of it for abi_x86_32. I suspect that > this the result of stuff like steam, wine, android-sdk-update-manager, > and eternal-lands - all packages that involve graphics libraries and > toolkits with huge dependency trees. Does that include the several lines of comments, often repeated, that portage includes in the auto-unmask output? I just checked two systems for abi_x86_32 and got around 130 lines in one and 220 in the other. The smaller number is for a laptop with a lighter install, although there isn't a massive difference between the total number of packages installed on each. Enabling the flag globally would probably affect the lighter, and slower, system more. > 1. Portage's error messages when it is unable to produce a resolution > are really confusing - somewhere in that wall of text are some clues > that might eventually lead you to the likely 1-3 use flag or keyword > tweaks that will fix the whole mess, but good luck finding it. Your > example isn't even a terribly bad one - when you get those errors with > something like qt it goes on forever. > > 2. Portage requires non-package-default use flags to always be > specified explicitly either globally or per-package. I don't have to > put qt in my world file to install kde, because portage knows it is > needed and just installs it, and removes it when it is no longer > needed. However, if something needs the qt use flag, portage can't > treat it the same way. > > Now, there are certainly reasons why both of these issues exist. > Solving them may not be trivial, and in the case of #2 perhaps there > may be unintended consequences like unnecessary package rebuilds to > progressively add/remove flags. And, of course, somebody has to do the > work and since I'm not busy writing patches to portage right now I'm > not going to complain too much about it. > > However, I really think that these are the real issue here. That, and > automatically solving depgraph issues isn't trivial. No argument there. Portage's output can be unhelpful, obtuse, even misleading at times, but as I'm not in a position to do something about it, neither am I in a position to complain about it. -- Neil Bothwick [ Printed on recycled electrons ] pgpHpychKlvgz.pgp Description: OpenPGP digital signature
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, May 16, 2015 at 6:20 AM, Neil Bothwick wrote: > On Sat, 16 May 2015 13:10:21 +0300, gevisz wrote: > >> > I'm afraid I cannot agree with you on this. On older PCs I would >> > rather did not have to install abi_x86_32 for packages that I don't >> > need to. The granular approach suits me better and also aligns >> > better with the light-footed Gentoo approach. >> >> With this "light-footed approach" I had about two full-screen rubbish >> in my /etc/portage/make.conf file and kept adding on almost every >> update. > > Unless your screen is IMAX-sized, two screens of text is a lot more > lightfooted than add extra libraries to nearly 200 packages - and most > of that text is comments anyway. > Well, it can be a lot more than two screens of text. I have 1300 lines of package.use, almost all of it for abi_x86_32. I suspect that this the result of stuff like steam, wine, android-sdk-update-manager, and eternal-lands - all packages that involve graphics libraries and toolkits with huge dependency trees. I still recommend the per-package approach, but I really think we're barking up the wrong tree here. I don't see the depgraph itself as the issue, or the ability to tweak flags per-package. I really see the bigger problem as the combination of two things: 1. Portage's error messages when it is unable to produce a resolution are really confusing - somewhere in that wall of text are some clues that might eventually lead you to the likely 1-3 use flag or keyword tweaks that will fix the whole mess, but good luck finding it. Your example isn't even a terribly bad one - when you get those errors with something like qt it goes on forever. 2. Portage requires non-package-default use flags to always be specified explicitly either globally or per-package. I don't have to put qt in my world file to install kde, because portage knows it is needed and just installs it, and removes it when it is no longer needed. However, if something needs the qt use flag, portage can't treat it the same way. Now, there are certainly reasons why both of these issues exist. Solving them may not be trivial, and in the case of #2 perhaps there may be unintended consequences like unnecessary package rebuilds to progressively add/remove flags. And, of course, somebody has to do the work and since I'm not busy writing patches to portage right now I'm not going to complain too much about it. However, I really think that these are the real issue here. That, and automatically solving depgraph issues isn't trivial. -- Rich
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, 16 May 2015 11:52:48 +0100, Mick wrote: > PS. I'm waiting for Neil's uncanny signature which if it works > correctly it should come with something like: "Nostalgia, it's not > what it used to be" LOL! You can't force these things, it's not uncanny if it's deliberate. -- Neil Bothwick Nostalgia isn't what it used to be. pgpWCuNnMml99.pgp Description: OpenPGP digital signature
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Saturday 16 May 2015 11:40:01 gevisz wrote: > 2015-05-16 13:20 GMT+03:00 Neil Bothwick : > > As Mick says, you get to choose, but the per-package approach is > > definitely lighter on the system. Enabling it globally may be less work > > though. I say "may" because when I tried that it introduced some > > breakages, > > If enabling abi_x86_32 globally may introduce breakages, then > the multilib profile is even more broken than I ever thought. :-( > > > so I went for the per-package approach. > > -- > > Neil Bothwick > > > > Things are more like they are today than they ever have been before. > > Yes, I do remember installing Linux on a brand-new laptop in 2003. > > I had to compile a new kernel only to get the command prompt. > > And, to get a graphic interface, I had to wait for a new release > of the distribution in 2004. :( Oh the nostalgia of the good old days! Back then we had to (bootstrap)^2 to begin the installation. I seem to recall 2004.1 as a relatively straight forward installation vintage/profile, although there were the odd horror stories depending on hardware combos and missing drivers. PS. I'm waiting for Neil's uncanny signature which if it works correctly it should come with something like: "Nostalgia, it's not what it used to be" LOL! -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 13:33 GMT+03:00 Mick : > On Saturday 16 May 2015 11:10:21 gevisz wrote: >> 2015-05-16 11:55 GMT+03:00 Mick : > >> > I'm afraid I cannot agree with you on this. On older PCs I would rather >> > did not have to install abi_x86_32 for packages that I don't need to. >> > The granular approach suits me better and also aligns better with the >> > light-footed Gentoo approach. >> >> With this "light-footed approach" I had about two full-screen rubbish >> in my /etc/portage/make.conf file and kept adding on almost every update. > > Ahh ... let's wind back a step. The recommended file to change for package by > package USE flags is /etc/portage/package.use, not /etc/portage/make.conf. It was my fault when typing. I actually mean /etc/portage/package.use and have sent corrections later. > The latter is only for setting USE flags globally, e.g. when you want libav > for all packages, instead of the (now default) ffmpeg flag. > > Ditto for the abi_x86_32 USE flag. > > -- > Regards, > Mick
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 13:20 GMT+03:00 Neil Bothwick : > On Sat, 16 May 2015 13:10:21 +0300, gevisz wrote: > >> > I'm afraid I cannot agree with you on this. On older PCs I would >> > rather did not have to install abi_x86_32 for packages that I don't >> > need to. The granular approach suits me better and also aligns >> > better with the light-footed Gentoo approach. >> >> With this "light-footed approach" I had about two full-screen rubbish >> in my /etc/portage/make.conf file and kept adding on almost every >> update. > > Unless your screen is IMAX-sized, two screens of text is a lot more > lightfooted than add extra libraries to nearly 200 packages - and most > of that text is comments anyway. > > As Mick says, you get to choose, but the per-package approach is > definitely lighter on the system. Enabling it globally may be less work > though. I say "may" because when I tried that it introduced some > breakages, If enabling abi_x86_32 globally may introduce breakages, then the multilib profile is even more broken than I ever thought. :-( > so I went for the per-package approach. > -- > Neil Bothwick > > Things are more like they are today than they ever have been before. Yes, I do remember installing Linux on a brand-new laptop in 2003. I had to compile a new kernel only to get the command prompt. And, to get a graphic interface, I had to wait for a new release of the distribution in 2004. :(
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Saturday 16 May 2015 11:10:21 gevisz wrote: > 2015-05-16 11:55 GMT+03:00 Mick : > > I'm afraid I cannot agree with you on this. On older PCs I would rather > > did not have to install abi_x86_32 for packages that I don't need to. > > The granular approach suits me better and also aligns better with the > > light-footed Gentoo approach. > > With this "light-footed approach" I had about two full-screen rubbish > in my /etc/portage/make.conf file and kept adding on almost every update. Ahh ... let's wind back a step. The recommended file to change for package by package USE flags is /etc/portage/package.use, not /etc/portage/make.conf. The latter is only for setting USE flags globally, e.g. when you want libav for all packages, instead of the (now default) ffmpeg flag. Ditto for the abi_x86_32 USE flag. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Sat, 16 May 2015 13:10:21 +0300, gevisz wrote: > > I'm afraid I cannot agree with you on this. On older PCs I would > > rather did not have to install abi_x86_32 for packages that I don't > > need to. The granular approach suits me better and also aligns > > better with the light-footed Gentoo approach. > > With this "light-footed approach" I had about two full-screen rubbish > in my /etc/portage/make.conf file and kept adding on almost every > update. Unless your screen is IMAX-sized, two screens of text is a lot more lightfooted than add extra libraries to nearly 200 packages - and most of that text is comments anyway. As Mick says, you get to choose, but the per-package approach is definitely lighter on the system. Enabling it globally may be less work though. I say "may" because when I tried that it introduced some breakages, so I went for the per-package approach. -- Neil Bothwick Things are more like they are today than they ever have been before. pgpnHCm9w4gm2.pgp Description: OpenPGP digital signature
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 13:10 GMT+03:00 gevisz : > 2015-05-16 11:55 GMT+03:00 Mick : >> On Saturday 16 May 2015 09:26:14 gevisz wrote: >>> 2015-05-16 10:51 GMT+03:00 gevisz : >> >>> >So, if I get no better suggestions, I will enable abi_x86_32 >>> >globally and try to update the world once more. >>> >>> Lukily, this approach worked out. Currently I am updating and recompiling >>> 199 packages but the blockers disappeared. >>> >>> >If that will not work, I will remove the libav USE flag from >>> >/etc/portage/make.conf and try to update the world for the last >>> >time. >>> >>> Now, when everything ended well, I can accept that by the phrase >>> "to update the world for the last time" above I meant that I was going >>> to switch to other Linux distribution if this issue with >>> ffmpeg-libav-multilib could not be solved in an elegant way, that is, >>> without poking with every single package, which is really ugly. >>> >>> Luckily, everything ended well and I am happy to stay with Gentoo, >>> but I should mention that, having such issues with multilib profile, >>> enabling abi_x86_32 on per package base really should be unrecommended >>> way to maintain the system and users should be warned about it. >> >> I'm afraid I cannot agree with you on this. On older PCs I would rather did >> not have to install abi_x86_32 for packages that I don't need to. The >> granular approach suits me better and also aligns better with the >> light-footed >> Gentoo approach. > > With this "light-footed approach" I had about two full-screen rubbish > in my /etc/portage/make.conf file and kept adding on almost every update. Correction: in /etc/portage/package.use >> I think had you followed my suggestion you could have found that >> by remerging half a dozen packages at most, your conflict would >> have been resolved. > > I think so, but this is what I call ugly. > >> Either way you got a result, so whatever works. :-) > > Yes, thank you.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 11:55 GMT+03:00 Mick : > On Saturday 16 May 2015 09:26:14 gevisz wrote: >> 2015-05-16 10:51 GMT+03:00 gevisz : > >> >So, if I get no better suggestions, I will enable abi_x86_32 >> >globally and try to update the world once more. >> >> Lukily, this approach worked out. Currently I am updating and recompiling >> 199 packages but the blockers disappeared. >> >> >If that will not work, I will remove the libav USE flag from >> >/etc/portage/make.conf and try to update the world for the last >> >time. >> >> Now, when everything ended well, I can accept that by the phrase >> "to update the world for the last time" above I meant that I was going >> to switch to other Linux distribution if this issue with >> ffmpeg-libav-multilib could not be solved in an elegant way, that is, >> without poking with every single package, which is really ugly. >> >> Luckily, everything ended well and I am happy to stay with Gentoo, >> but I should mention that, having such issues with multilib profile, >> enabling abi_x86_32 on per package base really should be unrecommended >> way to maintain the system and users should be warned about it. > > I'm afraid I cannot agree with you on this. On older PCs I would rather did > not have to install abi_x86_32 for packages that I don't need to. The > granular approach suits me better and also aligns better with the light-footed > Gentoo approach. With this "light-footed approach" I had about two full-screen rubbish in my /etc/portage/make.conf file and kept adding on almost every update. > I think had you followed my suggestion you could have found that > by remerging half a dozen packages at most, your conflict would > have been resolved. I think so, but this is what I call ugly. > Either way you got a result, so whatever works. :-) Yes, thank you.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Saturday 16 May 2015 09:26:14 gevisz wrote: > 2015-05-16 10:51 GMT+03:00 gevisz : > >So, if I get no better suggestions, I will enable abi_x86_32 > >globally and try to update the world once more. > > Lukily, this approach worked out. Currently I am updating and recompiling > 199 packages but the blockers disappeared. > > >If that will not work, I will remove the libav USE flag from > >/etc/portage/make.conf and try to update the world for the last > >time. > > Now, when everything ended well, I can accept that by the phrase > "to update the world for the last time" above I meant that I was going > to switch to other Linux distribution if this issue with > ffmpeg-libav-multilib could not be solved in an elegant way, that is, > without poking with every single package, which is really ugly. > > Luckily, everything ended well and I am happy to stay with Gentoo, > but I should mention that, having such issues with multilib profile, > enabling abi_x86_32 on per package base really should be unrecommended > way to maintain the system and users should be warned about it. I'm afraid I cannot agree with you on this. On older PCs I would rather did not have to install abi_x86_32 for packages that I don't need to. The granular approach suits me better and also aligns better with the light-footed Gentoo approach. I think had you followed my suggestion you could have found that by remerging half a dozen packages at most, your conflict would have been resolved. Either way you got a result, so whatever works. :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 10:51 GMT+03:00 gevisz : > 2015-05-16 9:44 GMT+03:00 Alan McKinnon : >> On 16/05/2015 07:52, gevisz wrote: >>> 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: > > On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury > wrote: > >> I had a similar problem with some packages wanting virtual/ffmpeg and >> it wouldn't take the -libav USE flag without adding a keyword for >> ~amd64 on the virtual. >> (yes, I am going the opposite way from you, but the cause seem the >> same -- various USE flags are not yet adjusted in the stable >> branches.) >> >> Perhaps we need to request "stabilization" for some of the newer >> packages to solve this. > > Thank you for confirming that libav USE flag do not work not only for me. > > However, it would be interesting to hear what the Gentoo devs think about > this issue. Portage news item No 19 has the answer you're looking for. >>> >>> No, it has not. >>> >>> As I have already written, I have libav USE flag in my >>> /etc/portage/make.conf >>> and still portage wants to merge media-video/ffmpeg >>> > eselect news read 19 > 2015-04-16-ffmpeg-default > Title FFmpeg default > AuthorBen de Groot > Posted2015-04-16 > Revision 1 > > Since the choice between ffmpeg and libav has been made more > explicit, there has been a lot of discussion about what the > default implementation should be. It can be concluded that > media-video/ffmpeg has wider support, and would be somewhat > more convenient for most end-users. > > For this reason the default implementation has been switched > back from media-video/libav to media-video/ffmpeg by removing > the libav useflag from the base profile. > > If the libav useflag is already globally enabled or disabled > in /etc/portage/make.conf, then no further action is required. > > Users who implicitly relied on libav being enabled in their > profile, and who wish to continue using libav, should enable > USE=libav in their /etc/portage/make.conf file. >>> >>> P.S. Trying to find out which packages currently depend on ffmpeg, >>>I get the following: >>> >>> $ equery depends ffmpeg >>> * These packages depend on ffmpeg: >>> app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) >>> media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) >>> media-plugins/alsa-plugins-1.0.28 (ffmpeg ? >>> virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >>> media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >>> media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >>> media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) >>> media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) >>> (!libav ? >=media-video/ffmpeg-1.2:0) >>> (!libav ? media-video/ffmpeg:0[vaapi]) >>> virtual/ffmpeg-9-r1 >>> (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) >>> >>> Interestingly enouth, when I try to find out why the tracker package >>> needs ffmpeg, >>> I get the following: >>> >>> $ equery uses tracker >>> [ Legend : U - final flag setting for installation] >>> [: I - package is installed with flag ] >>> [ Colors : set, unset ] >>> * Found these USE flags for app-misc/tracker-1.2.5: >>> U I >>> - - cue : Enable cue sheet parsing >>> + + exif : Add support for reading EXIF headers from >>> JPEG and TIFF images >>> - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support >>> - - firefox-bookmarks : Install bookmark data miner plugin for >>> www-client/firefox and www-client/firefox-bin >>> + + flac : Add support for FLAC: Free Lossless Audio Codec >>> + + gif : Add GIF image support >>> - - gsf : Enable gnome-extra/libgsf based data >>> extractor and for ODT. >>> + + gstreamer : Add support for media-libs/gstreamer (Streaming >>> media) >>> + + gtk : Add support for x11-libs/gtk+ (The GIMP Toolkit) >>>
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-16 9:44 GMT+03:00 Alan McKinnon : > On 16/05/2015 07:52, gevisz wrote: >> 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : >>> On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury wrote: > I had a similar problem with some packages wanting virtual/ffmpeg and > it wouldn't take the -libav USE flag without adding a keyword for > ~amd64 on the virtual. > (yes, I am going the opposite way from you, but the cause seem the > same -- various USE flags are not yet adjusted in the stable > branches.) > > Perhaps we need to request "stabilization" for some of the newer > packages to solve this. Thank you for confirming that libav USE flag do not work not only for me. However, it would be interesting to hear what the Gentoo devs think about this issue. >>> >>> Portage news item No 19 has the answer you're looking for. >> >> No, it has not. >> >> As I have already written, I have libav USE flag in my /etc/portage/make.conf >> and still portage wants to merge media-video/ffmpeg >> eselect news read 19 2015-04-16-ffmpeg-default Title FFmpeg default AuthorBen de Groot Posted2015-04-16 Revision 1 Since the choice between ffmpeg and libav has been made more explicit, there has been a lot of discussion about what the default implementation should be. It can be concluded that media-video/ffmpeg has wider support, and would be somewhat more convenient for most end-users. For this reason the default implementation has been switched back from media-video/libav to media-video/ffmpeg by removing the libav useflag from the base profile. If the libav useflag is already globally enabled or disabled in /etc/portage/make.conf, then no further action is required. Users who implicitly relied on libav being enabled in their profile, and who wish to continue using libav, should enable USE=libav in their /etc/portage/make.conf file. >> >> P.S. Trying to find out which packages currently depend on ffmpeg, >>I get the following: >> >> $ equery depends ffmpeg >> * These packages depend on ffmpeg: >> app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) >> media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) >> media-plugins/alsa-plugins-1.0.28 (ffmpeg ? >> virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >> media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? >>> =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >> media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? >>> =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) >> media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) >> media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) >> (!libav ? >=media-video/ffmpeg-1.2:0) >> (!libav ? media-video/ffmpeg:0[vaapi]) >> virtual/ffmpeg-9-r1 >> (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) >> >> Interestingly enouth, when I try to find out why the tracker package >> needs ffmpeg, >> I get the following: >> >> $ equery uses tracker >> [ Legend : U - final flag setting for installation] >> [: I - package is installed with flag ] >> [ Colors : set, unset ] >> * Found these USE flags for app-misc/tracker-1.2.5: >> U I >> - - cue : Enable cue sheet parsing >> + + exif : Add support for reading EXIF headers from >> JPEG and TIFF images >> - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support >> - - firefox-bookmarks : Install bookmark data miner plugin for >> www-client/firefox and www-client/firefox-bin >> + + flac : Add support for FLAC: Free Lossless Audio Codec >> + + gif : Add GIF image support >> - - gsf : Enable gnome-extra/libgsf based data >> extractor and for ODT. >> + + gstreamer : Add support for media-libs/gstreamer (Streaming >> media) >> + + gtk : Add support for x11-libs/gtk+ (The GIMP Toolkit) >> - - iptc : Enable extraction of IPTC data from pictures >> + + iso : Enable extraction of metadata from ISO dis
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On 16/05/2015 07:52, gevisz wrote: > 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : >> On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: >>> >>> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury >>> wrote: >>> I had a similar problem with some packages wanting virtual/ffmpeg and it wouldn't take the -libav USE flag without adding a keyword for ~amd64 on the virtual. (yes, I am going the opposite way from you, but the cause seem the same -- various USE flags are not yet adjusted in the stable branches.) Perhaps we need to request "stabilization" for some of the newer packages to solve this. >>> >>> Thank you for confirming that libav USE flag do not work not only for me. >>> >>> However, it would be interesting to hear what the Gentoo devs think about >>> this issue. >> >> Portage news item No 19 has the answer you're looking for. > > No, it has not. > > As I have already written, I have libav USE flag in my /etc/portage/make.conf > and still portage wants to merge media-video/ffmpeg > >>> eselect news read 19 >>> 2015-04-16-ffmpeg-default >>> Title FFmpeg default >>> AuthorBen de Groot >>> Posted2015-04-16 >>> Revision 1 >>> >>> Since the choice between ffmpeg and libav has been made more >>> explicit, there has been a lot of discussion about what the >>> default implementation should be. It can be concluded that >>> media-video/ffmpeg has wider support, and would be somewhat >>> more convenient for most end-users. >>> >>> For this reason the default implementation has been switched >>> back from media-video/libav to media-video/ffmpeg by removing >>> the libav useflag from the base profile. >>> >>> If the libav useflag is already globally enabled or disabled >>> in /etc/portage/make.conf, then no further action is required. >>> >>> Users who implicitly relied on libav being enabled in their >>> profile, and who wish to continue using libav, should enable >>> USE=libav in their /etc/portage/make.conf file. > > P.S. Trying to find out which packages currently depend on ffmpeg, >I get the following: > > $ equery depends ffmpeg > * These packages depend on ffmpeg: > app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) > media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) > media-plugins/alsa-plugins-1.0.28 (ffmpeg ? > virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) > media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? >> =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) > media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? >> =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) > media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) > media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) > (!libav ? >=media-video/ffmpeg-1.2:0) > (!libav ? media-video/ffmpeg:0[vaapi]) > virtual/ffmpeg-9-r1 > (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) > > Interestingly enouth, when I try to find out why the tracker package > needs ffmpeg, > I get the following: > > $ equery uses tracker > [ Legend : U - final flag setting for installation] > [: I - package is installed with flag ] > [ Colors : set, unset ] > * Found these USE flags for app-misc/tracker-1.2.5: > U I > - - cue : Enable cue sheet parsing > + + exif : Add support for reading EXIF headers from > JPEG and TIFF images > - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support > - - firefox-bookmarks : Install bookmark data miner plugin for > www-client/firefox and www-client/firefox-bin > + + flac : Add support for FLAC: Free Lossless Audio Codec > + + gif : Add GIF image support > - - gsf : Enable gnome-extra/libgsf based data > extractor and for ODT. > + + gstreamer : Add support for media-libs/gstreamer (Streaming > media) > + + gtk : Add support for x11-libs/gtk+ (The GIMP Toolkit) > - - iptc : Enable extraction of IPTC data from pictures > + + iso : Enable extraction of metadata from ISO disk images > + + jpeg : Add JPEG image support > + + miner-fs : Enable tracker-miner-fs (required for > filesyst
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
2015-05-15 20:30 GMT+03:00 Alexander Kapshuk : > On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: >> >> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury >> wrote: >> >> > I had a similar problem with some packages wanting virtual/ffmpeg and >> > it wouldn't take the -libav USE flag without adding a keyword for >> > ~amd64 on the virtual. >> > (yes, I am going the opposite way from you, but the cause seem the >> > same -- various USE flags are not yet adjusted in the stable >> > branches.) >> > >> > Perhaps we need to request "stabilization" for some of the newer >> > packages to solve this. >> >> Thank you for confirming that libav USE flag do not work not only for me. >> >> However, it would be interesting to hear what the Gentoo devs think about >> this issue. > > Portage news item No 19 has the answer you're looking for. No, it has not. As I have already written, I have libav USE flag in my /etc/portage/make.conf and still portage wants to merge media-video/ffmpeg >> eselect news read 19 >> 2015-04-16-ffmpeg-default >> Title FFmpeg default >> AuthorBen de Groot >> Posted2015-04-16 >> Revision 1 >> >> Since the choice between ffmpeg and libav has been made more >> explicit, there has been a lot of discussion about what the >> default implementation should be. It can be concluded that >> media-video/ffmpeg has wider support, and would be somewhat >> more convenient for most end-users. >> >> For this reason the default implementation has been switched >> back from media-video/libav to media-video/ffmpeg by removing >> the libav useflag from the base profile. >> >> If the libav useflag is already globally enabled or disabled >> in /etc/portage/make.conf, then no further action is required. >> >> Users who implicitly relied on libav being enabled in their >> profile, and who wish to continue using libav, should enable >> USE=libav in their /etc/portage/make.conf file. P.S. Trying to find out which packages currently depend on ffmpeg, I get the following: $ equery depends ffmpeg * These packages depend on ffmpeg: app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) media-plugins/alsa-plugins-1.0.28 (ffmpeg ? virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? >=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? >=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) (!libav ? >=media-video/ffmpeg-1.2:0) (!libav ? media-video/ffmpeg:0[vaapi]) virtual/ffmpeg-9-r1 (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) Interestingly enouth, when I try to find out why the tracker package needs ffmpeg, I get the following: $ equery uses tracker [ Legend : U - final flag setting for installation] [: I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for app-misc/tracker-1.2.5: U I - - cue : Enable cue sheet parsing + + exif : Add support for reading EXIF headers from JPEG and TIFF images - - ffmpeg: Enable ffmpeg/libav-based audio/video codec support - - firefox-bookmarks : Install bookmark data miner plugin for www-client/firefox and www-client/firefox-bin + + flac : Add support for FLAC: Free Lossless Audio Codec + + gif : Add GIF image support - - gsf : Enable gnome-extra/libgsf based data extractor and for ODT. + + gstreamer : Add support for media-libs/gstreamer (Streaming media) + + gtk : Add support for x11-libs/gtk+ (The GIMP Toolkit) - - iptc : Enable extraction of IPTC data from pictures + + iso : Enable extraction of metadata from ISO disk images + + jpeg : Add JPEG image support + + miner-fs : Enable tracker-miner-fs (required for filesystem indexing) + + mp3 : Add support for reading mp3 files + + nautilus : Enable tracker to integrate with gnome-base/nautilus by providing entries in its conte
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Friday 15 May 2015 18:30:29 Alexander Kapshuk wrote: > On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: > > On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury > > > > wrote: > > > I had a similar problem with some packages wanting virtual/ffmpeg and > > > it wouldn't take the -libav USE flag without adding a keyword for > > > ~amd64 on the virtual. > > > (yes, I am going the opposite way from you, but the cause seem the > > > same -- various USE flags are not yet adjusted in the stable > > > branches.) > > > > > > Perhaps we need to request "stabilization" for some of the newer > > > packages to solve this. > > > > Thank you for confirming that libav USE flag do not work not only for me. > > > > However, it would be interesting to hear what the Gentoo devs think about > > this issue. > > Portage news item No 19 has the answer you're looking for. > > > eselect news read 19 > > 2015-04-16-ffmpeg-default > > > > Title FFmpeg default > > AuthorBen de Groot > > Posted2015-04-16 > > Revision 1 > > > > Since the choice between ffmpeg and libav has been made more > > explicit, there has been a lot of discussion about what the > > default implementation should be. It can be concluded that > > media-video/ffmpeg has wider support, and would be somewhat > > more convenient for most end-users. > > > > For this reason the default implementation has been switched > > back from media-video/libav to media-video/ffmpeg by removing > > the libav useflag from the base profile. > > > > If the libav useflag is already globally enabled or disabled > > in /etc/portage/make.conf, then no further action is required. > > > > Users who implicitly relied on libav being enabled in their > > profile, and who wish to continue using libav, should enable > > USE=libav in their /etc/portage/make.conf file. No, this is not yet 100% true, or at least not true for some packages, which are also pulling in abi_x86_32 versions. I came across this problem something like a week ago on a PC with no ffmpeg or libav USE flags. I tried setting USE="-libav" and also +ffmpeg, but couldn't fix the blockers. Eventually, I uninstalled the hard blockers like 'media- libs/libpostproc' and then rebuilt any packages already installed which were causing portage to complain/want libav. Can't recall fully which packages these were, k3b springs to mind. There may be a more scientific way of resolving the conflict, but that's how I got around this problem. HTH. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Fri, May 15, 2015 at 9:04 AM, Gevisz wrote: > On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury > wrote: > > > I had a similar problem with some packages wanting virtual/ffmpeg and > > it wouldn't take the -libav USE flag without adding a keyword for > > ~amd64 on the virtual. > > (yes, I am going the opposite way from you, but the cause seem the > > same -- various USE flags are not yet adjusted in the stable > > branches.) > > > > Perhaps we need to request "stabilization" for some of the newer > > packages to solve this. > > Thank you for confirming that libav USE flag do not work not only for me. > > However, it would be interesting to hear what the Gentoo devs think about > this issue. > Portage news item No 19 has the answer you're looking for. > eselect news read 19 > 2015-04-16-ffmpeg-default > Title FFmpeg default > AuthorBen de Groot > Posted2015-04-16 > Revision 1 > > Since the choice between ffmpeg and libav has been made more > explicit, there has been a lot of discussion about what the > default implementation should be. It can be concluded that > media-video/ffmpeg has wider support, and would be somewhat > more convenient for most end-users. > > For this reason the default implementation has been switched > back from media-video/libav to media-video/ffmpeg by removing > the libav useflag from the base profile. > > If the libav useflag is already globally enabled or disabled > in /etc/portage/make.conf, then no further action is required. > > Users who implicitly relied on libav being enabled in their > profile, and who wish to continue using libav, should enable > USE=libav in their /etc/portage/make.conf file. >
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury wrote: > I had a similar problem with some packages wanting virtual/ffmpeg and > it wouldn't take the -libav USE flag without adding a keyword for > ~amd64 on the virtual. > (yes, I am going the opposite way from you, but the cause seem the > same -- various USE flags are not yet adjusted in the stable > branches.) > > Perhaps we need to request "stabilization" for some of the newer > packages to solve this. Thank you for confirming that libav USE flag do not work not only for me. However, it would be interesting to hear what the Gentoo devs think about this issue. > On Fri, May 15, 2015 at 1:18 AM, gevisz wrote: > > After Gentoo devs decided to switch back to ffmpeg default, > > I set libav USE flag at my /etc/portage/make.conf > > and was happy with that so far. :) > > > > However, after yesterday's > > # emerge-webrsync > > # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world > > I've got some blocks that in my view result from the fact that portage wants > > to emerge ffmpeg in addition to libav. (Please, correct me if I am wrong.) > > > > So, my questions, are: > > 1) What is happened? > > 2) Is this behavior desired? (If yes, by whome? :) > > 3) What shall I do with all this? > > > > The full output of the emerge update command is as follows: > > > > These are the packages that would be merged, in order: > > > > Calculating dependencies... done! > > [ebuild R] x11-proto/videoproto-2.3.2 ABI_X86="32*" > > [ebuild R] x11-libs/libXv-1.0.10 ABI_X86="32*" > > [ebuild U ] dev-libs/openssl-1.0.1m [1.0.1l-r1] > > [ebuild U ] dev-db/sqlite-3.8.10.1 [3.8.9] USE="-tools%" > > [ebuild NS] sys-kernel/gentoo-sources-3.18.12 [3.18.11] > > USE="-build -deblob -experimental -symlink" > > [ebuild r U ] media-video/libav-11.3 [9.17] USE="(-armv5te) > > (-armv6) (-armv6t2) (-armvfp) -bs2b% -fontconfig% -twolame% -wavpack% > > -webp% -x265%" CPU_FLAGS_X86="sse%* sse2%* sse3%* -avx2% -fma3% -fma4% > > -sse4_1% -sse4_2% -xop%" > > [ebuild rR] media-video/libav-9.17 > > [ebuild rR] media-libs/libpostproc-10.20140517-r1 > > [ebuild N ] media-video/ffmpeg-2.2.14 USE="X aac alsa bzip2 > > encode hardcoded-tables iconv mp3 network opengl pulseaudio sdl > > truetype vorbis x264 xvid zlib -aacplus (-altivec) -amr -amrenc > > (-armv5te) (-armv6) (-armv6t2) (-armvfp) -bluray -cdio -celt > > -cpudetection -debug -doc -examples -faac -fdk -flite -fontconfig > > -frei0r -gme -gnutls -gsm -iec61883 -ieee1394 -jack -jpeg2k -ladspa > > -libass -libcaca -libsoxr -libv4l (-mips32r2) (-mipsdspr1) > > (-mipsdspr2) (-mipsfpu) -modplug (-neon) -openal -openssl -opus -oss > > -pic -quvi -rtmp -schroedinger -speex -ssh -static-libs {-test} > > -theora -threads -twolame -v4l -vaapi -vdpau -vpx -wavpack -webp -x265 > > -zvbi" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="3dnow 3dnowext mmx > > mmxext sse sse2 sse3 -avx -avx2 -fma3 -fma4 -sse4_1 -sse4_2 -ssse3" > > FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt > > graph2dot ismindex pktdumper qt-faststart trasher" > > [ebuild N ] dev-qt/qtchooser-0_p20150102 USE="(-qt5) {-test}" > > [ebuild U ] dev-qt/qtcore-4.8.6-r2 [4.8.5-r2] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] dev-qt/qttranslations:4 ("dev-qt/qttranslations:4" is > > blocking dev-qt/qtcore-4.8.5-r2) > > [blocks b ] > blocking dev-qt/qtchooser-0_p20150102) > > [ebuild N ] dev-qt/qttranslations-4.8.6-r1 ABI_X86="(64) -32 (-x32)" > > [ebuild U ] dev-qt/qtscript-4.8.6-r2 [4.8.5] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] > is blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qtgui-4.8.6-r4 [4.8.5-r4] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] > blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qtsql-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > > [blocks b ] > blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qt3support-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] > (" > dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qtxmlpatterns-4.8.6-r1 [4.8.5] ABI_X86="(64%*) > > -32% (-x32)" > > [blocks b ] > (" > dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qtdbus-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > > [blocks b ] > blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/designer-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] > is blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qtopengl-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] > is blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qthelp-4.8.6-r3 [4.8.5-r2] ABI_X86="(64%*) -32% > > (-x32)" > > [blocks b ] > blocking dev-qt/qtchooser-0_p20150102) > > [ebuild U ] dev-qt/qtsvg-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > > [blocks b ] > blocking d
Re: [gentoo-user] libav and ffmpeg on the same computer issue once again
I had a similar problem with some packages wanting virtual/ffmpeg and it wouldn't take the -libav USE flag without adding a keyword for ~amd64 on the virtual. (yes, I am going the opposite way from you, but the cause seem the same -- various USE flags are not yet adjusted in the stable branches.) Perhaps we need to request "stabilization" for some of the newer packages to solve this. On Fri, May 15, 2015 at 1:18 AM, gevisz wrote: > After Gentoo devs decided to switch back to ffmpeg default, > I set libav USE flag at my /etc/portage/make.conf > and was happy with that so far. :) > > However, after yesterday's > # emerge-webrsync > # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world > I've got some blocks that in my view result from the fact that portage wants > to emerge ffmpeg in addition to libav. (Please, correct me if I am wrong.) > > So, my questions, are: > 1) What is happened? > 2) Is this behavior desired? (If yes, by whome? :) > 3) What shall I do with all this? > > The full output of the emerge update command is as follows: > > These are the packages that would be merged, in order: > > Calculating dependencies... done! > [ebuild R] x11-proto/videoproto-2.3.2 ABI_X86="32*" > [ebuild R] x11-libs/libXv-1.0.10 ABI_X86="32*" > [ebuild U ] dev-libs/openssl-1.0.1m [1.0.1l-r1] > [ebuild U ] dev-db/sqlite-3.8.10.1 [3.8.9] USE="-tools%" > [ebuild NS] sys-kernel/gentoo-sources-3.18.12 [3.18.11] > USE="-build -deblob -experimental -symlink" > [ebuild r U ] media-video/libav-11.3 [9.17] USE="(-armv5te) > (-armv6) (-armv6t2) (-armvfp) -bs2b% -fontconfig% -twolame% -wavpack% > -webp% -x265%" CPU_FLAGS_X86="sse%* sse2%* sse3%* -avx2% -fma3% -fma4% > -sse4_1% -sse4_2% -xop%" > [ebuild rR] media-video/libav-9.17 > [ebuild rR] media-libs/libpostproc-10.20140517-r1 > [ebuild N ] media-video/ffmpeg-2.2.14 USE="X aac alsa bzip2 > encode hardcoded-tables iconv mp3 network opengl pulseaudio sdl > truetype vorbis x264 xvid zlib -aacplus (-altivec) -amr -amrenc > (-armv5te) (-armv6) (-armv6t2) (-armvfp) -bluray -cdio -celt > -cpudetection -debug -doc -examples -faac -fdk -flite -fontconfig > -frei0r -gme -gnutls -gsm -iec61883 -ieee1394 -jack -jpeg2k -ladspa > -libass -libcaca -libsoxr -libv4l (-mips32r2) (-mipsdspr1) > (-mipsdspr2) (-mipsfpu) -modplug (-neon) -openal -openssl -opus -oss > -pic -quvi -rtmp -schroedinger -speex -ssh -static-libs {-test} > -theora -threads -twolame -v4l -vaapi -vdpau -vpx -wavpack -webp -x265 > -zvbi" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="3dnow 3dnowext mmx > mmxext sse sse2 sse3 -avx -avx2 -fma3 -fma4 -sse4_1 -sse4_2 -ssse3" > FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt > graph2dot ismindex pktdumper qt-faststart trasher" > [ebuild N ] dev-qt/qtchooser-0_p20150102 USE="(-qt5) {-test}" > [ebuild U ] dev-qt/qtcore-4.8.6-r2 [4.8.5-r2] ABI_X86="(64%*) -32% > (-x32)" > [blocks b ] dev-qt/qttranslations:4 ("dev-qt/qttranslations:4" is > blocking dev-qt/qtcore-4.8.5-r2) > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild N ] dev-qt/qttranslations-4.8.6-r1 ABI_X86="(64) -32 (-x32)" > [ebuild U ] dev-qt/qtscript-4.8.6-r2 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] is blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtgui-4.8.6-r4 [4.8.5-r4] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtsql-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qt3support-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% > (-x32)" > [blocks b ] (" dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtxmlpatterns-4.8.6-r1 [4.8.5] ABI_X86="(64%*) > -32% (-x32)" > [blocks b ] (" dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtdbus-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/designer-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] is blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtopengl-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] is blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qthelp-4.8.6-r3 [4.8.5-r2] ABI_X86="(64%*) -32% > (-x32)" > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtsvg-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild rR] media-video/vlc-2.1.5-r1 > [ebuild U ] dev-qt/qttest-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks b ] blocking dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtmultimedia-4.8.6-r1 [4.8.5] ABI_X86="(64%*) > -32% (-x32)" > [blocks b ] (" dev-qt/qtchooser-0_p20150102) > [ebuild U ] dev-qt/qtbearer-4.8.6-r1 [4.8.5] ABI_X86="(64%*) -32% (-x32)" > [blocks
[gentoo-user] libav and ffmpeg on the same computer issue once again
After Gentoo devs decided to switch back to ffmpeg default, I set libav USE flag at my /etc/portage/make.conf and was happy with that so far. :) However, after yesterday's # emerge-webrsync # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world I've got some blocks that in my view result from the fact that portage wants to emerge ffmpeg in addition to libav. (Please, correct me if I am wrong.) So, my questions, are: 1) What is happened? 2) Is this behavior desired? (If yes, by whome? :) 3) What shall I do with all this? The full output of the emerge update command is as follows: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R] x11-proto/videoproto-2.3.2 ABI_X86="32*" [ebuild R] x11-libs/libXv-1.0.10 ABI_X86="32*" [ebuild U ] dev-libs/openssl-1.0.1m [1.0.1l-r1] [ebuild U ] dev-db/sqlite-3.8.10.1 [3.8.9] USE="-tools%" [ebuild NS] sys-kernel/gentoo-sources-3.18.12 [3.18.11] USE="-build -deblob -experimental -symlink" [ebuild r U ] media-video/libav-11.3 [9.17] USE="(-armv5te) (-armv6) (-armv6t2) (-armvfp) -bs2b% -fontconfig% -twolame% -wavpack% -webp% -x265%" CPU_FLAGS_X86="sse%* sse2%* sse3%* -avx2% -fma3% -fma4% -sse4_1% -sse4_2% -xop%" [ebuild rR] media-video/libav-9.17 [ebuild rR] media-libs/libpostproc-10.20140517-r1 [ebuild N ] media-video/ffmpeg-2.2.14 USE="X aac alsa bzip2 encode hardcoded-tables iconv mp3 network opengl pulseaudio sdl truetype vorbis x264 xvid zlib -aacplus (-altivec) -amr -amrenc (-armv5te) (-armv6) (-armv6t2) (-armvfp) -bluray -cdio -celt -cpudetection -debug -doc -examples -faac -fdk -flite -fontconfig -frei0r -gme -gnutls -gsm -iec61883 -ieee1394 -jack -jpeg2k -ladspa -libass -libcaca -libsoxr -libv4l (-mips32r2) (-mipsdspr1) (-mipsdspr2) (-mipsfpu) -modplug (-neon) -openal -openssl -opus -oss -pic -quvi -rtmp -schroedinger -speex -ssh -static-libs {-test} -theora -threads -twolame -v4l -vaapi -vdpau -vpx -wavpack -webp -x265 -zvbi" ABI_X86="32 (64) (-x32)" CPU_FLAGS_X86="3dnow 3dnowext mmx mmxext sse sse2 sse3 -avx -avx2 -fma3 -fma4 -sse4_1 -sse4_2 -ssse3" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart trasher" [ebuild N ] dev-qt/qtchooser-0_p20150102 USE="(-qt5) {-test}" [ebuild U ] dev-qt/qtcore-4.8.6-r2 [4.8.5-r2] ABI_X86="(64%*) -32% (-x32)" [blocks b ] dev-qt/qttranslations:4 ("dev-qt/qttranslations:4" is blocking dev-qt/qtcore-4.8.5-r2) [blocks b ] =media-video/libav-9.12:0/9=[abi_x86_64(-)] required by (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3:0.10/0.10::gentoo, installed) ^ =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?] (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-),abi_x86_64(-),X,encode,mp3,sdl,truetype,x264]) required by (virtual/ffmpeg-9-r1:0/0::gentoo, installed) (media-libs/libpostproc-10.20140517-r1:0/0::gentoo, ebuild scheduled for merge) pulled in by media-libs/libpostproc:0 required by @__auto_slot_operator_replace_installed__ media-libs/libpostproc:0= required by (media-video/vlc-2.1.5-r1:0/5-7::gentoo, ebuild scheduled for merge) >=media-libs/libpostproc-10.20140517-r1:0=[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?] (>=media-libs/libpostproc-10.20140517-r1:0=[abi_x86_64(-)]) required by (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3:0.10/0.10::gentoo, installed) >=media-libs/libpostproc-10.20140517-r1:0/0=[abi_x86_64(-)] required by (media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3:0.10/0.10::gentoo, installed) For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): https://wiki.gentoo.org/wiki/Handbook:X86/Working/Portage#Blocked_packages The following packages are causing rebuilds: (media-video/libav-11.3:0/11::gentoo, ebuild scheduled for merge) causes rebuilds for: (media-libs/libpostproc-10.20140517-r1:0/0::gentoo, ebuild scheduled for merge) (media-video/vlc-2.1.5-r1:0/5-7::gentoo, ebuild scheduled for merge) The following USE changes are necessary to proceed: (see "package.use" in the portage(5) man page for more details) # required by virtual/ffmpeg-9-r1::gentoo # required by media-plugins/alsa-plugins-1.0.28::gentoo # required by media-sound/pulseaudio-5.0-r7::gentoo[alsa-plugin,alsa] # required by media-video/libav-9.17::gentoo[pulseaudio] # required by @__auto_slot_operator_replace_installed__ (argument) >=media-video/ffmpeg-2.2.14 abi_x86_32 # required by x11-libs/libXv-1.0.10::gentoo # required by media-video/ffmpeg-2.