Hi there,
Revisiting this one, again. Firstly, since we've had no other
people reporting having hit this issue, I plan to downgrade this
from a "critical" bug... I assume if it was happening to everyone
the arm port would be unusable, certainly that would be critical;
and we'd probably have made
On Tue, Aug 23, 2005 at 08:43:09AM +1000, Nathan Scott wrote:
> 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
> > > > segfaul
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)
> >
On Mon, Aug 22, 2005 at 03:29:54PM +1000, Nathan Scott wrote:
> On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery wrote:
> > ...
> > Recompiling libacl1 (itself an awkward task since the package itself
> > segfaults in the middle when it is doing something to the postinst script)
> >
On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery 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.
Given this sta
On Fri, Jun 24, 2005 at 08:40:42AM -0400, Lennart Sorensen wrote:
> On Fri, Jun 24, 2005 at 02:29:19AM -0700, Steve Langasek wrote:
> > So are there any porters alive out there on debian-arm? Being unable to use
> > cp, mv, and install after upgrading from woody to sarge is a rather serious
> > pr
On Fri, Jun 24, 2005 at 02:29:19AM -0700, Steve Langasek wrote:
> So are there any porters alive out there on debian-arm? Being unable to use
> cp, mv, and install after upgrading from woody to sarge is a rather serious
> problem. If anyone has any ideas about this, or can test the problem with a
So are there any porters alive out there on debian-arm? Being unable to use
cp, mv, and install after upgrading from woody to sarge is a rather serious
problem. If anyone has any ideas about this, or can test the problem with a
woody vs. a sarge kernel, please speak up so that we can at the very
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
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
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
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
Package: libacl1
Version: 2.2.23-1
Severity: critical
Justification: breaks unrelated software
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
13 matches
Mail list logo
