It could work if after the package is skipped apt recreates the dependency list; this might be bad to oversee though (especially without a GUI), however adding a printout a la "These packages were originally meant to be installed: $PACKAGES Since package $PACKAGE was removed after the update began, they are NOT going to be installed [Y/n]" where n would retry with the same package included again. One could even think of a skip-broken-packages option. Since non-installed packages remain in the dpkg/apt system as to-be-upgraded there is no real problem (if apt would additionally save the status then in update-manager they could be shown as unchecked with a hint that they failed to install).
2008/5/5 Andrew Sayers <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: > > > > Another different but related case is when a package is broken/frozen > and > > the user is not able to continue (phpbb2-conf-mysql, I'm looking at > you!), > > it would be nice to have a "skip" button for packages that seem to be > > stuck. > > > > -FFM > > > > "Skip package" wouldn't really work, because later packages might rely > on the package that's hung. On the other hand, I should imagine it's > possible to kill the process, tidy up any packages that have already > been installed, then give the user the option to remove the offending > package (and any dependencies) before retrying. > > Of course, this all goes way beyond my meagre shell-scripting abilities, > so now we're just developing a feature request to present to someone else. > > - Andrew Sayers > > -- > Ubuntu-devel-discuss mailing list > Ubuntu-devel-discuss@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss >
-- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss