Hi,
On Mon, 29 Jan 2007 01:33:09 +0000, Stephen Gran <[EMAIL PROTECTED]>
said:
> I at first thought the source symlink might be another candidate for
> this list, but I see now that source is dpkg managed, and properly
> removed. build is not shipped in the package, so must be handled
> manually. I assume modules.seriomap is another autogenerated file.
Actually, this is not true: make-kpkg build image packages do
ship the build symlink. So, if your image package did not ship the
build link, how did it get there? I think we need to fix
a) whatever created your linux image package, since it is not
creating the symlink, and failing to remove it, or
b) whatever package created the link, and did not put into place a
mechanism to remove the link.
So, in order to flush out these packages with the bugs,
perhaps the postinst should not forcibly remove a symbolic link that
should have been removed by dpkg, under normal operations.
So, if you could provide the information about the package
creating the build symlink, and the package creating the linux image
(linux-2.6, correct?); perhaps this bug can be cloned to those
packages to clean up the symbolic link they are leaving behind.
manoj
--
Microbiology Lab: Staph Only!
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
