kernel-packages team mailing list archive

[Timo Aaltonen <tjaalton@xxxxxxxxxx>]

Hello Martin, or anyone else affected,

Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04.2 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 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 to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  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!

** Changed in: dkms (Ubuntu Trusty)
       Status: Triaged => Fix Committed

** Tags added: verification-needed

** Changed in: dkms (Ubuntu Precise)
       Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1489045

Title:
  Backport autopkgtest script to precise/trusty

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Committed

Bug description:
  The kernel team has requested that we run DKMS tests via autopkgtests
  for precise and trusty the same way that we now do for vivid and
  upwards. For this we need to backport debian/scripts/dkms-autopkgtest
  from https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu1.

  TEST CASE:
   Run autopkgtest for a DKMS package:

     adt-run bcmwl --- qemu adt-trusty-amd64-cloud.img   # or use a
  precise image, or "--- lxc <container-name>"

  This currently fails with

     adt-run [15:18:24]: test command1: /usr/lib/dkms/dkms-autopkgtest
     adt-run [15:18:24]: test command1: [-----------------------
     bash: /usr/lib/dkms/dkms-autopkgtest: No such file or directory

  With the proposed packages this should work and look more like

  Setting up bcmwl-kernel-source (6.30.223.248+bdcom-0ubuntu4) ...
  Loading new bcmwl-6.30.223.248+bdcom DKMS files...
  First Installation: checking all kernels...
  Building only for 4.1.0-3-generic
  Building for architecture x86_64
  Building initial module for 4.1.0-3-generic
  Done.

  wl:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/4.1.0-3-generic/updates/dkms/

  depmod....

  DKMS: install completed.
  update-initramfs: deferring update (trigger activated)
  Setting up libfakeroot:amd64 (1.20.2-1ubuntu1) ...
  Setting up fakeroot (1.20.2-1ubuntu1) ...
  update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode
  Setting up manpages-dev (3.74-1ubuntu1) ...
  Processing triggers for initramfs-tools (0.120ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.1.0-3-generic
  I: Testing binary package bcmwl-kernel-source
  I: Testing if bcmwl modules are correctly installed
  bcmwl, 6.30.223.248+bdcom, 4.1.0-3-generic, x86_64: installed
  adt-run [17:23:43]: test command1: -----------------------]

  REGRESSION POTENTIAL: Almost zero. dkms is an arch: all package, thus
  no miscompilation possible. The new script is not being used in dkms'
  actual operation, only when being invoked through autopkgtest. As
  every DKMS package test fails right now, there is no test regression
  possible either.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1489045/+subscriptions