Jonathan Nieder wrote:
> Patrick Matthäi wrote:
>> Maybe it is created by depmod, dkms or whatever. But if you purge
>> linux-headers- the symlink will become broken and it is not
>> required if you remove both (image and headers) packages. It just
>> prevents dpkg to remove /lib/modules/ :(
>
> W
Patrick Matthäi wrote:
> Maybe it is created by depmod, dkms or whatever. But if you purge
> linux-headers- the symlink will become broken and it is not
> required if you remove both (image and headers) packages. It just
> prevents dpkg to remove /lib/modules/ :(
Would it be possible to take care
Am 28.01.2012 16:14, schrieb Ben Hutchings:
> On Sat, 2012-01-28 at 14:09 +0100, Patrick Matthäi wrote:
>> Package: linux-2.6
>> Version: 3.2.1-2
>> Severity: minor
>>
>> Hello,
>>
>> if you are building kernel modules on your own (or with dkms) the
>> symlink /lib/modules//build.save will be creat
On Sat, 2012-01-28 at 14:09 +0100, Patrick Matthäi wrote:
> Package: linux-2.6
> Version: 3.2.1-2
> Severity: minor
>
> Hello,
>
> if you are building kernel modules on your own (or with dkms) the
> symlink /lib/modules//build.save will be created with the
> source /usr/src/
> If you purge all re
Package: linux-2.6
Version: 3.2.1-2
Severity: minor
Hello,
if you are building kernel modules on your own (or with dkms) the
symlink /lib/modules//build.save will be created with the
source /usr/src/
If you purge all related packages
(linux-{kbuild,image,headers}) the (now) broken symlink is not
5 matches
Mail list logo