Is there a more general reason why it makes sense to not allow switching from desktop to server mode? Or is this just to avoid the AttributeError?
When I first looked at this issue, the question I had about the code was: why do we assign a `self.tasks` attribute at all, instead of accessing `self.cache.installedTasks` when needed? I.e.,
Is there a more general reason why it makes sense to not allow switching from desktop to server mode? Or is this just to avoid the AttributeError?
When I first looked at this issue, the question I had about the code was: why do we assign a `self.tasks` attribute at all, instead of accessing `self.cache. installedTasks` when needed? I.e.,
diff --git a/DistUpgrade/ DistUpgradeCont roller. py b/DistUpgrade/ DistUpgradeCont roller. py DistUpgradeCont roller. py DistUpgradeCont roller. py roller( object) :
self. config. set("Options" ,"foreignPkgs" , "True")
self. config. set("Options" ,"foreignPkgs" , "False") installedTasks
logging. debug(" Foreign: %s" % " ".join( sorted( self.foreign_ pkgs)))
logging. debug(" Obsolete: %s" % " ".join( sorted( self.obsolete_ pkgs))) roller( object) :
index 29002e61..71a5e4f4 100644
--- a/DistUpgrade/
+++ b/DistUpgrade/
@@ -945,8 +945,6 @@ class DistUpgradeCont
else:
- if self.serverMode:
- self.tasks = self.cache.
return True
@@ -1098,7 +1096,7 @@ class DistUpgradeCont
return False
if self.serverMode: installTasks( self.tasks) : installTasks( self.cache. installedTasks) :
return False
- if not self.cache.
+ if not self.cache.
# show changes and confirm