Saving dkpg-old files in /etc/modprobe.d doesn't make sense

Bug #125213 reported by Heike C. Zimmerer
4
Affects Status Importance Assigned to Milestone
module-init-tools (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: apt-utils

If a file in /etc/modprobe.d has been modified by the user, he/she will be
asked if it should be replaced and, depending on the answer, content will
be saved in a dpkg-old file in the same directory.

This doesn't make sense there since both the new file and the saved content
will get used; renaming to <filename>.dpkg-old doesn't deactivate anything since all
files there are considered valid.

Happened to me with alsa-base; will probably apply to other packages too, so
I'm filing a general bug against apt-utils for now (not sure, however).

Revision history for this message
Adam Conrad (adconrad) wrote :

If module-init-tools isn't ignoring dpkg conffile backups, it needs to be taught how, this isn't a dpkg bug.

Revision history for this message
Chris Jones (cmsj) wrote :

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:
status: New → Confirmed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Future versions of modprobe will only support files ending in ".conf", thus eliminating the problem.

Changed in module-init-tools:
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
what_if (jonathan-a-phelps) wrote :

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):
assignee: nobody → what_if (jonathan-a-phelps)
status: Triaged → Fix Committed
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

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):
assignee: what_if (jonathan-a-phelps) → nobody
status: Fix Committed → Triaged
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.