similar to: Bug#813678: blktap-dkms: fails to build with mainline 4.4 based kernels

Package: blktap-dkms Version: 2.0.93-0.3 Severity: serious Tags: sid stretch User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to build a kernel module for the current sid kernel: Setting up blktap-dkms (2.0.93-0.3) ... Loading new blktap-2.0.93 DKMS files... First Installation: checking all kernels... dpkg: warning: version

Package: blktap-dkms Version: 2.0.93-0.2 Severity: serious Justification: fails to build from source (but built successfully in the past) The build fails on 3.14 kernel with the following error: /var/lib/dkms/blktap/2.0.93/build/ring.c: In function ?blktap_ring_make_tr_request?: /var/lib/dkms/blktap/2.0.93/build/ring.c:314:32: error: ?struct bio? has no member named ?bi_sector?

Package: blktap-dkms Version: 2.0.93-0.1 Severity: serious Justification: fails to build from source (but built successfully in the past) blktap fails to build on kernel 3.13 and probably older kernels as well. According to this bug: https://bugs.launchpad.net/ubuntu/+source/blktap-dkms/+bug/1245009 VM_RESERVED is deprecated as of 3.7. Building with the patch described in that bug allows for

tags 742515 + patch tags 742515 + pending thanks Dear maintainer, I've prepared an NMU for blktap-dkms (versioned as 2.0.93-0.2) and uploaded it directly to the archive as discussed on IRC. Regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: blktap-dkms-2.0.93-0.2-nmu.diff Type: text/x-diff Size: 2499 bytes Desc: not available URL:

Package: blktap-dkms Version: 2.0.93-0.10 Severity: serious User: debian-qa at lists.debian.org Usertags: piuparts Hi, blktap-dkms fails to build a module for Linux 4.12: Selecting previously unselected package blktap-dkms. (Reading database ... 34976 files and directories currently installed.) Preparing to unpack .../blktap-dkms_2.0.93-0.10_amd64.deb ... Unpacking blktap-dkms (2.0.93-0.10) ...

Package: wnpp Severity: wishlist Owner: Debian Xen Team <pkg-xen-devel at lists.alioth.debian.org> * Package name : blktap-dkms Version : 2.0.90 Upstream Author : Jon Ludlam <jonathan.ludlam at eu.citrix.com> * URL : http://www.xen.org/ * License : GPL-2 Programming Lang: C Description : Xen blktap kernel component DKMS package This package

Package: blktap-dkms Version: 2.0.91-1 Severity: important User: debian-qa at lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean

Package: blktap-dkms Version: 2.0.91-1 Severity: normal After an update of the kernel in SID, I have noticed that blktap-dkms didn't automatically rebuild itself when I upgraded my server with a newer kernel version. My understanding is that it should have. Also, doing dpkg-reconfigure blktap-dkms or reinstalling the package did make it rebuild the kernel module. Thomas Goirand (zigo) --

blktap-dkms 2.0.93-0.5 is marked for autoremoval from testing on 2016-03-24 It is affected by these RC bugs: 813678: blktap-dkms: fails to build with mainline 4.4 based kernels

Package: blktap-dkms Version: 2.0.91-2 X-Debbugs-CC: wzssyqa at gmail.com This package has one or more -L/usr/lib in its build system, which will make it ftbfs if there is libraries under /usr/lib, while is not the default architecture, mips* for example. On mips* systems, /usr/lib is defined as place to hold O32 libraries, and /usr/lib32 for N32, and /usr/lib64 is for N64. Beside the way, on

FYI: The status of the blktap-dkms source package in Debian's testing distribution has changed. Previous version: 2.0.93-0.1 Current version: 2.0.93-0.2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more

FYI: The status of the blktap-dkms source package in Debian's testing distribution has changed. Previous version: 2.0.93-0.2 Current version: 2.0.93-0.3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more

FYI: The status of the blktap-dkms source package in Debian's testing distribution has changed. Previous version: 2.0.93-0.3 Current version: 2.0.93-0.4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more

FYI: The status of the blktap-dkms source package in Debian's testing distribution has changed. Previous version: 2.0.93-0.4 Current version: 2.0.93-0.5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more

FYI: The status of the blktap-dkms source package in Debian's testing distribution has changed. Previous version: 2.0.93-0.5 Current version: 2.0.93-0.6 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more

FYI: The status of the blktap-dkms source package in Debian's testing distribution has changed. Previous version: 2.0.91-2 Current version: 2.0.93-0.1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See http://release.debian.org/testing-watch/ for more

blktap-dkms 2.0.93-0.1 is marked for autoremoval from testing on 2014-05-07 It is affected by these RC bugs: 742515: blktap-dkms: blktapblktap kernel module failed to build

blktap-dkms 2.0.93-0.1 is marked for autoremoval from testing on 2014-05-28 It is affected by these RC bugs: 742515: blktap-dkms: blktapblktap kernel module failed to build

blktap-dkms 2.0.93-0.3 is marked for autoremoval from testing on 2015-11-27 It is affected by these RC bugs: 801768: blktap-dkms: module FTBFS for Linux 4.2: error: too many arguments to function 'mempool_resize'

My OQO boxes have the AR5413 wifi chipset, so for the first time in quite a while, I again need to run madwifi. So I went looking for the dkms madwifi rpms, but could not find them. They use to be on rpmforge, as I recall. dkms is there. So have I lost some memory cells or have these rpms taken a hike?