summaryrefslogtreecommitdiff
path: root/DistUpgrade
diff options
context:
space:
mode:
authorMichael Vogt <michael.vogt@ubuntu.com>2006-01-25 17:12:45 +0100
committerMichael Vogt <michael.vogt@ubuntu.com>2006-01-25 17:12:45 +0100
commit8591e0cddf642b028e99d9c10be34073a023240b (patch)
treeffe33ef4ef0f678895d9d6f912cdd231e483d004 /DistUpgrade
parentf8a5787cfd0143bae105db79cd28ef073ca776c4 (diff)
downloadpython-apt-8591e0cddf642b028e99d9c10be34073a023240b.tar.gz
* some more thought about the upgrade problem
Diffstat (limited to 'DistUpgrade')
-rw-r--r--DistUpgrade/TODO12
1 files changed, 11 insertions, 1 deletions
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