similar to: glib2 head file error when build libvirt with wireshark support

On Mon, Feb 15, 2016 at 03:05:00AM -0500, Han Han wrote: >I compile the latest libvirt from fedora rawhide, but failed. >The version of my software: >wireshark-devel-2.0.1-2.fc24.x86_64 >glib2-2.47.5-2.fc24.x86_64 >gcc-5.1.1-4.fc23.x86_64 >binutils-2.26-10.fc24.x86_64 > Can you post the output of: pkg-config --print-requires wireshark If it does not output glib-2.0 and

On Mon, Feb 15, 2016 at 10:40:11AM +0100, Martin Kletzander wrote: > On Mon, Feb 15, 2016 at 03:05:00AM -0500, Han Han wrote: > >I compile the latest libvirt from fedora rawhide, but failed. > >The version of my software: > >wireshark-devel-2.0.1-2.fc24.x86_64 > >glib2-2.47.5-2.fc24.x86_64 > >gcc-5.1.1-4.fc23.x86_64 > >binutils-2.26-10.fc24.x86_64 > >

On 20.12.2015 09:55, poma wrote: > ... > > Syslinux MultiFS test: > > - QEMU/KVM SeaBIOS: PASSED > - Bare-metal BIOS: FAILED [1] > - OVMF: FAILED [2] > - Bare-metal UEFI: not tested > > > [1] stalled: > Loading (hd3,2)/vmlinuz-4.3.2-200.fc22.x86_64... > > > [2] "failed: No such file or directory" > >

Hi folks I use libvirt to programmatically spawn lxc containers I am facing an issue when migrating from fedora23 to fedora24 I use the stock kernel and libvirt version on both deployments, i.e.: f23: libvirt-1.2.18.3-2.fc23.x86_64 - kernel 4.5.7-202.fc23.x86_64 f24: libvirt-1.3.3.1-4.fc24.x86_64 - kernel 4.6.3-300.fc24.x86_64 First off, I need to outline that the host installation is done

Does anyone know if there are any plans to update the dahdi-linux kernel module code? It no longer compiles with recent kernels, and the last release of dahdi-linux appears to have been around March of 2016. I am currently running 4.6.3-300.fc24.x86_64 (on a Fedora system obviously) and the dahdi-linux-complete-2.11.1+2.11.1 release builds and runs under this kernel, but if I try to build it under

Hi All, I have a freshly installed CentOS 5.3, x86_64 system -- just the Base package selection (via custom packages selection), and nothing else. Immediately after install (no updates), here's what's in the RPM db: [root at dev ~]# rpm -qa | grep -i glib2 glib2-2.12.3-2.fc6 glib2-2.12.3-2.fc6 [root at dev ~]# I have two questions about this: (1) Should this package be

https://bugzilla.netfilter.org/show_bug.cgi?id=845 Summary: checking for LIBNFNETLINK... configure: error: Package requirements (libnfnetlink >= 0.0.41) were not met: Product: libnetfilter_queue Version: unspecified Platform: i386 OS/Version: RedHat Linux Status: NEW Severity: normal

nouveau_drv_video.so - what should it be? https://koji.fedoraproject.org/koji/buildinfo?buildID=722316 ... 0.7.4-13 - Revert symlinks - should be handled by mesa rhbz#1271842 https://bugzilla.redhat.com/show_bug.cgi?id=1271842 ... 0.7.4-12 - Add symlinks for radeonsi,r600,nouveau - rhbz#1264499 https://bugzilla.redhat.com/show_bug.cgi?id=1264499 $ rpm -q

> I also sent (off-list) a bootable floppy image to GeneC, using binaries > from Fedora 24, package version "6.03-6" (coincidentally), and a simple > syslinux.cfg, replicating the behavior. > Testing with: _ 6.03-8.fc24 : still the same unwanted behavior as 6.03-6.fc24; _ 6.04-0.1.fc25: works correctly (regarding this matter). I still think that distributions using

