Bug#323999: Dangling Symlink in /lib/modules/2.6.8-2-386/source in kernel-image-2.6.8-16

[Horms <horms@debian.org>]

On Mon, Aug 22, 2005 at 12:23:03AM -0600, Bob Proulx wrote:
> Horms wrote:
> > Allyn, MarkX A wrote:
> > > There is a symbolic link at /lib/modules/2.6.8-2-386/source
> > > which points to someone's home directory (horms). The horms
> > > home directory does not exist on a new installation.
> > > 
> > > This is in the stable (Sarge) release.
> > 
> > Thanks, I'll take a look into fixing it and get it in the
> > next Sarge update. Incidently, that link isn't used for anything
> > much, so it shouldn't do much harm.
> 
> Strange that it would be there.  When I install a kernel that does not
> have the target of the source link in place then I get the following
> message (cut from the install of a locally compiled custom kernel
> compilation):
> 
>  Hmm. The package shipped with a symbolic link /lib/modules/2.6.12-1+1-p4-smp/source
>  However, I can not read it: No such file or directory
>  Therefore, I am deleting /lib/modules/2.6.12-1+1-p4-smp/source
> 
> Shouldn't the same thing have happened here with this non-existent
> link target?  The above was built with a sarge make-kpkg.  But perhaps
> in side the postinst script has changed?

I think that might be a slightly different check,
but I'm not sure.

> But I think the source link should never be shipped with the package.
> So avoiding including that would be useful.  To avoid the build link
> there is "delete_build_link := YES" in the kernel-pkg.conf file.  But
> Bob

-- 
Horms