On Mon, Aug 22, 2005 at 12:30:01AM -0700, Steve Langasek wrote:
> On Mon, Aug 22, 2005 at 03:29:54PM +1000, Nathan Scott wrote:
> > > ...
> > > Recompiling libacl1 (itself an awkward task since the package itself
> > > segfaults in the middle when it is doing something to the postinst script)
> > > and installing the recompiled version fixes the problem.
> > Any advice/suggestions, anyone?
>
> If it *is* a kernel ABI issue, it would be appropriate for the current
> libacl1 package in sarge to include a preinst check for the running
Yep, OK. I guess I'm not following how a kernel ABI issue
could be resolved by a re-compile though (not to say it is
not an ABI issue, just that I don't understand how).
> kernel version to avoid installing a known-broken combination. Please
> see the libc6 preinst for an example of this.
On Mon, Aug 22, 2005 at 12:30:01AM -0700, Steve Langasek wrote:
> On Mon, Aug 22, 2005 at 03:29:54PM +1000, Nathan Scott wrote:
> > > ...
> > > Recompiling libacl1 (itself an awkward task since the package itself
> > > segfaults in the middle when it is doing something to the postinst script)
> > > and installing the recompiled version fixes the problem.
> > Any advice/suggestions, anyone?
>
> If it *is* a kernel ABI issue, it would be appropriate for the current
> libacl1 package in sarge to include a preinst check for the running
Yep, OK. I guess I'm not following how a kernel ABI issue
could be resolved by a re-compile though (not to say it is
not an ABI issue, just that I don't understand how).
> kernel version to avoid installing a known-broken combination. Please
> see the libc6 preinst for an example of this.
Will certainly do that if we think it will work..
thanks Steve.
--
Nathan