I'm using an image (Fedora cloud) which apparently doesn't have iSCSI kernel module available as-is. I therefore need to update kernel-core in order to get it. Is there a way I can do it via virt-sysprep / virt-customize? I would like on the first boot already to use iSCSI (I'm using a script there to already login to a target, etc.), so first boot (+ it'll require an additional

Hi Fi, cmdline: console=hvc0 systemd.wants=getty at hvc0 Connect via virt-manager - View / Text Consoles / Text Console no.: Fedora 24 (Rawhide) Kernel 4.3.0-0.rc3.git2.4.fc24.x86_64 on an x86_64 (hvc0) localhost login: root Last login: Fri Oct 2 17:28:36 on hvc0 # tty /dev/hvc0 # systemctl status getty at hvc0.service ? getty at hvc0.service - Getty on hvc0 Loaded: loaded

Hi All, Fedora Core 24, x64 samba-4.4.5-1.fc24.x86_64 smbclient -L 127.0.0.1 is very, very slow. It comes back correctly, but takes 20 seconds. One another Samba server (Scientific Linux 7.2), it comes back in under a second. What am I doing wrong? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows

Hi All, Fedora Core 24, x64 samba-4.4.5-1.fc24.x86_64 Does Samba require a DNS controller? Many thanks, -T -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Fri, 19 Aug 2016 23:40:45 -0700 ToddAndMargo via samba <samba at lists.samba.org> wrote: > On 08/16/2016 12:52 AM, ToddAndMargo via samba wrote: > > Hi All, > > > > Fedora Core 24, x64 > > samba-4.4.5-1.fc24.x86_64 > > > > smbclient -L 127.0.0.1 > > > > is very, very slow. It comes back correctly, but takes 20 seconds. > > One

>From josv on IRC: > Hi! I am on Fedora 25 and installed libguestfs (1.36.2) from the > fedora repo. It seems that the squashfs feature is missing in this > installation (guestfish add-drive /dev/null : run : available squashfs > returns "error: squashfs: group not available"). What would be the > recommended way to have the squashfs feature available? $ guestfish -a

CentOS Errata and Bugfix Advisory 2014:0303 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0303.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: aafb14e964ab0725444d7cc5db5d157f5885015d1167678b7a7346ffdf3f31c1 glib2-2.26.1-7.el6_5.i686.rpm 961c916b174af5f8bf7a0cce67510effc5bdeba507060ee672fcf277b381252c

CentOS Errata and Bugfix Advisory 2019:1331 Upstream details at : https://access.redhat.com/errata/RHBA-2019:1331 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: c879b30359b2bcc25b573366ad19d9178780c0b53f241bb8c2435d3abec9d03e glib2-2.56.1-4.el7_6.i686.rpm 7aa639af3fe28bbbdb7c89b5deca96bbfcd18766c224f0f44e5fc97e49438fc4

CentOS Errata and Bugfix Advisory 2020:5048 Upstream details at : https://access.redhat.com/errata/RHBA-2020:5048 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 6c21b000ed4eaee655f575de1d380dded8d228f9631df396279ba89debbe6fae glib2-2.56.1-8.el7.i686.rpm e3c6ac455f3f655e70629ab69610a70ab4f4e55490536ec08dc32ec06031f28b

Hi All, Fedora Core 24, x64 samba-4.4.5-1.fc24.x86_64 I am using the following direction to set up SELinux with Samba: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Confined_Services/sect-Managing_Confined_Services-Samba-Configuration_examples.html to set up SELinux with Samba 1) I created a directory called /export # ls -al /export total 28

4.1.8-200.fc22.x86_64 dmesg: [ 11.809467] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x098200a2 [ 11.809493] nouveau [ DEVICE][0000:02:00.0] Chipset: G98 (NV98) [ 11.809508] nouveau [ DEVICE][0000:02:00.0] Family : NV50 4.3.0-0.rc4.git0.1.fc24.x86_64 dmesg: [ 2.483843] nouveau 0000:02:00.0: NVIDIA G98 (098200a2) Where vanished these Chipset & Family super cool lines?