Closing as invalid, since it already is a configuration file, so you've
probably just overwritten it by mistake.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Status: Confirmed = Invalid
--
updates of linux-restricted-modules-common clobber
/etc/default/linux-restricted-modules-common is a configuration file
already, so I'm not sure what's going on on your machine..
--
updates of linux-restricted-modules-common clobber
/etc/default/linux-restricted-modules-common
https://bugs.launchpad.net/bugs/150038
You received this bug
If you manually install upstream versions, you need to maintain them by
yourself. In hardy though, envyng will take care of installing upstream
versions.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Status: New = Invalid
--
updates of linux-restricted-modules-common clobber
Why isn't /etc/default/linux-restricted-modules-common set as a
configuration file which shouldn't be overwritten when a user changed
it, while /etc/modprobe.d/lrm-video does have user changes maintained ?
The way I see it is that you either do not allow user changes to both or
to none. This is
Ok, reopening.
** Changed in: linux-restricted-modules-2.6.24 (Ubuntu)
Sourcepackagename: linux-restricted-modules-2.6.22 =
linux-restricted-modules-2.6.24
Importance: Undecided = Low
Status: Invalid = Confirmed
--
updates of linux-restricted-modules-common clobber
