vfs snapper is being tried to be built by default. If this is not possible then it says that you can do:
vfs_snapper is enabled but prerequisite DBUS libraries or headers not found. Use --disable-snapper to disable vfs_snapper support.
(complete log in /home/samba/v4-13/bin/config.log)
But the right way to disable a vfs module is the configure option --with-shared-modules=!vfs_snapper - if you use that configre option, then the configure check still fails with above message.
The option --disable-snapper needs to be removed and the standard "!modulename" method needs to be fixed for vfs_snapper before 4.13.0
this boild down do revert the commit, that introduced all this:
Author: Matt Taylor <firstname.lastname@example.org>
Date: Mon May 11 15:26:41 2020 -0400
build: add configure option to control vfs_snapper build
vfs_snapper is currently built if dbus development headers / libraries
are detected during configure. This commit adds new --disable-snapper
and --enable-snapper (default) configure parameters. When enabled,
configure will fail if the dbus development headers / libraries are
Signed-off-by: Matt Taylor <email@example.com>
Reviewed-by: David Disseldorp <firstname.lastname@example.org>
Reviewed-by: Andrew Bartlett <email@example.com>
With that reverted, we get the intended consistency.
This bug has been discussed on the mailing list:
The current plan is to fix --with-shared-modules=!vfs_snapper behaviour and drop --disable-snapper/--enable-snapper, while avoiding the reintroduction of "automagic" configure functionality. I'll try to get around to this later this week.
I don't have the oportunity to participate in that discussion within the next two weeks. For now I can say that I i object to make more options force enabled (not auto-enabled) by default unless the specific feature is available on all platforms (Lunux, FreeBSD, AIX and Solaris) also.
Created attachment 16197 [details]
cherry-pick for v4-13-test
This bug was referenced in samba v4-13-test:
Pushed to v4-13-test.
Re-assigning to David as there might be another longterm fix.
(In reply to Karolin Seeger from comment #6)
> Pushed to v4-13-test.
> Re-assigning to David as there might be another longterm fix.
I don't plan on making any changes to the fix now in master. Please reopen if something comes up. Closing...
This bug was referenced in samba v4-13-stable: