Re: Bug#462677: rm assert error on arm: ((status) == RM_OK || (status) == RM_USER_DECLINED || (status) == RM_ERROR)
reassign 462677 linux-2.6
found 462677 2.6.22-6
thanks
On Mon, 2008-01-28 at 08:06:56 +0200, Guillem Jover wrote:
> On Sun, 2008-01-27 at 13:20:38 +0100, Matthias Klose wrote:
> > Guillem Jover writes:
> > > On Sat, 2008-01-26 at 23:11:32 +0100, Frank Lichtenheld wrote:
> > > > On Sat, Jan 26, 2008 at 10:03:18PM +0100, Matthias Klose wrote:
> > > > > > On Sat, 2008-01-26 at 20:59:15 +0100, Matthias Klose wrote:
> > > > > > > $ sudo dpkg -i /var/cache/apt/archives/dpkg_1.14.16.5_arm.deb
> > > > > > > (Reading database ... 31489 files and directories currently installed.)
> > > > > > > Preparing to replace dpkg 1.14.16.5 (using .../dpkg_1.14.16.5_arm.deb) ...
> > > > > > > Unpacking replacement dpkg ...
> > > > > > > rm: rm.c:371: main: Assertion `((status) == RM_OK || (status) == RM_USER_DECLINED || (status) == RM_ERROR)' failed.
> > > > > > > dpkg: error while cleaning up:
> > > > > > > subprocess rm cleanup killed by signal (Aborted)
> > > > > >
> > > > > > This assert is coming from the rm binary, and seems quite fishy. Is that
> > > > > > system ok otherwise, fs, kernel, memory etc?
> > > > >
> > > > > yes, a thecus running armel, with an arm chroot.
> > > >
> > > > Can't reproduce this on my slug.
> > >
> > > It could be related to the OABI compat layer. Which kernel version are
> > > you guys using?
> >
> > linux-image-2.6.22-3-iop32x 2.6.22-6
>
> Did you upgrade that recently? And would be possible to try with a
> non-EABI (normal arm) kernel, in case you have that chroot in a
> different partition, or maybe transfering it beforehand?
>
> Anyway, I don't think this is a problem related to dpkg in any way.
I'm just reassigning accordingly.
regards,
guillem
Reply to: