This one time, at band camp, Manoj Srivastava said: > 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.
Not here: ~$ dpkg -c /var/cache/apt/archives/linux-image-2.6.20-rc5-686_2.6.20~rc5-1~experimental.1~snapshot.8193_i386.deb | egrep '(build|source)' drwxr-xr-x root/root 0 2007-01-16 17:26 ./lib/modules/2.6.20-rc5-686/kernel/drivers/clocksource/ -rw-r--r-- root/root 4743 2007-01-16 17:26 ./lib/modules/2.6.20-rc5-686/kernel/drivers/clocksource/scx200_hrt.ko Although the image in sid currently: [EMAIL PROTECTED]:~$ dpkg -L linux-image-2.6.18-4-686 | egrep '(build|source)' /usr/share/doc/linux-image-2.6.18-4-686/examples/sample.force-build-link.sh /usr/share/doc/linux-image-2.6.18-4-686/buildinfo.gz /lib/modules/2.6.18-4-686/kernel/drivers/clocksource /lib/modules/2.6.18-4-686/kernel/drivers/clocksource/scx200_hrt.ko /lib/modules/2.6.18-4-686/source Does apparently ship a source. > 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. It looks like the postinst creates these links with fix_build_link and fix_source_link routines, respectively. Since the postinst creates the links, the postrm has to remove them. > 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. It is linux-image-2.6.20-rc5-686 from http://kernel-archive.buildserver.net/debian-kernel - whatevere they use to build their packages with is presumably at fault. The postinst and postrm sure look like kernel-package scripts to me, thoguh. -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
signature.asc
Description: Digital signature
