From 8591e0cddf642b028e99d9c10be34073a023240b Mon Sep 17 00:00:00 2001 From: Michael Vogt Date: Wed, 25 Jan 2006 17:12:45 +0100 Subject: * some more thought about the upgrade problem --- DistUpgrade/TODO | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/DistUpgrade/TODO b/DistUpgrade/TODO index fa31c041..9d26eefc 100644 --- a/DistUpgrade/TODO +++ b/DistUpgrade/TODO @@ -32,4 +32,14 @@ Robustness: DescURI for each failed item and guess from it what sources.list line failed (e.g. uri.endswith("Sources{.bz2|.gz") -> deb-src, get base-uri, find 'dists' in uri etc) - \ No newline at end of file + +- don't stop if a single pkg fails to upgrade: + - the problem here is apt, in apt-pkg/deb/dpkgpm.cc it will stop if + dpkg returns a non-zero exit code. The problem with this is of course + that this may happen in the middle of the upgrade, leaving half the + packages unpacked but not configured or loads of packages unconfigured. + One possible solution is to not stop in apt but try to continue as long + as possible. The problem here is that e.g. if libnoitfy0 explodes and + evolution, update-notifer depend on it, continuing means to evo and u-n + can't be upgraded and dpkg explodes on them too. This is not more worse + than what we have right now I guess. \ No newline at end of file -- cgit v1.2.3