On Fri, May 04, 2012 at 10:17:43PM -0500, Martin McCormick wrote:
> I tried a Control-C which had no effect at all but
> hitting Escape suddenly brought things back from the dead and I
> was able to complete the safe-upgrade. The system has been
> rebooted once and came right up so it is work
I tried a Control-C which had no effect at all but
hitting Escape suddenly brought things back from the dead and I
was able to complete the safe-upgrade. The system has been
rebooted once and came right up so it is working once again.
Again thanks for the help.
Martin McCormick
--
To U
Claudius Hubig writes:
Much appreciated information not quoted, here,
> This may well be due to the pending upgrade.
>
> The problem indeed appears to be whiptail waiting for input. As
> whiptail is called with the "nocancel" option, it is unlikely that
> its return value is checked, which then
Jochen Spieker writes:
> I would just Ctrl-c and apt-get -f install, followed by another
> safe-upgrade.
You don't know how close I have come to doing that. If
it can safely figure out where to resume, it is sure worth a
try.
I have been using Linux for about ten years and this is
Hello Martin,
It is usually appreciated not to format copied content at all (i. e.
the output of dpkg etc.), since most people can do that themselves
when necessary and forcibly formatting it might lead to even uglier
things than lines longer than 80 characters :)
Martin McCormick wrote:
> PID
Claudius Hubig writes:
> Your error description is a bit obscure, so I?ll have to ask for more
> information:
I am sorry about that. Right now, it looks very much like it is
just waiting for input.
> Currently running jobs:
> - What is the output of ps auxw?
There are the usual low-number
On Fri, May 04, 2012 at 05:20:11PM +0200, Jochen Spieker wrote:
> Martin McCormick:
> >
> > So far, I do not see any error yet. I will do the tests you
> > suggested and report back. It does act just like it is waiting
> > for more input. I have type y, yes and ok and do see the echo
> > back. I w
Martin McCormick:
>
> So far, I do not see any error yet. I will do the tests you
> suggested and report back. It does act just like it is waiting
> for more input. I have type y, yes and ok and do see the echo
> back. I will post a message later describing the tests.
I would just Ctrl-c and apt-
Claudius Hubig writes:
> Your error description is a bit obscure, so I?ll have to ask for more
So far, I do not see any error yet. I will do the tests you
suggested and report back. It does act just like it is waiting
for more input. I have type y, yes and ok and do see the echo
back. I will post
Hello Martin,
Martin McCormick wrote:
> Is there any way to make safe-upgrade at least attempt
> to go to the next task or at least report why it is stuck?
Your error description is a bit obscure, so I’ll have to ask for more
information:
Currently running jobs:
- What is the output of ps
Several weeks ago, I upgraded from lenny to squeeze and
was unaware of the removal of volatile so, after removing that
line from /etc/apt/sources.list, I did
aptitude update and then aptitude safe-upgrade.
It pulled in a huge number of packages and appeared to
be doing fine until
11 matches
Mail list logo
