Re: Bug#312936: Programmes linked against libacl1 segfault in libacl1 code.

2005-06-13 Thread Nathan Scott
On Mon, Jun 13, 2005 at 07:56:13PM -0700, Steve Langasek wrote: > On Tue, Jun 14, 2005 at 11:58:02AM +1000, Nathan Scott wrote: > > Anything specific you're looking for there Steve? > > + arm: upgrade doesn't work with 2.2, but can work with 2.4.24 or above. > (perhaps also with older versio

Re: Bug#312936: Programmes linked against libacl1 segfault in libacl1 code.

2005-06-13 Thread Steve Langasek
On Tue, Jun 14, 2005 at 11:58:02AM +1000, Nathan Scott wrote: > > Do you know if upgrading to the 2.4 kernel version available in sarge makes > > a difference here? > Anything specific you're looking for there Steve? Yes: + arm: upgrade doesn't work with 2.2, but can work with 2.4.24 or above

Re: Bug#312936: Programmes linked against libacl1 segfault in libacl1 code.

2005-06-13 Thread Nathan Scott
Hi there, On Fri, Jun 10, 2005 at 04:39:26PM -0700, Steve Langasek wrote: > On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery wrote: > > I've just upgraded my system from woody to sarge. Among other upgrade > > problems I noticed that programmes like cp, mv and install were > > occ

Re: Bug#312936: Programmes linked against libacl1 segfault in libacl1 code.

2005-06-10 Thread Steve Langasek
On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery wrote: > I've just upgraded my system from woody to sarge. Among other upgrade > problems I noticed that programmes like cp, mv and install were occasionally > segfaulting (and the packages that were invoking them failing to get > i