dm-writeboost 2.1.1-1ubuntu1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2

[Andy Whitcroft]

Testing failed on:
    amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/d/dm-writeboost/20170710_033146_b2be1@/log.gz
    armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/d/dm-writeboost/20170710_033525_b2be1@/log.gz
    i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/d/dm-writeboost/20170710_033208_b2be1@/log.gz
    ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/d/dm-writeboost/20170710_033322_b2be1@/log.gz
    s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/d/dm-writeboost/20170710_033100_b2be1@/log.gz

[Adam Conrad (adconrad)]

Hello Andy, or anyone else affected,

Accepted dm-writeboost into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dm-writeboost/2.2.6-1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Adam Conrad (adconrad)]

apw claimed on IRC that he verified this.

[Launchpad Janitor (janitor)]

This bug was fixed in the package dm-writeboost - 2.2.6-1~16.04.1

---------------
dm-writeboost (2.2.6-1~16.04.1) xenial; urgency=low

  * Backport to xenial to support linux-hwe 4.10 kernels.
    (LP: #1704280)

dm-writeboost (2.2.6-1) unstable; urgency=medium

  * New upstream release [September 2016].
    + fixed FTBFS with Linux 4.8 (Closes: #838547).

dm-writeboost (2.2.5-1) unstable; urgency=medium

  * New upstream release [September 2016].

dm-writeboost (2.2.4-1) unstable; urgency=medium

  * New upstream release [August 2016].

dm-writeboost (2.2.3-1) unstable; urgency=medium

  * New upstream release [August 2016].

dm-writeboost (2.2.1-1) unstable; urgency=medium

  * New upstream release [July 2016].
  * Vcs-Git URL to HTTPS.

dm-writeboost (2.2.0-1) unstable; urgency=medium

  * New upstream release [May 2016].
  * Standards-Version: 3.9.8.

dm-writeboost (2.1.2-1) unstable; urgency=medium

  * New upstream release [March 2016].
  * Standards-Version: 3.9.7.

 -- Andy Whitcroft <email address hidden> Fri, 14 Jul 2017 12:07:17 +0100

[Adam Conrad (adconrad)]

The verification of the Stable Release Update for dm-writeboost has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.