Re: dpkg was interrupted, you must MANUALLY *what*...????
On Tue, Oct 02, 2001 at 11:25:17PM -0500, Adam Heath wrote:
> On 3 Oct 2001, Paul Seelig wrote:
> > This happened to me as well a few times before using exclusively a
> > failing "dpkg -i foo_08-15_i386.deb" (reason: disk full) and it can
> > easily be reproduced by simply pressing ctrl-c during install.
> >
> > I guess, that rather makes it a dpkg problem which dpkg hopefully
> > should learn to handle by itself instead of bothering the user with
> > manual tinkering. If a normal admin-user has no other choice fixing
> > stuff anyway other than doing what dpkg demands, it could rather do it
> > all by itself instead of bothering the user-admin with this.
> >
> > I use a computer for making it do all the stuff i don't want to be
> > bothered with. But programs need to be cooperative in this regard.
>
> So, when a disk is full, you want dpkg to process it's updates dir,
> and write out a new status file? How do you expect it to do that,
> seeing as there is no disk space?
It happens frequently if you hit Ctrl-C during an install (perhaps
because you realize you've done something wrong, or because some package
has gone haywire), even when there are no other error conditions like
the disk being full. I initially thought it was expected behaviour
judging by the text of the error message, but perhaps dpkg could do with
a (better) SIGINT handler.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: