The problem is rather the opposite; the aufs in the kernel is newer than
the synced aufs-tools. And I just recently found out that aufs for 5.x
kernels is hosted in a different git repository, which explains why we
haven't been seeing any tags for 5.x kernels (and thus the version is
still 4.x-rcN).

For focal then we likely need to update aufs-tools from
and update aufs-tools every time we update the kernel support. However, if the 
tools and kernel support really are version locked as this build error implies, 
that seems to pose a problem for hwe kernels.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  aufs-tools 4.14 FTBFS because of wrong SAUCE driver in the kernel

Status in linux package in Ubuntu:

Bug description:
  The latest aufs-tools package synced from Debian fails to build in
  Ubuntu (but not in Debian) because the Ubuntu kernel package has aufs
  sauce patches and they are not at a compatible version.

          install -d /<<BUILDDIR>>/aufs-tools-4.14\+20190211/debian/aufs-tools
          make -j4 install 
AM_UPDATE_INFO_DIR=no "INSTALL=install --strip-program=true"
  make[1]: Entering directory '/<<BUILDDIR>>/aufs-tools-4.14+20190211'
  cc -g -O2 -fdebug-prefix-map=/<<BUILDDIR>>/aufs-tools-4.14+20190211=. 
-fstack-protector-strong -Wformat -Werror=format-security -O -Wall -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -I./libau -DAUFHSM_CMD=\"/usr/bin/aufhsm\" 
-DMOUNT_CMD=\"/bin/mount\" -DUMOUNT_CMD=\"/bin/umount\" 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now  ver.c   -o ver
  Wrong version!
  aufs-util for aufs4.14 20190211, but aufs is 4.x-rcN-20190805.
  See README in detail and try git branch -a.
  make[1]: *** [Makefile:120: ver_test] Error 255
  rm ver


  Please either update the aufs patches in the kernel tree, or else drop

  (My understanding is that we probably don't want to drop them because
  docker may use aufs as a backend; and while this is deprecated, there
  is currently no upgrade story for users currently using it.)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to