2015-05-16 10:51 GMT+03:00 gevisz <gev...@gmail.com>: > 2015-05-16 9:44 GMT+03:00 Alan McKinnon <alan.mckin...@gmail.com>: >> On 16/05/2015 07:52, gevisz wrote: >>> 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk <alexander.kaps...@gmail.com>: >>>> On Fri, May 15, 2015 at 9:04 AM, Gevisz <gev...@gmail.com> wrote: >>>>> >>>>> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury <redwo...@gmail.com> >>>>> 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 >>>>> Author Ben de Groot <yng...@gentoo.org> >>>>> Posted 2015-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 context menu >>> - - networkmanager : Enable net-misc/networkmanager support >>> + + pdf : Add general support for PDF (Portable >>> Document Format), this replaces the pdflib and cpdflib flags >>> - - playlist : Add support for playlists >>> - - rss : Enable support for RSS feeds >>> - - test : Workaround to pull in packages needed to run >>> with FEATURES=test. Portage-2.1.2 handles this internally, so don't >>> set it in >>> make.conf/package.use anymore >>> - - thunderbird : Install email data miner plugin for >>> mail-client/thunderbird and mail-client/thunderbird-bin >>> + + tiff : Add support for the TIFF image format >>> - - upnp-av : Enable UPnP audio/video streaming support >>> + + upower : Enable power management support >>> + + vorbis : Add support for the OggVorbis audio codec >>> + + xml : Add support for XML files >>> - - xmp : Enable support for Extensible Metadata >>> Platform (Adobe XMP) >>> - - xps : Add support for XPS file format through >>> app-text/libgxps. >>> >>> >>> That, in my view, means that the tracker package really should not >>> demand ffmpeg. >>> >> >> >> Just checking something. >> >> app-misc/tracker does NOT depends on ffmpeg. It depends on >> virtual/ffmpeg, which libav satisfies. I think you are chasing a red >> haerring with that one. >> >> Did you notice? > > Yes, you are right about the tracker package. > > However, portage wants to emerge media-video/ffmpeg-2.2.14 and > > $ equery depends media-video/ffmpeg-2.2.14 > * These packages depend on media-video/ffmpeg-2.2.14: > media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) > 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-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?]) > > So, more general questions remain relevant. > > P.S. I guess that the situation has something to do with the fact > that I have a multilib profile (on amd64) and have chosen > to enable abi_x86_32 on per package base. > > Probably, after portage-tree update, portage cannot find the > needed x86_32 libraries and decides to emerge media-video/ffmpeg > instead. > > 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.
