Your message dated Mon, 7 Jan 2008 23:00:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#134301: dpkg upgrade problem .18 -> .19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dpkg
Version: 1.9.19
OK, I didn't research this problem very closely, but I wanted to at
least report it. I have a pretty normal woody system. When I did an
upgrade today, the first thing that dpkg was upgrade itself. Then it
started segfaulting when it tried to do just about anything.
I suspect there was a conflict with the sysvinit on which dpkg depends.
My gut feeling is that sysvinit needs to be a pre-depend or something
similar to avoid problems for other people during this upgrade.
Like I said, this isn't researched and debugged but since my dpkg was
unusable for awhile I figured it needed to be reported.
It was actually an annoying experience. How did I get around it? I
rebooted, ran dpkg --configure -a (as the segfault error message said)
and dpkg successfully finished the upgrade of sysvinit and has not
segfaulted since.
--
-- Grant Bowman <[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---
Hi,
On Sat, 2002-02-16 at 23:24:31 -0800, Grant Bowman wrote:
> * Wichert Akkerman <[EMAIL PROTECTED]> [020216 14:43]:
> > Previously Grant Bowman wrote:
> > > OK, I didn't research this problem very closely, but I wanted to at
> > > least report it. I have a pretty normal woody system. When I did an
> > > upgrade today, the first thing that dpkg was upgrade itself. Then it
> > > started segfaulting when it tried to do just about anything.
> >
> > Can you show us an exact error message?
>
> Unfortunately, not any more. I should have typescripted it but I
> didn't.
>
> I was upgrading via dselect. Everything went fine through when dpkg
> unpacked the new dpkg. Then it segfaulted. I tried to run install from
> dselect again and it unpacked sysvinit and tried to update a conf file
> but then segfaulted. I tried to run a dselect update and it segfaulted.
> It's unreproducible now on this machine. I will try on a PPC machine I
> haven't updated in awhile.
I don't think we can do much with the little information provided in
this bug report. Also the versions involved are quite ancient. Thus
closing this report.
thanks,
guillem
--- End Message ---
