Jason Gunthorpe wrote: > Anyhow, I have no idea what you are doing here, but I don't see how it can > be an APT bug *unless* you are invoking APT from your post inst. (and > using 'exec' too boot!)
Yeah, I am similarly puzzled, and of course, I don't run apt at all in my postinst. > Basically, there is no way that the dpkg sub process (the post inst > script) would get a seg fault single from an APT proccess (the HTTP > method). The trace from dpkg can only happen if bash (your postinst > script) segs. Agreed. > I think it is more likely that the core file the submitter found is an old > one or corrupt or something and that the debconf core file is actually > still lurking someplace else. > > I'd also say that the core file itself looks bogus by the backtrace - that > sequence of call events never happens in APT. Hm. So do you want to reassign this back to debconf? -- see shy jo
