what_if: please don't change bug statuses like that.
This fix has not been Committed, and as far as I can tell, you're not
planning to upload it so don't assign it to yourself.
** Changed in: module-init-tools (Ubuntu)
Status: Fix Committed = Triaged
** Changed in: module-init-tools
The package module-init-tools will soon be changed to ignore all files
not ending in ' .conf '.
That change, when released, will fix this bug. As such, this bug is
merely awaiting the release of this newer version.
** Changed in: module-init-tools (Ubuntu)
Status: Triaged = Fix Committed
Future versions of modprobe will only support files ending in .conf,
thus eliminating the problem.
** Changed in: module-init-tools (Ubuntu)
Importance: Undecided = Low
Status: Confirmed = Triaged
--
Saving dkpg-old files in /etc/modprobe.d doesn't make sense
I think this makes sense - I just had to manually remove
/etc/modprobe.d/blacklist-e1000e.dpkg-bak after upgrading module-init-tools to
a version which removed blacklist-e1000e.
Without manually removing that file, the blacklist was still being honoured.
** Changed in: module-init-tools
** Changed in: dpkg (Ubuntu)
Sourcepackagename: apt = dpkg
--
Saving dkpg-old files in /etc/modprobe.d doesn't make sense
https://bugs.launchpad.net/bugs/125213
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
If module-init-tools isn't ignoring dpkg conffile backups, it needs to
be taught how, this isn't a dpkg bug.
** Changed in: module-init-tools (Ubuntu)
Sourcepackagename: dpkg = module-init-tools
--
Saving dkpg-old files in /etc/modprobe.d doesn't make sense
