This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1851447

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

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

  aufs-tools 4.9 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