Ubuntu 16.04 Can not install module-init-tools package

Bug #1553258 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
module-init-tools (Ubuntu)
Invalid
Undecided
Taco Screen team
util-vserver (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

---Problem Description---
To be able to build an external third-party package, the package has dependency on module-init-tools.
With 16.04 kernel 4.4.0-9-generic #24-Ubuntu when trying to install module-init-tools I get this
root@powerio-le14:~# apt-get install module-init-tools
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 module-init-tools : Depends: libkmod2 (= 21-1ubuntu1) but 22-1ubuntu1 is to be installed
E: Unable to correct problems, you have held broken packages.
dpkg --list | grep libkmod2
ii libkmod2:ppc64el 22-1ubuntu1 ppc64el libkmod shared library

I tried also to force the module-init-tools package but then any apt-get check call will fail.
If I try to remove libkmod2 then it will say it will remove kernel files, etc so that sound a little risky.

Machine Type = P8

---uname output---
Linux powerio-le14 4.4.0-9-generic #24-Ubuntu SMP Mon Feb 29 19:28:28 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-138404 severity-high targetmilestone-inin1604
Changed in ubuntu:
assignee: nobody → Taco Screen team (taco-screen-team)
Luciano Chavez (lnx1138)
affects: ubuntu → module-init-tools (Ubuntu)
Revision history for this message
Brian Murray (brian-murray) wrote :

module-init-tools was a transitional package and was recently removed in xenial.

kmod (22-1) unstable; urgency=medium

  * New upstream release.
  * Set $SOURCE_DATE_EPOCH in debian/rules for reproducibility.
    (Closes: #783152)
  * Remove the module-init-tools transitional package.

Revision history for this message
Steve Langasek (vorlon) wrote :

Closing as invalid based on Brian's explanation.

Changed in module-init-tools (Ubuntu):
status: New → Invalid
Revision history for this message
Breno Leitão (breno-leitao) wrote :

Right. i still can see it on my xenial archive:

apt-cache madison module-init-tools
module-init-tools | 21-1ubuntu1 | http://ports.ubuntu.com/ubuntu-ports xenial/universe ppc64el Packages

Revision history for this message
Steve Langasek (vorlon) wrote :

> Right. i still can see it on my xenial archive:

Indeed. This is because, although the binary package is no longer built, it has references in the archive to it so it hasn't found its way to being automatically cleaned up.

http://people.canonical.com/~ubuntu-archive/NBS/module-init-tools

Most of these references are false-positives, where the package has a dependency on 'kmod | module-init-tools'. But the util-vserver package depends exclusively on module-init-tools.

I'm removing the module-init-tools binary from xenial now and opening a bug task for util-vserver, which will now not be buildable.

Revision history for this message
James Cowgill (jcowgill) wrote :

Was fixed in util-vserver 0.30.216-pre3120-1ubuntu1

Changed in util-vserver (Ubuntu):
status: New → Fix Released
Revision history for this message
Breno Leitão (breno-leitao) wrote :

Tested and finally solved.

Closing at IBM side.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.