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] Net problems
On Thursday 14 May 2015 07:34:41 meino.cra...@gmx.de wrote: > This is what udevadm monitor prints, when I unplug both Ariettas > simultanously: > solfire:/home/mccramer>udevadm monitor > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[13781.884965] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/rx-0 > (queues) KERNEL[13781.885027] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/tx-0 > (queues) KERNEL[13781.885067] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1 (net) UDEV > [13781.886418] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/rx-0 > (queues) KERNEL[13781.889122] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0 (usb) > KERNEL[13781.889194] remove /devices/pci:00/:00:13.2/usb4/4-4 > (usb) UDEV [13781.902185] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/tx-0 > (queues) UDEV [13781.908021] remove > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1 (net) UDEV > [13781.908429] remove /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0 > (usb) UDEV [13781.919474] remove > /devices/pci:00/:00:13.2/usb4/4-4 (usb) KERNEL[13781.993142] > remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/rx-0 > (queues) KERNEL[13781.993182] remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/tx-0 > (queues) KERNEL[13781.993211] remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0 (net) UDEV > [13781.993928] remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/rx-0 > (queues) UDEV [13781.994215] remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/tx-0 > (queues) KERNEL[13781.998111] remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0 (usb) > KERNEL[13781.998170] remove /devices/pci:00/:00:13.2/usb4/4-5 > (usb) UDEV [13782.000177] remove > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0 (net) UDEV > [13782.000767] remove /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0 > (usb) UDEV [13782.013093] remove > /devices/pci:00/:00:13.2/usb4/4-5 (usb) > > > This is printed, when I connect the first Arietta to the PC: > > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[14000.140611] add /devices/pci:00/:00:13.2/usb4/4-5 > (usb) KERNEL[14000.141572] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0 (usb) > KERNEL[14000.141967] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0 (net) > KERNEL[14000.142000] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/rx-0 > (queues) KERNEL[14000.142046] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/tx-0 > (queues) UDEV [14000.162311] add > /devices/pci:00/:00:13.2/usb4/4-5 (usb) UDEV [14000.163727] add >/devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0 (usb) UDEV > [14000.170206] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0 (net) UDEV > [14000.170572] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/rx-0 > (queues) UDEV [14000.185482] add > /devices/pci:00/:00:13.2/usb4/4-5/4-5:1.0/net/usb0/queues/tx-0 > (queues > > > This is printed, when I connect the second Arietta to the PC: > > monitor will print the received events for: > UDEV - the event which udev sends out after rule processing > KERNEL - the kernel uevent > > KERNEL[14108.192714] add /devices/pci:00/:00:13.2/usb4/4-4 > (usb) KERNEL[14108.193781] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0 (usb) > KERNEL[14108.194211] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1 (net) > KERNEL[14108.194247] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/rx-0 > (queues) KERNEL[14108.194269] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/tx-0 > (queues) UDEV [14108.211967] add > /devices/pci:00/:00:13.2/usb4/4-4 (usb) UDEV [14108.213327] add >/devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0 (usb) UDEV > [14108.217344] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1 (net) UDEV > [14108.217615] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/rx-0 > (queues) UDEV [14108.237237] add > /devices/pci:00/:00:13.2/usb4/4-4/4-4:1.0/net/usb1/queues/tx-0 > (queues) > > > The assigment to certain USB ports may vary from time to time. > > > This is what lsusb prints for both devices > > > Bus 004 Device 007: ID 0525:a4a2 Netchip Technology, Inc. Linux-USB > Ethernet/RNDIS Gadget Device Descriptor: > bLength1
[gentoo-user] Re: udev hanging
On 05/14/2015 10:56 PM, Raffaele BELARDI wrote: > I have an amd64 system with an old 3.3.x kernel. Recently (I think after > last udev update to 217) the boot process became very slow due to "udev > waiting for uevents to populate /dev". After a minute or so udev prints > something about a lazy device (a TV tuner) then the boot continues. > > Yesterday I tried to update the kernel to 4.0.2... That kernel version is marked ~amd64 (unstable/testing). Are you accepting the ~amd64 keyword in your make.conf? If you ask for help in this group you should include that info as part of your question. You'll get better answers if you do. Just as important in the last year or so is whether you are using systemd or openrc at boot time. Life never gets simpler over time :(
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. >
