On Mon, 29 Jan 2007 12:28:50 +0000, Stephen Gran <[EMAIL PROTECTED]> said: 

> 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)'

        Hmm. And this was built with just make-kpkg, and without the
 linux-2.6 wrapper?  I wonder if this is  a  2.6.20 thing. You see,
 kbuild is the one that install the source and build symlinks;
 kernel-package does nto remove them from the tree.

__> egrep '(build|source)' /var/lib/dpkg/info/linux-image-2.6.1*.list
/var/lib/dpkg/info/linux-image-2.6.18.2-mh7-skas3-v9-pre9.list:/usr/share/doc/linux-image-2.6.18.2-mh7-skas3-v9-pre9/examples/sample.force-build-link.sh
/var/lib/dpkg/info/linux-image-2.6.18.2-mh7-skas3-v9-pre9.list:/usr/share/doc/linux-image-2.6.18.2-mh7-skas3-v9-pre9/buildinfo.gz
/var/lib/dpkg/info/linux-image-2.6.18.2-mh7-skas3-v9-pre9.list:/lib/modules/2.6.18.2-mh7-skas3-v9-pre9/source
/var/lib/dpkg/info/linux-image-2.6.18.2-mh7-skas3-v9-pre9.list:/lib/modules/2.6.18.2-mh7-skas3-v9-pre9/build
/var/lib/dpkg/info/linux-image-2.6.18-mh1-skas3-v9-pre9-fremap.list:/usr/share/doc/linux-image-2.6.18-mh1-skas3-v9-pre9-fremap/examples/sample.force-build-link.sh
/var/lib/dpkg/info/linux-image-2.6.18-mh1-skas3-v9-pre9-fremap.list:/usr/share/doc/linux-image-2.6.18-mh1-skas3-v9-pre9-fremap/buildinfo.gz
/var/lib/dpkg/info/linux-image-2.6.18-mh1-skas3-v9-pre9-fremap.list:/lib/modules/2.6.18-mh1-skas3-v9-pre9-fremap/source
/var/lib/dpkg/info/linux-image-2.6.18-mh1-skas3-v9-pre9-fremap.list:/lib/modules/2.6.18-mh1-skas3-v9-pre9-fremap/build
/var/lib/dpkg/info/linux-image-2.6.19.1-skas3-v9-pre9.list:/usr/share/doc/linux-image-2.6.19.1-skas3-v9-pre9/examples/sample.force-build-link.sh
/var/lib/dpkg/info/linux-image-2.6.19.1-skas3-v9-pre9.list:/usr/share/doc/linux-image-2.6.19.1-skas3-v9-pre9/buildinfo.gz
/var/lib/dpkg/info/linux-image-2.6.19.1-skas3-v9-pre9.list:/lib/modules/2.6.19.1-skas3-v9-pre9/source
/var/lib/dpkg/info/linux-image-2.6.19.1-skas3-v9-pre9.list:/lib/modules/2.6.19.1-skas3-v9-pre9/build

> Although the image in sid currently: [EMAIL PROTECTED]:~$ dpkg -L
> Does apparently ship a source.

        It would have shipped a build link too, if linux-2.6 had not
 deleted it.

>> 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.

        Umm, no. The fix routing fixes links, does not install new
 ones. 
sub fix_build_link {
  return unless -d "$modules_base/$version";
  # if we saved a build link in preinst, restore the link
  # This is in case there was an official header package that was
  # installed earlier -- this is a kludge
  }
  if ($relink_build_link || $force_build_link) {
    # remove dangling links or replace with link to source pkg
  }
}

>> 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.

        Right.

        manoj
-- 
Some are reborn in a human womb, evil-doers go to hell, the good go to
heaven, and those without inflowing thoughts achieve final liberation.
126
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]

Reply via email to