search for: libverto

...= 2.17-55.el7 for package: glibc-debuginfo-2.17-55.el7.x86_64 ---> Package keyutils-debuginfo.x86_64 0:1.5.8-3.el7 will be installed ---> Package krb5-debuginfo.x86_64 0:1.11.3-49.el7 will be installed ---> Package libselinux-debuginfo.x86_64 0:2.2.2-6.el7 will be installed ---> Package libverto-debuginfo.x86_64 0:0.2.5-4.el7 will be installed ---> Package nss-softokn-debuginfo.x86_64 0:3.15.4-2.el7 will be installed ---> Package openssl-debuginfo.x86_64 1:1.0.1e-34.el7_0.4 will be installed ---> Package pcre-debuginfo.x86_64 0:8.32-12.el7 will be installed ---> Package xz-debu...

...ompiled against the > tevent_internal.h of the tevent version that is later installed. Again - I compiled Samba against tevent-0.9.30. Did a "make uninstall" of Samba, uninstalled the working tevent-0.9.29, installed tevent-0.9.30 and then rebuilt other packages that depend on tevent (libverto, ldb, sssd). Then for Samba did a "make clean" and "make distclean", followed by "configure", "make", and "make install". Result? Samba crashes - both nmbd and smbd dump core. I've repeated the above steps many times, Samba fails with tevent-0....

...y this > > apt-get -s remove krb5-kdc > > This will prove one way or other if it is installed and what it wants to > remove along with it, it will not remove anything. Apparently nothing requires it: The following packages were automatically installed and are no longer required: libverto-libevent1 libverto1 Use 'apt autoremove' to remove them. The following packages will be REMOVED: krb5-kdc 0 upgraded, 0 newly installed, 1 to remove and 21 not upgraded. Remv krb5-kdc [1.16-2ubuntu0.1] I checked in apt history log and the package was installed manually, it's in the...

...tevent_internal.h of the tevent version that is later installed. > > Again - I compiled Samba against tevent-0.9.30. > Did a "make uninstall" of Samba, uninstalled the working > tevent-0.9.29, installed tevent-0.9.30 and then rebuilt other packages > that depend on tevent (libverto, ldb, sssd). Then for Samba did a > "make clean" and "make distclean", followed by "configure", "make", > and "make install". > Result? Samba crashes - both nmbd and smbd dump core. > > I've repeated the above steps many times, S...

...-s remove krb5-kdc >> >> This will prove one way or other if it is installed and what it wants to >> remove along with it, it will not remove anything. > Apparently nothing requires it: > The following packages were automatically installed and are no longer required: > libverto-libevent1 libverto1 > Use 'apt autoremove' to remove them. > The following packages will be REMOVED: > krb5-kdc > 0 upgraded, 0 newly installed, 1 to remove and 21 not upgraded. > Remv krb5-kdc [1.16-2ubuntu0.1] Please remove it, you do not need it. Do you know that you...

Also see: https://bugs.gentoo.org/show_bug.cgi?id=592502 On Tue, Sep 6, 2016 at 9:28 AM, Sonic <sonicsmith at gmail.com> wrote: > On Tue, Sep 6, 2016 at 5:16 AM, Volker Lendecke <vl at samba.org> wrote: >> When you build, please have the correct header and -dev libs around >> that you will later use. > > In most cases there are no separate dev packages in Gentoo,

...\ perl-Time-Local perl-threads-shared perl-File-Path perl-Scalar-List-Utils \ perl-Getopt-Long libcap-ng nss-softokn libassuan libunistring diffutils gpm-libs \ libnfnetlink keyutils-libs gettext-libs p11-kit-trust nettle \ gobject-introspection vim-minimal pinentry make libselinux-utils ncurses \ libverto libsemanage krb5-libs openldap cracklib libmount systemd-libs libuser \ pam libblkid util-linux python-libs dhcp-libs libcurl python-urlgrabber rpm-libs \ dhcp-common libselinux-python python-iniparse python-chardet yum-metadata-parser \ python-backports-ssl_match_hostname newt-python pyxattr binut...

> Not sure, but that is the way it looks, just a thought, are you using > sssd ? no, not even installed > Just like a normal share, '[homes]' is a special share that doesn't use > 'path. There used to be something on the wiki about using '[home]' on a > DC, I didn't know it had gone until you mentioned it ;-) So if I use [home] it would be a normal

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...