| Summary: | net-fs/samba-4.4.2 automagic dependency on dev-libs/libaio | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Timo Gurr (RETIRED) <tgurr> |
| Component: | [OLD] Server | Assignee: | Gentoo's SAMBA Team <samba> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | bkohler, netbox253 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Confirming this. Building samba-4.2.11 package on a build farm with USE="-aio" but with dev-libs/libaio installed, then emerging the samba tbz2 package on clients systems on the local network results in : > # revdep-rebuild -i -- -avk > * Configuring search environment for revdep-rebuild > > * Checking reverse dependencies > * Packages containing binaries and libraries broken by a package update > * will be emerged. > * Collecting system binaries and libraries > * Generated new 1_files.rr > * Collecting complete LD_LIBRARY_PATH > * Generated new 2_ldpath.rr > * Checking dynamic linking consistency > [ 83% ] * broken /usr/lib64/samba/vfs/aio_linux.so (requires libaio.so.1) > [ 100% ] Actually, this "bug" is the only thing which makes it possible to use the aio_linux VFS modul sincs the aio useflag disappeared for the recent (~amd64) samba ebuilds (which used to pull in libaio). I think somebody misinterpreted the Samba changelog about dropping the POSIX AIO support. That was a different thing (I don't even know if the POSIX AIO solution really required libaio or not, I never tried to use that one) but this kernel call based custom VFS module (which is still available in Samba 4.5) actually depends on libaio. So, if you want Samba to be fully functional (including the aio_linux VFS module), all you can do is manually emerging libaio and let samba passively (not explicitly guided by relevant useflag) find it. I think the aio useflag should be restored (to support aio_linux) and only then this bug should be fixed (to really kill aio if it's actually desired). All current samba ebuild depend directly on libaio |
When libaio is around during build time samba links to it: >>> package: dev-libs/libaio-0.3.110 * - /lib/libaio.so.1 * - /lib/libaio.so.1.0.1 * used by /usr/lib/samba/vfs/aio_linux.so (net-fs/samba-4.4.2) I could observe this problem on different systems, samba is build with: [ebuild R #] net-fs/samba-4.4.2::gentoo USE="acl addns ads gnutls ldap pam system-mitkrb5 winbind -addc -avahi -client -cluster -cups -dmapi -fam -iprint -quota (-selinux) -syslog -systemd {-test}" PYTHON_TARGETS="python2_7" 0 KiB