[Bug 340873] Re: modprobe requires .conf filenames since Jaunty

[Launchpad Bug Tracker]

This bug was fixed in the package oss-compat - 1

---------------
oss-compat (1) unstable; urgency=low


  * Switch to single-component versions.
  * Declare the package is "Multi-Arch: foreign", thanks to Steve Langasek
    for the hint! (Closes: #651335.)
  * Make /etc/modprobe.d/oss-compat.conf a file, handling the various
    upgrade cases, and only removing it on purge. (Closes: #649507.)
    (LP: #340873)
  * Add kmod as an alternative dependency to avoid preventing
    module-init-tools' removal.

 -- Stephen Kitt <steve at sk2.org>  Sun, 15 Jan 2012 14:06:16 +0100

** Changed in: oss-compat (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to acpi-support in Ubuntu.
https://bugs.launchpad.net/bugs/340873

Title:
  modprobe requires .conf filenames since Jaunty

Status in “acpi-support” package in Ubuntu:
  Fix Released
Status in “alsa-driver” package in Ubuntu:
  Fix Released
Status in “bluez” package in Ubuntu:
  Fix Released
Status in “irda-utils” package in Ubuntu:
  Fix Released
Status in “isdnutils” package in Ubuntu:
  New
Status in “ndiswrapper” package in Ubuntu:
  Confirmed
Status in “nvidia-kernel-common” package in Ubuntu:
  Invalid
Status in “oss-compat” package in Ubuntu:
  Fix Released
Status in “sane-backends” package in Ubuntu:
  Fix Released
Status in “acpi-support” source package in Lucid:
  Fix Released
Status in “alsa-driver” source package in Lucid:
  Triaged
Status in “bluez” source package in Lucid:
  Fix Released
Status in “irda-utils” source package in Lucid:
  Fix Released
Status in “isdnutils” source package in Lucid:
  New
Status in “ndiswrapper” source package in Lucid:
  New
Status in “nvidia-kernel-common” source package in Lucid:
  Invalid
Status in “oss-compat” source package in Lucid:
  Fix Released
Status in “sane-backends” source package in Lucid:
  Fix Released
Status in “acpi-support” source package in Jaunty:
  Fix Released
Status in “alsa-driver” source package in Jaunty:
  Fix Released
Status in “bluez” source package in Jaunty:
  Fix Released
Status in “irda-utils” source package in Jaunty:
  Won't Fix
Status in “isdnutils” source package in Jaunty:
  Won't Fix
Status in “ndiswrapper” source package in Jaunty:
  Won't Fix
Status in “nvidia-kernel-common” source package in Jaunty:
  Invalid
Status in “oss-compat” source package in Jaunty:
  Won't Fix
Status in “sane-backends” source package in Jaunty:
  Fix Released
Status in “acpi-support” source package in Karmic:
  Fix Released
Status in “alsa-driver” source package in Karmic:
  Won't Fix
Status in “bluez” source package in Karmic:
  Fix Released
Status in “irda-utils” source package in Karmic:
  Fix Released
Status in “isdnutils” source package in Karmic:
  Won't Fix
Status in “ndiswrapper” source package in Karmic:
  Won't Fix
Status in “nvidia-kernel-common” source package in Karmic:
  Invalid
Status in “oss-compat” source package in Karmic:
  Won't Fix
Status in “sane-backends” source package in Karmic:
  Fix Released

Bug description:
  Binary package hint: irda-utils

  $ grep conf /var/log/syslog|grep mod
  Mar 11 11:36:35 X24 irattach: + WARNING: All config files need .conf: /etc/modprobe.d/blacklist-scanner, it will be ignored in a future release.
  Mar 11 11:36:35 X24 irattach: + WARNING: All config files need .conf: /etc/modprobe.d/ibm_acpi.modprobe, it will be ignored in a future release.
  Mar 11 11:36:35 X24 irattach: + WARNING: All config files need .conf: /etc/modprobe.d/irda-utils, it will be ignored in a future release.
  Mar 11 11:36:35 X24 irattach: + WARNING: All config files need .conf: /etc/modprobe.d/oss-compat, it will be ignored in a future release.

  The config files for modprobe need to be renamed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/340873/+subscriptions