On Sat, Dec 24, 2005 at 05:30:26PM +0000, Colin Watson wrote: > On Sat, Dec 24, 2005 at 05:03:17PM +0100, Sven Luther wrote: > > Notice that the debconf helper scripts provide stdout on &3, so any > > scripts writing to stdout only need to redirect their output to &3, no > > My impression is that these days maintainer scripts are much better > about not mixing up debconf interaction with normal use of stdout, and > so it's still possible that the fd 3 hack will be removed some day.
Ok, now i read it all, shouldn't really be replying to email after the christmas party ... :) So, do you have any idea of what is going wrong here and how to fix it ? I mean having hosed powerpc kernels over christmas is really not the nicest thing to have happen, and i really don't understand the subtleties of what is going on here. k-p uses debconf (probably using the perl helpers you mentioned), and does a db_stop before calling the script hooks. The script hooks, of which only mkvmlinuz uses debconf, but using debconf being the right thing to do probably given the debconf-related policy, so the script hooks calls debconf itself, which checks that debconf is not yet running and reruns it if not. My belief is that somehow there is an inconsistency in the debconf helper, maybe in the interaction of the perl debconf helper and especially the perl db_stop, with the shell debconf helper. Can this be ? Do we have some kind of documented spec of how these helpers do handle the debconf interaction, or something, which would enable to investigate this issue without lengthy error-and-trial ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
