2007-07-11 09:22:50 |
Heike C. Zimmerer |
bug |
|
|
added bug |
2007-08-03 20:31:52 |
Michael Vogt |
apt: statusexplanation |
|
|
|
2007-08-04 02:14:13 |
Adam Conrad |
dpkg: statusexplanation |
|
If module-init-tools isn't ignoring dpkg conffile backups, it needs to be taught how, this isn't a dpkg bug.
|
|
2008-10-07 09:13:42 |
Chris Jones |
module-init-tools: status |
New |
Confirmed |
|
2008-10-07 09:13:42 |
Chris Jones |
module-init-tools: statusexplanation |
If module-init-tools isn't ignoring dpkg conffile backups, it needs to be taught how, this isn't a dpkg bug.
|
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. |
|
2009-03-09 17:18:35 |
Scott James Remnant (Canonical) |
module-init-tools: status |
Confirmed |
Triaged |
|
2009-03-09 17:18:35 |
Scott James Remnant (Canonical) |
module-init-tools: importance |
Undecided |
Low |
|
2009-03-09 17:18:35 |
Scott James Remnant (Canonical) |
module-init-tools: statusexplanation |
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. |
Future versions of modprobe will only support files ending in ".conf", thus eliminating the problem. |
|
2009-09-07 23:17:26 |
what_if |
module-init-tools (Ubuntu): status |
Triaged |
Fix Committed |
|
2009-09-07 23:17:26 |
what_if |
module-init-tools (Ubuntu): assignee |
|
what_if (jonathan-a-phelps) |
|
2009-09-08 14:49:11 |
Scott James Remnant (Canonical) |
module-init-tools (Ubuntu): status |
Fix Committed |
Triaged |
|
2009-09-08 14:49:11 |
Scott James Remnant (Canonical) |
module-init-tools (Ubuntu): assignee |
what_if (jonathan-a-phelps) |
|
|
2018-01-19 21:20:18 |
Chris Jones |
removed subscriber Chris Jones |
|
|
|