On Wed, May 21, 2008 at 11:49:30PM -0700, Ross Boylan <[EMAIL PROTECTED]> was
heard to say:
> I consider this pretty serious misbehavior, since it results in
> aptitude taking action without a request to take action. However,
> this only happens in peculiar circumstances, namely an X failure
> killed my who X session.
>
> I ran aptitude in a KDE terminal and hit u, U, and g (i.e., start
> upgrade). It downloaded the debs, checked for bugs (I don't think
> there were any) and showed me the changlog. It then asked (roughly)
> Proceed with upgrade (Y/N)?
At this point aptitude is waiting for apt-listchanges to finish.
Apparently when apt-listchanges gets EOF on standard input, it
happily continues:
tty.write('apt-listchanges: ' + _('Do you want to continue? [Y/n]? '))
tty.flush()
response = tty.readline()
return response == '\n' or re.search(locale.nl_langinfo(locale.YESEXPR),
response)
I'm not sure what happens to the HUP signal. aptitude doesn't
override it anywhere; nor do apt and apt-listchanges.
I'll reassign this to apt-listchanges, since it looks like a bug
there.
Daniel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
