Parent Directory
| 
Revision Log
| Sticky Revision: |
debconf-apt-progress: Handle cancellation right at the end. We don't have a process to kill at this point, but we should at least return the correct exit code.
debconf-apt-progress: If we get cancelled very early on before managing to start the process we're controlling, make sure that we don't carry on and start it anyway, and that we still return 30.
debconf-apt-progress: DEBIAN_HAS_FRONTEND is always set here at some point, even if only on the second run after starting debconf, so we need to invert our handling of the check for whether we started the debconf frontend ourselves (LP: #347648).
debconf-apt-progress: If we didn't start the debconf frontend ourselves, then it's unlikely that the passthrough child will be able to start debconf normally, so tell it to use a pipe database in that case and rely on passthrough to save answers (LP: #337306).
debconf-apt-progress: Don't send STOP if we didn't start the debconf frontend ourselves; in that case the application calling us should arrange to stop itself.
Add missing =back to debconf-apt-progress(1)'s OPTIONS section.
* Fix use of 'next' rather than 'return' in debconf-apt-progress handle_status.
* Use signal names rather than numbers in debconf-apt-progress.
* debconf-apt-progress sometimes gets captured by buggy daemons, causing tasksel to hang because $debconf_command_eof never becomes true. STATUS_READ should be the last fd to close, so checking $status_eof is sufficient (LP: #141601).
remove the new template, I don't think it will really ever be visible move paranoia code to the end, for paranoid reasons
add --dlwaypoint option, and add progress display when cancelling
better variable name
bleh, avoid ambigutity between command return code and cancelation
exit 30 if canceled
debconf-apt-progress: Notice if the child exited abnormally, and exit nonzero.
* Partial support for cancelable progress bars. While the dialog frontend cannot support them due to limitations in whiptail(1) and dialog(1), and I haven't implemented support in frontends like gnome or kde, the confmoodule does now check to see if the frontend's progress bar methods return nonzero, and will pass that nonzero status along to the caller. * Implemented support for cancelable progress bars in the passthrough frontend. * debconf-apt-progress: Check for the progress bar being canceled, and if this happens, try to kill the apt process. Users of debconf-apt-progress that want a cancelable progress bar can thus just set the progresscancel capb before calling it and everything should work. Of course, this should only be done when the apt operation being run is one that can be cleanly killed.
* debconf-apt-progress: Add --no-progress option intended to be used by apt-install in d-i.
* Make sure that apt status commands and debconf protocol commands under debconf-apt-progress are properly interleaved. Closes: #425397
reformat
* debconf-apt-progress: Avoid falling through to generic progress updating code from media-change handling.
* debconf-apt-progress: Die if debconf-apt-progress/media-change can't be displayed.
* Add support for media-change in debconf-apt-progress.
* debconf-apt-progress: Make sure to start up a debconf frontend properly (including saving/restoring @ARGV) in all modes except --config, not just in the all-in-one mode.
revert accidentally-committed and untested debconf-apt-progress change
* Add DebconfCommunicator class to debconf.py to allow speaking the debconf protocol over a debconf-communicate subprocess. Useful for querying the debconf database noninteractively.
* debconf-apt-progress: Allow --from and --to to be used with --start to change the endpoints of the created progress bar.
Call STOP after tearing down debconf-apt-progress' progress bar, to avoid leaving a zombie if some package starts a daemon that doesn't disconnect from fd 3.
Drop all the crazy debconf-copydb and temporary configuration file stuff, and just use DEBCONF_DB_REPLACE and DEBCONF_DB_OVERRIDE. This is faster and much less complex, although it does involve a change in the --config interface.
* Remove newline removal code from perl mangling in Makefile.
implement --logstderr; discard apt output by default
really fix newlines between debconf-apt-progress.conf stanzas
here it doesn't print newlines between the stanzas w/o a quoted "EOF"
* Add debconf-apt-progress, as discussed on debian-boot@, to install packages using debconf to display a progress bar. Requires apt 0.6.41.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| ViewVC Help | |
| Powered by ViewVC 1.1.5 |